DBT Cloud and CI/CD with GitHub
Вставка
- Опубліковано 25 кві 2022
- In this talk will cover how to deploy your DBT models seamlessly from development branches to other branches. We will specifically use GitHub to demonstrate running and deploying jobs to various environments.
We will cover concepts of environments, using custom schemas and environment variable and web hooks.
Amazing video. Just didn't understand what you were planning on doing with the custom schema else if statement, I think you were going to mention it but ended up not going for it.
Hi Tamir,
I did discuss @58:00 min mark to about 1:00:00 hour mark the custom schema macro. In that I had outlined the else if condition saying that ignore the default schema that was defined when creating the connecting in my case and use the custom schema which was called TeamA and it created the tableb2 in that schema.
The else functionality if we invoked it would have appended default schema to the custom schema which would have default_custom as the schema and in our case the custom schema was TeamA.
But that isn’t the functionality we wanted. We only wanted to write to TeamA schema which was our custom schema.
Other things you can do with in the else if could have been depending on the environment or tag change the schema you want to write to.
But I think I did do what I had intended there as far as showing that you can write to a custom schema.
If I didn’t mention something you would have liked or you want more detailed answer please reach out to me on my LinkedIn www.linkedin.com/in/sehaconsulting
If I orchestrate dbt in Airflow, how can i do CI CD
so worthless