50ceb8d7d8
open(path) throws an error when called on a directory or UNIX socket, and therefore a check to ensure that the path is absent will always succeed when there is a directory or file located there. This updates the check to use os.access(path, os.F_OK) instead, which instead just checks that the path exists instead of trying to open it as a file, and therefore properly handles directories and sockets. This causes a slight semantic change in how permissions are handled. The existing code will fail to work correctly if the user running the module on the managed host has no read access to the path specified. The new code will work correctly in that situation. Both versions fail if the user can't traverse the parent directory. I've also added a check to the try block to catch OSError. I've seen this call fail with an OSError on rare occasion in the face of odd extended permissions (usually MAC configuration) in cases where it should technically return False. In such cases, the file is functionally inaccessible to the user making the call, so it's essentially not there, but it can't be created by them either. I've documented this, as well as the fact that the bug this change fixes exists, and a rather nasty inconsistency involving symbloic handling that I stumbled across while testing this change. Fixes: #20870 |
7 years ago | |
|---|---|---|
| .github | 7 years ago | |
| bin | 7 years ago | |
| contrib | 7 years ago | |
| docs | 7 years ago | |
| examples | ||
| hacking | 7 years ago | |
| lib/ansible | 7 years ago | |
| licenses | ||
| packaging | 7 years ago | |
| test | 7 years ago | |
| ticket_stubs | ||
| .coveragerc | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .mailmap | ||
| .yamllint | ||
| CHANGELOG.md | 7 years ago | |
| CODING_GUIDELINES.md | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| MANIFEST.in | ||
| MODULE_GUIDELINES.md | ||
| Makefile | ||
| README.md | ||
| RELEASES.txt | ||
| ROADMAP.rst | ||
| VERSION | ||
| ansible-core-sitemap.xml | ||
| docsite_requirements.txt | ||
| requirements.txt | ||
| setup.py | ||
| 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.