[Feature] Allow the specification of parameter overrides per schedule #2919
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cicdw
approved these changes
Feb 5, 2025
znicholasbrown
approved these changes
Feb 5, 2025
|
cooool |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the
ScheduleFormModalto provide an input for parameter overrides for an individual schedule.By default, schedules start with no overrides, but users can choose which parameters should be overridden. After choosing a parameter to override, the form will update to include fields for that parameter with the default value defined on the base deployment.
Here's what it looks like in action:
Screen.Recording.2025-02-05.at.11.59.52.AM.mov
Closes OSS-6191