deploy
deploy list
List recent deployments.
read onlyrepeatable
What has shipped, newest first, for one application or across the whole team.
This is also where a deployment id comes from when you no longer have the one
deploy create printed.
Usage
outplane deploy list [APP] [flags]Arguments
| Argument | Type | Description |
|---|---|---|
APP | string | App name or id. Omit for the whole team. |
Flags
| Flag | Type | Description |
|---|---|---|
--limit | int | How many of the most recent deployments to show. Defaults to 20. |
The global flags apply as well.
Output
| Field | Type | Description |
|---|---|---|
deploymentId | int | The id deploy get and deploy logs take. |
app | string | null | Which application it belongs to. |
appId | string | null | |
status | string | One of queued, building, deploying, ready, failed, crashed, canceled. |
branch | string | null | For a Git-sourced app. |
imageRef | string | null | For a container-registry app. |
commitMessage | string | null | |
startedAt | string | RFC 3339, UTC. |
duration | string | null | The server's own figure for the build, already humanised. Empty for an app that builds nothing. |
Examples
What has been deployed lately
outplane deploy listOne application's history
outplane deploy list checkout --limit 5Find the last failure
outplane deploy list --json --fields deploymentId,app,status{
"items": [
{
"app": "checkout",
"deploymentId": 412,
"status": "ready"
},
{
"app": "worker",
"deploymentId": 411,
"status": "failed"
}
],
"total": 2,
"truncated": false
}What to Know
- Newest first, ordered by deploymentId. The server returns them oldest first; the CLI reverses that, because the row anybody wants is the last one.
- truncated is true when more deployments exist than --limit asked for. There is no cursor: raise the limit or narrow to one application.
- total means what it can. For one application the endpoint returns everything, so it is the complete history. Across a team the endpoint paginates and offers no count, so total is what was returned and truncated is what tells you more exist.
- A canceled deployment was superseded by a newer one. Nothing went wrong.
- duration is empty for an application that deploys a ready-made image, because nothing was built.
Errors
Beyond 0 for success, this command exits with:
| Exit | Kind | Meaning |
|---|---|---|
2 | usage | Invalid arguments, unknown flag, or client-side validation failure. |
3 | auth | Not authenticated, token revoked or expired, or forbidden for this team. |
5 | not_found | The named resource does not exist, or is not visible to this credential. |
8 | upstream | The Out Plane API returned a server error. |
The code on the error object is one of app.not_found, usage.bad_limit, context.no_team. Branch on that, or on the exit status. The message is prose and changes.