Advanced DSL Project Management

Get push status

Retrieves the current push readiness status for a project without acquiring a lock.

Features:

  • Non-locking status check
  • Revision conflict detection
  • Active lock holder information
  • Lock expiry countdown

Use Cases:

  • Fast-fail check before starting expensive conflict detection
  • Dashboard status display for project push availability
  • CI/CD gate check before automated push

Scenarios:

  • Pre-flight call immediately before push-reservation
  • Polling while another user holds the push lock
  • Detecting stale local revision before upload begins

Status values:

  • ready — No lock held, revision number matches expectations.
  • push_in_progress — Another user holds the lock.
  • revision_conflict — Proposed revision number doesn't match latest + 1.

Required Permissions: replication-pipeline::view

get/v1/integration/advanced-dsl/projects/{projectId}/push-status

Request

  • Base URL: https://integration-adapter.connect.cloud.precisely.com
  • URL: https://integration-adapter.connect.cloud.precisely.com/v1/integration/advanced-dsl/projects/{projectId}/push-status
  • Auth: HTTP bearer

Path parameters

projectIdstring required

Unique project identifier

Query parameters

proposedRevisionNumberinteger required

The revision number the client proposes to push

Response

Push status retrieved successfully

projectIdstring

The project ID (catalog asset ID)

proposedRevisionNumberinteger

The proposed revision number provided by the caller

latestRevisionIdstring

Catalog asset ID of the latest DISDSLRevision, or null if none

latestRevisionNumberinteger

The latest revision number on the server

canPushboolean

Whether the caller can proceed with a push at this moment

reason'ready' | 'revision_conflict' | 'push_in_progress'

Reason for the readiness state

Example response

{
  "projectId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "proposedRevisionNumber": 4,
  "latestRevisionId": "rev-latest-xyz",
  "latestRevisionNumber": 3,
  "canPush": true,
  "reason": "ready",
  "reservation": {
    "reservationId": "res-uuid-12345",
    "state": "in_progress",
    "owner": "jane.doe@example.com",
    "expiresAt": "2026-05-18T12:05:00Z",
    "retryAfterSeconds": 30
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.