-
Notifications
You must be signed in to change notification settings - Fork 25
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
Read GCP role returns different value than described in documentation #56
Comments
Thanks for highlighting this. This was changed recently in #52 I will review/update the Vault docs. |
kalafut
pushed a commit
to hashicorp/vault
that referenced
this issue
Nov 14, 2018
kalafut
added a commit
to hashicorp/vault
that referenced
this issue
Nov 15, 2018
kalafut
added a commit
to hashicorp/vault
that referenced
this issue
Nov 15, 2018
Thanks for fixing this @kalafut! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The type of a gcp role when running a read operation is named "role" instead of "role_type" as described in the documentation.
To Reproduce
Please note the "role" attribute set to gce here.
Expected behavior
As described in the documentation the "role" attribute should be named "role_type".
Environment:
vault status
): 0.11.4vault version
): 0.11.4Additional context
This breaks functionality in the terraform-provider-vault. Which is the expected value here? "role_type" as in the documentation (then it is a bug), or "role" as in the current implementation (then the documentation should be updated (and I will take care of the terraform provider), or a totally different name such as "type" which is used when creating a gcp role initially.
The text was updated successfully, but these errors were encountered: