ci: fix s3 layer cache access forbidden on 8x runners #1521
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
strophy
requested review from
shumkov,
antouhou and
QuantumExplorer
as code owners
strophy
changed the title
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.
Issue being fixed or feature implemented
Docker release action for drive was failing with
#58 ERROR: failed to check file presence in cache: operation error S3: HeadObject, https response error StatusCode: 403, RequestID: 9VNRXCFQ8K9RYSTQ, HostID: nts8Mzz86NQp8cuWQIQXD66YifLHv8H9M344MUNmV/trDlo14kJNzygIoAvB7tv0hFLWofcliEBJ7utdUVI7nw==, api error Forbidden: ForbiddenWhat was done?
Ensure correct bucket is passed to layer cache configuration step
How Has This Been Tested?
Untested
Breaking Changes
None
Checklist:
For repository code-owners and collaborators only