From 0ce11faffd75ec8eb33d0daf01e939324ec8816b Mon Sep 17 00:00:00 2001 From: Justin Long Date: Thu, 22 Oct 2020 09:35:02 -0700 Subject: [PATCH] Clear wording that bucket must pre-exist (#26276) Experienced similar issue as https://github.com/hashicorp/terraform/issues/18417 this updates the documentation so that it's more clear a storage bucket must exist prior to configuring the backend. --- website/docs/backends/types/gcs.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/backends/types/gcs.html.md b/website/docs/backends/types/gcs.html.md index 62ee24b440..b1fb6f1573 100644 --- a/website/docs/backends/types/gcs.html.md +++ b/website/docs/backends/types/gcs.html.md @@ -10,8 +10,8 @@ description: |- **Kind: Standard (with locking)** -Stores the state as an object in a configurable prefix in a given bucket on [Google Cloud Storage](https://cloud.google.com/storage/) (GCS). -This backend also supports [state locking](/docs/state/locking.html). +Stores the state as an object in a configurable prefix in a pre-existing bucket on [Google Cloud Storage](https://cloud.google.com/storage/) (GCS). +This backend also supports [state locking](/docs/state/locking.html). The bucket must exist prior to configuring the backend. ~> **Warning!** It is highly recommended that you enable [Object Versioning](https://cloud.google.com/storage/docs/object-versioning)