1. Docs
2. Reference
3. REST API Docs
4. Schema
5. ListDeploymentResponseV2

Response containing a paginated list of deployment snapshots (v2).

Properties

• deployments array[ListDeploymentSnapshot] required
  The list of deployment snapshots
• ↳ id string required
  Unique identifier for this deployment.
• ↳ projectName string optional
  ProjectName is the name of the project.
• ↳ created string required
  Created defines when the Deployment was created.
• ↳ stackName string optional
  StackName is the name of the stack.
• ↳ modified string required
  Created defines when the corresponding WorkflowRun was modified.
• ↳ paused boolean optional
  Paused indicates whether or not deployments are paused for this program.
• ↳ pulumiOperation enum required
  PulumiOperation is the operation that was performed.
  Values:

  update — Update

  preview — Preview

  destroy — Destroy

  refresh — Refresh

  detect-drift — DetectDrift

  remediate-drift — RemediateDrift

• ↳ status enum required
  The current execution status of the deployment. not-started means the deployment is waiting in the queue. The Pulumi Cloud console shows it as Queued, or as Paused when deployments are paused for the stack or the organization. accepted means the deployment has been taken off the queue for execution but has not started running yet. The console shows it alongside running. Webhook payloads report both not-started and accepted as queued. running means at least one step has started and no step has failed. failed covers, for example, a failed step, a timeout, or a cancellation, whether the deployment was queued or running. skipped means the deployment was removed from the queue without running, either because operationContext.options.skipIntermediateDeployments is enabled for it and a newer deployment of the same operation is queued right behind it for the same stack, or because it was still queued seven days after it was created. Once the deployment’s job has started, this matches the job’s status.
  Values:

  not-started — NotStarted

  The work has been created but has not started yet.

  accepted — Accepted

  The work has been picked up for execution but has not started running yet.

  running — Running

  The work is executing.

  failed — Failed

  The work finished without completing successfully. Failures, timeouts, and cancellations are all reported as failed, and there is no separate status for canceled work. This is a terminal status.

  succeeded — Succeeded

  The work completed successfully. This is a terminal status.

  skipped — Skipped

  The work was dropped without ever running. Only deployments report this status. This is a terminal status.

• ↳ updates array[DeploymentNestedUpdate] required
  Updates
• ↳ version integer required
  Version is the ordinal ID for the stack
• ↳ jobs array[DeploymentJob] required
  The list of jobs in this deployment
• ↳ requestedBy UserInfo required
  RequestedBy contains the user information about the user who created the Deployment
• ↳ initiator string optional
  Initiator is the initiation source of the deployment.
• ↳ agentPool ListDeploymentSnapshotAgentPool optional
  The agent pool used for this deployment, if any
• itemsPerPage integer required
  The number of items per page
• total integer required
  The total number of deployments