chore(deps): update terraform google-beta to v6
This MR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
google-beta (source) | required_provider | major |
~> 5.0 -> ~> 6.0
|
Release Notes
hashicorp/terraform-provider-google-beta (google-beta)
v6.0.1
BREAKING CHANGES:
- sql: removed
settings.ip_configuration.require_ssl
fromgoogle_sql_database_instance
in favor ofsettings.ip_configuration.ssl_mode
. This field was intended to be removed in 6.0.0. (#8043)
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. (#8004) - activedirectory: added
deletion_protection
field togoogle_active_directory_domain
resource. This field defaults totrue
, preventing accidental deletions. To delete the resource, you must first setdeletion_protection = false
before destroying the resource. (#7837) - alloydb: removed
network
ingoogle_alloy_db_cluster
. Usenetwork_config.network
instead. (#7999) - billing: revised the format of
id
forgoogle_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
fromgoogle_bigquery_table
. Resource tags are now always allowed on table deletion. (#7940) - bigqueryreservation: removed
multi_region_auxiliary
fromgoogle_bigquery_reservation
(#7844) - cloudrunv2: added
deletion_protection
field togoogle_cloudrunv2_service
to make deleting them require an explicit intent. This field defaults totrue
, preventing accidental deletions. To delete the resource, you must first setdeletion_protection = false
before destroying the resource. (#7901) - cloudrunv2: changed
liveness_probe
to no longer infer a default value from api ongoogle_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 forgoogle_cloud_run_v2_service
andgoogle_cloud_run_v2_job
. (#7812) - composer:
ip_allocation_policy = []
ingoogle_composer_environment
is no longer valid configuration. Removing the field from configuration should not produce a diff. (#8011) - compute: added new required field
enabled
ingoogle_compute_backend_service
andgoogle_compute_region_backend_service
(#7758) - compute: revised and in some cases removed default values of
connection_draining_timeout_sec
,balancing_mode
andoutlier_detection
ingoogle_compute_region_backend_service
andgoogle_compute_backend_service
. (#7723) - compute: updated resource id for
compute_network_endpoints
(#7806) - compute: stopped the
certifcate_id
field ingoogle_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 ingoogle_compute_instance
. To explicitly set an empty list of objects, set guest_accelerator.count = 0. (#8011) - compute:
google_compute_instance_from_template
andgoogle_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 = []
ingoogle_compute_subnetwork
is no longer valid configuration. To set an explicitly empty list, usesend_secondary_ip_range_if_empty
and completely removesecondary_ip_range
from config. (#8011) - container: made
advanced_datapath_observability_config.enable_relay
required ingoogle_container_cluster
(#7930) - container: removed deprecated field
advanced_datapath_observability_config.relay_mode
fromgoogle_container_cluster
resource. Users are expected to useenable_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-onlyterraform_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-onlyeffective_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
, andeffective_labels
be present ingoogle_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 toeffective_labels
on the resource. (#7932) - container:
guest_accelerator = []
is no longer valid configuration ingoogle_container_cluster
andgoogle_container_node_pool
. To explicitly set an empty list of objects, set guest_accelerator.count = 0. (#8011) - container:
guest_accelerator.gpu_driver_installation_config = []
andguest_accelerator.gpu_sharing_config = []
are no longer valid configuration ingoogle_container_cluster
andgoogle_container_node_pool
. Removing the fields from configuration should not produce a diff. (#8011) - datastore: removed
google_datastore_index
in favor ofgoogle_firestore_index
(#7987) - edgenetwork: three label-related fields are now in
google_edgenetwork_network
andgoogle_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-onlyterraform_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-onlyeffective_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 ofgoogle_identity_platform_project_config
(#7880) - integrations: removed
create_sample_workflows
andprovision_gmek
fromgoogle_integrations_client
(#7977) - pubsub: allowed
schema_settings
ingoogle_pubsub_topic
to be removed (#7674) - redis: added a
deletion_protection_enabled
field to thegoogle_redis_cluster
resource. This field defaults totrue
, preventing accidental deletions. To delete the resource, you must first setdeletion_protection_enabled = false
before destroying the resource. (#7995) - resourcemanager: added
deletion_protection
field togoogle_folder
to make deleting them require an explicit intent. Folder resources now cannot be destroyed unlessdeletion_protection = false
is set for the resource. (#7903) - resourcemanager: made
deletion_policy
ingoogle_project
'PREVENT' by default. This makes deleting them require an explicit intent.google_project
resources cannot be destroyed unlessdeletion_policy
is set to 'ABANDON' or 'DELETE' for the resource. (#7946) - storage: removed
no_age
field fromlifecycle_rule.condition
in thegoogle_storage_bucket
resource (#7923) - sql: removed
settings.ip_configuration.require_ssl
ingoogle_sql_database_instance
. Please usesettings.ip_configuration.ssl_mode
instead. (#7804) - vpcaccess: removed default values for
min_throughput
andmin_instances
fields ongoogle_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
andmin_instances
fields ongoogle_vpc_access_connector
(#7709) - vpcaccess: added a conflicting fields restriction between
max_throughput
andmax_instances
fields ongoogle_vpc_access_connector
(#7709) - workstation: defaulted
host.gce_instance.disable_ssh
to true forgoogle_workstations_workstation_config
(#7946)
IMPROVEMENTS:
- compute: added fields
reserved_internal_range
andsecondary_ip_ranges[].reserved_internal_range
togoogle_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 nulliap
message ingoogle_compute_backend_service
andgoogle_compute_region_backend_service
(#7758)
v5.43.0
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.
Edited by uis-devops-renovatebot