migration.example.yaml

# Migration profile — keys mirror the CLI flags. Every value is exactly what you
# would otherwise pass to `migrate_cli`; explicit flags override the profile.
#
#   python -m traust_engine.corpus.migrate_cli run --profile migration.yaml
#
# Relative paths resolve against this file's directory.

results-root: ./results-example # --results-root  (findings to import)
config: ./corpus-config.yaml # --config        (deployment config: trees/scope)
output: ./migration-output # --output        (base dir; plan/ and run/ subdirs)
# Layer artifacts are imported into traust_ledger in the database below, after
# artifact reconciliation. There is no separate layer destination or database.

# Where the data is taken — the destination database. `type` picks the shape;
# supply the connection info for that type.
database:
  type: postgres # postgres | sqlite
  dsn-env: TRAUST_MIGRATION_DSN # postgres: env var holding the connection string
  # dsn: postgresql://user:pass@host:5432/db   # postgres: literal (creds in file — avoid)
  # path: ./artifact-store.sqlite               # sqlite: file path (new, nonexistent)

# Filesystem findings/<product>/<repo> supplies product/ref; audit metadata supplies
# the repository URL. Missing/contradictory repository identity is rejected, not inferred
# from an external CSV inventory. The run is fresh-only (no pre-v1 in-place upgrade).
# Source files to ignore, in addition to the config's migration.exclude.
# Root-relative POSIX globs; `*` spans `/`.
exclude:
  - "_manifest/*"
  - "*/candidate.json"

# findings-db: ./reference.sqlite     # --findings-db  (optional parity snapshot)
# max-seconds: 900                     # --max-seconds  (optional time budget)