Repository navigation
feat: introduce Actor data object in NCU - #65987
Open
salmart-dev wants to merge 1 commit into
Open
salmart-dev wants to merge 1 commit into
salmart-dev wants to merge 1 commit into
Conversation
Signed-off-by: Salvatore Martire <4652631+salmart-dev@users.noreply.github.com> Assisted-by: ClaudeCode:claude-opus-5-5
salmart-dev
force-pushed
the
feat/ncu-actor
branch
from
October 28, 2026 17:39
9cbcae1 to
c3c02cf
Compare
salmart-dev
marked this pull request as ready for review
October 28, 2026 17:40
salmart-dev
requested review from
icewind1991,
leftybournes,
provokateurin and
sorbaugh
and removed request for
a team
October 28, 2026 17:40
This branch has not been deployed
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
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.
Summary
Introduces an
Actordata object to pass around the information of who is performing an action / request, and include information about "privilege escalation" or delegation, so that audit or compliance apps can log a chain, and apps can take decisions losing less context and avoiding mix ups like$userId = nullequalling to "all privileges" or "no privileges" depending on the call, which are completely different answers.The
DelegationKindandPrincipalTypecould be extended in the future as "stable" cases become more prominent.Example: SystemTagManager
I took the example of the
SystemTagManager, where I stumbled on the pattern first-hand.Before
After
Checklist
3. to review, feature component)stable32)AI (if applicable)