too many changed_when: false
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-ansible |
In Progress
|
Wishlist
|
Jimmy McCrory |
Bug Description
In our playbooks and role, we have many occurrences of changed_when: false, which is often use for convenience (not triggering handlers, override shell scripts default "changed" behavior).
I'd be happy to see these "changed_when" lines changed to:
- (If the changed_when tasks are used in a "read-only" manner:) maybe a facts or a different way to do the tasks that are using the registered value of the changed_when task.
- (If the changed_when tasks are used in a "read-write" manner:) maybe introduce more tasks to really check the expected results of the tasks, and either introduce a new module/action for handling state changes (if any).
We currently don't test idempotency, but it's could be part of our testing improvements of this cycle.
It seems a lower priority than the failed_when: false, imo.
Changed in openstack-ansible: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
Fix proposed to branch: master /review. openstack. org/433860
Review: https:/