sheled-code opened a new issue, #34852: URL: https://github.com/apache/superset/issues/34852
### Bug description I use the superset import-dashboards CLI command to migrate dashboards between different environments. This process worked reliably in apache-superset==3.1.3 Upon attempting to upgrade to apache-superset==5.0.0, the import-dashboards command now fails. After investigation, I found that the new version attempts to validate the sqlalchemy_uri by [resolving the hostname](https://github.com/apache/superset/blob/master/superset/databases/schemas.py#L877) and testing the connection during the import process, while version 3.1.3 did not perform this check. I propose to add a new flag like --skip-database-validation which would explicitly tell the import-dashboards command to bypass the hostname resolution during the import process, allowing the old behavior. ### Screenshots/recordings _No response_ ### Superset version 5.0.0 ### Python version 3.11 ### Node version Not applicable ### Browser Not applicable ### Additional context _No response_ ### Checklist - [ ] I have searched Superset docs and Slack and didn't find a solution to my problem. - [ ] I have searched the GitHub issue tracker and didn't find a similar bug report. - [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- 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]
