You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm happy to make a PR to one of these two code bases to true up the matter. However I would be interested to hear from the maintainers here on the background context. I.e., is LIST request to the /azure/role path the intended specification (in which case we can update the Vault repository's docs) or is the documentation accurately capturing the intended path (in which case, the path_role.go source within this codebase should presumably be updated to match the path listed within https://github.com/hashicorp/vault's documentation).
The text was updated successfully, but these errors were encountered:
jeffwecan
changed the title
Ambiguity In List Roles Path
Ambiguity In List Roles Path - vault-plugin-auth-azure Versus Upstream Azure Auth Documentation
Feb 1, 2019
Within https://github.com/hashicorp/vault-plugin-auth-azure/blob/24c521e5d747a42fb2c746ddea23a6a183a146c3/path_role.go, the "List Roles" path appears to be defined as plain 'ole
/role
however the related https://github.com/hashicorp/vault documentation specifies a path of/azure/roles
: https://github.com/hashicorp/vault/blob/068da60712ce8ccc260513b564bd862b110deadd/website/source/api/secret/azure/index.html.md#list-roles.I'm happy to make a PR to one of these two code bases to true up the matter. However I would be interested to hear from the maintainers here on the background context. I.e., is LIST request to the
/azure/role
path the intended specification (in which case we can update the Vault repository's docs) or is the documentation accurately capturing the intended path (in which case, thepath_role.go
source within this codebase should presumably be updated to match the path listed within https://github.com/hashicorp/vault's documentation).The text was updated successfully, but these errors were encountered: