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
10019 commits 10 branches 167 tags 272 MiB
Python 99.5%
Shell 0.3%
HCL 0.1%
Find a file
follower 4be010b09b Clarify the port value always defaults to 3306 
While the [boto docs](https://github.com/boto/boto/blob/develop/boto/rds/__init__.py#L253) make it seem like the default value of `port` is changed depending on the engine chosen, AFAICT from looking at the code the default value is never changed from 3306.

I think the docs are intended to be read as "the default value used by <engine> is <port> so you should change `port` to that value".

If you don't specify the port value and chose the database engine as PostgreSQL you'll end up with a PostgreSQL instance running on port 3306.
2014-04-02 02:25:14 +13:00
bin Addresses #4109 Remove debug print statement 2014-03-27 11:51:22 -04:00
docs/man Fixes #6398 Add missing parameters to ansible-playbook manpage 2014-03-31 16:49:09 -04:00
docsite Add docs examples for regex_replace 2014-03-31 14:14:57 -04:00
examples Documentation/examples updates for new 1.6 accelerate options 2014-03-25 19:32:48 -05:00
hacking Add tesing deps installation into hacking/README 2014-03-23 00:42:51 +04: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 Apply extra vars after all other vars have been merged in a play 2014-03-31 15:31:10 -05:00
library Clarify the port value always defaults to 3306 2014-04-02 02:25:14 +13:00
packaging Merge pull request #6053 from cgtx/devel 2014-03-16 10:45:46 -05:00
plugins Make ssh_config paramiko 1.12/1.13 compatible 2014-03-26 17:34:04 -07:00
test Merge branch 'regexreplace' of git://github.com/jacobweber/ansible into jacobweber-regexreplace 2014-03-31 13:48:13 -04:00
.gitignore Add generated test files to .gitignore 2014-03-11 09:21:33 -04:00
CHANGELOG.md Update changelog for #5958 2014-03-31 13:51:21 -04:00
CODING_GUIDELINES.md Update CODING_GUIDELINES.md 2014-03-14 11:23:34 -05:00
CONTRIBUTING.md Update CONTRIBUTING.md 2014-03-31 18:48:28 -04:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile Adding a man page for ansible-vault 2014-03-17 10:02:54 -05: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 Update files for 1.5.1 release. 2014-03-10 17:40:36 -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