MBS-13108: Require relationship editor, not admin, privs for attributes #3116
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.
Implement MBS-13108
Description
There's no real reason editing attributes such as activating languages or adding entity types should be locked behind
account_admin
. It has nothing to do with accounts nor private data, and a lot to do with schema / style, which is what we generally userelationship_editor
for (not just relationships but also genres, instruments).Testing
Edited the test requiring
account_admin
to requirerelationship_editor
instead.Notes
On top of #3115