estoe

Secret to Env. Turn one cloud secret into a local .env file without copying secret values by hand. The multi-cloud version supports AWS Secrets Manager, Azure Key Vault, and Google Secret Manager.

estoe is available on PyPI. This source version, 0.2.1, includes the eMudhra certificate dependency updates. Check the PyPI version before installing; a source checkout can be ahead of the registry.

The owner reported successful AWS pull and GCP pull/preview on macOS. Azure is covered by offline tests; its live-test release gate was waived by the owner.

GitHub repository · PyPI package

Before you start

You need Python 3.12+, uv, Git, and macOS or Linux. Windows is not supported yet. macOS also needs the built-in diskutil command for file-safety checks. Your cloud identity must already have read access to the secret you select.

The secret must contain a JSON object whose values are all strings:

{"APP_MODE":"development","API_URL":"https://example.com","API_TOKEN":"synthetic-test-value"}

For that fictional example, estoe writes:

API_TOKEN="synthetic-test-value"
API_URL="https://example.com"
APP_MODE="development"

Never put real values in command arguments, Git, screenshots, or issue reports. estoe reads secrets; it does not create them or log you in.

1. Install the version you want

Use uv 0.13.4+ or pip 26.2.2+ before installing or updating estoe. Older installers may trust compromised eMudhra certificate chains. This checkout requires certifi>=2026.10.19 and locks certifi 2026.10.23; existing installations must be updated separately. See TLS certificate updates for the environment and custom certificate-store boundaries.

Install from PyPI

First verify that the PyPI page links back to this repository and lists the intended version. Install the standalone CLI with:

uv tool install estoe
estoe --version
estoe pull --help

For an application virtual environment, python -m pip install estoe also installs the CLI there. You do not need to clone the repository for a PyPI installation.

Multi-cloud development version: AWS, Azure, GCP

The multi-cloud changes are merged into main. To run the latest source checkout:

git clone https://github.com/alibacelonia/estoe.git
cd estoe
uv sync --locked
uv run estoe --version
uv run estoe pull --help

Run the examples below from that directory using uv run estoe. This selects the checkout, not an older globally installed estoe. The branch is development code, not a published stable release.

2. Choose a provider and authenticate

Replace the example resource names with your own authorized test resources. Never pass passwords or access tokens as flags.

For AWS SSO, refresh your existing session yourself with aws sso login --profile sandbox when needed. Without --profile, AWS uses its default credential chain. Without --region, the SDK/profile must supply one. GCP --project selects the secret's project, not the login identity or quota project.

New to Azure or GCP? Start with the complete setup guides:

• Azure: create a synthetic secret, configure permissions, and test
• GCP: create a synthetic secret, configure ADC, and test

Those guides include resource creation and IAM changes for you to review and run. Cloud resources and reads may cost money. estoe never performs setup automatically.

3. Check output safety, then preview

Use an existing directory owned by you and not writable by other users. Inside a Git repository, add your destination to your own .gitignore first, for example .env.local. This repository already ignores .env and .env.*. Never use a tracked file for output.

Choose one command for your provider:

# AWS
uv run estoe pull --provider aws --secret example/dev/app \
  --profile sandbox --region us-east-1 --output .env.local --preview

# Azure
uv run estoe pull --provider azure --secret estoe-test-app \
  --vault-url https://example-vault.vault.azure.net/ --output .env.local --preview

# GCP
uv run estoe pull --provider gcp --secret estoe-test-app \
  --project example-project --output .env.local --preview

For the fictional JSON above, preview prints only:

Preview: 3 variable(s)
API_TOKEN
API_URL
APP_MODE

Preview writes no file, but does read the cloud secret and may incur charges. It checks the selected output path too. Secret values are never printed by estoe.

4. Write the file

Run your chosen command again without --preview. For example:

uv run estoe pull --provider aws --secret example/dev/app \
  --profile sandbox --region us-east-1 --output .env.local

Expected success for three variables:

Wrote 3 variable(s) to the selected output (mode 0600).

Mode 0600 means only the owning user has POSIX read/write permissions. The file still contains plaintext secrets: keep it out of shared folders, backups, and sync tools where possible. Do not paste its contents into terminals or support tickets.

If the file exists, estoe asks before replacing it in an interactive terminal. In scripts, deliberately pass --overwrite only when replacement is intended. --preview and --overwrite cannot be combined.

5. Load the file in your application

The supported consumer is python-dotenv 1.x with interpolation disabled. Install python-dotenv in your application's environment separately, then use:

from dotenv import load_dotenv

load_dotenv(".env.local", interpolate=False)

This keeps dollar expressions such as ${TOKEN} literal. Other dotenv loaders may parse escapes differently. Never execute or shell-source the file.

Options and limits

Run uv run estoe pull --help for all options. With the released installation, use estoe pull --help instead.

• --provider is always required; there is no default provider.
• --output defaults to .env. Provider-specific flags cannot be mixed.
• --allow-unignored bypasses only the Git-ignore requirement. Prefer fixing your ignore rule. Tracked files are always refused, even with this flag.
• Outside a Git worktree, estoe warns that Git-ignore protection cannot be checked.
• Keys match [A-Za-z_][A-Za-z0-9_]*; output is sorted and keys stay unchanged. Empty strings work. Numbers must be quoted, for example "PORT":"8000".
• Duplicate keys, nesting, arrays, non-string values, binary secrets, NUL, and invalid Unicode fail before writing. Content is capped at 64 KiB; encoded output at 256 KiB. One secret is read per command; existing files are not merged.
• Azure supports public-cloud vaults and the latest version only. GCP supports global secrets and versions/latest, not regional secrets or custom endpoints.
• Retrieval has a 15-second worker deadline plus startup/cleanup. AWS/Azure allow at most two SDK attempts; GCP automatic API retries are disabled. Authentication may make additional requests. Git/filesystem checks have separate short timeouts.

Troubleshooting

Exit codes: 0 success, 2 invalid arguments, 1 operational failure. Errors are deliberately value-free; raw SDK warnings and exceptions are not shown.

Common secret-format mistakes

The cloud secret's entire value must be JSON, not the resulting dotenv file. For example, store {"PORT":"8000"}, not PORT=8000 or {"PORT":8000}.

Correct the intended secret through your normal authorized workflow, then run preview again. An invalid secret does not create a new output or replace an existing one. Do not paste real secret content into a JSON-validation website or public issue.

On an external macOS drive with “Ignore ownership on this volume” enabled, choose --output /absolute/path/on/a/private/volume/.env.local instead. estoe never changes system settings. GCP quota-project setup is explained in the GCP guide. After an interrupt or error, check whether the destination already exists before retrying: a completed atomic write can survive an interruption immediately afterward. See security boundaries for the full limitations.

Development and permissions

From the checkout:

uv sync --locked
uv run ruff format --check .
uv run ruff check .
uv run pytest
uv build

Automated tests use synthetic data and deny network access. Azure's live-test gate was waived, not passed. Its guide remains available for voluntary sandbox testing. AWS needs secretsmanager:GetSecretValue on the intended secret; a customer-managed KMS key may also need kms:Decrypt on that key. See the IAM examples. Azure/GCP least-privilege roles are in their setup guides. No telemetry, secret cache, automatic login, or secret discovery is used.

The protected main branch requires PRs, passing CI/audit, an up-to-date branch and resolved review conversations. Force pushes/deletion are blocked; no bypass actors are configured. Reviewer approvals are optional for solo maintenance. See the ruleset reference. These rules do not publish releases.

Maintainers: packaging and PyPI releases

CI checks formatting, tests, dependency vulnerabilities and the installed package. The separate Package and publish workflow also validates package metadata and stores downloadable wheel/source artifacts. PRs and manual runs never upload to PyPI.

Publishing is disabled by default. After one-time Trusted Publisher and approval setup, an approved stable GitHub release such as v0.2.1 can publish to PyPI. No permanent PyPI token is needed. Package metadata includes the GitHub repository, issues, documentation and changelog URLs for PyPI's project links.

Follow the step-by-step publishing guide. Merging this workflow does not publish a package or configure your PyPI account.

Project documents

• Requirements
• Architecture
• Decisions
• Task plan
• Security
• Changelog

Source, issues, and release artifacts: alibacelonia/estoe. PyPI package: estoe.

License

MIT.