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
Capabilities endpoint #1171
Capabilities endpoint #1171
Conversation
} | ||
|
||
type capabilitiesResponse struct { | ||
Message string `json:"message"` |
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.
Having a separate message feedback mechanism is inconsistent with the rest of Vault. I don't think it's really needed. If there are no capabilities, simply return ["deny"] since that's the default. If it's root, I'd take advantage of the Warnings field (resp.AddWarning) and return the notification that way.
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 was wanting to ask you about Warnings. Thanks!
I'll do this.
c5ae867
to
a510b80
Compare
a510b80
to
7f832f2
Compare
d1474ee
to
b5ca8ba
Compare
Usage: vault capabilities [options] [token] path | ||
|
||
Fetch the capabilities of a token on a given path. | ||
If a token is provided as an argument, '/sys/capabilities' endpoint will be invoked |
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.
nitpick: it should be "the '/sys/capabilities' endpoint..."
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.
done
Fixes #1069