GitHub user ampil added a comment to the discussion: Best Practices for Storing Superset Dashboards in Git
@meyyazhagan , yes that's a usual error. I don't have an automatic solution yet, my daily routine is to change datasets' source related with the dashboard. Then I export the dashboard from one environment and import it to another environment. If it works correctly (meaning no errors), I go back to my previous environment and revert connections back. There is also an option to disable database connection check during the dashboard import process in the python code. You may check `/app/superset/cli/importexport.py` and play with the lines related with import error handling https://github.com/apache/superset/blob/master/superset/cli/importexport.py#L308 GitHub link: https://github.com/apache/superset/discussions/30190#discussioncomment-13653909 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
