Actions
Bug #6728
closed
Acceptation timestamp of Technique are not updated what breaks change detection
Status:
Rejected
Priority:
1
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When a Technique is updated, for ex. when one modifies a Techniques with the Technique Editor, its acceptation timestamp is not updated.
Acceptation timestamp is a property in Rudder that track when a Technique files (for a given version) changed for the last time. It is used to invalidate node configuration caches and so to know if promises must be regenerate for a given rule.
Updated by François ARMAND almost 9 years ago
- Status changed from In progress to Rejected
So, the behavior is in fact correct. On the first test, an side problem prevented the technique library to be reloaded, and the timestamp is updated on reload.
Closing that one.
Actions