-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
openapi: Add display attributes for Okta auth #19391
Conversation
logical.CreateOperation: &framework.PathOperation{ | ||
Callback: b.pathConfigWrite, | ||
DisplayAttrs: &framework.DisplayAttributes{ | ||
OperationVerb: "configure", |
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.
Will there be any limitations on what plugin authors can provide for OperationVerb
or OperationSuffix
? If so, is there a place for developers to discover this information?
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.
There are currently no limitations, just suggestions. In general the OperationID's will be constructed with prefix
+ verb
+ suffix
. If not specified, these will be implied from the path / mount path. I'll see if we can add more guidelines to tutorials/docs.
Please see #19319 for more details on how this will affect the generated OpenAPI schema.
The following OperationID's will be generated for Okta auth:
okta-read-configuration
okta-configure
okta-list-groups
okta-read-group
okta-write-group
okta-delete-group
okta-log-in
okta-list-users
okta-read-user
okta-write-user
okta-delete-user
okta-verify