Loading request...
Users are facing issues managing multiple GCP accounts locally, especially with authentication and project targeting. A feature to isolate gcloud CLI usage and ensure consistent Application Default Credentials (ADC) would greatly enhance user experience.
Hey all, I’m running into friction managing two separate GCP accounts on my Mac (work + personal). Switching between them with gcloud config configurations activate works in theory, but in practice I keep running into issues, especially with Terraform and local apps using Application Default Credentials. I often have to re-run gcloud auth application-default login, Terraform sometimes picks up the wrong account, and I occasionally realize I’m targeting the wrong project. It just feels brittle. I’d love a clean, reliable setup where: * gcloud CLI usage is clearly isolated * ADC works consistently for Terraform/Go without constant re-auth * It’s hard to accidentally use the wrong account/project * No long-lived service account keys if possible If you manage both work and personal GCP accounts locally, how are you structuring it? Separate CLOUDSDK\_CONFIG directories? Impersonation? direnv-based setup? Something else entirely? Looking for patterns that have held up well over time. Thanks!