Initial Implementation

[jrobertson20]

Summary

This PR implements the load_dotenvx() function, which extends the existing load_dotenv() functionality to decrypt any encrypted environment variables before injecting them into os.environ.

Changes Made

• Added load_dotenvx() function in src/dotenvx/main.py.
• Utilized python-dotenv for existing dotenv loading logic.
• Implemented decryption for encrypted variables.

Usage Example

from dotenvx import load_dotenvx
load_dotenvx()

[Lfooligan]

Hey I'd love to use this library - it's especially useful for AWS Lambda functions. Any word on when this PR might be merged?

[tmf-chilledornaments]

I'd love to see this merged. My org is eager to use dotenvx for Lambda

[Lfooligan]

Since .env.keys should be .gitignored, can we assume os.environ['DOTENV_PRIVATE_KEY'] is already set correctly and use it?

[motdotla]

hi everyone, this is great BUT any reason you're not just using dotenvx via the binary install? That should work for lambda @Lfooligan, right? Or use python and node together on a lambda and use the npm dotenvx?

background: this repo was originally a placeholder with the intention to add a light python wrapper around native extensions. Similar to like nokogiri does for example as a rubygem. In other words, we'd write convenient python methods for dotenvx's functions but those functions would call out to binaries and/or c-code that did the heavy lifting. This would avoid feature drift with the core dotenvx library.

[nmatte]

In support of implementing this library:
My team's workflow makes heavy use of PyCharm, which does not support dotenvx + Python out of the box.

I ended up writing my own version of this PR in order to "natively" use dotenvx without relying on the binary. It greatly improved the portability of our application in CI, local workflows, etc, while allowing us to take advantage of better secrets management through dotenvx.

Counterpoint:
PyCharm supports command wrappers, so we could have done something like this:

#/bin/bash  
PATH=~/.pyenv/shims:/usr/local/bin:$PATH  
exec /usr/local/bin/dotenvx run -q -f /home/t4/proj/example/.env.test -- python "$@"

This solution was not easy to discover, though (I couldn't find this via googling and had to ask JetBrains support).

In conclusion: it was quicker/easier to implement and use this library than go digging for a way to properly use the binary in PyCharm. So, at least for my use case, this library would have been helpful.