-
Notifications
You must be signed in to change notification settings - Fork 800
Add ARCHIVED state to LaunchPlanState enum #7056
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from 3 commits
8705f09
e0f3c36
9549a4c
97b152f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What if we do deactivate and archive? It shouldn't raise an error
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are three distinct states in the enum (
ACTIVE,INACTIVE,ARCHIVED), and each flag maps to exactly oneLaunchPlanStatevalue. If we allowed--deactivate --archivetogether it would be ambiguous — we'd have to silently pick one, which is more confusing than just asking the user to specify a single flag.Archive already implies the launch plan won't be scheduled (the server-side behavior disables any active schedule), so there's no need to also pass
--deactivate. If the intent is to archive,--archivealone is sufficient.