Mirror of https://github.com/ansible/ansible.git

ansible hacktoberfest python

You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Go to file

Matt Clay dd45caa7a9 [stable-2.14] Docs removal and other backports (#81407 ) * Remove straight.plugin dependency (#80084) (cherry picked from commit `f587856beb`) * Update package-data sanity test (#80344) The test no longer relies on the Makefile. (cherry picked from commit `46362bbd27`) * Remove obsolete release bits (#80347) Releases are now built using the `packaging/release.py` tool. This makes the `Makefile` and associated files in `packaging/release/` and `packaging/sdist/` obsolete. * Use --no-isolation for package-data sanity test (#80377) The dependencies are already in the sanity test venv. This avoids use of unpinned dependencies and a dependency on a network connection. (cherry picked from commit `7fcb9960e6`) * Set the minimum setuptools to 45.2.0 (#80649) Also update the package-data sanity test to use the minimum setuptools version. (cherry picked from commit `4d25e3d54f`) * Use package_data instead of include_package_data (#80652) This resolves warnings generated by setuptools such as the following: _Warning: Package 'ansible.galaxy.data' is absent from the `packages` configuration. (cherry picked from commit `5ac292e12d`) * Fix os.walk issues in package-data sanity test (#80703) * Remove `docs` and `examples` directories (#81011) * Remove docs dir * Updates to reflect docs removal * Fix integration test * Remove examples dir * Updates to reflect examples removal * Remove build_library and build-ansible.py * Remove refs to build_library and build-ansible.py * Remove obsolete template * Remove obsolete template reference * Remove the now obsolete rstcheck sanity test (cherry picked from commit `72e038e823`) * Omit pre-built man pages from sdist (#81395) Since man pages aren't accessible to users after a `pip install`, there's no need to include them in the sdist. This change makes it trivial to build man pages from source, which makes them much easier to iterate on. It also simplifies creation and testing of the sdist, since it no longer requires building man pages. The new `packaging/cli-doc/build.py` script can generate both man pages and RST documentation. This supports inclusion on the docs site without a dependency on `ansible-core` internals. Having a single implementation for both simplifies keeping the two formats in sync. (cherry picked from commit `691c8e8603`)		2 years ago
.azure-pipelines	[stable-2.14] Docs removal and other backports (#81407 )	2 years ago
.github	[stable-2.14] Docs removal and other backports (#81407 )	2 years ago
bin	Modernize install (#76021 )	4 years ago
changelogs	[stable-2.14] Docs removal and other backports (#81407 )	2 years ago
hacking	[stable-2.14] Docs removal and other backports (#81407 )	2 years ago
lib/ansible	[stable-2.14] Fix missing command descriptions in manpages/docs (#81366 ). (#81371 )	2 years ago
licenses	Update PSF-license.txt to version from CPython 3.9.5. (#77805 )	4 years ago
packaging	[stable-2.14] Docs removal and other backports (#81407 )	2 years ago
test	[stable-2.14] Docs removal and other backports (#81407 )	2 years ago
.cherry_picker.toml	🚸 🐍 🍒 ⛏ Integrate cherry picker (#41403 )	8 years ago
.gitattributes	Makefile: Allow one to specify python version (#74517 )	5 years ago
.gitignore	Env gitignore (#78766 )	3 years ago
.mailmap	Fix syntax typo	8 years ago
COPYING	license file should be in source tree	14 years ago
MANIFEST.in	[stable-2.14] Docs removal and other backports (#81407 )	2 years ago
README.md	[stable-2.14] Convert non-docs .rst files to .md (#81217 ) (#81223 )	3 years ago
pyproject.toml	[stable-2.14] Docs removal and other backports (#81407 )	2 years ago
requirements.txt	Pin PyYAML version compatible with Python 3.8+ (#77936 )	4 years ago
setup.cfg	[stable-2.14] Docs removal and other backports (#81407 )	2 years ago
setup.py	Modernize install (#76021 )	4 years ago

README.md

Ansible

Ansible is a radically simple IT automation system. It handles configuration management, application deployment, cloud provisioning, ad-hoc task execution, network automation, and multi-node orchestration. Ansible makes complex changes like zero-downtime rolling updates with load balancers easy. More information on the Ansible website.

Design Principles

Have an extremely simple setup process with a minimal learning curve.
Manage machines 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.

Use Ansible

You can install a released version of Ansible with pip or a package manager. See our installation guide for details on installing Ansible on a variety of platforms.

Power users and developers can run the devel branch, which has the latest features and fixes, directly. Although it is reasonably stable, you are more likely to encounter breaking changes when running the devel branch. We recommend getting involved in the Ansible community if you want to run the devel branch.

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.
Join a Working Group, an organized community devoted to a specific technology domain or platform.
Submit a proposed code update through a pull request to the devel branch.
Talk to us before making larger changes to avoid duplicate efforts. This not only helps everyone know what is going on, but it also helps save time and effort if we decide some changes are needed.
For a list of email lists, IRC channels and Working Groups, see the Communication page

Coding Guidelines

We document our Coding Guidelines in the Developer Guide. We particularly suggest you review:

Branch Info

The devel branch corresponds to the release actively under development.
The stable-2.X branches correspond to stable releases.
Create a branch based on devel and set up a dev environment if you want to open a PR.
See the Ansible release and maintenance page for information about active branches.

Roadmap

Based on team and community feedback, an initial roadmap will be published for a major or minor version (ex: 2.7, 2.8). The Ansible Roadmap page details what is planned and how to influence the roadmap.

Authors

Ansible was created by Michael DeHaan and has contributions from over 5000 users (and growing). Thanks everyone!

Ansible is sponsored by Red Hat, Inc.

License

GNU General Public License v3.0 or later

See COPYING to see the full text.