chore(deps): update terraform google provider to v6

[renovate-bot]

This PR contains the following updates:

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

---

Release Notes

hashicorp/terraform-provider-google (google)

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)

v5.43.1

Compare Source

v5.43.0

Compare Source

v5.42.0

Compare Source

v5.41.0

Compare Source

v5.40.0

Compare Source

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

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)

v5.43.1

Compare Source

NOTES:

• 5.43.1 is a backport release, and some changes will not appear in 6.X series releases until 6.1.0

BUG FIXES:

• pubsub: fixed a validation bug that didn't allow empty filter definitions for google_pubsub_subscription resources (#​8055)

v5.43.0

Compare Source

DEPRECATIONS:

• storage: deprecated lifecycle_rule.condition.no_age field in google_storage_bucket. Use the new lifecycle_rule.condition.send_age_if_zero field instead. (#​7994)

FEATURES:

• New Resource: google_kms_ekm_connection_iam_binding (#​7969)
• New Resource: google_kms_ekm_connection_iam_member (#​7969)
• New Resource: google_kms_ekm_connection_iam_policy (#​7969)
• New Resource: google_scc_v2_organization_scc_big_query_exports (#​8002)

IMPROVEMENTS:

• compute: exposed service side id as new output field forwarding_rule_id on resource google_compute_forwarding_rule (#​7972)
• container: added EXTENDED as a valid option for release_channel field in google_container_cluster resource (#​7973)
• logging: changed enable_analytics parsing to "no preference" in analytics if omitted, instead of explicitly disabling analytics in google_logging_project_bucket_config. (#​7964)
• networkservices: added idle_timeout field to the google_network_services_tcp_route resource (#​7996)
• pusbub: added validation to filter field in resource google_pubsub_subscription (#​7968)
• resourcemanager: added default_labels field to google_client_config data source (#​7992)
• vmwareengine: added PC undelete support in google_vmwareengine_private_cloud (#​8005)

BUG FIXES:

• alloydb: fixed a permadiff on psc_instance_config in google_alloydb_instance resource (#​7975)
• compute: fixed a malformed URL that affected updating the server_tls_policy property on google_compute_target_https_proxy resources (#​7988)
• compute: fixed force diff replacement logic for network_ip on resource google_compute_instance (#​7971)

v5.42.0

Compare Source

DEPRECATIONS:

• compute: setting google_compute_subnetwork.secondary_ip_range = [] to explicitly set a list of empty objects is deprecated and will produce an error in the upcoming major release. Use send_secondary_ip_range_if_empty while removing secondary_ip_range from config instead. (#​7961)

FEATURES:

• New Data Source: google_artifact_registry_locations (#​7922)
• New Data Source: google_cloud_identity_transitive_group_memberships (#​7917)
• New Resource: google_discovery_engine_schema (#​7963)
• New Resource: google_scc_folder_notification_config (#​7928)
• New Resource: google_scc_v2_folder_notification_config (#​7927)
• New Resource: google_vertex_ai_index_endpoint_deployed_index (#​7931)

IMPROVEMENTS:

• clouddeploy: added serial_pipeline.stages.strategy.canary.runtime_config.kubernetes.gateway_service_mesh.pod_selector_label and serial_pipeline.stages.strategy.canary.runtime_config.kubernetes.service_networking.pod_selector_label fields to google_clouddeploy_delivery_pipeline resource (#​7945)
• compute: added TDX instance option to confidential_instance_type instance in google_compute_instance (#​7913)
• compute: added send_secondary_ip_range_if_empty to google_compute_subnetwork (#​7961)
• discoveryengine: added skip_default_schema_creation field to google_data_store resource (#​7900)
• dns: changed load_balancer_type field from required to optional in google_dns_record_set (#​7925)
• parallelstore: added file_stripe_level, directory_stripe_level fields to google_parallelstore_instance resource (#​7942)
• servicenetworking: added update_on_creation_fail field to google_service_networking_connection resource. When it is set to true, enforce an update of the reserved peering ranges on the existing service networking connection in case of a new connection creation failure. (#​7915)
• sql: added server_ca_mode field to google_sql_database_instance resource (#​7886)

BUG FIXES:

• bigquery: made google_bigquery_dataset_iam_member non-authoritative. To remove a bigquery dataset iam member, use an authoritative resource like google_bigquery_dataset_iam_policy (#​7960)
• cloudfunctions2: fixed a "Provider produced inconsistent final plan" bug affecting the service_config.environment_variables field in google_cloudfunctions2_function resource (#​7905)
• cloudfunctions2: fixed a permadiff on storage_source.generation in google_cloudfunctions2_function resource (#​7912)
• compute: fixed issue where sub-resources managed by google_compute_forwarding_rule prevented resource deletion (#​7958)
• logging: changed google_logging_project_bucket_config.enable_analytics behavior to set "no preference" in analytics if omitted, instead of explicitly disabling analytics. (#​19126)
• workbench: fixed a bug with google_workbench_instance metadata drifting when using custom containers. (#​7959)

v5.41.0

Compare Source

DEPRECATIONS:

• resourcemanager: deprecated skip_delete field in the google_project resource. Use deletion_policy instead. (#​7817)

FEATURES:

• New Data Source: google_scc_v2_organization_source_iam_policy (#​7888)
• New Resource: google_access_context_manager_service_perimeter_dry_run_egress_policy (#​7882)
• New Resource: google_access_context_manager_service_perimeter_dry_run_ingress_policy (#​7882)
• New Resource: google_scc_v2_folder_mute_config (#​7846)
• New Resource: google_scc_v2_project_mute_config (#​7881)
• New Resource: google_scc_v2_project_notification_config (#​7892)
• New Resource: google_scc_v2_organization_source (#​7888)
• New Resource: google_scc_v2_organization_source_iam_binding (#​7888)
• New Resource: google_scc_v2_organization_source_iam_member (#​7888)
• New Resource: google_scc_v2_organization_source_iam_policy (#​7888)

IMPROVEMENTS:

• clouddeploy: added gke.proxy_url field to google_clouddeploy_target (#​7899)
• cloudrunv2: added field binary_authorization.policy to resource google_cloud_run_v2_job and resource google_cloud_run_v2_service to support named binary authorization policy. (#​7883)
• compute: added update-in-place support for the google_compute_target_https_proxy.server_tls_policy field (#​7884)
• compute: added update-in-place support for the google_compute_region_target_https_proxy.server_tls_policy field (#​7891)
• container: added auto_provisioning_locations field to google_container_cluster (#​7849)
• dataform: added kms_key_name field to google_dataform_repository resource (#​7855)
• discoveryengine: added skip_default_schema_creation field to google_discovery_engine_data_store resource (#​7900)
• gkehub: added configmanagement.management and configmanagement.config_sync.enabled fields to google_gkehub_feature_membership (#​7899)
• gkehub: added management field to google_gke_hub_feature.fleet_default_member_config.configmanagement (#​7862)
• resourcemanager: added deletion_policy field to the google_project resource. Setting deletion_policy to PREVENT will protect the project against any destroy actions caused by a terraform apply or terraform destroy. Setting deletion_policy to ABANDON allows the resource to be abandoned rather than deleted and it behaves the same with skip_delete = true. Default value is DELETE. skip_delete = true takes precedence over deletion_policy = "DELETE".
• storage: added force_destroy field to google_storage_managed_folder resource (#​7867)
• storage: added generation field to google_storage_bucket_object resource (#​7866)

BUG FIXES:

• compute: fixed google_compute_instance.alias_ip_range update behavior to avoid temporarily deleting unchanged alias IP ranges (#​7898)
• compute: fixed the bug that creation of PSC forwarding rules fails in google_compute_forwarding_rule resource when provider default labels are set (#​7873)
• sql: fixed a perma-diff in settings.insights_config in google_sql_database_instance (#​7861)

v5.40.0

Compare Source

IMPROVEMENTS:

• bigquery: added support for value DELTA_LAKE to source_format in google_bigquery_table resource (#​7841)
• compute: added access_mode field to google_compute_disk resource (#​7813)
• compute: added stack_type, and gateway_ip_version fields to google_compute_router resource (#​7801)
• container: added field ray_operator_config for resource_container_cluster (#​7795)
• monitoring: updated goal field to accept a max threshold of up to 0.9999 in google_monitoring_slo resource to 0.9999 (#​7807)
• networkconnectivity: added export_psc field to google_network_connectivity_hub resource (#​7816)
• sql: added enable_dataplex_integration field to google_sql_database_instance resource (#​7810)

BUG FIXES:

• bigquery: fixed a permadiff when handling "assets" in params in the google_bigquery_data_transfer_config resource (#​7833)
• bigquery: fixed an issue preventing certain keys in params from being assigned values in google_bigquery_data_transfer_config (#​7828)
• compute: fixed perma-diff in google_compute_router (#​7818)
• container: fixed perma-diff on node_config.guest_accelerator.gpu_driver_installation_config field in GKE 1.30+ in google_container_node_pool resource (#​7799)
• sql: fixed a perma-diff in settings.insights_config in google_sql_database_instance (#​7861)

---

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

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[dpebot]

/gcbrun