joeyJsonar opened a new issue, #36956: URL: https://github.com/apache/superset/issues/36956
### Bug description Export a working big query database, and delete the database and try to import it. It looks like it works, but it fails when testing connection and it fails when creating dataset. This is due to the functionality that Superset only exports the serialized database connection and doesn't include any encrypted private keys. This is meant for extra security, but I will change it so that editing the imported Google BigQuery connection will prompt for uploading these 'Service Account' credentials again. ### Screenshots/recordings https://github.com/user-attachments/assets/d6329b31-05dc-4b19-abe6-fb0bd36c3943 ### Superset version master / latest-dev ### Python version 3.9 ### Node version 16 ### Browser Chrome ### 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]
