feat: ignore variables with targetValue nil
#72
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The targetValue of variables only evaluates to
nil
if their actual value is undefined.This case might occur if one defines an inventory value which uses bash / environment variables, which
ook like skipper variables, but actually aren't.
If in the inventory you have
Then
${MY_ENV_VARIABLE}
would be treated as skipper variable, but without atargetValue
, hence it would bereplaced with
nil
. This PR changes the default behaviour so that these variables are not replaced at all.