Bump hashicorp/google from 6.5.0 to 6.7.0 in /src

[dependabot]

Bumps hashicorp/google from 6.5.0 to 6.7.0.

Release notes

Sourced from hashicorp/google's releases.

v6.7.0

FEATURES:

• New Resource: google_healthcare_pipeline_job (#19717)
• New Resource: google_secure_source_manager_branch_rule (#19773)

IMPROVEMENTS:

• container: google_container_cluster will now accept server-specified values for node_pool_auto_config.0.node_kubelet_config when it is not defined in configuration and will not detect drift. Note that this means that removing the value from configuration will now preserve old settings instead of reverting the old settings. (#19817)
• discoveryengine: added chat_engine_config.dialogflow_agent_to_link field to google_discovery_engine_chat_engine resource (#19723)
• networkconnectivity: added field migration to resource google_network_connectivity_internal_range (#19757)
• networkservices: added routing_mode field to google_network_services_gateway resource (#19764)

BUG FIXES:

• bigtable: fixed an error where BigTable IAM resources could be created with conditions but the condition was not stored in state (#19725)
• container: fixed issue which caused to not being able to disable enable_cilium_clusterwide_network_policy field on google_container_cluster. (#19736)
• container: fixed a diff triggered by a new API-side default value for node_config.0.kubelet_config.0.insecure_kubelet_readonly_port_enabled. Terraform will now accept server-specified values for node_config.0.kubelet_config when it is not defined in configuration and will not detect drift. Note that this means that removing the value from configuration will now preserve old settings instead of reverting the old settings. (#19817)
• dataproc: fixed a bug in google_dataproc_cluster that prevented creation of clusters with internal_ip_only set to false (#19782)
• iam: addressed google_service_account creation issues caused by the eventual consistency of the GCP IAM API by ignoring 403 errors returned on polling the service account after creation. (#19727)
• logging: fixed the whitespace permadiff on exclusions.filter field in google_logging_billing_account_sink, google_logging_folder_sink, google_logging_organization_sink and google_logging_project_sink resources (#19744)
• pubsub: fixed permadiff with configuring an empty retry_policy. (#19784)
• secretmanager: fixed the issue of unpopulated fields labels, annotations and version_destroy_ttl in the terraform state for the google_secret_manager_secrets datasource (#19748)

v6.6.0

FEATURES:

• New Resource: google_dataproc_batch (#19686)
• New Resource: google_healthcare_pipeline_job (#19717)
• New Resource: google_site_verification_owner (#19641)

IMPROVEMENTS:

• assuredworkloads: added HEALTHCARE_AND_LIFE_SCIENCES_CONTROLS and HEALTHCARE_AND_LIFE_SCIENCES_CONTROLS_WITH_US_SUPPORT enum values to compliance_regime in the google_assuredworkload_workload resource (#19714)
• compute: added bgp_best_path_selection_mode ,bgp_bps_always_compare_med and bgp_bps_inter_region_cost fields to google_compute_network resource (#19708)
• compute: added next_hop_origin ,next_hop_med and next_hop_inter_region_cost output fields to google_compute_route resource (#19708)
• compute: added enum STATEFUL_COOKIE_AFFINITY and strong_session_affinity_cookie field to google_compute_backend_service and google_compute_region_backend_service resource (#19665)
• compute: moved TDX instance option for confidential_instance_type in google_compute_instance from Beta to GA (#19706)
• containeraws: added kubelet_config field group to the google_container_aws_node_pool resource (#19714)
• pubsub: added GCS ingestion settings and platform log settings to google_pubsub_topic resource (#19669)
• sourcerepo: added create_ignore_already_exists field to google_sourcerepo_repository resource (#19716)
• sql: added in-place update support for settings.time_zone in google_sql_database_instance resource (#19654)
• tags: increased maximum accepted input length for the short_name field in google_tags_tag_key and google_tags_tag_value resources (#19712)

BUG FIXES:

• bigquery: fixed google_bigquery_dataset_iam_member to be able to delete itself and overwrite the existing iam members for bigquery dataset keeping the authorized datasets as they are. (#19682)
• bigquery: fixed an error which could occur with service account field values containing non-lower-case characters in google_bigquery_dataset_access (#19705)
• compute: fixed an issue where the boot_disk.initialize_params.resource_policies field in google_compute_instance forced a resource recreation when used in combination with google_compute_disk_resource_policy_attachment (#19692)
• compute: fixed the issue that labels is not set when creating the resource google_compute_interconnect (#19632)
• tags: removed google_tags_location_tag_binding resource from the Terraform state when its parent resource has been removed outside of Terraform (#19693)
• workbench: fixed a bug in the google_workbench_instance resource where the removal of labels was not functioning as expected. (#19620)

Changelog

Sourced from hashicorp/google's changelog.

6.7.0 (October 14, 2024)

FEATURES:

• New Resource: google_healthcare_pipeline_job (#19717)
• New Resource: google_secure_source_manager_branch_rule (#19773)

IMPROVEMENTS:

• container: google_container_cluster will now accept server-specified values for node_pool_auto_config.0.node_kubelet_config when it is not defined in configuration and will not detect drift. Note that this means that removing the value from configuration will now preserve old settings instead of reverting the old settings. (#19817)
• discoveryengine: added chat_engine_config.dialogflow_agent_to_link field to google_discovery_engine_chat_engine resource (#19723)
• networkconnectivity: added field migration to resource google_network_connectivity_internal_range (#19757)
• networkservices: added routing_mode field to google_network_services_gateway resource (#19764)

BUG FIXES:

• bigtable: fixed an error where BigTable IAM resources could be created with conditions but the condition was not stored in state (#19725)
• container: fixed issue which caused to not being able to disable enable_cilium_clusterwide_network_policy field on google_container_cluster. (#19736)
• container: fixed a diff triggered by a new API-side default value for node_config.0.kubelet_config.0.insecure_kubelet_readonly_port_enabled. Terraform will now accept server-specified values for node_config.0.kubelet_config when it is not defined in configuration and will not detect drift. Note that this means that removing the value from configuration will now preserve old settings instead of reverting the old settings. (#19817)
• dataproc: fixed a bug in google_dataproc_cluster that prevented creation of clusters with internal_ip_only set to false (#19782)
• iam: addressed google_service_account creation issues caused by the eventual consistency of the GCP IAM API by ignoring 403 errors returned on polling the service account after creation. (#19727)
• logging: fixed the whitespace permadiff on exclusions.filter field in google_logging_billing_account_sink, google_logging_folder_sink, google_logging_organization_sink and google_logging_project_sink resources (#19744)
• pubsub: fixed permadiff with configuring an empty retry_policy. (#19784)
• secretmanager: fixed the issue of unpopulated fields labels, annotations and version_destroy_ttl in the terraform state for the google_secret_manager_secrets datasource (#19748)

6.6.0 (October 7, 2024)

FEATURES:

• New Resource: google_dataproc_batch (#19686)
• New Resource: google_healthcare_pipeline_job (#19717)
• New Resource: google_site_verification_owner (#19641)

IMPROVEMENTS:

• assuredworkloads: added HEALTHCARE_AND_LIFE_SCIENCES_CONTROLS and HEALTHCARE_AND_LIFE_SCIENCES_CONTROLS_WITH_US_SUPPORT enum values to compliance_regime in the google_assuredworkload_workload resource (#19714)
• compute: added bgp_best_path_selection_mode ,bgp_bps_always_compare_med and bgp_bps_inter_region_cost fields to google_compute_network resource (#19708)
• compute: added next_hop_origin ,next_hop_med and next_hop_inter_region_cost output fields to google_compute_route resource (#19708)
• compute: added enum STATEFUL_COOKIE_AFFINITY and strong_session_affinity_cookie field to google_compute_backend_service and google_compute_region_backend_service resource (#19665)
• compute: moved TDX instance option for confidential_instance_type in google_compute_instance from Beta to GA (#19706)
• containeraws: added kubelet_config field group to the google_container_aws_node_pool resource (#19714)
• pubsub: added GCS ingestion settings and platform log settings to google_pubsub_topic resource (#19669)
• sourcerepo: added create_ignore_already_exists field to google_sourcerepo_repository resource (#19716)
• sql: added in-place update support for settings.time_zone in google_sql_database_instance resource (#19654)
• tags: increased maximum accepted input length for the short_name field in google_tags_tag_key and google_tags_tag_value resources (#19712)

BUG FIXES:

• bigquery: fixed google_bigquery_dataset_iam_member to be able to delete itself and overwrite the existing iam members for bigquery dataset keeping the authorized datasets as they are. (#19682)
• bigquery: fixed an error which could occur with service account field values containing non-lower-case characters in google_bigquery_dataset_access (#19705)
• compute: fixed an issue where the boot_disk.initialize_params.resource_policies field in google_compute_instance forced a resource recreation when used in combination with google_compute_disk_resource_policy_attachment (#19692)
• compute: fixed the issue that labels is not set when creating the resource google_compute_interconnect (#19632)
• tags: removed google_tags_location_tag_binding resource from the Terraform state when its parent resource has been removed outside of Terraform (#19693)
• workbench: fixed a bug in the google_workbench_instance resource where the removal of labels was not functioning as expected. (#19620)

Commits

• 5a33a2b Cherrypick GKE fix to 6.7.0 (#19830)
• 3b5eb05 6.7.0 ga change-logs (#19809)
• 00a5231 pubsub: fix permadiff with configuring an empty retry_policy. (#11834) (#19784)
• 45e717a Added information about VCR tests (#11943) (#19783)
• 8098ac9 Force send internal_ip_only (#11923) (#19782)
• a808d53 Add major release number to dev ua (#11938) (#19781)
• 270d18f Update examples about how to make major release test projects in TeamCity (#1...
• fff2b70 adding new google_secure_source_manager_branch_rule resource (#11709) (#19773)
• 2099815 tests: add a acc test for CAS instance creation. (#11931) (#19772)
• 542ac84 Update v6.6.0 CHANGELOG.md (#19771)
• 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)