02e3f4b526
When becoming an unprivileged user using non-sudo on a platform where getlogin() failed in our situation we were not able to detect that the user had switched. This meant that all of our logic to use move vs copy if the user had switched was attempting the wrong thing. This change tries the to do the right thing but then falls back to an acceptable second choice if it doesn't work. The bug wasn't easily detected because: * sudo was not affected because sudo records that the user's have been switched so we were able to detect that. * getlogin() works on most platforms. RHEL5 with python-2.4 seems to be the only platform we still care about where getlogin() fails for this case. * It had to be becoming an unprivileged user. When becoming a privileged user, the user would be able to successfully perform the best case tasks. |
8 years ago | |
|---|---|---|
| .github | 8 years ago | |
| bin | 8 years ago | |
| contrib | 8 years ago | |
| docs/man | 8 years ago | |
| docs-api | 8 years ago | |
| docsite | 8 years ago | |
| examples | 8 years ago | |
| hacking | 8 years ago | |
| lib/ansible | 8 years ago | |
| packaging | 8 years ago | |
| test | 8 years ago | |
| ticket_stubs | 8 years ago | |
| .coveragerc | 8 years ago | |
| .gitattributes | ||
| .gitignore | 8 years ago | |
| .gitmodules | 8 years ago | |
| .mailmap | 9 years ago | |
| .yamllint | 8 years ago | |
| CHANGELOG.md | 8 years ago | |
| CODING_GUIDELINES.md | 8 years ago | |
| CONTRIBUTING.md | 9 years ago | |
| COPYING | ||
| MANIFEST.in | 8 years ago | |
| MODULE_GUIDELINES.md | 8 years ago | |
| Makefile | 8 years ago | |
| README.md | 8 years ago | |
| RELEASES.txt | 8 years ago | |
| ROADMAP.rst | 8 years ago | |
| VERSION | 8 years ago | |
| ansible-core-sitemap.xml | 8 years ago | |
| setup.py | 8 years ago | |
| shippable.yml | 8 years ago | |
| tox.ini | 8 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/
Many users run straight from the development branch (it's generally fine to do so), but you might also wish to consume a release.
You can find instructions here for a variety of platforms.
If you want to download a tarball of a release, go to releases.ansible.com, though most users use yum (using the EPEL instructions linked above), apt (using the PPA instructions linked above), or pip install ansible.
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.
- For releases 1.8 - 2.2, modules are kept in different repos, you'll want to follow core and extras
- 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
Licence
GNU Click on the Link to see the full text.