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
8863 commits 10 branches 167 tags 272 MiB
Python 99.5%
Shell 0.3%
HCL 0.1%
Find a file
Michael DeHaan fe7d3773ae Various tests using datafiles are being moved into the integration test framework (tests_new right now). 
The unit test infrastructure will remain for things that are mocked out and testable with out filesystem
side effects, and a few cases of things that might not be quite so much (like inventory) that can still
benefit from heavy access to the API.

See the 'tests_new/integration' directory, this will soon fold into tests_new.
2014-02-20 17:16:58 -05:00
bin Fixes #6082 Set vault password to None by default 2014-02-19 21:26:12 -05:00
docs/man Updated footer date and adding in misc. file generated by earlier doc update 2014-02-12 16:14:41 -06:00
docsite Added 'expanduser' filter to the docs 2014-02-20 13:51:01 -05:00
examples Config resoution order correction and documentation. 2014-02-14 14:34:58 -06:00
hacking Allow hacking/env-setup module path to use config file library path 2014-02-12 12:06:57 +10:00
legacy Various tests using datafiles are being moved into the integration test framework (tests_new right now). 2014-02-20 17:16:58 -05:00
lib/ansible Fixing bug in which playbook vars were not merged properly 2014-02-20 15:25:52 -05:00
library Adding the backup destination to the resut dictionary for lineinfile 2014-02-20 13:31:54 -05:00
packaging Fix spec changelog date again 2014-02-13 10:06:09 -05:00
plugins Save api id to index as an int instead of a list 2014-02-09 16:33:34 +00:00
test Various tests using datafiles are being moved into the integration test framework (tests_new right now). 2014-02-20 17:16:58 -05:00
tests_new Remove -e for echo in test_facts_d 2014-02-20 17:09:46 -05:00
.gitignore Further modifications to the module formatter to adjust to the new theme, and some misc docs text corrections. 2013-12-25 13:24:29 -05:00
CHANGELOG.md Update CHANGELOG.md 2014-02-13 19:49:46 -05:00
CODING_GUIDELINES.md Fix various typos in markdown documentation 2014-02-10 23:00:19 +00:00
CONTRIBUTING.md Update bug reporting instructions to refer to the issue template 2014-02-11 10:26:25 -05:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile Remove man3 stuff since this is available via ansible-doc, rpm target should 2014-01-03 11:06:45 -05:00
MANIFEST.in Add some docs/examples 2012-08-14 13:05:44 -04:00
README.md AnsibleWorks -> Ansible 2014-01-28 20:29:42 -05:00
RELEASES.txt Updating documentation for release 1.4.5 2014-02-12 15:46:05 -06:00
setup.py Tweak library installation path to default to /usr/share/ansible if specified 2014-02-17 14:45:15 -06:00
VERSION Version bump for 1.5 2013-11-21 16:33:23 -05:00

README.md

PyPI version

Ansible

Ansible is a radically simple configuration-management, deployment, task-execution, and multinode orchestration framework.

Read the documentation and more at http://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 a tarball of the last release, go to releases.ansible.com and you can also install with pip.

Design Principles

  • Dead simple setup
  • Super fast & parallel by default
  • No server or client daemons; use existing SSHd
  • No additional software required on client boxes
  • Modules can be written in ANY language
  • Awesome API for creating very powerful distributed scripts
  • Be usable as non-root
  • The easiest config management system to use, ever.

Get Involved

  • Read Contributing.md 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.
  • When submitting a bug report, include 1) the output of 'ansible --version', 2) what you expected to happen, 3) what actually happened, and 4) any relevant commands and output.
  • 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.
  • irc.freenode.net: #ansible

Branch Info

  • Releases are 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 "CONTRIBUTING.md" for process notes.

Author

Michael DeHaan -- michael@ansible.com

Ansible, Inc