2fb7c957a4
When we switched to the current edition of the HCL parser, we inadvertently broke some undocumented behavior where users could successfully used escaped double quotes in a nested interpolation like this: foo = "${somefunc(\"somearg\")}" The proper syntax here is: foo = "${somefunc("somearg")}" Because once you are inside the interpolation braces, the "quoting context" is different. At the time, while we didn't like the fact that the non-standard syntax was in the wild, we didn't want to break BC, so we treated it as a bug and fixed it in #62. Now that we are at the moment of a major Terraform release, we can yank the BC compatible behavior, which fixes a currently broken use case - there is no way to express strings with double quotes in them from inside interpolation braces. foo = "${somefunc("\"inquotes\"")}" After merge and a dep upgrade, this will take care of https://github.com/hashicorp/terraform/issues/5550 |
||
---|---|---|
.. | ||
basic_int_string.hcl | ||
basic_squish.hcl | ||
basic.hcl | ||
basic.json | ||
decode_policy.hcl | ||
decode_policy.json | ||
decode_tf_variable.hcl | ||
decode_tf_variable.json | ||
empty.hcl | ||
escape.hcl | ||
flat.hcl | ||
float.hcl | ||
float.json | ||
multiline_bad.hcl | ||
multiline_indented.hcl | ||
multiline_no_eof.hcl | ||
multiline_no_hanging_indent.hcl | ||
multiline_no_marker.hcl | ||
multiline.hcl | ||
multiline.json | ||
nested_block_comment.hcl | ||
nested_provider_bad.hcl | ||
object_list.json | ||
scientific.hcl | ||
scientific.json | ||
slice_expand.hcl | ||
structure2.hcl | ||
structure2.json | ||
structure_flat.json | ||
structure_flatmap.hcl | ||
structure_list_deep.json | ||
structure_list.hcl | ||
structure_list.json | ||
structure_multi.hcl | ||
structure_multi.json | ||
structure.hcl | ||
structure.json | ||
terraform_heroku.hcl | ||
terraform_heroku.json | ||
tfvars.hcl | ||
unterminated_block_comment.hcl | ||
unterminated_brace.hcl |