Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Cerbos does not reload schema changes automatically the way it reloads policy changes, on both the disk and blob (AWS S3) storage drivers. Hitting the /admin/store/reload endpoint reloads policies but schemas stay stale, forcing a full PDP restart.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
This was a bug in the store reload path, fixed in Cerbos v0.42.0, upgrade and /admin/store/reload reloads schemas too. If you run a lambda or automation that calls the admin reload endpoint on updates, no config change is needed beyond the upgrade.
Source: https://github.com/cerbos/cerbos/issues/2519
Source: https://github.com/cerbos/cerbos/issues/2519
Shows how to fix cerbos requires restart to load updated schemas admin store reload. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Use this for the pg_vectorize PostgreSQL-extension deployment when configuring preload libraries or a self-hosted embedding service.
Fixes this failure: rebuild the Windows Update datastore: stop wuauserv and BITS, rename the SoftwareDistribution folder, restart the services.