Nomad Pack 0.1 (meta issue)

[mikenomitch]

This is a meta issue for capturing the various things we want to do for the "beta" Pack release.

The contents of this are subject to change as we get further along:

Quality of Life Improvements:

• Add support for rendering non-job files #299
• Add support for optional jobs #188
• Rendered jobs should be auto-formatted #301
• Add var-file command to initialize a variables file #25
• Do not error when passing additional variables #302

Structural Changes:

• Registry metadata improvements #304
• Remove "author" from pack metadata #300
• Improve nested packs (better variable scoping, metadata access) #339
• Change "registry list" to list registries and add "list" for listing Packs #354

Bug Fixes/QOL:

• Nomad Pack Panics at job deployment on Nomad 0.9.7 #279
• nomad-pack does not support basic auth in NOMAD_ADDR env var #153
• client: set client region and namespace based on jobspec #266

Outside of the Repo:

• Add Packs and Registries to Nomad-specific HashiCorp Integrations page (similar to Vault's).
• Document deps flow better and/or vendoring helper

[attachmentgenie]

@mikenomitch i would like to make a case for #153 and #266. These tickets describe IMHO reasonably annoying behavior that cause nomad-pack to behave different from vanilla nomad

[betterthanbreakfast]

@mikenomitch fyi, looks like nomad-openapi v0.0.0-20221012231901-fc8faf7e8906 is broken, it throughs an error with nomad version 1.5.0 prior to 1.5.2:

! Failed To Parse Job Specification

        Error:   Post "https://example.com/v1/jobs/parse": remote error: tls: handshake failure
        Type:    *v1.APIError

I've tried to manually update nomad-openapi library from c88966d commit, and it works fine.

Moreover, #307 is also related to this issue and got fixed after update.

[david-yu]

@angrycub Should we close this as well?