MinBZK/DAWO-NixOS
33
3
Fork 0
Code Issues 14 Pull requests 4 Projects Releases Wiki Activity Actions

Fleet auto-update: git-driven device reconcile #23

New issue
Open
opened 2026-06-18 12:14:58 +00:00 by bram.buijs · 1 comment
bram.buijs commented 2026-06-18 12:14:58 +00:00
Collaborator
Copy link

Managed devices should converge on new commits without a manual deploy. Propose a
dawo.autoUpdate block (comin) following the #8 interface, that tracks a flake on
code.overheid.nl and rebuilds the device when commits land.

  • A bare device tracks the upstream core (this repo). A workplace points
    dawo.autoUpdate.options.repoUrl at its own overlay flake, which consumes the
    core as an input, so the chosen overlay is pulled in on every update.
  • Tunables: repoUrl (asserts non-empty), branch, pollSeconds (default 1800).
  • Replaces the current hard-wired services-comin.

Question: is comin the right mechanism for the managed fleet, or do you prefer
deploy-rs push or system.autoUpgrade pull for the estate? PR follows the choice.

Managed devices should converge on new commits without a manual deploy. Propose a `dawo.autoUpdate` block (comin) following the #8 interface, that tracks a flake on code.overheid.nl and rebuilds the device when commits land. - A bare device tracks the upstream core (this repo). A workplace points `dawo.autoUpdate.options.repoUrl` at its own overlay flake, which consumes the core as an input, so the chosen overlay is pulled in on every update. - Tunables: `repoUrl` (asserts non-empty), `branch`, `pollSeconds` (default 1800). - Replaces the current hard-wired `services-comin`. Question: is comin the right mechanism for the managed fleet, or do you prefer deploy-rs push or `system.autoUpgrade` pull for the estate? PR follows the choice.
rutger.putter commented 2026-06-18 13:10:16 +00:00
Collaborator
Copy link

@bram.buijs wrote in #23 (comment):

Question: is comin the right mechanism for the managed fleet, or do you prefer
deploy-rs push or system.autoUpgrade pull for the estate? PR follows the choice.

I prefer comin as this has a built-in Prometheus exporter. We can use this as device-update reporting in the future.
Secondly, comin has a command line interface that is available to users without sudo and allows for easy debugging.
Thirdly, comin has desktop notifications that will inform users on the updates as they come in.

@bram.buijs wrote in https://code.overheid.nl/MinBZK/DAWO-NixOS/issues/23#issue-309: > Question: is comin the right mechanism for the managed fleet, or do you prefer > deploy-rs push or `system.autoUpgrade` pull for the estate? PR follows the choice. I prefer comin as this has a built-in Prometheus exporter. We can use this as device-update reporting in the future. Secondly, comin has a command line interface that is available to users without sudo and allows for easy debugging. Thirdly, comin has desktop notifications that will inform users on the updates as they come in.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
release/0.1.0
No results found.
Labels
Clear labels   
Compat/Breaking
Breaking change that won't be backward compatible

  
Kind/Bug
Something is not working

  
Kind/Discussion
Any topic that needs discussion before a technical solution is accepted

  
Kind/Documentation
Documentation changes

  
Kind/Enhancement
Improve existing functionality

  
Kind/Feature
New functionality

  
Kind/Security
This is security issue

  
Kind/Testing
Issue or pull request related to testing

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Reviewed
Confirmed
 Issue has been confirmed

  
Reviewed
Duplicate
 This issue or pull request already exists

  
Reviewed
Invalid
 Invalid issue

  
Reviewed
Won't Fix
 This issue won't be fixed

  
Status
Abandoned
 Somebody has started to work on this but abandoned work

  
Status
Blocked
 Something is blocking this issue or pull request

  
Status
Help Wanted
 If you're looking to help out, start here

  
Status
Need More Info
 Feedback is required to reproduce issue or to continue work

  
Prio - Hoog
Hoge prioriteit

  
Prio - Laag
Lage prioriteit

  
Prio - Middel
Medium prioriteit

  
styling
Verbeteringen aan de styling

No labels
Compat/Breaking
Kind/Bug
Kind/Discussion
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Help Wanted
Status
Need More Info
Prio - Hoog
Prio - Laag
Prio - Middel
styling
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
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
MinBZK/DAWO-NixOS#23
No description provided.