Update a DSL file
Updates the content and metadata of an existing DSL file asset within a project using a multipart/form-data upload.
Features
- Updates content, content-hash, size, MIME type, encoding, and phase.
- Ensures the file is linked to a revision via Includes relationship after save.
- Accepts optional revisionNumber; when omitted, links against the latest project revision.
Use Cases
- Persisting a modified DSL file during a push operation.
Scenarios
- File exists → patch content, hash, size, MIME type, encoding, and phase.
- File not yet linked to selected/latest revision → create missing Includes relationship.
- File already linked to selected/latest revision → no duplicate relationship is created.
Required Permissions: replication-pipeline::update when permission harmonization is enabled; otherwise, replication-pipeline::manage.
Request
- Base URL: https://integration-adapter.connect.cloud.precisely.com
- URL: https://integration-adapter.connect.cloud.precisely.com/v1/integration/advanced-dsl/projects/{projectId}/files/{fileId}
- Auth: HTTP bearer
Path parameters
Unique project identifier
The existing file asset ID to update
Query parameters
MIME type of the file content
Encoding applied to the content
Target lifecycle phase to apply after save
Expected current version for optimistic concurrency on existing files (optional)
Flattened path of the file within the project (e.g., pipelines/customer-sync.dis.yaml). If not provided, preserves existing path.
Optional revision number to associate the file with. If omitted, latest project revision is used.
Response
File updated successfully
Example response
{
"fileId": "file-abc123",
"name": "customer-sync.dis.yaml",
"flattenedPath": "pipelines/customer-sync.dis.yaml",
"phase": "DRAFT",
"version": 3,
"timestamp": "2026-05-17T10:00:00Z"
}Changes
No recorded changes to this operation across all 1 revision of this API.