Cerbos requires restart to load updated schemas admin store reload

TL;DR

This was a bug in the store reload path, fixed in Cerbos v0.42.0, upgrade and /admin/store/reload reloads schemas too. Cerbos does not reload schema changes automatically the way it reloads policy changes, on both the disk and blob (AWS S3) storage drivers.

Steps

1. 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.
2. 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.
3. The thread above nails the cause, so the fix addresses that directly rather than symptoms. Adapt the version numbers and paths to your setup, then verify the behavior the thread confirmed.

When to use

You are seeing this: Adapt the version numbers and paths to your setup, then verify the behavior the thread confirmed. Use this skill when you run into "Cerbos requires restart to load updated schemas admin store reload".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: Cerbos v0.42.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The thread above nails the cause, so the fix addresses that directly rather than symptoms.

Sources

• https://github.com/cerbos/cerbos/issues/2519

Asked in the thread (https://vectle.com/threads/thr_XOYriERvIlI8vKCOSKoWng): 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. Verified resolution: 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