Bump hashicorp/google from 4.77.0 to 5.1.0 in /terraform

[dependabot]

Bumps hashicorp/google from 4.77.0 to 5.1.0.

Release notes

Sourced from hashicorp/google's releases.

v5.1.0

FEATURES:

• New Resource: google_database_migration_service_private_connection (#16104)
• New Resource: google_edgecontainer_cluster (#16055)
• New Resource: google_edgecontainer_node_pool (#16055)
• New Resource: google_edgecontainer_vpn_connection (#16055)
• New Resource: google_firebase_hosting_custom_domain (#16062)
• New Resource: google_gke_hub_fleet (#16072)

IMPROVEMENTS:

• compute: added device_name field to scratch_disk block of google_compute_instance resource (#16049)
• container: added node_config.linux_node_config.cgroup_mode field to google_container_node_pool (#16103)
• databasemigrationservice: added support for oracle profiles to google_database_migration_service_connection_profile (#16087)
• firestore: added api_scope field to google_firestore_index resource (#16085)
• gkehub: added location field to google_gke_hub_membership_iam_* resources (#16105)
• gkehub: added location field to google_gke_hub_membership resource (#16105)
• gkeonprem: added update-in-place support for vcenter fields in google_gkeonprem_vmware_cluster (#16073)
• identityplatform: added sms_region_config to the resource google_identity_platform_config (#16044)

BUG FIXES:

• dns: fixed record set configuration parsing in google_dns_record_set (#16042)
• provider: fixed an issue where the plugin-framework implementation of the provider handled default region values that were self-links differently to the SDK implementation. This issue is not believed to have affected users because of downstream functions that turn self links into region names. (#16100)
• provider: fixed a bug that caused update requests to be sent for resources with a terraform_labels field even if no fields were updated (#16111)

v5.0.0

KNOWN ISSUES:

• Updating some resources post-upgrade results in an error like "The update_mask in the Update{{Resource}}Request must be set". This should be resolved in 5.1.0, see hashicorp/terraform-provider-google#16091 for details.

Terraform Google Provider 5.0.0 Upgrade Guide

NOTES:

• provider: some provider default values are now shown at plan-time (#15707)

LABELS REWORK:

• provider: default labels configured on the provider through the new default_labels field are now supported. The default labels configured on the provider will be applied to all of the resources with standard labels field.
• provider: resources with labels - three label-related fields are now in all of the resources with standard labels field. 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.
• provider: resources with annotations - two annotation-related fields are now in all of the resources with standard annotations field. The annotations field is non-authoritative and only manages the annotations defined by the users on the resource through Terraform. The new output-only effective_annotations field lists all of annotations present on the resource in GCP, including the annotations configured through Terraform, the system, and other clients.
• provider: datasources with labels - three fields labels, terraform_labels, and effective_labels are now present in most resource-based datasources. All three fields 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.
• provider: datasources with annotations - both annotations and effective_annotations are now present in most resource-based datasources. Both fields have all of annotations present on the resource in GCP including the annotations configured through Terraform, the system, and other clients, equivalent to effective_annotations on the resource.

BREAKING CHANGES:

• provider: added provider-level validation so these fields are not set as empty strings in a user's config: credentials, access_token, impersonate_service_account, project, billing_project, region, zone (#15968)
• provider: fixed many import functions throughout the provider that matched a subset of the provided input when possible. Now, the GCP resource id supplied to "terraform import" must match exactly. (#15977)
• provider: made data sources return errors on 404s when applicable instead of silently failing (#15799)
• provider: made empty strings in the provider configuration block no longer be ignored when configuring the provider(#15968)
• accesscontextmanager: changed multiple array fields to sets where appropriate to prevent duplicates and fix diffs caused by server side reordering. (#15756)
• bigquery: added more input validations for google_bigquery_table schema (#15338)
• bigquery: made routine_type required for google_bigquery_routine (#15517)
• cloudfunction2: made location required on google_cloudfunctions2_function (#15830)

... (truncated)

Changelog

Sourced from hashicorp/google's changelog.

5.1.0 (Unreleased)

5.0.0 (Oct 2, 2023)

KNOWN ISSUES:

• Updating some resources post-upgrade results in an error like "The update_mask in the Update{{Resource}}Request must be set". This should be resolved in 5.1.0, see hashicorp/terraform-provider-google#16091 for details.

Terraform Google Provider 5.0.0 Upgrade Guide

NOTES:

• provider: some provider default values are now shown at plan-time (#15707)

LABELS REWORK:

• provider: default labels configured on the provider through the new default_labels field are now supported. The default labels configured on the provider will be applied to all of the resources with standard labels field.
• provider: resources with labels - three label-related fields are now in all of the resources with standard labels field. 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.
• provider: resources with annotations - two annotation-related fields are now in all of the resources with standard annotations field. The annotations field is non-authoritative and only manages the annotations defined by the users on the resource through Terraform. The new output-only effective_annotations field lists all of annotations present on the resource in GCP, including the annotations configured through Terraform, the system, and other clients.
• provider: datasources with labels - three fields labels, terraform_labels, and effective_labels are now present in most resource-based datasources. All three fields 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.
• provider: datasources with annotations - both annotations and effective_annotations are now present in most resource-based datasources. Both fields have all of annotations present on the resource in GCP including the annotations configured through Terraform, the system, and other clients, equivalent to effective_annotations on the resource.

BREAKING CHANGES:

• provider: added provider-level validation so these fields are not set as empty strings in a user's config: credentials, access_token, impersonate_service_account, project, billing_project, region, zone (#15968)
• provider: fixed many import functions throughout the provider that matched a subset of the provided input when possible. Now, the GCP resource id supplied to "terraform import" must match exactly. (#15977)
• provider: made data sources return errors on 404s when applicable instead of silently failing (#15799)
• provider: made empty strings in the provider configuration block no longer be ignored when configuring the provider(#15968)
• accesscontextmanager: changed multiple array fields to sets where appropriate to prevent duplicates and fix diffs caused by server side reordering. (#15756)
• bigquery: added more input validations for google_bigquery_table schema (#15338)
• bigquery: made routine_type required for google_bigquery_routine (#15517)
• cloudfunction2: made location required on google_cloudfunctions2_function (#15830)
• cloudiot: removed deprecated datasource google_cloudiot_registry_iam_policy (#15739)
• cloudiot: removed deprecated resource google_cloudiot_device (#15739)
• cloudiot: removed deprecated resource google_cloudiot_registry (#15739)
• cloudiot: removed deprecated resource google_cloudiot_registry_iam_* (#15739)
• cloudrunv2: removed deprecated field liveness_probe.tcp_socket from google_cloud_run_v2_service resource. (#15430)
• cloudrunv2: removed deprecated fields startup_probe and liveness_probe from google_cloud_run_v2_job resource. (#15430)
• cloudrunv2: retyped volumes.cloud_sql_instance.instances to SET from ARRAY for google_cloud_run_v2_service (#15831)
• compute: made google_compute_node_group require one of initial_size or autoscaling_policy fields configured upon resource creation (#16006)
• compute: made size in google_compute_node_group an output only field. (#16006)
• compute: removed default value for rule.rate_limit_options.encorce_on_key on resource google_compute_security_policy (#15681)
• compute: retyped consumer_accept_lists to a SET from an ARRAY type for google_compute_service_attachment (#15985)
• container: added deletion_protection to google_container_cluster which is enabled to true by default. When enabled, this field prevents Terraform from deleting the resource. (#16013)
• container: changed management.auto_repair and management.auto_upgrade defaults to true in google_container_node_pool (#15931)
• container: changed networking_mode default to VPC_NATIVE for newly created google_container_cluster resources (#6402)
• container: removed enable_binary_authorization in google_container_cluster (#15868)
• container: removed default for logging_variant in google_container_node_pool (#15931)
• container: removed default value in network_policy.provider in google_container_cluster (#15920)
• container: removed the behaviour that google_container_cluster will delete the cluster if it's created in an error state. Instead, it will mark the cluster as tainted, allowing manual inspection and intervention. To proceed with deletion, run another terraform apply. (#15887)
• container: reworked the taint field in google_container_cluster and google_container_node_pool to only manage a subset of taint keys based on those already in state. Most existing resources are unaffected, unless they use sandbox_config- see upgrade guide for details. (#15959)
• dataplex: removed data_profile_result and data_quality_result from google_dataplex_scan (#15505)
• firebase: changed deletion_policy default to DELETE for google_firebase_web_app. (#15406)

... (truncated)

Commits

• 9650cb7 Release 5.1.0 CHANGELOG (#16143)
• 618cefc Apply new labels model for edgecontainer resources (#9193) (#16171)
• bb23e06 Revert "SSL Mode and Require Connectors support for AlloyDB (#9064)" (#9192) ...
• b7cea94 Don't send update request if updatemask is empty for resources with terraform...
• 5a3ca8c Add info about plannable import to handwritten documentation **for IAM resour...
• 20392cb Update Import section of on remainging non-IAM resources (#9101) (#16109)
• 37002a8 Add info about plannable import to handwritten documentation (non-IAM resourc...
• f15f455 Add info about plannable import to handwritten documentation (non-IAM resourc...
• dcb17b4 Update generated resource documentation to include config-driven import along...
• 2c40af1 Enabling Membership resource to be regionalized with global as default value ...
• 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)

---

This change is 

[dependabot]

Superseded by #118.