Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

introduce caveat context in PermissionService #40

Merged
merged 1 commit into from
Oct 14, 2022

Conversation

vroldanbet
Copy link
Contributor

@vroldanbet vroldanbet commented Oct 5, 2022

Part of authzed/spicedb#881
Part of authzed/spicedb#882
Part of authzed/spicedb#880

this makes it possible for clients to provide context for caveat evaluation at request time.
This context will be injected at evaluation time and influence the evaluation result.

@vroldanbet vroldanbet self-assigned this Oct 5, 2022
@vroldanbet vroldanbet marked this pull request as ready for review October 5, 2022 18:28
@vroldanbet vroldanbet force-pushed the add-caveat-context-to-permission-service branch from 3f47eb1 to 008d221 Compare October 6, 2022 18:04
@vroldanbet vroldanbet force-pushed the add-caveat-context-to-permission-service branch 3 times, most recently from 3d87dec to 4df875a Compare October 6, 2022 18:09
@vroldanbet vroldanbet force-pushed the add-caveat-context-to-permission-service branch from 4df875a to c962285 Compare October 6, 2022 18:49
@@ -4,10 +4,9 @@ on:
push:
branches:
- "!dependabot/*"
- "*"
- "main"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why was this changed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we don't get duplicated CI builds running in a PR. It's the same pattern we use in other repos.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you put that as a distinct commit then and explain that in the message?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

addressed in 1a3254e

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ideally, development would be done on a fork and this value should be * so that if we were to produce a v2 branch etc... it would run CI correctly.

this makes it possible for clients to provide
context for caveat evaluation at request time.
This context will be injected at evaluation
time and influence the evaluation result.
@vroldanbet vroldanbet force-pushed the add-caveat-context-to-permission-service branch from c962285 to 5b454a7 Compare October 7, 2022 15:43
josephschorr
josephschorr previously approved these changes Oct 7, 2022
Copy link
Member

@josephschorr josephschorr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jakedt jakedt requested a review from jzelinskie October 12, 2022 16:07
@vroldanbet vroldanbet force-pushed the add-caveat-context-to-permission-service branch from 1a3254e to 5b454a7 Compare October 14, 2022 17:44
@vroldanbet vroldanbet merged commit d693bb0 into main Oct 14, 2022
@vroldanbet vroldanbet deleted the add-caveat-context-to-permission-service branch October 14, 2022 17:46
@github-actions github-actions bot locked and limited conversation to collaborators Oct 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants