-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOPPLER_ENV=1 crashes poetry #11
Comments
@drawnwren Hey! What's your use case for setting |
spent an entire day debugging this in my docker container .. the issue is poetry runs scripts and captures stdout (for like to get info on the current interpreter thats executing) .. if all doppler-env logging is turned off then that resolves the issue, the JSONDecode error is where poetry takes the recent stdout where it expects the script it called to print json and tries to parse it, but with the added print from doppler-env its obv no longer a valid json string my use case is i wanted to set it in my container, so that when i logged into my server , i could use my scripts and cli tool n have env vars available without any extra steps |
@jermatic Would using something like direnv work for that use-case? Or alternately, just exporting the variables via the Doppler CLI in your bash profile? Either of those options should allow you to get your environment variables into the shell environment. Or is it that you have Regardless, it might make sense to update the behavior around
Did you set that to |
Environment
Description
python-doppler-env breaks poetry.
Steps to Reproduce
Expected Behavior
When
DOPPLER_ENV
is unset,poetry
installs and manages packages normally. Expected behavior is to not break the package manager.The text was updated successfully, but these errors were encountered: