Materialisation level for different environments

[Mårten]

Hi.

I am currently running a dataform-project with some 50+ models and need a way to configure the materialisation of some tables based on the current environment (prod, dev).  Are there any best practices on how to solve this in a convenient way?

[caryna]

Hi @Mårten,

Welcome to Google Cloud Community!

You can review the best practices in Dataform and apply the recommended guidelines for managing code lifecycle in Dataform. You may also find valuable insights in this related discussion on the Google Cloud Community. 

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

[Mårten]

Thanks for getting back to me. I have read that post but it doesn't address
my issue of setting different materialisation strategy per environment.
For example using table views in development, but materialising them as
tables when building to production, much like DBT offers.
/Mårten

[caryna]

Hi @Mårten,

Regarding on the shared discussion, the only point there is the mentioned feature of Dataform, which is using workspace compilation override. This will let you create isolated Dataform development environments and may use it for your future reference. I apologized if I made you confused. 

However, it is also worth checking the best practices documentation. This will give you an overview on how you will manage your repository, how to handle your data sources and environments. 

You may also find these YouTube videos helpful: Dataform best practices, Managing Environments. It offers how you will structure your project and it also mentions the other built-in features of Dataform.