feat(deps): Update Terraform Google Provider to v6 (major) - autoclosed

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending
google (source)	required_provider	major	>= 4.84, < 6 -> >= 4.84, < 7	6.3.0
google-beta (source)	required_provider	major	>= 4.84, < 6 -> >= 4.84, < 7	6.3.0

---

Release Notes

hashicorp/terraform-provider-google (google)

v6.2.0

Compare Source

FEATURES:

• New Data Source: google_certificate_manager_certificates (#​19361)
• New Resource: google_network_security_server_tls_policy (#​19314)
• New Resource: google_scc_v2_folder_scc_big_query_export (#​19327)
• New Resource: google_scc_v2_project_scc_big_query_export (#​19311)

IMPROVEMENTS:

• assuredworkload: added field partner_service_billing_account to google_assured_workloads_workload (#​19358)
• bigtable: added support for column_family.type in google_bigtable_table (#​19302)
• cloudrun: promoted support for nfs and csi volumes (for Cloud Storage FUSE) for google_cloud_run_service to GA (#​19359)
• cloudrunv2: promoted support for nfs and gcs volumes for google_cloud_run_v2_job to GA (#​19359)
• compute: added boot_disk.interface field to google_compute_instance resource (#​19319)
• container: added node_pool_auto_config.node_kublet_config.insecure_kubelet_readonly_port_enabled field to google_container_cluster. (#​19320)
• container: added insecure_kubelet_readonly_port_enabled to node_pool.node_config.kubelet_config and node_config.kubelet_config in google_container_node_pool resource. (#​19312)
• container: added insecure_kubelet_readonly_port_enabled to node_pool_defaults.node_config_defaults, node_pool.node_config.kubelet_config, and node_config.kubelet_config in google_container_cluster resource. (#​19312)
• container: added support for in-place updates for google_compute_node_pool.node_config.gcfs_config and google_container_cluster.node_config.gcfs_cluster and google_container_cluster.node_pool.node_config.gcfs_cluster (#​19365)
• container: promoted the additive_vpc_scope_dns_domain field on the google_container_cluster resource to GA (#​19313)
• iambeta: added x509 field to google_iam_workload_identity_pool_provider resource (#​19375)
• networkconnectivity: added include_export_ranges to google_network_connectivity_spoke (#​19346)
• pubsub: added cloud_storage_config.max_messages and cloud_storage_config.avro_config.use_topic_schema fields to google_pubsub_subscription resource (#​19338)
• redis: added the maintenance_policy field to the google_redis_cluster resource (#​19341)
• resourcemanager: added tags field to google_project to allow setting tags for projects at creation time (#​19351)
• securitycenter: added support for empty streaming_config.filter values in google_scc_notification_config resources (#​19369)

BUG FIXES:

• compute: fixed google_compute_interconnect to support correct available_features option of IF_MACSEC (#​19330)
• compute: fixed a bug where advertised_route_priority was accidentally set to 0 during updates in google_compute_router_peer (#​19366)
• compute: fixed a permadiff caused by setting start_time in an incorrect H:mm format in google_compute_resource_policies resources (#​19297)
• compute: fixed network_interface.subnetwork_project validation to match with the project in network_interface.subnetwork field when network_interface.subnetwork has full self_link in google_compute_instance resource (#​19348)
• container: removed unnecessary force replacement in node pool gcfs_config (#​19365
• kms: updated the google_kms_autokey_config resource's folder field to accept values that are either full resource names (folders/{folder_id}) or just the folder id ({folder_id} only) (#​19364))
• storage: added retry support for 429 errors in google_storage_bucket resource (#​19353)

v6.1.0

Compare Source

v6.0.1

Compare Source

BREAKING CHANGES:

• sql: removed settings.ip_configuration.require_ssl from google_sql_database_instance in favor of settings.ip_configuration.ssl_mode. This field was intended to be removed in 6.0.0. (#​19263)

v6.0.0

Compare Source

Terraform Google Provider 6.0.0 Upgrade Guide

BREAKING CHANGES:

• provider: changed provider labels to add the goog-terraform-provisioned: true label by default. (#​19190)
• activedirectory: added deletion_protection field to google_active_directory_domain resource. This field defaults to true, preventing accidental deletions. To delete the resource, you must first set deletion_protection = false before destroying the resource. (#​18906)
• alloydb: removed network in google_alloy_db_cluster. Use network_config.network instead. (#​19181)
• bigquery: added client-side validation to prevent table view creation if schema contains required fields for google_bigquery_table resource (#​18767)
• bigquery: removed allow_resource_tags_on_deletion from google_bigquery_table. Resource tags are now always allowed on table deletion. (#​19077)
• bigqueryreservation: removed multi_region_auxiliary from google_bigquery_reservation (#​18922)
• billing: revised the format of id for google_billing_project_info (#​18823)
• cloudrunv2: added deletion_protection field to google_cloudrunv2_service. This field defaults to true, preventing accidental deletions. To delete the resource, you must first set deletion_protection = false before destroying the resource.(#​19019)
• cloudrunv2: changed liveness_probe to no longer infer a default value from api on google_cloud_run_v2_service. Removing this field and applying the change will now remove liveness probe from the Cloud Run service. (#​18764)
• cloudrunv2: retyped containers.env to SET from ARRAY for google_cloud_run_v2_service and google_cloud_run_v2_job. (#​18855)
• composer: ip_allocation_policy = [] in google_composer_environment is no longer valid configuration. Removing the field from configuration should not produce a diff. (#​19207)
• compute: added new required field enabled in google_compute_backend_service and google_compute_region_backend_service (#​18772)
• compute: changed certifcate_id in google_compute_managed_ssl_certificate to correctly be output only. (#​19069)
• compute: revised and in some cases removed default values of connection_draining_timeout_sec, balancing_mode and outlier_detection in google_compute_region_backend_service and google_compute_backend_service. (#​18720)
• compute: revised the format of id for compute_network_endpoints (#​18844)
• compute: guest_accelerator = [] is no longer valid configuration in google_compute_instance. To explicitly set an empty list of objects, set guest_accelerator.count = 0. (#​19207)
• compute: google_compute_instance_from_template and google_compute_instance_from_machine_image network_interface.alias_ip_range, network_interface.access_config, attached_disk, guest_accelerator, service_account, scratch_disk can no longer be set to an empty block []. Removing the fields from configuration should not produce a diff. (#​19207)
• compute: secondary_ip_ranges = [] in google_compute_subnetwork is no longer valid configuration. To set an explicitly empty list, use send_secondary_ip_range_if_empty and completely remove secondary_ip_range from config. (#​19207)
• container: made advanced_datapath_observability_config.enable_relay required in google_container_cluster (#​19060)
• container: removed deprecated field advanced_datapath_observability_config.relay_mode from google_container_cluster resource. Users are expected to use enable_relay field instead. (#​19060)
• container: three label-related fields are now in google_container_cluster resource. resource_labels field is non-authoritative and only manages the labels defined by the users on the resource through Terraform. The new output-only terraform_labels field merges the labels defined by the users on the resource through Terraform and the default labels configured on the provider. The new output-only effective_labels field lists all of labels present on the resource in GCP, including the labels configured through Terraform, the system, and other clients. (#​19062)
• container: made three fields resource_labels, terraform_labels, and effective_labels be present in google_container_cluster datasources. All three fields will have all of labels present on the resource in GCP including the labels configured through Terraform, the system, and other clients, equivalent to effective_labels on the resource. (#​19062)
• container: guest_accelerator = [] is no longer valid configuration in google_container_cluster and google_container_node_pool. To explicitly set an empty list of objects, set guest_accelerator.count = 0. (#​19207)
• container: guest_accelerator.gpu_driver_installation_config = [] and guest_accelerator.gpu_sharing_config = [] are no longer valid configuration in google_container_cluster and google_container_node_pool. Removing the fields from configuration should not produce a diff. (#​19207)
• datastore: removed google_datastore_index in favor of google_firestore_index (#​19160)
• edgenetwork: three label-related fields are now in google_edgenetwork_network and google_edgenetwork_subnet resources. labels field is non-authoritative and only manages the labels defined by the users on the resource through Terraform. The new output-only terraform_labels field merges the labels defined by the users on the resource through Terraform and the default labels configured on the provider. The new output-only effective_labels field lists all of labels present on the resource in GCP, including the labels configured through Terraform, the system, and other clients. (#​19062)
• identityplatform: removed resource google_identity_platform_project_default_config in favor of google_identity_platform_project_config (#​18992)
• pubsub: allowed schema_settings in google_pubsub_topic to be removed (#​18631)
• integrations: removed create_sample_workflows and provision_gmek from google_integrations_client (#​19148)
• redis: added a deletion_protection_enabled field to the google_redis_cluster resource. This field defaults to true, preventing accidental deletions. To delete the resource, you must first set deletion_protection_enabled = false before destroying the resource. (#​19173)
• resourcemanager: added deletion_protection field to google_folder to make deleting them require an explicit intent. Folder resources now cannot be destroyed unless deletion_protection = false is set for the resource. (#​19021)
• resourcemanager: made deletion_policy in google_project 'PREVENT' by default. This makes deleting them require an explicit intent. google_project resources cannot be destroyed unless deletion_policy is set to 'ABANDON' or 'DELETE' for the resource. (#​19114)
• sql: removed settings.ip_configuration.require_ssl in google_sql_database_instance. Please use settings.ip_configuration.ssl_mode instead. (#​18843)
• storage: removed no_age field from lifecycle_rule.condition in the google_storage_bucket resource (#​19048)
• vpcaccess: removed default values for min_throughput and min_instances fields on google_vpc_access_connector and made them default to values returned from the API when not provided by users (#​18697)
• vpcaccess: added a conflicting fields restriction between min_throughput and min_instances fields on google_vpc_access_connector (#​18697)
• vpcaccess: added a conflicting fields restriction between max_throughput and max_instances fields on google_vpc_access_connector (#​18697)
• workstation: defaulted host.gce_instance.disable_ssh to true for google_workstations_workstation_config (#​19101)
  IMPROVEMENTS:
• compute: added fields reserved_internal_range and secondary_ip_ranges[].reserved_internal_range to google_compute_subnetwork resource (#​19151)
• compute: changed the behavior of name_prefix in multiple Compute resources to allow for a longer max length of 54 characters. See the upgrade guide and resource documentation for more details. (#​19152)
  BUG FIXES:
• compute: fixed an issue regarding sending enabled field by default for null iap message in google_compute_backend_service and google_compute_region_backend_service (#​18772)

hashicorp/terraform-provider-google-beta (google-beta)

v6.2.0

Compare Source

FEATURES:

• New Data Source: google_certificate_manager_certificates (#​8099)
• New Resource: google_backup_dr_backup_vault (#​8083)
• New Resource: google_scc_v2_folder_scc_big_query_export (#​8079)
• New Resource: google_scc_v2_project_scc_big_query_export (#​8070)

IMPROVEMENTS:

• assuredworkload: added field partner_service_billing_account to google_assured_workloads_workload (#​8097)
• bigtable: added support for column_family.type in google_bigtable_table (#​8069)
• cloudrunv2: added template.service_mesh to google_cloud_run_v2_service (#​8096)
• compute: added boot_disk.interface field to google_compute_instance resource (#​8075)
• container: added node_pool_auto_config.node_kublet_config.insecure_kubelet_readonly_port_enabled field to google_container_cluster. (#​8076)
• container: added insecure_kubelet_readonly_port_enabled to node_pool.node_config.kubelet_config and node_config.kubelet_config in google_container_node_pool resource. (#​8071)
• container: added insecure_kubelet_readonly_port_enabled to node_pool_defaults.node_config_defaults, node_pool.node_config.kubelet_config, and node_config.kubelet_config in google_container_cluster resource. (#​8071)
• container: added support for in-place updates for google_compute_node_pool.node_config.gcfs_config and google_container_cluster.node_config.gcfs_cluster and google_container_cluster.node_pool.node_config.gcfs_cluster (#​8101)
• iambeta: added x509 field to google_iam_workload_identity_pool_provider resource (#​8110)
• networkconnectivity: added include_export_ranges to google_network_connectivity_spoke (#​8088)
• pubsub: added cloud_storage_config.max_messages and cloud_storage_config.avro_config.use_topic_schema fields to google_pubsub_subscription resource (#​8086)
• redis: added the maintenance_policy field to the google_redis_cluster resource (#​8087)
• resourcemanager: added tags field to google_project to allow setting tags for projects at creation time (#​8091)
• securitycenter: added support for empty streaming_config.filter values in google_scc_notification_config resources (#​8105)

BUG FIXES:

• compute: fixed google_compute_interconnect to support correct available_features option of IF_MACSEC (#​8082)
• compute: fixed a bug where advertised_route_priority was accidentally set to 0 during updates in google_compute_router_peer (#​8102)
• compute: fixed a permadiff caused by setting start_time in an incorrect H:mm format in google_compute_resource_policies resources (#​8067)
• compute: fixed network_interface.subnetwork_project validation to match with the project in network_interface.subnetwork field when network_interface.subnetwork has full self_link in google_compute_instance resource (#​8089)
• kms: updated the google_kms_autokey_config resource's folder field to accept values that are either full resource names (folders/{folder_id}) or just the folder id ({folder_id} only) (#​8100)
• storage: added retry support for 429 errors in google_storage_bucket resource (#​8092)

v6.1.0

Compare Source

FEATURES:

• New Data Source: google_kms_crypto_key_latest_version (#​8032)
• New Data Source: google_kms_crypto_key_versions (#​8026)

IMPROVEMENTS:

• databasemigrationservice: added support in google_database_migration_service_connection_profile for creating DMS connection profiles that link to existing Cloud SQL instances/AlloyDB clusters. (#​8062)
• alloydb: added subscription_type and trial_metadata field to google_alloydb_cluster resource (#​8042)
• bigquery: added encryption_configuration field to google_bigquery_data_transfer_config resource (#​8045)
• bigqueryanalyticshub: added selected_resources, and restrict_direct_table_access to google_bigquery_analytics_hub_listing resource (#​8029)
• bigqueryanalyticshub: added sharing_environment_config to google_bigquery_analytics_hub_data_exchange resource (#​8029)
• cloudtasks: added http_target field to google_cloud_tasks_queue resource (#​8033)
• compute: added accelerators field to google_compute_node_template resource (#​8063)
• compute: allowed disabling server_tls_policy during update in google_compute_target_https_proxy resources (#​8023)
• datastream: added transaction_logs and change_tables to datastream_stream resource (#​8031)
• discoveryengine: added chunking_config and layout_parsing_config fields to google_discovery_engine_data_store resource (#​8049)
• dlp: added inspect_template_modified_cadence field to big_query_target and cloud_sql_target in google_data_loss_prevention_discovery_config resource (#​8054)
• dlp: added tag_resources field to google_data_loss_prevention_discovery_config resource (#​8054)

BUG FIXES:

• bigquery: fixed an error which could occur with email field values containing non-lower-case characters in google_bigquery_dataset_access resource (#​8039)
• bigqueryanalyticshub: made bigquery_dataset immutable in google_bigquery_analytics_hub_listing as it was not updatable in the API. Now modifying the field in Terraform will correctly recreate the resource rather than causing Terraform to report it would attempt an invalid update. (#​8029)
• container: fixed update inconsistency in google_container_cluster resource (#​8030)
• pubsub: fixed a validation bug that didn't allow empty filter definitions for google_pubsub_subscription resources (#​8055)
• resourcemanager: fixed a bug where data.google_client_config failed silently when inadequate credentials were used to configure the provider (#​8057)
• sql: fixed importing google_sql_user where host is an IPv4 CIDR (#​8028)
• sql: fixed overwriting of name field for IAM Group user for google_sql_user resource (#​8024)

v6.0.1

Compare Source

BREAKING CHANGES:

• sql: removed settings.ip_configuration.require_ssl from google_sql_database_instance in favor of settings.ip_configuration.ssl_mode. This field was intended to be removed in 6.0.0. (#​8043)

v6.0.0

Compare Source

Terraform Google Provider 6.0.0 Upgrade Guide

BREAKING CHANGES:

• provider: changed provider labels to add the goog-terraform-provisioned: true label by default. (#​8004)
• activedirectory: added deletion_protection field to google_active_directory_domain resource. This field defaults to true, preventing accidental deletions. To delete the resource, you must first set deletion_protection = false before destroying the resource. (#​7837)
• alloydb: removed network in google_alloy_db_cluster. Use network_config.network instead. (#​7999)
• billing: revised the format of id for google_billing_project_info (#​7793)
• bigquery: added client-side validation to prevent table view creation if schema contains required fields for google_bigquery_table resource (#​7755)
• bigquery: removed allow_resource_tags_on_deletion from google_bigquery_table. Resource tags are now always allowed on table deletion. (#​7940)
• bigqueryreservation: removed multi_region_auxiliary from google_bigquery_reservation (#​7844)
• cloudrunv2: added deletion_protection field to google_cloudrunv2_service to make deleting them require an explicit intent. This field defaults to true, preventing accidental deletions. To delete the resource, you must first set deletion_protection = false before destroying the resource. (#​7901)
• cloudrunv2: changed liveness_probe to no longer infer a default value from api on google_cloud_run_v2_service. Removing this field and applying the change will now remove liveness probe from the Cloud Run service. (#​7753)
• cloudrunv2: retyped containers.env to SET from ARRAY for google_cloud_run_v2_service and google_cloud_run_v2_job. (#​7812)
• composer: ip_allocation_policy = [] in google_composer_environment is no longer valid configuration. Removing the field from configuration should not produce a diff. (#​8011)
• compute: added new required field enabled in google_compute_backend_service and google_compute_region_backend_service (#​7758)
• compute: revised and in some cases removed default values of connection_draining_timeout_sec, balancing_mode and outlier_detection in google_compute_region_backend_service and google_compute_backend_service. (#​7723)
• compute: updated resource id for compute_network_endpoints (#​7806)
• compute: stopped the certifcate_id field in google_compute_managed_ssl_certificate resource being incorrectly marked as a user-configurable value when it should just be an output. (#​7936)
• compute: guest_accelerator = [] is no longer valid configuration in google_compute_instance. To explicitly set an empty list of objects, set guest_accelerator.count = 0. (#​8011)
• compute: google_compute_instance_from_template and google_compute_instance_from_machine_image network_interface.alias_ip_range, network_interface.access_config, attached_disk, guest_accelerator, service_account, scratch_disk can no longer be set to an empty block []. Removing the fields from configuration should not produce a diff. (#​8011)
• compute: secondary_ip_ranges = [] in google_compute_subnetwork is no longer valid configuration. To set an explicitly empty list, use send_secondary_ip_range_if_empty and completely remove secondary_ip_range from config. (#​8011)
• container: made advanced_datapath_observability_config.enable_relay required in google_container_cluster (#​7930)
• container: removed deprecated field advanced_datapath_observability_config.relay_mode from google_container_cluster resource. Users are expected to use enable_relay field instead. (#​7930)
• container: three label-related fields are now in google_container_cluster resource. resource_labels field is non-authoritative and only manages the labels defined by the users on the resource through Terraform. The new output-only terraform_labels field merges the labels defined by the users on the resource through Terraform and the default labels configured on the provider. The new output-only effective_labels field lists all of labels present on the resource in GCP, including the labels configured through Terraform, the system, and other clients. (#​7932)
• container: made three fields resource_labels, terraform_labels, and effective_labels be present in google_container_cluster datasources. All three fields will have all of labels present on the resource in GCP including the labels configured through Terraform, the system, and other clients, equivalent to effective_labels on the resource. (#​7932)
• container: guest_accelerator = [] is no longer valid configuration in google_container_cluster and google_container_node_pool. To explicitly set an empty list of objects, set guest_accelerator.count = 0. (#​8011)
• container: guest_accelerator.gpu_driver_installation_config = [] and guest_accelerator.gpu_sharing_config = [] are no longer valid configuration in google_container_cluster and google_container_node_pool. Removing the fields from configuration should not produce a diff. (#​8011)
• datastore: removed google_datastore_index in favor of google_firestore_index (#​7987)
• edgenetwork: three label-related fields are now in google_edgenetwork_network and google_edgenetwork_subnet resources. labels field is non-authoritative and only manages the labels defined by the users on the resource through Terraform. The new output-only terraform_labels field merges the labels defined by the users on the resource through Terraform and the default labels configured on the provider. The new output-only effective_labels field lists all of labels present on the resource in GCP, including the labels configured through Terraform, the system, and other clients. (#​7932)
• identityplatform: removed resource google_identity_platform_project_default_config in favor of google_identity_platform_project_config (#​7880)
• integrations: removed create_sample_workflows and provision_gmek from google_integrations_client (#​7977)
• pubsub: allowed schema_settings in google_pubsub_topic to be removed (#​7674)
• redis: added a deletion_protection_enabled field to the google_redis_cluster resource. This field defaults to true, preventing accidental deletions. To delete the resource, you must first set deletion_protection_enabled = false before destroying the resource. (#​7995)
• resourcemanager: added deletion_protection field to google_folder to make deleting them require an explicit intent. Folder resources now cannot be destroyed unless deletion_protection = false is set for the resource. (#​7903)
• resourcemanager: made deletion_policy in google_project 'PREVENT' by default. This makes deleting them require an explicit intent. google_project resources cannot be destroyed unless deletion_policy is set to 'ABANDON' or 'DELETE' for the resource. (#​7946)
• storage: removed no_age field from lifecycle_rule.condition in the google_storage_bucket resource (#​7923)
• sql: removed settings.ip_configuration.require_ssl in google_sql_database_instance. Please use settings.ip_configuration.ssl_mode instead. (#​7804)
• vpcaccess: removed default values for min_throughput and min_instances fields on google_vpc_access_connector and made them default to values returned from the API when not provided by users (#​7709)
• vpcaccess: added a conflicting fields restriction between min_throughput and min_instances fields on google_vpc_access_connector (#​7709)
• vpcaccess: added a conflicting fields restriction between max_throughput and max_instances fields on google_vpc_access_connector (#​7709)
• workstation: defaulted host.gce_instance.disable_ssh to true for google_workstations_workstation_config (#​7946)

IMPROVEMENTS:

• compute: added fields reserved_internal_range and secondary_ip_ranges[].reserved_internal_range to google_compute_subnetwork resource (#​7980)
• compute: changed the behavior of name_prefix in multiple Compute resources to allow for a longer max length of 54 characters. See the upgrade guide and resource documentation for more details. (#​7981)

BUG FIXES:

• compute: fixed an issue regarding sending enabled field by default for null iap message in google_compute_backend_service and google_compute_region_backend_service (#​7758)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[dpebot]

/gcbrun

[gservat]

@imrannayer any idea when the breaking changes for 6.x will be reviewed/implemented into the module so this PR can be merged? just asking as we're keen to upgrade to 6.x but we can't as this module is version constrained to < 6.

[riccardosalamanna]

There's at least this change that needs to be implemented

[imrannayer]

/gcbrun

[imrannayer]

@gservat Issue #451 needs to be fixed for this to work

[dpebot]

/gcbrun

[btkelly]

@imrannayer I opened a PR to this branch with the necessary changes I believe. I can open a PR directly to master but I figured keeping this PR and just adding a commit to it made more sense. Let me know if that works 👍

[dpebot]

/gcbrun