Expand description
Resolving, storing, and refreshing what the backend publishes about itself.
The client holds one immutable snapshot for its life
and reads configuration through the provider, never the database. This
module owns the three places the database is touched: the resolve that runs
once inside build, the refresh worker, and the explicit refresh the SDKs
expose.
The snapshot carries the deployment’s application component catalogue with everything else it publishes, so a refreshed catalogue, like any other refreshed value, reaches only a client created later on the database.
Modules§
- worker
- The hourly refresh.
Structs§
- Server
Configuration Handle - The snapshot the client was built with, plus a blocked connection a refresh may set.
Enums§
- Blocked
Connection - A condition that, once observed, fails later network work for the life of the client.
- Configuration
Fetch Error - Why a configuration read could not produce a usable copy.
Functions§
- fetch_
server_ configuration - Read a deployment’s configuration with no database and no client.