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.
This commit is contained in:
Justin Long 2020-10-22 09:35:02 -07:00 committed by GitHub
parent bc1a841d65
commit 0ce11faffd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions

View File

@ -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)