Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: aws_dx_gateway name validation error when using underscores #30732

Closed
marcincuber opened this issue Apr 14, 2023 · 2 comments · Fixed by #30739
Closed

[Bug]: aws_dx_gateway name validation error when using underscores #30732

marcincuber opened this issue Apr 14, 2023 · 2 comments · Fixed by #30739
Labels
bug Addresses a defect in current functionality. regression Pertains to a degraded workflow resulting from an upstream patch or internal enhancement. service/directconnect Issues and PRs that pertain to the directconnect service.

Comments

@marcincuber
Copy link

marcincuber commented Apr 14, 2023

Terraform Core Version

1.4.2

AWS Provider Version

4.63.0

Affected Resource(s)

aws_dx_gateway

Expected Behavior

Validation should work for dx_gateway name which uses _. It is acceptable in AWS console.

Actual Behavior

Error: invalid value for name (Name must contain no more than 100 characters. Valid characters are a-z, 0-9, and hyphens (–).)

  with aws_dx_gateway.lnd_eng_1,
  on dx-gateway.tf line 2, in resource "aws_dx_gateway" "lnd_eng_1":
   2:   name            = "LDN_IXN_ENG_1"

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

resource "aws_dx_gateway" "lnd_eng_1" {
  name            = "LDN_IXN_ENG_1"
  amazon_side_asn = "64515"
}

Steps to Reproduce

apply above code

Panic Output

No response

Important Factoids

No response

References

Problem introduced by this
https://github.com/hashicorp/terraform-provider-aws/pull/30375/files

Validation also fails when I use the following name = "LDN-IXN-ENG-1" which should be allowed.

Would you like to implement a fix?

No

@marcincuber marcincuber added bug Addresses a defect in current functionality. needs-triage Waiting for first response or review from a maintainer. labels Apr 14, 2023
@github-actions
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • 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.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/directconnect Issues and PRs that pertain to the directconnect service. label Apr 14, 2023
@ewbankkit ewbankkit added regression Pertains to a degraded workflow resulting from an upstream patch or internal enhancement. and removed needs-triage Waiting for first response or review from a maintainer. labels Apr 14, 2023
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. regression Pertains to a degraded workflow resulting from an upstream patch or internal enhancement. service/directconnect Issues and PRs that pertain to the directconnect service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants