Skip to main content

Module oracle

Module oracle 

Source
Expand description

Where the reference oracle lives, and what to say when it does not answer.

ONE typed resolution of the oracle’s kubeconfig (OracleKubeconfig) and ONE typed diagnostic for an oracle that stayed silent (OracleUnreachable).

Both used to be inlined per test binary. m0_core_crud_parity.rs carried its own copy of each, and its copy of the hint told the operator to check a tunnel — kubectl --tls-server-name 127.0.0.1 … — to a hand-built k3s VM that has not existed since 2026-08-08. So the one sentence an operator acts on named a knob that is gone instead of ORACLE_KUBECONFIG_ENV, the knob that works.

That is how a duplicated operator-facing hint fails: silently. Both binaries went on passing against a live oracle and failing loudly against a dead one, exactly as designed — only the human reading the panic was sent to the wrong place. A hint has to hold wherever the harness panics, so it is represented once, at that scope, and every binary reads it from here.

Structs§

OracleKubeconfig
The reference oracle’s kubeconfig path, resolved once.
OracleUnreachable
The oracle did not answer — the ONE operator-facing hint for that state.
OracleUnresolved
Neither ORACLE_KUBECONFIG_ENV nor HOME named anything, so there is no path to even attempt.

Constants§

ORACLE_KUBECONFIG_ENV
The environment variable that selects the oracle’s kubeconfig. The ONE knob; every diagnostic in this module names it.
ORACLE_KUBECONFIG_FALLBACK
Where the oracle’s kubeconfig is looked for when ORACLE_KUBECONFIG_ENV says nothing: $HOME joined with this.