Provide defaults for missing JOB values #28
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.
As reported in Slack, if a value is missing,
jq
returnsnull
. When run normally (e.g.,echo "${JOB}" | jq -r '.somekey'
), this becomes an empty string when the key is missing. However, when run within a subshell (e.g., when assigning to a variable, such asVALUE=$(echo "${JOB}" | jq -r '.somekey')
), the stringnull
is returned.Fortunately,
jq
allows specifying an alternative value if a value is missing orfalse
ornull
, via the//
operator. This patch adds alternatives everywherejq
is invoked when assigning a variable.