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.
/cc @erwinmombay Does Canary config differing from Prod config actually work? ( I don't remember ever doing this in the past. It does make sense for us to do this here, just want to make sure it actually does something)
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.
https://github.com/ampproject/amphtml/blob/89b69a952b27c091e2a594a297a73c1afcbcf800/build-system/global-configs/README.md
I think per this documentation,
canary-config.json
is actually just 1% of production, so for 1%, we can just opt in all of canary and leave production alone.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.
yeah Canary always goes to 1% of production on or around Wednesdays anyway. it is fine to keep what you have. May endup being ~1.5%