Prepare the source
A promotion starts from a published Mapping, Session or Workflow version. Select the source Tenant, Domain and Environment. Save and publish any changes to include; a local draft is outside the reviewed bundle.
Open Promote to Test from the editor or Configuration → Environment promotions. Select artifact type, published version and destination. The usual forward path is Development → Test → Production; Stage is optional when available. Copying from Production back to Development uses Fork to Development, a separate operation.
Review the bundle and its bindings
- Inspect the preview and exact published dependency chain. A Workflow includes the Sessions and Mappings it actually references; a Session includes its Mapping.
- Assign existing destination Connections. Use authorized, compatible identifiers; credentials remain in Dova Vault.
- Review applicable worker, execution profile, parameters and input/output bindings. The worker must be permitted in the destination environment’s pool.
- Check the effective plan, available DPU, concurrency and processing limits.
- Inspect differences, versions and Git provenance before continuing.
After changing version, configuration or context, generate a new preview. The server rechecks permissions, revisions and configuration during apply; an old review does not authorize a changed package.
Confirm and verify
Apply only the reviewed bundle. Production requires explicit approval and a comment, together with the necessary permissions. The operation creates separate destination definitions while preserving source versions. It does not run the pipeline or enable its schedules automatically.
In history, confirm environment, version, actor and result. Open the destination, inspect Connections and Runtime and perform an authorized manual run against test data and a test destination. In Monitor, verify consumed versions, rows and the final file before enabling a schedule.
Restore a version
Rollback is a manual operation on an earlier promoted version and its saved configuration. Review the current destination revision and confirm again; Production retains its approval requirement. Restoring definitions does not undo writes to files, databases or other external services.
Git and DevOps
Record repository, commit or tag provenance and export the manifest of an applied promotion. Dova’s promotion API supports preview and apply with authorized authentication and permissions. GitOps kit 1.1.2 exports the manifest through promotion-export; its separate definition-plan/apply flow imports only into Development, Test or Stage. Keep the manifest and digest in your review process.
This integration does not perform Git push, provider OAuth, webhooks or automatic deployments by itself. An external pipeline must configure its own permissions and deliberately invoke available operations. DovaAI can explain a failure and recommend steps, but never approves, applies, restores, configures or executes a promotion.
See environments and recovery and CLI and API.
Prepare destination Connections
Before promoting to Production, prepare target-owned Connections with valid custody and permissions. An authorized administrator can register them or change metadata with etl.connections.manage and etl.environments.production.edit. This specific authorization does not unlock Production Mapping, Session or Workflow editors. Shared or ambiguous legacy Connections stay read only.
Promotion and Fork to Development previews offer only compatible existing destination Connections. Select each replacement explicitly; passwords are not copied and secret references are not fabricated. Connection Domain and Environment remain tied to their ownership context.
GitOps kit per workspace
The GitOps kit 1.1.2 binds Tenant, Domain and Environment for queries, draft reservations, publications and leases. Use source.environment and source.domainId for exports; target.environment and bindings.domainId for imports. Defaults are Development and General; preserve state per target. See the Finance example and state recovery. Direct Production authoring requires governed promotion rather than the import command.