Build and Configure Mainframe Integration Projects
Push mainframe files
Executes orchestrated push for Mainframe pipeline files.
Features:
- Phase-based orchestration: preflight, upload, rename, delete, reconcile
- Preflight drift detection against expected snapshot fingerprint
- Batch upload support with conflict resolution (REPLACE_ALL, PARTIAL, FAIL)
- Returns per-phase status, counts, and final refreshed snapshot
Use Cases:
- Sync local extension edits to remote mainframe pipeline assets
- Apply selective updates/deletes after local diff planning
- Guard against stale push via drift checks before write operations
Required Permissions: replication-pipeline::create when permission harmonization is enabled; otherwise, replication-pipeline::manage.
post/v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/push
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
- Auth: HTTP bearer
Path parameters
projectIdstring required
Unique identifier of the project that owns the pipeline.
pipelineIdstring required
Unique identifier of the pipeline that will be pushed.
Query parameters
includeHiddenboolean
Include hidden/system files (e.g., .DS_Store, .env, pycache) in push preflight fingerprint evaluation and upload filtering. When false (default), hidden files are excluded from fingerprint computation and upload phases, preventing unintended sync of system/configuration files.
Response
Push orchestration executed (success/partial/failure encoded in payload status)
Example response
{
"status": "success",
"phaseResults": [
{
"success": true,
"errors": [
"Error message"
]
}
],
"totalBatches": 3,
"completedBatches": 1,
"errorMessage": "Remote drift detected"
}Changes
No recorded changes to this operation across all 1 revision of this API.