Skip to content
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.

Sign up for GitHub

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

Jump to bottom

dynaconf fail on bad $PWD #55

Open
il-steffen opened this issue Dec 16, 2022 · 3 comments
Open

dynaconf fail on bad $PWD #55

il-steffen opened this issue Dec 16, 2022 · 3 comments

Comments

@il-steffen
Copy link
Contributor

Running some unsuspecting command from invalid $PWD is now broken:
image

Dynaconf should probably handle this. But even if it does, I think this sourcing of a .env seems like a bad idea to me since env scripts are usually meant to be activated by user or shell script, to be consistently available for all apps launched from there. We have KAFL_CONFIG_FILE and ./kafl.yaml as app-specific override options.

Worse, this seems to happen already on import. Disabling in Dynaconf initialization in settings.py does not work and adding LOAD_DOTENV_FOR_DYNACONF=false to our env is a silly workaround :-/
@Wenzel
Copy link
Collaborator

Wenzel commented Jan 10, 2023

Bug reported to dynaconf

@Wenzel Wenzel mentioned this issue Mar 3, 2023
Closed
@Wenzel
Copy link
Collaborator

Wenzel commented Mar 3, 2023

The original issue has been fixed in dynaconf: dynaconf/dynaconf#853

However after testing to repro this bug with 3.1.12 dynaconf release, i found another one:
dynaconf/dynaconf#876

@Wenzel
Copy link
Collaborator

Wenzel commented May 10, 2023

This issue is waiting on next dynaconfig release v3.1.13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Wenzel @il-steffen