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.
We're closing the account under which the bucket was created and ownership of buckets can't be transferred. So we're recreating it.
On the new bucket I'm also using bucket policies to control object access instead of putting object ACL.
will have to update the dashboard as well: https://github.com/mui-org/mui-contributor-dashboard/blob/9010a86de7aee24aabc2dbb0ef421c8f6a267395/src/pages/SizeComparison.tsx#L150
To Do after merging:
AWS_ACCESS_KEY_ID_ARTIFACTS
andAWS_SECRET_ACCESS_KEY_ARTIFACTS
in circle env vars to the new credentials for thecircleci
useraws s3 cp s3://mui-org-material-ui/artifacts/master/ s3://mui-org-ci/artifacts/master/ --recursive
)..._TMP
vars in the circleci config with the original ones and remove the bucket fallback_TMP
vars from circleci