ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity
Mirror of https://github.com/ansible-collections/community.general.git
28230 commits 10 branches 167 tags 272 MiB
Python 99.5%
Shell 0.3%
HCL 0.1%
Find a file
Mark Mielke b4a1542670 Reduce the system calls performed by the "file" module 
when using "state: link", and particularly when using
"force: yes".

Symbolic link resolution can be expensive. In our case,
the symbolic links are legacy links to automounts, and
the "file" task was causing all of the legacy links to
be traversed and mounted on every host every time the
task executed, even when the links were correct and there
was nothing to do.

This change avoids the system calls that perform the
symbolic link resolution by taking advantage of the short
circuit behaviur of the boolean "and" operator. The code
behaviour is unchanged except that it no longer performs
unnecessary system calls.

As it turns out, this change is not sufficient to fully
solve the symbolic link resolution problem, as the "file"
module still performs a stat() at the end of execution to
provide the caller with information about the file.
However, this change is very simple, it will eliminate
unnecessary system calls in a number of use cases, and it
gets the "file" module closer to the desired end result.
2017-01-24 12:31:25 -08:00
.github Remove the hint to report module issue elsewhere. 2016-12-14 11:30:44 -05:00
bin adds more logging to ansible-connection (#20298) 2017-01-16 08:32:08 -05:00
contrib Add account ID grouping and attribute to ease multi-account management 2017-01-23 13:49:02 -05:00
docs docs fixes 2017-01-24 15:11:11 -05:00
examples Add pipeline-ish method using dd for file transfer over SSH (#18642) 2017-01-19 12:31:14 -05:00
hacking minor cleanups 2017-01-19 19:37:36 -05:00
lib/ansible Reduce the system calls performed by the "file" module 2017-01-24 12:31:25 -08:00
packaging Updating packaging releases 2017-01-16 13:06:09 -06:00
test Fix typo on test_ios_config_before_after_no_change test (#20565) 2017-01-24 11:16:16 -05:00
ticket_stubs Remove obsolete ticket stubs. 2016-12-08 11:35:20 -05:00
.coveragerc Update coverage exclusions. (#18675) 2016-11-29 22:46:56 -08:00
.gitattributes updated changelog with 1.8.2-4 content, added .gitattributes 2015-02-23 22:20:33 +00:00
.gitignore Enable more ios tests on Shippable. 2017-01-20 13:26:59 -08:00
.gitmodules Code cleanup. 2016-12-08 11:35:04 -05:00
.mailmap Add new mailmap entry for @willthames 2017-01-05 10:59:43 -05:00
.yamllint Lint YAML files under test/ 2016-11-11 14:50:57 -08:00
ansible-core-sitemap.xml Remove remnants of obsolete fireball mode. 2016-12-09 16:56:34 -07:00
CHANGELOG.md Add logstash_plugin to manange logstash plugins (#20592) 2017-01-24 15:52:51 +00:00
CODING_GUIDELINES.md Migrate basestring to a python3 compatible type (#17199) 2016-08-23 13:13:44 -07:00
CONTRIBUTING.md Update CONTRIBUTING.md with more recent developments 2016-03-23 15:32:29 +01:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile set cpus only if not set already 2017-01-19 23:09:55 -05:00
MANIFEST.in include all docs and tests in the sdist (#20004) 2017-01-10 13:30:33 -08:00
MODULE_GUIDELINES.md Move GUIDELINES.md from modules repo (#19313) 2016-12-14 11:46:14 -05:00
README.md Remove obsolete files and instructions. (#19079) 2016-12-09 12:42:29 -05:00
RELEASES.txt brought releases up to date 2016-11-17 10:57:44 -05:00
ROADMAP.rst Update ROADMAP (#20002) 2017-01-16 11:36:53 +00:00
setup.py Updating setup.py to remove extras specific paths 2016-12-08 11:35:19 -05:00
shippable.yml Disable pull of updated Shippable docker image. 2017-01-19 11:43:07 -08:00
tox.ini Pass the HOME environment variable to testenv in tox.ini 2017-01-19 12:06:16 -08:00
VERSION Bumping devel version to 2.3.0 2016-10-03 11:46:31 -05:00

README.md

PyPI version Build Status

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 rebase vs git merge for 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.