feat(bucket): add access policy #63
Open
Conversation
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
acamilleri
force-pushed
the
feat/bucket-access-policy
branch
from
1c123fd to
37b2aaf
Compare
* fix(chart): duplicate rules field * fix(chart): s3 instance secret is optional * fix(chart): s3 instance namespace * fix(chart): s3 instance allowedNamespaces values as slice * fix(chart): s3 instance secret values indentation * fix(chart): s3 instance credentials secret type * fix(chart): sync crds
acamilleri
force-pushed
the
feat/bucket-access-policy
branch
from
37b2aaf to
b747f89
Compare
Donatien26
force-pushed
the
main
branch
7 times, most recently
from
7aa36da to
c77853a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi.
This is adding an accessPolicy setting on Bucket to configure the default policy of a bucket.
Following the Minio UX on the console, by default it's a private access policy, so the buckets can only be used by authenticated users.
The public access policy opens the buckets with r/w rights to all users, including anonymous.
The last one is Custom, which allows an administrator to configure the policy he wants on the bucket.
Be careful, I updated Chart.yaml !