The HashiCorp Nomad Resource Provider lets you manage Nomad resources.
This package is available in many languages in the standard packaging formats.
To use from JavaScript or TypeScript in Node.js, install using either npm
:
$ npm install @pulumi/nomad
or yarn
:
$ yarn add @pulumi/nomad
To use from Python, install using pip
:
$ pip install pulumi_nomad
To use from Go, use go get
to grab the latest version of the library
$ go get github.com/pulumi/pulumi-nomad/sdk/v2
To use from .NET, install using dotnet add package
:
$ dotnet add package Pulumi.Nomad
The following configuration points are available:
-
nomad:address
- The HTTP(S) API address of the Nomad agent. This must include the leading protocol (e.g. https://). This can also be specified as theNOMAD_ADDR
environment variable. -
nomad:region
- The Nomad region to target. This can also be specified as theNOMAD_REGION
environment variable. -
nomad:httpAuth
- HTTP Basic Authentication credentials to be used when communicating with Nomad, in the format of eitheruser
oruser:pass
. This can also be specified using theNOMAD_HTTP_AUTH
environment variable. -
nomad:caFile
- A local file path to a PEM-encoded certificate authority used to verify the remote agent's certificate. This can also be specified as theNOMAD_CACERT
environment variable. -
nomad:caPerm
- PEM-encoded certificate authority used to verify the remote agent's certificate. -
nomad:certFile
- A local file path to a PEM-encoded certificate provided to the remote agent. If this is specified, key_file or key_pem is also required. This can also be specified as theNOMAD_CLIENT_CERT
environment variable. -
nomad:certPem
- PEM-encoded certificate provided to the remote agent. If this is specified,keyFile
orkeyPem
is also required. -
nomad:keyFile
- A local file path to a PEM-encoded private key. This is required ifcertFile
orcertPem
is specified. This can also be specified via theNOMAD_CLIENT_KEY
environment variable. -
nomad:keyPem
- PEM-encoded private key. This is required ifcertFile
orcertPem
is specified. -
nomad:headers
- A configuration block, described below, that provides headers to be sent along with all requests to Nomad. This block can be specified multiple times. -
nomad:vaultToken
- A Vault token used when submitting the job. This can also be specified as theVAULT_TOKEN
environment variable or using a Vault token helper (see Vault's documentation for more details). -
nomad:consulToken
- A Consul token used when submitting the job. This can also be specified as theCONSUL_HTTP_TOKEN
environment variable. See below for strategies when multiple Consul tokens are required. -
nomad:secretId
- The Secret ID of an ACL token to make requests with, for ACL-enabled clusters. This can also be specified via theNOMAD_TOKEN
environment variable.
The nomad:headers
configuration block accepts the following arguments:
-
name
- The name of the header. -
value
- The value of the header.
For further information, please visit the Nomad provider docs or for detailed reference documentation, please visit the API docs.