1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Find a file
2020-06-25 13:34:46 +02:00
.github Deprecate logicmonitor and logicmonitor_facts (#541) 2020-06-23 15:55:59 +02:00
changelogs pkgng: Add stdout and stderr to response object (#560) 2020-06-23 19:55:40 +02:00
meta Deprecate logicmonitor and logicmonitor_facts (#541) 2020-06-23 15:55:59 +02:00
plugins modules: fix seealso sections (#581) 2020-06-25 13:34:46 +02:00
scripts sanity: Add future boilerplate (#573) 2020-06-24 21:50:36 +02:00
tests sanity: Add future boilerplate (#573) 2020-06-24 21:50:36 +02:00
.gitignore Initial commit 2020-03-09 09:11:07 +00:00
CHANGELOG.rst Release 0.2.0 of community.general (#546) 2020-06-20 12:49:50 +02:00
COPYING Initial commit 2020-03-09 09:11:07 +00:00
galaxy.yml aix_filesystem - fix module_util pathing issue for ansible 2.9 (#567) 2020-06-23 13:42:32 +02:00
README.md Release 0.2.0 of community.general (#546) 2020-06-20 12:49:50 +02:00
shippable.yml Add Ansible 2.10 runs. (#531) 2020-06-18 11:20:05 +02:00

Run Status Codecov

Ansible Collection: community.general

This repo contains the community.general Ansible Collection.

The collection includes the modules and plugins supported by Ansible community.

Installation and Usage

Installing the Collection from Ansible Galaxy

Before using the General community collection, you need to install the collection with the ansible-galaxy CLI:

ansible-galaxy collection install community.general

You can also include it in a requirements.yml file and install it via ansible-galaxy collection install -r requirements.yml using the format:

collections:
- name: community.general

Testing and Development

If you want to develop new content for this collection or improve what is already here, the easiest way to work on the collection is to clone it into one of the configured COLLECTIONS_PATHS, and work on it there.

You can find more information in the developer guide for collections

Testing with ansible-test

See here.

Release notes

See here.

Publishing New Version

Basic instructions without release branches:

  1. Create changelogs/fragments/<version>.yml with release_summary: section (which must be a string, not a list).
  2. Run antsibull-changelog release --collection-flatmap yes
  3. Make sure CHANGELOG.rst and changelogs/changelog.yaml are added to git, and the deleted fragments have been removed.
  4. Tag the commit with <version>. Push changes and tag to the main repository.

More Information

TBD

Communication

We have a dedicated Working Group for Ansible development.

You can find other people interested on the following Freenode IRC channels -

  • #ansible - For general use questions and support.
  • #ansible-devel - For discussions on developer topics and code related to features or bugs.
  • #ansible-community - For discussions on community topics and community meetings.

For more information about communities, meetings and agendas see Community Wiki.

For more information about communication

License

GNU General Public License v3.0 or later

See LICENSE to see the full text.