onepub-dev / onepub-dev/reVault
how does ci/cd work given a vault is required.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 0
- Avg merge
- 1h 55m
- Merged PRs (30d)
- 1
Description
we need a plan for how ci/cd systems will work with a lockbox to provide secrets.
To open a lockbox you need a vault (unless the lockbox uses a password).
This would require that the vault is initialised each ci/cd run and then the original keys imported.
Some ci/cd system do have shared resources in which case the vault could be initialised once, the keys imported and then the ci/cd flow would just need the vault password injected.
This suggests that the ci/cd process has its own vault/profile and uses then add give that vault profile 'access' to a lockbox.
Further thought is required and we need to document alternate work flows for ci/cd environments.
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
Start by comparing the per-run vault initialization flow with the shared-resource CI/CD flow described in the issue. Done means the supported CI/CD workflows, vault/profile setup, secret-import steps, and required password or access handling are documented with their prerequisites.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, devops, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100