New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to export/import configuration and metadata #6485

Open
kstan79 opened this Issue Nov 28, 2017 · 11 comments

Comments

Projects
None yet
8 participants
@kstan79
Copy link

kstan79 commented Nov 28, 2017

I'm new in metabase, I would like to check is there a way to support multiple database but same schema by export and import the configuration.

The use case as below:

  1. we develop chart and dashboard at development server
  2. we export all charts/dashboard/configuration and import into different server (production)
    Cause we may have a few production server shared identical schema, we wish to eliminate repeated work on create chart, create dashboard cause we frequently change our work.

Or, if metabase support multi-tenancy and allow administrator replace data source it will be much more easier.

Is there any suitable solution for my use case?

Thanks in advance.
Ks

@jornh

This comment has been minimized.

Copy link
Contributor

jornh commented Dec 2, 2017

@salsakran

This comment has been minimized.

Copy link
Contributor

salsakran commented Dec 4, 2017

We don't currently allow you to export settings or have explicit multi-tenancy support.

You can probably do this via the rest API, however. https://github.com/metabase/metabase/wiki/Using-the-REST-API

@salsakran salsakran added the Proposal label Dec 4, 2017

@paoliniluis

This comment has been minimized.

Copy link

paoliniluis commented Dec 6, 2017

I would do this with an ETL between the testing and production databases (in case you use postgres or mysql). Metabase has a pretty self explanatory database!

@jornh

This comment has been minimized.

Copy link
Contributor

jornh commented Jan 22, 2018

@ijgonzalez-stratio

This comment has been minimized.

Copy link

ijgonzalez-stratio commented Feb 8, 2018

Workaround.

Create a dump (just the data, not the DDLs) of your current DB using at least this tables:
public.report_card
public.report_dashboard
public.report_dashboardcard
public.collection
public.metabase_fieldvalues
public.metabase_field
public.metabase_table
public.metabase_database

Then you can import your dump file into a new Metabase clean environment.

@shmoulana

This comment has been minimized.

Copy link

shmoulana commented Mar 22, 2018

Did any body tried and succeed on this ?

@ghost

This comment has been minimized.

Copy link

ghost commented Mar 23, 2018

Hi @shmoulana,

We implemented @ijgonzalez-stratio workaround and worked for us.

@mausch

This comment has been minimized.

Copy link

mausch commented Jun 4, 2018

Maybe I'm missing something, but the problem I see with that workaround is that it assumes that the entries in metabase_database will be the same in the origin and destination, which isn't the case when "promoting" questions/dashboards from a dev environment to prod.

@mausch

This comment has been minimized.

Copy link

mausch commented Jul 12, 2018

I ended up writing a tool to export/import SQL questions and dashboards to a JSON file

@gajus

This comment has been minimized.

Copy link

gajus commented Jul 15, 2018

I ended up writing a tool to export/import SQL questions and dashboards to a JSON file

Did you make it open-source?

@mausch

This comment has been minimized.

Copy link

mausch commented Jul 17, 2018

I've just been approved to make it open source : https://github.com/elevate/elevate.metabase.tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment