Closed philipsd6 closed 7 months ago
I just noticed you removed this in daf091d:
- class Config:
- env_file = "fastapi_msal.env"
…any reason why? In any case, I'd prefer to support the standard .env
file.
Hello @philipsd6 - I can't recall as it was long time ago. I remember vaguely that was some conflict - I'll have to check again and test.
@dudil In my case, I resorted to auth.cfg
because I have Python paths as environment variables listed in .env
file (VS Code linter couldn't lint properly). Wouldn't want to track that on VCS, right?
@philipsd6 & @yuenherny - I believe that Pydantic had since changed their way of reading values from .env files. Are you able to verify that on your end? This would be very much appreciated 🙏
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.
This PR was closed because it has been stalled for 10 days with no activity.
@philipsd6 & @yuenherny - I believe that Pydantic had since changed their way of reading values from .env files. Are you able to verify that on your end? This would be very much appreciated 🙏
Hi @dudil , I believe so. Pydantic moved from declaring a Config
class in V1 to using ConfigDict
in V2. Pydantic V2 support for .env
is available here.
Apologies for the late reply. Was occupied for the past few months.
Hi @yuenherny, Thank you for that. This was already handled with the migration to Pydantic V2.
🙏
This is useful for me, as in development mode I can consolidate all my runtime variables in one .env file, including the MSAL config.