swarm-controller: make socketPath readOnly instead of asserting it
readOnly makes a bad socketPath inexpressible rather than diagnosed after the fact. Since readOnly rejects any definition including one arriving through a rename shim, drop the deploy.nix rename entry for it and the fixture line exercising it, and update the controllerOldPath comment's shim count from seven to six. Refs #4208
This commit is contained in:
parent
205986f77e
commit
fcb8a594bb
3 changed files with 3 additions and 27 deletions
|
|
@ -69,10 +69,6 @@ in
|
|||
[ "services" "hyperhive" "swarm" "controller" "enable" ]
|
||||
[ "services" "hyperhive" "deploy" "swarm-controller" "enable" ]
|
||||
)
|
||||
(lib.mkRenamedOptionModule
|
||||
[ "services" "hyperhive" "swarm" "controller" "socketPath" ]
|
||||
[ "services" "hyperhive" "deploy" "swarm-controller" "socketPath" ]
|
||||
)
|
||||
(lib.mkRenamedOptionModule
|
||||
[ "services" "hyperhive" "swarm" "controller" "forgeTokenFile" ]
|
||||
[ "services" "hyperhive" "deploy" "swarm-controller" "forgeTokenFile" ]
|
||||
|
|
|
|||
Loading…
Reference in a new issue