Add S3 bucket authentication to oci-copy #1208
Merged
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
ralphbean
force-pushed
the
s3-credentials
branch
2 times, most recently
from
ed6512d to
8a6266d
Compare
chmeliik
reviewed
Jul 29, 2024
chmeliik
reviewed
Jul 29, 2024
ralphbean
force-pushed
the
s3-credentials
branch
from
b313443 to
36de6e1
Compare
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 existing bearer token auth is not sufficient for pulling from an S3 bucket. This enables just that: pulling content from an s3 bucket.
Policy mechanisms (already in place and merged) prevent redistributing content from buckets that are not explicitly allowed.