Rule & directive order is not taken into account for nodeConfig cache invalidation
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 Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.2.9 and 3.1.16 which were released today.
- 3.2.9: Announce Changelog
- 3.1.16: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/