7fbacf920d
* Remove misleading statement passwords must be same Since 2.4 Ansible has supported multiple vault passwords: <https://docs.ansible.com/ansible/latest/user_guide/vault.html#multiple-vault-passwords> Meaning lines like the following are misleading: > The password used with vault currently must be the same for all files you wish > to use together at the same time. -- `docs/docsite/rst/user_guide/vault.rst` To demonstrate this with Ansible 2.7, save the following as `example.yaml`: ``` - name: Display output from two vaults with different passwords hosts: localhost connection: local vars_files: [one.yaml, two.yaml] tasks: - name: View secret from one.yaml vault debug: { var: one } - name: View secret from two.yaml vault debug: { var: two } ``` Then run the three following commands choosing two different passwords: ``` $ echo 'one: 1' | ansible-vault encrypt --vault-id id1@prompt --output=one.yaml $ echo 'two: 2' | ansible-vault encrypt --vault-id id2@prompt --output=two.yaml $ ansible-playbook --vault-id id1@prompt --vault-id id2@prompt example.yaml ``` `ansible-vault` stores an ID in plain text in the vault file. * Remove note about default in Ansible 2.1 As requested by gundalow in https://github.com/ansible/ansible/pull/49798 |
7 years ago | |
|---|---|---|
| .. | ||
| _extensions | 7 years ago | |
| _static | 7 years ago | |
| _themes | 7 years ago | |
| js/ansible | 9 years ago | |
| rst | 7 years ago | |
| .gitignore | 9 years ago | |
| .nojekyll | 9 years ago | |
| Makefile | 7 years ago | |
| Makefile.sphinx | 8 years ago | |
| README.md | 7 years ago | |
| jinja2-2.9.7.inv | 9 years ago | |
| keyword_desc.yml | 7 years ago | |
| modules.js | 9 years ago | |
| python2-2.7.13.inv | 9 years ago | |
| python3-3.6.2.inv | 9 years ago | |
| requirements.txt | 7 years ago | |
| variables.dot | 9 years ago | |
README.md
Homepage and documentation source for Ansible
This project hosts the source behind docs.ansible.com
Contributions to the documentation are welcome. To make changes, submit a pull request that changes the reStructuredText files in the rst/ directory only, and the core team can do a docs build and push the static files.
If you wish to verify output from the markup such as link references, you may install sphinx and build the documentation by running make webdocs from the ansible/docs/docsite directory.
To include module documentation you'll need to run make webdocs at the top level of the repository. The generated html files are in docsite/htmlout/.
To limit module documentation building to a specific module, run MODULES=NAME make webdocs instead. This should make testing module documentation syntax much faster. Instead of a single module, you can also specify a comma-separated list of modules. In order to skip building documentation for all modules, specify non-existing module name, for example MODULES=none make webdocs.
If you do not want to learn the reStructuredText format, you can also file issues about documentation problems on the Ansible GitHub project.
Note that module documentation can actually be generated from a DOCUMENTATION docstring in the modules directory, so corrections to modules written as such need to be made in the module source, rather than in docsite source.
To install sphinx and the required theme, install pip and then "pip install sphinx sphinx_rtd_theme"
HEADERS
RST allows for arbitrary hierchy for the headers, it will 'learn on the fly' but we want a standard so all our documents can follow:
##########################
# with overline, for parts
##########################
*****************************
* with overline, for chapters
*****************************
=, for sections
===============
-, for subsections
------------------
^, for sub-subsections
^^^^^^^^^^^^^^^^^^^^^
", for paragraphs
"""""""""""""""""
We do have pages littered with ```````` headers, but those should be removed for one of the above.