EBoisseauSierra commented on pull request #16606: URL: https://github.com/apache/superset/pull/16606#issuecomment-938695411
@PowerPlop that could be a good option indeed. However, for that, I'd need to have _successfully_ imported the dashboards first. And for this to be possible, because the password (of the dev db URI) is masked in the export archive, I'd need to establish — as far as I understand — a _successful_ connection to the dev db (because it's the one in the export), from the prod VM. This is obviously better than the other way around, but is still not perfect, as this would mean having to fiddle with the dev db using prod details (e.g. allowing connection from the prod VM in dev's `pg_hba.conf`) for it to work. But that opens an interesting alternative solution: adding a flag for `import-dashboards` to work without ensuring that the db connection is successful (so that dashboards are effectively imported, yet with the db connection broken), and _then_, fixing the db connection as you suggests. -- 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]
