11 Commits (2cc94b4e89ccd47475c2b894e7cb9bd758ae73fc)

Author	SHA1	Message	Date
Ashlee Boyer	32f7b8ebd0	Migrating links to new format	3 years ago
bharathkkb	05ff3c3278	Add a GCS backend specific env var for impersonation	3 years ago
Liam Nesteroff	5957d2657a	Update GCS backend docs for TF >=0.12 (#32065) ... * Update gcs.mdx Updated GCS remote backend to include the >=0.12 remote backend data source formatting (incl .output before output name) * Update gcs.mdx removed old data source example * Update gcs.mdx updated to local_file and output->outputs * Update gcs.mdx removed "outputs" from the pre 0.12 ref	4 years ago
Kevin Wang	03e262a70b	chore: rewrite internal redirects (#32038)	4 years ago
Sarah French	89ef27d3b4	Add Private Service Connect endpoint support to GCS backend (#31967) ... * Add support for `storage_custom_endpoint` in `gcs` backend * Add documentation for new `storage_custom_endpoint` endpoint * Empty commit to trigger Vercel deployment	4 years ago
Sarah French	d43ec0f30f	Add customer-managed encryption key (KMS) support to GCS backend (#31786) ... * Add ability to use customer-managed KMS key to encrypt state, add acceptance tests * Change test names for different encrpytion methods * Commit files updated by `go mod tidy` * Add guard against missing ENVs to `setupKmsKey` func * Update KMS setup function to get credentials from ENVs * Update tests to not include zero-values in config This means that default values are supplied later by TF instead of supplied as config from the user This also avoids issues related to making field conflicts explicit with `ConflictsWith` * Make `encryption_key` & `kms_encryption_key` conflicting fields Removing the Default from `encryption_key` does not appear to be a breaking change when tested manually * Add ability to set `kms_encryption_key` via ENV * Refactor `encryption_key` to use `DefaultFunc` to access ENV, if set * Remove comments * Update `gcs` backend docs & descriptions in schema * Update `gcs` backend docs to include information on encryption methods * Apply technical writing suggestions from code review Co-authored-by: Matthew Garrell <69917312+mgarrell777@users.noreply.github.com> * Update documentation to remove passive voice * Change use of context in tests, add inline comment, update logs * Remove use of `ReadPathOrContents` for new field Co-authored-by: Matthew Garrell <69917312+mgarrell777@users.noreply.github.com>	4 years ago
Laura Pacilio	fa76c1dcf0	apply suggestions from PR review	4 years ago
Laura Pacilio	53d0661785	Add warning note to each backend page	4 years ago
Dylan Staley	21cbb5b392	migrate docs to mdx	4 years ago
Dylan Staley	0e48f58688	Revert "migrate docs to mdx" ... This reverts commit 3cb12b5a52.	4 years ago
Dylan Staley	3cb12b5a52	migrate docs to mdx	4 years ago