You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The goal of the idempotent test is to let us know when we are following bad practices for ansible playbooks. Unfortunately, it is impossible for shell commands to be truly idempotent and there are other things that inevitably change (ie, git clones) or could easily change and not be an indicator of bad practice (ie, if an update to a package happened to come out between runs).
To improve the situation, we need to do two things:
Label tests that cannot be reliably made idempotent with the tag “not-idempotent” so that they are skipped by this test.
Add changed_when and failed_when fields to shell command tasks, which will give them something resembling idempotent status.
This is relatively low priority.
The text was updated successfully, but these errors were encountered:
The goal of the idempotent test is to let us know when we are following bad practices for ansible playbooks. Unfortunately, it is impossible for shell commands to be truly idempotent and there are other things that inevitably change (ie, git clones) or could easily change and not be an indicator of bad practice (ie, if an update to a package happened to come out between runs).
To improve the situation, we need to do two things:
changed_when
andfailed_when
fields to shell command tasks, which will give them something resembling idempotent status.This is relatively low priority.
The text was updated successfully, but these errors were encountered: