Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distributed events for Setting/FeatureValue/PermissionGrant changes #22201

Open
1 task done
gdlcf88 opened this issue Feb 20, 2025 · 0 comments
Open
1 task done

Distributed events for Setting/FeatureValue/PermissionGrant changes #22201

gdlcf88 opened this issue Feb 20, 2025 · 0 comments

Comments

@gdlcf88
Copy link
Contributor

gdlcf88 commented Feb 20, 2025

Is there an existing issue for this?

  • I have searched the existing issues

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant