mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
Documentation fixes
This commit is contained in:
parent
4c8d27f7bb
commit
4839243366
4 changed files with 7 additions and 7 deletions
|
@ -26,8 +26,8 @@ become_method
|
|||
at play or task level overrides the default method set in ansible.cfg
|
||||
|
||||
|
||||
New ansible_ variables
|
||||
----------------------
|
||||
New ansible\_ variables
|
||||
-----------------------
|
||||
Each allows you to set an option per group and/or host
|
||||
|
||||
ansible_become
|
||||
|
|
|
@ -157,7 +157,7 @@ it will be automatically discoverable via a dynamic group like so::
|
|||
Using this philosophy can be a great way to keep systems separated by the function they perform.
|
||||
|
||||
In this example, if we wanted to define variables that are automatically applied to each machine tagged with the 'class' of 'webserver', 'group_vars'
|
||||
in ansible can be used. See :doc:`splitting_out_vars`.
|
||||
in ansible can be used. See :ref:`splitting_out_vars`.
|
||||
|
||||
Similar groups are available for regions and other classifications, and can be similarly assigned variables using the same mechanism.
|
||||
|
||||
|
|
|
@ -264,7 +264,7 @@ This option causes notified handlers to run on a host even if a failure occurs o
|
|||
force_handlers = True
|
||||
|
||||
The default is False, meaning that handlers will not run if a failure has occurred on a host.
|
||||
This can also be set per play or on the command line. See :doc:`_handlers_and_failure` for more details.
|
||||
This can also be set per play or on the command line. See :ref:`handlers_and_failure` for more details.
|
||||
|
||||
.. _forks:
|
||||
|
||||
|
|
|
@ -51,12 +51,12 @@ requirements:
|
|||
notes:
|
||||
- Ansible uses the C(cs) library's configuration method if credentials are not
|
||||
provided by the options C(api_url), C(api_key), C(api_secret).
|
||||
Configuration is read from several locations, in the following order:
|
||||
Configuration is read from several locations, in the following order":"
|
||||
- The C(CLOUDSTACK_ENDPOINT), C(CLOUDSTACK_KEY), C(CLOUDSTACK_SECRET) and
|
||||
C(CLOUDSTACK_METHOD) environment variables.
|
||||
C(CLOUDSTACK_METHOD) environment variables.
|
||||
- A C(CLOUDSTACK_CONFIG) environment variable pointing to an C(.ini) file,
|
||||
- A C(cloudstack.ini) file in the current working directory.
|
||||
- A C(.cloudstack.ini) file in the users home directory.
|
||||
See https://github.com/exoscale/cs for more information.
|
||||
See https://github.com/exoscale/cs for more information.
|
||||
- This module supports check mode.
|
||||
'''
|
||||
|
|
Loading…
Reference in a new issue