Well I'll start with a question :slightly_smiling_...
# advice-data-governance
m
Well I'll start with a question 🙂 How many of us are managing schemas / table creation ddl statements as versioned artifacts checked into source control? What are the best practices that you're following to ensure that these are evolving in the right way? What are the tools / libraries you are using for this?
✋ 1
h
We use Alembic and Flyway, depending on the service. Not sure what you mean by evolving the right way, but we have quite strict check in our CI pipelines that we dot end up with for example "split heads", i.e migrations that are not linearly order.
n
We use liquibase as part of our development process... We have a repo in which we store all migrations and we follow the same process as for ETLs code... PR + Code Review + a dry run before it gets merged.