A method for suppressing deprecation diagnostics

[ericrichtert]

Terraform Version

λ terraform version
Terraform v1.15.1
on windows_amd64
+ provider registry.terraform.io/hashicorp/aws v6.43.0

Terraform Configuration Files

data "aws_region" "current" {}

output "region" {
  description = "AWS region"
  value       = data.aws_region.current
}

Debug Output

https://gist.github.com/ericrichtert/989e2ce096a99d9e4c1e264e91be8ffe

Expected Behavior

No warnings about deprecation, just like TF 1.14.x

Actual Behavior

│ Warning: Deprecated value used
│
│   on test.tf line 5, in output "region":
│    5:   value       = data.aws_region.current
│
│   The deprecation originates from data.aws_region.current.name
│
│ name is deprecated. Use region instead.

Steps to Reproduce

1. terraform init -backend=false
2. terraform validate

Additional Context

No response

References

No response

Generative AI / LLM assisted development?

No response

[jbardin]

Hi @ericrichtert,

Thanks for filing the issue. The output you see here is the expected behavior, because name is being used as part of the output value. Terraform doesn't know what is being done with the deprecated value other than it is being used in some way. Because the transition of the data to an output would otherwise lose the diagnostics, and consumers of that output would be unaware of the situation, Terraform prints the diagnostic at the last chance it has to raise it.

If you are only concerned with the name of the region, specifying only the region attribute is preferable. If you want multiple parts of the object, explicitly constructing the output object out of the desired values is the intended usage:

output "region" {
  description = "AWS region"
  value       = {
    region = data.aws_region.current.region,
    endpoint = data.aws_region.current.endpoint,
}

Perhaps a method for intentionally suppressing diagnostic is something that could be looked into in the future.