Curious if anyone is using Doppler - https://docs.doppler.com/docs - with Pants. It seems like a great fit for a Pants project. I ran into an issue of running a test via Pants that depended on loading env vars from my local .env file, and that wasn't working since the .env file of course isn't in the working directory from which Pants runs a test (there's probably a way to fix that, haven't found it yet). Doppler makes .env files go away though, instead injecting env vars into the Pants process. So running e.g.

doppler run -- ./pants test path/to/test.py

works great (though I still need to configure test/extra_env_vars so that env vars in the Pants env carry over to the env running the tests)

I have no doppler experience, but it's surprising to me that

./pants test ...

+

[test] extra_env_vars

isn't enough. If

./pants

is in the right location to pick up

.env

(and it's run in a shell with direnv active I'm guessing?), then

pants

should see those env vars and let them through to

test

.

Right, we're using python-dotenv to read the .env file from the root directory of the project (in our current setup). I worked around it by adding this to the root BUILD file:

file(
    name="root_env_file",
    source=".env",
)

And then I've had to add this to every BUILD file in a test directory:

python_tests(
    name="tests0",
    dependencies=["//:root_env_file"]
)

Aha, your mention of

.env

threw me off. I did not realize

doppler

didn't use

.env

. Gotcha.