You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using {{ and }} for variable substitution makes it cumbersome to generate venom scripts with yaml library, when we need to make data substitutions (as opposed to string substitutions).
The following script is a valid venom script but cannot be written or parsed by a standard yaml library:
In this particular case, the variable cannot be enclosed in " because the executor needs a map, not a string.
Using an alternative marker, in addition to {{}} (if not in replacement of) would make things a lots smoother for programs that manipulates venom scripts.
The text was updated successfully, but these errors were encountered:
cdevienne
changed the title
(suggestion) replace "{{ }}" with "$( )" or any yaml-friendly marker
(suggestion) replace "{{ }}" with "$( )", "${ }" or any yaml-friendly marker
Mar 25, 2024
How about an alternative markup in addition to {{}} that would not break any existing script but would still solve my main issue?
I can provide a patch.
For now, the basecode is linked to the CDS SDK Interpolate func (github.com/ovh/cds/sdk/interpolate), not sure that it's possible to add an alternative markup easily.
In the next major release, we will move to ${{..}} and remove the CDS Interpolate usage.
--> #804
Using {{ and }} for variable substitution makes it cumbersome to generate venom scripts with yaml library, when we need to make data substitutions (as opposed to string substitutions).
The following script is a valid venom script but cannot be written or parsed by a standard yaml library:
In this particular case, the variable cannot be enclosed in " because the executor needs a map, not a string.
Using an alternative marker, in addition to {{}} (if not in replacement of) would make things a lots smoother for programs that manipulates venom scripts.
The text was updated successfully, but these errors were encountered: