@Trevor what is an idempotent Ansible module ?
Most Ansible modules check whether the desired final state has already been achieved, and exit without performing any actions if that state has been achieved, so that repeating the task does not change the final state. Modules that behave this way are often called ‘idempotent.’ Whether you run a playbook once, or multiple times, the outcome should be the same.
out of the given options :
- Copy - repeating the execution does not change anything. Hence Idempotent.
- File - repeating the execution does not change anything. Hence Idempotent.
- Shell - repeating the execution does change something eg. access time, date, uptime etc. Hence NOT Idempotent.
- User - repeating the execution does not change anything or if the system is already in that desired state - it does nothing. Hence Idempotent.
