Expand description
The key namespaces featherbit writes under a store’s key_prefix.
Every key is {key_prefix}:{namespace}:.... These must stay disjoint: a
policy-written key must never be able to name a key a managed subsystem
reads or writes, in either direction. Declaring them in one place – and
testing the real builders against it – is what keeps that true as
subsystems are added.
The whole module is gated on redis-store: every subsystem it describes is,
so in a headless build there are no keys to namespace.
Constants§
- ACME
- ACME account, certificate, challenge and lease state (
src/acme/storage/redis.rs). - CACHE
- Cached responses (
proxy-cachewithpolicy: redis). - COUNTERS
- Rate-limit counters (
src/stores/counter.rs). - POLICY_
KV - Policy-written keys: the
store-get/store-set/store-incr/store-deletenodes. - SESSIONS
- Server-side sessions (
src/sessions/redis.rs). - SESSION_
LOCKS - Server-side session refresh locks (
src/sessions/redis.rs’slock_key). - SESSION_
SUBJECTS - Subject -> session-id index, for revoke-by-subject (
src/sessions/redis.rs’ssubj_key).