Set up a secret management scheme #26
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
#291 code passes security check
fediversity/fediversity
Reference: fediversity/fediversity#26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For provisioning and managing machines we need secrets. Choose a mechanism and integrate it into our deployment and development workflows.
see our notes
earlier we had settled on
agenixfor the time being, which hard-codes encrypted secrets into our source code.if end users are to be able to specify their admin credentials from our online panel however, we will need a different strategy.
or some cases, we may need to first decide on a way to handle secrets, c.f. https://codeberg.org/kiara/e2ed-hetzner/issues/6.
closing in favor of #493