This message was deleted.
# opal
s
This message was deleted.
s
Hi @Ben Adrian Sarmiento , I’m checking with my team and getting back to you..
🙌 1
b
Thank you!
o
Hi Ben, sorry for the delayed answer here. OPAL itself doesn't have a cache, instead it relies on the cache of the administrated policy engine (e.g OPA , Cedar-agent)
When OPAL starts it bring the agent to the baseline data state(as indicated by data-sources-config) and follows to update it with incoming events. Read more here: https://docs.opal.ac/FAQ#what-is-the-difference-between-initial-data-load-baseline-and-follow-on-updates-
Note that any disconnection from the OPAL server, the client assumes it's out of sync, and reloads the entire state from scratch (yes that means your data-sources-config should always point to a full current state)
There are new features in development (e.g. data tracking) that would give OPAL more visibility into what things changed (still without reading their content) to provide more flexibility here