New release v2.12.3 (#77158)

Signed-off-by: Christian M. Adams <chadams@redhat.com>

.azure-pipelines/azure-pipelines.yml

@@ -26,8 +26,6 @@ variables:
     value: ansible
   - name: coverageBranches
     value: devel
-  - name: pipelinesCoverage
-    value: coverage
   - name: entryPoint
     value: test/utils/shippable/shippable.sh
   - name: fetchDepth
@@ -120,8 +118,6 @@ stages:
               test: centos6
             - name: CentOS 7
               test: centos7
-            - name: CentOS 8
-              test: centos8
             - name: Fedora 33
               test: fedora33
             - name: Fedora 34
@@ -194,8 +190,6 @@ stages:
               test: centos6
             - name: CentOS 7
               test: centos7
-            - name: CentOS 8
-              test: centos8
             - name: Fedora 33
               test: fedora33
             - name: Fedora 34

.azure-pipelines/scripts/aggregate-coverage.sh

@@ -9,9 +9,9 @@ PATH="${PWD}/bin:${PATH}"
 
 mkdir "${agent_temp_directory}/coverage/"
 
-options=(--venv --venv-system-site-packages --color -v)
+options=(--venv --color -v)
 
-ansible-test coverage combine --export "${agent_temp_directory}/coverage/" "${options[@]}"
+ansible-test coverage combine --group-by command --export "${agent_temp_directory}/coverage/" "${options[@]}"
 
 if ansible-test coverage analyze targets generate --help >/dev/null 2>&1; then
     # Only analyze coverage if the installed version of ansible-test supports it.

.azure-pipelines/scripts/publish-codecov.py

@@ -0,0 +1,101 @@
+#!/usr/bin/env python
+"""
+Upload code coverage reports to codecov.io.
+Multiple coverage files from multiple languages are accepted and aggregated after upload.
+Python coverage, as well as PowerShell and Python stubs can all be uploaded.
+"""
+
+import argparse
+import dataclasses
+import pathlib
+import shutil
+import subprocess
+import tempfile
+import typing as t
+import urllib.request
+
+
+@dataclasses.dataclass(frozen=True)
+class CoverageFile:
+    name: str
+    path: pathlib.Path
+    flags: t.List[str]
+
+
+@dataclasses.dataclass(frozen=True)
+class Args:
+    dry_run: bool
+    path: pathlib.Path
+
+
+def parse_args() -> Args:
+    parser = argparse.ArgumentParser()
+    parser.add_argument('-n', '--dry-run', action='store_true')
+    parser.add_argument('path', type=pathlib.Path)
+
+    args = parser.parse_args()
+
+    # Store arguments in a typed dataclass
+    fields = dataclasses.fields(Args)
+    kwargs = {field.name: getattr(args, field.name) for field in fields}
+
+    return Args(**kwargs)
+
+
+def process_files(directory: pathlib.Path) -> t.Tuple[CoverageFile, ...]:
+    processed = []
+    for file in directory.joinpath('reports').glob('coverage*.xml'):
+        name = file.stem.replace('coverage=', '')
+
+        # Get flags from name
+        flags = name.replace('-powershell', '').split('=')  # Drop '-powershell' suffix
+        flags = [flag if not flag.startswith('stub') else flag.split('-')[0] for flag in flags]  # Remove "-01" from stub files
+
+        processed.append(CoverageFile(name, file, flags))
+
+    return tuple(processed)
+
+
+def upload_files(codecov_bin: pathlib.Path, files: t.Tuple[CoverageFile, ...], dry_run: bool = False) -> None:
+    for file in files:
+        cmd = [
+            str(codecov_bin),
+            '--name', file.name,
+            '--file', str(file.path),
+        ]
+        for flag in file.flags:
+            cmd.extend(['--flags', flag])
+
+        if dry_run:
+            print(f'DRY-RUN: Would run command: {cmd}')
+            continue
+
+        subprocess.run(cmd, check=True)
+
+
+def download_file(url: str, dest: pathlib.Path, flags: int, dry_run: bool = False) -> None:
+    if dry_run:
+        print(f'DRY-RUN: Would download {url} to {dest} and set mode to {flags:o}')
+        return
+
+    with urllib.request.urlopen(url) as resp:
+        with dest.open('w+b') as f:
+            # Read data in chunks rather than all at once
+            shutil.copyfileobj(resp, f, 64 * 1024)
+
+    dest.chmod(flags)
+
+
+def main():
+    args = parse_args()
+    url = 'https://ci-files.testing.ansible.com/codecov/linux/codecov'
+    with tempfile.TemporaryDirectory(prefix='codecov-') as tmpdir:
+        codecov_bin = pathlib.Path(tmpdir) / 'codecov'
+        download_file(url, codecov_bin, 0o755, args.dry_run)
+
+        files = process_files(args.path)
+        upload_files(codecov_bin, files, args.dry_run)
+
+
+if __name__ == '__main__':
+    main()

.azure-pipelines/scripts/publish-codecov.sh

@@ -1,27 +0,0 @@
-#!/usr/bin/env bash
-# Upload code coverage reports to codecov.io.
-# Multiple coverage files from multiple languages are accepted and aggregated after upload.
-# Python coverage, as well as PowerShell and Python stubs can all be uploaded.
-
-set -o pipefail -eu
-
-output_path="$1"
-
-curl --silent --show-error https://ansible-ci-files.s3.us-east-1.amazonaws.com/codecov/codecov.sh > codecov.sh
-
-for file in "${output_path}"/reports/coverage*.xml; do
-    name="${file}"
-    name="${name##*/}"  # remove path
-    name="${name##coverage=}"  # remove 'coverage=' prefix if present
-    name="${name%.xml}"  # remove '.xml' suffix
-
-    bash codecov.sh \
-        -f "${file}" \
-        -n "${name}" \
-        -X coveragepy \
-        -X gcov \
-        -X fix \
-        -X search \
-        -X xcode \
-        || echo "Failed to upload code coverage report to codecov.io: ${file}"
-done

.azure-pipelines/scripts/report-coverage.sh

@@ -14,4 +14,4 @@ fi
 
 # Generate stubs using docker (if supported) otherwise fall back to using a virtual environment instead.
 # The use of docker is required when Powershell code is present, but Ansible 2.12 was the first version to support --docker with coverage.
-ansible-test coverage xml --stub --docker --color -v || ansible-test coverage xml --stub --venv --venv-system-site-packages --color -v
+ansible-test coverage xml --group-by command --stub --docker --color -v || ansible-test coverage xml --group-by command --stub --venv --color -v

.azure-pipelines/templates/coverage.yml

@@ -23,20 +23,7 @@ jobs:
       - bash: .azure-pipelines/scripts/report-coverage.sh
         displayName: Generate Coverage Report
         condition: gt(variables.coverageFileCount, 0)
-      - task: PublishCodeCoverageResults@1
-        inputs:
-          codeCoverageTool: Cobertura
-          # Azure Pipelines only accepts a single coverage data file.
-          # That means only Python or PowerShell coverage can be uploaded, but not both.
-          # Set the "pipelinesCoverage" variable to determine which type is uploaded.
-          # Use "coverage" for Python and "coverage-powershell" for PowerShell.
-          summaryFileLocation: "$(outputPath)/reports/$(pipelinesCoverage).xml"
-          # Override the root (sources) path specified in the coverage XML files.
-          # This allows coverage to be reported in Azure Pipelines even if the report was generated in a container.
-          pathToSources: "$(Agent.BuildDirectory)/$(checkoutPath)"
-        displayName: Publish to Azure Pipelines
-        condition: gt(variables.coverageFileCount, 0)
-      - bash: .azure-pipelines/scripts/publish-codecov.sh "$(outputPath)"
+      - bash: .azure-pipelines/scripts/publish-codecov.py "$(outputPath)"
         displayName: Publish to codecov.io
         condition: gt(variables.coverageFileCount, 0)
         continueOnError: true

README.rst

@@ -32,8 +32,6 @@ You can install a released version of Ansible with ``pip`` or a package manager.
 `installation guide <https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html>`_ for details on installing Ansible
 on a variety of platforms.
 
-Red Hat offers supported builds of `Ansible Engine <https://www.ansible.com/ansible-engine>`_.
-
 Power users and developers can run the ``devel`` branch, which has the latest
 features and fixes, directly. Although it is reasonably stable, you are more likely to encounter
 breaking changes when running the ``devel`` branch. We recommend getting involved

changelogs/CHANGELOG-v2.12.rst

@@ -0,0 +1,565 @@
+====================================================
+ansible-core 2.12 "Dazed and Confused" Release Notes
+====================================================
+
+.. contents:: Topics
+
+
+v2.12.3
+=======
+
+Release Summary
+---------------
+
+| Release Date: 2022-02-28
+| `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+
+Minor Changes
+-------------
+
+- The collection loader now reports a Python warning if an attempt is made to install the Ansible collection loader a second time. Previously this condition was reported using an Ansible warning.
+- ansible-test - Installation of ``cryptography`` is no longer version constrained when ``openssl`` 1.1.0 or later is installed.
+- ansible-test - Requirements for the plugin import test are now frozen.
+- ansible-test - The ``pip`` and ``wheel`` packages are removed from all sanity test virtual environments after installation completes to reduce their size. Previously they were only removed from the environments used for the ``import`` sanity test.
+- ansible-test - The hash for all managed sanity test virtual environments has changed. Containers that include ``ansible-test sanity --prime-venvs`` will need to be rebuilt to continue using primed virtual environments.
+- ansible-test - Update ``pip`` used to bootstrap remote FreeBSD instances from version 20.3.4 to 21.3.1.
+- ansible-test - Update the ``alpine`` container to version 3.3.0. This updates the base image from 3.14.2 to 3.15.0, which includes support for installing binary wheels using pip.
+- ansible-test - Update the ``galaxy`` test plugin to get its container from a copy on quay.io.
+- ansible-test - Update the ``openshift`` test plugin to get its container from a copy on quay.io.
+- junit callback - Add support for replacing the directory portion of out-of-tree relative task paths with a placeholder.
+
+Bugfixes
+--------
+
+- ansible-test - All virtual environments managed by ansible-test are marked as usable after being bootstrapped, to avoid errors caused by use of incomplete environments. Previously this was only done for sanity tests. Existing environments from previous versions of ansible-test will be recreated on demand due to lacking the new marker.
+- ansible-test - Fix the ``validate-modules`` sanity test to avoid double-loading the collection loader and possibly failing on import of the ``packaging`` module.
+- ansible-test - Import ``yaml.cyaml.CParser`` instead of ``_yaml.CParser`` in the ``yamllint`` sanity test.
+- ansible-test - Replace the directory portion of out-of-tree paths in JUnit files from integration tests with the ``out-of-tree:`` prefix.
+- ansible-test - Sanity tests run with the ``--requirements` option for Python 2.x now install ``virtualenv`` when it is missing or too old. Previously it was only installed if missing. Version 16.7.12 is now installed instead of the latest version on Python 2.7.
+- ansible-test - The ``import`` sanity test no longer reports errors about ``packaging`` being missing when testing collections.
+- ansible-test - Update the ``default`` containers to version 4.2.0.
+- ansible-test - Use https://ci-files.testing.ansible.com/ for instance bootstrapping instead of an S3 endpoint.
+- ansible-test - Use relative paths in JUnit files generated during integration test runs.
+- ansible-test - Virtual environments managed by ansible-test now use consistent versions of ``pip``, ``setuptools`` and ``wheel``. This avoids issues with virtual environments containing outdated or dysfunctional versions of these tools. The initial bootstrapping of ``pip`` is done by ansible-test from an HTTPS endpoint instead of creating the virtual environment with it already present.
+- cleaning facts will now only warn about the variable name and not post the content, which can be undesireable to disclose
+- correctly inherit vars from parent in block (https://github.com/ansible/ansible/issues/75286).
+- gather_facts action now handles the move of base connection plugin types into collections to add/prevent subset argument correctly
+- junit callback - Fix traceback during automatic fact gathering when using relative paths.
+- junit callback - Fix unicode error when handling non-ASCII task paths.
+- ssh connection now uses more correct host source as play_context can ignore loop/delegation variations.
+- task_executor reverts the change to push facts into delegated vars on loop finalization as result managing code already handles this and was duplicating effort to wrong result.
+- template lookup - restore inadvertently deleted default for ``convert_data`` (https://github.com/ansible/ansible/issues/77004)
+- unarchive - Make extraction work when the LANGUAGE environment variable is set to a non-English locale.
+
+v2.12.2
+=======
+
+Release Summary
+---------------
+
+| Release Date: 2022-01-31
+| `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+
+Bugfixes
+--------
+
+- Fix ``AttributeError`` when providing password file via ``--connection-password-file`` (https://github.com/ansible/ansible/issues/76530)
+- Fix ``end_play`` to end the current play only (https://github.com/ansible/ansible/issues/76672)
+- Templating - Ensure we catch exceptions when getting ``.filters`` and ``.tests`` attributes on their respective plugins and properly error, instead of aborting which results in no filters being added to the jinja2 environment
+- ``Templar.copy_with_new_env`` - set the ``finalize`` method of the new ``Templar`` object for the new environment (https://github.com/ansible/ansible/issues/76379)
+- ansible-config avoid showing _terms and _input when --only-changed.
+- ansible-galaxy - Fix using the '--ignore-certs' option when there is no server-specific configuration for the Galaxy server.
+- ansible-galaxy collection build - Ignore any existing ``MANIFEST.json`` and ``FILES.json`` in the root directory when building a collection.
+- ansible-test - Fix the ``import`` sanity test to work properly when Ansible's built-in vendoring support is in use.
+- ansible-test - Fix traceback in the ``validate-modules`` sanity test when testing an Ansible module without any callables.
+- ansible-test - Fix traceback when running from an install and delegating execution to a different Python interpreter.
+- ansible-test - Show an error message instead of a traceback when running outside of a supported directory.
+- ansible-test - Update help links to reference ``ansible-core`` instead of ``ansible``.
+- ansible-test - Update unit tests to use the ``--forked`` option instead of the deprecated ``--boxed`` option.
+- async - Improve performance of sending async callback events by never sending the full task through the queue (https://github.com/ansible/ansible/issues/76729)
+- default callback - Ensure we compare FQCN also in lockstep logic, to ensure using the FQCN of a strategy plugin triggers the correct behavior in the default callback plugin. (https://github.com/ansible/ansible/issues/76782)
+- hostname - Do not require SystemdStrategy subclasses for every distro (https://github.com/ansible/ansible/issues/76792)
+- include_vars, properly initialize variable as there is corner case in which it can end up referenced and not defined
+- ssh connection - properly quote controlpersist path given by user to avoid issues with spaces and other characters
+- ssh connection avoid parsing ssh cli debug lines as they can match expected output at high verbosities.
+- sudo become plugin, fix handling of non interactive flags, previous substitution was too naive
+- unarchive - Fix zip archive file listing that caused issues with content postprocessing (https://github.com/ansible/ansible/issues/76067).
+- yum - prevent storing unnecessary cache data by running `yum makecache fast` (https://github.com/ansible/ansible/issues/76336)
+
+v2.12.1
+=======
+
+Release Summary
+---------------
+
+| Release Date: 2021-12-06
+| `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+
+Minor Changes
+-------------
+
+- jinja2_native - keep same behavior on Python 3.10.
+
+Bugfixes
+--------
+
+- Ansible.ModuleUtils.LinkUtil - Ignore the ``LIB`` environment variable when loading the ``LinkUtil`` code
+- ansible-test - Automatic target requirements installation is now based on the target environment instead of the controller environment.
+- ansible-test - Fix Python real prefix detection when running in a ``venv`` virtual environment.
+- ansible-test - Fix installation and usage of ``pyyaml`` requirement for the ``import`` sanity test for collections.
+- ansible-test - Fix traceback in ``import`` sanity test on Python 2.7 when ``pip`` is not available.
+- ansible-test - Relocate constants to eliminate symlink.
+- ansible-test - Target integration test requirements are now correctly installed for target environments running on the controller.
+- ansible-test - Update the ``default`` containers to version 4.1.1, which includes the updated ``import`` sanity test requirements.
+- ansible-test - Use the legacy collection loader for ``import`` sanity tests on target-only Python versions.
+- set_fact/include_vars correctly handle delegation assignments within loops
+- setup - detect docker container with check for ./dockerenv or ./dockinit (https://github.com/ansible/ansible/pull/74349).
+- validate_argument_spec - Skip suboption validation if the top level option is an invalid type (https://github.com/ansible/ansible/issues/75612).
+
+v2.12.0
+=======
+
+Release Summary
+---------------
+
+| Release Date: 2021-11-05
+| `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+
+Major Changes
+-------------
+
+- Python Controller Requirement - Python 3.8 or newer is required for the control node (the machine that runs Ansible) (https://github.com/ansible/ansible/pull/74013)
+- ansible-test - All "cloud" plugins which use containers can now be used with all POSIX and Windows hosts. Previously the plugins did not work with Windows at all, and support for hosts created with the ``--remote`` option was inconsistent.
+- ansible-test - Collections can now specify controller and target specific integration test requirements and constraints. If provided, they take precedence over the previously available requirements and constraints files.
+- ansible-test - Integration tests run with the ``integration`` command can now be executed on two separate hosts instead of always running on the controller. The target host can be one provided by ``ansible-test`` or by the user, as long as it is accessible using SSH.
+- ansible-test - Most container features are now supported under Podman. Previously a symbolic link for ``docker`` pointing to ``podman`` was required.
+- ansible-test - New ``--controller`` and ``--target`` / ``--target-python`` options have been added to allow more control over test environments.
+- ansible-test - Python 3.8 - 3.10 are now required to run ``ansible-test``, thus matching the Ansible controller Python requirements. Older Python versions (2.6 - 2.7 and 3.5 - 3.10) can still be the target for relevant tests.
+- ansible-test - SSH port forwarding and redirection is now used exclusively to make container ports available on non-container hosts. When testing on POSIX systems this requires SSH login as root. Previously SSH port forwarding was combined with firewall rules or other port redirection methods, with some platforms being unsupported.
+- ansible-test - Sanity tests always run in isolated Python virtual environments specific to the requirements of each test. The environments are cached.
+- ansible-test - Sanity tests are now separated into two categories, controller and target. All tests except ``import`` and ``compile`` are controller tests. The controller tests always run using the same Python version used to run ``ansible-test``. The target tests use the Python version(s) specified by the user, or all available Python versions.
+- ansible-test - Sanity tests now use fully pinned requirements that are independent of each other and other test types.
+- ansible-test - Tests run with the ``centos6`` and ``default`` test containers now use a PyPI proxy container to access PyPI when Python 2.6 is used. This allows tests running under Python 2.6 to continue functioning even though PyPI is discontinuing support for non-SNI capable clients.
+- ansible-test - The ``future-import-boilerplate`` and ``metaclass-boilerplate`` sanity tests are limited to remote-only code. Additionally, they are skipped for collections which declare no support for Python 2.x.
+- ansible-test - The ``import`` and ``compile`` sanity tests limit remote-only Python version checks to remote-only code.
+- ansible-test - Unit tests for controller-only code now require Python 3.8 or later.
+- ansible-test - Version neutral sanity tests now require Python 3.8 or later.
+- junit callback - The ``junit_xml`` and ``ordereddict`` Python modules are no longer required to use the ``junit`` callback plugin.
+
+Minor Changes
+-------------
+
+- Add ``end_batch`` meta task.
+- Allow connection and become passwords to be set by file/executable script. Also document this was already the case for vault.
+- CLI - Remove ``__requires__`` attribute for ``pkg_resources``
+- Collections can define action_groups in ``meta/runtime.yml``.
+- Introduce a config option to enable/disable emitting warning about Jinja2 version being old for ``jinja2_native``. The option is on by default, only in CI it is off.
+- Make the code structure of ansible-doc's generic snippet feature more maintainable.
+- On RHEL 9, CentOS Stream 9 etc., use /usr/bin/python3 as the default interpreter; /usr/libexec/platform-python is just a backwards-compatibility symbolic link there.
+- PowerShell - Added support for optional module_util imports by scanning for ``-Optional`` at the end of the import declaration
+- Python 2.6 Target Support - Deprecate Python 2.6 for targets, requiring Python 2.7 or newer. ``ansible-core==2.13`` will drop support for Python 2.6. (https://github.com/ansible/ansible/pull/74165)
+- Task - Add a resolved_action attribute for Task objects to get the final resolved plugin.
+- Templar - remove ``_fail_on_lookup_errors`` and ``_fail_on_filter_errors`` instance variables that were never used. (https://github.com/ansible/ansible/pull/73785)
+- The AnsiballZ Python wrapper now changes the working directory to ``~`` or ``/`` if the current one is not accessible. This allows become to drop privileges on macOS when using pipelining.
+- Update test container ansible-core-test-container to version 3.6.0
+- Update test container ansible-core-test-container to version 3.7.0
+- Update test container default-test-container to version 3.6.0
+- Update test container default-test-container to version 3.7.0
+- Update vendored copy of ``six`` to 1.16.0 to eliminate warnings for deprecated python loader methods in Python 3.10+ (https://github.com/ansible/ansible/issues/74659)
+- Update vendored copy of distro to 1.6.0
+- Vendor ``distutils.version`` due to it's deprecation in Python 3.10 and impending removal in Python 3.12 (https://github.com/ansible/ansible/issues/74599)
+- YAML parsing - Create common utils for loading and dumping YAML that prefer the C extensions if available
+- ``include_role`` - Allow use of ``omit`` in the ``from_*`` arguments (https://github.com/ansible/ansible/issues/66349)
+- ``uri``/``get_url`` - Expose ``unredirected_headers`` to modules to allow user control
+- `ansible.plugins.callback.CallbackBase.host_label()` has been factored out as a static method (https://github.com/ansible/ansible/pull/73814).
+- action_groups can include actions from other groups by using the special ``metadata`` dictionary field.
+- add a quick short circuit when checking if a string is a template to improve performance on large strings (https://github.com/ansible/ansible/issues/74336)
+- add host label to retry print statements
+- added new function to module utils to choose best possible locale.
+- adds the ``undef`` keyword to the templating environment. This allows for directly creating Undefined values in templates. It is most useful for providing a hint for variables which must be overridden.
+- ansbile-doc now also shows snippets for inventory and lookup, adding to existing modules.
+- ansible adhoc, clarified the help to some options, also added some comments to code.
+- ansible-cli - remove unnecessary trailing space in ``ansible --version`` (https://github.com/ansible/ansible/issues/74875).
+- ansible-config can now list and dump for specific documentable plugins by specifying them in the command line
+- ansible-config has new 'init' option to create, highly commented, example configurations as ini (ansible.cfg), environment variables (shell) or Ansible variable files (YAML)
+- ansible-config now supports displaying plugin configuration info.
+- ansible-doc - ``version_added`` in ``attributes`` now comes with ``version_added_collection`` (https://github.com/ansible/ansible/pull/74602).
+- ansible-doc - show ``version_added`` for the plugin/module itself in text output, and improve ``version_added`` formatting (https://github.com/ansible/ansible/pull/73602).
+- ansible-doc now supports 'attributes' for plugins as per proposal.
+- ansible-doc pretty cli options output.
+- ansible-doc, improve handling of rstisms, try to make the display more meaningfull for the terminal users.
+- ansible-galaxy - Allow specification of client_id override value for Keycloak Token (https://github.com/ansible/ansible/issues/75593).
+- ansible-galaxy - Allow validate_certs to be configured for individual Galaxy servers (https://github.com/ansible/ansible/issues/75677).
+- ansible-galaxy - Installing a collection from a git repository without specifying a version (or using the version ``HEAD``) will clone the repository using --depth=1.
+- ansible-galaxy - Non-HTTP exceptions from Galaxy servers are now a warning and only fatal if the collection to download|install|verify is not available from any of the servers (https://github.com/ansible/ansible/issues/75443).
+- ansible-test - A new ``base`` test container is available. It is similar to the ``default`` test container, but contains no pre-installed Python packages other than ``pip`` and its dependencies.
+- ansible-test - Add RHEL 8.4 as a remote.
+- ansible-test - Add ``--prime-venvs`` option to create virtual environments without running tests.
+- ansible-test - Add constraint for ``decorator`` for Python versions prior to 3.5.
+- ansible-test - Add support for Windows Server 2022.
+- ansible-test - Add support for an ansible-test configuration file in collections under ``tests/config.yml``.
+- ansible-test - Add support for testing with Python 3.10.
+- ansible-test - Added a ``--prime-containers`` option to support downloading containers without running tests.
+- ansible-test - Adding DigitalOcean cloud support to ansible-test (https://github.com/ansible/ansible/pull/74222).
+- ansible-test - All "cloud" plugins have been refactored for more consistency. For those that use docker containers, management of the containers has been standardized.
+- ansible-test - All "cloud" plugins now use fixed hostnames and ports in tests. Previously some tests used IP addresses and/or randomly assigned ports.
+- ansible-test - Changes made to the ``hosts`` file on test systems are now done using an Ansible playbook for both POSIX and Windows systems. Changes are applied before a test target runs and are reverted after the test target finishes.
+- ansible-test - Clean up code in the cloud plugins.
+- ansible-test - Collections can declare their remote-only code (modules/module_utils and related tests) as controller-only.
+- ansible-test - Collections can limit the Python versions used for testing their remote-only code (modules/module_utils and related tests).
+- ansible-test - Command line help has been updated to hide the ``--remote`` option (and related options) when the user lacks an API key to use the feature.
+- ansible-test - Constraints provided by ``ansible-test`` for Python package installs have been reduced.
+- ansible-test - Default settings are now applied to unknown versions of known ``--remote`` platforms.
+- ansible-test - Distribution specific test containers have been updated to version 3.0.0.
+- ansible-test - Environment checking (``pip``, ``python``, ``~/.ssh/known_hosts``, etc.) is no longer performed when running integration tests.
+- ansible-test - Environment variables exposed by "cloud" plugins are now available to the controller for role based tests. Previously only script based tests had access to the exposed environment variables.
+- ansible-test - Fedora 32 and 33 (``fedora32`` and ``fedora33``) containers have been updated and now allow for ssh in more container environments.
+- ansible-test - Fedora 34 (``fedora34``) container has been added.
+- ansible-test - Installation of ``cryptography`` no longer occurs when it is already installed. This avoids downgrading existing OS packages.
+- ansible-test - Minor code cleanup.
+- ansible-test - More efficient string splitting.
+- ansible-test - Most scripts used internally by ``ansible-test`` no longer have a shebang or the executable bit set.
+- ansible-test - Move code from ``_data`` directory to ``_util`` directory.
+- ansible-test - Relocate change classification code.
+- ansible-test - Remove CI provider support for Shippable, now that the service has been discontinued.
+- ansible-test - Remove check for legacy ``core`` and ``extras`` directories.
+- ansible-test - Remove deprecated container ``fedora32``.
+- ansible-test - Remove deprecated remote platforms ``freebsd/11.4`` and ``rhel/8.3```.
+- ansible-test - Removed the warning filter for ``PyYAML`` in the ``import`` sanity test.
+- ansible-test - Removed unused pip constraints. Collections may need to add their own constraints if they depended on any which were removed.
+- ansible-test - Reorganize code for individual commands.
+- ansible-test - Reorganize integration test implementation by command.
+- ansible-test - Rewrite the ``compile`` sanity test to improve error handling and support Python 3.10.
+- ansible-test - Sanity test warnings relating to Python version support have been improved.
+- ansible-test - Set minimum version constraints for ``pytest``.
+- ansible-test - Split out shell command implementation.
+- ansible-test - The "injector" scripts are now generated at runtime to avoid issues with symlinks and shebangs.
+- ansible-test - The HTTP Tester can now be used without the ``--docker`` or `--remote`` options. It still requires use of the ``docker`` command to run the container.
+- ansible-test - The HTTP Tester has been converted to a "cloud" plugin and can now be requested using the ``cloud/httptester`` alias. The original ``needs/httptester`` alias is still supported for backwards compatibility.
+- ansible-test - The ``--docker-keep-git`` option (used only for testing ansible-core) has been renamed to ``--keep-git``.
+- ansible-test - The ``--python`` option can be used without another delegation option such as the ``--venv`` or ``--docker`` options.
+- ansible-test - The ``ansible-test coverage`` commands ``combine``, ``report``, ``html`` and ``xml`` now support delegation.
+- ansible-test - The ``default`` test container has been updated to version 3.4.0 and now uses Python 3.9 by default instead of Python 3.6.
+- ansible-test - The ``docker run`` option ``--link`` is no longer used to connect test containers. As a result, changes are made to the ``/etc/hosts`` file as needed on all test containers. Previously containers which were used with the ``--link`` option did not require changes to the ``/etc/hosts`` file.
+- ansible-test - The ``import`` sanity test now requires that Ansible modules guard instantiation of ``AnsibleModule`` with a ``if __name__ == '__main__'`` conditional, or equivalent logic.
+- ansible-test - The ``import`` sanity test now requires that non-modules do not instantiate ``AnsibleModule`` on import.
+- ansible-test - The ``validate-modules`` sanity test codes ``ansible-deprecated-module`` and ``collection-deprecated-module`` have been added.
+- ansible-test - The ``validate-modules`` sanity test codes ``last-line-main-call``, ``missing-if-name-main`` and ``missing-main-call`` have been removed.
+- ansible-test - The ``validate-modules`` sanity test no longer enforces the ``missing-if-name-main``, ``last-line-main-call`` or ``missing-main-call`` checks on non-deleted Ansible modules. Modules are still required to instantiate ``AnsibleModule`` when ``__name__ == '__main__'``.
+- ansible-test - Unit tests are now run in separate contexts (``controller``, ``modules``, ``module_utils``), each using separate invocations of ``pytest``.
+- ansible-test - Unit tests other than ``modules`` and ``module_utils`` are now run only on Python versions supported by the controller (Python 3.8+).
+- ansible-test - Update ``typed-ast`` constraint to version 1.4.3 for compatibility with Python 3.10.
+- ansible-test - Update distribution test containers from version 2.0.1 to 2.0.2.
+- ansible-test - Update the Ansible Core and Ansible Collection default test containers to 3.2.0 and 3.2.2 respectively.
+- ansible-test - Update the ``base`` and ``default`` containers from Python 3.10.0rc2 to 3.10.0.
+- ansible-test - Update the ``import`` sanity test to avoid a new warning in Python 3.10.
+- ansible-test - Update the ``runtime-metadata`` sanity test to handle a new warning on Python 3.10.
+- ansible-test - Updated the ``default`` containers to version 4.0.1.
+- ansible-test - Updated the help message for failed tests in the ``azure`` test plugin.
+- ansible-test - Upgrade ``pylint`` to version 2.9.3 and update its dependencies to the latest versions as well.
+- ansible-test - Using an unknown ``--docker`` or ``--remote`` environment now requires specifying a Python version.
+- ansible-test - add freebsd/13.0 as a remote option.
+- ansible-test - aws creates and exposes a new tiny_prefix variable to provide a shorter prefix for the AWS tests.
+- ansible-test - display recent ``ssh`` debug logs after connection failures (https://github.com/ansible/ansible/pull/75374)
+- ansible-test - validate-modules now properly checks ``attributes`` for plugins (https://github.com/ansible/ansible/pull/74602).
+- ansible-test - virtualenv-isolated.sh is no longer provided. Prefer virtualenv.sh in its place.
+- ansible-test validate-modules - enforce that ``_info`` and ``_facts`` modules set ``supports_check_mode=True`` (https://github.com/ansible/ansible/pull/75324).
+- ansible-vault - remove support for ``PyCrypto`` (https://github.com/ansible/ansible/issues/72646)
+- apt - added an ``allow_downgrade`` option to enable safe downgrade of packages without using ``force`` which doesn't verify signatures (https://github.com/ansible/ansible/issues/29451, https://github.com/ansible/ansible/pull/74852).
+- apt, added a 'lock_timeout' to be more resilient when encountering the apt db already locked and handle it w/o haveing to rerun task.
+- async tasks - the use of the task-level ``ANSIBLE_ASYNC_DIR`` variable within ``environment:`` is no longer valid. Use the shell configuration variable ``async_dir`` instead.
+- async_wrapper, better reporting on timeout, slight refactor on reporting itself.
+- basic module_util - Clean up ``selinux`` compat import.
+- blockinfile - Remove unused code for Ansible 1.x.
+- cache base - More efficient string splitting.
+- callback API - implemented ``v2_runner_on_async_ok`` and ``v2_runner_on_async_failed`` callbacks (https://github.com/ansible/ansible/pull/74953).
+- cli scripts - remove trailing blank space in help after newline when outputting.
+- collection - match skip message as per role installation.
+- command - update the user warning message to point out command name (https://github.com/ansible/ansible/pull/74475).
+- config lookup now can handle plugin settings.
+- config, default site for ansible-core is now under /ansbile-core/.
+- connection base - Avoid using deprecated ``@abstractproperty`` decorator.
+- constructed - a new options ``trailing_separator`` and ``default_value`` to deal with key's value empty on keyed group.
+- cron - ``name`` is now a required parameter always
+- cron - ``reboot`` parameter has been dropped in favor of ``special_time: reboot``
+- cron, removed previously deprecated 'reboot' and now requires either 'name' as unique identifier.
+- default callback plugin - displays output for ``v2_runner_on_async_ok`` and ``v2_runner_on_async_failed`` callbacks.
+- deprecate ``_remote_checksum()`` and remove all internal uses (https://github.com/ansible/ansible/pull/74848)
+- dnf - Add ``cacheonly`` option (https://github.com/ansible/ansible/issues/69397).
+- dnf - allow for ``download_only`` to be run without root privileges (https://github.com/ansible/ansible/issues/75530)
+- encrypt - add new parameter ``ident`` to specify version of BCrypt algorithm to be used (https://github.com/ansible/ansible/issues/74571).
+- fact cache - Remove deprecated backwards compatibility shim for the FactCache `update` method to accept multiple arguments.
+- fact cache - Remove the deprecated location for FactCache. Import FactCache from `ansible.vars.fact_cache` instead.
+- facts - add fiber channel facts for HP-UX (https://github.com/ansible/ansible/pull/57406)
+- galaxy - support role artifact download from API response ``download_url`` location (https://github.com/ansible/ansible/issues/73103).
+- get_distribution - ``lib.ansible.module_utils.common.sys_info.get_distribution`` now returns distribution information for all platforms not just Linux (https://github.com/ansible/ansible/issues/17587)
+- get_distribution_version - ``lib.ansible.module_utils.common.sys_info.get_distribution_version`` now returns the version for all platfroms not just Linux (https://github.com/ansible/ansible/issues/17587)
+- git - Add ``accept_newhostkey`` option (https://github.com/ansible/ansible/issues/69846).
+- hostname - add support RedOS (https://github.com/ansible/ansible/issues/74779).
+- import_role - Template tasks_from, vars_from, defaults_from, and handlers_from with --extra-vars (https://github.com/ansible/ansible/issues/69097).
+- include_vars - add ``hash_behaviour`` option (https://github.com/ansible/ansible/pull/72944).
+- ini - added new parameter ``allow_no_value`` to ini lookup plugin (https://github.com/ansible/ansible/issues/50594).
+- ini lookup - add case sensitive option (https://github.com/ansible/ansible/issues/74601)
+- interpreter discovery - allow the default list of ``INTERPRETER_PYTHON_FALLBACK`` to be changed using a variable
+- interpreter discovery - prefer Python 3 over Python 2
+- inventory plugins - Remove the deprecated cache interface. Set top level keys in the inventory plugin's `_cache` attribute (a dictionary) instead.
+- jinja2_native - short-circuit ``ast.literal_eval`` for non-string values
+- module_utils distro - when a 'distro' package/module is in PYTHONPATH but isn't the real 'distro' package/module that we expect, gracefully fall back to our own bundled distro.
+- modules - add Anolis distro in hostname.py. project website https://openanolis.org/
+- move all builtin modules to use the best possible locale function instead of hardcoding 'C'.
+- password - add new parameter ``ident`` to specify version of BCrypt algorithm to be used (https://github.com/ansible/ansible/issues/74571).
+- password - add new parameter ``seed`` in lookup plugin (https://github.com/ansible/ansible/pull/69775).
+- password_hash uses passlib default if option isn't set
+- playbook - Error if a playbook is an empty list instead of just skipping
+- playbook - Error if using ``include`` instead of ``import_playbook``
+- replaced examples/ansible.cfg with instructions on how to generate an up to date copy.
+- service - add description how service module works internally (https://github.com/ansible/ansible/issues/74507).
+- service_facts now handles more states/statuses from systemd and in a more reliable way (failed, not-found, masked).
+- setup - add ``epoch_int`` option to date_time facts (https://github.com/ansible/ansible/pull/73822).
+- ssh - added pkcs11 support by adding the pkcs11_provider option in the ssh connection module. (https://www.github.com/ansible/ansible/pull/32829)
+- ssh connection, can not configure ssh_transfer_method with a variable.
+- ssh connection, ssh_transfer_method is now configurable via variable.
+- subelements lookup - Use generator in instance type check.
+- tempfile - Remove unnecessary conditional for creating a temporary directory.
+- template - Add comment attributes (``comment_start_string`` and ``comment_end_string``)
+- unicode utils - Fix ``__all__`` which was incorrectly declared as a string instead of a tuple.
+- user - Add ``umask`` option (https://github.com/ansible/ansible/issues/40359).
+- user module - Remove unused code.
+- validation testcases for check_* APIs (https://github.com/ansible/ansible/issues/55994).
+- winrm - Allow explicit environment variables to be passed through to the ``kinit`` call for Kerberos authentication
+- yaml dumper - YAML representer for AnsibleUndefined (https://github.com/ansible/ansible/issues/75072).
+- yum - Add ``cacheonly`` option (https://github.com/ansible/ansible/issues/69397).
+
+Breaking Changes / Porting Guide
+--------------------------------
+
+- Action, module, and group names in module_defaults must be static values. Their values can still be templates.
+- Fully qualified 'ansible.legacy' plugin names are not included implicitly in action_groups.
+- Unresolvable groups, action plugins, and modules in module_defaults are an error.
+- ansible-test - Automatic installation of requirements for "cloud" test plugins no longer occurs. The affected test plugins are ``aws``, ``azure``, ``cs``, ``hcloud``, ``nios``, ``opennebula``, ``openshift`` and ``vcenter``. Collections should instead use one of the supported integration test requirements files, such as the ``tests/integration/requirements.txt`` file.
+- ansible-test - The HTTP Tester is no longer available with the ``ansible-test shell`` command. Only the ``integration`` and ``windows-integration`` commands provide HTTP Tester.
+- ansible-test - The ``--disable-httptester`` option is no longer available. The HTTP Tester is no longer optional for tests that specify it.
+- ansible-test - The ``--httptester`` option is no longer available. To override the container used for HTTP Tester tests, set the ``ANSIBLE_HTTP_TEST_CONTAINER`` environment variable instead.
+- ansible-test - Unit tests for ``modules`` and ``module_utils`` are now limited to importing only ``ansible.module_utils`` from the ``ansible`` module.
+- conditionals - ``when`` conditionals no longer automatically parse string booleans such as ``"true"`` and ``"false"`` into actual booleans. Any non-empty string is now considered true. The ``CONDITIONAL_BARE_VARS`` configuration variable no longer has any effect.
+- hostname - Drops any remaining support for Python 2.4 by using ``with open()`` to simplify exception handling code which leaked file handles in several spots
+- hostname - On FreeBSD, the string ``temporarystub`` no longer gets written to the hostname file in the get methods (and in check_mode). As a result, the default hostname will now appear as ``''`` (empty string) instead of ``temporarystub`` for consistency with other strategies. This means the ``before`` result will be different.
+- hostname - On OpenRC systems and Solaris, the ``before`` value will now be ``''`` (empty string) if the permanent hostname file does not exist, for consistency with other strategies.
+- intersect, difference, symmetric_difference, union filters - the default behavior is now to be case-sensitive (https://github.com/ansible/ansible/issues/74255)
+- unique filter - the default behavior is now to fail if Jinja2's filter fails and explicit ``case_sensitive=False`` as the Ansible's fallback is case-sensitive (https://github.com/ansible/ansible/pull/74256)
+
+Deprecated Features
+-------------------
+
+- ansible-test - The ``--docker-no-pull`` option is deprecated and has no effect.
+- ansible-test - The ``--no-pip-check`` option is deprecated and has no effect.
+- include action is deprecated in favor of include_tasks, import_tasks and import_playbook.
+- module_utils' FileLock is scheduled to be removed, it is not used due to its unreliable nature.
+
+Removed Features (previously deprecated)
+----------------------------------------
+
+- The built-in module_util ``ansible.module_utils.common.removed`` was previously deprecated and has been removed.
+- connections, removed password check stubs that had been moved to become plugins.
+- task, inline parameters being auto coerced into variables has been removed.
+
+Security Fixes
+--------------
+
+- Do not include params in exception when a call to ``set_options`` fails. Additionally, block the exception that is returned from being displayed to stdout. (CVE-2021-3620)
+- templating engine fix for not preserving usnafe status when trying to preserve newlines. CVE-2021-3583
+
+Bugfixes
+--------
+
+- Add RockyLinux to fact gathering (https://github.com/ansible/ansible/pull/74530).
+- Add unicode support to ``ansible-inventory`` CLI (https://github.com/ansible/ansible/issues/57378)
+- Add yaml representer for VarsWithSources (https://github.com/ansible/ansible/pull/68525).
+- Added page describing terminal plugins to docsite
+- AnsibleModule.set_mode_if_different - don't check file existence when check_mode is activated (https://github.com/ansible/ansible/issues/61185).
+- Apply ``display_failed_stderr`` callback option on loop item results. (https://github.com/ansible/ansible/issues/74864)
+- Binary GnuPG keys downloaded via URLs by the 'ansible.builtin.apt_key' module were corrupted so 'gpg' could not import them (https://github.com/ansible/ansible/issues/74424).
+- Ensure end_play ends play, not batch (https://github.com/ansible/ansible/issues/73971)
+- Ensure we get full path for extra vars into cliargs to avoid realpath issues after initial load.
+- Fix ``keys()`` implementation of ``BaseFileCacheModule`` to strip the prefix from the key and only return keys that share the same prefix as the cache.
+- Fix ``when`` evaluation on Native Jinja and Python 3.10.
+- Fix templating task action with host-specific vars (https://github.com/ansible/ansible/issues/75568)
+- Fully qualified 'ansible.legacy' and 'ansible.builtin' plugin names work in conjunction with module_defaults.
+- Give a warning instead of an error if a handler name contains undefined variables and has no listen topics (https://github.com/ansible/ansible/issues/58841).
+- Improve resilience of ``ansible-galaxy collection`` by increasing the page size to make fewer requests overall and retrying queries with a jittered exponential backoff when rate limiting HTTP codes (520 and 429) occur. (https://github.com/ansible/ansible/issues/74191)
+- Jinja2 globals should be accessible even when importing a template without the context (https://github.com/ansible/ansible/issues/75371)
+- PlayContext - Remove deprecated ``make_become_cmd`` (https://github.com/ansible/ansible/issues/74136)
+- PowerShell - Ignore the ``LIB`` environment variable when compiling C# Ansible code
+- Prevent ``ansible_failed_task`` from further templating (https://github.com/ansible/ansible/issues/74036)
+- Remove 'default' from ssh plugin as we want to rely on default from ssh itself or ssh/config.
+- Replace usage of private dnf.Base() attribute by future dnf API
+- Save unreachable hosts between plays by adding them to the PlayIterator's _play._removed_hosts (https://github.com/ansible/ansible/issues/66945).
+- Solaris - correct version check in svcadm_supports_sync (https://github.com/ansible/ansible/pull/73860).
+- Task depth - Prevent exception when the task depth exceeds Pythons recursion depth (https://github.com/ansible/ansible/issues/73996)
+- Templating - Ensure we catch exceptions when calling ``.filters()`` or ``.tests()`` on their respective plugins and properly error, instead of aborting which results in no filters being added to the jinja2 environment (https://github.com/ansible/ansible/pull/74127)
+- The ``apt_key`` module did not properly handle GnuPG errors (https://github.com/ansible/ansible/issues/74477)
+- The error message about the failure to import a ```gpg`` key by the ``apt_key`` module was incorrect (https://github.com/ansible/ansible/issues/74423).
+- Update network user guide to explain use of cli_parse and validate plugins.
+- Variable Manager - Only check if ``play.hosts`` is a template when the play hasn't been finalized (https://github.com/ansible/ansible/issues/73926)
+- WorkerProcess - Python 3.5 fix for workaround for stdout deadlock in multiprocessing shutdown to avoid process hangs. (https://github.com/ansible/ansible/issues/74149)
+- ``AnsibleModule.run_command`` - Address thread safety issues, concerning mutating the environment, current working directory, and umask. (https://github.com/ansible/ansible/issues/74783)
+- ``failed_when``/``changed_when`` - Catch templating errors to prevent masking of module output (https://github.com/ansible/ansible/issues/37187)
+- ``heuristic_log_sanitize`` - Return the full string if there is no password (https://github.com/ansible/ansible/issues/75542)
+- ``pip`` now uses the ``pip`` Python module installed for the Ansible module's Python interpreter, if available, unless ``executable`` or ``virtualenv`` were specified.
+- advanced_host_list inventory plugin - Fixed variable referenced before assignment when hostname/range could not be parsed.
+- ansiballz - avoid treating path to site_packages as regex; escape it. This prevents a crash when ansible is installed to, or running from, an oddly named directory like ``ansi[ble``
+- ansible-doc - in text output, do not show empty ``version_added_collection`` values (https://github.com/ansible/ansible/pull/74999).
+- ansible-doc can now dump kewyords with --metadata-dump (still just for internal use)
+- ansible-doc, fix output for internal metadata dump option
+- ansible-doc, make inventory plugin selection for snippets generic and not a hardcoded list
+- ansible-galaxy - Fix a bug with build_ignore when installing collections from source (https://github.com/ansible/ansible/issues/75528).
+- ansible-galaxy - Fix handling HTTP exceptions from Galaxy servers. Continue to the next server in the list until the collection is found.
+- ansible-galaxy - Improve error message from dependency resolution when a candidate has inconsistent requirements (https://github.com/ansible/ansible/issues/75139).
+- ansible-inventory - handle an exception while parsing inventory in toml format (https://github.com/ansible/ansible/issues/74404).
+- ansible-playbook, more robust handling of --list-hosts and undefined vars in hosts keyword.
+- ansible-pull - update documentation for ``--directory`` option to clarify path must be absolute.
+- ansible-pull, restore other options to use as repo other than git.
+- ansible-test - Add constraint for ``pyspnego>=0.1.6`` for Python 3.10 - https://github.com/ansible/ansible/pull/74612
+- ansible-test - Avoid publishing the port used by the ``pypi-test-container`` since it is only accessed by other containers. This avoids issues when trying to run tests in parallel on a single host.
+- ansible-test - Failure to download test results from a remote host no longer hide test failures. If a download failure occurs after tests fail, a warning will be issued instead.
+- ansible-test - Fix docker container IP address detection. The ``bridge`` network is no longer assumed to be the default.
+- ansible-test - Fix path to inventory file for ``windows-integration`` and ``network-integration`` commands for collections.
+- ansible-test - Fix traceback when generating coverage reports and no coverage directory exists.
+- ansible-test - Random port selection is no longer handled by ``ansible-test``, avoiding possible port conflicts. Previously ``ansible-test`` would, under some circumstances, use one host's available ports to determine those of another host.
+- ansible-test - Running tests in a single test run with multiple "cloud" plugins no longer results in port conflicts. Previously two or more containers with overlapping ports could not be used in the same test run.
+- ansible-test - Tab completion after options like ``--docker`` which accept an optional argument will no longer provide incorrect completions.
+- ansible-test - The ``--python`` and ``--venv`` options are no longer ignored by some commands, such as ``coverage``.
+- ansible-test - The ``docker inspect`` command is now used to check for existing images instead of the ``docker images`` command. This resolves an issue where a ``docker pull`` would be unnecessarily executed for an image referenced by checksum.
+- ansible-test - Update distribution test containers to version 3.1.0.
+- ansible-test - Use ``--strict`` for ``pytest`` on Python 2.6 since ``--strict-markers`` is not available.
+- ansible-test - Use documented API to retrieve build information from Azure Pipelines.
+- ansible-test - Use pwsh to generate correct coverage line counts for stub files to get a more accurate coverage result
+- ansible-test - Use the correct variable to reference the client's SSH key when generating inventory.
+- ansible-test - add packaging python module to ``ansible-doc`` sanity test requirements.
+- ansible-test - allow the same listening port on all container interfaces
+- ansible-test - ensure the correct unit test target is given when the ``__init__.py`` file is modified inside the connection plugins directory
+- ansible-test - make the ``a/`` and ``b/`` prefixes an optional match since these can be turned off with the ``diff.noprefix`` setting in ``git``
+- ansible-test - restrict ``packaging`` to ``< 21.0`` for Python ``< 3.6`` (https://github.com/ansible/ansible/pull/75186).
+- ansible-test pslint - Fix error when encountering validation results that are highly nested - https://github.com/ansible/ansible/issues/74151
+- ansible-test validate-modules - EXAMPLES will no longer be marked as invalid YAML when it uses Ansible-specific YAML tags (https://github.com/ansible/ansible/pull/74384).
+- ansible-test validate-modules - correctly validate positional parameters to ``AnsibleModules`` (https://github.com/ansible/ansible/pull/75332).
+- ansible.builtin.cron - Keep non-empty crontabs, when removing cron jobs (https://github.com/ansible/ansible/pull/74497).
+- ansible.utils.encrypt now handles missing or unusable 'crypt' library.
+- ansible_test - add constraint for ``MarkupSafe`` (https://github.com/ansible/ansible/pull/74666)
+- apt_key - set --recv argument as last one in apt-key command when using env var HTTP_PROXY (https://github.com/ansible/ansible/issues/74946)
+- arg_spec - remove unused imports
+- async_status, ensure we always get documented returns
+- async_status, resurrected module to deprecate for those that were invoking it directly.
+- basic - skip over module parameters which are used in ``journal.send`` API call (https://github.com/ansible/ansible/issues/71343).
+- become - fix a regression on Solaris where chmod can return 5 which we interpret as auth failure and stop trying become tmpdir permission fallbacks
+- become - work around setfacl not existing on modern Solaris (and possibly failing on some filesystems even when it does exist)
+- callbacks, restore displaying delegation to host as host label.
+- cli defaults for ssh args set to None as '' was bypassing normal default.
+- command - remove unreachable code path when trying to convert the value for ``chdir`` to bytes (https://github.com/ansible/ansible/pull/75036)
+- command module, clarify order of remove/creates checks.
+- command module, correctly handles chdir to symlinks.
+- command module, move to standarized messages in 'msg' vs abusing 'stdout'.
+- command module, now all options work in ad-hoc execution.
+- command module, now always returns what we documented as 'returns always'.
+- config - use ``callbacks_enabled`` instead ``callback_enabled`` in a deprecated message (https://github.com/ansible/ansible/issues/70028).
+- config lookup, can also handle collection plugins now
+- config, ensure 'quoted' lists from ini or env do not take the quotes literally as part of the list item.
+- connection ssh, no ssh_args cli option, so removed doc entry.
+- constants, internal _deprecated function always requires version.
+- correct doc links for become on warnings over world readable settings.
+- correctly use world readable setting since old constant is not 'settable' anymore.
+- dnf - align the return value of the list argument with the ``yum`` module (https://github.com/ansible/ansible/issues/75483)
+- dnf - properly capture transaction error (https://github.com/ansible/ansible/issues/72651)
+- dnf - refactor code to use `dnf whatprovides` API (https://github.com/ansible/ansible/issues/73503).
+- dnf - support non-english environments (https://github.com/ansible/ansible/issues/75021)
+- dnf module - Use all components of a package name to determine if it's installed (https://github.com/ansible/ansible/issues/75311).
+- do not trigger interpreter discovery in the forced_local module path as they should use the ansible playbook python unless otherwise configured.
+- facts - detect homebrew installed at /opt/homebrew/bin/brew
+- facts, service_mgr, handle issues if ps command fails or returns empty.
+- filter plugins - patch new versions of Jinja2 to prevent warnings/errors on renamed filter decorators (https://github.com/ansible/ansible/issues/74667)
+- find - fix a bug where ``size`` argument was ignored for regular files with ``file_type`` of ``any``.
+- find action, correctly convert path to text when warning about skiping.
+- find does not ignore errors from os.walk anymore and issues warnings as expected.
+- gather_facts, improved message on timeout.
+- gather_facts, package, service - fix using module_defaults for the modules in addition to the action plugins. (https://github.com/ansible/ansible/issues/72918)
+- get_bin_path, clarify with quotes what the missing required executable is.
+- get_url - Fixed checksum validation for binary files (leading asterisk) in checksum files (https://github.com/ansible/ansible/pull/74502).
+- getent, fix return data for when there are multiple results for the same key
+- git - Fix git path used when .git file is present (https://github.com/ansible/ansible/issues/75608).
+- host_group_vars vars plugin fixed ini entry, section and key were reversed.
+- hostname - Add Rocky Linux support
+- hostname - No longer modifies system files in get_* methods and therefore when consulted in check_mode (https://github.com/ansible/ansible/issues/66432)
+- include - Remove deprecated ``static`` argument for ``include`` (https://github.com/ansible/ansible/issues/74135)
+- includes - Remove the deprecated ability to specify ``tags`` as ``vars`` on includes (https://github.com/ansible/ansible/issues/74144)
+- ini lookup - better error on mixed/bad parameters
+- ini lookup - handle errors for duplicate keys and missing sections (https://github.com/ansible/ansible/issues/74601)
+- interpreter discovery - Debian 8 and lower will avoid unsupported Python3 version in interpreter discovery
+- interpreter discovery is now handling special (ansible_network_os) cases in less noisy ways.
+- interpreter_discovery - hide warning 'No python interpreters...' when ANSIBLE_PYTHON_INTERPRETER=auto_silent (https://github.com/ansible/ansible/issues/74274).
+- module_common - handle exception when multiple workers try to create the cache directory
+- module_defaults - Fix action defaults for legacy actions/modules (https://github.com/ansible/ansible/issues/75279).
+- module_utils - detect symlinked init systems, even if unable to read /proc/1/comm (https://github.com/ansible/ansible/issues/74866).
+- netconf - catch and handle exception to prevent stack trace when running in FIPS mode
+- network module_utils - fix bug where ``to_bits()`` returned the ``str`` type instead of a useful value.
+- paramiko_ssh - mark connection as connected when ``_connect()`` is called (https://github.com/ansible/ansible/issues/74081)
+- password - Handle passlib wrapped algos bsd_nthash, django_argon2, django_bcrypt, ldap_bcrypt, ldap_bsdi_crypt, ldap_des_crypt, ldap_hex_md5, ldap_hex_sha1, ldap_md5_crypt, ldap_pbkdf2_sha1, ldap_pbkdf2_sha256, ldap_pbkdf2_sha512, ldap_sha1_crypt, ldap_sha256_crypt, ldap_sha512_crypt, roundup_plaintext (https://github.com/ansible/ansible/pull/75527).
+- pause - ensure control characters are always set to an appropriate value (https://github.com/ansible/ansible/issues/73264)
+- pkg_mgr.py - Lower the priority of rpm-ostree detection to avoid false positives on systems not using it as the main package manager (https://github.com/ansible/ansible/issues/74578)
+- play - validate the ``hosts`` entry in a play (https://github.com/ansible/ansible/issues/65386)
+- playbook loaded from collection subdir now does not ignore subdirs.
+- plugin config now allows list type options to have multiple valid choices (#74225).
+- psrp - Always cleanup the last run pipeline if a second pipeline is invoked to avoid violating any resource limits.
+- psrp - Fix error when resetting a connection that was initialised but not connected - (https://github.com/ansible/ansible/issues/74092).
+- psrp - Try to clean up any server-side resources when resetting a connection.
+- recursive_diff - handle condition when parameters are not dict (https://github.com/ansible/ansible/issues/56249).
+- register - Ensure that ``register`` used on ``set_fact`` or ``include_vars`` does not automatically wrap the facts as unsafe. (https://github.com/ansible/ansible/issues/21088)
+- rekey_on_member - handle undefined positional arguments better.
+- remote tmpdir permissions - fix type error in macOS chmod ACL fallback (https://github.com/ansible/ansible/pull/74613).
+- replace - better handling of file operation exceptions (https://github.com/ansible/ansible/pull/74686).
+- roles - allow for role arg specs in new meta file (https://github.com/ansible/ansible/issues/74525).
+- roles - fix unexpected ``AttributeError`` when an empty ``argument_specs.yml`` is present (https://github.com/ansible/ansible/pull/75604).
+- roles - make sure argspec validation task is tagged with ``always`` (https://github.com/ansible/ansible/pull/74994).
+- roles - make sure argspec validation task templates suboptions (https://github.com/ansible/ansible/issues/75070).
+- schema validation now uses dynamic range of versions for valid deprecation entries vs hardcoded out of date list.
+- script inventory plugin - Remove deprecated caching support (https://github.com/ansible/ansible/issues/74143)
+- sequence - fix error message so that unrecognized options to the plugin display correctly as a list and normalize error messages.
+- service - compare version without LooseVersion API (https://github.com/ansible/ansible/issues/74488).
+- set ssh host_key_checking defaults to True, restoring original behaviour (https://github.com/ansible/ansible/issues/75168)
+- setup module should now not truncate hpux interface names.
+- setup module, fix filter to adjust for missing ``ansible_`` prefix on query.
+- setup, while gathering linux hardware facts be more resilient to errors and try to return more info.
+- slurp - Fix error messages for unreadable files and directories(https://github.com/ansible/ansible/issues/67340).
+- slurp - handle error when ``path`` is a directory and not a file (https://github.com/ansible/ansible/pull/74930).
+- slurp - improve the logic in the error handling and remove ``os.stat()`` call (https://github.com/ansible/ansible/pull/75038)
+- ssh connection now correctly handle ssh_transfer_method and scp_if_ssh interactions.
+- ssh connection, fix interaction between trasnfer settings options.
+- ssh connection, use self.host which has the most up2date info instead of pc.remote_addr
+- ssh_connection - rename ``retries`` to ``reconnection_retries`` to avoid conflicts with task vars (https://github.com/ansible/ansible/issues/75142).
+- ssh_connection - set the default for ``reconnection_retries`` back to ``0`` (https://github.com/ansible/ansible/issues/75142).
+- subversion - fix stack trace when getting information about the repository (https://github.com/ansible/ansible/issues/36498)
+- system_service - use a context manager for file handling.
+- task_executor, Actions using AnsibleActionFail/Skip will now propagate 'results' if given
+- task_executor/ssh_connection - use the ``retries`` value from ``ssh_connection`` settings, not the default from the ``Task`` field attributes (https://github.com/ansible/ansible/issues/75142).
+- template - ensure Jinja2 overrides from template header are used (https://github.com/ansible/ansible/issues/75275)
+- unarchive - allow extracting archives that contain files which size exceeds free system memory (https://github.com/ansible/ansible/issues/73985).
+- unarchive - fail when zipinfo binary is not found in executable paths (https://github.com/ansible/ansible/issues/39029).
+- unarchive - move failure for missing binary to ``can_handle_archive()`` rather than ``__init__()``
+- uri - Fix traceback and provide error message when trying to use non-string or mapping for ``form-multipart`` body - https://github.com/ansible/ansible/issues/74276
+- urls - Fix logic in matching ``unredirected_headers`` to perform case insensitive matching
+- validate_argument_spec, correct variable precedence and merge method and add missing examples
+- variable manager, avoid sourcing delegated variables when no inventory hostname is present. This affects scenarios like syntax check and imports.
+- version test - improve error message when an empty version is provided
+- yum - Fixed typo in failure message (https://github.com/ansible/ansible/pull/72964).
+- yum - When upgrading, every architecture of a package is now included in the module results, instead of just one (https://github.com/ansible/ansible/issues/73284).
+- yum - fix ``yumstate`` return value when wildcards are used in the ``list`` argument (https://github.com/ansible/ansible/issues/74557)
+- yum - fix parsing of multiple subsequent empty lines from ``yum check-update`` output (https://github.com/ansible/ansible/issues/70949)
+- yum - yum action plugin changes to support 'use' as an alias of 'use_backend' (https://github.com/ansible/ansible/issues/70774).
+
+Known Issues
+------------
+
+- ansible-test - Tab completion anywhere other than the end of the command with the new composite options will provide incorrect results. See https://github.com/kislyuk/argcomplete/issues/351 for additional details.

changelogs/fragments/74127-bad-filter-2.yml

@@ -0,0 +1,5 @@
+bugfixes:
+- Templating - Ensure we catch exceptions when getting ``.filters`` and
+  ``.tests`` attributes on their respective plugins and properly error,
+  instead of aborting which results in no filters being added to the
+  jinja2 environment

changelogs/fragments/74349-improve-docker-detection.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - setup - detect docker container with check for ./dockerenv or ./dockinit (https://github.com/ansible/ansible/pull/74349).

changelogs/fragments/75635-fix-role-argspec-suboption-validation.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - validate_argument_spec - Skip suboption validation if the top level option is an invalid type (https://github.com/ansible/ansible/issues/75612).

changelogs/fragments/76069-fix-unarchive-file-listing-in-zip.yaml

@@ -0,0 +1,3 @@
+bugfixes:
+- unarchive - Fix zip archive file listing that caused issues with content
+  postprocessing (https://github.com/ansible/ansible/issues/76067).

changelogs/fragments/76336-yum-makecache-fast.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - yum - prevent storing unnecessary cache data by running `yum makecache fast` (https://github.com/ansible/ansible/issues/76336)

changelogs/fragments/76379-set-finalize-on-new-env.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - "``Templar.copy_with_new_env`` - set the ``finalize`` method of the new ``Templar`` object for the new environment (https://github.com/ansible/ansible/issues/76379)"

changelogs/fragments/76530-connection-password-file-tb-fix.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - Fix ``AttributeError`` when providing password file via ``--connection-password-file`` (https://github.com/ansible/ansible/issues/76530)

changelogs/fragments/76542-fix-unarchive-on-nenglish-locales.yml

@@ -0,0 +1,2 @@
+bugfixes:
+- unarchive - Make extraction work when the LANGUAGE environment variable is set to a non-English locale.

changelogs/fragments/76672-fix-end_play-multiple_plays.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - Fix ``end_play`` to end the current play only (https://github.com/ansible/ansible/issues/76672)

changelogs/fragments/76729-async-callback-perf.yml

@@ -0,0 +1,3 @@
+bugfixes:
+- async - Improve performance of sending async callback events by never sending the full task through the queue
+  (https://github.com/ansible/ansible/issues/76729)

changelogs/fragments/76735-ansible-galaxy-fix-ignore-certs.yaml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-galaxy - Fix using the '--ignore-certs' option when there is no server-specific configuration for the Galaxy server.

changelogs/fragments/76782-fqcn-compare-lockstep-strategies.yml

@@ -0,0 +1,4 @@
+bugfixes:
+- default callback - Ensure we compare FQCN also in lockstep logic, to ensure
+  using the FQCN of a strategy plugin triggers the correct behavior in the
+  default callback plugin. (https://github.com/ansible/ansible/issues/76782)

changelogs/fragments/76792-hostname-all-systemd.yml

@@ -0,0 +1,3 @@
+bugfixes:
+- hostname - Do not require SystemdStrategy subclasses for every distro
+  (https://github.com/ansible/ansible/issues/76792)

changelogs/fragments/77004-restore-missing-default.yml

@@ -0,0 +1,3 @@
+bugfixes:
+- template lookup - restore inadvertently deleted default for ``convert_data``
+  (https://github.com/ansible/ansible/issues/77004)

changelogs/fragments/ansible-test-alpine3-update.yaml

@@ -0,0 +1,3 @@
+minor_changes:
+  - ansible-test - Update the ``alpine`` container to version 3.3.0.
+    This updates the base image from 3.14.2 to 3.15.0, which includes support for installing binary wheels using pip.

changelogs/fragments/ansible-test-bootstrap-pip.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - ansible-test - Update ``pip`` used to bootstrap remote FreeBSD instances from version 20.3.4 to 21.3.1.

changelogs/fragments/ansible-test-ci-files.yaml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Use https://ci-files.testing.ansible.com/ for instance bootstrapping instead of an S3 endpoint.

changelogs/fragments/ansible-test-container-images.yml

@@ -0,0 +1,3 @@
+minor_changes:
+  - ansible-test - Update the ``galaxy`` test plugin to get its container from a copy on quay.io.
+  - ansible-test - Update the ``openshift`` test plugin to get its container from a copy on quay.io.

changelogs/fragments/ansible-test-default-base-containers-python-3.10.yaml

@@ -0,0 +1,2 @@
+minor_changes:
+  - ansible-test - Update the ``base`` and ``default`` containers from Python 3.10.0rc2 to 3.10.0.

changelogs/fragments/ansible-test-default-containers-4.1.1.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Update the ``default`` containers to version 4.1.1, which includes the updated ``import`` sanity test requirements.

changelogs/fragments/ansible-test-default-containers-4.2.0.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Update the ``default`` containers to version 4.2.0.

changelogs/fragments/ansible-test-delegation-pythonpath.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Fix traceback when running from an install and delegating execution to a different Python interpreter.

changelogs/fragments/ansible-test-distro-containers-3.1.0.yaml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Update distribution test containers to version 3.1.0.

changelogs/fragments/ansible-test-import-collections.yml

@@ -0,0 +1,5 @@
+bugfixes:
+  - ansible-test - The ``import`` sanity test no longer reports errors about ``packaging`` being missing when testing collections.
+minor_changes:
+  - The collection loader now reports a Python warning if an attempt is made to install the Ansible collection loader a second time.
+    Previously this condition was reported using an Ansible warning.

changelogs/fragments/ansible-test-inventory-path.yaml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Fix path to inventory file for ``windows-integration`` and ``network-integration`` commands for collections.

changelogs/fragments/ansible-test-inventory-ssh-key.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Use the correct variable to reference the client's SSH key when generating inventory.

changelogs/fragments/ansible-test-junit-relative-paths.yml

@@ -0,0 +1,6 @@
+bugfixes:
+  - ansible-test - Use relative paths in JUnit files generated during integration test runs.
+  - ansible-test - Replace the directory portion of out-of-tree paths in JUnit files from integration tests with the ``out-of-tree:`` prefix.
+  - junit callback - Fix traceback during automatic fact gathering when using relative paths.
+minor_changes:
+  - junit callback - Add support for replacing the directory portion of out-of-tree relative task paths with a placeholder.

changelogs/fragments/ansible-test-links.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Update help links to reference ``ansible-core`` instead of ``ansible``.

changelogs/fragments/ansible-test-managed-venv.yml

@@ -0,0 +1,15 @@
+bugfixes:
+  - ansible-test - Virtual environments managed by ansible-test now use consistent versions of ``pip``, ``setuptools`` and ``wheel``.
+                   This avoids issues with virtual environments containing outdated or dysfunctional versions of these tools.
+                   The initial bootstrapping of ``pip`` is done by ansible-test from an HTTPS endpoint instead of creating the virtual environment with it already present.
+  - ansible-test - Sanity tests run with the ``--requirements` option for Python 2.x now install ``virtualenv`` when it is missing or too old.
+                   Previously it was only installed if missing.
+                   Version 16.7.12 is now installed instead of the latest version on Python 2.7.
+  - ansible-test - All virtual environments managed by ansible-test are marked as usable after being bootstrapped, to avoid errors caused by use of incomplete environments.
+                   Previously this was only done for sanity tests.
+                   Existing environments from previous versions of ansible-test will be recreated on demand due to lacking the new marker.
+minor_changes:
+  - ansible-test - The ``pip`` and ``wheel`` packages are removed from all sanity test virtual environments after installation completes to reduce their size.
+                   Previously they were only removed from the environments used for the ``import`` sanity test.
+  - ansible-test - The hash for all managed sanity test virtual environments has changed.
+                   Containers that include ``ansible-test sanity --prime-venvs`` will need to be rebuilt to continue using primed virtual environments.

changelogs/fragments/ansible-test-pyopenssl.yaml

@@ -0,0 +1,2 @@
+minor_changes:
+  - ansible-test - Installation of ``cryptography`` is no longer version constrained when ``openssl`` 1.1.0 or later is installed.

changelogs/fragments/ansible-test-pytest-forked.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Update unit tests to use the ``--forked`` option instead of the deprecated ``--boxed`` option.

changelogs/fragments/ansible-test-relocate-constants.yaml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Relocate constants to eliminate symlink.

changelogs/fragments/ansible-test-requirements-target.yaml

@@ -0,0 +1,3 @@
+bugfixes:
+  - ansible-test - Target integration test requirements are now correctly installed for target environments running on the controller.
+  - ansible-test - Automatic target requirements installation is now based on the target environment instead of the controller environment.

changelogs/fragments/ansible-test-sanity-import-loader.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Use the legacy collection loader for ``import`` sanity tests on target-only Python versions.

changelogs/fragments/ansible-test-sanity-import-no-pip.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Fix traceback in ``import`` sanity test on Python 2.7 when ``pip`` is not available.

changelogs/fragments/ansible-test-sanity-import.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Fix installation and usage of ``pyyaml`` requirement for the ``import`` sanity test for collections.

changelogs/fragments/ansible-test-sanity-requirements-update.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - ansible-test - Requirements for the plugin import test are now frozen.

changelogs/fragments/ansible-test-sanity-vendoring.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Fix the ``import`` sanity test to work properly when Ansible's built-in vendoring support is in use.

changelogs/fragments/ansible-test-unsupported-directory-traceback.yaml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Show an error message instead of a traceback when running outside of a supported directory.

changelogs/fragments/ansible-test-validate-modules-collection-loader.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Fix the ``validate-modules`` sanity test to avoid double-loading the collection loader and possibly failing on import of the ``packaging`` module.

changelogs/fragments/ansible-test-validate-modules-no-callable.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Fix traceback in the ``validate-modules`` sanity test when testing an Ansible module without any callables.

changelogs/fragments/ansible-test-venv-real-prefix.yaml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Fix Python real prefix detection when running in a ``venv`` virtual environment.

changelogs/fragments/ansible-test-yaml-import.yaml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Import ``yaml.cyaml.CParser`` instead of ``_yaml.CParser`` in the ``yamllint`` sanity test.

changelogs/fragments/avoid-set_options-leak.yaml

@@ -0,0 +1,5 @@
+---
+security_fixes:
+  - Do not include params in exception when a call to ``set_options`` fails.
+    Additionally, block the exception that is returned from being displayed to stdout.
+    (CVE-2021-3620)

changelogs/fragments/clean_facts_values.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - cleaning facts will now only warn about the variable name and not post the content, which can be undesireable to disclose

changelogs/fragments/config_fix_terms.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-config avoid showing _terms and _input when --only-changed.

changelogs/fragments/fix_block_var_inh.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - correctly inherit vars from parent in block (https://github.com/ansible/ansible/issues/75286).

changelogs/fragments/fix_fax_delegation_loops.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - task_executor reverts the change to push facts into delegated vars on loop finalization as result managing code already handles this and was duplicating effort to wrong result.

changelogs/fragments/fix_sudo_flag_mangling.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - sudo become plugin, fix handling of non interactive flags, previous substitution was too naive

changelogs/fragments/galaxy-build-files-ignore.yml

@@ -0,0 +1,4 @@
+bugfixes:
+- >-
+  ansible-galaxy collection build - Ignore any existing ``MANIFEST.json`` and ``FILES.json`` in the root directory
+  when building a collection.

changelogs/fragments/gather_facts_collections.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - gather_facts action now handles the move of base connection plugin types into collections to add/prevent subset argument correctly

changelogs/fragments/include_vars_failed.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - include_vars, properly initialize variable as there is corner case in which it can end up referenced and not defined

changelogs/fragments/jinja2_native-literal_eval-py310.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - jinja2_native - keep same behavior on Python 3.10.

changelogs/fragments/junit-callback-task-path-unicode.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - junit callback - Fix unicode error when handling non-ASCII task paths.

changelogs/fragments/pslint-sanity-warning.yml

@@ -0,0 +1,2 @@
+bugfixes:
+- ansible-test pslint - Fix error when encountering validation results that are highly nested - https://github.com/ansible/ansible/issues/74151

changelogs/fragments/set_fact_delegation.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - set_fact/include_vars correctly handle delegation assignments within loops

changelogs/fragments/ssh_debug_noparse.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ssh connection avoid parsing ssh cli debug lines as they can match expected output at high verbosities.

changelogs/fragments/ssh_quote_cp.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ssh connection - properly quote controlpersist path given by user to avoid issues with spaces and other characters

changelogs/fragments/ssh_use_right_host.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ssh connection now uses more correct host source as play_context can ignore loop/delegation variations.

changelogs/fragments/v2.12.0_summary.yaml

@@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2021-11-05
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__

changelogs/fragments/v2.12.0b1_summary.yaml

@@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2021-09-27
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__

changelogs/fragments/v2.12.0b2_summary.yaml

@@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2021-10-11
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__

changelogs/fragments/v2.12.0rc1_summary.yaml

@@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2021-10-18
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__

changelogs/fragments/v2.12.1_summary.yaml

@@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2021-12-06
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__

changelogs/fragments/v2.12.1rc1_summary.yaml

@@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2021-11-29
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__

changelogs/fragments/v2.12.2_summary.yaml

@@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2022-01-31
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__

changelogs/fragments/v2.12.2rc1_summary.yaml

@@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2022-01-24
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__

changelogs/fragments/v2.12.3_summary.yaml

@@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2022-02-28
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__

changelogs/fragments/v2.12.3rc1_summary.yaml

@@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2022-02-23
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__

changelogs/fragments/win_LinkUtil-ignore-LIB.yml

@@ -0,0 +1,2 @@
+bugfixes:
+- Ansible.ModuleUtils.LinkUtil - Ignore the ``LIB`` environment variable when loading the ``LinkUtil`` code

docs/docsite/.templates/banner.html

@@ -14,7 +14,8 @@
       });
     }
     var banner = '';
-    //use extra_banner for when marketing wants something extra, like a survey or AnsibleFest notice
+      var extra_banner = '';
+    /*use extra_banner for when marketing wants something extra, like a survey or AnsibleFest notice
     var extra_banner =
       '<div id="latest_extra_banner_id" class="admonition important">' +
       '<br>' +
@@ -26,7 +27,7 @@
         '<a href="https://reg.ansiblefest.redhat.com/flow/redhat/ansible21/regGenAttendee/login?sc_cid=7013a000002pemAAAQ">Register now!</a> ' +
       '</p>' +
       '<br>' +
-      '</div>';
+      '</div>'; */
     // Create a banner if we're not on the official docs site
     if (location.host == "docs.testing.ansible.com") {
       document.write('<div id="testing_banner_id" class="admonition important">' +

docs/docsite/requirements.txt

@@ -3,7 +3,7 @@
 # if you want known good versions of these dependencies
 # use known_good_reqs.txt instead 
 
-antsibull >= 0.34.0
+antsibull >= 0.38.2
 docutils == 0.16 # pin for now until the problem with unordered lists is fixed
 # see https://github.com/readthedocs/sphinx_rtd_theme/issues/1115jinja2==3.0.1
 jinja2

docs/docsite/rst/community/communication.rst

@@ -71,7 +71,9 @@ IRC chat supports:
 * simple text interface
 * bridging from Matrix
 
-Our IRC channels may require you to register your IRC nickname. If you receive an error when you connect or when posting a message, see `libera.chat's Nickname Registration guide <https://libera.chat/guides/registration>`_ for instructions. To find all ``ansible`` specific channels on the libera.chat network, use the following command in your IRC client::
+Our IRC channels may require you to register your IRC nickname. If you receive an error when you connect or when posting a message, see `libera.chat's Nickname Registration guide <https://libera.chat/guides/registration>`_ for instructions. To find all ``ansible`` specific channels on the libera.chat network, use the following command in your IRC client:
+
+.. code-block:: text
 
    /msg alis LIST #ansible* -min 5
 

docs/docsite/rst/community/development_process.rst

@@ -243,7 +243,7 @@ Here are some examples:
       remote_src=True even if mode was not set as a parameter.  This failed on
       filesystems which do not have permission bits (https://github.com/ansible/ansible/issues/29444).
 
-You can find more example changelog fragments in the `changelog directory <https://github.com/ansible/ansible/tree/stable-2.11/changelogs/fragments>`_ for the 2.11 release.
+You can find more example changelog fragments in the `changelog directory <https://github.com/ansible/ansible/tree/stable-2.12/changelogs/fragments>`_ for the 2.12 release.
 
 After you have written the changelog fragment for your PR, commit the file and include it with the pull request.
 
@@ -307,20 +307,20 @@ We do **not** backport features.
 
    These instructions assume that:
 
-    * ``stable-2.11`` is the targeted release branch for the backport
+    * ``stable-2.12`` is the targeted release branch for the backport
     * ``https://github.com/ansible/ansible.git`` is configured as a ``git remote`` named ``upstream``. If you do not use a ``git remote`` named ``upstream``, adjust the instructions accordingly.
     * ``https://github.com/<yourgithubaccount>/ansible.git`` is configured as a ``git remote`` named ``origin``. If you do not use a ``git remote`` named ``origin``, adjust the instructions accordingly.
 
 #. Prepare your devel, stable, and feature branches:
 
-   ::
+.. code-block:: shell
 
        git fetch upstream
-       git checkout -b backport/2.11/[PR_NUMBER_FROM_DEVEL] upstream/stable-2.11
+       git checkout -b backport/2.12/[PR_NUMBER_FROM_DEVEL] upstream/stable-2.12
 
 #. Cherry pick the relevant commit SHA from the devel branch into your feature branch, handling merge conflicts as necessary:
 
-   ::
+.. code-block:: shell
 
        git cherry-pick -x [SHA_FROM_DEVEL]
 
@@ -328,17 +328,17 @@ We do **not** backport features.
 
 #. Push your feature branch to your fork on GitHub:
 
-   ::
+.. code-block:: shell
 
-       git push origin backport/2.11/[PR_NUMBER_FROM_DEVEL]
+       git push origin backport/2.12/[PR_NUMBER_FROM_DEVEL]
 
-#. Submit the pull request for ``backport/2.11/[PR_NUMBER_FROM_DEVEL]`` against the ``stable-2.11`` branch
+#. Submit the pull request for ``backport/2.12/[PR_NUMBER_FROM_DEVEL]`` against the ``stable-2.12`` branch
 
 #. The Release Manager will decide whether to merge the backport PR before the next minor release. There isn't any need to follow up. Just ensure that the automated tests (CI) are green.
 
 .. note::
 
-    The branch name ``backport/2.11/[PR_NUMBER_FROM_DEVEL]`` is somewhat arbitrary, but conveys meaning about the purpose of the branch. This branch name format is not required, but it can be helpful, especially when making multiple backport PRs for multiple stable branches.
+    The branch name ``backport/2.12/[PR_NUMBER_FROM_DEVEL]`` is somewhat arbitrary, but conveys meaning about the purpose of the branch. This branch name format is not required, but it can be helpful, especially when making multiple backport PRs for multiple stable branches.
 
 .. note::
 

docs/docsite/rst/dev_guide/developing_collections_contributing.rst

@@ -25,16 +25,22 @@ Creating a PR
 
 
 
-* Create the directory ``~/dev/ansible/collections/ansible_collections/community``::
+* Create the directory ``~/dev/ansible/collections/ansible_collections/community``:
+
+.. code-block:: shell
 
     mkdir -p ~/dev/ansible/collections/ansible_collections/community
 
-* Clone `the community.general Git repository <https://github.com/ansible-collections/community.general/>`_ or a fork of it into the directory ``general``::
+* Clone `the community.general Git repository <https://github.com/ansible-collections/community.general/>`_ or a fork of it into the directory ``general``:
+
+.. code-block:: shell
 
     cd ~/dev/ansible/collections/ansible_collections/community
     git clone git@github.com:ansible-collections/community.general.git general
 
-* If you clone from a fork, add the original repository as a remote ``upstream``::
+* If you clone from a fork, add the original repository as a remote ``upstream``:
+
+.. code-block:: shell
 
     cd ~/dev/ansible/collections/ansible_collections/community/general
     git remote add upstream git@github.com:ansible-collections/community.general.git

docs/docsite/rst/dev_guide/developing_collections_distributing.rst

@@ -54,7 +54,7 @@ You can create additional namespaces on Ansible Galaxy if you choose. For Red Ha
 * To create a namespace on Galaxy, see `Galaxy namespaces <https://galaxy.ansible.com/docs/contributing/namespaces.html#galaxy-namespaces>`_ on the Galaxy docsite for details.
 * To create a namespace on Red Hat Automation Hub, see the `Ansible Certified Content FAQ <https://access.redhat.com/articles/4916901>`_.
 
-Specify the namespace in the :file:`galaxy.yaml` file for each collection. For more information on the :file:`galaxy.yaml` file, see :ref:`collections_galaxy_meta`.
+Specify the namespace in the :file:`galaxy.yml` file for each collection. For more information on the :file:`galaxy.yml` file, see :ref:`collections_galaxy_meta`.
 
 .. _galaxy_get_token:
 
@@ -124,7 +124,7 @@ Building your collection tarball
 
 After configuring one or more distribution servers, build a collection tarball. The collection tarball is the published artifact, the object that you upload and other users download to install your collection. To build a collection tarball:
 
-#. Review the version number in your :file:`galaxy.yaml` file. Each time you publish your collection, it must have a new version number. You cannot make changes to existing versions of your collection on a distribution server. If you try to upload the same collection version more than once, the distribution server returns the error ``Code: conflict.collection_exists``. Collections follow semantic versioning rules. For more information on versions, see :ref:`collection_versions`. For more information on the :file:`galaxy.yaml` file, see :ref:`collections_galaxy_meta`.
+#. Review the version number in your :file:`galaxy.yml` file. Each time you publish your collection, it must have a new version number. You cannot make changes to existing versions of your collection on a distribution server. If you try to upload the same collection version more than once, the distribution server returns the error ``Code: conflict.collection_exists``. Collections follow semantic versioning rules. For more information on versions, see :ref:`collection_versions`. For more information on the :file:`galaxy.yml` file, see :ref:`collections_galaxy_meta`.
 #. Run ``ansible-galaxy collection build`` from inside the top-level directory of the collection. For example:
 
 .. code-block:: bash

docs/docsite/rst/dev_guide/developing_collections_structure.rst

@@ -13,7 +13,9 @@ A collection is a simple data structure. None of the directories are required un
 Collection directories and files
 ================================
 
-A collection can contain these directories and files::
+A collection can contain these directories and files:
+
+.. code-block:: shell-session
 
     collection/
     ├── docs/
@@ -201,7 +203,7 @@ A collection can store some additional metadata in a ``runtime.yml`` file in the
 
 - *requires_ansible*:
 
-  The version of Ansible required to use the collection. Multiple versions can be separated with a comma.
+  The version of Ansible Core (ansible-core) required to use the collection. Multiple versions can be separated with a comma.
 
   .. code:: yaml
 

docs/docsite/rst/dev_guide/developing_collections_testing.rst

@@ -20,7 +20,9 @@ You must always execute ``ansible-test`` from the root directory of a collection
 Compile and sanity tests
 ------------------------
 
-To run all compile and sanity tests::
+To run all compile and sanity tests:
+
+.. code-block:: shell-session
 
     ansible-test sanity --docker default -v
 
@@ -31,15 +33,21 @@ Adding unit tests
 
 You must place unit tests in the appropriate ``tests/unit/plugins/`` directory. For example, you would place tests for ``plugins/module_utils/foo/bar.py`` in ``tests/unit/plugins/module_utils/foo/test_bar.py`` or ``tests/unit/plugins/module_utils/foo/bar/test_bar.py``. For examples, see the `unit tests in community.general <https://github.com/ansible-collections/community.general/tree/master/tests/unit/>`_.
 
-To run all unit tests for all supported Python versions::
+To run all unit tests for all supported Python versions:
+
+.. code-block:: shell-session
 
     ansible-test units --docker default -v
 
-To run all unit tests only for a specific Python version::
+To run all unit tests only for a specific Python version:
+
+.. code-block:: shell-session
 
     ansible-test units --docker default -v --python 3.6
 
-To run only a specific unit test::
+To run only a specific unit test:
+
+.. code-block:: shell-session
 
     ansible-test units --docker default -v --python 3.6 tests/unit/plugins/module_utils/foo/test_bar.py
 
@@ -59,13 +67,17 @@ For examples, see the `integration tests in community.general <https://github.co
 
 Since integration tests can install requirements, and set-up, start and stop services, we recommended running them in docker containers or otherwise restricted environments whenever possible. By default, ``ansible-test`` supports Docker images for several operating systems. See the `list of supported docker images <https://github.com/ansible/ansible/blob/devel/test/lib/ansible_test/_data/completion/docker.txt>`_ for all options. Use the ``default`` image mainly for platform-independent integration tests, such as those for cloud modules. The following examples use the ``centos8`` image.
 
-To execute all integration tests for a collection::
+To execute all integration tests for a collection:
+
+.. code-block:: shell-session
 
     ansible-test integration --docker centos8 -v
 
 If you want more detailed output, run the command with ``-vvv`` instead of ``-v``. Alternatively, specify ``--retry-on-error`` to automatically re-run failed tests with higher verbosity levels.
 
-To execute only the integration tests in a specific directory::
+To execute only the integration tests in a specific directory:
+
+.. code-block:: shell-session
 
     ansible-test integration --docker centos8 -v connection_bar
 

docs/docsite/rst/dev_guide/developing_inventory.rst

@@ -360,9 +360,11 @@ Inventory script conventions
 Inventory scripts must accept the ``--list`` and ``--host <hostname>`` arguments. Although other arguments are allowed, Ansible will not use them.
 Such arguments might still be useful for executing the scripts directly.
 
-When the script is called with the single argument ``--list``, the script must output to stdout a JSON object that contains all the groups to be managed. Each group's value should be either an object containing a list of each host, any child groups, and potential group variables, or simply a list of hosts::
+When the script is called with the single argument ``--list``, the script must output to stdout a JSON object that contains all the groups to be managed. Each group's value should be either an object containing a list of each host, any child groups, and potential group variables, or simply a list of hosts:
 
 
+.. code-block:: json
+
     {
         "group001": {
             "hosts": ["host001", "host002"],
@@ -383,12 +385,13 @@ When the script is called with the single argument ``--list``, the script must o
 
 If any of the elements of a group are empty, they may be omitted from the output.
 
-When called with the argument ``--host <hostname>`` (where <hostname> is a host from above), the script must print a JSON object, either empty or containing variables to make them available to templates and playbooks. For example::
+When called with the argument ``--host <hostname>`` (where <hostname> is a host from above), the script must print a JSON object, either empty or containing variables to make them available to templates and playbooks. For example:
 
+.. code-block:: json
 
     {
         "VAR001": "VALUE",
-        "VAR002": "VALUE",
+        "VAR002": "VALUE"
     }
 
 Printing variables is optional. If the script does not print variables, it should print an empty JSON object.
@@ -404,7 +407,9 @@ The stock inventory script system mentioned above works for all versions of Ansi
 
 To avoid this inefficiency, if the inventory script returns a top-level element called "_meta", it is possible to return all the host variables in a single script execution. When this meta element contains a value for "hostvars", the inventory script will not be invoked with ``--host`` for each host. This behavior results in a significant performance increase for large numbers of hosts.
 
-The data to be added to the top-level JSON object looks like this::
+The data to be added to the top-level JSON object looks like this:
+
+.. code-block:: text
 
     {
 
@@ -424,7 +429,9 @@ The data to be added to the top-level JSON object looks like this::
     }
 
 To satisfy the requirements of using ``_meta``, to prevent ansible from calling your inventory with ``--host`` you must at least populate ``_meta`` with an empty ``hostvars`` object.
-For example::
+For example:
+
+.. code-block:: text
 
     {
 

docs/docsite/rst/dev_guide/developing_module_utilities.rst

@@ -8,7 +8,9 @@ Ansible provides a number of module utilities, or snippets of shared code, that
 provide helper functions you can use when developing your own modules. The
 ``basic.py`` module utility provides the main entry point for accessing the
 Ansible library, and all Python Ansible modules must import something from
-``ansible.module_utils``. A common option is to import ``AnsibleModule``::
+``ansible.module_utils``. A common option is to import ``AnsibleModule``:
+
+.. code-block:: python
 
   from ansible.module_utils.basic import AnsibleModule
 

docs/docsite/rst/dev_guide/developing_modules.rst

@@ -36,7 +36,7 @@ If your use case isn't covered by an existing module, an action plugin, or a rol
 * I want to :ref:`write a Windows module <developing_modules_general_windows>`.
 * I want :ref:`an overview of Ansible's architecture <developing_program_flow_modules>`.
 * I want to :ref:`document my module <developing_modules_documenting>`.
-* I want to :ref:`contribute my module back to Ansible Core <developing_modules_checklist>`.
+* I want to :ref:`contribute my module to an existing Ansible collection <developing_modules_checklist>`.
 * I want to :ref:`add unit and integration tests to my module <developing_testing>`.
 * I want to :ref:`add Python 3 support to my module <developing_python_3>`.
 * I want to :ref:`write multiple modules <developing_modules_in_groups>`.

docs/docsite/rst/dev_guide/developing_modules_documenting.rst

@@ -217,11 +217,20 @@ All fields in the ``DOCUMENTATION`` block are lower-case. All fields are require
         - ref: aci_guide
           description: Detailed information on how to manage your ACI infrastructure using Ansible.
 
+        # Reference by rST documentation anchor (with custom title)
+        - ref: The official Ansible ACI guide <aci_guide>
+          description: Detailed information on how to manage your ACI infrastructure using Ansible.
+
         # Reference by Internet resource
         - name: APIC Management Information Model reference
           description: Complete reference of the APIC object model.
           link: https://developer.cisco.com/docs/apic-mim-ref/
 
+
+  * If you use ``ref:`` to link to an anchor that is not associated with a title, you must add a title to the ref for the link to work correctly.
+  * You can link to non-module plugins with ``ref:`` using the rST anchor, but plugin and module anchors are never associated with a title, so you must supply a title when you link to them. For example ``ref: namespace.collection.plugin_name lookup plugin  <ansible_collections.namespace.collection.plugin_name_lookup>``.
+
+
 :notes:
 
   * Details of any important information that doesn't fit in one of the above sections.
@@ -235,6 +244,8 @@ You can link from your module documentation to other module docs, other resource
 
 * ``L()`` for links with a heading. For example: ``See L(Ansible Automation Platform,https://www.ansible.com/products/automation-platform).`` As of Ansible 2.10, do not use ``L()`` for relative links between Ansible documentation and collection documentation.
 * ``U()`` for URLs. For example: ``See U(https://www.ansible.com/products/automation-platform) for an overview.``
+* ``R()`` for cross-references with a heading (added in Ansible 2.10). For example: ``See R(Cisco IOS Platform Guide,ios_platform_options)``.  Use the RST anchor for the cross-reference. See :ref:`adding_anchors_rst` for details.
+* ``M()`` for module names. For example: ``See also M(ansible.builtin.yum) or M(community.general.apt_rpm)``.
 
 There are also some macros which do not create links but we use them to display certain types of
 content in a uniform way:
@@ -247,12 +258,17 @@ content in a uniform way:
 
 .. note::
 
-  For links between modules and documentation within a collection, you can use either of the options above. Use ``U()`` or ``L()`` with full URLs (not relative links).
+  Cross-references with ``R()`` currently **do not work** inside option and return value documentations. They do work however in the global description, notes, and ``seealso`` descriptions.
 
 .. note::
-    - When a collection is not the right granularity, use ``C(..)``:
 
-        - ``The C(win_*) modules (spread across several collections) allow you to manage various aspects of windows hosts.``
+  For links between modules and documentation within a collection, you can use any of the options above. For links outside of your collection, use ``R()`` if available. Otherwise, use ``U()`` or ``L()`` with full URLs (not relative links). For modules, use ``M()`` with the FQCN or ``ansible.builtin`` as shown in the example. If you are creating your own documentation site, you will need to use the `intersphinx extension <https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html>`_ to convert ``R()`` and ``M()`` to the correct links.
+
+.. note::
+  To refer to a group of modules in a collection, use ``R()``.  When a collection is not the right granularity, use ``C(..)``:
+
+    - ``Refer to the R(kubernetes.core collection, plugins_in_kubernetes.core) for information on managing kubernetes clusters.``
+    - ``The C(win_*) modules (spread across several collections) allow you to manage various aspects of windows hosts.``
 
 .. note::
 
@@ -325,7 +341,9 @@ EXAMPLES block
 
 After the shebang, the UTF-8 coding, the copyright line, the license section, and the ``DOCUMENTATION`` block comes the ``EXAMPLES`` block. Here you show users how your module works with real-world examples in multi-line plain-text YAML format. The best examples are ready for the user to copy and paste into a playbook. Review and update your examples with every change to your module.
 
-Per playbook best practices, each example should include a ``name:`` line::
+Per playbook best practices, each example should include a ``name:`` line:
+
+.. code-block:: text
 
     EXAMPLES = r'''
     - name: Ensure foo is installed
@@ -371,7 +389,9 @@ Otherwise, for each value returned, provide the following fields. All fields are
   :contains:
     Optional. To describe nested return values, set ``type: dict``, or ``type: list``/``elements: dict``, or if you really have to, ``type: complex``, and repeat the elements above for each sub-field.
 
-Here are two example ``RETURN`` sections, one with three simple fields and one with a complex nested field::
+Here are two example ``RETURN`` sections, one with three simple fields and one with a complex nested field:
+
+.. code-block:: text
 
     RETURN = r'''
     dest:

docs/docsite/rst/dev_guide/developing_modules_general.rst

@@ -153,7 +153,9 @@ Verifying your module code in a playbook
 The next step in verifying your new module is to consume it with an Ansible playbook.
 
 -  Create a playbook in any directory: ``$ touch testmod.yml``
--  Add the following to the new playbook file::
+-  Add the following to the new playbook file:
+
+.. code-block:: yaml
 
     - name: test my new module
       hosts: localhost

docs/docsite/rst/dev_guide/developing_modules_general_windows.rst

@@ -579,7 +579,9 @@ are some steps that need to be followed to set this up:
     #!powershell
 
 You can add more args to ``$complex_args`` as required by the module or define the module options through a JSON file
-with the structure::
+with the structure:
+
+.. code-block:: json
 
     {
         "ANSIBLE_MODULE_ARGS": {

docs/docsite/rst/dev_guide/developing_plugins.rst

@@ -473,7 +473,7 @@ Vars plugins
 
 Vars plugins inject additional variable data into Ansible runs that did not come from an inventory source, playbook, or command line. Playbook constructs like 'host_vars' and 'group_vars' work using vars plugins.
 
-Vars plugins were partially implemented in Ansible 2.0 and rewritten to be fully implemented starting with Ansible 2.4. Vars plugins are unsupported by collections.
+Vars plugins were partially implemented in Ansible 2.0 and rewritten to be fully implemented starting with Ansible 2.4. Vars plugins are supported by collections starting with Ansible 2.10.
 
 Older plugins used a ``run`` method as their main body/work:
 

docs/docsite/rst/dev_guide/developing_program_flow_modules.rst

@@ -425,7 +425,9 @@ _ansible_selinux_special_fs
 
 List. Names of filesystems which should have a special SELinux
 context. They are used by the `AnsibleModule` methods which operate on
-files (changing attributes, moving, and copying). To set, add a comma separated string of filesystem names in :file:`ansible.cfg`::
+files (changing attributes, moving, and copying). To set, add a comma separated string of filesystem names in :file:`ansible.cfg`:
+
+.. code-block:: ini
 
   # ansible.cfg
   [selinux]

docs/docsite/rst/dev_guide/developing_rebasing.rst

@@ -14,17 +14,23 @@ Rebasing the branch used to create your PR will resolve both of these issues.
 Configuring your remotes
 ========================
 
-Before you can rebase your PR, you need to make sure you have the proper remotes configured. These instructions apply to any repository on GitHub, including collections repositories. On other platforms (bitbucket, gitlab), the same principles and commands apply but the syntax may be different. We use the ansible/ansible repository here as an example. In other repositories, the branch names may be different. Assuming you cloned your fork in the usual fashion, the ``origin`` remote will point to your fork::
+Before you can rebase your PR, you need to make sure you have the proper remotes configured. These instructions apply to any repository on GitHub, including collections repositories. On other platforms (bitbucket, gitlab), the same principles and commands apply but the syntax may be different. We use the ansible/ansible repository here as an example. In other repositories, the branch names may be different. Assuming you cloned your fork in the usual fashion, the ``origin`` remote will point to your fork:
+
+.. code-block:: shell-session
 
    $ git remote -v
    origin  git@github.com:YOUR_GITHUB_USERNAME/ansible.git (fetch)
    origin  git@github.com:YOUR_GITHUB_USERNAME/ansible.git (push)
 
-However, you also need to add a remote which points to the upstream repository::
+However, you also need to add a remote which points to the upstream repository:
+
+.. code-block:: shell-session
 
    $ git remote add upstream https://github.com/ansible/ansible.git
 
-Which should leave you with the following remotes::
+Which should leave you with the following remotes:
+
+.. code-block:: shell-session
 
    $ git remote -v
    origin  git@github.com:YOUR_GITHUB_USERNAME/ansible.git (fetch)
@@ -32,7 +38,9 @@ Which should leave you with the following remotes::
    upstream        https://github.com/ansible/ansible.git (fetch)
    upstream        https://github.com/ansible/ansible.git (push)
 
-Checking the status of your branch should show your fork is up-to-date with the ``origin`` remote::
+Checking the status of your branch should show your fork is up-to-date with the ``origin`` remote:
+
+.. code-block:: shell-session
 
    $ git status
    On branch YOUR_BRANCH
@@ -42,14 +50,18 @@ Checking the status of your branch should show your fork is up-to-date with the
 Rebasing your branch
 ====================
 
-Once you have an ``upstream`` remote configured, you can rebase the branch for your PR::
+Once you have an ``upstream`` remote configured, you can rebase the branch for your PR:
+
+.. code-block:: shell-session
 
    $ git pull --rebase upstream devel
 
 This will replay the changes in your branch on top of the changes made in the upstream ``devel`` branch.
 If there are merge conflicts, you will be prompted to resolve those before you can continue.
 
-After you rebase, the status of your branch changes::
+After you rebase, the status of your branch changes:
+
+.. code-block:: shell-session
 
    $ git status
    On branch YOUR_BRANCH
@@ -65,7 +77,9 @@ Updating your pull request
 
 Now that you've rebased your branch, you need to push your changes to GitHub to update your PR.
 
-Since rebasing re-writes git history, you will need to use a force push::
+Since rebasing re-writes git history, you will need to use a force push:
+
+.. code-block:: shell-session
 
    $ git push --force-with-lease
 

docs/docsite/rst/dev_guide/overview_architecture.rst

@@ -40,7 +40,9 @@ To add new machines, there is no additional SSL signing server involved, so ther
 
 If there's another source of truth in your infrastructure, Ansible can also connect to that. Ansible can draw inventory, group, and variable information from sources like EC2, Rackspace, OpenStack, and more.
 
-Here's what a plain text inventory file looks like::
+Here's what a plain text inventory file looks like:
+
+.. code-block:: text
 
     ---
     [webservers]
@@ -62,7 +64,9 @@ Playbooks can finely orchestrate multiple slices of your infrastructure topology
 
 Ansible's approach to orchestration is one of finely-tuned simplicity, as we believe your automation code should make perfect sense to you years down the road and there should be very little to remember about special syntax or features.
 
-Here's what a simple playbook looks like::
+Here's what a simple playbook looks like:
+
+.. code-block:: yaml
 
     ---
     - hosts: webservers