Comment by gregw2
Interesting. It makes sense with Fivetran and dbt being so complimentary, ingestion (Fivetran) vs transformation (DBT).
But I still feel like I'm missing, in DBT, capabilities for DB DDL/DML deployment (which I've done from Liquibase in DBT) for a fully CICD modern data stack. Preconditions, post-conditions, only-deploy-changed-code capabilities... Am I missing something in DBT?
There's the slim ci best practice and ways to deploying only what's changed in dbt, but these require some config and underlying knowledge.
Verifying schema changes pre-production is only part of the issues, figuring out the actual data changes caused by code logic changes is trickier.