* convert aws_acm_facts to AnsibleAWSModule * factor aws_acm_facts into module_utils * add more filtering options for aws_acm_info * add aws_acm module and tests * uncomment aws_acm test * fix linting for aws_acm * fix __future__ linting for aws_acm * fix linting for aws_acm * fix linting for aws_acm * fix linting for aws_acm * fix linting for aws_acm * fix aws_acm_info arg type * remove test for old module name aws_acm_facts * simplify AWS ACM client creation * fix indent typo in aws_acm test * catch BotoCoreError in aws_acm * fix indent typo in aws_acm test * tighten AWS ACM test policy resource * move aws acm int test to venv * remove errant file * fix AWS ACM int test perms * undo copyright addition to wrong file * fix invalid log message in aws_acm Co-Authored-By: Jill R <4121322+jillr@users.noreply.github.com> * rephrase aws_acm_info doc from facts to information Co-Authored-By: Jill R <4121322+jillr@users.noreply.github.com> * rename aws_facts var to aws_info * remove case insensitivity for aws_acm pem compare * add no_log for aws_acm credential setting * add per-test prefix to aws_acm test resource names * make aws_acm use crypto module_util * clarify copyright for aws_acm * make aws_acm int test clearer * add explicit crypto dependency to aws_acm * change requests for aws_acm pr * fix wrong copyright owner aws_acm test * fix wrong copyright owner aws_acm test * rewrite aws_acm cert chain compare with regex, no dependency * fix linting for aws_acm unit test * fix linting for aws_acm unit test * fix linting and duplicate ignore * fix failed cert chain split in aws_acm, add more tests * remove errant file * more linting fixes for aws_acm * fix sanity ignore * rewrite cert compare in aws_acm to use base64 decode * improve regex for pem cert chain split in aws_acm * undo changes to crypto module util for aws_acm * increment ansible version for new aws_acm module * convert aws_acm return(x) to return x * increment version added for aws_acm_info new features * fix linting * fix bugs with AWS ACM * fix bad rebase * disable AWS ACM integration test, due to AWS account limit issue * remove aws acm integration test from shippable group |
||
---|---|---|
.github | ||
bin | ||
changelogs | ||
contrib | ||
docs | ||
examples | ||
hacking | ||
lib/ansible | ||
licenses | ||
packaging | ||
test | ||
.cherry_picker.toml | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
CODING_GUIDELINES.md | ||
COPYING | ||
Makefile | ||
MANIFEST.in | ||
MODULE_GUIDELINES.md | ||
README.rst | ||
requirements.txt | ||
setup.py | ||
shippable.yml |
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 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.
Use Ansible
You can install a released version of Ansible via pip
, a
package manager, or our release repository. See
our installation
guide for details on installing Ansible on a variety of
platforms.
Red Hat offers supported builds of Ansible Engine.
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, 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
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 4600 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.