EBoisseauSierra commented on pull request #16606: URL: https://github.com/apache/superset/pull/16606#issuecomment-945786830
@betodealmeida , I think we can close this PR. Indeed, I reckon I raised an XY problem: what I want to be able to do is use different SQLA URI in dev (instance generating the export) and in prod (instance importing the export), without having to modify the archive/export itself. I'm still unsure how UUIDs are generated. However, it doesn't really matter as — as hinted by @PowerPlop — changing the SQLA URI of a db connection using its name as lookup key… is exactly what is already happening with `set-database-uri -d <db_connection_name>`! So running this command _after_ the `import-dashboards` would tick the box. The reason why we did it beforehand is that importing an export/archive containing a masked password in the `sqlalchemy_uri` key of a `export/databases/*.yaml` file fails, due to [this `ValidationError`](https://github.com/apache/superset/blob/master/superset/databases/schemas.py#L601-L602) — happening on a blank instance, at least. ➥ long story short, we still have a problem, but matching db connections with names rather than UUID is probably not the best way to address it. -- 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]
