Avoid running traffic increase hooks when waiting for promotion or promoting #1470
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
Signed-off-by: ta924@yahoo.com <ta924@yahoo.com>
aryan9600
approved these changes
Aug 7, 2023
aryan9600
changed the title
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 is a fix for issue #1468. This will stop traffic increase checks once the canary has moved into promotion statuses.
The only callout that I do have here would be if both hooks are configured on the max step weight, you will have to approve the traffic increase then the following iteration will involve the confirm promotion hook. This can seem a bit redundant but it does satisfy the issue of continuous traffic increase hooks being called