Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
A
ansible
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
OpenEdx
ansible
Commits
48392433
Commit
48392433
authored
May 05, 2015
by
Toshio Kuratomi
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Documentation fixes
parent
4c8d27f7
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
7 additions
and
7 deletions
+7
-7
docsite/rst/become.rst
+2
-2
docsite/rst/guide_aws.rst
+1
-1
docsite/rst/intro_configuration.rst
+1
-1
lib/ansible/utils/module_docs_fragments/cloudstack.py
+3
-3
No files found.
docsite/rst/become.rst
View file @
48392433
...
...
@@ -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
...
...
docsite/rst/guide_aws.rst
View file @
48392433
...
...
@@ -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.
...
...
docsite/rst/intro_configuration.rst
View file @
48392433
...
...
@@ -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:
...
...
lib/ansible/utils/module_docs_fragments/cloudstack.py
View file @
48392433
...
...
@@ -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.
'''
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment