ca59a4ede4
* Better handling of absent AWS SES identity notification information. Fixes #36065 aws_ses_identity module now handles the cases where information about the notification setup for the identity isn't returned by the AWS api. This seems to happen in an edge case, believed to be eventual consistency on registering new identities. So this case is treated as if has been no notification setup for the identity yet. Also fix 2 flake8 warnings in the module, a missing newline and unused import. * Increase the Boto Retries on SES APIs to deal with throttling. This should address the unstable integration test failing due to parallel runs in shippable hitting AWS throttling. * Add retries loading SES details for inclusion in successful response. There seems to be an eventual consistency behaviour with identity registration. It's possible to still get no identity back after registration. This can cause failures in the shippable builds. This should fix that by creating a retry of retrieving the identity information after registration. A similar retry loop has been added to notification attributes to ensure this doesn't suffer from the same failure. * Add missing sleep in get_notification_attributes to avoid busy loop. |
7 years ago | |
|---|---|---|
| .github | 7 years ago | |
| bin | 7 years ago | |
| contrib | 7 years ago | |
| docs | 7 years ago | |
| examples | 7 years ago | |
| hacking | 7 years ago | |
| lib/ansible | 7 years ago | |
| licenses | 7 years ago | |
| packaging | 7 years ago | |
| test | 7 years ago | |
| ticket_stubs | 7 years ago | |
| .coveragerc | 7 years ago | |
| .gitattributes | 7 years ago | |
| .gitignore | 7 years ago | |
| .gitmodules | 8 years ago | |
| .mailmap | 7 years ago | |
| .yamllint | 7 years ago | |
| CHANGELOG.md | 7 years ago | |
| CODING_GUIDELINES.md | 7 years ago | |
| CONTRIBUTING.md | 7 years ago | |
| COPYING | 13 years ago | |
| MANIFEST.in | 7 years ago | |
| MODULE_GUIDELINES.md | 7 years ago | |
| Makefile | 7 years ago | |
| README.md | 7 years ago | |
| RELEASES.txt | 7 years ago | |
| ROADMAP.rst | 7 years ago | |
| VERSION | 7 years ago | |
| ansible-core-sitemap.xml | 8 years ago | |
| docsite_requirements.txt | 8 years ago | |
| requirements.txt | 7 years ago | |
| setup.py | 7 years ago | |
| shippable.yml | 7 years ago | |
| tox.ini | 7 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, 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. Take care to make sure no merge commits are in the submission, and use
git rebasevsgit mergefor this reason. If submitting a large code change (other than modules), it's probably a good idea to join ansible-devel and talk about what you would like to do or add first and 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
Branch Info
- Releases are named after Led Zeppelin songs. (Releases prior to 2.0 were named after Van Halen songs.)
- The devel branch corresponds to the release actively under development.
- Various release-X.Y branches exist for previous releases.
- We'd love to have your contributions, read Community Information for notes on how to get started.
Authors
Ansible was created by Michael DeHaan (michael.dehaan/gmail/com) and has contributions from over 1000 users (and growing). Thanks everyone!
Ansible is sponsored by Ansible, Inc
License
GNU General Public License v3.0
See COPYING to see the full text.