The new 2.0.0 doesn't parse %${var} core about terraform-provider-template HOT 6 OPEN

Hi @phreddrick,

We'll investigate the weird issue here... it looks like the % is escaping the ${ in a similar way that $${ would work, as a side effect of the new 2.0.0 feature allowing %{...} sequences that can themselves be escaped as %%{...}. That is, I think the escape handling is incorrectly permitting mixtures of % and $ rather than requiring two consecutive identical characters.

In the mean time, if you do not wish to pin your provider version back to 1.0.0 I think you can work around this by including the percent sign in the expression somehow. For example:

${join("", ["%", metagroup])} ALL=(ALL:ALL) ALL

from terraform-provider-template.

Thanks for the workaround. It didn't occur to me to use one of the builtin functions like that.

from terraform-provider-template.

Turns out the work-around doesn't work for terraform 0.11.11. I get:

data.template_file.sudoers: Refreshing state...

Error: Error refreshing state: 1 error(s) occurred:

* data.template_file.sudoers: 1 error(s) occurred:

* data.template_file.sudoers: data.template_file.sudoers: failed to render : <template_file>:3,1-1: Invalid character; This character is not used within the language., and 1 other diagnostic(s)

when I use the example you gave above.

from terraform-provider-template.

So the following workaround worked for me with both 1.0.0 and 2.0.0:

send in "%" as a variable called percent, then the template file looks like:

# Give ${metagroup} sudo access
${join("", list(percent, metagroup))} ALL=(ALL:ALL) ALL

from terraform-provider-template.

Sorry, yes, the workaround I suggested was intended for provider 2.0.0. Provider 1.0.0 shouldn't need a workaround at all because it doesn't yet have the %{...} control sequence syntax that led to this parser bug.

However, if you wish to write configuration that works for both, the list(...) function is a good way to do that, since it's supported as an alias of [ ... ] for backward-compatibility.

from terraform-provider-template.

yeah, I have to support both plugin's at the moment. At any rate, the big surprise to me was that I couldn't have the literal string "%" in the join, I had to pass it in as a variable

from terraform-provider-template.