Centralize SOPS secret declarations #43

Open
opened 2026-11-07 19:50:54 +00:00 by martin · 0 comments
Owner

Summary

Consolidate scattered SOPS declarations into a central location while preserving secret ownership and existing service references. Secret values remain user-managed.

Context

Migrated from TODO.md. Original TODO:

Refactor sops to be defined in a central location instead of all over

Scope

  • Consolidate scattered SOPS secret declarations into a central location.
  • Preserve secret ownership and existing service references.

Out of scope

Secret values remain user-managed; changing or exposing them is not part of this refactor.

Acceptance criteria

  • SOPS secret declarations are maintained in a central location rather than scattered through service modules.
  • Existing secret ownership and service references remain intact.
  • Affected host configurations build without activation.
## Summary Consolidate scattered SOPS declarations into a central location while preserving secret ownership and existing service references. Secret values remain user-managed. ## Context Migrated from `TODO.md`. Original TODO: > Refactor sops to be defined in a central location instead of all over ## Scope - Consolidate scattered SOPS secret declarations into a central location. - Preserve secret ownership and existing service references. ## Out of scope Secret values remain user-managed; changing or exposing them is not part of this refactor. ## Acceptance criteria - [ ] SOPS secret declarations are maintained in a central location rather than scattered through service modules. - [ ] Existing secret ownership and service references remain intact. - [ ] Affected host configurations build without activation.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Personal/nixos-configuration#43
No description provided.