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
Hex string is parsed, and converted to a number (decimal 153).
Actual Behavior
Error: Invalid function argument
on main.tf line 5, in output "input-v1":
5: value = tonumber(var.v1)
|----------------
| var.v1 is "0x99"
Invalid value for "v" parameter: cannot convert "0x99" to number; given string
must be a decimal representation of a number.
Additional Context
The above example is a reduced case. In the real life use case, the hex string is generated from the substring of a hash to deterministically determine AZ placement without placement changing if other nodes are torn down (i.e. can't use index.count) - so this must be represented as a string and converted to a number for lookup in a list. Worked under 0.11 and previous, so considered a bug in 0.12.
The text was updated successfully, but these errors were encountered:
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
Oct 18, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
0.12.7
Terraform Configuration Files
Expected Behavior
Hex string is parsed, and converted to a number (decimal 153).
Actual Behavior
Additional Context
The above example is a reduced case. In the real life use case, the hex string is generated from the substring of a hash to deterministically determine AZ placement without placement changing if other nodes are torn down (i.e. can't use index.count) - so this must be represented as a string and converted to a number for lookup in a list. Worked under 0.11 and previous, so considered a bug in 0.12.
The text was updated successfully, but these errors were encountered: