@luckystack/secret-manager
v0.16.1
Published
Rotation-aware secret resolver client for LuckyStack. Commit `.env` pointers (e.g. OPENAI_KEY=OPENAI_AUTHORIZATION_KEY_V5) instead of real secrets; at boot this client resolves them against an external append-only secret-manager server and writes the real
Maintainers
Readme
@luckystack/secret-manager
Boot-time client for an external versioned secret store. Commit opaque environment pointers instead of real values; keep the bearer token in a gitignored file or a secret store. Install @luckystack/secret-manager, then initialize it before importing application modules that read environment variables. See the installed initSecretManager types and architecture for the boundary with the external server.
Specify an explicit envNames allowlist: without one nothing is resolved off-host, intentionally protecting unrelated inherited variables. For production, use fail-closed resolution when an unresolved secret would compromise service behavior. Do not use development fallback mode to silently tolerate missing production secrets.
Secret rotations publish a new immutable pointer version rather than changing an existing one, so old branches can still start. The token file must never be committed; the raw resolution cache must never be logged or exposed by a health endpoint. Use metadata-only diagnostics.
