Expand description
The Lys HTTP routes the production service bindings read and ask (ACCESS-003 R1), behind one seam.
lys-pass at the pinned commit carries only the pass, batch-check and
draft routes; the budget, stop, start-command and usage routes the
services bind to are Lys identity-server routes on Lys main
(budgets_api.rs, stop_api.rs, launch_api.rs, budgets_act.rs).
LysHttp is the seam they go through and HttpLys is its real
implementation: one request, with the bearer the binding names, answered
by Lys’s status and JSON body unchanged. Nothing is cached and nothing is
retried here; a transport failure is lys_could_not_be_asked, and a
refusal status is carried back with Lys’s own body so the refusal keeps
its name.
Structs§
- HttpLys
LysHttpoverreqwest.- LysAnswer
- One Lys answer: the HTTP status and the JSON body exactly as Lys sent it
(
Nullfor an empty body).
Traits§
- LysHttp
- The Lys routes the services bind to, asked with a bearer pass.
Functions§
- segment
- One URL path segment, percent-encoded (
.included, so..can never climb), so a name can never reach another Lys route.