OperationCode / OperationCode/operationcode_infra
Unified secrets management
Nobody has claimed this yet.
- Dominant language
- HCL
- Stars
- 17
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
As recently experienced, having a bus factor of 1 for critical items like secrets can become a huge blocker for even the most basic of tasks. Given the occasionally transient nature of contributors, we want to make things simple to use and secure.
We need a secrets management solution that:
- Allows OpCode users and contributors to easily retrieve secrets they are authorized access to.
- Facilitates automation so that deployments and other system operations can be abstracted so an individual access isn't required to keep things moving forward.
- Allows revocation of access to secrets.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by defining and comparing a secrets-management approach against the three stated requirements, then document the chosen design, access and revocation flows, and how automation will operate without individual access.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100