jobspec: expose the hcl2 strict config parameter for user toggling #11164
Labels
stage/accepted
Confirmed, and intend to work on. No timeline committment though.
theme/cli
theme/hcl
theme/jobspec
type/enhancement
When running plan/run/validate commands on job specification files that use hclv2 rendering, users may wish to pass generic variables files which include variables not used by the job. Currently, Nomad parsing with return an error as override variables must be matched with a variable definition in the job specification file.
Internally, the jobspec2 parsing includes a strict config parameter which can defined whether these undefined variable occurrences are treated as an error or a warning. This currently is not exposed to users to change the behaviour, however, should be considered, to cover such use cases.
Opened as a result of discussion within #11149
The text was updated successfully, but these errors were encountered: