chore: refactor request models to include scope #3104
Merged
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.
scope
to request model to aide in authz, as we will be 'scoping' authz policies to be at thenamespace
,flag
,segment
, andtoken
levels. ie we wont support policies where you can update a flag but not a variant since variants are 'nested' under flagsscope
is present, then we will fallback to thesubject
for authznamespaced
interface torequestor
as we'll need to be able to get the namespace of the request for future RBAC supportI initially was going to have the
Request
also know how to 'create' it's own audit event, however I realized this wasn't really possible since the majority of audit events include the entire object / structure after the response has already been constructed, which we wont have at 'request time'