Certify a source profile
Add or certify source support without turning an upstream connector row into an unsupported product claim.
The typed profile says which implementation path Airlift supports. The capability registry separately proves each provider route for a source variant. Client certification then proves that path against a particular source version, workload corpus, Databricks target, and acceptance policy.
Do not update a profile's implementation routing metadata as a substitute for registry evidence. Use the capability registry to register the provider generation, delivery mode, limitations, proof, and expiry.
Developer acceptance contract
| Layer | Implement and retain | Failure behavior |
|---|---|---|
| Assessment | profiler/analyzer run, source version, accepted inventory, dependencies, exclusions, report digests | estate remains unassessed |
| Conversion | representative corpus, pinned transpiler, artifact digests, warnings/errors, residue taxonomy | object moves to rework or human lane |
| Transfer | snapshot, incremental catch-up, watermark, restart, lag, counts, cleanup | data readiness remains pending or failed |
| Validation | schema, row/data, business query and object-type scenarios from an admitted producer | object cannot be certified |
| Non-functional | workload, threshold, measured result, security checks, observation window | non-functional track remains open |
| Cutover | endpoint checkpoint, apply-once, verify, rollback/compensation rehearsal | automated cutover remains disabled |
Add a new source pack
- Add the ID to
sourceSystemSchemainpackages/airlift/src/schemas.ts. - Add a complete
SourceSystemProfilewith archetype, variants, adapter contract, and an honest initial support level. - Map applicable analyzer, profiler, converter, reconcile, managed-ingestion, API, pipeline, query-engine, or streaming boundaries; leave unavailable routes explicit.
- Populate workload surfaces, transfer strategy, validation checks, residue, modernization targets, and credential boundary.
- Add aliases only when they resolve unambiguously.
- Extend
packages/airlift/test/sources.test.ts; every generated action ID must exist in the installed governed action catalog. - Add a developer guide under
apps/docs/content/docs/sources/. - Add the pack to
source-packs-e2e.test.tsthrough the canonical registry and run the hermetic suite. - Run representative live routes and check their immutable certification manifest before changing a support level.
Use these commands during development.
fa sources --json
fa source inspect <source> --json
fa source plan <source> --variant <variant> --json
fa source certification-check source-certification.json
fa capability matrix --source <source> --variant <variant>
pnpm test:e2e:source
pnpm test:e2e:hermeticThe generated plan is deterministic and testable. Client acceptance remains governed state and must enter through Platform actions.
Connection diagnostics
Source-pack v2 connectivity and permission diagnostics, observed-state derivation, admitted recording, and verification.
SQL Server to Databricks migration
Implement SQL Server, Azure SQL, and RDS for SQL Server migrations with Lakebridge, governed Airlift actions, transfer evidence, and Databricks validation.