Search results for “site:docs.ansible.com”
Page 3 of about
45 results
d
docs.ansible.com
ansible › latest › dev_guide › developing_locally.html
You can extend Ansible by adding custom modules or plugins. You can create them from scratch or copy existing ones for local use. You can store a local module or plugin on your Ansible control node and share it with your team or...
d
docs.ansible.com
ansible › latest › getting_started › introduction.html
Ansible provides open-source automation that reduces complexity and runs everywhere. Using Ansible lets you automate virtually any task. Here are some common use cases for Ansible: Eliminate repetition and simplify workflows Manage and maintain system configuration Continuously deploy complex...
d
docs.ansible.com
ansible › latest › reference_appendices › glossary.html
The following is a list (and re-explanation) of term definitions used elsewhere in the Ansible documentation. Consult the documentation home page for the full documentation and to see the terms in context, but this should be a good resource to check your knowledge of Ansible’s components and...
d
docs.ansible.com
ansible › latest › playbook_guide › playbooks_intro.html
Ansible Playbooks offer a repeatable, reusable, simple configuration management and multi-machine deployment system, one that is well suited to deploying complex applications. If you need to execute a task with Ansible more than once, write a playbook and put it under source control. Then you can...
d
docs.ansible.com
ansible › latest › module_plugin_guide › modules_intro.html
Modules (also referred to as “task plugins” or “library plugins”) are discrete units of code that can be used from the command line or in a playbook task. Ansible executes each module, usually on the remote managed node, and collects...
d
docs.ansible.com
ansible › devel › community › contributions_collections.html
If you have a specific Ansible interest or expertise (for example, VMware, Linode, and so on), consider joining a working group. Working with the Ansible collection repositories How can I find editors, linters, and other tools that will support my Ansible development efforts? Where can I find...
d
docs.ansible.com
ansible › latest › getting_started › get_started_ansible.html
Get started with Ansible by creating an automation project, building an inventory, and creating a “Hello World” playbook. Install Ansible. pip install ansible Create a project folder on your filesystem. mkdir ansible_quickstart && cd ansible_quickstart Using a single directory structure makes it...
d
docs.ansible.com
ansible › latest › getting_started › get_started_inventory.html
Inventories organize managed nodes in centralized files that provide Ansible with system information and network locations. Using an inventory file, Ansible can manage a large number of hosts with a single command. To complete the following steps, you will need the IP address or fully qualified...
d
docs.ansible.com
ansible › latest › dev_guide › testing_sanity.html
Sanity tests are made up of scripts and tools used to perform static code analysis. The primary purpose of these tests is to enforce Ansible coding standards and requirements. Tests are run with ansible-test sanity. All available tests are run unless the --test option is used. Set up your...
d
docs.ansible.com
ansible › latest › dev_guide › testing_units.html
Unit tests are small isolated tests that target a specific library or module. Unit tests in Ansible are currently the only way of driving tests from python within Ansible’s continuous integration process. This means that in some...
Try “site:docs.ansible.com” on:
Marginalia ·
Mojeek ·
Wiby ·
DuckDuckGo ·
Bing ·
Google ·
Wikipedia ·
Internet Archive