remove the old snapshot store; tombstone its options
This commit is contained in:
parent
de3c5cbb65
commit
20d286f06a
1 changed files with 97 additions and 1308 deletions
|
|
@ -2,8 +2,7 @@
|
|||
# ./swarm.nix because the two are different concerns with different
|
||||
# audiences: that file declares WHO the peers are (consumed by
|
||||
# swarm-controller's hive roster and, here, the mesh), while this one
|
||||
# is plain host networking that a machine which runs no hive at all
|
||||
# --- the snapshot store, for one --- still needs.
|
||||
# is plain host networking that a machine which runs no hive can also enable.
|
||||
#
|
||||
# The two stay coupled by data, not by structure: the per-peer
|
||||
# `wireguard*` fields live on the peer submodule in ./swarm.nix, since
|
||||
|
|
@ -86,7 +85,7 @@
|
|||
|
||||
# Gated on the mesh itself, NOT on `deploy.hive-controller.enable`. The
|
||||
# mesh is host networking, not a c0re feature: a swarm host that runs no
|
||||
# hive — the snapshot store, for one — still has to join the mesh.
|
||||
# hive can join the mesh too.
|
||||
# Nothing below is c0re-specific; the peer data c0re consumes
|
||||
# (HIVE_PEER_CA_PATHS) is rendered in ./hive-c0re and stays gated there.
|
||||
config = lib.mkIf config.services.hyperhive.deploy.wireguard.enable {
|
||||
|
|
|
|||
Loading…
Reference in a new issue