Expand description
The services registry and its lifecycle (SRV-028 R2 to R5).
A service is made from one of the server’s own templates
([[auth.lys.templates]]), never from a command line a request names. Its
record is kept under the persistence path, one JSON file per service,
written whole with one full flush per transition and read back by one
directory scan at start: nothing is replayed. A held or retired service is
kept with its history; nothing here removes a record.
Who may act is decided before any method here is called (the lifecycle route asks Lys); this module records the holder it is handed. A create is placed in Lys first, the service under the network and each subject under the network, and is recorded only when every placement is answered.
Structs§
- Lifecycle
- The registry, its templates and the processes it started.
- LysPlacer
Placerover Lys’s placement route with this liminal’s app credential.- Process
Grant - What a service process’s own credential admits: registering its subjects, and nothing else.
- Service
Record - One service, as kept.
- Transition
- One change of state, with who made it and when.
Enums§
- Lifecycle
Error - Why a lifecycle request did nothing, by name.
- Service
State - Where a service stands.
Traits§
- Placer
- Places a resource under its parent in Lys.