Bump hashicorp/google from 5.32.0 to 6.0.0 in /tf-workspace

[dependabot]

Bumps hashicorp/google from 5.32.0 to 6.0.0.

Release notes

Sourced from hashicorp/google's releases.

v6.0.0

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)

... (truncated)

Changelog

Sourced from hashicorp/google's changelog.

5.43.0 (Unreleased)

5.42.0 (August 19, 2024)

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. (#19122)

FEATURES:

• New Data Source: google_artifact_registry_locations (#19047)
• New Data Source: google_cloud_identity_transitive_group_memberships (#19038)
• New Resource: google_discovery_engine_schema (#19124)
• New Resource: google_scc_folder_notification_config (#19057)
• New Resource: google_scc_v2_folder_notification_config (#19055)
• New Resource: google_vertex_ai_index_endpoint_deployed_index (#19061)

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 (#19100)
• compute: added send_secondary_ip_range_if_empty to google_compute_subnetwork (#19122)
• discoveryengine: added skip_default_schema_creation field to google_data_store resource (#19017)
• dns: changed load_balancer_type field from required to optional in google_dns_record_set (#19050)
• firestore: added cmek_config field to google_firestore_database resource (#19107)
• 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. (#19035)
• sql: added server_ca_mode field to google_sql_database_instance resource (#18998)

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 (#19121)
• cloudfunctions2: fixed a "Provider produced inconsistent final plan" bug affecting the service_config.environment_variables field in google_cloudfunctions2_function resource (#19024)
• cloudfunctions2: fixed a permadiff on storage_source.generation in google_cloudfunctions2_function resource (#19031)
• compute: fixed issue where sub-resources managed by google_compute_forwarding_rule prevented resource deletion (#19117)
• 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. (#19119)

5.41.0 (August 13, 2024)

DEPRECATIONS:

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

FEATURES:

• New Data Source: google_logging_log_view_iam_policy (#18990)
• New Data Source: google_scc_v2_organization_source_iam_policy (#19004)
• New Resource: google_access_context_manager_service_perimeter_dry_run_egress_policy (#18994)
• New Resource: google_access_context_manager_service_perimeter_dry_run_ingress_policy (#18994)
• New Resource: google_scc_v2_folder_mute_config (#18924)
• New Resource: google_scc_v2_project_mute_config (#18993)
• New Resource: google_scc_v2_project_notification_config (#19008)
• New Resource: google_scc_v2_organization_source (#19004)
• New Resource: google_scc_v2_organization_source_iam_binding (#19004)
• New Resource: google_scc_v2_organization_source_iam_member (#19004)
• New Resource: google_scc_v2_organization_source_iam_policy (#19004)
• New Resource: google_logging_log_view_iam_binding (#18990)
• New Resource: google_logging_log_view_iam_member (#18990)

... (truncated)

Commits

• 1f38e4d 6.0.0 changelog (#19231)
• 13124b5 Update version_6_upgrade.html.markdown
• 14bf312 Merge pull request #11521 from c2thorn/main (#19214)
• 4960d0b Merge pull request #19211 from hashicorp/merge-6.0-branch
• 00b984c Merge 6.0 branch into main
• 944e9f0 Merge pull request #11513 from c2thorn/sync-main-FEATURE-BRANCH-6.0.0 (#19210)
• 301eeab Remove SchemaConfigModeAttr (#11506) (#19207)
• c76216d Fix test `TestAccSecurityCenterManagementOrganizationEventThreatDetectionCust...
• 08d0600 Promoted labelFingerprint field to GA (#11504) (#19204)
• cfed4de Merge pull request #11499 from c2thorn/sync-main-FEATURE-BRANCH-6.0.0 (#19194)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #221.