-
Notifications
You must be signed in to change notification settings - Fork 452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update terraform google provider to v6 #2583
Open
renovate-bot
wants to merge
1
commit into
GoogleCloudPlatform:master
Choose a base branch
from
renovate-bot:renovate/test-cleanup-terraform-google-provider
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
chore(deps): update terraform google provider to v6 #2583
renovate-bot
wants to merge
1
commit into
GoogleCloudPlatform:master
from
renovate-bot:renovate/test-cleanup-terraform-google-provider
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 5, 2024 23:34
5e5b666
to
5cf3f2e
Compare
forking-renovate
bot
added
the
dependencies
Pull requests that update a dependency file
label
Sep 5, 2024
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 9, 2024 16:29
5cf3f2e
to
c550cf7
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 10, 2024 21:36
c550cf7
to
9471ad9
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 12, 2024 19:07
9471ad9
to
2dec452
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 12, 2024 19:19
2dec452
to
d25d372
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 12, 2024 23:52
d25d372
to
99d715d
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 13, 2024 15:41
99d715d
to
fae0928
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 13, 2024 16:10
fae0928
to
b45934c
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 13, 2024 16:16
b45934c
to
2bce8d2
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 13, 2024 17:28
2bce8d2
to
6ceb297
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 13, 2024 17:52
6ceb297
to
c1b4da8
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 13, 2024 17:59
c1b4da8
to
2293348
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 13, 2024 18:02
2293348
to
9a50912
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 13, 2024 18:22
9a50912
to
ce3b389
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 14, 2024 03:22
ce3b389
to
3a6d0f6
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 14, 2024 03:55
3a6d0f6
to
7d6e5d0
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 16, 2024 16:22
7d6e5d0
to
ec500ba
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 16, 2024 23:24
ec500ba
to
e4c0012
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 16, 2024 23:48
e4c0012
to
a0641ab
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 18, 2024 00:43
a0641ab
to
54cc9a7
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 19, 2024 16:07
54cc9a7
to
cf1b7ca
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 19, 2024 16:17
cf1b7ca
to
4b0fb82
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 19, 2024 17:09
4b0fb82
to
0f18d0d
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 20, 2024 17:09
0f18d0d
to
759d105
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 20, 2024 17:39
759d105
to
7d901e6
Compare
/gcbrun |
renovate-bot
force-pushed
the
renovate/test-cleanup-terraform-google-provider
branch
from
September 20, 2024 18:12
7d901e6
to
3913685
Compare
/gcbrun |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
>= 3.38, < 6
->>= 3.38, < 7
6.3.0
>= 3.38, < 6
->>= 3.38, < 7
6.3.0
Release Notes
hashicorp/terraform-provider-google (google)
v6.2.0
Compare Source
FEATURES:
google_certificate_manager_certificates
(#19361)google_network_security_server_tls_policy
(#19314)google_scc_v2_folder_scc_big_query_export
(#19327)google_scc_v2_project_scc_big_query_export
(#19311)IMPROVEMENTS:
partner_service_billing_account
togoogle_assured_workloads_workload
(#19358)column_family.type
ingoogle_bigtable_table
(#19302)google_cloud_run_service
to GA (#19359)google_cloud_run_v2_job
to GA (#19359)boot_disk.interface
field togoogle_compute_instance
resource (#19319)node_pool_auto_config.node_kublet_config.insecure_kubelet_readonly_port_enabled
field togoogle_container_cluster
. (#19320)insecure_kubelet_readonly_port_enabled
tonode_pool.node_config.kubelet_config
andnode_config.kubelet_config
ingoogle_container_node_pool
resource. (#19312)insecure_kubelet_readonly_port_enabled
tonode_pool_defaults.node_config_defaults
,node_pool.node_config.kubelet_config
, andnode_config.kubelet_config
ingoogle_container_cluster
resource. (#19312)google_compute_node_pool.node_config.gcfs_config
andgoogle_container_cluster.node_config.gcfs_cluster
andgoogle_container_cluster.node_pool.node_config.gcfs_cluster
(#19365)additive_vpc_scope_dns_domain
field on thegoogle_container_cluster
resource to GA (#19313)x509
field togoogle_iam_workload_identity_pool_provider
resource (#19375)include_export_ranges
togoogle_network_connectivity_spoke
(#19346)cloud_storage_config.max_messages
andcloud_storage_config.avro_config.use_topic_schema
fields togoogle_pubsub_subscription
resource (#19338)maintenance_policy
field to thegoogle_redis_cluster
resource (#19341)tags
field togoogle_project
to allow setting tags for projects at creation time (#19351)streaming_config.filter
values ingoogle_scc_notification_config
resources (#19369)BUG FIXES:
google_compute_interconnect
to support correctavailable_features
option ofIF_MACSEC
(#19330)advertised_route_priority
was accidentally set to 0 during updates ingoogle_compute_router_peer
(#19366)start_time
in an incorrect H:mm format ingoogle_compute_resource_policies
resources (#19297)network_interface.subnetwork_project
validation to match with the project innetwork_interface.subnetwork
field whennetwork_interface.subnetwork
has full self_link ingoogle_compute_instance
resource (#19348)gcfs_config
(#19365google_kms_autokey_config
resource'sfolder
field to accept values that are either full resource names (folders/{folder_id}
) or just the folder id ({folder_id}
only) (#19364))google_storage_bucket
resource (#19353)v6.1.0
Compare Source
v6.0.1
Compare Source
BREAKING CHANGES:
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. (#19263)v6.0.0
Compare Source
Terraform Google Provider 6.0.0 Upgrade Guide
BREAKING CHANGES:
goog-terraform-provisioned: true
label by default. (#19190)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. (#18906)network
ingoogle_alloy_db_cluster
. Usenetwork_config.network
instead. (#19181)google_bigquery_table
resource (#18767)allow_resource_tags_on_deletion
fromgoogle_bigquery_table
. Resource tags are now always allowed on table deletion. (#19077)multi_region_auxiliary
fromgoogle_bigquery_reservation
(#18922)id
forgoogle_billing_project_info
(#18823)deletion_protection
field togoogle_cloudrunv2_service
. This field defaults totrue
, preventing accidental deletions. To delete the resource, you must first setdeletion_protection = false
before destroying the resource.(#19019)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. (#18764)containers.env
to SET from ARRAY forgoogle_cloud_run_v2_service
andgoogle_cloud_run_v2_job
. (#18855)ip_allocation_policy = []
ingoogle_composer_environment
is no longer valid configuration. Removing the field from configuration should not produce a diff. (#19207)enabled
ingoogle_compute_backend_service
andgoogle_compute_region_backend_service
(#18772)certifcate_id
ingoogle_compute_managed_ssl_certificate
to correctly be output only. (#19069)connection_draining_timeout_sec
,balancing_mode
andoutlier_detection
ingoogle_compute_region_backend_service
andgoogle_compute_backend_service
. (#18720)id
forcompute_network_endpoints
(#18844)guest_accelerator = []
is no longer valid configuration ingoogle_compute_instance
. To explicitly set an empty list of objects, set guest_accelerator.count = 0. (#19207)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. (#19207)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. (#19207)advanced_datapath_observability_config.enable_relay
required ingoogle_container_cluster
(#19060)advanced_datapath_observability_config.relay_mode
fromgoogle_container_cluster
resource. Users are expected to useenable_relay
field instead. (#19060)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. (#19062)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. (#19062)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. (#19207)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. (#19207)google_datastore_index
in favor ofgoogle_firestore_index
(#19160)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. (#19062)google_identity_platform_project_default_config
in favor ofgoogle_identity_platform_project_config
(#18992)schema_settings
ingoogle_pubsub_topic
to be removed (#18631)create_sample_workflows
andprovision_gmek
fromgoogle_integrations_client
(#19148)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. (#19173)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. (#19021)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. (#19114)settings.ip_configuration.require_ssl
ingoogle_sql_database_instance
. Please usesettings.ip_configuration.ssl_mode
instead. (#18843)no_age
field fromlifecycle_rule.condition
in thegoogle_storage_bucket
resource (#19048)min_throughput
andmin_instances
fields ongoogle_vpc_access_connector
and made them default to values returned from the API when not provided by users (#18697)min_throughput
andmin_instances
fields ongoogle_vpc_access_connector
(#18697)max_throughput
andmax_instances
fields ongoogle_vpc_access_connector
(#18697)host.gce_instance.disable_ssh
to true forgoogle_workstations_workstation_config
(#19101)IMPROVEMENTS:
reserved_internal_range
andsecondary_ip_ranges[].reserved_internal_range
togoogle_compute_subnetwork
resource (#19151)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:
enabled
field by default for nulliap
message ingoogle_compute_backend_service
andgoogle_compute_region_backend_service
(#18772)v5.44.0
Compare Source
NOTES:
IMPROVEMENTS:
insecure_kubelet_readonly_port_enabled
tonode_pool.node_config.kubelet_config
andnode_config.kubelet_config
ingoogle_container_node_pool
resource. (#19312)insecure_kubelet_readonly_port_enabled
tonode_pool_defaults.node_config_defaults
,node_pool.node_config.kubelet_config
, andnode_config.kubelet_config
ingoogle_container_cluster
resource. (#19312)node_pool_auto_config.node_kublet_config.insecure_kubelet_readonly_port_enabled
field togoogle_container_cluster
. (#19320)v5.43.1
Compare Source
NOTES:
BUG FIXES:
google_pubsub_subscription
resources (#19284)v5.43.0
Compare Source
DEPRECATIONS:
lifecycle_rule.condition.no_age
field ingoogle_storage_bucket
. Use the newlifecycle_rule.condition.send_age_if_zero
field instead. (#19172)FEATURES:
google_kms_ekm_connection_iam_binding
(#19132)google_kms_ekm_connection_iam_member
(#19132)google_kms_ekm_connection_iam_policy
(#19132)google_scc_v2_organization_scc_big_query_exports
(#19184)IMPROVEMENTS:
label_fingerprint
field togoogle_compute_global_address
resource (#19204)forwarding_rule_id
on resourcegoogle_compute_forwarding_rule
(#19139)release_channel
field ingoogle_container_cluster
resource (#19141)enable_analytics
parsing to "no preference" in analytics if omitted, instead of explicitly disabling analytics ingoogle_logging_project_bucket_config
(#19126)filter
field in resourcegoogle_pubsub_subscription
(#19131)default_labels
field togoogle_client_config
data source (#19170)google_vmwareengine_private_cloud
(#19192)BUG FIXES:
psc_instance_config
ingoogle_alloydb_instance
resource (#19143)server_tls_policy
property ongoogle_compute_target_https_proxy
resources (#19164)labels
field could not be updated ongoogle_compute_global_address
(#19204)network_ip
on resourcegoogle_compute_instance
(#19135)v5.42.0
Compare Source
DEPRECATIONS:
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. Usesend_secondary_ip_range_if_empty
while removingsecondary_ip_range
from config instead. (#19122)FEATURES:
google_artifact_registry_locations
(#19047)google_cloud_identity_transitive_group_memberships
(#19038)google_discovery_engine_schema
(#19124)google_scc_folder_notification_config
(#19057)google_scc_v2_folder_notification_config
(#19055)google_vertex_ai_index_endpoint_deployed_index
(#19061)IMPROVEMENTS:
serial_pipeline.stages.strategy.canary.runtime_config.kubernetes.gateway_service_mesh.pod_selector_label
andserial_pipeline.stages.strategy.canary.runtime_config.kubernetes.service_networking.pod_selector_label
fields togoogle_clouddeploy_delivery_pipeline
resource (#19100)send_secondary_ip_range_if_empty
togoogle_compute_subnetwork
(#19122)skip_default_schema_creation
field togoogle_data_store
resource (#19017)load_balancer_type
field from required to optional ingoogle_dns_record_set
(#19050)cmek_config
field togoogle_firestore_database
resource (#19107)update_on_creation_fail
field togoogle_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)server_ca_mode
field togoogle_sql_database_instance
resource (#18998)BUG FIXES:
google_bigquery_dataset_iam_member
non-authoritative. To remove a bigquery dataset iam member, use an authoritative resource likegoogle_bigquery_dataset_iam_policy
(#19121)service_config.environment_variables
field ingoogle_cloudfunctions2_function
resource (#19024)storage_source.generation
ingoogle_cloudfunctions2_function
resource (#19031)google_compute_forwarding_rule
prevented resource deletion (#19117)google_logging_project_bucket_config.enable_analytics
behavior to set "no preference" in analytics if omitted, instead of explicitly disabling analytics. (#19126)google_workbench_instance
metadata drifting when using custom containers. (#19119)v5.41.0
Compare Source
DEPRECATIONS:
skip_delete
field in thegoogle_project
resource. Usedeletion_policy
instead. (#18867)FEATURES:
google_logging_log_view_iam_policy
(#18990)google_scc_v2_organization_source_iam_policy
(#19004)google_access_context_manager_service_perimeter_dry_run_egress_policy
(#18994)google_access_context_manager_service_perimeter_dry_run_ingress_policy
(#18994)google_scc_v2_folder_mute_config
(#18924)google_scc_v2_project_mute_config
(#18993)google_scc_v2_project_notification_config
(#19008)google_scc_v2_organization_source
(#19004)google_scc_v2_organization_source_iam_binding
(#19004)google_scc_v2_organization_source_iam_member
(#19004)google_scc_v2_organization_source_iam_policy
(#19004)google_logging_log_view_iam_binding
(#18990)google_logging_log_view_iam_member
(#18990)google_logging_log_view_iam_policy
(#18990)IMPROVEMENTS:
gke.proxy_url
field togoogle_clouddeploy_target
(#19016)binary_authorization.policy
to resourcegoogle_cloud_run_v2_job
and resourcegoogle_cloud_run_v2_service
to support named binary authorization policy. (#18995)source_regions
field togoogle_compute_healthcheck
resource (#19006)google_compute_target_https_proxy.server_tls_policy
field (#18996)google_compute_region_target_https_proxy.server_tls_policy
field (#19007)auto_provisioning_locations
field togoogle_container_cluster
(#18928)kms_key_name
field togoogle_dataform_repository
resource (#18947)skip_default_schema_creation
field togoogle_discovery_engine_data_store
resource (#19017)configmanagement.management
andconfigmanagement.config_sync.enabled
fields togoogle_gkehub_feature_membership
(#19016)management
field togoogle_gke_hub_feature.fleet_default_member_config.configmanagement
(#18963)deletion_policy
field to thegoogle_project
resource. Settingdeletion_policy
toPREVENT
will protect the project against any destroy actions caused by a terraform apply or terraform destroy. Settingdeletion_policy
toABANDON
allows the resource to be abandoned rather than deleted and it behaves the same withskip_delete = true
. Default value isDELETE
.skip_delete = true
takes precedence overdeletion_policy = "DELETE"
.force_destroy
field togoogle_storage_managed_folder
resource (#18973)generation
field togoogle_storage_bucket_object
resource (#18971)BUG FIXES:
google_compute_instance.alias_ip_range
update behavior to avoid temporarily deleting unchanged alias IP ranges (#19015)google_compute_forwarding_rule
resource when provider default labels are set (#18984)settings.insights_config
ingoogle_sql_database_instance
(#18962)v5.40.0
Compare Source
IMPROVEMENTS:
DELTA_LAKE
tosource_format
ingoogle_bigquery_table
resource (#18915)access_mode
field togoogle_compute_disk
resource (#18857)stack_type
, andgateway_ip_version
fields togoogle_compute_router
resource (#18839)ray_operator_config
forresource_container_cluster
(#18825)additional_node_network_configs
andadditional_pod_network_configs
fields to GA in thegoogle_container_node_pool
resource (#18842)enable_multi_networking
to GA in thegoogle_container_cluster
resource (#18842)goal
field to accept a max threshold of up to 0.9999 ingoogle_monitoring_slo
resource to 0.9999 (#18845)export_psc
field togoogle_network_connectivity_hub
resource (#18866)enable_dataplex_integration
field togoogle_sql_database_instance
resource (#18852)BUG FIXES:
params
in thegoogle_bigquery_data_transfer_config
resource (#18898)params
from being assigned values ingoogle_bigquery_data_transfer_config
(#18888)advertised_ip_ranges
field ingoogle_compute_router
resource (#18869)node_config.guest_accelerator.gpu_driver_installation_config
field in GKE 1.30+ ingoogle_container_node_pool
resource (#18835)settings.insights_config
ingoogle_sql_database_instance
(#18962)hashicorp/terraform-provider-google-beta (google-beta)
v6.2.0
Compare Source
FEATURES:
google_certificate_manager_certificates
(#8099)google_backup_dr_backup_vault
(#8083)google_scc_v2_folder_scc_big_query_export
(#8079)google_scc_v2_project_scc_big_query_export
(#8070)IMPROVEMENTS:
partner_service_billing_account
togoogle_assured_workloads_workload
(#8097)column_family.type
ingoogle_bigtable_table
(#8069)template.service_mesh
togoogle_cloud_run_v2_service
(#8096)boot_disk.interface
field togoogle_compute_instance
resource (#8075)node_pool_auto_config.node_kublet_config.insecure_kubelet_readonly_port_enabled
field togoogle_container_cluster
. (#8076)insecure_kubelet_readonly_port_enabled
tonode_pool.node_config.kubelet_config
andnode_config.kubelet_config
ingoogle_container_node_pool
resource. (#8071)insecure_kubelet_readonly_port_enabled
tonode_pool_defaults.node_config_defaults
,node_pool.node_config.kubelet_config
, andnode_config.kubelet_config
ingoogle_container_cluster
resource. (#8071)google_compute_node_pool.node_config.gcfs_config
andgoogle_container_cluster.node_config.gcfs_cluster
andgoogle_container_cluster.node_pool.node_config.gcfs_cluster
(#8101)x509
field togoogle_iam_workload_identity_pool_provider
resource (#8110)include_export_ranges
togoogle_network_connectivity_spoke
(#8088)cloud_storage_config.max_messages
andcloud_storage_config.avro_config.use_topic_schema
fields togoogle_pubsub_subscription
resource (#8086)maintenance_policy
field to thegoogle_redis_cluster
resource (#8087)tags
field togoogle_project
to allow setting tags for projects at creation time (#8091)streaming_config.filter
values ingoogle_scc_notification_config
resources (#8105)BUG FIXES:
google_compute_interconnect
to support correctavailable_features
option ofIF_MACSEC
(#8082)advertised_route_priority
was accidentally set to 0 during updates ingoogle_compute_router_peer
(#8102)start_time
in an incorrectH:mm
format ingoogle_compute_resource_policies
resources (#8067)network_interface.subnetwork_project
validation to match with the project innetwork_interface.subnetwork
field whennetwork_interface.subnetwork
has full self_link ingoogle_compute_instance
resource (#8089)google_kms_autokey_config
resource'sfolder
field to accept values that are either full resource names (folders/{folder_id}
) or just the folder id ({folder_id}
only) (#8100)google_storage_bucket
resource (#8092)v6.1.0
Compare Source
FEATURES:
google_kms_crypto_key_latest_version
(#8032)google_kms_crypto_key_versions
(#8026)IMPROVEMENTS:
google_database_migration_service_connection_profile
for creating DMS connection profiles that link to existing Cloud SQL instances/AlloyDB clusters. (#8062)subscription_type
andtrial_metadata
field togoogle_alloydb_cluster
resource (#8042)encryption_configuration
field togoogle_bigquery_data_transfer_config
resource (#8045)selected_resources
, andrestrict_direct_table_access
togoogle_bigquery_analytics_hub_listing
resource (#8029)sharing_environment_config
togoogle_bigquery_analytics_hub_data_exchange
resource (#8029)http_target
field togoogle_cloud_tasks_queue
resource (#8033)accelerators
field togoogle_compute_node_template
resource (#8063)server_tls_policy
during update ingoogle_compute_target_https_proxy
resources (#8023)transaction_logs
andchange_tables
todatastream_stream
resource (#8031)chunking_config
andlayout_parsing_config
fields togoogle_discovery_engine_data_store
resource (#8049)inspect_template_modified_cadence
field tobig_query_target
andcloud_sql_target
ingoogle_data_loss_prevention_discovery_config
resource (#8054)tag_resources
field togoogle_data_loss_prevention_discovery_config
resource (#8054)BUG FIXES:
google_bigquery_dataset_access
resource (#8039)bigquery_dataset
immutable ingoogle_bigquery_analytics_hub_listing
as it was not updatable in the API. Now modifying the field in Terraform will correctly recreate the resource rather than causing Terraform to report it would attempt an invalid update. (#8029)google_container_cluster
resource (#8030)google_pubsub_subscription
resources (#8055)google_sql_user
wherehost
is an IPv4 CIDR (#8028)name
field for IAM Group user forgoogle_sql_user
resource (#8024)v6.0.1
Compare Source
BREAKING CHANGES:
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
Compare Source
Terraform Google Provider 6.0.0 Upgrade Guide
BREAKING CHANGES:
goog-terraform-provisioned: true
label by default. (#8004)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)network
ingoogle_alloy_db_cluster
. Usenetwork_config.network
instead. (#7999)id
forgoogle_billing_project_info
(#7793)google_bigquery_table
resource (#7755)allow_resource_tags_on_deletion
fromgoogle_bigquery_table
. Resource tags are now always allowed on table deletion. (#7940)multi_region_auxiliary
fromgoogle_bigquery_reservation
(#7844)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)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)containers.env
to SET from ARRAY forgoogle_cloud_run_v2_service
andgoogle_cloud_run_v2_job
. (#7812)ip_allocation_policy = []
ingoogle_composer_environment
is no longer valid configuration. Removing the field from configuration should not produce a diff. (#8011)enabled
ingoogle_compute_backend_service
andgoogle_compute_region_backend_service
(#7758)connection_draining_timeout_sec
,balancing_mode
andoutlier_detection
ingoogle_compute_region_backend_service
andgoogle_compute_backend_service
. (#7723)compute_network_endpoints
(#7806)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)guest_accelerator = []
is no longer valid configuration ingoogle_compute_instance
. To explicitly set an empty list of objects, set guest_accelerator.count = 0. (#8011)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)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)advanced_datapath_observability_config.enable_relay
required ingoogle_container_cluster
(#7930)advanced_datapath_observability_config.relay_mode
fromgoogle_container_cluster
resource. Users are expected to useenable_relay
field instead. (#7930)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)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)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)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)google_datastore_index
in favor ofgoogle_firestore_index
(#7987)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)google_identity_platform_project_default_config
in favor ofgoogle_identity_platform_project_config
(#7880)create_sample_workflows
andprovision_gmek
fromgoogle_integrations_client
(#7977)schema_settings
ingoogle_pubsub_topic
to be removed (#7674)deletion_protection_enabled
field to thegoogle_redis_cluster
resource. This field defaults totrue
, preventingConfiguration
📅 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.
This PR was generated by Mend Renovate. View the repository job log.