internet/community.general
3
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2026-05-08 22:33:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

Modify instances of the use of the word idempotence to be correct. (#18704)

Browse Source 
Idempotence has a very specific meaning and it is generally not used correctly
in the manual. My attention was first drawn to this problem by the incorrect
definition in the glossary, but on further reading of the docs I found that
the problem occurred in a number of places.

Signed-off-by: mulhern <amulhern@redhat.com>
This commit is contained in:
mulkieran
2016-12-01 17:32:55 -05:00
committed by scottb
parent d2af88ba8a
commit 1fae3aecc7
7 changed files with 45 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docsite/rst/modules_intro.rst
View File

@@ -35,8 +35,10 @@ Another way to pass arguments to a module is using yaml syntax also called 'comp
All modules technically return JSON format data, though if you are using the command line or playbooks, you don't really need to know much about
that. If you're writing your own module, you care, and this means you do not have to write modules in any particular language -- you get to choose.
Modules strive to be `idempotent`, meaning they will seek to avoid changes to the system unless a change needs to be made. When using Ansible
playbooks, these modules can trigger 'change events' in the form of notifying 'handlers' to run additional tasks.
Modules should be idempotent, and should avoid making any changes if
they detect that the current state matches the desired final state. When using
Ansible playbooks, these modules can trigger 'change events' in the form of
notifying 'handlers' to run additional tasks.
Documentation for each module can be accessed from the command line with the ansible-doc tool::