WOR-1797 roles for rawls #1496
Merged
WOR-1797 roles for rawls #1496
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
dvoet
requested review from
a team,
blakery and
marctalbott
and removed request for
a team
marctalbott
approved these changes
Aug 5, 2024
blakery
approved these changes
Aug 6, 2024
|
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.
Ticket: https://broadworkbench.atlassian.net/browse/WOR-1797
What:
add permissions required by rawls for the tasks detailed in the ticket
Why:
see ticket for design doc
How:
Mostly adding new roles for rawls and creating resource type admin policies to grant the new role to rawls. Existing roles were used where our services require them. Roles are used instead of adding actions directly to policies to reduce database churn when altering the actions. Also there are cases where Leo required a role to exist but any role will do.
PR checklist