Options for layer / serve / serveRemote.
Pass the same per-HyperService readiness Effect Node.httpServer uses for /health
when you want FleetHealth's leaf to match the node-handle status snapshot. Absent ⇒ empty
HyperServices / ok.
export interface FleetHealthOptions {
readonly FleetHealthOptions.readiness?: Effect.Effect<ReadonlyArray<ServiceReadiness>>readiness?: import EffectEffect.interface Effect<out A, out E = never, out R = never>The Effect interface defines a value that lazily describes a workflow or
job. The workflow requires some context R, and may fail with an error of
type E, or succeed with a value of type A.
When to use
Use when you need to represent a lazy, composable workflow that can require
services, fail with a typed error, or succeed with a typed value.
Details
Effect values model resourceful interaction with the outside world,
including synchronous, asynchronous, concurrent, and parallel interaction.
They use a fiber-based concurrency model, with built-in support for
scheduling, fine-grained interruption, structured concurrency, and high
scalability.
To run an Effect value, you need a Runtime, which is a type that is
capable of executing Effect values.
Effect<interface ReadonlyArray<T>ReadonlyArray<type ServiceReadiness = {
readonly key: string;
readonly kind: string;
readonly ready: boolean;
readonly detail?: string | undefined;
readonly contractHash?: string | undefined;
}
A served HyperService's readiness as reported by its node.
ServiceReadiness>>;
}