terraform/website/docs/backends
Paddy Carver b8752c7610 Add a backend-specific env var for the GCS backend.
Right now, the only environment variable available is the same
environment variable that will be picked up by the GCP provider. Users
would like to be able to store state in separate projects or accounts or
otherwise authenticate to the provider with a service account that
doesn't have access to the state. This seems like a reasonable enough
practice to me, and the solution seems straightforward--offer an
environment variable that doesn't mean anything to the provider to
configure the backend credentials. I've added GOOGLE_BACKEND_CREDENTIALS
to manage just the backend credentials, and documented it appropriately.
2019-12-12 03:35:39 -08:00
..
types Add a backend-specific env var for the GCS backend. 2019-12-12 03:35:39 -08:00
config.html.md website: Using demo.consul.io requires scheme = "https" 2018-06-22 10:18:27 -07:00
index.html.md website: Update URLs and name references for Terraform Cloud rebrand 2019-08-16 15:55:29 -07:00
init.html.md
legacy-0-8.html.md
operations.html.md website: Update URLs and name references for Terraform Cloud rebrand 2019-08-16 15:55:29 -07:00
state.html.md