--missing-key-action is only relevant for the use case where you:
Reference a variable that does not have an explicit configuration in boilerplate.yml.
That variable does not have a value passed in via --var or --var-file.
You want to silently render that because you can't tolerate errors.
I think this is very hard to use in practice, and encourages poor boilerplate templates, where you by design use variables that have no explicitly passed in values, or defaults defined in the boilerplate.yml config.
I think this is an anti-pattern, and we should make boilerplate always encourage and enforce that a referenced variable shows up in at least one of the following:
The boilerplate.yml config
An explicitly set variable in --var
An explicitly set variable in --var-file
This is the equivalent of setting --missing-key-action=error, which is the default.
I don't see a valid use case for the other actions in boilerplate land, as I believe all other use cases can be handled by defining the variable explicitly (e.g., if you want --missing-key-action zero, you set the variable to the expected zero value in CLI with --var or in a var file).
--missing-key-actionis only relevant for the use case where you:boilerplate.yml.--varor--var-file.I think this is very hard to use in practice, and encourages poor boilerplate templates, where you by design use variables that have no explicitly passed in values, or defaults defined in the
boilerplate.ymlconfig.I think this is an anti-pattern, and we should make
boilerplatealways encourage and enforce that a referenced variable shows up in at least one of the following:boilerplate.ymlconfig--var--var-fileThis is the equivalent of setting
--missing-key-action=error, which is the default.I don't see a valid use case for the other actions in
boilerplateland, as I believe all other use cases can be handled by defining the variable explicitly (e.g., if you want--missing-key-action zero, you set the variable to the expected zero value in CLI with--varor in a var file).