adk_deployment_lifecycle (erlang_adk v0.10.0)

View Source

Dependency-aware deployment health and bounded admission draining.

Health output contains only component names and coarse states. It never serializes service handles, configuration, credentials, principals, or provider failures. Draining is atomic at the admission controller: queued calls are failed before this module waits for already-granted owners.

Summary

Functions

begin_drain()

-spec begin_drain() -> {ok, map()} | {error, term()}.

begin_drain(Timeout)

-spec begin_drain(non_neg_integer()) -> {ok, map()} | {error, term()}.

drain_code(Timeout)

-spec drain_code(term()) -> 0 | 1.

liveness()

-spec liveness() -> {ok, map()} | {error, not_live}.

liveness_code()

-spec liveness_code() -> 0 | 1.

readiness()

-spec readiness() -> {ok, map()} | {error, {not_ready, [atom()]}}.

readiness_code()

-spec readiness_code() -> 0 | 1.

status()

-spec status() -> map().