Allow users to create and delete buckets #97

Closed
opened 2021-08-24 13:00:26 +00:00 by quentin · 2 comments
Owner

The following S3 features could benefit to Bagage:

The following S3 features could benefit to [Bagage](https://git.deuxfleurs.fr/bagage): - [CreateBucket](https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html) - [DeleteBucket](https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucket.html)
quentin added the
S3 Compatibility
label 2021-08-24 13:00:32 +00:00
quentin self-assigned this 2021-08-24 13:00:36 +00:00
quentin changed title from S3 Features that could be useful to Bagage to Features that could be useful to Bagage 2021-09-01 11:01:10 +00:00
quentin changed title from Features that could be useful to Bagage to Allow users to create and delete buckets 2021-09-07 13:28:58 +00:00
quentin removed their assignment 2021-10-18 12:17:25 +00:00
lx added the
Improvement
label 2021-11-22 14:21:17 +00:00
lx added the
Critical
label 2021-12-09 12:56:35 +00:00
Owner

This is a requirement for runing test suites such as Mint (https://github.com/minio/mint/tree/master/run/core)

This is a requirement for runing test suites such as Mint (https://github.com/minio/mint/tree/master/run/core)
lx self-assigned this 2021-12-09 12:57:08 +00:00
Author
Owner

We could implement it with an ACL on the key:

garage key allow --create-bucket --delete-bucket my-key

It would allow us to add this feature for "admin keys" without increasing the attack surface on less trusted keys?

Later, if we choose to implement quota, we could also extend our code to put some quota on these endpoints ?!

It's just a proposition.

We could implement it with an ACL on the key: ``` garage key allow --create-bucket --delete-bucket my-key ``` It would allow us to add this feature for "admin keys" without increasing the attack surface on less trusted keys? Later, if we choose to implement quota, we could also extend our code to put some quota on these endpoints ?! It's just a proposition.
lx closed this issue 2022-01-10 13:16:02 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#97
No description provided.