-
Notifications
You must be signed in to change notification settings - Fork 545
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
Add vault_gcp_secret_roleset
#312
Add vault_gcp_secret_roleset
#312
Conversation
e2efabf
to
bc74e56
Compare
adec7f2
to
bc1fdb5
Compare
bc1fdb5
to
7385b3e
Compare
Thanks @lawliet89 ! This looks great! Should we wait until hashicorp/vault-plugin-secrets-gcp#28 lands and then use |
@tyrannosaurus-becks I've added code to handle both cases since that change might take a while to land in Vault and not everyone will upgrade right away. |
e017913
to
a9e9eda
Compare
Failure is due to unrelated |
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.
This looks fantastic! I merged master and found the tests pass. Thank you.
@tyrannosaurus-becks Is there a feel for when Edit: Ignore that comment, I've just refreshed the repo and noticed that |
Add `vault_gcp_secret_roleset`
To test this, we need to set
GOOGLE_CREDENTIALS
as a path to the JSON file containing GCP credentials, andGOOGLE_PROJECT
as the name of the GCP project to run the tests against.I have tested it locally and the test pass.
The bindings could have been passed to Vault as JSON, but it is currently bugged.