Support optional object type attributes in Nomad HCL variables

[atavakoliyext]

Proposal

Support optional(...) in object type attributes, similar to the equivalent feature from Terraform

Use-cases

Variables that use complex types (e.g. list(object({ ... })), where some fields are optional, currently have to be specified in full, or have to be defined as maps where the burden of type validation falls on the template author.

Attempted Solutions

• Using a type = map(string) and checking each field for existence/type-correctness
• Using a type = string, setting the value to some structured data format, like JSON or YAML, which is then (yaml|json)decoded and its contents' fields checked for existence/type-correctness

[jrasell]

Hi @atavakoliyext and thanks for raising this issue. I think supporting the type definition within job specification variables in a similar manner to Terraform makes sense. I'll move this onto our roadmapping list.

[atavakoliyext]

Great to hear, thank you! I look forward to seeing where it lands on your roadmap 🙂