Add full s3 cp to update cdn script for aws issue workaround #5
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
…s s3 sync` -- this is the correct workaround to the problem explained in the related comment
da70
deleted the
add-full-s3-cp-to-update-cdn-script-for-aws-issue-workaround
branch
da70
restored the
add-full-s3-cp-to-update-cdn-script-for-aws-issue-workaround
branch
da70
deleted the
add-full-s3-cp-to-update-cdn-script-for-aws-issue-workaround
branch
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 enhancement I'd made to the workaround for s3 sync --exact-timestamps flag ignored for uploads #4460 in scripts/update-cdn.sh was missing a full
cp, which is now added by this PR.