Pass env directly from GCP, AWS and Azure Secrets to your application

1 GorillaMoe 1 8/20/2025, 12:35:26 AM github.com ↗

Comments (1)

GorillaMoe · 4h ago
IDK if some of you also struggle with passing `.env` files..

It's getting a bit ridiculous at the moment, because we have so many teams working on different projects and when you're jumping in and trying support a different team we mostly have to ask around for the latest dotenv files to get the projects working locally, after cloning.

I know there are solutions like hashicorp vault and doppler out there, but they are not cheap and I don't want another service handling my secrets, because they are stored in gcp secrets anyway and mostly managed via terraform / terragrunt / terramate.

I implemented a really hacky way of "automatically" creating a .env file when you first checkout the project and have access to the secrets, but it was really messy and did just work on macos and linux (and additionally required you to have gcloud and direnv installed).

So I basically wanted something like doppler, but for free and it should just work with gcp, azure and aws, so that people who are using the secret managers by these cloud providers don't have to change anything (regarding how they store their secrets).

I couldn't find anything, so I build the first version of it: https://github.com/mistweaverco/kuba

Disclaimer: Currently, it only supports GCP so far, because that was my main goal for my day-job. I'm going to add AWS and Azure support tomorrow.