jobspec: expose the hcl2 strict config parameter for user toggling

[jrasell]

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

[apollo13]

Thanks for opening this. I am wondering if changing the default to strict=false and not adding a cli option would be an option. More code means more complexity and personally I cannot imagine that people rely on the behavior of strict=true.

If you think simply changing the default is not an option, please let me know how the env variable / cli flag should be named and I'll try to come up with a PR.

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.