From 473488f5d1385c57464fb3729d8b958efa7d8d8e Mon Sep 17 00:00:00 2001 From: The Magician Date: Mon, 13 Nov 2023 14:53:56 -0800 Subject: [PATCH] Update doc links for lifecycle meta argument (#9461) (#16526) [upstream:5320b7984e43c4f7ff843058ea029551327e4a06] Signed-off-by: Modular Magician --- .changelog/9461.txt | 3 +++ website/docs/r/api_gateway_gateway.html.markdown | 3 ++- website/docs/r/kms_crypto_key.html.markdown | 5 +++-- website/docs/r/spanner_database.html.markdown | 3 ++- 4 files changed, 10 insertions(+), 4 deletions(-) create mode 100644 .changelog/9461.txt diff --git a/.changelog/9461.txt b/.changelog/9461.txt new file mode 100644 index 00000000000..fd34606df73 --- /dev/null +++ b/.changelog/9461.txt @@ -0,0 +1,3 @@ +```release-note:none +kms: added link for `lifecycle` argument to documentation for `google_kms_crypto_key` +``` diff --git a/website/docs/r/api_gateway_gateway.html.markdown b/website/docs/r/api_gateway_gateway.html.markdown index b9ac960e6d6..2ba5ba6dc21 100644 --- a/website/docs/r/api_gateway_gateway.html.markdown +++ b/website/docs/r/api_gateway_gateway.html.markdown @@ -75,7 +75,8 @@ The following arguments are supported: * `api_config` - (Required) Resource name of the API Config for this Gateway. Format: projects/{project}/locations/global/apis/{api}/configs/{apiConfig}. - When changing api configs please ensure the new config is a new resource and the lifecycle rule `create_before_destroy` is set. + When changing api configs please ensure the new config is a new resource and the + [lifecycle](https://developer.hashicorp.com/terraform/language/meta-arguments/lifecycle) rule `create_before_destroy` is set. * `gateway_id` - (Required) diff --git a/website/docs/r/kms_crypto_key.html.markdown b/website/docs/r/kms_crypto_key.html.markdown index 5f052d48cab..a0f6908d1e0 100644 --- a/website/docs/r/kms_crypto_key.html.markdown +++ b/website/docs/r/kms_crypto_key.html.markdown @@ -27,8 +27,9 @@ Destroying a Terraform-managed CryptoKey will remove it from state and delete all CryptoKeyVersions, rendering the key unusable, but *will not delete the resource from the project.* When Terraform destroys these keys, any data previously encrypted with these keys will be irrecoverable. -For this reason, it is strongly recommended that you add lifecycle hooks -to the resource to prevent accidental destruction. +For this reason, it is strongly recommended that you add +[lifecycle](https://developer.hashicorp.com/terraform/language/meta-arguments/lifecycle) +hooks to the resource to prevent accidental destruction. To get more information about CryptoKey, see: diff --git a/website/docs/r/spanner_database.html.markdown b/website/docs/r/spanner_database.html.markdown index e4ac1abd4e0..81e68fdc246 100644 --- a/website/docs/r/spanner_database.html.markdown +++ b/website/docs/r/spanner_database.html.markdown @@ -32,7 +32,8 @@ To get more information about Database, see: (and run `terraform apply` to write the field to state) in order to destroy an instance. It is recommended to not set this field (or set it to true) until you're ready to destroy. On older versions, it is strongly recommended to set `lifecycle { prevent_destroy = true }` -on databases in order to prevent accidental data loss. See [Terraform docs](https://www.terraform.io/docs/configuration/resources.html#prevent_destroy) +on databases in order to prevent accidental data loss. See +[Terraform docs](https://developer.hashicorp.com/terraform/language/meta-arguments/lifecycle#prevent_destroy) for more information on lifecycle parameters.