Skip to content
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

Merged
merged 17 commits into from Mar 8, 2016
Merged

Capabilities endpoint #1171

merged 17 commits into from Mar 8, 2016

Conversation

vishalnayak
Copy link
Member

Fixes #1069

}

type capabilitiesResponse struct {
Message string `json:"message"`
Copy link
Member

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.

Copy link
Member Author

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.

@vishalnayak vishalnayak force-pushed the capabilities-endpoint branch 2 times, most recently from c5ae867 to a510b80 Compare March 4, 2016 23:51
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
Copy link
Member

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..."

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

vishalnayak added a commit that referenced this pull request Mar 8, 2016
@vishalnayak vishalnayak merged commit 3ad525f into master Mar 8, 2016
@vishalnayak vishalnayak deleted the capabilities-endpoint branch March 8, 2016 18:12
rajanadar added a commit to rajanadar/VaultSharp that referenced this pull request Aug 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants