Backport of template: error on missing key into release/1.4.x #15148
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hc-github-team-nomad-core
force-pushed
the
backport/f-err-on-missing-key/multiply-daring-ram
branch
from
7c8b7d3
to
4057c4b
Compare
hc-github-team-nomad-core
deleted the
backport/f-err-on-missing-key/multiply-daring-ram
branch
|
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport
This PR is auto-generated from #15141 to be assessed for backporting due to the inclusion of the label backport/1.4.x.
The below text is copied from the body of the original PR.
This PR adds the consul-template configuration option
error_on_missing_key. This allows jobspec authors to specify that a template should fail if it references a map key that does not exist. The default value isfalseand should be fully backward compatible.This PR does not prevent the template engine from performing normal blocking behavior for functions that use blocking queries. This solely addresses the missing key in a map case. The other cases can be managed by using a non-blocking alternative and the
sprig_fail «message»functionThis PR replaces #14002, just because it was easier to hand recreate it then to tease through the merge conflicts.