-
Notifications
You must be signed in to change notification settings - Fork 144
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
add graph foreign key to nodegroup #11396
Comments
whatisgalen
added a commit
that referenced
this issue
Aug 23, 2024
whatisgalen
added a commit
that referenced
this issue
Aug 23, 2024
12 tasks
whatisgalen
added a commit
that referenced
this issue
Aug 23, 2024
whatisgalen
added a commit
that referenced
this issue
Aug 23, 2024
whatisgalen
added a commit
that referenced
this issue
Aug 23, 2024
whatisgalen
added a commit
that referenced
this issue
Aug 23, 2024
whatisgalen
added a commit
that referenced
this issue
Aug 23, 2024
whatisgalen
added a commit
that referenced
this issue
Aug 23, 2024
whatisgalen
added a commit
that referenced
this issue
Aug 23, 2024
whatisgalen
added a commit
that referenced
this issue
Aug 24, 2024
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is an outcome from this forum post. Basically, the nodegroups are the primary elements that makeup a graph and nodegroupids are unique globally. Given that many of the permissions methods focus on nodegroup-permissions, to get the graph it ought to be easy, but instead we do so via a roundabout nodegroup --> node --> graph, when the structure actually looks like this: graph --> nodegroup --> node. This issue also directly supports a solution for #11217 in that the existing methods to get nodegroup permissions could simply be extended to also supply resource-model permissions
The text was updated successfully, but these errors were encountered: