Hi everyone. We are currently upgrading our cerbods instance to 0.47.0 and just saw that

compile.cacheDuration

and

compile.cacheSize

configuration entries have been deprecated. I didn't see anything related to cache configuration in the release notes for this version. Does that mean compiled policies are not cached anymore ?

Hi Steven. We’ve made a few updates to the underlying engine over the last few releases (starting with

0.41.0

), which changed how policy data is represented. In short, all policies are now compiled and cached in memory at startup, rather than lazily computed at evaluation time.

Thank you for your answer. Is it still possible to configure how long policies are cached ?

No, the policies are loaded and then held statically in memory for the lifetime of the PDP (it might have been misleading to describe it as a "cache" in my previous message). Full reloads now prompt the engine to gather and reindex the full policy set from the given store again.

ok, thanks you for the clarification. So basically, to be sure I understood everything: • policies are stored in memory forever as long as the cerbos PDP is not restarted • Policies will be refreshed/reindexed (and stored again in memory ?) when a call to reloadStore endpoint is received. Am I getting this right ?

Yes, that's it 👍

perfect, thank you for the help !