* 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
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 ;)
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>
* Change old recommendation about insecure variables
These warnings were relevant before ansible had the secure vault feature:
any secret put into a variable used to be a bad idea.
With the vault feature (available since ansible 1.5) it's no longer a bad
idea to use these variables, as long as they aren't stored in plain text.
* Update intro_inventory.rst
Minor edit
* better explain task vs play includes
* clarification of play levels
* Update playbooks_roles.rst
Tweaked for grammar and clarity.
* Update playbooks_roles.rst
Typo fix
* ROADMAP updates
* Formatting - Especially the first section
* Reno Release notes is out of scope (I believe?)
* Change "Speed up make webdocs to stretched Goal - As I don't believe we currently know *how* we can achieve this
* Removed the word `Hardening` as it implies security, which isn't something we are actively working on in 2.3
* initial checkin. needs annotation at the top, dates, and review
* Update ROADMAP_2_3.rst
cleanup and add notes at the top
* Update ROADMAP_2_3.rst
fix indentation