kyma-project / test-infra

Test infrastructure for the Kyma project.
https://status.build.kyma-project.io/
Apache License 2.0
37 stars 180 forks source link

tf(deps): bump hashicorp/google from 6.11.2 to 6.12.0 in /configs/terraform/core #12358

Closed dependabot[bot] closed 4 days ago

dependabot[bot] commented 4 days ago

Bumps hashicorp/google from 6.11.2 to 6.12.0.

Release notes

Sourced from hashicorp/google's releases.

v6.12.0

FEATURES:

  • New Data Source: google_access_context_manager_access_policy (#20295)
  • New Resource: google_dataproc_gdc_spark_application (#20242)
  • New Resource: google_managed_kafka_cluster and google_managed_kafka_topic (#20237)

IMPROVEMENTS:

  • artifactregistry: added common_repository field to google_artifact_registry_repository resource (#20305)
  • cloudrunv2: added urls output field to google_cloud_run_v2_service resource (#20313)
  • compute: added IDPF as a possible value for the network_interface.nic_type field in google_compute_instance resource (#20250)
  • compute: added IDPF as a possible value for the guest_os_features.type field in google_compute_image resource (#20250)
  • compute: added replica_names field to sql_database_instance resource (#20202)
  • filestore: added performance_config field to google_filestore_instance (#20218)
  • redis: added persistence_config to google_redis_cluster. (#20212)
  • securesourcemanager: added workforce_identity_federation_config field to google_secure_source_manager_instance resource (#20290)
  • spanner: added default_backup_schedule_type field to google_spanner_instance (#20213)
  • sql: added psc_auto_connections fields to google_sql_database_instance resource (#20307)

BUG FIXES:

  • accesscontextmanager: fixed permadiff in perimeter google_access_context_manager_service_perimeter_ingress_policy and google_access_context_manager_service_perimeter_egress_policy resources when there are duplicate resources in the rules (#20294)
    • accesscontextmanager: fixed comparison of identity_type in ingress_from and egress_from when the IDENTITY_TYPE_UNSPECIFIED is set (#20221)
  • compute: fixed permadiff on attempted type field updates in google_computer_security_policy, updating this field will now force recreation of the resource (#20316)
  • identityplatform: fixed perma-diff originating from the sign_in.anonymous.enabled field in google_identity_platform_config (#20244)
Changelog

Sourced from hashicorp/google's changelog.

6.12.0 (Unreleased)

6.11.1 (November 12, 2024)

BUG FIXES:

  • container: fixed diff on google_container_cluster.user_managed_keys_config field for resources that had not set it. (#20314)
  • container: marked google_container_cluster.user_managed_keys_config as immutable because it can't be updated in place. (#20314)

6.11.0 (November 11, 2024)

NOTES:

  • compute: migrated google_compute_firewall_policy_rule from DCL engine to MMv1 engine. (#20160)

BREAKING CHANGES:

  • looker: made oauth_config a required field in google_looker_instance, as creating this resource without that field always triggers an API error (#20196)

FEATURES:

  • New Data Source: google_spanner_database (#20114)
  • New Resource: google_apigee_api (#20113)
  • New Resource: google_dataproc_gdc_application_environment (#20165)
  • New Resource: google_dataproc_gdc_service_instance (#20147)
  • New Resource: google_memorystore_instance (#20108)

IMPROVEMENTS:

  • apigee: added in-place update support for google_apigee_env_references (#20182)
  • apigee: added in-place update support for google_apigee_environment resource (#20189)
  • cloudrun: added empty_dir field to google_cloud_run_service (#20185)
  • cloudrunv2: added empty_dir field to google_cloud_run_v2_service and google_cloud_run_v2_job (#20185)
  • compute: added disks field to google_compute_node_template resource (#20180)
  • compute: added preconfigured_waf_config field to google_compute_security_policy resource (#20183)
  • compute: added replica_names field to sql_database_instance resource (#20202)
  • compute: added instance_flexibility_policy field to google_compute_region_instance_group_manager resource (#20132)
  • compute: increased google_compute_security_policy timeouts from 20 minutes to 30 minutes (#20145)
  • container: added control_plane_endpoints_config field to google_container_cluster resource. (#20193)
  • container: added parallelstore_csi_driver_config field to google_container_cluster resource. (#20163)
  • container: added user_managed_keys_config field to google_container_cluster resource. (#20105)
  • firestore: allowed single field indexes to support __name__ DESC indexes in google_firestore_index resources (#20124)
  • privateca: added support for google_privateca_certificate_authority with type = "SUBORDINATE" to be activated into "STAGED" state (#20103)
  • spanner: added default_backup_schedule_type field to google_spanner_instance (#20213)
  • vertexai: added traffic_split, private_service_connect_config, predict_request_response_logging_config, dedicated_endpoint_enabled, and dedicated_endpoint_dns fields to google_vertex_ai_endpoint resource (#20179)
  • workflows: added deletion_protection field to google_workflows_workflow resource (#20106)

BUG FIXES:

  • compute: fixed a diff based on server-side reordering of match.src_address_groups and match.dest_address_groups in google_compute_network_firewall_policy_rule (#20148)
  • compute: fixed permadiff on the preconfigured_waf_config field for google_compute_security_policy resource (#20183)
  • container: fixed in-place updates for node_config.containerd_config in google_container_cluster and google_container_node_pool (#20112)

5.45.0 (November 11, 2024)

NOTES:

... (truncated)

Commits


Dependabot compatibility score

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 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)
kyma-bot commented 4 days ago

Plan Result

CI link

No changes. Your infrastructure matches the configuration.
kyma-bot commented 4 days ago

:x: Apply Result

CI link

Error: Error acquiring the state lock

Error message: writing
"gs://tf-state-kyma-project/kyma-test-infra-prod/default.tflock" failed:
googleapi: Error 412: At least one of the pre-conditions you specified did
not hold., conditionNotMet
Lock Info:
  ID:        1731955810047386
  Path:      gs://tf-state-kyma-project/kyma-test-infra-prod/default.tflock
  Operation: OperationTypePlan
  Who:       runner@fv-az1146-599
  Version:   1.6.1
  Created:   2024-11-18 18:50:09.751649006 +0000 UTC
  Info:      

OpenTofu acquires a state lock to protect the state from being written
by multiple users at the same time. Please resolve the issue above and try
again. For most commands, you can disable locking with the "-lock=false"
flag, but this is not recommended.
Details (Click me) ```hcl Acquiring state lock. This may take a few moments... Error: Error acquiring the state lock Error message: writing "gs://tf-state-kyma-project/kyma-test-infra-prod/default.tflock" failed: googleapi: Error 412: At least one of the pre-conditions you specified did not hold., conditionNotMet Lock Info: ID: 1731955810047386 Path: gs://tf-state-kyma-project/kyma-test-infra-prod/default.tflock Operation: OperationTypePlan Who: runner@fv-az1146-599 Version: 1.6.1 Created: 2024-11-18 18:50:09.751649006 +0000 UTC Info: OpenTofu acquires a state lock to protect the state from being written by multiple users at the same time. Please resolve the issue above and try again. For most commands, you can disable locking with the "-lock=false" flag, but this is not recommended. ```

`