Fix manifests.txt invalidation#94
Merged
Merged
Conversation
The run yesterday failed ``` running "aws" "cloudfront" "create-invalidation" "--invalidation-batch" "file:///codebuild/output/src2735315778/src/release/payload.json" "--distribution-id" "E3NZU1LCBHH4A4" An error occurred (InvalidArgument) when calling the CreateInvalidation operation: Your request contains one or more invalid invalidation paths. ``` And the docs say > In the CloudFront console, you can omit the leading slash in the path, like this: images/image2.jpg. When you use the CloudFront API directly, invalidation paths must begin with a leading slash. So looks like that's the bug.
emilyalbini
approved these changes
Jul 6, 2025
emilyalbini
left a comment
emilyalbini
left a comment
Member
There was a problem hiding this comment.
Looks good (I gave Nora the failure log)
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
2 participants
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 run yesterday failed
And the docs say
So looks like that's the bug.