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
..
backend.go	Add a backend-specific env var for the GCS backend.	2019-12-12 03:35:39 -08:00
backend_state.go	terraform: Ugly huge change to weave in new State and Plan types	2018-10-16 19:11:09 -07:00
backend_test.go	backend/gcs: Mark the unused attributes project and region as removed.	2019-03-19 17:29:04 -07:00
client.go	backend/gcs: make Unlock error message more clear	2019-05-27 20:07:14 -07:00