feat: enforce min and max bounds on workspace TTL and Deadline #1902
+143
−36
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
kylecarbs
approved these changes
May 30, 2022
kylecarbs
pushed a commit
that referenced
this pull request
Jun 10, 2022
* Enforces upper bound for workspace TTL * Enforces upper bound for workspace deadline
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 adds enforcement for both workspace TTL and deadline:
NOTE: These upper bounds are chosen arbitrarily; then can be changed later. The main takeaway here is that it is easier to modify an existing upper bound than it is to add a new one.
Closes #1758