Name plan time validation aws_globalaccelerator_accelerator broken

[e-moshaya]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Affected Resource(s)

• aws_globalaccelerator_accelerator

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

resource "aws_globalaccelerator_accelerator" "this" {
  name = "tes-mount-test-global-accelerator"
}

Debug Output

Error: expected length of name to be in the range (1 - 32), got syn-scout-test-global-accelerator

Expected Behavior

The plan time validation in #17739 has broken our Terraform project. The expected length of name to be in the range for the aws_globalaccelerator_accelerator should be (1 - 64) and not (1 - 32). Our plans for previously created resources are failing. Check the API documentation for name range.

Error: expected length of name to be in the range (1 - 32), got tes-catlo-besg-global-accelerator

Even though this name is within the allowed range.

Actual Behavior

The plan time validation for the name length should be between 1-64 and not 1-32

Steps to Reproduce

1. terraform apply

Important Factoids

References

• https://docs.aws.amazon.com/global-accelerator/latest/api/API_CreateAccelerator.html#API_CreateAccelerator_RequestSyntax
• r/aws_globalaccelerator_accelerator: Correctly update flow log attributes when enabled #17739

[anGie44]

Hi @e-moshaya , thank you raising this issue and apologies you came across this behavior! This issue happens to duplicate #17978, so I'm going to close this but please refer to #17978 for updates.

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!