Actions
Bug #9320
closed
Rule & directive order is not taken into account for nodeConfig cache invalidation
Status:
Released
Priority:
2
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
We have a node configuration cache that tracks if a node config should be updated or not.
In that cache, we don't track the ordering (rule name & directive name). That means that if we only changed that, the config won't be updated, resulting to no policies written for the node.
Updated by 
Updated by
Actions