a22f46bacf
* Docs: Add a separate "seealso" section to the module docs
to list related modules and/or related references. This clears up the notes
section for things that are actual notes.
So you can add a section in your module documentation and four types of
references are possible.
seealso:
# Reference by module name
- module: aci_tenant
# Reference by module name, including description
- module: aci_tenant
description: ACI module to create tenants on a Cisco ACI fabric.
# Reference by rST documentation anchor
- ref: aci_guide
description: Detailed information on how to manage your ACI infrastructure using Ansible.
# Reference by Internet resource
- name: APIC Management Information Model reference
description: Complete reference of the APIC object model.
link: https://developer.cisco.com/docs/apic-mim-ref/
This PR also includes:
- Implements ansible-doc support
- Implements schema support for the seealso options
- Updates to the development documentation
- Rename filter convert_symbols_to_format to rst_ify, cfr the existing html_ify and tty_ify filters
- This makes the existing template a lot easier to read and fixes the confusion I had myself rereading the template (again).
- We fixed the possible suboption types (which was limited to 'bool' only)
* Use latest stable instead of devel docs
(cherry picked from commit
|
||
|---|---|---|
| .github | ||
| bin | ||
| changelogs | ||
| contrib | ||
| docs | ||
| examples | ||
| hacking | ||
| lib/ansible | ||
| licenses | ||
| packaging | ||
| test | ||
| .cherry_picker.toml | ||
| .coveragerc | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| CODING_GUIDELINES.md | ||
| COPYING | ||
| docsite_requirements.txt | ||
| Makefile | ||
| MANIFEST.in | ||
| MODULE_GUIDELINES.md | ||
| README.rst | ||
| requirements.txt | ||
| setup.py | ||
| shippable.yml | ||
| tox.ini | ||
Ansible
Ansible is a radically simple IT automation system. It handles configuration-management, application deployment, cloud provisioning, ad-hoc task-execution, and multinode orchestration -- including trivializing things like zero-downtime rolling updates with load balancers.
Read the documentation and more at https://ansible.com/
You can find installation instructions here for a variety of platforms.
Most users should probably install a released version of Ansible from
pip, a package manager or our release repository. Officially supported
builds of Ansible are also available. Some power users run directly from
the development branch - while significant efforts are made to ensure
that devel is reasonably stable, you're more likely to
encounter breaking changes when running Ansible this way.
Design Principles
- Have a dead simple setup process and a minimal learning curve.
- Manage machines very quickly and in parallel.
- Avoid custom-agents and additional open ports, be agentless by leveraging the existing SSH daemon.
- Describe infrastructure in a language that is both machine and human friendly.
- Focus on security and easy auditability/review/rewriting of content.
- Manage new remote machines instantly, without bootstrapping any software.
- Allow module development in any dynamic language, not just Python.
- Be usable as non-root.
- Be the easiest IT automation system to use, ever.
Get Involved
- Read Community Information for all kinds of ways to contribute to and interact with the project, including mailing list information and how to submit bug reports and code to Ansible.
- All code submissions are done through pull requests to the
develbranch. - Feel free to talk to us before making larger changes to avoid duplicate efforts. This not only helps everyone know what's going on, it also helps save time and effort if we decide some changes are needed.
- Users list: ansible-project
- Development list: ansible-devel
- Announcement list: ansible-announce -- read only
- irc.freenode.net: #ansible
- For the full list of Email Lists, IRC channels see the Communication page
Branch Info
- Releases are named after Led Zeppelin songs. (Releases prior to 2.0 were named after Van Halen songs.)
- The
develbranch corresponds to the release actively under development. - The
stable-2.xbranches exist for current releases. - Various release-X.Y branches exist for previous releases.
- For information about the active branches see the Ansible release and maintenance page.
- We'd love to have your contributions, read the Community Guide for notes on how to get started.
Roadmap
Based on team and community feedback, an initial roadmap will be published for a major or minor version (ex: 2.0, 2.1). Subminor versions will generally not have roadmaps published.
The Ansible Roadmap page details what is planned and how to influence the roadmap.
Authors
Ansible was created by Michael DeHaan (michael.dehaan/gmail/com) and has contributions from over 3700 users (and growing). Thanks everyone!
Ansible is sponsored by Red Hat, Inc.
License
GNU General Public License v3.0
See COPYING to see the full text.