mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-07-22 12:50:22 -07:00
typofixes - https://github.com/vlajos/misspell_fixer
This commit is contained in:
parent
ae17b993d9
commit
bf5d8ee678
24 changed files with 31 additions and 31 deletions
|
@ -453,7 +453,7 @@ gives them slightly higher development priority (though they'll work in exactly
|
|||
Deprecating and making module aliases
|
||||
``````````````````````````````````````
|
||||
|
||||
Starting in 1.8 you can deprecate modules by renaming them with a preceeding _, i.e. old_cloud.py to
|
||||
Starting in 1.8 you can deprecate modules by renaming them with a preceding _, i.e. old_cloud.py to
|
||||
_old_cloud.py, This will keep the module available but hide it from the primary docs and listing.
|
||||
|
||||
You can also rename modules and keep an alias to the old name by using a symlink that starts with _.
|
||||
|
|
|
@ -29,7 +29,7 @@ and then commenting on that particular issue on GitHub. Here's how:
|
|||
or Docker for this, but they are optional. It is also useful to have virtual machines of different Linux or
|
||||
other flavors, since some features (apt vs. yum, for example) are specific to those OS versions.
|
||||
|
||||
First, you will need to configure your testing environment with the neccessary tools required to run our test
|
||||
First, you will need to configure your testing environment with the necessary tools required to run our test
|
||||
suites. You will need at least::
|
||||
|
||||
git
|
||||
|
|
|
@ -149,7 +149,7 @@ it will be automatically discoverable via a dynamic group like so::
|
|||
tasks:
|
||||
- ping
|
||||
|
||||
Using this philosophy can be a great way to keep systems seperated by the function they perform.
|
||||
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`.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue