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
We use Vault to generate dynamic GCP Secrets to then run terraform.
We would like to use the OAuth token rather than the json private key for all the good reasons stated here but currently we can't because while the terraform google provider support using the token , see here and the option to expose it as an environment variable, the backend does not.
I did raise a case to the terraform provider first without understanding that the backend is actually part of core
Attempted Solutions
None really since the backend only work with credentials.json
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked as resolved and limited conversation to collaborators
Dec 7, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current Terraform Version
0.11.13
Use-cases
We use Vault to generate dynamic GCP Secrets to then run terraform.
We would like to use the OAuth token rather than the json private key for all the good reasons stated here but currently we can't because while the terraform google provider support using the token , see here and the option to expose it as an environment variable, the backend does not.
I did raise a case to the terraform provider first without understanding that the backend is actually part of core
Attempted Solutions
None really since the backend only work with
credentials.json
Proposal
References
The text was updated successfully, but these errors were encountered: