38d49d240e
* test(yarn): add Alpine Linux support via apk Install nodejs and yarn via apk on Alpine, sharing the functional test block with the existing non-Alpine (pre-built binary) path. Extracts the test block into tests.yml to avoid duplication. Fixes #4270 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(yarn): skip Node.js runtime warnings in stderr processing Node.js 24 emits DeprecationWarning lines to stderr (e.g. for url.parse()) that are not JSON, causing _process_yarn_error to fail with "Unexpected stderr output from Yarn". Skip lines starting with "(node:" before attempting JSON parsing. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * test(yarn): add changelog fragment for #11943 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(yarn): only JSON-parse lines starting with '{' in stderr Node.js 24 emits multi-line DeprecationWarnings to stderr (e.g. the hint line "(Use `node --trace-deprecation ...`") that are not JSON and were tripping the "Unexpected stderr output from Yarn" failure. Yarn's structured output always starts with '{', so skip any line that doesn't. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * test(yarn): install sqlite on Alpine to fix nodejs 22 symbol error On Alpine 3.21 nodejs 22 requires SQLite session extension symbols (sqlite3session_*) that are not present in sqlite-libs; installing the full sqlite package provides them. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * test(yarn): refresh apk cache and upgrade sqlite-libs before installing nodejs The CI Alpine container may have a stale sqlite-libs that lacks the session extension symbols (sqlite3session_*) required by nodejs 22+. Force a cache refresh and upgrade sqlite-libs to the latest revision. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(yarn): warn on non-JSON stderr lines instead of silently skipping Non-JSON lines in stderr (e.g. Node.js runtime DeprecationWarnings) are surfaced to the user via module.warn() rather than being silently ignored, since their content and meaning are not known in advance. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * prefix yarn output line * Update changelogs/fragments/11943-yarn-nodejs-runtime-warnings.yml Co-authored-by: Felix Fontein <felix@fontein.de> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: Felix Fontein <felix@fontein.de>
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.18, ansible-core 2.19, ansible-core 2.20, ansible-core 2.21 releases and the current development version of ansible-core. Ansible-core versions before 2.18.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
Watchbutton →All Activityin 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 and the MIT 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.toml. This conforms to the REUSE specification.