What problem does it solve?
This reference provides guidance for secrets architecture in node-template deployments, clarifying when to use OpenBao+ESO vs GitHub environment secrets and how to apply the correct write/rotate/add flows to keep credentials safe and consistent.
Core Features & Use Cases
- Decision framework for choosing between Open Bao/ESO and GitHub env secrets based on custody and workload.
- Catalog-led workflow guidance for creating and maintaining per-env and per-node secret catalogs and the loader scripts that consume them.
- Operational patterns for adding, rotating, and debugging ExternalSecret, writer-role login, and per-node vs per-env routing across substrate and Compose infra.
- Real-world scenarios including node onboarding, secret rotation events, and integrating with per-node catalogs and infra catalogs (paths like nodes/<node>/.cogni/secrets-catalog.yaml and infra/secrets-catalog.yaml).
Quick Start
Review the canonical secret workflow patterns in this reference and apply the OpenBao+ESO vs GitHub env decision logic to your node-template secret strategy.