Repository navigation
extension-utils: clarify policy cache invalidation ownership #147
Description
Both the Policies endpoint and Coolify deployments can register policy-cache invalidation hooks, and both use DIRECTUS_POLICY_CACHE_INVALIDATION_ENABLED.
When both extensions are installed in the same Directus instance, the shared environment variable cannot disable invalidation for only one of them.
Clarify ownership and avoid duplicate registration. Possible directions include central/shared registration, idempotent registration, or extension-specific enable flags.
Follow-up surfaced by #144.
Activity
remihuigen commentedon Sep 28, 2026
Impact is probably low - the worst cache scenario is that the same stuff is flushed twice
remihuigen commentedon Sep 30, 2026
Im also not sure whether extensions in the same project, that all use the directus policy cache, actually share a cache instance.
If the cache store is redis, then yeah probably (because they share a namespace).
But if the cache store is memory (eg a js map is used), im not sure if that points to the exact same object, because the cache utility is imported separately from each extension, and the map is declared in the utility global scope. Not sure if all imported than share the same variable? 🤔
Anyway, this needs further investigation