Skip to content

v4.47.0
Compare
Choose a tag to compare
@github-actions github-actions released this 21 Dec 21:20
· 2256 commits to main since this release
v4.47.0
87f866a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

NOTES:

  • sql: fixed an issue where google_sql_database was abandoned by default as of version 4.45.0. Users who have upgraded to 4.45.0 or 4.46.0 will see a diff when running their next terraform apply after upgrading this version, indicating the deletion_policy field's value has changed from "ABANDON" to "DELETE". This will create a no-op call against the API, but can otherwise be safely applied. (#13226)

FEATURES:

  • New Resource: google_alloydb_backup (#13202)
  • New Resource: google_filestore_backup (#13209)

IMPROVEMENTS:

  • bigtable: added deletion_protection field to google_bigtable_table (#13232)
  • compute: made google_compute_subnetwork.ipv6_access_type field updatable in-place (#13211)
  • container: added auto_provisioning_defaults.cluster_autoscaling.upgrade_settings in google_container_cluster (#13199)
  • container: added gateway_api_config block to google_container_cluster resource for supporting the gke gateway api controller (#13233)
  • container: promoted gke_backup_agent_config in google_container_cluster to GA (#13223)
  • container: promoted min_cpu_platform in google_container_cluster to GA (#13199)
  • datacatalog: added update support for fields in google_data_catalog_tag_template (#13216)
  • iam: Added plan-time validation for IAM members (#13203)
  • logging: added bucket_name field to google_logging_metric (#13210)
  • logging: made metric_descriptor field optional for google_logging_metric (#13225)

BUG FIXES:

  • composer: fixed a crash when updating ip_allocation_policy of google_composer_environment (#13188)
  • sql: fixed an issue where google_sql_database was abandoned by default as of version 4.45.0. Users who have upgraded to 4.45.0 or 4.46.0 will see a diff when running their next terraform apply after upgrading this version, indicating the deletion_policy field's value has changed from "ABANDON" to "DELETE". This will create a no-op call against the API, but can otherwise be safely applied. (#13226)
Assets 4