ListDeploymentSnapshot
ListDeploymentResponse is the response from the API when listing Deployments.
Properties
idstring requiredUnique identifier for this deployment.projectNamestring optionalProjectName is the name of the project.createdstring requiredCreated defines when the Deployment was created.stackNamestring optionalStackName is the name of the stack.modifiedstring requiredCreated defines when the corresponding WorkflowRun was modified.pausedboolean optionalPaused indicates whether or not deployments are paused for this program.pulumiOperationenum requiredPulumiOperation is the operation that was performed.Values:update— Updatepreview— Previewdestroy— Destroyrefresh— Refreshdetect-drift— DetectDriftremediate-drift— RemediateDrift
statusenum requiredThe current execution status of the deployment.not-startedmeans the deployment is waiting in the queue. The Pulumi Cloud console shows it asQueued, or asPausedwhen deployments are paused for the stack or the organization.acceptedmeans the deployment has been taken off the queue for execution but has not started running yet. The console shows it alongsiderunning. Webhook payloads report bothnot-startedandacceptedasqueued.runningmeans at least one step has started and no step has failed.failedcovers, for example, a failed step, a timeout, or a cancellation, whether the deployment was queued or running.skippedmeans the deployment was removed from the queue without running, either becauseoperationContext.options.skipIntermediateDeploymentsis 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
- ↳
idstring requiredUnique identifier for this update. - ↳
updateIDstring requiredIdentifier of the underlying Pulumi CLI update operation. - ↳
versioninteger requiredThe version number of the update. - ↳
startTimeinteger requiredThe Unix timestamp when the update started. - ↳
endTimeinteger requiredThe Unix timestamp when the update ended. - ↳
resultenum requiredThe outcome of this individual Pulumi update. This reports the result of one update rather than the status of the deployment as a whole, and it uses a different set of values from the deployment’sstatus.Values:not-started— NotStarted- The update has not started.
in-progress— InProgress- The update has not yet completed.
succeeded— Succeeded- The update completed successfully.
failed— Failed- The update has failed.
- ↳
kindenum requiredThe kind of update operation.Values:update— Update- A Pulumi program update.
preview— Preview- A preview of an update, without impacting resources.
refresh— Refresh- A refresh operation.
rename— Rename- A rename of the stack or project name.
destroy— Destroy- An update which removes all resources.
import— Import- An update that entails importing a raw checkpoint file.
resource-import— ResourceImport- An update that entails importing one or more resources.
Pupdate— PreviewUpdate- A preview of an update operation.
Prefresh— PreviewRefresh- A preview of a refresh operation.
Pdestroy— PreviewDestroy- A preview of a destroy operation.
Pimport— PreviewImport- A preview of an import operation.
Prename— PreviewRename- A preview of a rename operation.
- ↳
messagestring requiredA message associated with the update. - ↳
environmentmap[string]string requiredThe environment variables associated with the update. versioninteger requiredVersion is the ordinal ID for the stack- The list of jobs in this deployment
- ↳
statusenum requiredThe current execution status of this job. A deployment reports the status of its job, so this is normally the same value as the deployment’s ownstatus.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.
- ↳
startedstring optionalThe timestamp when the job started. - ↳
lastUpdatedstring optionalThe timestamp when the job was last updated. - The list of steps in the deployment job.
- RequestedBy contains the user information about the user who created the Deployment
- ↳
namestring requiredThe user’s display name. - ↳
githubLoginstring requiredThe user’s login name. - ↳
avatarUrlstring requiredThe URL of the user’s avatar image. - ↳
emailstring optionalThe user’s email address. It is only populated on selected endpoints and is omitted from most responses. Treat it as sensitive information. initiatorstring optionalInitiator is the initiation source of the deployment.- The agent pool used for this deployment, if any
- ↳
idstring requiredThe agent pool identifier - ↳
namestring requiredThe agent pool name