Secrets Manager: Where I Finally Stopped Hardcoding API Keys

We've all done it. Hardcoded API keys in config files. Committed them to Git. Then scrambled to revoke them when you realize the repo is public. I was guilty of this for years. Then I discovered Secrets Manager on GCP. Now, every API key, every database password, every certificate lives in Secrets Manager. My code fetches them at runtime. No more secrets in environment variables. No more .env files floating around. And Secrets Manager has versioning, so I can roll back if I push a bad key. It also integrates with Cloud Run, GKE, and Cloud Functions natively. My security posture improved overnight. If you're still storing secrets in plain text, stop. Use Secrets Manager. It's one of those services that feels like it should be built into every cloud, and GCP does it really well.