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
{{ message }}
This repository was archived by the owner on May 22, 2025. It is now read-only.
Since StrictYAML parses all literals as strings, variables fit into configuration files seamlessly without having to quote them:
number: 400line: some stringvariable: ${pullconf::some-variable}
Right now variables need to resolve to the same type that is expected from the parameter where the variable is found or resolve to a string if substring substitution is used inside another string parameter:
Since StrictYAML parses all literals as strings, variables fit into configuration files seamlessly without having to quote them:
Right now variables need to resolve to the same type that is expected from the parameter where the variable is found or resolve to a string if substring substitution is used inside another string parameter:
It would be useful if variables were subscriptable in a way so values inside hash and array variables can be accessed:
The syntax for accessing values inside hashes and arrays could be:
Making variables subscriptable allows users to organize their variables better.
Possible issues: Variables should still be able to contain other variables. Resolving variables thus becomes a little more complex.