-
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
VAULT-12144: add openapi responses for /sys/seal endpoints #18625
Conversation
Signed-off-by: Daniel Huckins <[email protected]>
Signed-off-by: Daniel Huckins <[email protected]>
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -493,6 +499,77 @@ func (b *SystemBackend) rekeyPaths() []*framework.Path { | |||
Operations: map[logical.Operation]framework.OperationHandler{ | |||
logical.UpdateOperation: &framework.PathOperation{ | |||
Summary: "Unseal the Vault.", | |||
Responses: map[int][]framework.Response{ | |||
http.StatusOK: {{ | |||
// unseal returns `vault.SealStatusResponse` struct |
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.
I see warnings as a part of SealStatusResponse
here. Should that get handled here too?
// unseal returns `vault.SealStatusResponse` struct | ||
Fields: map[string]*framework.FieldSchema{ | ||
"type": { | ||
Type: framework.TypeString, |
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 descriptions here? I believe it will affect code comments and intellisense when generating code
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.
A few small comments, but looks good otherwise
UPDATE
UPDATE
READ
N/A already done
couldn't find any tests (at least not in the same package)