Environments Within a Project

Feature Requests Secrets Manager
1

Hi,

For my use case, I really need a way to specify different values of a key based on the environment an application is running in. For example, let’s say I have a key called MY_NEAT_API_KEY in a project called My_API.

Within My_API I want three environments DEV, STAGING, and PROD. MY_NEAT_API_KEY would have a different value for each environment. Then in an SDK client, I could specify which environment I want keys for.

For the sake of example, using the node SDK (with typescript here) the client setting could have an extra parameter “environment”

    const settings: ClientSettings = {
      apiUrl: apiUrl,
      identityUrl: identityUrl,
      userAgent: "bitwarden/sm-action",
      deviceType: DeviceType.SDK,
      environment: 'DEV'
    };
    const client = new BitwardenClient(settings, LogLevel.Info);
    const result = await client.loginWithAccessToken(accessToken);
    if (!result.success) {
      throw Error("Authentication to Bitwarden failed");
    }

   const MY_NEAT_API_KEY_UUID = '8e42803f-7c97-4920-b924-b06201015ceb';
   const key = await client.secrets().get(MY_NEAT_API_KEY_UUID);

Good work by the team so far, I like what I see! I would love to use this at work, but at the moment this just won’t quite meet our requirements.

2 Likes
2

Thanks so much for the feedback! Environments within Projects is something we are currently working on for upcoming releases.

4 Likes
3

@jtouchstone Is this something still on the radar?

4

Environments remain on our roadmap, though it will still be some time before we get to them. The goal is to allow multiple environments per project, with names shared across environments by default while values can differ.

1 Like
5

Environments per project are an essential feature. Without it, we’re forced to create a separate project for each real-world environment. This makes bws rather cumbersome in a real application.

I’m actually struggling to see how bws can be used effectively without support for environments on anything but the simplest, most basic systems. If you have even 2 developers, a staging environment, and a production environment, managing and syncing the environments with bws is much more difficult and error-prone than just using .env files and a build script.

Larger clouds like GCP don’t have environment-specific secrets management but that’s because they have a lot of additional supporting infrastructure that helps scaffold and automate them.

Direct competitors like Doppler do have environments per project because they recognize the necessity. It’s a core feature, not a nice-to-have.

Please prioritize this feature. I’m very sad to say that bws is, unfortunately, next to useless without it.

6

One option here is to use the Varlock bitwarden plugin
You could then have multiple .env files which contain references to individual bitwarden secrets. Lots of options on how you compose values together… Plus you get validation, type safety, and extra security guardrails.