chore(deps): update terraform aws to v6.73.0 #128
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/aws-6.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
6.72.0→6.73.0Release Notes
hashicorp/terraform-provider-aws (aws)
v6.73.0Compare Source
BREAKING CHANGES:
and_statementfromstatementblocks nested inand_statement, andor_statementfromstatementblocks nested inor_statement. These values are rejected by AWS. (#50604)managed_rule_group_statement,rate_based_statementandrule_group_reference_statementfromstatementblocks nested inand_statement,not_statementandor_statement. These values are rejected by AWS. (#50604)or_statementfromstatementblocks nested inor_statement. These values are rejected by AWS. (#50604)NOTES:
encrypted = truetoencrypted = falsewill seem to have succeeded without modifying anything on the AWS side. In this scenario you will need to manually recreate the file system viaterraform destroyandterraform apply(#49999)FEATURES:
aws_dsql_stream(#50813)aws_networksecuritymanager_admin_account(#50164)aws_networksecuritymanager_deployment(#50815)aws_networksecuritymanager_policy(#50789)aws_networksecuritymanager_template(#50799)aws_config_connector(#49559)aws_dsql_stream(#50813)aws_networksecuritymanager_admin_account(#50164)aws_networksecuritymanager_deployment(#50815)aws_networksecuritymanager_policy(#50789)aws_networksecuritymanager_template(#50799)ENHANCEMENTS:
connection_typeattribute (#50454)validation_window_hoursto be0(#50272)encrypted = truefor new file systems.kms_key_idno longer requiresencryptedto be set explicitly totrue, and settingencrypted = falseno longer forces resource replacement (#49999)connection_typeargument to support public endpoints (#50454)azureconfiguration block toconnector_providerfor Microsoft Azure multi-cloud coverage (#49560)memory_in_mb(#49826)tunnel_bandwidthargument (#47843)BUG FIXES:
sort_by.keyvalidation (#50814)InvalidDocumentOperationexceptions during Read when sharing is managed through AWS RAM (#50416)net/http: TLS handshake timeouterrors when making AWS API calls from networks where TLS traffic is inspected by middleboxes such as AWS Network Firewall, corporate proxies and firewalls. v6.71.0 and v6.72.0 were built with Go1.27.3, which advertises the post-quantum ML-DSA signature algorithms in the TLS 1.3ClientHellosignature_algorithms_certextension, and such middleboxes are known to drop thoseClientHellomessages silently. The provider is now built with Go1.27.4, which omits ML-DSA fromsignature_algorithms_cert, and a regression test guards theClientHelloagainst future toolchain changes (#50816)user_idsadditions being silently dropped when the same update also removes an already-detached user (#49948)ConflictException: Account or org is already onboarded(#50807)contentwhen AWS returns policy statement elements in a different order (#47190)InvalidDocumentOperationexceptions during Read when sharing is managed through AWS RAM (#50416)private_dns_only_for_inbound_resolver_endpointbeing forced totrueand not configurable for S3 interface endpoints that use thes3-fipsservice name (#50857)rulenorrule_jsonhas a planned change (#50790)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ 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 this update again.
This PR has been generated by Mend Renovate CLI.