Repository navigation
Clear cached promotion assets for every deployed language - #522
Merged
Merged
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
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.
The promotion upload succeeded, but cached theme assets still served the summer campaign because CloudFront only recognizes a wildcard at the end of an invalidation path. Generate explicit script and stylesheet paths for each deployed language, with trailing wildcards to include query-string variants.
After invalidation completes, compare the live JavaScript, CSS and banner image with repository files for every language so the deployment only succeeds when production serves the intended assets.
Validation: actionlint and git diff --check pass. The issue was reproduced against the live CDN after the initial deployment.