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
9496 commits 10 branches 167 tags 272 MiB
Python 99.5%
Shell 0.3%
HCL 0.1%
Find a file
James Laska aacccd441b Add integration test for apt_repository 
Tests several ways to specify the repository.  For every repo added, the test
asserts that:

 * the apt-cache was updated as expected (depends on `update_cache` parameter)
 * the PPA key was installed (depends on `repo` format)
2014-03-14 13:07:12 -04:00
bin Implement new default cipher class AES256 2014-03-10 16:15:44 -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 Update index.rst 2014-03-13 19:30:01 -05:00
examples Merge pull request #6381 from franckcuny/doc-module-lang 2014-03-10 20:35:04 -05:00
hacking Remove obsolete module development docs 2014-02-22 15:51:59 +01: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 Be sure to return to the old directory if cwd is set in run_command 2014-03-13 16:24:29 -05:00
library Fix docs for ec2_lc module. 2014-03-14 12:01:23 -04:00
packaging Updating CHANGELOG/RELEASES in devel for 1.5.3 and older releases 2014-03-13 16:31:19 -05:00
plugins Rename lxc to libvirt_lxc 2014-03-11 16:16:24 -04:00
test Add integration test for apt_repository 2014-03-14 13:07:12 -04:00
.gitignore Add generated test files to .gitignore 2014-03-11 09:21:33 -04:00
CHANGELOG.md Updating CHANGELOG/RELEASES in devel for 1.5.3 and older releases 2014-03-13 16:31:19 -05:00
CODING_GUIDELINES.md Update CODING_GUIDELINES.md 2014-03-14 11:23:34 -05:00
CONTRIBUTING.md Update CONTRIBUTING.md 2014-03-03 16:43:04 -05:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile Revert "Adding a Makefile target for integration tests - "make integration"" 2014-02-26 09:30:16 -06:00
MANIFEST.in Add some docs/examples 2012-08-14 13:05:44 -04:00
README.md Update README.md 2014-02-21 12:58:09 -05:00
RELEASES.txt Updating CHANGELOG/RELEASES in devel for 1.5.3 and older releases 2014-03-13 16:31:19 -05:00
setup.py Added ansible-vault to the installer 2014-02-21 09:18:49 +01:00
VERSION Set version to 1.6 2014-03-03 12:51:52 -05:00

README.md

PyPI version

Ansible

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

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

  • Have a dead simple setup process and a minimal learning curve
  • Be super fast & parallel by default
  • Require no server or client daemons; use existing SSHd
  • Use a language that is both machine and human friendly
  • Focus on security and easy auditability/review/rewriting of content
  • Manage remote machines instantly, without bootstrapping
  • 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 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.
  • 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