feat: Blueapi policy#304
Open
Alexj9837 wants to merge 1 commit into
Open
Conversation
Alexj9837
force-pushed
the
blueapi_policy
branch
4 times, most recently
from
55a4d89 to
22857f8
Compare
Collaborator
|
I don't think we're ever going to have task data available in OPA. Most of these task checks will have to be on the blueapi side. |
tpoliaw
requested changes
May 26, 2026
Collaborator
tpoliaw
left a comment
tpoliaw
left a comment
There was a problem hiding this comment.
Might need a rebase, this is wiping out the tiled service account change
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
2 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.
Jira ticket
Adds Rego policy for blueapi task submission and querying.
task ownership (delete,query,about) by comparing "user" in the meta against fedid