Skip to content

[feature] Generic solution for invalidating cache on related field changes #1095

@pandafy

Description

@pandafy

Is your feature request related to a problem? Please describe.
Currently, cache invalidation when related fields are changed is not handled in a generic way. This issue is particularly critical for the VPN, Config, and Device (controller views) models, where related field changes require cache invalidation to ensure data consistency and correctness.

Describe the solution you'd like
Develop an extensible mechanism that automatically invalidates cache upon related field changes. Ensure this solution can be applied to other models as needed, enhancing maintainability and consistency across OpenWISP.

Describe alternatives you've considered
Evaluate and document the feasibility of moving this functionality to openwisp-utils for broader reuse.

Additional context
This feature will improve data reliability and consistency, particularly for models with interdependent fields that affect caching behavior.

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    To do (general)

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions