tflint-ruleset-google
tflint-ruleset-google copied to clipboard
TFLint ruleset for terraform-provider-google
See https://www.terraform.io/docs/providers/google/r/compute_attached_disk.html > Note: When using google_compute_attached_disk you must use lifecycle.ignore_changes = ["attached_disk"] on the google_compute_instance resource that has the disks attached. Otherwise the two resources will fight for control...
See https://www.terraform.io/docs/providers/google/r/spanner_database.html > Warning: It is strongly recommended to set lifecycle { prevent_destroy = true } on databases in order to prevent accidental data loss. See Terraform docs for more...
See https://www.terraform.io/docs/providers/google/r/usage_export_bucket.html > Note: You should specify only one of these per project. If there are two or more they will fight over which bucket the reports should be stored...
See https://www.terraform.io/docs/providers/google/r/kms_crypto_key.html > Note: CryptoKeys cannot be deleted from Google Cloud Platform. Destroying a Terraform-managed CryptoKey will remove it from state and delete all CryptoKeyVersions, rendering the key unusable, but...
See https://www.terraform.io/docs/providers/google/r/bigtable_table.html > Note: It is strongly recommended to set lifecycle { prevent_destroy = true } on tables in order to prevent accidental data loss. See Terraform docs for more...
See https://www.terraform.io/docs/providers/google/r/bigquery_table_iam.html > Note: google_bigquery_table_iam_binding resources can be used in conjunction with google_bigquery_table_iam_member resources only if they do not grant privilege to the same role.
See https://www.terraform.io/docs/providers/google/r/bigquery_table_iam.html > Note: google_bigquery_table_iam_policy cannot be used in conjunction with google_bigquery_table_iam_binding and google_bigquery_table_iam_member or they will fight over what your policy should be.
See https://www.terraform.io/docs/providers/google/r/bigquery_dataset_iam.html > Note: google_bigquery_dataset_iam_binding resources can be used in conjunction with google_bigquery_dataset_iam_member resources only if they do not grant privilege to the same role.
See https://www.terraform.io/docs/providers/google/r/bigquery_dataset_iam.html > Note: google_bigquery_dataset_iam_policy cannot be used in conjunction with google_bigquery_dataset_iam_binding and google_bigquery_dataset_iam_member or they will fight over what your policy should be.
See https://www.terraform.io/docs/providers/google/r/bigquery_dataset_iam.html > Note: These resources cannot be used with google_bigquery_dataset_access resources or the access field on google_bigquery_dataset or they will fight over what the policy should be.