feat: make force_destroy configurable (#703)

Use a variable to set the force_destroy attribute of the Cloud Storage
bucket to store the Terraform state. This is helpful to simplify the
related tutorial because we can ask users to adjust the value of the
variable, instead of asking them to modify the source code.

Author: ferrarimarco

storage/remote_terraform_backend_template/README.md

@@ -16,12 +16,12 @@ To run this example, do the following:
 
     terraform init -migrate-state
 
-
-
 <!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
 ## Inputs
 
-No inputs.
+| Name | Description | Type | Default | Required |
+|------|-------------|------|---------|:--------:|
+| terraform\_state\_bucket\_force\_destroy | Set this to true to enable destroying the Terraform remote state Cloud Storage bucket | `bool` | `false` | no |
 
 ## Outputs
 

storage/remote_terraform_backend_template/main.tf

@@ -22,14 +22,21 @@ resource "google_storage_bucket" "default" {
   name     = "${random_id.default.hex}-terraform-remote-backend"
   location = "US"
 
-  force_destroy               = false
+  force_destroy               = var.terraform_state_bucket_force_destroy
   public_access_prevention    = "enforced"
   uniform_bucket_level_access = true
 
   versioning {
     enabled = true
   }
 }
+
+variable "terraform_state_bucket_force_destroy" {
+  description = "Set this to true to enable destroying the Terraform remote state Cloud Storage bucket"
+  default     = false
+  type        = bool
+}
+
 # [END storage_bucket_tf_with_versioning_pap_uap_no_destroy]
 
 # [START storage_remote_backend_local_file]