What is the difference between '"(())"', '(())' and (())? about fissile

[mook-as]

There is no actual difference; they all get parsed as YAML. But format one (two levels of quoting) may be required, if the expanded value is a string that looks like a number and it needs to go through multiple levels of YAML parsing (there's one in configgin as well).

The pass where fissile parses it to put it into /opt/fissile/env2conf.yml (in the docker images) should round trip fine, and that file gets parsed by configgin.

Let me know if that explanation is too confusing… because it sort of is :D

[qibobo]

@mook-as For format one: "But format one (two levels of quoting) may be required, if the expanded value is a string that looks like a number and it needs to go through multiple levels of YAML parsing (there's one in configgin as well)." Could you give an example?

[mook-as]

Looking more at this, I think that might actually be obsolete (sort of).

• Fissile copies it, verbatim, to env2conf.yml in the docker images
• Configgin loads it in here
• #transmogrify then (repeatedly) applies mustache templating to it
• Which happens in #processMustacheTemplate. (This will always strip one level of quoting)

So it should only end up needing multiple levels if it goes through multiple expansions (now), I think. I believe that previously fissile would do one level of unquoting as well, but we fixed it at some point? Looks like it was initially added in SUSE/scf@1aeb76d but the relevant PR didn't mention it.

(In general, I've been reducing the level of quoting when I touch things, but others might not have been…)

[viovanov]

1. '"((ONE))"'
   This forces the rendered template to be a string when loaded by configgin as a YAML value.
   e.g. ONE=5 '"((ONE))"' -> renders as "5" -> parsed as YAML string value "5".

2. '((ONE))'
   This does not force the rendered template to be a string.
   e.g. ONE=5 '((ONE))' -> renders as 5 -> parsed as YAML integer value 5.

3. ((ONE))
   Same as 2.

[jandubois]

This was not an issue, but a question, and seems to have been answered.