[bug] bud.env somehow pulling local env vars into remote environment

[rguttersohn]

Agreement

• This is not a duplicate of an existing issue
• I have read the guidelines for Contributing to Roots Projects
• This is not a personal support request that should be posted on the Roots Discourse community

Describe the issue

It appears bud.env is bringing my public development env vars to my remote environment instead of using the remote .env file.

For example:

My dev env file:

PUBLIC_TOKEN='dev_token'

My staging env file:

PUBLIC_TOKEN='staging_token'

if I have console.log(TOKEN), in the dev and staging env, it returns 'dev_token'.

I also added a env var to staging only called PUBLIC_TEST. On staging, console.log(TEST) returns 'undefined'.

Expected Behavior

Dev public env vars should only be accessible in the dev environment. Staging public env vars should only be accessible in the staging environment.

Actual Behavior

When adding env vars, the local dev vars are being used in a remote staging env instead of the public vars from the remote .env file.

Steps To Reproduce

1. Add a env var to staging and another to dev and add a console.log for the var.
2. Provision staging server.
3. Deploy staging codebase
4. check the console.log and see if it returns the dev env var.

version

6.23.3

Logs

No response

Configuration

No response

Relevant .budfiles

No response

[kellymears]

I don't think it's possible for bud.js to do this.

This is the code that reads the env file:

https://github.com/roots/bud/blob/main/sources/@roots/bud-framework/src/bootstrap/env/index.ts#L64-L94

There is no caching involved; it is a straight filesystem read. I think the value must be set incorrectly in the .env file.