Deprecated attribute warning after upgrading the hashicorp/aws provider to 6.0.0

[eisraeli]

Description

A deprecation warning is issued by Terraform upon executing terraform validate after upgrading the hashicorp/aws provider to version 6.0.0

│ Warning: Deprecated attribute
│ 
│   on .terraform/modules/s3_bucket/main.tf line 623, in data "aws_iam_policy_document" "elb_log_delivery":
│  623:     for_each = { for k, v in local.elb_service_accounts : k => v if k == data.aws_region.current.name }
│ 
│ The attribute "name" is deprecated. Refer to the provider documentation for details.
│ 
│ (and 2 more similar warnings elsewhere)
╵

• Not using workspaces.
• Cleared local cache.

Versions

• Module version: 4.11.0
• Terraform version: 1.12.2
• Provider version(s): hashicorp/aws 6.0.0

Expected behavior

No warnings when running when running terraform validate

Actual behavior

The warning as pasted above.

[antonbabenko]

Resolved by #335

[mohag]

That requires Terraform 1.10, which means that it is not a fix for older versions (which works fine with the newer provider) (we are on 1.7, due to the removal of the use_legacy_workflow option (which we set to false), which meant that we couldn't have a config that is compatible with both 1.6 (where that needs to be set to get auth to work correctly) and 1.8 (where it was removed). (And upgrades have been blocked since to prevent changes that would be incompatible with a potential migration to a fork)

(The module does not seem to require any 1.10 features)

[denisazevedo]

It is still happening in latest Terraform:

Terraform v1.12.2
on darwin_arm64
+ provider registry.terraform.io/hashicorp/aws v6.4.0

Warning: Deprecated attribute
│ 
│   on .terraform/modules/cloudfront.s3_app/main.tf line 623, in data "aws_iam_policy_document" "elb_log_delivery":
│  623:     for_each = { for k, v in local.elb_service_accounts : k => v if k == data.aws_region.current.name }

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.