Skip to content

feat(secrets): add recovery toolkit - #2

Merged
g4st3r-d3v merged 5 commits into
mainfrom
feature/secrets-recovery-bitwarden
May 17, 2026
Merged

g4st3r-d3v merged 5 commits into
mainfrom
feature/secrets-recovery-bitwarden

Conversation

@g4st3r-d3v

Copy link
Copy Markdown
Contributor

Summary

  • Add a GitHub Actions secrets inventory and logical mapping for AssRep repositories with names/metadata only.
  • Add gitignored local recovery flow for pulling deployed env files into .secrets-recovery/.
  • Add a Bitwarden CLI importer that reads .secrets-recovery/consolidated.env, defaults to dry-run, supports --apply/--update, and never logs values.
  • Document the manual recovery flow, provider checklist, regenerate-required entries, and local file policy.

Validation

  • bash -n scripts/secrets-pull.sh scripts/secrets-to-bitwarden.sh
  • shellcheck scripts/secrets-pull.sh scripts/secrets-to-bitwarden.sh
  • ruby -e 'require "yaml"; YAML.load_file("secrets/secrets-inventory.yaml"); YAML.load_file("secrets/secret-mapping.yaml")'
  • git diff --check origin/main..HEAD
  • checked git diff origin/main..HEAD for common token/key/DSN patterns; no real values found

Security

  • No secret values are committed.
  • Runtime pulled values are written only under .secrets-recovery/, which is gitignored.
  • targets.env.example contains empty variable assignments only.

⚠️ Требует внимания юзера (вне scope этого PR)

  1. telegram-frontend/.env.lock contains a real BOT_TOKEN; if this file is in git history, the token is compromised and should be rotated via @Botfather.
  2. core/app/settings/base.py: JWT_SECRET defaults to "change-me"; verify staging overrides it.

@g4st3r-d3v
g4st3r-d3v merged commit 7c71a12 into main May 17, 2026
1 check passed
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.

2 participants