RFC: Changing the way environment variables expansion works in Task Manifests

[kdembler]

Problem

Current Snap environment variable expansion is quite 'greedy'. Due to call to os.ExpandEnv() any symbol starting with $ will be expanded with no way to escape it. There should be some way to allow users to, for example pass config parameters with $ in them.

Possible solutions

• Provide way to escape symbols with $ in them
• Enable mechanism that expands only those symbols that are valid (set) environment variables

Further information can be found at issue #1691

@intelsdi-x/snap-maintainers

[kindermoumoute]

There's still a way to pass $ if you store it in an environment variable. I agree that's tricky, but it's doing the job. :-)