Build and Configure Mainframe Integration Projects
Get push status for mainframe files
Computes preflight push status for a Mainframe pipeline before upload starts.
Features:
- Compares client-provided proposed snapshot fingerprint against latest remote snapshot
- Returns canPush=false with remote files payload when drift is detected
- Validates project/pipeline association before evaluation
- Hidden/system files are excluded from fingerprint evaluation by default (includeHidden=false)
- Supports fast UI preflight checks before destructive push operations
Use Cases:
- Push preflight guard before user confirms push
- Detecting server-side edits done after last pull/snapshot
- Blocking stale push operations and guiding refresh workflows
Required Permissions: replication-pipeline::view when permission harmonization is enabled; otherwise, replication-pipeline::manage.
get/v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/push-status
Request
- Base URL: https://integration-adapter.connect.cloud.precisely.com
- URL: https://integration-adapter.connect.cloud.precisely.com/v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/push-status
- Auth: HTTP bearer
Path parameters
projectIdstring required
Unique identifier of the project that owns the pipeline.
pipelineIdstring required
Unique identifier of the pipeline to evaluate for push readiness.
Query parameters
proposedSnapshotFingerprintstring required
Client-computed canonical fingerprint of the proposed snapshot baseline.
includeHiddenboolean
Include hidden/system files in push-status fingerprint evaluation
Response
Successfully computed push preflight status
Example response
{
"canPush": true,
"remoteSnapshotFingerprint": "4f3dfafda2ddf9753f6d9b7cf5f97f2c81f668f756ad0d6a4c930f725f4f3c8e"
}Changes
No recorded changes to this operation across all 1 revision of this API.