Product
PR blast-radius / impact
Preview downstream impact of pipeline spec changes in CI.
How impact works
POST /api/v1/specs/impact validates a proposed spec, diffs it against the registered catalog (or base_spec), and BFS-walks lineage for blast radius.
The response includes changed datasets, downstream nodes, consumer contracts at risk, passports at risk, and markdown ready for a PR comment.
GitHub Actions
Copy examples/github-actions/dataxpipe-spec-gate.yml or dataxpipe-impact.yml into your data repo.
Store DATAXPIPE_API_KEY as a secret for catalog-aware impact; validate alone needs no key.