This repository was archived by the owner on Aug 30, 2024. It is now read-only.
feat: implement cordon/uncordon workspace provider #302
Conversation
This file contains hidden or 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
|
This pull request has been linked to Clubhouse Story #7500: More granular WSP states. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What this does?
Implements two new subcommands.
coder providers cordon
Usage
coder providers cordon --reason "cloud cost" provider-nameAllows users to cordon a provider; preventing it from supporting new workspaces.
Note : the
--reasonflag is required to explain why this action was performed.coder providers uncordon
Usage
coder providers uncordon provider-nameAlso supports uncordoning a provider; allowing the provider to continue provisioning resources for new workspaces.
Sample Output