Specify each verb instead of using * in project owner#55061
Merged
Conversation
andreas-kupries
previously approved these changes
May 13, 2026
Contributor
Provisioning Tests Results 7 files 42 suites 3h 49m 47s ⏱️ Results for commit d33cd93. |
pmatseykanets
approved these changes
May 13, 2026
This was referenced May 13, 2026
JonCrowther
added a commit
that referenced
this pull request
May 14, 2026
JonCrowther
added a commit
that referenced
this pull request
May 14, 2026
JonCrowther
added a commit
that referenced
this pull request
May 14, 2026
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
3 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.
Issue:
Problem
To conform to RBAC best practices, change
*permissions in project-owner to be an explicit list of verbsSolution
Testing
Engineering Testing
Manual Testing
Automated Testing
Summary: TODO
QA Testing Considerations
Regressions Considerations
TODO
Existing / newly added automated tests that provide evidence there are no regressions: