* Adding the list-option for reading the registered repodata * adding a parameter list * if the parameter is set, return the output (as a dictionary) * adjusting the documentation for the new parameter * Adding changelot-fragment and link to the issue in the issue-tracker https://github.com/ansible-collections/community.general/issues/8777 * Adding description and example for the new list parameter * Adding type for new parameter list to argument_spec * Revert "Adding type for new parameter list to argument_spec" This reverts commit 6b86e8ba447a9b53e434c79d33c7fe260485b342. * Revert "Adding description and example for the new list parameter" This reverts commit db06dafb958f6aeffa38adeee85623904b26bbb1. * Adding a new module for reading the list of regiestered repositories I created a new module for reading the repositories based on a sub-procedure from the existing zypper_repository * Removing the changes to module zypper_repository because the list-option is not supposed to go into this module * removing the last change from the zypper_repository module * Fixing linter errors Adding extra lines before definitions adding the missing dash in the documentation removing the unused imports * Adding maintainer under BOTMETA, adding test and fixing suggestions I added the maintainer to BOTMETA I applied the suggestions on the code form the review I added a test for the new module to the existing zypper_repository-tests * Adding maintainer under BOTMETA, adding test and fixing suggestions I added the maintainer to BOTMETA I applied the suggestions on the code form the review I added a test for the new module to the existing zypper_repository-tests * Deleting the fragment because this will be created automatically I deleted the fragment because this will be created automatically based on the short_description and version_added * removing foreign commits from history that accidentily sneaked in with the last rebase * Update plugins/modules/zypper_repository_info.py Co-authored-by: Felix Fontein <felix@fontein.de> * Update .github/BOTMETA.yml Co-authored-by: Felix Fontein <felix@fontein.de> * Update plugins/modules/zypper_repository_info.py Co-authored-by: Felix Fontein <felix@fontein.de> * Update plugins/modules/zypper_repository_info.py Co-authored-by: Felix Fontein <felix@fontein.de> * Update plugins/modules/zypper_repository_info.py Co-authored-by: Felix Fontein <felix@fontein.de> * Update plugins/modules/zypper_repository_info.py Co-authored-by: Felix Fontein <felix@fontein.de> * removing irrelevant return fields from the sample * Quoting the line with the colon * fixing syntax errors in sam * removing duplicate Note section * Removing newline on sample-code * Update version_added to 9.5.0 Co-authored-by: Alexei Znamensky <103110+russoz@users.noreply.github.com> * Update description (notespelling) Co-authored-by: Felix Fontein <felix@fontein.de> * Update .github/BOTMETA.yml Co-authored-by: Felix Fontein <felix@fontein.de> * Update descriptino (notespelling URL) Co-authored-by: Felix Fontein <felix@fontein.de> * use module_utils.deps to include the parseString/parseXML module * clean up module and botmeta cleanup: * remove duplicate entry from botmeta * move imports below DOCUMENTATION * remove unused imports * add required key 'returned' * moving import and fixing syntax In this documentation example the return type is dict instead of dictionary: https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_documenting.html#return-block Also the from __future__ import should be at the beginning of the file, according to lint * Enabling check-mode because the module doesn't change anything anyways * indicate empty dictionary Co-authored-by: Alexei Znamensky <103110+russoz@users.noreply.github.com> * Update version_added Co-authored-by: Alexei Znamensky <103110+russoz@users.noreply.github.com> --------- Co-authored-by: Felix Fontein <felix@fontein.de> Co-authored-by: Alexei Znamensky <103110+russoz@users.noreply.github.com> |
||
---|---|---|
.azure-pipelines | ||
.github | ||
.reuse | ||
LICENSES | ||
changelogs | ||
docs/docsite | ||
meta | ||
plugins | ||
tests | ||
.gitignore | ||
CHANGELOG.md | ||
CHANGELOG.md.license | ||
CHANGELOG.rst | ||
CHANGELOG.rst.license | ||
CONTRIBUTING.md | ||
COPYING | ||
README.md | ||
commit-rights.md | ||
galaxy.yml |
README.md
Community General Collection
This repository contains the community.general
Ansible Collection. The collection is a part of the Ansible package and includes many modules and plugins supported by Ansible community which are not part of more specialized community collections.
You can find documentation for this collection on the Ansible docs site.
Please note that this collection does not support Windows targets. Only connection plugins included in this collection might support Windows targets, and will explicitly mention that in their documentation if they do so.
Code of Conduct
We follow Ansible Code of Conduct in all our interactions within this project.
If you encounter abusive behavior violating the Ansible Code of Conduct, please refer to the policy violations section of the Code of Conduct for information on how to raise a complaint.
Communication
-
Join the Ansible forum:
- Get Help: get help or help others. This is for questions about modules or plugins in the collection. Please add appropriate tags if you start new discussions.
- Tag
community-general
: discuss the collection itself, instead of specific modules or plugins. - Social Spaces: gather and interact with fellow enthusiasts.
- News & Announcements: track project-wide announcements including social events.
-
The Ansible Bullhorn newsletter: used to announce releases and important changes.
For more information about communication, see the Ansible communication guide.
Tested with Ansible
Tested with the current ansible-core 2.15, ansible-core 2.16, ansible-core 2.17, ansible-core 2.18 releases and the current development version of ansible-core. Ansible-core versions before 2.15.0 are not supported. This includes all ansible-base 2.10 and Ansible 2.9 releases.
External requirements
Some modules and plugins require external libraries. Please check the requirements for each plugin or module you use in the documentation to find out which requirements are needed.
Included content
Please check the included content on the Ansible Galaxy page for this collection or the documentation on the Ansible docs site.
Using this collection
This collection is shipped with the Ansible package. So if you have it installed, no more action is required.
If you have a minimal installation (only Ansible Core installed) or you want to use the latest version of the collection along with the whole Ansible package, you need to install the collection from Ansible Galaxy manually with the ansible-galaxy
command-line tool:
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
Note that if you install the collection manually, it will not be upgraded automatically when you upgrade the Ansible package. To upgrade the collection to the latest available version, run the following command:
ansible-galaxy collection install community.general --upgrade
You can also install a specific version of the collection, for example, if you need to downgrade when something is broken in the latest version (please report an issue in this repository). Use the following syntax where X.Y.Z
can be any available version:
ansible-galaxy collection install community.general:==X.Y.Z
See Ansible Using collections for more details.
Contributing to this collection
The content of this collection is made by good people just like you, a community of individuals collaborating on making the world better through developing automation software.
We are actively accepting new contributors.
All types of contributions are very welcome.
You don't know how to start? Refer to our contribution guide!
The current maintainers are listed in the commit-rights.md file. If you have questions or need help, feel free to mention them in the proposals.
You can find more information in the developer guide for collections, and in the Ansible Community Guide.
Also for some notes specific to this collection see our CONTRIBUTING documentation.
Running tests
See here.
Collection maintenance
To learn how to maintain / become a maintainer of this collection, refer to:
It is necessary for maintainers of this collection to be subscribed to:
- The collection itself (the
Watch
button →All Activity
in the upper right corner of the repository's homepage). - The "Changes Impacting Collection Contributors and Maintainers" issue.
They also should be subscribed to Ansible's The Bullhorn newsletter.
Publishing New Version
See the Releasing guidelines to learn how to release this collection.
Release notes
See the changelog.
Roadmap
In general, we plan to release a major version every six months, and minor versions every two months. Major versions can contain breaking changes, while minor versions only contain new features and bugfixes.
See this issue for information on releasing, versioning, and deprecation.
More information
- Ansible Collection overview
- Ansible User guide
- Ansible Developer guide
- Ansible Community code of conduct
Licensing
This collection is primarily licensed and distributed as a whole under the GNU General Public License v3.0 or later.
See LICENSES/GPL-3.0-or-later.txt for the full text.
Parts of the collection are licensed under the BSD 2-Clause license, the MIT license, and the PSF 2.0 license.
All files have a machine readable SDPX-License-Identifier:
comment denoting its respective license(s) or an equivalent entry in an accompanying .license
file. Only changelog fragments (which will not be part of a release) are covered by a blanket statement in .reuse/dep5
. This conforms to the REUSE specification.