Under the hood
Useful2 Signal2
Managed policy limits can be cached through the storage backend, falling back to the cache file.
What's wrong with this entry?
Anonymous. No account, no email.
What
The loader for managed policy limits can now prime its cache from a storage backend at startup and write and delete through it, under a policy-limits key. If the prime read fails or the cached blob is too large it logs and falls back to reading the raw cache file as before. Polling, stale-cache fallback and the existing telemetry are unchanged.
Details
- the storage path is used only when a storage backend is supplied; otherwise the file path is used
Evidence
Policy limits: prime skipped (oversize cache); raw cache read stays
Strings lifted out of the shipped bundle, so the claim above can be checked against them.