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
The formula's yaml files are carrying too much logic for files that must let you, at a quick glance, understand what values are being set as default or overriden in each of those files.
Even more, some of logic in these files, which should be loaded before pillars, are querying pillar values to construct variables or include values.
My understanding is that these files should just contain variables' assignments like here, have as little jinja as possible (like simple sets to avoid repetition) and then let map.jinja do all the magic.
The text was updated successfully, but these errors were encountered:
Agreed... This really isn't in the spirit that we originally had in putting some of this stuff into yaml to begin with. The original "shoving everything into map.jinja" way was impossible to read. This has just come full circle to be impossible to read again.
The formula's yaml files are carrying too much logic for files that must let you, at a quick glance, understand what values are being set as default or overriden in each of those files.
Even more, some of logic in these files, which should be loaded before pillars, are querying pillar values to construct variables or include values.
My understanding is that these files should just contain variables' assignments like here, have as little jinja as possible (like simple
set
s to avoid repetition) and then letmap.jinja
do all themagic
.The text was updated successfully, but these errors were encountered: