-
Notifications
You must be signed in to change notification settings - Fork 3
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
PLTCONN-3883: Implement changes to support Direct permission config in connector spec that will show up in UI #41
Conversation
…ec that will show up in UI
…ec that will show up in UI
…ec that will show up in UI
…ec that will show up in UI
lib/commands/command.ts
Outdated
@@ -157,5 +163,5 @@ export type AccountSchema = Schema & { | |||
* Entitlement schema | |||
*/ | |||
export type EntitlementSchema = Schema & { | |||
type: string | |||
type: string, |
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.
Do we want to add the boolean flag here also?
lib/commands/std-entitlement-list.ts
Outdated
@@ -18,5 +18,6 @@ export type StdEntitlementListInput = { | |||
export type StdEntitlementListOutput = ObjectOutput & { | |||
type: string | |||
deleted?: boolean | |||
attributes: Attributes | |||
attributes: Attributes, | |||
permissions: Permission[] |
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 about the entitlement read command? Also if we want to have permission as part of the attribute, we don't need to worry about it here at all
…tor spec that will show up in UI
Description
What is the intent of this change and why is it being made?
Add permissions to entitlements
How Has This Been Tested?
What testing have you done to verify this change?
Manual testing