mandelsoft / spiff Goto Github PK

It is not easily possible to create a yaml file that contains dynaml expressions after being parsed by spiff.

For example, I would have expected this expression

foo: (( "(( bar ))" ))

to result in

foo: (( bar ))

which I could render with spiff again at a later time when bar is available. However, when rendering the above expression, spiff immediately also tries to resolve the resulting (( bar )) which causes an error in this case, since bar does not exist.

It is possible to achieve some kind of unresolved dynaml expression by using &template, but this makes things more complicated.
It should somehow be possible to write a dynaml expression that renders into another dynaml expression.

can someone help spiff merge issues for this case?

template.yaml

command: ["/cloud_sql_proxy",
                "-instances="(( .postgresconnectionnam ))"=tcp:5432"]

values.yaml

postgresconnectionname: PROJECT:REGION:INSTANCE

spiff merge template.yml values.yml

Output:

- /cloud_sql_proxy
- -instances=(( .postgresconnectionnam ))=tcp:5432

but the output should be

command:
- /cloud_sql_proxy
- -instances=PROJECT:REGION:INSTANCE=tcp:5432

I see that data is not getting interpolated. can someone help here?

This is a pretty cool project! I was wondering if any consideration has ever been made about support for external resources, either remote (across a network, e.g. something in a Github repo) or just somewhere else on disk. The remote case would be interesting if it was vcs aware allowing e.g. reference of a Git repo and tag to manage versioning.

spiff++ seems to automatically wrap long lines:

foo.yaml:

wrapTest: a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a

spiff merge foo.yaml =>

wrapTest: a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a
  a a a a a

It should somehow be possible to suppress this behaviour, as it e.g. screws with pattern matching.

please fix or do a 1.3.0 release.