devops-engineer
11f15aa86e
schema-drift-check / drift-check (push) Failing after 15s
Phase 1 scope: molecule-core-postgres-1 docker dev DB only. Phase 2 (Neon staging) and Phase 3 (Neon prod) deferred per CTO 2026-05-19 GO option C on the schema-SSOT memory. Contents: - atlas.hcl: 3 envs (mc-postgres wired, neon-staging/neon-prod stubbed) - mc/schema/schema.hcl: declarative HCL captured from live mc-postgres (30 tables, 1878 lines) - mc/migrations/20260519191337_baseline.sql: initial migration generated from the declarative schema - mc/migrations/atlas.sum: integrity hash - .gitea/workflows/ci-drift-check.yml: PR gate (validate + destructive-op down.sql requirement). Uses OSS `atlas migrate validate` since `migrate lint` was paywalled in v0.38+ — see open question below. - Makefile + README quickstart targets Open questions raised during PoC: 1. Atlas Pro lint vs OSS validate — accept OSS floor, or license Pro for destructive-change/data-loss analyzers? Current workflow uses a grep-based destructive-op check as a stopgap. This commit is the PoC for RFC#549 Phase 1. No live DB was mutated; Atlas plans against an ephemeral docker dev DB. The existing molecule-core/migrations/ and molecule-controlplane/migrations/ directories remain authoritative for their products until cut over.