Skip to content

Commit

Permalink
5.20.0 release notes (#17541)
Browse files Browse the repository at this point in the history
  • Loading branch information
slevenick authored Mar 11, 2024
1 parent 99a090f commit b15aab4
Showing 1 changed file with 16 additions and 1 deletion.
17 changes: 16 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,19 @@
## 5.20.0 (Unreleased)
## 5.21.0 (Unreleased)
## 5.20.0 (Mar 11, 2024)

FEATURES:
* **New Resource:** `google_clouddeploy_custom_target_type_iam_*` ([#17445](https://github.com/hashicorp/terraform-provider-google/pull/17445))

IMPROVEMENTS:
* certificatemanager: added `type` field to `google_certificate_manager_dns_authorization` resource ([#17459](https://github.com/hashicorp/terraform-provider-google/pull/17459))
* compute: added the `network_url` attribute to the `consumer_accept_list`-block of the `google_compute_service_attachment` resource ([#17492](https://github.com/hashicorp/terraform-provider-google/pull/17492))
* gkehub: added support for `policycontroller.policy_controller_hub_config.policy_content.bundles` and
`policycontroller.policy_controller_hub_config.deployment_configs` fields to `google_gke_hub_feature_membership` ([#17483](https://github.com/hashicorp/terraform-provider-google/pull/17483))

BUG FIXES:
* artifactregistry: fixed permadiff when `google_artifact_repository.docker_config` field is unset ([#17484](https://github.com/hashicorp/terraform-provider-google/pull/17484))
* bigquery: corrected plan-time validation on `google_bigquery_dataset.dataset_id` ([#17449](https://github.com/hashicorp/terraform-provider-google/pull/17449))
* kms: fixed issue where `google_kms_crypto_key_version.attestation.cert_chains` properties were incorrectly set to type string ([#17486](https://github.com/hashicorp/terraform-provider-google/pull/17486))

## 5.19.0 (Mar 4, 2024)

Expand Down

0 comments on commit b15aab4

Please sign in to comment.