feat(rbac): add Role-Based Access Control to pulp_npm - #414
Open
CryptoRodeo wants to merge 1 commit into
Open
Conversation
CryptoRodeo
force-pushed
the
feat/add-rbac
branch
2 times, most recently
from
August 3, 2026 20:51
3971090 to
2b040a9
Compare
Enable fine-grained permission enforcement across all npm resources. Users can now be assigned creator, owner, or viewer roles on repositories, remotes, and distributions, with object-level scoping and cross-object permission checks. Signed-off-by: Bryan ramos <bramos@redhat.com> Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
CryptoRodeo
force-pushed
the
feat/add-rbac
branch
from
August 3, 2026 20:52
2b040a9 to
8681ff7
Compare
CryptoRodeo
marked this pull request as ready for review
August 3, 2026 21:00
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
1 participant
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.
Enable fine-grained permission enforcement across all npm resources. Users can now be assigned creator, owner, or viewer roles on repositories, remotes, and distributions, with object-level scoping and cross-object permission checks.
fixes #387
📜 Checklist
See: Pull Request Walkthrough