Commit Graph

20 Commits (4bfb83c9668e10bc2dd02c5bd437d2b53f1bab2c)

Author SHA1 Message Date
John R Barker ec95cbc96e Formatting 8 years ago
John R Barker 71cc868f2b Update repomerge.rst 8 years ago
John R Barker b9e98406bd Reenable prmover (#19001) 8 years ago
John R Barker 250b0dff46 Remove link to PR mover 8 years ago
John R Barker 5cdc2b5738 repomerge.rst (#18756)
* repomerge.rst

* Past tense

* Update repomerge.rst

* Readonly repos, not deleted

* Make ansible/ansible a link

* Links

* maturity of the module's parameters

* PR & Issue mover is done - don't document as future

* Update repomerge.rst

* Typo
8 years ago
Evgeni Golov ea5c3df043 fix stray i in developing_modules.rst 8 years ago
Erwan Velu a252d71573 Update developing_modules.rst (#18646)
I was wondering how to return a new fact from a module I got the answer on IRC thx to "mgedmin".
I read this doc several time but didn't understood that I had to return a "ansible_facts" in the module.exit_json.
This change is about showing a sample code of it to help the next reader ;)
8 years ago
mulkieran 1fae3aecc7 Modify instances of the use of the word idempotence to be correct. (#18704)
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>
8 years ago
John R Barker fb73e89efe Typo 8 years ago
David Wittman d276947a58 Fix typo in Developing Modules doc
Fix pluralization of `ANSIBLE_KEEP_REMOTE_FILES` environment
variable.
8 years ago
scottb ba78f02dc5 Update developing_plugins.rst
Editorial pass.
8 years ago
scottb f38f43df61 Update developing_plugins.rst 8 years ago
Brian Coca 6bde3f1174 updated devleoping plugins guide 8 years ago
Scott Butler 844a7c8823 Fix for #18092 8 years ago
Scott Butler 427ce69645 Continued refurb of dev content 8 years ago
Will Thames c661f9f561 Module examples should be in YAML format
Given that Ansible best practices say to use YAML format, our
documentation should not make the excuse that it's too hard,
but rather represent examples in YAML format.

This will allow those using the examples to instantly see
best practices
8 years ago
Toshio Kuratomi d4f4abfb49 Fix python3 developer docs to build.
A couple small refactors to clarify meaning.
8 years ago
Scott Butler 578170a908 Edits for docs PR #18032 8 years ago
Toshio Kuratomi b8765d3d22 Update dev_guide with Python3 porting advice.
Also update the date that Python2.4 support will be dropped to say
Ansible-2.4 will no longer have python-2.4 support.
8 years ago
scottb f46de631af Dev guide reorg continues (#17732) 8 years ago