-
Notifications
You must be signed in to change notification settings - Fork 4.6k
List private definitions endpoint #11339
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
Conversation
description: true if this connector definition is available to all workspaces | ||
type: boolean | ||
default: false | ||
custom: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the definition of custom vs public? I would be careful before adding that kind of specific flags on the data model. They risk proliferating.
Are they mutually exclusive? then it should be a enum and if we foresee that it is only these two states then just one boolean
Can it be true on both? false on both? what is the expected behavior in these cases?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great points. Let me copy this over to #11305 (which has these same migration and model changes broken out into its own PR) and continue the discussion there.
Worth discussing since there was a thread about this in the design doc as well
Discussion continued in #11305 (comment)
a11e3ba
to
bab7631
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
What
Part of #9652
Tech Spec
Implements routes to list all private, non-custom definitions, and for each indicate whether the given workspace has a grant for using the definition. Used by admins to view and modify a given workspace's grants.
Depends on #11305 and #11336
Recommended reading order
Easiest to view by commit
User Impact
Doesn't change the behavior of existing routes