feat: Implement authorizers to use data from ProjectAuth graph #1688
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
15 tasks
only there we have all dependencies in scope.
eikek
force-pushed
the
1538-authorize-via-project-auth
branch
from
32a258e
to
b483c19
Compare
jachro
approved these changes
Sep 4, 2023
Merged
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.
This implements
SecurityRecordFinderby using the new data in theProjectAuthgraph. Previous corresponding classes are removed. The finders by dataset id and sameAs are moved to the kg module, since only here all required dependencies are available (and to add to thinning out the graph-commons module). The finder by slug stays in graph-commons, because it is used together with a GL based one and thought to keep that for now.