open-nomad/website/content/docs/commands/deployment/resume.mdx

57 lines
1.5 KiB
Plaintext
Raw Normal View History

---
2020-02-06 23:45:31 +00:00
layout: docs
page_title: 'Commands: deployment resume'
description: |
The deployment resume command is used to resume a paused deployment.
---
# Command: deployment resume
The `deployment resume` command is used used to unpause a paused deployment.
Resuming a deployment will resume the placement of new allocations as part of
rolling deployment.
## Usage
```plaintext
nomad deployment resume [options] <deployment id>
```
The `deployment resume` command requires a single argument, a deployment ID or
prefix.
When ACLs are enabled, this command requires a token with the `submit-job`
and `read-job` capabilities for the deployment's namespace.
## General Options
2020-02-06 23:45:31 +00:00
@include 'general_options.mdx'
## Resume Options
- `-detach`: Return immediately instead of monitoring. A new evaluation ID
will be output, which can be used to examine the evaluation using the
[eval status] command
- `-verbose`: Show full information.
## Examples
Manually resume a deployment:
2020-05-18 20:53:06 +00:00
```shell-session
$ nomad deployment resume c848972e
Deployment "c848972e-dcd3-7354-e0d2-39d86642cdb1" resumed
==> Monitoring evaluation "5e266d42"
Evaluation triggered by job "example"
Evaluation within deployment: "c848972e"
Allocation "00208424" created: node "6240eed6", group "web"
Allocation "68c72edf" created: node "6240eed6", group "cache"
Allocation "00208424" status changed: "pending" -> "running"
Evaluation status changed: "pending" -> "complete"
==> Evaluation "5e266d42" finished with status "complete"
```
2020-02-06 23:45:31 +00:00
[eval status]: /docs/commands/eval-status