jessie-ross commented on issue #26390: URL: https://github.com/apache/superset/issues/26390#issuecomment-1874940333
> [...] look into how using the Google Sheets engine authentication secrets for export would work [...] The question here is if we want to use the same authentication or separate authentication for export. For our use-case we'd want separate authentication, as we wouldn't want an extra DB engine to show up (we don't use Google Sheets as an adaptor.) I'm not really familiar with the UI based configuration system as we exclusively use `superset_config.py`, but from my perspective it seems simple enough to have a separate config variable for `GOOGLE_SHEETS_EXPORT_SERVICE_ACCOUNT_JSON_PATH`. I could code to detect if a service account is available with a Google Sheets engine to automatically enable Google Sheets export, but this becomes complicated if setup has more than one Google Sheets engine, and auto-enable like this might lead to unintended issues if an admin isn't expecting 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]
