PostgreSQL to Databricks

fa source inspect postgres
fa source plan postgresql --variant postgresql
fa source plan postgresql --variant aurora_postgresql --json

The pack covers PostgreSQL, Amazon Aurora PostgreSQL, and Amazon RDS for PostgreSQL. It inventories tables, schemas, views, functions, extensions, logical replication, schedulers, and application or BI consumers.

What Airlift adds

• A governed estate with the exact platform variant and opaque connection reference.
• Dependency-aware waves for tables, functions, ingestion jobs, and consumers.
• Explicit disposition of extensions, PL-language functions, cross-database access, large objects, and transactional side effects.
• Snapshot, WAL/CDC or watermark catch-up evidence with retained LSN and restart state.
• Independent checks for JSONB, arrays, collation, numeric/timestamp semantics, ordering, deletes, business queries, and accepted performance thresholds.
• Signed certificates, frozen wave scope, authenticated approvals, and a verifiable consumer cutover or rollback.

Lakeflow Connect or another admitted connector may perform movement; Airlift records what ran and what it proved. The public pack is cataloged until immutable live runs support a higher level.

Complete developer command sequence

Generate this exact recipe from the installed CLI so the guide and executable surface stay in sync:

fa source recipe postgresql
fa source recipe postgresql --variant postgresql --json > .airlift/postgresql-recipe.json

The App is engagement-aware. PostgreSQL and Aurora PostgreSQL appears under Active sources only after the source estate is added to an active engagement. The menu is derived from governed engagement scope; installing Airlift does not expose unrelated source pages.

Every remote mutation below requires --host, --org, authenticated workspace identity, and a stable --idempotency-key. JSON request files contain identifiers, artifact references, and opaque credential references—never passwords, tokens, or connection strings. Run fa <resource> <operation> --help for the current schema and exit semantics.

0. Inspect the source contract

fa source inspect postgresql --json > .airlift/postgresql-profile.json
fa source plan postgresql --variant postgresql --json > .airlift/postgresql-capability-plan.json

Expected artifacts:

• .airlift/postgresql-profile.json
• .airlift/postgresql-capability-plan.json

Open Engagements → active engagement in the App. This stage is visible at /engagements after replacing the placeholder ID with the governed engagement ID.

1. Create governed scope and connection references

fa engagement create --file engagement.json --idempotency-key migration-create-v1
fa estate register --file postgresql-estate.json --idempotency-key postgresql-estate-v1
fa connection register --file postgresql-connection.json --idempotency-key postgresql-connection-v1
fa engagement update --file postgresql-scope.json --idempotency-key postgresql-scope-v1
fa engagement preflight <engagement-id>

Expected artifacts:

• Governed engagement
• Source estate
• Opaque connection binding

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id> after replacing the placeholder ID with the governed engagement ID.

2. Assess and accept inventory

fa assessment start --file postgresql-assessment-start.json --idempotency-key postgresql-assessment-start-v1
fa assessment status <assessment-id> --json
fa assessment record --file postgresql-assessment-record.json --idempotency-key postgresql-assessment-record-v1
fa assessment accept --file postgresql-assessment-accept.json --idempotency-key postgresql-assessment-accept-v1
fa inventory list --estate-id <estate-id> --json

Expected artifacts:

• Assessment report reference
• Normalized inventory
• Dependency graph

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/sources/postgresql after replacing the placeholder ID with the governed engagement ID.

3. Implement the admitted source adapter

No source-specific executable compiler exists in this release. Continue with assessment, governed work, and an admitted adapter; Airlift does not invent executable output.

Expected artifacts:

• Capability plan and adapter requirements only

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/artifacts after replacing the placeholder ID with the governed engagement ID.

This source is cataloged or assessable but has no source-specific executable compiler in the installed Airlift generation.

4. Convert, move, and remediate

fa plan generate --file postgresql-migration-plan.json --idempotency-key postgresql-plan-v1
fa conversion batch create --file postgresql-batch.json --idempotency-key postgresql-batch-v1
fa conversion batch start --file conversion-batch-start.json --idempotency-key conversion-start-v1
fa residue list --engagement-id <engagement-id>
fa transfer plan --file postgresql-transfer.json --idempotency-key postgresql-transfer-v1
fa transfer run <transfer-id> --idempotency-key transfer-run-v1
fa transfer reconcile <transfer-id> --idempotency-key transfer-reconcile-v1

Expected artifacts:

• Target artifacts
• Residue cases
• Transfer checkpoints
• Reconciliation evidence

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/runs after replacing the placeholder ID with the governed engagement ID.

5. Validate independently and inspect discrepancies

fa validation run --file postgresql-validation.json --idempotency-key postgresql-validation-v1
fa validation status <validation-execution-id> --json
fa discrepancy list --engagement-id <engagement-id>
fa artifact list --engagement-id <engagement-id>

Expected artifacts:

• Provider run references
• Readiness evidence
• Discrepancies

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/runs after replacing the placeholder ID with the governed engagement ID.

6. Certify, cut over, and export evidence

fa certificate list --object-id <object-id>
fa cutover status <wave-id> --json
fa evidence list --engagement-id <engagement-id>
fa evidence export --file postgresql-evidence-export.json --idempotency-key postgresql-evidence-export-v1

Expected artifacts:

• Migration certificates
• Cutover evidence
• Content-digested evidence export

Open Engagements → active engagement in the App. This stage is visible at /assurance after replacing the placeholder ID with the governed engagement ID.

Runway executes releases; Experiments owns validation verdicts; Airlift owns migration readiness and cutover policy.

What developers see in the App

The contextual source workspace shows the accepted estate and the factory stages for this engagement. Artifacts displays immutable references, content digests, media types, and provider lineage. Runs displays assessment, conversion, transfer, validation, and deployment executions without treating a provider's success as an Airlift verdict.

View full size

These are automated captures from public synthetic engagements. The source workspace is specific to PostgreSQL and Aurora PostgreSQL; no unrelated source is presented as its migration journey. For sources without an evidence-backed journey, the image demonstrates setup, navigation, and developer entry points only—not a live connection, converted output, or certified migration. No client data, credentials, workspace hostnames, or internal deployment identifiers are embedded in the images.