You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As pointed out in #5532, -e file is loaded after the default .env and .flaskenv files, which means it won't override env vars that are set by the defaults. It will be a little tricky to track during CLI startup, but I think it should be possible to fix this so that precedence is: os.environ > -e path > .env > .flaskenv.
The text was updated successfully, but these errors were encountered:
…ult files
In the previous commit, pallets#5628 was fixed by creating the context
before loading the default environment variables. However, as
pointed out by @davidism, this can cause issues with the load
pipeline. Thus, this commit reverses that approach and uses the
`override` argument provided by `python-dotenv` to give priority
to custom file over default file.
Signed-off-by: Jalaj <96870071+jalaj711@users.noreply.github.com>
As pointed out in #5532,
-e file
is loaded after the default.env
and.flaskenv
files, which means it won't override env vars that are set by the defaults. It will be a little tricky to track during CLI startup, but I think it should be possible to fix this so that precedence is:os.environ
>-e path
>.env
>.flaskenv
.The text was updated successfully, but these errors were encountered: