Deployments HTTP API
The /deployment
endpoints are used to query for and interact with deployments.
List Deployments
This endpoint lists all deployments.
Method | Path | Produces |
---|---|---|
GET | /v1/deployments | application/json |
The table below shows this endpoint's support for blocking queries and required ACLs.
Blocking Queries | ACL Required |
---|---|
YES | namespace:read-job |
Parameters
prefix
(string: "")
- Specifies a string to filter deployments based on an ID prefix. Because the value is decoded to bytes, the prefix must have an even number of hexadecimal characters (0-9a-f) .This is specified as a query string parameter and is used before anyfilter
expression is applied.namespace
(string: "default")
- Specifies the target namespace. Specifying*
will return all evaluations across all authorized namespaces. This parameter is used before anyfilter
expression is applied.next_token
(string: "")
- This endpoint supports paging. Thenext_token
parameter accepts a string which is theID
field of the next expected deployment. This value can be obtained from theX-Nomad-NextToken
header from the previous response.per_page
(int: 0)
- Specifies a maximum number of deployments to return for this request. If omitted, the response is not paginated. TheID
of the last deployment in the response can be used as thelast_token
of the next request to fetch additional pages.filter
(string: "")
- Specifies the expression used to filter the results. Consider using pagination or a query parameter to reduce resource used to serve the request.reverse
(bool: false)
- Specifies the list of returned deployments should be sorted in the reverse order. By default deployments are returned sorted in chronological order (older deployments first), or in lexicographical order by their ID if theprefix
query parameter is used.
Sample Request
Sample Response
Read Deployment
This endpoint reads information about a specific deployment by ID.
Method | Path | Produces |
---|---|---|
GET | /v1/deployment/:deployment_id | application/json |
The table below shows this endpoint's support for blocking queries and required ACLs.
Blocking Queries | ACL Required |
---|---|
YES | namespace:read-job |
Parameters
:deployment_id
(string: <required>)
- Specifies the UUID of the deployment. This must be the full UUID, not the short 8-character one. This is specified as part of the path.
Sample Request
Sample Response
List Allocations for Deployment
This endpoint lists the allocations created or modified for the given deployment.
Method | Path | Produces |
---|---|---|
GET | /v1/deployment/allocations/:deployment_id | application/json |
The table below shows this endpoint's support for blocking queries and required ACLs.
Blocking Queries | ACL Required |
---|---|
YES | namespace:read-job |
Parameters
:deployment_id
(string: <required>)
- Specifies the UUID of the deployment. This must be the full UUID, not the short 8-character one. This is specified as part of the path.
Sample Request
Sample Response
Fail Deployment
This endpoint is used to mark a deployment as failed. This should be done to force the scheduler to stop creating allocations as part of the deployment or to cause a rollback to a previous job version. This endpoint only triggers a rollback if the most recent stable version of the job has a different specification than the job being reverted.
Method | Path | Produces |
---|---|---|
POST | /v1/deployment/fail/:deployment_id | application/json |
The table below shows this endpoint's support for blocking queries and required ACLs.
Blocking Queries | ACL Required |
---|---|
NO | namespace:submit-job |
Parameters
:deployment_id
(string: <required>)
- Specifies the UUID of the deployment. This must be the full UUID, not the short 8-character one. This is specified as part of the path.
Sample Request
Sample Response
Pause Deployment
This endpoint is used to pause or unpause a deployment. This is done to pause a rolling upgrade or resume it.
Method | Path | Produces |
---|---|---|
POST | /v1/deployment/pause/:deployment_id | application/json |
The table below shows this endpoint's support for blocking queries and required ACLs.
Blocking Queries | ACL Required |
---|---|
NO | namespace:submit-job |
Parameters
:deployment_id
(string: <required>)
- Specifies the UUID of the deployment. This must be the full UUID, not the short 8-character one. This is specified as part of the path and in the JSON payload.Pause
(bool: false)
- Specifies whether to pause or resume the deployment.
Sample Payload
Sample Request
Sample Response
Promote Deployment
This endpoint is used to promote task groups that have canaries for a deployment. This should be done when the placed canaries are healthy and the rolling upgrade of the remaining allocations should begin.
Method | Path | Produces |
---|---|---|
POST | /v1/deployment/promote/:deployment_id | application/json |
The table below shows this endpoint's support for blocking queries and required ACLs.
Blocking Queries | ACL Required |
---|---|
NO | namespace:submit-job |
Parameters
:deployment_id
(string: <required>)
- Specifies the UUID of the deployment. This must be the full UUID, not the short 8-character one. This is specified as part of the path and JSON payload.All
(bool: false)
- Specifies whether all task groups should be promoted.Groups
(array<string>: nil)
- Specifies a particular set of task groups that should be promoted.
Sample Payload
Sample Request
Sample Response
Set Allocation Health in Deployment
This endpoint is used to set the health of an allocation that is in the
deployment manually. In some use cases, automatic detection of allocation health
may not be desired. As such those task groups can be marked with an upgrade
policy that uses health_check = "manual"
. Those allocations must have their
health marked manually using this endpoint. Marking an allocation as healthy
will allow the rolling upgrade to proceed. Marking it as failed will cause the
deployment to fail. This endpoint only triggers a rollback if the most recent stable
version of the job has a different specification than the job being reverted.
Method | Path | Produces |
---|---|---|
POST | /v1/deployment/allocation-health/:deployment_id | application/json |
The table below shows this endpoint's support for blocking queries and required ACLs.
Blocking Queries | ACL Required |
---|---|
NO | namespace:submit-job |
Parameters
:deployment_id
(string: <required>)
- Specifies the UUID of the deployment. This must be the full UUID, not the short 8-character one. This is specified as part of the path and the JSON payload.HealthyAllocationIDs
(array<string>: nil)
- Specifies the set of allocation that should be marked as healthy.UnhealthyAllocationIDs
(array<string>: nil)
- Specifies the set of allocation that should be marked as unhealthy.
Sample Payload
Sample Request
Sample Response
Unblock Deployment
This endpoint is used to manually mark a blocked multiregion deployment as successful. A blocked deployment is a multiregion deployment within a region that has completed within a region but is waiting on the other federated regions. The endpoint can be used in cases where a failed peer region is unable to communicate its failed deployment status to other regions to force a deployment to complete.
Method | Path | Produces |
---|---|---|
POST | /v1/deployment/unblock/:deployment_id | application/json |
The table below shows this endpoint's support for blocking queries and required ACLs.
Blocking Queries | ACL Required |
---|---|
NO | namespace:submit-job |
Parameters
:deployment_id
(string: <required>)
- Specifies the UUID of the deployment. This must be the full UUID, not the short 8-character one. This is specified as part of the path.
Sample Request
Sample Response