Skip to content

Move secret management toward Vaultwarden and OpenBao#4

Open
Twix166 wants to merge 3 commits into
feat/exposure-map-collectorsfrom
feat/vaultwarden-openbao-secret-management
Open

Move secret management toward Vaultwarden and OpenBao#4
Twix166 wants to merge 3 commits into
feat/exposure-map-collectorsfrom
feat/vaultwarden-openbao-secret-management

Conversation

@Twix166

@Twix166 Twix166 commented Jun 14, 2026

Copy link
Copy Markdown
Owner

Summary

  • remove tracked SOPS config and encrypted secret payloads from the repo
  • add zero-secret Git guardrails for Vaultwarden/OpenBao data, tokens, exports, snapshots, and runtime files
  • add Vaultwarden + OpenBao migration plan, bootstrap runbook, example compose scaffold, OpenBao config scaffold, and metadata-only inventory examples

Validation

  • python3 scripts/secrets/validate_no_git_secrets.py
  • git diff --cached --check
  • YAML parse for compose/compose.secrets.example.yaml
  • JSON parse for secrets/inventory.example.json

Notes

  • This does not deploy Vaultwarden/OpenBao yet.
  • Bootstrap secrets, unseal/recovery material, and real migrations need Robert present and must stay out of GitHub.

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