deploy: retention is the store host's decision, not the swarm's
Both retentionPeriods move to deploy.<store>.retentionPeriod. Measured before moving: each is read exactly once, in the container definition of the module that deploys the store, and no client hive consults either -- so they are options on the auto-deployed service rather than something every host has to agree on. What stays in swarm.* is what a client needs to reach the store: the package, the name it answers on, the port. Both modules said "what stays here is its package, domain, retention and wiring" in their options-block comments; retention no longer does, so those say so. Renames go in deploy.nix with the rest, so the whole move keeps one home and one file to delete when the deprecation window closes.
This commit is contained in:
parent
4423da4899
commit
4f4f1ec3ee
4 changed files with 60 additions and 37 deletions
|
|
@ -97,6 +97,19 @@ in
|
|||
[ "services" "hyperhive" "swarm" "forge" "ci" "package" ]
|
||||
[ "services" "hyperhive" "deploy" "forgejo" "ci" "package" ]
|
||||
)
|
||||
|
||||
# Retention is read only where the container is defined, so it is a
|
||||
# decision of the host running the store rather than something the swarm
|
||||
# agrees on. The two stores keep everything else — package, domain, port
|
||||
# — in `swarm.*`, because a client hive needs those to reach them.
|
||||
(lib.mkRenamedOptionModule
|
||||
[ "services" "hyperhive" "swarm" "victoriametrics" "retentionPeriod" ]
|
||||
[ "services" "hyperhive" "deploy" "victoriametrics" "retentionPeriod" ]
|
||||
)
|
||||
(lib.mkRenamedOptionModule
|
||||
[ "services" "hyperhive" "swarm" "victorialogs" "retentionPeriod" ]
|
||||
[ "services" "hyperhive" "deploy" "victorialogs" "retentionPeriod" ]
|
||||
)
|
||||
];
|
||||
|
||||
# ⚠️ `deploy.forgejo` is declared in ./hive-ci.nix, not here, and it is the
|
||||
|
|
|
|||
Loading…
Reference in a new issue