Details
-
Type:
Task
-
Status: Rejected
-
Priority:
Medium
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Promise type: packages
-
Labels:None
Description
At the moment the promise is marked as kept even if the constraint was not fulfilled.
It does not look obvious and logical: when we require a file to be created and it cannot - then cfengine marks it as a failed promise.
Why not follow the same logic and fail `packages` promises when a version constraint is not satisfied?
