Module stores 

Admin CRUD for the stores: resource (named redis/valkey connections).

Responses always carry the RAW stored config — ${ENV} placeholders are never resolved here (they resolve only when a client is built). Deleting a store still referenced by any plugin config is rejected with 409 {"error":"in_use","referrers":[...]} — a new envelope, since the reference is not discoverable via graph recompilation (a store used only by a shared plugin_config compiles fine without the node being wired). The same guard also covers acme.storage (system.yaml), since an ACME type: store storage config references a store outside gateway.yaml entirely and would otherwise go undetected.

Functions

create_store 🔒

delete_store 🔒

get_store 🔒

list_stores 🔒

ping_store 🔒

Connectivity check: resolves the store’s config (env placeholders included) and PINGs it, bounded by the store’s own connect_timeout_ms. The response never echoes resolved connection details — only latency and version.

router

store_referrers 🔒

Everything that references store name: node config store: keys (flat, for limit-count/workflow), nested session.store (session plugins — wired in a later plan, scanned now so the guard never lags the feature), and workflow’s per-rule action params (config.rules[].actions[][1].store — actions are [name, params] pairs; see plugins/native/workflow.rs).

update_store 🔒