handle credentials in NixOps4 #219
Labels
No labels
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
blocked
component
api-service
component
fediversity-panel
component
nixops4
documentation
points
0
points
0.5
points
1
points
13
points
2
points
21
points
3
points
34
points
5
points
55
points
8
points
infinite
productisation
project-management
question
role
application-developer
role
application-operator
role
hosting-provider
role
maintainer
security
technical debt
testing
type
bug
type
deliverable
type
key-result
type
objective
type
task
type
unclear
type
user-story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#221 handle sensitive variable inputs in NixOps4
fediversity/fediversity
Reference
fediversity/fediversity#219
Loading…
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?
As an operator,
given I can get admin credentials that help me log in to my deployed services,
I want these credentials to be handled securely during orchestration, including prevention of output in stdout/stderr (unless explicitly requested) or passing them through clear-text.
c.f. #130, which handles hard-coded secrets
kiara referenced this issue2025-03-03 07:57:45 +01:00
superseded by #307