Skip to content

Manifest schemas

This page collects public manifest schema entrypoints. Use it when configuring an editor, CI validation, or generated manifests.

Public schema catalog

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

Registered schemas: 18.

Schema Kind Purpose Required fields
capability-discovery.schema.json dpone.capability-discovery.v1 dpone capability discovery v1 schema, snapshot_id, connectors, routes, recipes, issues
catalog-bundle-verification.schema.json dpone.catalog-bundle-verification.v1 dpone catalog bundle verification schema, decision, code, bundle_id, bundle_manifest_sha256, kind, publisher_id, environment, policy_fingerprint, verified_artifacts, verifier_version, verified_at, errors
catalog-bundle.schema.json dpone.catalog-bundle.v1 dpone catalog bundle schema, bundle_id, kind, publisher_id, environment, entrypoint, artifacts
catalog-trust-policy.schema.json dpone.catalog-trust-policy.v1 dpone catalog trust policy schema, policy_id, allowed_kinds, allowed_publishers, certificate_identity, certificate_oidc_issuer, trusted_root_sha256, verifier
component.schema.json dpone.component.v1 dpone declarative recipe component schema, id, version, owner, status, processes
etl-batch-manifest.schema.json dpone.batch.v1 Batch manifest: 1 YAML file defines many ETL processes via defaults + schema/table overrides. kind, schemas
etl-config.schema.json - ETL process configuration for PostgreSQL, BigQuery, and ClickHouse with incremental loading, state tracking, and Vault integration. name, source, sink
etl-flow-fragment-manifest.schema.json dpone.flow-fragment.v1 A bounded process fragment explicitly referenced by one dpone.flow.v1 folder source. kind, processes
etl-flow-manifest.schema.json dpone.flow.v1 A short editable authoring source compiled into dpone.batch.v1 on the build plane. kind, authoring, metadata
extension-check-receipt.schema.json dpone.extension-check-receipt.v1 dpone extension check receipt schema, check, subject_digest, status, producer, command
extension-conformance-request.schema.json dpone.extension-conformance-request.v1 dpone extension conformance request schema, profile, subject, evidence
extension-conformance.schema.json dpone.extension-conformance.v1 dpone extension conformance report schema, conformance_id, profile, subject, status, checks, evaluated_at
pipeline-summary.schema.json dpone.pipeline-summary.v1 dpone pipeline summary v1 schema, id, source_path, valid, operational_status, authoring_mode, recipe, processes, quality_gates, schedule, artifact_state, support, certification, next_actions, errors
profile.schema.json dpone.profile.v1 dpone declarative recipe profile schema, id, version, owner, status, values, locked_parameters
recipe-catalog.schema.json dpone.recipe-catalog.v1 dpone declarative recipe catalog schema, catalog_id, artifacts
recipe.schema.json dpone.recipe.v1 dpone declarative recipe schema, id, version, owner, status, domain, parameter_schema, override_allowlist, profiles, components
selectors.schema.json dpone.selectors.v1 dpone named workload selectors schema, selectors
test-manifest.schema.json dpone.test.v1 dpone GitOps hermetic test manifest kind, pipeline, input, expect

Editor hint:

# yaml-language-server: $schema=https://raw.githubusercontent.com/PaulKov/dpone/master/src/dpone/schema/etl-batch-manifest.schema.json

For short flow authoring:

# yaml-language-server: $schema=https://raw.githubusercontent.com/PaulKov/dpone/master/src/dpone/schema/etl-flow-manifest.schema.json

Folder fragments can opt into their narrower schema:

# yaml-language-server: $schema=https://raw.githubusercontent.com/PaulKov/dpone/master/src/dpone/schema/etl-flow-fragment-manifest.schema.json

Recipe artifacts use the same editor convention. For example:

# yaml-language-server: $schema=https://raw.githubusercontent.com/PaulKov/dpone/master/src/dpone/schema/recipe.schema.json