EBoisseauSierra commented on pull request #16606: URL: https://github.com/apache/superset/pull/16606#issuecomment-938139484
With hindsight, it might be an XY problem I've been trying to solve. Indeed, what we eventually want to achieve is to “clone” one dev instance into production — with the slight difference that our (assuming only) database on dev would be connected to `postgresql://devuser:Tr0ub4dor&[email protected]/mock_data`, while on prod it would query `postgresql://produser:[email protected]/client_data`. Our process so far is: * on dev: 1. `superset export-dashboards` 2. `git push` * on prod: 1. `superset set-database-uri -d foobar -u postgresql://produser:[email protected]/client_data` 2. `git pull` 3. `superset import-dashboards` … and we'd like the import to use the already existing `foobar` db connection (i.e. to the prod db), rather than using the URI found in the export (which is pointing to the dev db) — using only the db name (`foobar`) as the matching key (and without having to manually tinker with the URI in the export archive, so that all can be automated nicely). (I know this should rather be a new Issue, I'll format it as such in the upcoming days.) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
