Hi Dennis, You mention that cloning the complete Superset database seems overkill here, but for our use case, we've found that copying almost the entire Superset db into our dev and staging environments solves these types of issues for us. To ensure the process doesn't take too long, we exclude the `logs` and the `queries` tables from our DB dump, but everything else we copy straight from prod to dev and staging for testing purposes.
I know this doesn't address a case where you build a chart in dev and want to move it to prod, but that's not a pattern we've really seen or needed in our deployment. Hope this helps! Erik On Wed, Jun 17, 2020 at 7:46 AM Maxime Beauchemin < maximebeauche...@gmail.com> wrote: > Few thoughts: > - did you try removing the id? this should work without the id since it's > totally possible to have an explore session without a saved chart > - we spoke in the past about introducing *uuids* for exportable/importable > objects that would be consistent across superset instances > - slugs for chart would help here, and should be easy to implement - we > need that regardless > - side note: it'd be great to use rison here for more readable URL encoding > - more generally - should an embeddable snippet point to a chart or a state > of an explore session? I think both use-cases make sense > > On Tue, Jun 16, 2020 at 12:39 PM Dennis Meyer <den...@jdeluxe.org> wrote: > > > Sorry for broken formatting. The URL contains an “slice_id”, see edited > > mail below for better readability. > > > > > > > > > > Hi, > > > > > > In the charts there’s an explicit embedding functionality generating > > Iframe code: > > > > > > <iframe > > > width="600" > > > height="400" > > > seamless > > > frameBorder="0" > > > scrolling="no" > > > > src="…slice_id=306…” > > > > > > > </iframe> > > > > > > It seems like there’s an ID hardcoded (see above) - which is very > > unfortunate when exporting and importing again and the embedding is in > > another application. In this case ids are different after import. > > > > > > I found a ticket about adding Slug to a chart, but it didn’t get too > > much attention. > > > https://github.com/apache/incubator-superset/issues/6537 < > > https://github.com/apache/incubator-superset/issues/6537> > > > > > > Is there currently a way to address this better if I wanted to use > > embedding code in dev, staging and prod environments? > > > Cloning the complete Superset database seems overkill for this. Also it > > won’t really work if you let production add charts by users and create > some > > major charts in dev you want to move to prod after some thorough testing. > > > > > > I’m glad for any suggestion. > > > > > > Thanks, > > > Dennis > > > > > > > > > > >
