-
Notifications
You must be signed in to change notification settings - Fork 894
feat: Add provisioner force-cancel flag #4947
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
Merged
mtojek
merged 4 commits into
coder:main
from
mtojek:4586-increase-cancellation-timeout-b
Nov 8, 2022
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next
Next commit
feat: Add provisionerd force cancel flag
- Loading branch information
commit adfd782ab8d5225dd1678a48f742e1e0987d5eab
There are no files selected for viewing
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 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
Oops, something went wrong.
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.
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.
We have another config called
ProvisionerDaemons
. I think it would be sensible to unify these underProvisioner.Daemons
andProvisioner.ForceCancelInterval
?Should be a non-breaking change as well since the flag/env translate to the same.
Uh oh!
There was an error while loading. Please reload this page.
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.
I assumed that this would be a breaking change if there is a customer who uses the
ProvisionerDaemons
. I'm for unification, but a bit concerned about disturbing somebody's environment.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.
I think it should be fine. Neither flag or env should break (was
PROVISIONER_DAEMONS
and will be the same in the new structure, please correct me if I’m wrong @f0ssel).The only breakage I can think if is when used as part of
server.yaml
. But it’s a recent addition and not widely used yet AFAIK.There may be even more breaking changes to this in the future as we split out provisionerd servers from the coderd server.