Policy provider force is not idempotent
Bug #2069606 reported by
Francesco Di Nucci
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-openstacklib |
New
|
Undecided
|
Unassigned |
Bug Description
When using purge_config in a policy, if I understand well the policy file is set to empty and then the policy is written line-by-line, thus a change is reported at every agent run. Is it possible to implement this in a idempotent way? What would the proper implementation be? Create a temporary file with the new policy and compare it with the existing one?
To post a comment you must log in.