Configuration Management

Now that we are a Cloud Prod Customer, I'm finding some features that are really essential for managing a client facing product that gives me the ability for something sorta like SDLC , or more specifically configuration management. Nirvana would be a way to manage all Metabase Objects (Dashboards, collections, Questions , Models etc ) via GIT. This would allow me to develop on one instance/branch and deploy on another i.e.) PROD, as well as the ability to rollback any issues found post UAT.

Its not entirely clear how I would do that now without having to resort to making changes directly to a production client facing instance.

I know there is discussion around providing a token on a separate dev instance and to use serialization to move back and forth .

It would be great if there were a clearer direction or roadmap and best practice recommendations on how you are thinking about this important issue.
I apologize if this already exists, I have not seen it however.

1 Like

The answer to this is serialization, and we’re making this simpler on pro accounts on the cloud very very soon so stay tuned

1 Like

Hey, I would also be very interested in some more detailed example, how to setup a system with one DEV Metabase instance for developing dashboards and then pushing the same dashboard to multiple production Metabase instances (where each of our customers can only interact with their own data), probably having to programmatically change some things in the yaml files for each individual client (im guessing maybe some connection names, colors, ...) . For us that would be on a selfhosted pro plan

Hope you guys can could dive into this things at one of you webinars or in a post.
Regards, Janez