Sign in
Deployments

Get Current

Get the current deployment for the device.

get/deployments/current

Response

Successfully retrieved the current deployment.

object'deployment' required

The object type, which is always deployment.

idstring required

ID of the deployment.

descriptionstring required

The description of the deployment.

status'drifted' | 'staged' | 'queued' | 'deployed' | 'removing' | 'archived' | 'failed' | 'retrying' required

This status merges the 'activity_status' and 'error_status' fields, with error states taking precedence over activity states when errors are present. For example, if the activity status is 'deployed' but the error status is 'failed', the status is 'failed'. However, if the error status is 'none' and the activity status is 'deployed', the status is 'deployed'.

activity_status'drifted' | 'staged' | 'queued' | 'deployed' | 'removing' | 'archived' required

Last known activity state of the deployment.

drifted means the device's configurations have drifted since this deployment was staged, and the deployment needs to be reviewed before it can be deployed.

staged means the deployment is ready to be deployed.

queued means the deployment's config instances are waiting to be received by the device and will be deployed as soon as the device is online.

deployed means the deployment's config instances are currently available for consumption on the device.

removing means the deployment's config instances are being removed from the device.

archived means the deployment is available for historical reference but cannot be deployed and is not active on the device.

error_status'none' | 'failed' | 'retrying' required

Last known error state of the deployment.

none means there are no errors.

retrying means an error has been encountered and the agent is retrying to reach the target status.

failed means a fatal error has been encountered; the deployment is archived and, if deployed, removed from the device.

target_status'staged' | 'deployed' | 'archived' required

Desired state of the deployment.

staged means the deployment is ready to be deployed.

deployed means all config instances in the deployment are available for consumption on the device.

archived means the deployment is available for historical reference but cannot be deployed and is not active on the device.

device_idstring required

ID of the device.

release_idstring required

ID of the release.

created_atstring date-time required

Timestamp of when the device release was created.

Example response

{
  "object": "deployment",
  "id": "dpl_123",
  "description": "Deployment for the motion control config instance",
  "status": "staged",
  "activity_status": "staged",
  "error_status": "none",
  "target_status": "staged",
  "device_id": "dvc_123",
  "release_id": "rls_123",
  "created_at": "2024-01-01T00:00:00Z"
}

Changes

Changed in 3 of the 5 revisions of this API.1212

  • 3baf7b9ffbac2See the full diff
    • ●

      added the new removing enum value to the activity_status response property for the response status 200

      response-property-enum-value-added

    • ●

      added the new removing enum value to the status response property for the response status 200

      response-property-enum-value-added

  • 6c5a928176c5111See the full diff
    • ▲

      the response's body type/format changed from / to object/ for status 200

      response-body-type-changed

    • ○

      removed BaseDeployment from the response body allOf list for the response status 200

      response-body-all-of-removed

    • ○

      added the required property activity_status to the response with the 200 status

      response-required-property-added

    • ○

      added the required property created_at to the response with the 200 status

      response-required-property-added

    • ○

      added the required property description to the response with the 200 status

      response-required-property-added

    • ○

      added the required property device_id to the response with the 200 status

      response-required-property-added

    • ○

      added the required property error_status to the response with the 200 status

      response-required-property-added

    • ○

      added the required property id to the response with the 200 status

      response-required-property-added

    • ○

      added the required property object to the response with the 200 status

      response-required-property-added

    • ○

      added the required property release_id to the response with the 200 status

      response-required-property-added

    • ○

      added the required property status to the response with the 200 status

      response-required-property-added

    • ○

      added the required property target_status to the response with the 200 status

      response-required-property-added

    This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • d827cc046cad1See the full diff
    • ○

      removed subschema #2 from the response body allOf list for the response status 200

      response-body-all-of-removed

    This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog