Use CRDB instead of SpiceDB for getting role resource #280
Conversation
This file contains 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
Roles created with no actions are not able to be retrieved or deleted in permissions-api as a result of fetching the role's resource ID from SpiceDB rather than CRDB. This commit updates the storage engine to use CRDB instead. Signed-off-by: John Schaeffer <[email protected]>
adammohammed
approved these changes
Aug 22, 2024
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.
Roles created with no actions are not able to be retrieved or deleted in permissions-api as a result of fetching the role's resource ID from SpiceDB rather than CRDB. This PR updates the storage engine to use CRDB instead.