Actions
Bug #4540
closed
If /var/rudder/configuration-repository files are different from the git status, during a Technique reload, the modification will not be take into account but regeneration of promise will be made.
Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
If per chance the git status of /var/rudder/configuration-repository (State C) is not synchronized by the state of the filesystem (State C-1), during the reload of the Techniques Rudder will make a new commit.
This new commit will return git in the state of the filesystem (It will pass from State C to C-1) which mean that no modification has been made but Rudder will despite everything regenerate its promises.
Updated by Benoît PECCATTE almost 10 years ago
- Category set to Web - Config management
- Status changed from New to Rejected
- Target version set to Ideas (not version specific)
This highly improbable, moreover we are missing details.
Actions