Skip to content

CLI reference

This document is intentionally concise and auto-generated from the current argparse tree. For guided workflows and examples, see CLI examples and DAG debugging.

Use:

dpone docs update-cli-reference
dpone docs update-cli-reference --check

This section is auto-generated by dpone docs update-cli-reference.

dpone doctor

dpone doctor

  • Usage: dpone doctor [--profile {local,ci,production}] [--format {text,json,md}]
  • Options:
  • --profile PROFILE
  • --format FORMAT

dpone init

dpone init

  • Usage: dpone init --source-type SOURCE_TYPE --sink-type SINK_TYPE --source-connection SOURCE_CONNECTION --sink-connection SINK_CONNECTION --source-schema SOURCE_SCHEMA --source-table SOURCE_TABLE --target-schema TARGET_SCHEMA --target-table TARGET_TABLE [--strategy STRATEGY] [--unique-key UNIQUE_KEY] --out OUT [--format {text,json,md}]
  • Options:
  • --source-type SOURCE_TYPE
  • --sink-type SINK_TYPE
  • --source-connection SOURCE_CONNECTION
  • --sink-connection SINK_CONNECTION
  • --source-schema SOURCE_SCHEMA
  • --source-table SOURCE_TABLE
  • --target-schema TARGET_SCHEMA
  • --target-table TARGET_TABLE
  • --strategy STRATEGY
  • --unique-key UNIQUE_KEY
  • --out OUT
  • --format FORMAT

dpone plan

dpone plan

  • Usage: dpone plan [--selector SELECTOR] [--apply-safe-schema] [--explain-strategy] [--format {text,json,md}] path
  • Positional arguments:
  • path
  • Options:
  • --selector SELECTOR
  • --apply-safe-schema
  • --explain-strategy
  • --format FORMAT

dpone run

dpone run

  • Usage: dpone run [--selector SELECTOR] [--run-id RUN_ID] [--dag-id DAG_ID] [--execution-date EXECUTION_DATE] [--retry-attempts RETRY_ATTEMPTS] [--retry-backoff-seconds RETRY_BACKOFF_SECONDS] [--registry REGISTRY] [--format {text,json,md}] path
  • Positional arguments:
  • path — Path to a YAML manifest
  • Options:
  • --selector SELECTOR — Process selector inside a batch manifest
  • --run-id RUN_ID — Explicit run id; defaults to process name
  • --dag-id DAG_ID
  • --execution-date EXECUTION_DATE
  • --retry-attempts RETRY_ATTEMPTS — Retry failed process results this many times
  • --retry-backoff-seconds RETRY_BACKOFF_SECONDS — Sleep between failed attempts; defaults to no backoff
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated)
  • --format FORMAT

dpone resync

dpone resync

  • Usage: dpone resync --run-id RUN_ID --source-type SOURCE_TYPE --sink-type SINK_TYPE --strategy STRATEGY [--partition PARTITION] [--artifact-dir ARTIFACT_DIR] [--yes] [--live-backend] [--connection-id CONNECTION_ID] [--connection-type {env,vault,airflow,params}] [--target-schema TARGET_SCHEMA] [--target-table TARGET_TABLE] [--staging-schema STAGING_SCHEMA] [--mount-point MOUNT_POINT] [--connection-path CONNECTION_PATH] [--format {text,json,md}]
  • Options:
  • --run-id RUN_ID
  • --source-type SOURCE_TYPE
  • --sink-type SINK_TYPE
  • --strategy STRATEGY
  • --partition PARTITION
  • --artifact-dir ARTIFACT_DIR
  • --yes — Mark replay as approved for execution
  • --live-backend — Execute through runtime SQL/Kafka replay backend when combined with --yes
  • --connection-id CONNECTION_ID — Target sink connection id used by the runtime replay backend
  • --connection-type CONNECTION_TYPE — Credential provider for --connection-id
  • --target-schema TARGET_SCHEMA — Target schema/database for DB replay backends
  • --target-table TARGET_TABLE — Target table or Kafka topic for live replay
  • --staging-schema STAGING_SCHEMA — Staging schema/database for DB replay backends
  • --mount-point MOUNT_POINT — Vault mount point when --connection-type vault is used
  • --connection-path CONNECTION_PATH — Vault path or provider-specific credential path
  • --format FORMAT

dpone resume

dpone resume

  • Usage: dpone resume [--from-stage FROM_STAGE] --source-type SOURCE_TYPE --sink-type SINK_TYPE --strategy STRATEGY [--artifact-dir ARTIFACT_DIR] [--yes] [--live-backend] [--connection-id CONNECTION_ID] [--connection-type {env,vault,airflow,params}] [--target-schema TARGET_SCHEMA] [--target-table TARGET_TABLE] [--staging-schema STAGING_SCHEMA] [--mount-point MOUNT_POINT] [--connection-path CONNECTION_PATH] [--format {text,json,md}] run_id
  • Positional arguments:
  • run_id
  • Options:
  • --from-stage FROM_STAGE
  • --source-type SOURCE_TYPE
  • --sink-type SINK_TYPE
  • --strategy STRATEGY
  • --artifact-dir ARTIFACT_DIR
  • --yes — Mark resume as approved for execution
  • --live-backend — Execute through runtime SQL/Kafka replay backend when combined with --yes
  • --connection-id CONNECTION_ID — Target sink connection id used by the runtime replay backend
  • --connection-type CONNECTION_TYPE — Credential provider for --connection-id
  • --target-schema TARGET_SCHEMA — Target schema/database for DB replay backends
  • --target-table TARGET_TABLE — Target table or Kafka topic for live replay
  • --staging-schema STAGING_SCHEMA — Staging schema/database for DB replay backends
  • --mount-point MOUNT_POINT — Vault mount point when --connection-type vault is used
  • --connection-path CONNECTION_PATH — Vault path or provider-specific credential path
  • --format FORMAT

dpone run-report

dpone run-report

  • Usage: dpone run-report --run-id RUN_ID --pipeline PIPELINE [--rows ROWS] [--out-dir OUT_DIR] [--format {text,json,md}]
  • Options:
  • --run-id RUN_ID
  • --pipeline PIPELINE
  • --rows ROWS
  • --out-dir OUT_DIR
  • --format FORMAT

dpone studio

dpone studio

  • Usage: dpone studio [--host HOST] [--port PORT] [--serve] [--format {text,json,md}]
  • Options:
  • --host HOST
  • --port PORT
  • --serve — Start the local HTTP API server and block
  • --format FORMAT

dpone certify

dpone certify

  • Usage: dpone certify [--format {markdown,json}]
  • Options:
  • --format FORMAT

dpone schema-plan

dpone schema-plan

  • Usage: dpone schema-plan --source SOURCE --target TARGET --table TABLE [--dialect {mssql,postgres,clickhouse,bigquery}] [--mode {strict,additive,widening}] [--on-type-change {fail,new_column}] [--new-column-prefix NEW_COLUMN_PREFIX] [--ddl-mode {online,safe_window,plan_only,manual_approval}] [--lock-timeout-seconds LOCK_TIMEOUT_SECONDS] [--statement-timeout-seconds STATEMENT_TIMEOUT_SECONDS] [--max-table-size-for-inline-ddl MAX_TABLE_SIZE_FOR_INLINE_DDL] [--apply-safe] [--plan-only] [--allow-drop] [--fail-on-breaking] [--format {text,json}]
  • Options:
  • --source SOURCE — Path to source columns JSON
  • --target TARGET — Path to target columns JSON
  • --table TABLE — Qualified target table, e.g. dbo.orders
  • --dialect DIALECT
  • --mode MODE
  • --on-type-change ON_TYPE_CHANGE
  • --new-column-prefix NEW_COLUMN_PREFIX
  • --ddl-mode DDL_MODE
  • --lock-timeout-seconds LOCK_TIMEOUT_SECONDS
  • --statement-timeout-seconds STATEMENT_TIMEOUT_SECONDS
  • --max-table-size-for-inline-ddl MAX_TABLE_SIZE_FOR_INLINE_DDL
  • --apply-safe — Alias for documenting runtime parity; CLI remains plan-only
  • --plan-only — Render plan without applying DDL (default CLI behavior)
  • --allow-drop
  • --fail-on-breaking
  • --format FORMAT

dpone cdc-plan

dpone cdc-plan

  • Usage: dpone cdc-plan --backend {postgres_logical,mssql_cdc,mssql_change_tracking} --schema SCHEMA --table TABLE [--slot-name SLOT_NAME] [--publication-name PUBLICATION_NAME] [--capture-instance CAPTURE_INSTANCE] [--format {text,json}]
  • Options:
  • --backend BACKEND
  • --schema SCHEMA
  • --table TABLE
  • --slot-name SLOT_NAME
  • --publication-name PUBLICATION_NAME
  • --capture-instance CAPTURE_INSTANCE
  • --format FORMAT

dpone state

dpone state inspect

  • Usage: dpone state inspect --backend {bigquery,postgres,mssql} --state-type {xmin,kafka_offsets,cdc_offsets,run_state} [--format {text,json,md}] identity
  • Positional arguments:
  • identity
  • Options:
  • --backend BACKEND
  • --state-type STATE_TYPE
  • --format FORMAT

dpone state reset

  • Usage: dpone state reset --backend {bigquery,postgres,mssql} --state-type {xmin,kafka_offsets,cdc_offsets,run_state} [--format {text,json,md}] [--yes] identity
  • Positional arguments:
  • identity
  • Options:
  • --backend BACKEND
  • --state-type STATE_TYPE
  • --format FORMAT
  • --yes

dpone state export

  • Usage: dpone state export --backend {bigquery,postgres,mssql} --state-type {xmin,kafka_offsets,cdc_offsets,run_state} [--format {text,json,md}] identity
  • Positional arguments:
  • identity
  • Options:
  • --backend BACKEND
  • --state-type STATE_TYPE
  • --format FORMAT

dpone state replay-from

  • Usage: dpone state replay-from --backend {bigquery,postgres,mssql} --state-type {xmin,kafka_offsets,cdc_offsets,run_state} [--format {text,json,md}] --offset OFFSET [--yes] identity
  • Positional arguments:
  • identity
  • Options:
  • --backend BACKEND
  • --state-type STATE_TYPE
  • --format FORMAT
  • --offset OFFSET
  • --yes

dpone state compare

  • Usage: dpone state compare --backend {bigquery,postgres,mssql} --state-type {xmin,kafka_offsets,cdc_offsets,run_state} [--format {text,json,md}] left right
  • Positional arguments:
  • left
  • right
  • Options:
  • --backend BACKEND
  • --state-type STATE_TYPE
  • --format FORMAT

dpone connectors

dpone connectors list

  • Usage: dpone connectors list [--format {text,json,md}]
  • Options:
  • --format FORMAT

dpone connectors certify

  • Usage: dpone connectors certify [--format {markdown,json}] [--artifact-dir ARTIFACT_DIR] [--fail-on-missing]
  • Options:
  • --format FORMAT
  • --artifact-dir ARTIFACT_DIR
  • --fail-on-missing

dpone connectors scaffold

  • Usage: dpone connectors scaffold [--root ROOT] [--connector-type {api,database,event,file}] [--capability {source,sink,state}] [--no-certification] [--format {text,json,md}] name
  • Positional arguments:
  • name
  • Options:
  • --root ROOT
  • --connector-type CONNECTOR_TYPE
  • --capability CAPABILITIES
  • --no-certification
  • --format FORMAT

dpone ops

dpone ops artifact-index

  • Usage: dpone ops artifact-index [--output-dir OUTPUT_DIR] [--root ROOT] [--release RELEASE] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --root ROOT
  • --release RELEASE
  • --format FORMAT

dpone ops certification-run

  • Usage: dpone ops certification-run [--artifact-dir ARTIFACT_DIR] [--source SOURCE] [--sink SINK] [--strategy STRATEGY] [--row-count ROW_COUNT] [--format {md,json}]
  • Options:
  • --artifact-dir ARTIFACT_DIR
  • --source SOURCE
  • --sink SINK
  • --strategy STRATEGY
  • --row-count ROW_COUNT
  • --format FORMAT

dpone ops certification-history

  • Usage: dpone ops certification-history [--history-dir HISTORY_DIR] --release RELEASE --current-report CURRENT_REPORT [--previous-report PREVIOUS_REPORT] [--format {md,json}]
  • Options:
  • --history-dir HISTORY_DIR
  • --release RELEASE
  • --current-report CURRENT_REPORT
  • --previous-report PREVIOUS_REPORT
  • --format FORMAT

dpone ops connector-badges

  • Usage: dpone ops connector-badges [--output-dir OUTPUT_DIR] [--history-index HISTORY_INDEX] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --history-index HISTORY_INDEX
  • --format FORMAT

dpone ops contract-check

  • Usage: dpone ops contract-check --rows-json ROWS_JSON --contract-json CONTRACT_JSON [--mode {fail,warn}] [--format {md,json}]
  • Options:
  • --rows-json ROWS_JSON
  • --contract-json CONTRACT_JSON
  • --mode MODE
  • --format FORMAT

dpone ops quarantine-export

  • Usage: dpone ops quarantine-export [--dir DIR] --run-id RUN_ID [--format {md,json}]
  • Options:
  • --dir DIR
  • --run-id RUN_ID
  • --format FORMAT

dpone ops quarantine-replay

  • Usage: dpone ops quarantine-replay [--dir DIR] --run-id RUN_ID [--yes] [--format {md,json}]
  • Options:
  • --dir DIR
  • --run-id RUN_ID
  • --yes
  • --format FORMAT

dpone ops package-start

  • Usage: dpone ops package-start [--dir DIR] --run-id RUN_ID --target TARGET [--chunk-id CHUNK_ID] [--format {md,json}]
  • Options:
  • --dir DIR
  • --run-id RUN_ID
  • --target TARGET
  • --chunk-id CHUNK_ID
  • --format FORMAT

dpone ops package-commit

  • Usage: dpone ops package-commit [--dir DIR] --load-id LOAD_ID --rows-loaded ROWS_LOADED [--state-after-json STATE_AFTER_JSON] [--format {md,json}]
  • Options:
  • --dir DIR
  • --load-id LOAD_ID
  • --rows-loaded ROWS_LOADED
  • --state-after-json STATE_AFTER_JSON
  • --format FORMAT

dpone ops rollback-plan

  • Usage: dpone ops rollback-plan --sink {mssql,postgres,clickhouse,bigquery} --target TARGET --load-id LOAD_ID [--strategy STRATEGY] [--format {md,json}]
  • Options:
  • --sink SINK
  • --target TARGET
  • --load-id LOAD_ID
  • --strategy STRATEGY
  • --format FORMAT

dpone ops rollback-apply

  • Usage: dpone ops rollback-apply --plan-json PLAN_JSON [--yes] [--format {md,json}]
  • Options:
  • --plan-json PLAN_JSON
  • --yes
  • --format FORMAT

dpone ops rollback-execute

  • Usage: dpone ops rollback-execute --sink {mssql,postgres,clickhouse,bigquery} --target TARGET --load-id LOAD_ID [--strategy STRATEGY] [--require-backup] [--yes] [--format {md,json}]
  • Options:
  • --sink SINK
  • --target TARGET
  • --load-id LOAD_ID
  • --strategy STRATEGY
  • --require-backup
  • --yes
  • --format FORMAT

dpone ops marketplace

  • Usage: dpone ops marketplace [--format {md,json}]
  • Options:
  • --format FORMAT

dpone ops evidence-bundle

  • Usage: dpone ops evidence-bundle [--artifact-dir ARTIFACT_DIR] --run-id RUN_ID --source SOURCE --sink SINK --strategy STRATEGY --rows-json ROWS_JSON --contract-json CONTRACT_JSON [--row-count ROW_COUNT] [--format {md,json}]
  • Options:
  • --artifact-dir ARTIFACT_DIR
  • --run-id RUN_ID
  • --source SOURCE
  • --sink SINK
  • --strategy STRATEGY
  • --rows-json ROWS_JSON
  • --contract-json CONTRACT_JSON
  • --row-count ROW_COUNT
  • --format FORMAT

dpone ops evidence-chain

  • Usage: dpone ops evidence-chain [--chain-dir CHAIN_DIR] --release RELEASE --artifact-index ARTIFACT_INDEX [--previous-entry PREVIOUS_ENTRY] [--format {md,json}]
  • Options:
  • --chain-dir CHAIN_DIR
  • --release RELEASE
  • --artifact-index ARTIFACT_INDEX
  • --previous-entry PREVIOUS_ENTRY
  • --format FORMAT

dpone ops evidence-chain-verify

  • Usage: dpone ops evidence-chain-verify [--chain-dir CHAIN_DIR] [--format {md,json}]
  • Options:
  • --chain-dir CHAIN_DIR
  • --format FORMAT

dpone ops go-live-gate

  • Usage: dpone ops go-live-gate --bundle-json BUNDLE_JSON [--format {md,json}]
  • Options:
  • --bundle-json BUNDLE_JSON
  • --format FORMAT

dpone ops policy-evaluate

  • Usage: dpone ops policy-evaluate --bundle-json BUNDLE_JSON --policy-json POLICY_JSON [--format {md,json}]
  • Options:
  • --bundle-json BUNDLE_JSON
  • --policy-json POLICY_JSON
  • --format FORMAT

dpone ops diff

  • Usage: dpone ops diff --source-rows-json SOURCE_ROWS_JSON --target-rows-json TARGET_ROWS_JSON --key KEY [--compare-columns COMPARE_COLUMNS] [--sample-limit SAMPLE_LIMIT] [--format {md,json}]
  • Options:
  • --source-rows-json SOURCE_ROWS_JSON
  • --target-rows-json TARGET_ROWS_JSON
  • --key KEY — Comma-separated business key columns
  • --compare-columns COMPARE_COLUMNS — Comma-separated columns to compare; defaults to all non-key columns
  • --sample-limit SAMPLE_LIMIT
  • --format FORMAT

dpone ops security-audit

  • Usage: dpone ops security-audit [--manifest-json MANIFEST_JSON] [--log-text LOG_TEXT] [--format {md,json}]
  • Options:
  • --manifest-json MANIFEST_JSON
  • --log-text LOG_TEXT
  • --format FORMAT

dpone ops slo-evaluate

  • Usage: dpone ops slo-evaluate --metrics-json METRICS_JSON --objectives-json OBJECTIVES_JSON [--format {md,json}]
  • Options:
  • --metrics-json METRICS_JSON
  • --objectives-json OBJECTIVES_JSON
  • --format FORMAT

dpone ops incident-pack

  • Usage: dpone ops incident-pack [--artifact-dir ARTIFACT_DIR] --incident-id INCIDENT_ID --title TITLE [--severity SEVERITY] [--artifact ARTIFACT] [--format {md,json}]
  • Options:
  • --artifact-dir ARTIFACT_DIR
  • --incident-id INCIDENT_ID
  • --title TITLE
  • --severity SEVERITY
  • --artifact ARTIFACT — Artifact reference as name=/path/to/file
  • --format FORMAT

dpone ops release-gate

  • Usage: dpone ops release-gate [--artifact-dir ARTIFACT_DIR] --release RELEASE [--artifact ARTIFACT] [--format {md,json}]
  • Options:
  • --artifact-dir ARTIFACT_DIR
  • --release RELEASE
  • --artifact ARTIFACT — Artifact reference as name=/path/to/file
  • --format FORMAT

dpone ops production-maturity

  • Usage: dpone ops production-maturity [--output-dir OUTPUT_DIR] --release RELEASE [--artifact ARTIFACT] [--require REQUIRE] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --release RELEASE
  • --artifact ARTIFACT — Artifact reference as name=/path/to/file
  • --require REQUIRE — Required evidence domain; can be repeated
  • --format FORMAT

dpone ops industrial-readiness

  • Usage: dpone ops industrial-readiness [--output-dir OUTPUT_DIR] --release RELEASE [--artifact ARTIFACT] [--require REQUIRE] [--case CASE] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --release RELEASE
  • --artifact ARTIFACT — Artifact reference as name=/path/to/file
  • --require REQUIRE — Required evidence domain; can be repeated
  • --case CASE — Required matrix case as source:sink:strategy; can be repeated
  • --format FORMAT

dpone ops release-summary

  • Usage: dpone ops release-summary [--output-dir OUTPUT_DIR] --release-id RELEASE_ID --replay-chain-dir REPLAY_CHAIN_DIR --matrix-suite MATRIX_SUITE --matrix-chain-dir MATRIX_CHAIN_DIR --connector-suite CONNECTOR_SUITE --connector-chain-dir CONNECTOR_CHAIN_DIR [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --release-id RELEASE_ID
  • --replay-chain-dir REPLAY_CHAIN_DIR
  • --matrix-suite MATRIX_SUITE
  • --matrix-chain-dir MATRIX_CHAIN_DIR
  • --connector-suite CONNECTOR_SUITE
  • --connector-chain-dir CONNECTOR_CHAIN_DIR
  • --format FORMAT

dpone ops release-orchestrator

  • Usage: dpone ops release-orchestrator [--output-dir OUTPUT_DIR] --release RELEASE [--root ROOT] [--artifact ARTIFACT] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --release RELEASE
  • --root ROOT
  • --artifact ARTIFACT — Artifact reference as name=/path/to/file
  • --format FORMAT

dpone ops release-promote

  • Usage: dpone ops release-promote [--output-dir OUTPUT_DIR] --release RELEASE --from-env FROM_ENV --to-env TO_ENV [--artifact ARTIFACT] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --release RELEASE
  • --from-env FROM_ENV
  • --to-env TO_ENV
  • --artifact ARTIFACT — Artifact reference as name=/path/to/file
  • --format FORMAT

dpone ops env-drift

  • Usage: dpone ops env-drift [--output-dir OUTPUT_DIR] --source-env SOURCE_ENV --target-env TARGET_ENV --source SOURCE --target TARGET [--allowlist-path ALLOWLIST_PATH] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --source-env SOURCE_ENV
  • --target-env TARGET_ENV
  • --source SOURCE
  • --target TARGET
  • --allowlist-path ALLOWLIST_PATH
  • --format FORMAT

dpone ops change-request

  • Usage: dpone ops change-request [--output-dir OUTPUT_DIR] --change-id CHANGE_ID --release RELEASE --target-env TARGET_ENV --risk-level {low,medium,high,critical} --requested-by REQUESTED_BY [--approver APPROVER] [--expires-at EXPIRES_AT] [--artifact ARTIFACT] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --change-id CHANGE_ID
  • --release RELEASE
  • --target-env TARGET_ENV
  • --risk-level RISK_LEVEL
  • --requested-by REQUESTED_BY
  • --approver APPROVER
  • --expires-at EXPIRES_AT
  • --artifact ARTIFACT — Artifact reference as name=/path/to/file
  • --format FORMAT

dpone ops approval-record

  • Usage: dpone ops approval-record [--output-dir OUTPUT_DIR] --change-request CHANGE_REQUEST --actor ACTOR --decision {approved,rejected} [--comment COMMENT] [--quorum-required QUORUM_REQUIRED] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --change-request CHANGE_REQUEST
  • --actor ACTOR
  • --decision DECISION
  • --comment COMMENT
  • --quorum-required QUORUM_REQUIRED
  • --format FORMAT

dpone ops deployment-record

  • Usage: dpone ops deployment-record [--output-dir OUTPUT_DIR] --deployment-id DEPLOYMENT_ID --environment ENVIRONMENT --actor ACTOR --approval-record APPROVAL_RECORD --status {succeeded,completed,failed,partial} [--post-check POST_CHECK] [--rollback-artifact ROLLBACK_ARTIFACT] [--started-at STARTED_AT] [--finished-at FINISHED_AT] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --deployment-id DEPLOYMENT_ID
  • --environment ENVIRONMENT
  • --actor ACTOR
  • --approval-record APPROVAL_RECORD
  • --status STATUS
  • --post-check POST_CHECK — Post-deploy check as name=true|false
  • --rollback-artifact ROLLBACK_ARTIFACT
  • --started-at STARTED_AT
  • --finished-at FINISHED_AT
  • --format FORMAT

dpone ops post-deploy-verify

  • Usage: dpone ops post-deploy-verify [--output-dir OUTPUT_DIR] --deployment-record DEPLOYMENT_RECORD [--artifact ARTIFACT] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --deployment-record DEPLOYMENT_RECORD
  • --artifact ARTIFACT — Artifact reference as name=/path/to/file
  • --format FORMAT

dpone ops release-close

  • Usage: dpone ops release-close [--output-dir OUTPUT_DIR] --release RELEASE --closed-by CLOSED_BY --post-deploy-verify POST_DEPLOY_VERIFY [--notes NOTES] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --release RELEASE
  • --closed-by CLOSED_BY
  • --post-deploy-verify POST_DEPLOY_VERIFY
  • --notes NOTES
  • --format FORMAT

dpone ops docs-publish-pack

  • Usage: dpone ops docs-publish-pack [--output-dir OUTPUT_DIR] --release RELEASE [--artifact ARTIFACT] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --release RELEASE
  • --artifact ARTIFACT — Artifact reference as name=/path/to/file
  • --format FORMAT

dpone ops manifest-bundle

  • Usage: dpone ops manifest-bundle [--output-dir OUTPUT_DIR] --bundle-id BUNDLE_ID [--file FILE] [--redact] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --bundle-id BUNDLE_ID
  • --file FILE — File reference as name=/path/to/file
  • --redact
  • --format FORMAT

dpone ops runbook-pack

  • Usage: dpone ops runbook-pack [--output-dir OUTPUT_DIR] --runbook-id RUNBOOK_ID --title TITLE [--artifact ARTIFACT] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --runbook-id RUNBOOK_ID
  • --title TITLE
  • --artifact ARTIFACT — Artifact reference as name=/path/to/file
  • --format FORMAT

dpone ops run-registry

  • Usage: dpone ops run-registry [--output-dir OUTPUT_DIR] --run-result RUN_RESULT [--artifact ARTIFACT] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --run-result RUN_RESULT
  • --artifact ARTIFACT — Artifact reference as name=/path/to/file
  • --format FORMAT

dpone ops lineage-export

  • Usage: dpone ops lineage-export [--output-dir OUTPUT_DIR] --run-registry-entry RUN_REGISTRY_ENTRY [--namespace NAMESPACE] [--input INPUT] [--output OUTPUT] [--event-type {auto,START,COMPLETE,FAIL}] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --run-registry-entry RUN_REGISTRY_ENTRY
  • --namespace NAMESPACE
  • --input INPUT — Input dataset as namespace=name
  • --output OUTPUT — Output dataset as namespace=name
  • --event-type EVENT_TYPE
  • --format FORMAT

dpone ops benchmark-baseline

  • Usage: dpone ops benchmark-baseline [--output-dir OUTPUT_DIR] --metrics-json METRICS_JSON --baseline-json BASELINE_JSON [--allowed-regression-ratio ALLOWED_REGRESSION_RATIO] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --metrics-json METRICS_JSON
  • --baseline-json BASELINE_JSON
  • --allowed-regression-ratio ALLOWED_REGRESSION_RATIO
  • --format FORMAT

dpone ops certification-automation-plan

  • Usage: dpone ops certification-automation-plan [--output-dir OUTPUT_DIR] [--profile {mock_contract,mock_local,vendor_live}] [--row-count ROW_COUNT] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --profile PROFILE
  • --row-count ROW_COUNT
  • --format FORMAT

dpone ops dbt-lineage

  • Usage: dpone ops dbt-lineage [--output-dir OUTPUT_DIR] --manifest MANIFEST [--run-results RUN_RESULTS] [--run-registry-entry RUN_REGISTRY_ENTRY] [--namespace NAMESPACE] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --manifest MANIFEST — Path to dbt target/manifest.json
  • --run-results RUN_RESULTS — Path to dbt target/run_results.json
  • --run-registry-entry RUN_REGISTRY_ENTRY — Optional dpone run registry entry JSON
  • --namespace NAMESPACE
  • --format FORMAT

dpone ops integration-matrix-report

  • Usage: dpone ops integration-matrix-report --artifact-dir ARTIFACT_DIR --output-dir OUTPUT_DIR [--format {md,json}]
  • Options:
  • --artifact-dir ARTIFACT_DIR
  • --output-dir OUTPUT_DIR
  • --format FORMAT

dpone ops certification-suite

  • Usage: dpone ops certification-suite [--output-dir OUTPUT_DIR] --suite-id SUITE_ID --certification-report CERTIFICATION_REPORT [--benchmark-baseline BENCHMARK_BASELINE] [--lineage-report LINEAGE_REPORT] [--dbt-lineage-report DBT_LINEAGE_REPORT] [--evidence-bundle EVIDENCE_BUNDLE] [--strategy-certification-bundle STRATEGY_CERTIFICATION_BUNDLE] [--require-benchmark] [--require-lineage] [--require-dbt-lineage] [--require-evidence] [--require-strategy-certification] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --suite-id SUITE_ID
  • --certification-report CERTIFICATION_REPORT
  • --benchmark-baseline BENCHMARK_BASELINE
  • --lineage-report LINEAGE_REPORT
  • --dbt-lineage-report DBT_LINEAGE_REPORT
  • --evidence-bundle EVIDENCE_BUNDLE
  • --strategy-certification-bundle STRATEGY_CERTIFICATION_BUNDLE
  • --require-benchmark
  • --require-lineage
  • --require-dbt-lineage
  • --require-evidence
  • --require-strategy-certification
  • --format FORMAT

dpone ops certification-pack

  • Usage: dpone ops certification-pack [--output-dir OUTPUT_DIR] --pack-id PACK_ID [--artifact ARTIFACT] [--require REQUIRE] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --pack-id PACK_ID
  • --artifact ARTIFACT — Artifact reference as name=/path/to/file
  • --require REQUIRE — Required evidence artifact name
  • --format FORMAT

dpone ops recovery-plan

  • Usage: dpone ops recovery-plan [--state-dir STATE_DIR] [--lock-dir LOCK_DIR] [--load-package-dir LOAD_PACKAGE_DIR] [--output-dir OUTPUT_DIR] [--format {md,json}]
  • Options:
  • --state-dir STATE_DIR
  • --lock-dir LOCK_DIR
  • --load-package-dir LOAD_PACKAGE_DIR
  • --output-dir OUTPUT_DIR
  • --format FORMAT

dpone ops reconcile

  • Usage: dpone ops reconcile [--output-dir OUTPUT_DIR] --source-rows-json SOURCE_ROWS_JSON --target-rows-json TARGET_ROWS_JSON --key KEY [--compare-columns COMPARE_COLUMNS] [--delete-column DELETE_COLUMN] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --source-rows-json SOURCE_ROWS_JSON
  • --target-rows-json TARGET_ROWS_JSON
  • --key KEY — Comma-separated key columns
  • --compare-columns COMPARE_COLUMNS — Comma-separated compare columns
  • --delete-column DELETE_COLUMN — Source delete marker/timestamp column
  • --format FORMAT

dpone ops observability-pack

  • Usage: dpone ops observability-pack [--output-dir OUTPUT_DIR] [--service-name SERVICE_NAME] [--dashboard-title DASHBOARD_TITLE] [--alert ALERT] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --service-name SERVICE_NAME
  • --dashboard-title DASHBOARD_TITLE
  • --alert ALERT — Alert threshold as metric.max=value or metric.min=value
  • --format FORMAT

dpone ops deploy-render

  • Usage: dpone ops deploy-render [--output-dir OUTPUT_DIR] --target {docker-compose,k8s-cronjob,airflow,dagster} --manifest MANIFEST [--selector SELECTOR] [--image IMAGE] [--schedule SCHEDULE] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --target TARGET
  • --manifest MANIFEST
  • --selector SELECTOR
  • --image IMAGE
  • --schedule SCHEDULE
  • --format FORMAT

dpone ops staging-evidence

  • Usage: dpone ops staging-evidence [--output-dir OUTPUT_DIR] --manifest MANIFEST --sink {mssql,postgres,clickhouse,bigquery} --target-table TARGET_TABLE [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --manifest MANIFEST — Path to object storage staging manifest JSON
  • --sink SINK
  • --target-table TARGET_TABLE
  • --format FORMAT

dpone ops catalog-publish

  • Usage: dpone ops catalog-publish [--output-dir OUTPUT_DIR] --run-registry-entry RUN_REGISTRY_ENTRY [--namespace NAMESPACE] [--input INPUT] [--output OUTPUT] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --run-registry-entry RUN_REGISTRY_ENTRY
  • --namespace NAMESPACE
  • --input INPUT — Input dataset as namespace=name
  • --output OUTPUT — Output dataset as namespace=name
  • --format FORMAT

dpone ops live-certification-plan

  • Usage: dpone ops live-certification-plan [--output-dir OUTPUT_DIR] [--profile {local_live,real_local,vendor_live}] [--row-count ROW_COUNT] [--include-vendor-live] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --profile PROFILE
  • --row-count ROW_COUNT
  • --include-vendor-live
  • --format FORMAT

dpone ops benchmark-slo-gate

  • Usage: dpone ops benchmark-slo-gate [--output-dir OUTPUT_DIR] --metrics-json METRICS_JSON --baseline-json BASELINE_JSON --objectives-json OBJECTIVES_JSON [--allowed-regression-ratio ALLOWED_REGRESSION_RATIO] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --metrics-json METRICS_JSON
  • --baseline-json BASELINE_JSON
  • --objectives-json OBJECTIVES_JSON
  • --allowed-regression-ratio ALLOWED_REGRESSION_RATIO
  • --format FORMAT

dpone ops performance-certification

  • Usage: dpone ops performance-certification [--output-dir OUTPUT_DIR] [--profile PROFILE] [--row-count ROW_COUNT] --metrics-json METRICS_JSON [--minimum-json MINIMUM_JSON] [--maximum-json MAXIMUM_JSON] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --profile PROFILE
  • --row-count ROW_COUNT
  • --metrics-json METRICS_JSON
  • --minimum-json MINIMUM_JSON
  • --maximum-json MAXIMUM_JSON
  • --format FORMAT

dpone ops live-state-reconciliation

  • Usage: dpone ops live-state-reconciliation [--output-dir OUTPUT_DIR] [--profile PROFILE] [--artifact ARTIFACT] [--require REQUIRE] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --profile PROFILE
  • --artifact ARTIFACT — Artifact reference as name=/path/to/file
  • --require REQUIRE — Required evidence artifact name
  • --format FORMAT

dpone ops release-evidence-pack

  • Usage: dpone ops release-evidence-pack [--output-dir OUTPUT_DIR] --release RELEASE [--profile PROFILE] [--artifact ARTIFACT] [--require REQUIRE] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --release RELEASE
  • --profile PROFILE
  • --artifact ARTIFACT — Artifact reference as name=/path/to/file
  • --require REQUIRE — Required evidence artifact name
  • --format FORMAT

dpone ops pre-release-checklist

  • Usage: dpone ops pre-release-checklist [--output-dir OUTPUT_DIR] --release RELEASE [--release-type {patch,minor,major}] [--check CHECK] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --release RELEASE
  • --release-type RELEASE_TYPE
  • --check CHECK — Check result as name=true|false
  • --format FORMAT

dpone orchestrate

dpone orchestrate run

  • Usage: dpone orchestrate run --manifest MANIFEST [--selector SELECTOR] [--run-id RUN_ID] [--dag-id DAG_ID] [--execution-date EXECUTION_DATE] [--retry-attempts RETRY_ATTEMPTS] [--retry-backoff-seconds RETRY_BACKOFF_SECONDS] [--concurrency-key CONCURRENCY_KEY] [--lock-dir LOCK_DIR] [--state-dir STATE_DIR] [--lock-ttl-seconds LOCK_TTL_SECONDS] [--resume-policy {fail,resume,restart}] [--output-dir OUTPUT_DIR] [--registry REGISTRY] [--format {md,json}]
  • Options:
  • --manifest MANIFEST — Path to a YAML manifest
  • --selector SELECTOR — Process selector inside a batch manifest
  • --run-id RUN_ID — Explicit run id
  • --dag-id DAG_ID
  • --execution-date EXECUTION_DATE
  • --retry-attempts RETRY_ATTEMPTS
  • --retry-backoff-seconds RETRY_BACKOFF_SECONDS
  • --concurrency-key CONCURRENCY_KEY
  • --lock-dir LOCK_DIR
  • --state-dir STATE_DIR
  • --lock-ttl-seconds LOCK_TTL_SECONDS
  • --resume-policy RESUME_POLICY
  • --output-dir OUTPUT_DIR
  • --registry REGISTRY
  • --format FORMAT

dpone observability

dpone observability metrics-export

  • Usage: dpone observability metrics-export [--output-dir OUTPUT_DIR] [--run-report RUN_REPORT] [--metric METRIC] [--label LABEL] [--resource-attr RESOURCE_ATTR] [--service-name SERVICE_NAME] [--namespace NAMESPACE] [--format {md,json}]
  • Options:
  • --output-dir OUTPUT_DIR
  • --run-report RUN_REPORT — Path to JSON output from dpone run --format json
  • --metric METRIC — Custom numeric metric as name=value; can be repeated
  • --label LABEL — Metric label as key=value; can be repeated
  • --resource-attr RESOURCE_ATTR — OpenTelemetry resource attribute as key=value; can be repeated
  • --service-name SERVICE_NAME
  • --namespace NAMESPACE
  • --format FORMAT

dpone supply-chain

dpone supply-chain attest

  • Usage: dpone supply-chain attest [--project-root PROJECT_ROOT] [--output-dir OUTPUT_DIR] --release RELEASE --subject SUBJECT --repository REPOSITORY --commit-sha COMMIT_SHA [--builder-id BUILDER_ID] [--signing-key SIGNING_KEY] [--signing-key-id SIGNING_KEY_ID] [--format {md,json}]
  • Options:
  • --project-root PROJECT_ROOT
  • --output-dir OUTPUT_DIR
  • --release RELEASE
  • --subject SUBJECT — Artifact file to include as provenance subject
  • --repository REPOSITORY
  • --commit-sha COMMIT_SHA
  • --builder-id BUILDER_ID
  • --signing-key SIGNING_KEY — Local HMAC signing key; prefer CI secret or Sigstore/GitHub attestation
  • --signing-key-id SIGNING_KEY_ID
  • --format FORMAT

dpone strategy

dpone strategy advise

  • Usage: dpone strategy advise [--estimated-rows ESTIMATED_ROWS] [--changed-percent CHANGED_PERCENT] [--delete-percent DELETE_PERCENT] [--cdc-available] [--format {text,json,md}] path
  • Positional arguments:
  • path
  • Options:
  • --estimated-rows ESTIMATED_ROWS
  • --changed-percent CHANGED_PERCENT
  • --delete-percent DELETE_PERCENT
  • --cdc-available
  • --format FORMAT

dpone strategy preflight

  • Usage: dpone strategy preflight --source-type SOURCE_TYPE --sink-type SINK_TYPE [--fail-on-missing] [--format {text,json,md}]
  • Options:
  • --source-type SOURCE_TYPE
  • --sink-type SINK_TYPE
  • --fail-on-missing
  • --format FORMAT

dpone strategy repair-plan

  • Usage: dpone strategy repair-plan --source-type SOURCE_TYPE --sink-type SINK_TYPE --strategy STRATEGY [--failed-stage FAILED_STAGE] [--partition PARTITION] [--format {text,json,md}] run_id
  • Positional arguments:
  • run_id
  • Options:
  • --source-type SOURCE_TYPE
  • --sink-type SINK_TYPE
  • --strategy STRATEGY
  • --failed-stage FAILED_STAGE
  • --partition PARTITION
  • --format FORMAT

dpone strategy certification-artifact

  • Usage: dpone strategy certification-artifact [--artifact-dir ARTIFACT_DIR] [--format {text,json,md}]
  • Options:
  • --artifact-dir ARTIFACT_DIR
  • --format FORMAT

dpone strategy certification-bundle

  • Usage: dpone strategy certification-bundle --bundle-id BUNDLE_ID [--output-dir OUTPUT_DIR] [--replay-evidence REPLAY_EVIDENCE] [--matrix-artifact MATRIX_ARTIFACT] [--connector-artifact CONNECTOR_ARTIFACT] [--benchmark-artifact BENCHMARK_ARTIFACT] [--docs-link DOCS_LINK] [--format {text,json,md}]
  • Options:
  • --bundle-id BUNDLE_ID
  • --output-dir OUTPUT_DIR
  • --replay-evidence REPLAY_EVIDENCE
  • --matrix-artifact MATRIX_ARTIFACT
  • --connector-artifact CONNECTOR_ARTIFACT
  • --benchmark-artifact BENCHMARK_ARTIFACT
  • --docs-link DOCS_LINK
  • --format FORMAT

dpone perf

dpone perf advise

  • Usage: dpone perf advise [--selector SELECTOR] [--format {text,json,md}] path
  • Positional arguments:
  • path
  • Options:
  • --selector SELECTOR
  • --format FORMAT

dpone schema

dpone schema plan

  • Usage: dpone schema plan --source SOURCE --target TARGET --table TABLE [--dialect {mssql,postgres,clickhouse,bigquery}] [--mode {strict,additive,widening}] [--on-type-change {fail,new_column}] [--new-column-prefix NEW_COLUMN_PREFIX] [--ddl-mode {online,safe_window,plan_only,manual_approval}] [--lock-timeout-seconds LOCK_TIMEOUT_SECONDS] [--statement-timeout-seconds STATEMENT_TIMEOUT_SECONDS] [--max-table-size-for-inline-ddl MAX_TABLE_SIZE_FOR_INLINE_DDL] [--apply-safe] [--plan-only] [--allow-drop] [--fail-on-breaking] [--format {text,json}]
  • Options:
  • --source SOURCE — Path to source columns JSON
  • --target TARGET — Path to target columns JSON
  • --table TABLE — Qualified target table, e.g. dbo.orders
  • --dialect DIALECT
  • --mode MODE
  • --on-type-change ON_TYPE_CHANGE
  • --new-column-prefix NEW_COLUMN_PREFIX
  • --ddl-mode DDL_MODE
  • --lock-timeout-seconds LOCK_TIMEOUT_SECONDS
  • --statement-timeout-seconds STATEMENT_TIMEOUT_SECONDS
  • --max-table-size-for-inline-ddl MAX_TABLE_SIZE_FOR_INLINE_DDL
  • --apply-safe — Alias for documenting runtime parity; CLI remains plan-only
  • --plan-only — Render plan without applying DDL (default CLI behavior)
  • --allow-drop
  • --fail-on-breaking
  • --format FORMAT

dpone schema approve

  • Usage: dpone schema approve --ledger LEDGER --approver APPROVER [--output-dir OUTPUT_DIR] [--format {text,json}]
  • Options:
  • --ledger LEDGER — Path to schema change ledger JSON
  • --approver APPROVER — Approver identifier
  • --output-dir OUTPUT_DIR
  • --format FORMAT

dpone schema infer

  • Usage: dpone schema infer [--manifest MANIFEST] [--source SOURCE] [--rows ROWS] [--format {text,json,md}]
  • Options:
  • --manifest MANIFEST — Manifest path with source.options.columns and sink options
  • --source SOURCE — Optional source columns JSON
  • --rows ROWS — Optional JSON array or JSONL row sample file
  • --format FORMAT

dpone schema physical-plan

  • Usage: dpone schema physical-plan [--manifest MANIFEST] [--source SOURCE] [--table TABLE] [--sink {mssql,postgres,clickhouse,bigquery,kafka}] [--format {text,json,md}]
  • Options:
  • --manifest MANIFEST — Manifest path with sink.options.physical_design
  • --source SOURCE — Optional source columns JSON
  • --table TABLE — Qualified target table override
  • --sink SINK — Sink override
  • --format FORMAT

dpone schema expand-contract

  • Usage: dpone schema expand-contract --source SOURCE --target TARGET --table TABLE [--dialect {mssql,postgres,clickhouse,bigquery}] [--output-dir OUTPUT_DIR] [--format {text,json}]
  • Options:
  • --source SOURCE — Path to source columns JSON
  • --target TARGET — Path to target columns JSON
  • --table TABLE — Qualified target table
  • --dialect DIALECT
  • --output-dir OUTPUT_DIR
  • --format FORMAT

dpone cdc

dpone cdc plan

  • Usage: dpone cdc plan --backend {postgres_logical,mssql_cdc,mssql_change_tracking} --schema SCHEMA --table TABLE [--slot-name SLOT_NAME] [--publication-name PUBLICATION_NAME] [--capture-instance CAPTURE_INSTANCE] [--format {text,json}]
  • Options:
  • --backend BACKEND
  • --schema SCHEMA
  • --table TABLE
  • --slot-name SLOT_NAME
  • --publication-name PUBLICATION_NAME
  • --capture-instance CAPTURE_INSTANCE
  • --format FORMAT

dpone cdc replay-plan

  • Usage: dpone cdc replay-plan --backend {postgres_logical,mssql_cdc,mssql_change_tracking} --pipeline-name PIPELINE_NAME --schema SCHEMA --table TABLE [--stored-offset STORED_OFFSET] --replay-from REPLAY_FROM [--replay-to REPLAY_TO] [--retention-min RETENTION_MIN] [--high-watermark HIGH_WATERMARK] [--artifact-uri ARTIFACT_URI] [--allow-rewind] [--format {md,json}]
  • Options:
  • --backend BACKEND
  • --pipeline-name PIPELINE_NAME
  • --schema SCHEMA
  • --table TABLE
  • --stored-offset STORED_OFFSET
  • --replay-from REPLAY_FROM
  • --replay-to REPLAY_TO
  • --retention-min RETENTION_MIN
  • --high-watermark HIGH_WATERMARK
  • --artifact-uri ARTIFACT_URI
  • --allow-rewind
  • --format FORMAT

dpone manifest

dpone manifest list

  • Usage: dpone manifest list [--recursive] [--registry REGISTRY] path
  • Positional arguments:
  • path — Path to a YAML file or a directory
  • Options:
  • --recursive — Scan directories recursively
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone manifest render

  • Usage: dpone manifest render [--selector SELECTOR] [--all] [--registry REGISTRY] path
  • Positional arguments:
  • path — Path to a YAML manifest
  • Options:
  • --selector SELECTOR — Process selector inside a batch manifest
  • --all — Render all processes (batch)
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone manifest explain

  • Usage: dpone manifest explain [--selector SELECTOR] [--why WHY] [--item-provenance] [--patches] [--patches-mode {user,all}] [--patch-from PATCH_FROM] [--patch-to PATCH_TO] [--post-parse] [--why-parsed WHY_PARSED] [--format {text,json}] [--only ONLY] [--max-lines MAX_LINES] [--max-items MAX_ITEMS] [--registry REGISTRY] path
  • Positional arguments:
  • path — Path to a YAML manifest
  • Options:
  • --selector SELECTOR — Process selector inside a batch manifest
  • --why WHY — Explain why a specific config path has its value. Supports list indices, e.g. depends_on[2]. Can be repeated.
  • --item-provenance — Show per-item provenance for list fields (depends_on, transforms).
  • --patches — Show diff-friendly deep-merge patches per layer (copy/paste friendly).
  • --patches-mode PATCHES_MODE — Which layers to include in --patches output.
  • --patch-from PATCH_FROM — Compute a single patch from a given layer snapshot to another snapshot (or final).
  • --patch-to PATCH_TO — Target layer for --patch-from (default: final compiler config).
  • --post-parse — Explain post-parse normalization (how compiled dict becomes ETLProcessConfig/LoadConfig).
  • --why-parsed WHY_PARSED — Explain why a specific normalized path has its value (post-parse). Paths are inside a normalized tree: etl., load_config., dependencies[0].path, transforms[0].name, ... Can be repeated.
  • --format FORMAT — Output format
  • --only ONLY — Show only config changes for dot-path prefix (can be repeated), e.g. --only sink.options
  • --max-lines MAX_LINES — Max number of change lines to print (text mode)
  • --max-items MAX_ITEMS — Max number of list items to print (item-level provenance)
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone manifest validate

  • Usage: dpone manifest validate [--recursive] [--profile PROFILE] [--warn-only] [--registry REGISTRY] path
  • Positional arguments:
  • path — Path to a YAML file or a directory
  • Options:
  • --recursive — Scan directories recursively
  • --profile PROFILE — Built-in validation profile (e.g. landing_raw_v1). If omitted, will use manifest.validation block if present.
  • --warn-only — Exit 0 even if there are ERROR issues
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone manifest lint-registry

  • Usage: dpone manifest lint-registry [--recursive] [--require-field REQUIRE_FIELD] [--warn-only] [--registry REGISTRY] path
  • Positional arguments:
  • path — Path to a YAML file or a directory
  • Options:
  • --recursive — Scan directories recursively
  • --require-field REQUIRE_FIELD — Registry vars that must exist for each used (src_system, src_database) pair. Can be repeated.
  • --warn-only — Exit 0 even if there are ERROR issues
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone manifest stats

  • Usage: dpone manifest stats [--recursive] [--registry REGISTRY] path
  • Positional arguments:
  • path — Directory or manifest file
  • Options:
  • --recursive — Scan directories recursively
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone manifest migrate

  • Usage: dpone manifest migrate [--out-dir OUT_DIR] [--recursive] [--group-by {dataset,task_group,dataset_task_group}] [--dry-run] [--overwrite] [--no-infer-naming] [--naming-threshold NAMING_THRESHOLD] [--convention CONVENTION] [--registry REGISTRY] src
  • Positional arguments:
  • src — Source directory (legacy manifests) or a single YAML file
  • Options:
  • --out-dir OUT_DIR — Output directory for batch manifests (default: src dir)
  • --recursive — Scan directories recursively
  • --group-by GROUP_BY — Grouping strategy for batch manifests
  • --dry-run — Plan only; do not write files
  • --overwrite — Overwrite output files if they already exist
  • --no-infer-naming — Disable naming template inference
  • --naming-threshold NAMING_THRESHOLD — Min fraction of tables matching a pattern to enable naming templates (0..1)
  • --convention CONVENTION — Add convention: to generated batch manifests (e.g. landing_raw_v1). Convention provides default naming/metadata/validation; user config wins.
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone manifest verify

  • Usage: dpone manifest verify --batch-dir BATCH_DIR [--recursive] [--group-by {dataset,task_group,dataset_task_group}] [--ignore-depends] [--ignore IGNORE] [--max-diffs MAX_DIFFS] [--out-json OUT_JSON] [--warn-only] [--registry REGISTRY] legacy
  • Positional arguments:
  • legacy — Legacy directory (or file) with single manifests
  • Options:
  • --batch-dir BATCH_DIR — Directory containing generated batch manifests
  • --recursive — Scan legacy directories recursively
  • --group-by GROUP_BY — Grouping strategy used during migration (must match)
  • --ignore-depends — Do not compare depends_on (useful if you rewrite dependencies manually)
  • --ignore IGNORE — Ignore a dot-path during comparison (can be repeated), e.g. --ignore sink.options
  • --max-diffs MAX_DIFFS — Max number of diffs to print per mismatched process
  • --out-json OUT_JSON — Write full report to a JSON file (useful for CI artifacts)
  • --warn-only — Exit 0 even if verification finds mismatches
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone dag

dpone dag explain-edge

  • Usage: dpone dag explain-edge --from UPSTREAM --to DOWNSTREAM [--base-path BASE_PATH] [--path] [--explain-path] [--path-view {edges,grouped}] [--path-output {compact,full}] [--max-triggers MAX_TRIGGERS] [--format {text,json}] [--registry REGISTRY] root
  • Positional arguments:
  • root — Root manifest (same entrypoint you pass to DAG builder). If no extension, .yaml is assumed.
  • Options:
  • --from UPSTREAM — Upstream task: task_id or file.yaml#selector
  • --to DOWNSTREAM — Downstream task: task_id or file.yaml#selector
  • --base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
  • --path — If there is no direct edge, try to find and print a shortest path A ~> B.
  • --explain-path — With --path: also explain every edge along the found path.
  • --path-view PATH_VIEW — How to present path explanations when --explain-path is enabled.
  • --path-output PATH_OUTPUT — Level of detail for each edge explanation along the path.
  • --max-triggers MAX_TRIGGERS — Max trigger tasks to print for group-to-group reasons.
  • --format FORMAT — Output format
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone dag explain-edge-e2e

  • Usage: dpone dag explain-edge-e2e --from UPSTREAM --to DOWNSTREAM [--base-path BASE_PATH] [--max-triggers MAX_TRIGGERS] [--path] [--explain-path] [--path-view {edges,grouped}] [--path-output {compact,full}] [--format {text,json}] [--registry REGISTRY] root
  • Positional arguments:
  • root — Root manifest (same entrypoint you pass to DAG builder). If no extension, .yaml is assumed.
  • Options:
  • --from UPSTREAM — Upstream task: task_id or file.yaml#selector
  • --to DOWNSTREAM — Downstream task: task_id or file.yaml#selector
  • --base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
  • --max-triggers MAX_TRIGGERS — Max trigger tasks to print for group-to-group attributions.
  • --path — If there is no direct edge, try to find and print a shortest path A ~> B.
  • --explain-path — With --path (or when used alone): explain every edge along the found shortest path end-to-end.
  • --path-view PATH_VIEW — How to present path explanations when --explain-path is enabled.
  • --path-output PATH_OUTPUT — Level of detail for each end-to-end edge explanation along the path.
  • --format FORMAT — Output format
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone dag list-edges

  • Usage: dpone dag list-edges [--base-path BASE_PATH] [--from UPSTREAM] [--to DOWNSTREAM] [--task TASK] [--group GROUP] [--file FILE] [--selector SELECTOR] [--with-refs] [--with-files] [--with-groups] [--with-reasons] [--max MAX_EDGES] [--max-triggers MAX_TRIGGERS] [--format {text,json}] [--registry REGISTRY] root
  • Positional arguments:
  • root — Root manifest (same entrypoint you pass to DAG builder). If no extension, .yaml is assumed.
  • Options:
  • --base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
  • --from UPSTREAM — Filter: upstream task token (task_id, #selector, file.yaml#selector)
  • --to DOWNSTREAM — Filter: downstream task token (task_id, #selector, file.yaml#selector)
  • --task TASK — Filter: include only edges touching this task token (can be repeated)
  • --group GROUP — Filter: include only edges touching this task_group (can be repeated)
  • --file FILE — Filter: include only edges touching a YAML file (absolute or relative; can be repeated)
  • --selector SELECTOR — Filter: include only edges touching this selector (can be repeated)
  • --with-refs — Include node refs (file.yaml#selector) for copy/paste into explain-edge
  • --with-files — Include node config_path filenames
  • --with-groups — Include upstream/downstream task_group columns
  • --with-reasons — Include reason kinds for each printed edge (slower for large graphs)
  • --max MAX_EDGES — Max number of edges to print (after filtering)
  • --max-triggers MAX_TRIGGERS — Max trigger tasks to attribute for group-to-group reasons (when --with-reasons)
  • --format FORMAT — Output format
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone dag explain-node

  • Usage: dpone dag explain-node [--direction {in,out,both}] [--output {compact,full}] [--max-in MAX_IN] [--max-out MAX_OUT] [--max-triggers MAX_TRIGGERS] [--base-path BASE_PATH] [--format {text,json}] [--registry REGISTRY] root task
  • Positional arguments:
  • root — Root manifest (same entrypoint you pass to DAG builder). If no extension, .yaml is assumed.
  • task — Task token (task_id, #selector, file.yaml#selector)
  • Options:
  • --direction DIRECTION — Which edges to show.
  • --output OUTPUT — Compact table or full edge-by-edge explanations.
  • --max-in MAX_IN — Max incoming edges
  • --max-out MAX_OUT — Max outgoing edges
  • --max-triggers MAX_TRIGGERS — Max trigger tasks to print for group-to-group reasons.
  • --base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
  • --format FORMAT — Output format
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone dag explain-node-e2e

  • Usage: dpone dag explain-node-e2e [--focus-peer FOCUS_PEER] [--direction {in,out,both}] [--output {compact,full}] [--max-in MAX_IN] [--max-out MAX_OUT] [--max-triggers MAX_TRIGGERS] [--base-path BASE_PATH] [--format {text,json}] [--registry REGISTRY] root task
  • Positional arguments:
  • root — Root manifest (same entrypoint you pass to DAG builder). If no extension, .yaml is assumed.
  • task — Task token (task_id, #selector, file.yaml#selector)
  • Options:
  • --focus-peer FOCUS_PEER — Limit end-to-end details to edges between the node and this peer (token).
  • --direction DIRECTION — Which edges to show.
  • --output OUTPUT — Compact table or full edge-by-edge explanations.
  • --max-in MAX_IN — Max incoming edges
  • --max-out MAX_OUT — Max outgoing edges
  • --max-triggers MAX_TRIGGERS — Max trigger tasks to print for group-to-group reasons.
  • --base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
  • --format FORMAT — Output format
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone dag subgraph

  • Usage: dpone dag subgraph --from UPSTREAM --to DOWNSTREAM [--all-shortest] [--max-edges MAX_EDGES] [--max-triggers MAX_TRIGGERS] [--with-reasons] [--with-evidence] [--base-path BASE_PATH] [--format {text,json,dot,mermaid}] [--registry REGISTRY] root
  • Positional arguments:
  • root — Root manifest (same entrypoint you pass to DAG builder). If no extension, .yaml is assumed.
  • Options:
  • --from UPSTREAM — Upstream task: task_id, selector, #selector, file.yaml#selector
  • --to DOWNSTREAM — Downstream task: task_id, selector, #selector, file.yaml#selector
  • --all-shortest — Use the union of all shortest paths (can include more nodes/edges than a single path).
  • --max-edges MAX_EDGES — Safety limit: max edges to include in subgraph.
  • --max-triggers MAX_TRIGGERS — Max trigger tasks to print for group-to-group reasons (when reasons are enabled).
  • --with-reasons — Attach reason kinds to edges.
  • --with-evidence — Include full reason evidence blocks (text/json).
  • --base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
  • --format FORMAT — Output format: text/json for inspection, dot/mermaid for visualization.
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone dag report

  • Usage: dpone dag report [--base-path BASE_PATH] [--preset {default,ci,debug,debug-lite}] [--format {md,json,both}] [--out-json OUT_JSON] [--out-md OUT_MD] [--max-edges MAX_EDGES] [--md-max-edges MD_MAX_EDGES] [--include-evidence | --no-evidence] [--max-triggers MAX_TRIGGERS] [--registry-require-field REGISTRY_REQUIRE_FIELD] [--profile PROFILE] [--no-lint] [--fail-on {none,lint_errors,anomalies,both}] [--fail-severity {ERROR,WARNING}] [--registry REGISTRY] root
  • Positional arguments:
  • root — Root manifest (same entrypoint you pass to DAG builder). If no extension, .yaml is assumed.
  • Options:
  • --base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
  • --preset PRESET — Report preset. 'ci' uses safe defaults for CI artifacts (e.g., max-edges=500, no evidence). 'debug' includes evidence and disables truncation by default (max-edges=0, md-max-edges=0). 'debug-lite' includes evidence but keeps safe truncation defaults (max-edges=500, md-max-edges=200). Explicit CLI args override preset values.
  • --format FORMAT — Output format. 'both' emits Markdown + embedded JSON (or writes to --out-* files).
  • --out-json OUT_JSON — Write JSON report to this file (optional).
  • --out-md OUT_MD — Write Markdown report to this file (optional).
  • --max-edges MAX_EDGES — Safety limit: max edges to include in the report (defaults: preset/2000).
  • --md-max-edges MD_MAX_EDGES — Max edges to print in Markdown output (defaults: preset/200).
  • --include-evidence — Include full reasons evidence for edges (report can be large).
  • --no-evidence — Do not include full reasons evidence for edges (overrides preset).
  • --max-triggers MAX_TRIGGERS — Max trigger tasks to include for group-to-group reasons evidence (defaults: preset/10).
  • --registry-require-field REGISTRY_REQUIRE_FIELD — Registry required field for dag report lint (can be repeated). Default: host,type. Use 'none' to disable required-field checks.
  • --profile PROFILE — Validation profile name for manifest validation (overrides per-manifest validation blocks).
  • --no-lint — Skip lint section (manifest validation / registry lint / dependency checks).
  • --fail-on FAIL_ON — Exit with code 1 if the generated report contains issues at or above --fail-severity. lint_errors: any lint issue; anomalies: any anomaly; both: either lint_errors or anomalies; none: always exit 0 (default).
  • --fail-severity FAIL_SEVERITY — Minimum severity threshold for --fail-on. ERROR (default) fails only on ERROR; WARNING fails on WARNING or ERROR.
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone dag explain-deps

  • Usage: dpone dag explain-deps --for TASK [--index INDEX] [--no-inherited-groups] [--max-upstreams MAX_UPSTREAMS] [--max-triggers MAX_TRIGGERS] [--base-path BASE_PATH] [--format {text,json}] [--registry REGISTRY] root
  • Positional arguments:
  • root — Root manifest (same entrypoint you pass to DAG builder). If no extension, .yaml is assumed.
  • Options:
  • --for TASK — Downstream task token to explain: task_id, selector, #selector, file.yaml#selector
  • --index INDEX — Explain only depends_on item with this index (0-based). Can be repeated.
  • --no-inherited-groups — Do not include inherited TaskGroup group-to-group dependencies affecting the task.
  • --max-upstreams MAX_UPSTREAMS — Max upstream tasks to print per dependency.
  • --max-triggers MAX_TRIGGERS — Max trigger tasks to inspect/print for group-to-group dependencies.
  • --base-path BASE_PATH — Manifest directory (defaults to MANIFEST_DIR). Used for resolving relative root and refs.
  • --format FORMAT — Output format
  • --registry REGISTRY — Path to a sources registry YAML (can be repeated). Registry provides default vars like host/type for naming/metadata conventions.

dpone docs

dpone docs update-dev-metrics

  • Usage: dpone docs update-dev-metrics [--check] [--target {all,md,quality}] [--docs-dir DOCS_DIR] [--top TOP]
  • Options:
  • --check — Only check that docs are up-to-date (do not rewrite). Exit!=0 if differs.
  • --target TARGET — Which docs to update/check: all (default) | md | quality
  • --docs-dir DOCS_DIR — Docs dir in the repository (default: docs)
  • --top TOP — How many largest modules to show (default: 15)

dpone docs update-cli-reference

  • Usage: dpone docs update-cli-reference [--check] [--doc DOC]
  • Options:
  • --check — Only check that CLI reference is up-to-date.
  • --doc DOC — Target markdown file (default: docs/cli-reference.md)

dpone docs update-deprecation-roadmap

  • Usage: dpone docs update-deprecation-roadmap [--check] [--registry REGISTRY] [--doc DOC] [--package PACKAGE] [--top-sources TOP_SOURCES]
  • Options:
  • --check — Only check that the roadmap doc is up-to-date.
  • --registry REGISTRY — Compatibility registry yaml file
  • --doc DOC — Target markdown file
  • --package PACKAGE — Package root to scan for internal imports
  • --top-sources TOP_SOURCES — How many canonical source modules to show per blocked entry

dpone docs update-shim-removal-plan

  • Usage: dpone docs update-shim-removal-plan [--check] [--registry REGISTRY] [--doc DOC] [--package PACKAGE] [--batch BATCH]
  • Options:
  • --check — Only check that the shim removal plan is up-to-date.
  • --registry REGISTRY — Compatibility registry path
  • --doc DOC — Target markdown file
  • --package PACKAGE — Package directory (default: src/dpone)
  • --batch BATCH — Removal batch to render (default: cleanup-release-1)

dpone docs check-docs

  • Usage: dpone docs check-docs [--format {text,json}] [--docs-dir DOCS_DIR] [--no-root-readme]
  • Options:
  • --format FORMAT — Output format: text (default) or json
  • --docs-dir DOCS_DIR — Docs directory relative to repo root (default: docs)
  • --no-root-readme — Do not include top-level README.md in docs checks

dpone docs check-compatibility

  • Usage: dpone docs check-compatibility [--format {text,json}] [--registry REGISTRY] [--doc DOC] [--package PACKAGE] [--write-doc]
  • Options:
  • --format FORMAT — Output format: text (default) or json
  • --registry REGISTRY — Compatibility registry path relative to repo root
  • --doc DOC — Compatibility markdown page to validate/update
  • --package PACKAGE — Package directory relative to repo root (default: src/dpone)
  • --write-doc — Update generated compatibility matrix block inside docs/compatibility.md

dpone docs check-import-rules

  • Usage: dpone docs check-import-rules [--format {text,json}] [--package PACKAGE]
  • Options:
  • --format FORMAT — Output format: text (default) or json
  • --package PACKAGE — Package directory relative to repo root (default: src/dpone)

dpone docs check-layer-metrics

  • Usage: dpone docs check-layer-metrics [--format {text,json}] [--package PACKAGE] [--top TOP] [--exclude-layer EXCLUDE_LAYER] [--baseline BASELINE | --no-baseline] [--write-baseline] [--min-intra-layer-ratio MIN_INTRA_LAYER_RATIO] [--max-cross-layer-ratio MAX_CROSS_LAYER_RATIO] [--max-top-cross-layer-flow MAX_TOP_CROSS_LAYER_FLOW] [--allowed-ratio-regression ALLOWED_RATIO_REGRESSION] [--allowed-flow-regression ALLOWED_FLOW_REGRESSION]
  • Options:
  • --format FORMAT — Output format: text (default) or json
  • --package PACKAGE — Package directory relative to repo root (default: src/dpone)
  • --top TOP — How many top cross flows to retain in the computed snapshot (default: 15)
  • --exclude-layer EXCLUDE_LAYER — Layer to exclude from the coarse architecture view (repeatable, default: dpone.compat)
  • --baseline BASELINE — Baseline JSON path relative to repo root (default: docs/layer_metrics_baseline.json)
  • --no-baseline — Do not compare against a baseline JSON snapshot
  • --write-baseline — Write current layer metrics snapshot to --baseline and exit 0
  • --min-intra-layer-ratio MIN_INTRA_LAYER_RATIO — Fail if current intra-layer ratio is below this threshold (default: 0.55)
  • --max-cross-layer-ratio MAX_CROSS_LAYER_RATIO — Fail if current cross-layer ratio is above this threshold (default: 0.45)
  • --max-top-cross-layer-flow MAX_TOP_CROSS_LAYER_FLOW — Optional absolute cap for the largest layer->layer flow
  • --allowed-ratio-regression ALLOWED_RATIO_REGRESSION — Allowed regression vs baseline for ratio metrics (default: 0.02)
  • --allowed-flow-regression ALLOWED_FLOW_REGRESSION — Allowed regression vs baseline for largest cross-layer flow (default: 5)

dpone docs check-architecture-fitness

  • Usage: dpone docs check-architecture-fitness [--format {text,json}] [--package PACKAGE] [--top TOP] [--target-avg-clustering TARGET_AVG_CLUSTERING] [--max-avg-clustering MAX_AVG_CLUSTERING] [--max-cross-layer-ratio MAX_CROSS_LAYER_RATIO] [--target-module-ce TARGET_MODULE_CE] [--max-module-ce MAX_MODULE_CE] [--max-class-methods MAX_CLASS_METHODS] [--max-class-loc MAX_CLASS_LOC] [--fail-on-class-warnings]
  • Options:
  • --format FORMAT
  • --package PACKAGE
  • --top TOP
  • --target-avg-clustering TARGET_AVG_CLUSTERING
  • --max-avg-clustering MAX_AVG_CLUSTERING
  • --max-cross-layer-ratio MAX_CROSS_LAYER_RATIO
  • --target-module-ce TARGET_MODULE_CE
  • --max-module-ce MAX_MODULE_CE
  • --max-class-methods MAX_CLASS_METHODS
  • --max-class-loc MAX_CLASS_LOC
  • --fail-on-class-warnings — Treat high-responsibility class findings as errors instead of warnings.

dpone docs check-module-size

  • Usage: dpone docs check-module-size [--format {text,json}] [--package PACKAGE] [--baseline BASELINE | --no-baseline] [--write-baseline] [--warn-lines WARN_LINES] [--max-lines MAX_LINES]
  • Options:
  • --format FORMAT
  • --package PACKAGE
  • --baseline BASELINE
  • --no-baseline
  • --write-baseline
  • --warn-lines WARN_LINES
  • --max-lines MAX_LINES

dpone docs check-removal-readiness

  • Usage: dpone docs check-removal-readiness [--format {text,json}] [--registry REGISTRY] [--doc DOC] [--package PACKAGE] [--batch BATCH] [--write-doc]
  • Options:
  • --format FORMAT — Output format
  • --registry REGISTRY — Compatibility registry path
  • --doc DOC — Shim removal plan markdown path
  • --package PACKAGE — Package directory (default: src/dpone)
  • --batch BATCH — Removal batch to validate (default: cleanup-release-1)
  • --write-doc — Update docs/shim-removal-plan.md before validation

Kafka manifests

Kafka uses the same manifest commands as other backends. Use source.type: kafka for bounded batch topic reads and sink.type: kafka for producing rows into topics. See Kafka batch source/sink for options and examples.

Live replay backend mode

dpone resync and dpone resume are safe artifact-only commands by default. Add --live-backend together with --yes to execute through runtime replay backends built by RuntimeReplayBackendFactory.

MSSQL/Postgres/ClickHouse/BigQuery example:

dpone resync \
  --run-id 01JREPLAY000000000000000101 \
  --source-type postgres \
  --sink-type mssql \
  --strategy incremental_merge \
  --partition 2026-06-05 \
  --yes \
  --live-backend \
  --connection-type env \
  --connection-id mssql_dwh \
  --target-schema dbo \
  --target-table orders \
  --staging-schema staging

Kafka example:

dpone resume 01JREPLAY000000000000000102 \
  --from-stage finalize \
  --source-type postgres \
  --sink-type kafka \
  --strategy incremental_merge \
  --yes \
  --live-backend \
  --connection-type params \
  --connection-id '{"bootstrap_servers":"localhost:9092"}' \
  --target-table dwh.orders

Live replay flags:

Flag Purpose
--live-backend Opt into runtime SQL/Kafka backend execution. Without --yes, no live backend is built.
--connection-id Target sink connection id or params JSON. Required with --live-backend.
--connection-type Credential provider: env, vault, airflow, or params.
--target-schema Target schema/database for DB sinks. Defaults to public.
--target-table Target table for DB sinks or Kafka topic for Kafka. Required with --live-backend.
--staging-schema Staging schema/database for DB sinks. Defaults to staging.
--mount-point Vault mount point when --connection-type vault is used.
--connection-path Vault path or provider-specific credential path.

dpone strategy certification-bundle

Aggregate strategy certification evidence into one JSON/Markdown bundle.

dpone strategy certification-bundle \
  --bundle-id oss_rc_2026_06_05 \
  --output-dir test_artifacts/strategies/certification_bundle \
  --replay-evidence test_artifacts/replay_integration/resync_01_evidence.json \
  --matrix-artifact test_artifacts/integration_matrix/certification_report.json \
  --connector-artifact test_artifacts/connectors/connector_certification.json \
  --benchmark-artifact test_artifacts/benchmarks/benchmark_baseline.json \
  --docs-link docs/testing/replay-integration.md \
  --format json
Flag Purpose
--bundle-id Stable release, certification, or audit id. Required.
--output-dir Directory for strategy_certification_bundle.json and .md.
--replay-evidence Replay evidence JSON. Can be repeated.
--matrix-artifact Source -> sink matrix or certification report JSON. Can be repeated.
--connector-artifact Connector certification JSON. Can be repeated.
--benchmark-artifact Benchmark baseline/regression JSON. Can be repeated.
--docs-link Relevant runbook or evidence docs link. Can be repeated.

dpone ops release-summary

Build the final replay + matrix + connector release go/no-go report.

dpone ops release-summary \
  --output-dir test_artifacts/certification/release-summary \
  --release-id v0.7.1 \
  --replay-chain-dir test_artifacts/replay-evidence-chain \
  --matrix-suite test_artifacts/source-sink-certification-suite/certification_suite.json \
  --matrix-chain-dir test_artifacts/source-sink-evidence-chain \
  --connector-suite test_artifacts/connector-certification-suite/certification_suite.json \
  --connector-chain-dir test_artifacts/connector-evidence-chain \
  --format json

Required inputs:

  • --release-id: release, RC, or promotion identifier.
  • --replay-chain-dir: directory containing evidence_chain_index.json and replay chain entries.
  • --matrix-suite: source -> sink certification_suite.json.
  • --matrix-chain-dir: source -> sink evidence chain directory.
  • --connector-suite: connector certification_suite.json.
  • --connector-chain-dir: connector evidence chain directory.

Exit code 0 means all chains verify and all suites pass. Exit code 1 means the release remains blocked.

dpone ops certification-automation-plan

Render the full source -> sink certification automation plan and required artifacts.

dpone ops certification-automation-plan \
  --output-dir test_artifacts/full_certification/automation \
  --profile mock_contract \
  --row-count 10000 \
  --format json

Options:

  • --output-dir: where certification_automation_plan.json and .md are written.
  • --profile: mock_contract, mock_local, or vendor_live.
  • --row-count: mock matrix row count, capped by the service at 100000.
  • --format: md or json.

Use this before changing .github/workflows/full-certification.yml so command order, required artifacts, docs, and runbooks remain aligned.

dpone normalize

Preview and infer nested normalization output from local row samples. This is a plan-only/self-service command: it does not connect to source systems and does not write target data.

dpone normalize preview

dpone normalize preview \
  --sample examples/nested/orders.jsonl \
  --root-table orders \
  --config examples/nested/normalization.yml \
  --format md \
  --output .dpone/normalization-preview.md

Options:

Option Description
--sample Local JSON, JSONL/NDJSON, CSV, or TSV sample file.
--root-table Root normalized table name.
--config Optional normalization config JSON/YAML file.
--nested-level Override normalization.nested.nested_level.
--limit Maximum sample rows to read; default 1000.
--format text, json, or md; default text.
--output Optional output file path.

dpone normalize infer

dpone normalize infer \
  --sample examples/nested/orders.jsonl \
  --root-table orders \
  --nested-level 3 \
  --format json

Use infer when the output will be stored as GitOps evidence or reviewed in a pull request. See Nested normalization for policies, raw landing, guardrails, hierarchy contracts, and reverse hierarchy checks.

dpone normalize lint

dpone normalize lint \
  --root-table orders \
  --config examples/nested/normalization.yml \
  --format md \
  --output .dpone/nested-lint.md \
  --fail-on-error

Checks nested configuration for table collisions, missing explosion guardrails, and rollout risks before a manifest is enabled in production.

dpone normalize certify

dpone normalize certify \
  --row-count 1000 \
  --output-dir test_artifacts/nested/latest

Writes JSON and Markdown certification evidence covering lint, spill-to-disk, reverse readback, child finalizers, snapshot stores, schema-evolution contract, native fast-path execution contract, live harness contract, quarantine and raw landing.

dpone normalize benchmark

dpone normalize benchmark \
  --row-count 10000 \
  --max-rows 100000 \
  --output-dir test_artifacts/nested/benchmark-latest

Runs a deterministic local benchmark and writes throughput/row-count evidence.

dpone normalize stress

dpone normalize stress \
  --row-count 100000 \
  --max-rows 100000 \
  --spill-output-format json_each_row \
  --output-dir test_artifacts/nested/stress-latest

Runs skewed nested payload certification with sparse nested objects and child array sizes such as 0, 1, 10 and 1000 rows per parent.