You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe the problem.
No response
Describe the solution you'd like
If there are multiple ABP applications in a distributed system that use different Cache Prefixes and all depend on the SettingManagement module, when a user updates the value of a setting on the UI, only the distributed cache of the local application is updated. Other applications, because they use different Cache Prefixes, will not update their caches.
It is also not possible to set a specific prefix for SettingManagement.
So I think when a Setting Value is updated, a SettingValueChangedEto event should be published, and subscribers should clear their local distributed caches.
The same principle might apply to Features and Permissions as well.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
No response
Describe the solution you'd like
If there are multiple ABP applications in a distributed system that use different Cache Prefixes and all depend on the SettingManagement module, when a user updates the value of a setting on the UI, only the distributed cache of the local application is updated. Other applications, because they use different Cache Prefixes, will not update their caches.
It is also not possible to set a specific prefix for SettingManagement.
So I think when a Setting Value is updated, a
SettingValueChangedEto
event should be published, and subscribers should clear their local distributed caches.The same principle might apply to Features and Permissions as well.
Additional context
No response
The text was updated successfully, but these errors were encountered: