Add child bucket: inherit all parent permissions#311
Merged
Conversation
Coverage Report
|
TimCsaky
approved these changes
Jul 7, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
When creating a child bucket, all of the parent bucket's permissions are now also applied to said child bucket.
This prevents an edge case where child buckets created by non-IDIR users cannot be deleted; the creator as a non-IDIR user won't be able to delete buckets (see #307), nor can any IDIR users that have bucket deletion permissions on the parent, as only the user creating the child bucket will have permissions assigned to it.
Not part of any existing ticket, but this issue was discovered while testing SHOWCASE-3980.
Types of changes
New feature (non-breaking change which adds functionality)
Checklist
Further comments
N/A