mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-06-19 06:40:21 -07:00
Mirror of the Ansible Community General collection.
https://galaxy.ansible.com/ui/repo/published/community/general/
6aa851c6bc
* Added cyberarkpassword lookup plugin Added cyberarkpassword lookup plugin: It allows to retrieve credentials (password, sshkey) from CyberArk Digital Vault * Added Modules: cyberark_authentication & cyberark_user Added Modules: - cyberark_authentication: Logon/Logoff to CyberArk Vault - cyberark_user: user management These 2 modules use CyberArk Privileged Account Security Web Services SDK * Update cyberark_authentication.py * Update cyberark_user.py * Removed ternary conditional to comply with 2.4 * Replaced usage of iteritems() for items() to comply with python3 * PEP8 Updates * Fixed Doc Issues * Doc Fixes * More Doc Fixes * Removing cyberark_user module, and cyberark lookup plugin for initial approval of PR, and continue with 2 different PRs after PR #21764 is approved. * PEP8 Fixes * Moved cyberark modules to identity category From IRC #ansible-devel recommendation (@bcoca) I moved cyberark to identity category so the authorized maintainers can provide feedback and move it forward. * Updates based on community_review by bjolivot - Updated description lines to have full stops in the documentation section. - changed file to use delimiter-separated words instead of camel case - Updated AnsibleModule module_spec parameters to use mutually_exclusive, required_if and required_together parameters to avoid manual validation of the parameters. - Added comments for more readability. - Removed “required”: false as they are implicit. - Enhanced check_mode handling. * PEP8 Updates * Updates based on IRC Feedback June 6 * Fixed description for token item * Fixed Documentation RETURN string * Fixed PEP8 W291 trailing whitespace * Changes based on feedback from community review * Added import to_text from ansible.module_utils._text * Updates based on recommendation from community * Changed Exception for Error in friendly messages in try/except blocks * Updates based on community review (bcoca & dagwieers) * Fixed httplib for python3 (http.client) |
||
|---|---|---|
| .github | ||
| bin | ||
| contrib | ||
| docs | ||
| examples | ||
| hacking | ||
| lib/ansible | ||
| packaging | ||
| test | ||
| ticket_stubs | ||
| .coveragerc | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .mailmap | ||
| .yamllint | ||
| ansible-core-sitemap.xml | ||
| CHANGELOG.md | ||
| CODING_GUIDELINES.md | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| docsite_requirements.txt | ||
| Makefile | ||
| MANIFEST.in | ||
| MODULE_GUIDELINES.md | ||
| README.md | ||
| RELEASES.txt | ||
| requirements.txt | ||
| ROADMAP.rst | ||
| setup.py | ||
| shippable.yml | ||
| tox.ini | ||
| VERSION | ||
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.
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.