The idea is:
When running on GCP, external secrets (External secrets | n8n Docs) should have an option to use credentials detection instead of an explicit service account key.
My use case:
I’m running n8n on Google Cloud Run, the service has a service account configured, and I’d like to use GCP’s Secrets Manager for external secrets. Currently I have to generate a service account key and upload that to the external secrets configuration in n8n, despite the fact that the service is already running under a service account.
I think it would be beneficial to add this because:
Easier setup through automatic credentials, fewer credentials/secrets to manage.