Better credential handling
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github, helm, kubernetes
- Domain
- devops, infrastructure, security
Research direction
No files, tests, or entry points are identified. Compare the mentioned local Kubernetes secrets, Argo and Helm options, GitHub admin-only variables, and Vault integration, then define the approach and verify that secrets no longer need to be stored in plaintext Git.
Written by the indexing model from the issue text.
Description
For the 2023 overhaul I've focused on just making things work, while trying to get away from having secrets in plaintext Git necessitating that our infra repo remained private. Initially we might just share the few secrets individually and create Kubernetes secrets from a local workspace with the secrets pasted in but not committed. There are options within Argo and Helm to make this a little more friendly, and also an Argo plugin for outright integration with Vault - although with the current open source drama brewing over a license change Hashicorp pushed on some of their projects that might be a thing to think twice about or reach for a true open source fork at some point. In the meantime the secrets may just live in heads or perhaps variables defined on GitHub that only admins can get to.
- Dominant language
- Groovy
- Stars
- 0
- Forks
- 2
- Avg merge
- 14m
- Merged PRs (30d)
- 8
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from MovingBlocks/Logistics
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
MovingBlocks/Logistics#11 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MovingBlocks/Logistics#5 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in MovingBlocks/Logistics
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
opengovsg/FormSG#10118 · 1 comment ·
Maintainers usually reply within 1 day
-
tagbot-manual
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
JuliaGraphics/Colors.jl#589 · 2 comments ·
-
area: ci area: tests bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Nitjsefnie-Harness-Commons/daedalus#1174 ·
Maintainers usually reply within 1 day
-
area:docs priority:p2 type:docs wave:1
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jejjohnson/gaussx#395 ·
Maintainers usually reply within 1 day