Nomad
nomad-pack status command reference
Use the nomad-pack status command to fetch information on deployed Nomad packs.
Usage
nomad-pack status <pack_name> [options]
If you do not specify a pack name, the nomad-pack status command returns a
list of all deployed packs. If you do specify a pack name, this command returns
a list of all deployed jobs belonging to that pack, along with their status and
deployment names.
Options
-registry=<string>: Specific registry name containing the pack to inspect.If not specified, the command uses the default registry.-ref=<string>: Specific Git reference of the pack to retrieve info about. Supports tags, SHA, and@latest. If you do not specify a reference, the value defaults to@latest. Usingrefwith a file path is not supported.
Operation options
-var-file=<string>: Specifies the path to a variable override file. You may provide this multiple times on a single command for multiple files.-allow-unset-vars: Suppress errors from unset variables without default values. Equivalent of setting the NOMAD_PACK_ALLOW_UNSET_VARS environment variable to1ortrue.-ignore-missing-vars: Determines whether the command should override variables not present in the pack or should produce an error.-var=<key=value>: Specifies single override variables in the form of HCL syntax. You may specify multiple times per command.-name=<string>: If set, this is the unique identifier of this deployed instance of the specified pack. If not set, the pack name becomes the unique identifier. Setting a name is useful for running more than one instance of a pack within the same cluster. Note that this name must be globally unique within a cluster. Running the run command multiple times with the same name re-submits the same pack and applies changes if you have made any to the underlying pack. Be mindful that, whether you have made changes or not, the underlying allocations are replaced.When managing packs, the name specified here is the name that you should be pass to Nomad Packs'plananddestroycommands.-parser-v1: Use the legacy syntax parser to parse your job. This enables pack to run packs for earlier versions while you are migrating them to the new syntax
Nomad cluster options
-address=<string>: The address of the Nomad server. Overrides the NOMAD_ADDR environment variable if set.-namespace=<string>: The target namespace for queries and actions bound to a namespace. Overrides the NOMAD_NAMESPACE environment variable if set.-region=<string>: The region of the Nomad servers to forward commands to. Overrides the NOMAD_REGION environment variable if set.-ca-cert=<string>: Path to a PEM encoded CA cert file to use to verify the Nomad server SSL certificate. Overrides the NOMAD_CACERT environment variable if set.-client-cert=<string>: Path to a PEM encoded client certificate for TLS authentication to the Nomad server. Must also specify--client-key. Overrides the NOMAD_CLIENT_CERT environment variable if set.-client-key=<string>: Path to an unencrypted PEM encoded private key matching the client certificate from--client-cert. Overrides the NOMAD_CLIENT_KEY environment variable if set.-tls-server-name=<string>: The server name to use as the SNI host when connecting via TLS. Overrides the NOMAD_TLS_SERVER_NAME environment variable if set.-token=<string>: The SecretID of an ACL token to use to authenticate API requests with. Overrides the NOMAD_TOKEN environment variable if set.-tls-skip-verify: Do not verify TLS certificate. We do not recommend this. Verification is also skipped if you set the NOMAD_SKIP_VERIFY environment variable.
Examples
Get a list of all deployed packs and their registries.
nomad-pack status
Get a list of all deployed jobs in pack example, along with their status and deployment names.
nomad-pack status example
Get a list of all deployed jobs and their status for an example pack in the deployment name "dev".
nomad-pack status example --name=dev
Get a list of all deployed jobs and their status for an example pack in the deployment name "dev".
nomad-pack status example --name=dev --registry=community