You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWS ELBs have a naming requirement which prevents chars like _'s. That is all well and good, but the terraform syntax parser (0.6.3) applies the same logic to the variable names and the interpolated value. It's my opinion the parser shouldn't care what the variable/interpolated thing is called, only it's value.
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.
ghost
locked and limited conversation to collaborators
Apr 30, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Related to #2580
AWS ELBs have a naming requirement which prevents chars like _'s. That is all well and good, but the terraform syntax parser (0.6.3) applies the same logic to the variable names and the interpolated value. It's my opinion the parser shouldn't care what the variable/interpolated thing is called, only it's value.
Example:
Tosses
Short term fix is
sed 's/es_elb/es-elb/g'
, just weird because all my other variables have _'s in them.Terraform does inspect the value in ${aws_elb.es_elb.name}, and throws an error if theres an underscore, so that's good.
The text was updated successfully, but these errors were encountered: