Skip to content

feat: let an app skip vaults entirely instead of using an empty one - #160

Merged
ineedjet merged 2 commits into
mainfrom
feat/vault-less-apps
Aug 25, 2026
Merged

feat: let an app skip vaults entirely instead of using an empty one#160
ineedjet merged 2 commits into
mainfrom
feat/vault-less-apps

Conversation

@ineedjet

Copy link
Copy Markdown
Collaborator

Summary

  • Reverts feat: make a vault manifest's env: optional #158 (making a vault manifest's env: optional) — an empty vault has nothing to encrypt and gains nothing over not attaching one at all.
  • apps.<name>.env_refs in a target manifest is now optional. When omitted (or empty), deploy/deploy.py skips vault download/decryption for that app entirely — it still gets APP_NAME/DATA_DIR in its .env, nothing else.
  • Updated README's "Vaults And Targets" section and AGENTS.md's env-var-system docs accordingly, with beszel (zero vault-sourced env) as the example.

Test plan

  • python3 -m unittest discover -s deploy/tests — 52 tests pass, including a new test_app_without_env_refs_gets_no_vault_decrypted
  • .github/actions/encrypt-env tests pass with the revert (vault manifest env: non-empty requirement restored)

An empty vault (env: {}) has nothing to encrypt and gains nothing over
just not attaching one - env_refs on a target's app entry is now
optional, and deploy.py skips vault download/decryption for it.
@ineedjet
ineedjet merged commit 3940976 into main Aug 25, 2026
5 checks passed
@ineedjet
ineedjet deleted the feat/vault-less-apps branch August 25, 2026 20:33
@ineedjet ineedjet mentioned this pull request Aug 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant