New release v2.13.5 (#79075 )

Update Ansible release version to v2.13.5rc1.post0. (#78995 )
New release v2.13.5rc1 (#78937 )
2022-10-10 10:27:11 -04:00 · 2022-10-03 15:20:03 -05:00 · 2022-10-03 11:53:54 -04:00 · 2022-09-29 16:57:40 -07:00 · 2022-09-29 16:56:13 -07:00 · 2022-09-29 16:55:51 -07:00
304 changed files with 46022 additions and 17148 deletions
--- a/changelogs/CHANGELOG-v2.13.rst
+++ b/changelogs/CHANGELOG-v2.13.rst
@ -5,13 +5,118 @@ ansible-core 2.13 "Nobody's Fault but Mine" Release Notes
 .. contents:: Topics


-v2.13.1rc1
-==========
+v2.13.5
+=======

 Release Summary
 ---------------

-| Release Date: 2022-06-13
+| Release Date: 2022-10-10
+| `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+
+Bugfixes
+--------
+
+- ``ansible-galaxy`` - remove extra server api call during dependency resolution for requirements and dependencies that are already satisfied (https://github.com/ansible/ansible/issues/77443).
+- ansible-test - Allow disabled, unsupported, unstable and destructive integration test targets to be selected using their respective prefixes.
+- ansible-test - Allow unstable tests to run when targeted changes are made and the ``--allow-unstable-changed`` option is specified (resolves https://github.com/ansible/ansible/issues/74213).
+- apt - Fix module failure when a package is not installed and only_upgrade=True. Skip that package and check the remaining requested packages for upgrades. (https://github.com/ansible/ansible/issues/78762)
+- apt module should not traceback on invalid type given as package. issue 78663.
+- known_hosts - do not return changed status when a non-existing key is removed (https://github.com/ansible/ansible/issues/78598)
+- paramiko - Add back support for ``ssh_args``, ``ssh_common_args``, and ``ssh_extra_args`` for parsing the ``ProxyCommand`` (https://github.com/ansible/ansible/issues/78750)
+- plugin loader, fix detection for existing configuration before initializing for a plugin
+
+v2.13.4
+=======
+
+Release Summary
+---------------
+
+| Release Date: 2022-09-12
+| `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+
+Bugfixes
+--------
+
+- Fix for network_cli not getting all relevant connection options
+- ansible-galaxy - Fix detection of ``--role-file`` in arguments for implicit role invocation (https://github.com/ansible/ansible/issues/78204)
+- ansible-galaxy - Fix exit codes for role search and delete (https://github.com/ansible/ansible/issues/78516)
+- ansible-test - Fix change detection for ansible-test's own integration tests.
+- ansible-test - ansible-doc sanity test - Correctly determine the fully-qualified collection name for plugins in subdirectories, resolving https://github.com/ansible/ansible/issues/78490.
+- apt - don't actually update the cache in check mode with update_cache=true.
+- apt - don't mark existing packages as manually installed in check mode (https://github.com/ansible/ansible/issues/66413).
+- apt - fix package selection to include /etc/apt/preferences(.d) (https://github.com/ansible/ansible/issues/77969)
+- urls - Guard imports of ``urllib3`` by catching ``Exception`` instead of ``ImportError`` to prevent exceptions in the import process of optional dependencies from preventing use of ``urls.py`` (https://github.com/ansible/ansible/issues/78648)
+- wait_for - Read file and perform comparisons using bytes to avoid decode errors (https://github.com/ansible/ansible/issues/78214)
+
+v2.13.3
+=======
+
+Release Summary
+---------------
+
+| Release Date: 2022-08-15
+| `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+
+Bugfixes
+--------
+
+- Avoid 'unreachable' error when chmod on AIX has 255 as return code.
+- Fix PluginLoader to mimic Python import machinery by adding module to sys.modules before exec
+- Fix dnf module documentation to indicate that comparison operators for package version require spaces around them (https://github.com/ansible/ansible/issues/78295)
+- ansible-connection - decrypt vaulted parameters before sending over the socket, as vault secrets are not available on the other side.
+- ansible-galaxy - Fix reinitializing the whole collection directory with ``ansible-galaxy collection init ns.coll --force``. Now directories and files that are not included in the collection skeleton will be removed.
+- ansible-galaxy - do not require mandatory keys in the ``galaxy.yml`` of source collections when listing them (https://github.com/ansible/ansible/issues/70180).
+- ansible-galaxy - fix listing collections that contains metadata but the namespace or name are not strings.
+- ansible-galaxy - fix setting the cache for paginated responses from Galaxy NG/AH (https://github.com/ansible/ansible/issues/77911).
+- ansible-test - Delegation for commands which generate output for programmatic consumption no longer redirect all output to stdout. The affected commands and options are ``shell``, ``sanity --lint``, ``sanity --list-tests``, ``integration --list-targets``, ``coverage analyze``
+- ansible-test - Delegation now properly handles arguments given after ``--`` on the command line.
+- ansible-test - Test configuration for collections is now parsed only once, prior to delegation. Fixes issue: https://github.com/ansible/ansible/issues/78334
+- ansible-test - The ``shell`` command no longer redirects all output to stdout when running a provided command. Any command output written to stderr will be mixed with the stderr output from ansible-test.
+- ansible-test - The ``shell`` command no longer requests a TTY when using delegation unless an interactive shell is being used. An interactive shell is the default behavior when no command is given to pass to the shell.
+- dnf - fix output parsing on systems with ``LANGUAGE`` set to a language other than English (https://github.com/ansible/ansible/issues/78193)
+- if a config setting prevents running ansible it should at least show it's "origin".
+- prevent type annotation shim failures from causing runtime failures (https://github.com/ansible/ansible/pull/77860)
+- template module/lookup - fix ``convert_data`` option that was effectively always set to True for Jinja macros (https://github.com/ansible/ansible/issues/78141)
+- uri - properly use uri parameter use_proxy (https://github.com/ansible/ansible/issues/58632)
+- yum - fix traceback when ``releasever`` is specified with ``latest`` (https://github.com/ansible/ansible/issues/78058)
+
+v2.13.2
+=======
+
+Release Summary
+---------------
+
+| Release Date: 2022-07-18
+| `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+
+Minor Changes
+-------------
+
+- ansible-test - An improved error message is shown when the download of a pip bootstrap script fails. The download now uses ``urllib2`` instead of ``urllib`` on Python 2.
+
+Bugfixes
+--------
+
+- Move undefined check from concat to finalize (https://github.com/ansible/ansible/issues/78156)
+- ansible-doc - no longer list module and plugin aliases that are created with symlinks (https://github.com/ansible/ansible/pull/78137).
+- ansible-doc - when listing modules in collections, proceed recursively. This fixes module listing for community.general 5.x.y and community.network 4.x.y (https://github.com/ansible/ansible/pull/78137).
+- ansible-doc will not add 'website for' in ":ref:" substitutions as it made them confusing.
+- file backed cache plugins now handle concurrent access by making atomic updates to the files.
+- password lookup does not ignore k=v arguments anymore.
+- user - Fix error "Permission denied" in user module while generating SSH keys (https://github.com/ansible/ansible/issues/78017).
+
+v2.13.1
+=======
+
+Release Summary
+---------------
+
+| Release Date: 2022-06-20
 | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__


--- a/changelogs/changelog.yaml
+++ b/changelogs/changelog.yaml
@ -769,6 +769,17 @@ releases:
    - 77535-prevent-losing-unsafe-lookups.yml
    - v2.13.0rc1_summary.yaml
    release_date: '2022-05-02'
+  2.13.1:
+    changes:
+      release_summary: '| Release Date: 2022-06-20
+
+        | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+        '
+    codename: Nobody's Fault but Mine
+    fragments:
+    - v2.13.1_summary.yaml
+    release_date: '2022-06-20'
  2.13.1rc1:
    changes:
      bugfixes:
@ -866,3 +877,223 @@ releases:
    - v2.13.1rc1_summary.yaml
    - windows_conn_option_fix.yml
    release_date: '2022-06-13'
+  2.13.2:
+    changes:
+      release_summary: '| Release Date: 2022-07-18
+
+        | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+        '
+    codename: Nobody's Fault but Mine
+    fragments:
+    - v2.13.2_summary.yaml
+    release_date: '2022-07-18'
+  2.13.2rc1:
+    changes:
+      bugfixes:
+      - Move undefined check from concat to finalize (https://github.com/ansible/ansible/issues/78156)
+      - ansible-doc - no longer list module and plugin aliases that are created with
+        symlinks (https://github.com/ansible/ansible/pull/78137).
+      - ansible-doc - when listing modules in collections, proceed recursively. This
+        fixes module listing for community.general 5.x.y and community.network 4.x.y
+        (https://github.com/ansible/ansible/pull/78137).
+      - ansible-doc will not add 'website for' in ":ref:" substitutions as it made
+        them confusing.
+      - file backed cache plugins now handle concurrent access by making atomic updates
+        to the files.
+      - password lookup does not ignore k=v arguments anymore.
+      - user - Fix error "Permission denied" in user module while generating SSH keys
+        (https://github.com/ansible/ansible/issues/78017).
+      minor_changes:
+      - ansible-test - An improved error message is shown when the download of a pip
+        bootstrap script fails. The download now uses ``urllib2`` instead of ``urllib``
+        on Python 2.
+      release_summary: '| Release Date: 2022-07-11
+
+        | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+        '
+    codename: Nobody's Fault but Mine
+    fragments:
+    - 78137-ansible-doc-list-modules-recursively.yml
+    - 78156-undefined-check-in-finalize.yml
+    - ansible-test-pip-bootstrap.yml
+    - atomic_cache_files.yml
+    - fix_adoc_text.yml
+    - password_lookup_fix.yml
+    - permission-denied-spwd-module.yml
+    - v2.13.2rc1_summary.yaml
+    release_date: '2022-07-11'
+  2.13.3:
+    changes:
+      release_summary: '| Release Date: 2022-08-15
+
+        | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+        '
+    codename: Nobody's Fault but Mine
+    fragments:
+    - v2.13.3_summary.yaml
+    release_date: '2022-08-15'
+  2.13.3rc1:
+    changes:
+      bugfixes:
+      - Avoid 'unreachable' error when chmod on AIX has 255 as return code.
+      - Fix PluginLoader to mimic Python import machinery by adding module to sys.modules
+        before exec
+      - Fix dnf module documentation to indicate that comparison operators for package
+        version require spaces around them (https://github.com/ansible/ansible/issues/78295)
+      - ansible-connection - decrypt vaulted parameters before sending over the socket,
+        as vault secrets are not available on the other side.
+      - ansible-galaxy - Fix reinitializing the whole collection directory with ``ansible-galaxy
+        collection init ns.coll --force``. Now directories and files that are not
+        included in the collection skeleton will be removed.
+      - ansible-galaxy - do not require mandatory keys in the ``galaxy.yml`` of source
+        collections when listing them (https://github.com/ansible/ansible/issues/70180).
+      - ansible-galaxy - fix listing collections that contains metadata but the namespace
+        or name are not strings.
+      - ansible-galaxy - fix setting the cache for paginated responses from Galaxy
+        NG/AH (https://github.com/ansible/ansible/issues/77911).
+      - ansible-test - Delegation for commands which generate output for programmatic
+        consumption no longer redirect all output to stdout. The affected commands
+        and options are ``shell``, ``sanity --lint``, ``sanity --list-tests``, ``integration
+        --list-targets``, ``coverage analyze``
+      - ansible-test - Delegation now properly handles arguments given after ``--``
+        on the command line.
+      - 'ansible-test - Test configuration for collections is now parsed only once,
+        prior to delegation. Fixes issue: https://github.com/ansible/ansible/issues/78334'
+      - ansible-test - The ``shell`` command no longer redirects all output to stdout
+        when running a provided command. Any command output written to stderr will
+        be mixed with the stderr output from ansible-test.
+      - ansible-test - The ``shell`` command no longer requests a TTY when using delegation
+        unless an interactive shell is being used. An interactive shell is the default
+        behavior when no command is given to pass to the shell.
+      - dnf - fix output parsing on systems with ``LANGUAGE`` set to a language other
+        than English (https://github.com/ansible/ansible/issues/78193)
+      - if a config setting prevents running ansible it should at least show it's
+        "origin".
+      - prevent type annotation shim failures from causing runtime failures (https://github.com/ansible/ansible/pull/77860)
+      - template module/lookup - fix ``convert_data`` option that was effectively
+        always set to True for Jinja macros (https://github.com/ansible/ansible/issues/78141)
+      - uri - properly use uri parameter use_proxy (https://github.com/ansible/ansible/issues/58632)
+      - yum - fix traceback when ``releasever`` is specified with ``latest`` (https://github.com/ansible/ansible/issues/78058)
+      release_summary: '| Release Date: 2022-08-08
+
+        | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+        '
+    codename: Nobody's Fault but Mine
+    fragments:
+    - 58632-uri-include_use_proxy.yaml
+    - 70180-collection-list-more-robust.yml
+    - 77014-ansible-galaxy-list-fix-null-metadata-namespace-name.yml
+    - 78058-yum-releasever-latest.yml
+    - 78141-template-fix-convert_data.yml
+    - 78295-dnf-fix-comparison-operators-docs.yml
+    - 78325-ansible-galaxy-fix-caching-paginated-responses-from-v3-servers.yml
+    - aix_chmod_255.yml
+    - ansible-connection_decode.yml
+    - ansible-galaxy-collection-init-force.yml
+    - ansible-test-content-config.yml
+    - ansible-test-filter-options.yml
+    - ansible-test-tty-output-handling.yml
+    - config_error_origin.yml
+    - dnf-fix-locale-language.yml
+    - self_referential.yml
+    - type_shim_exception_swallow.yml
+    - v2.13.3rc1_summary.yaml
+    release_date: '2022-08-08'
+  2.13.4:
+    changes:
+      release_summary: '| Release Date: 2022-09-12
+
+        | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+        '
+    codename: Nobody's Fault but Mine
+    fragments:
+    - v2.13.4_summary.yaml
+    release_date: '2022-09-12'
+  2.13.4rc1:
+    changes:
+      bugfixes:
+      - Fix for network_cli not getting all relevant connection options
+      - ansible-galaxy - Fix detection of ``--role-file`` in arguments for implicit
+        role invocation (https://github.com/ansible/ansible/issues/78204)
+      - ansible-galaxy - Fix exit codes for role search and delete (https://github.com/ansible/ansible/issues/78516)
+      - ansible-test - Fix change detection for ansible-test's own integration tests.
+      - ansible-test - ansible-doc sanity test - Correctly determine the fully-qualified
+        collection name for plugins in subdirectories, resolving https://github.com/ansible/ansible/issues/78490.
+      - apt - don't actually update the cache in check mode with update_cache=true.
+      - apt - don't mark existing packages as manually installed in check mode (https://github.com/ansible/ansible/issues/66413).
+      - apt - fix package selection to include /etc/apt/preferences(.d) (https://github.com/ansible/ansible/issues/77969)
+      - urls - Guard imports of ``urllib3`` by catching ``Exception`` instead of ``ImportError``
+        to prevent exceptions in the import process of optional dependencies from
+        preventing use of ``urls.py`` (https://github.com/ansible/ansible/issues/78648)
+      - wait_for - Read file and perform comparisons using bytes to avoid decode errors
+        (https://github.com/ansible/ansible/issues/78214)
+      release_summary: '| Release Date: 2022-09-06
+
+        | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+        '
+    codename: Nobody's Fault but Mine
+    fragments:
+    - 74446-network-conn-options.yaml
+    - 77969-apt-preferences.yml
+    - 78204-galaxy-role-file-detection.yml
+    - 78214-wait-for-compare-bytes.yml
+    - 78496-fix-apt-check-mode.yml
+    - 78516-galaxy-cli-exit-codes.yml
+    - 78648-urllib3-import-exceptions.yml
+    - ansible-test-ansible-doc-sanity-fqcn.yml
+    - ansible-test-self-change-classification.yml
+    - v2.13.4rc1_summary.yaml
+    release_date: '2022-09-06'
+  2.13.5:
+    changes:
+      bugfixes:
+      - apt - Fix module failure when a package is not installed and only_upgrade=True.
+        Skip that package and check the remaining requested packages for upgrades.
+        (https://github.com/ansible/ansible/issues/78762)
+      - apt module should not traceback on invalid type given as package. issue 78663.
+      - paramiko - Add back support for ``ssh_args``, ``ssh_common_args``, and ``ssh_extra_args``
+        for parsing the ``ProxyCommand`` (https://github.com/ansible/ansible/issues/78750)
+      release_summary: '| Release Date: 2022-10-10
+
+        | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+        '
+    codename: Nobody's Fault but Mine
+    fragments:
+    - 78750-paramiko-ssh-args-compat.yml
+    - 78781-fix-apt-only_upgrade-behavior.yml
+    - apt_notb.yml
+    - v2.13.5_summary.yaml
+    release_date: '2022-10-10'
+  2.13.5rc1:
+    changes:
+      bugfixes:
+      - '``ansible-galaxy`` - remove extra server api call during dependency resolution
+        for requirements and dependencies that are already satisfied (https://github.com/ansible/ansible/issues/77443).'
+      - ansible-test - Allow disabled, unsupported, unstable and destructive integration
+        test targets to be selected using their respective prefixes.
+      - ansible-test - Allow unstable tests to run when targeted changes are made
+        and the ``--allow-unstable-changed`` option is specified (resolves https://github.com/ansible/ansible/issues/74213).
+      - known_hosts - do not return changed status when a non-existing key is removed
+        (https://github.com/ansible/ansible/issues/78598)
+      - plugin loader, fix detection for existing configuration before initializing
+        for a plugin
+      release_summary: '| Release Date: 2022-10-03
+
+        | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
+
+        '
+    codename: Nobody's Fault but Mine
+    fragments:
+    - 77468-ansible-galaxy-remove-unnecessary-api-call.yml
+    - 78878--fix-known-hosts-wrong-changed-status.yaml
+    - ansible-test-integration-targets-filter.yml
+    - plugin_loader_fix.yml
+    - v2.13.5rc1_summary.yaml
+    release_date: '2022-10-03'
--- a/changelogs/fragments/58632-uri-include_use_proxy.yaml
+++ b/changelogs/fragments/58632-uri-include_use_proxy.yaml
@ -0,0 +1,2 @@
+bugfixes:
+  - uri - properly use uri parameter use_proxy (https://github.com/ansible/ansible/issues/58632)
--- a/changelogs/fragments/70180-collection-list-more-robust.yml
+++ b/changelogs/fragments/70180-collection-list-more-robust.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-galaxy - do not require mandatory keys in the ``galaxy.yml`` of source collections when listing them (https://github.com/ansible/ansible/issues/70180).
--- a/changelogs/fragments/74446-network-conn-options.yaml
+++ b/changelogs/fragments/74446-network-conn-options.yaml
@ -0,0 +1,3 @@
+---
+bugfixes:
+  - Fix for network_cli not getting all relevant connection options
--- a/changelogs/fragments/77014-ansible-galaxy-list-fix-null-metadata-namespace-name.yml
+++ b/changelogs/fragments/77014-ansible-galaxy-list-fix-null-metadata-namespace-name.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-galaxy - fix listing collections that contains metadata but the namespace or name are not strings.
--- a/changelogs/fragments/77468-ansible-galaxy-remove-unnecessary-api-call.yml
+++ b/changelogs/fragments/77468-ansible-galaxy-remove-unnecessary-api-call.yml
@ -0,0 +1,5 @@
+bugfixes:
+- >-
+  ``ansible-galaxy`` - remove extra server api call during dependency resolution
+  for requirements and dependencies that are already satisfied
+  (https://github.com/ansible/ansible/issues/77443).
--- a/changelogs/fragments/77969-apt-preferences.yml
+++ b/changelogs/fragments/77969-apt-preferences.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - apt - fix package selection to include /etc/apt/preferences(.d) (https://github.com/ansible/ansible/issues/77969)
--- a/changelogs/fragments/78058-yum-releasever-latest.yml
+++ b/changelogs/fragments/78058-yum-releasever-latest.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - "yum - fix traceback when ``releasever`` is specified with ``latest`` (https://github.com/ansible/ansible/issues/78058)"
--- a/changelogs/fragments/78137-ansible-doc-list-modules-recursively.yml
+++ b/changelogs/fragments/78137-ansible-doc-list-modules-recursively.yml
@ -0,0 +1,3 @@
+bugfixes:
+  - "ansible-doc - when listing modules in collections, proceed recursively. This fixes module listing for community.general 5.x.y and community.network 4.x.y (https://github.com/ansible/ansible/pull/78137)."
+  - "ansible-doc - no longer list module and plugin aliases that are created with symlinks (https://github.com/ansible/ansible/pull/78137)."
--- a/changelogs/fragments/78141-template-fix-convert_data.yml
+++ b/changelogs/fragments/78141-template-fix-convert_data.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - template module/lookup - fix ``convert_data`` option that was effectively always set to True for Jinja macros (https://github.com/ansible/ansible/issues/78141)
--- a/changelogs/fragments/78156-undefined-check-in-finalize.yml
+++ b/changelogs/fragments/78156-undefined-check-in-finalize.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - Move undefined check from concat to finalize (https://github.com/ansible/ansible/issues/78156)
--- a/changelogs/fragments/78204-galaxy-role-file-detection.yml
+++ b/changelogs/fragments/78204-galaxy-role-file-detection.yml
@ -0,0 +1,3 @@
+bugfixes:
+- ansible-galaxy - Fix detection of ``--role-file`` in arguments for implicit role invocation
+  (https://github.com/ansible/ansible/issues/78204)
--- a/changelogs/fragments/78214-wait-for-compare-bytes.yml
+++ b/changelogs/fragments/78214-wait-for-compare-bytes.yml
@ -0,0 +1,3 @@
+bugfixes:
+- wait_for - Read file and perform comparisons using bytes to avoid decode errors
+  (https://github.com/ansible/ansible/issues/78214)
--- a/changelogs/fragments/78295-dnf-fix-comparison-operators-docs.yml
+++ b/changelogs/fragments/78295-dnf-fix-comparison-operators-docs.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - Fix dnf module documentation to indicate that comparison operators for package version require spaces around them (https://github.com/ansible/ansible/issues/78295)
--- a/changelogs/fragments/78325-ansible-galaxy-fix-caching-paginated-responses-from-v3-servers.yml
+++ b/changelogs/fragments/78325-ansible-galaxy-fix-caching-paginated-responses-from-v3-servers.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-galaxy - fix setting the cache for paginated responses from Galaxy NG/AH (https://github.com/ansible/ansible/issues/77911).
--- a/changelogs/fragments/78496-fix-apt-check-mode.yml
+++ b/changelogs/fragments/78496-fix-apt-check-mode.yml
@ -0,0 +1,3 @@
+bugfixes:
+  - apt - don't actually update the cache in check mode with update_cache=true.
+  - apt - don't mark existing packages as manually installed in check mode (https://github.com/ansible/ansible/issues/66413).
--- a/changelogs/fragments/78516-galaxy-cli-exit-codes.yml
+++ b/changelogs/fragments/78516-galaxy-cli-exit-codes.yml
@ -0,0 +1,3 @@
+bugfixes:
+- ansible-galaxy - Fix exit codes for role search and delete
+  (https://github.com/ansible/ansible/issues/78516)
--- a/changelogs/fragments/78648-urllib3-import-exceptions.yml
+++ b/changelogs/fragments/78648-urllib3-import-exceptions.yml
@ -0,0 +1,5 @@
+bugfixes:
+- urls - Guard imports of ``urllib3`` by catching ``Exception`` instead of
+  ``ImportError`` to prevent exceptions in the import process of optional
+  dependencies from preventing use of ``urls.py``
+  (https://github.com/ansible/ansible/issues/78648)
--- a/changelogs/fragments/78750-paramiko-ssh-args-compat.yml
+++ b/changelogs/fragments/78750-paramiko-ssh-args-compat.yml
@ -0,0 +1,3 @@
+bugfixes:
+- paramiko - Add back support for ``ssh_args``, ``ssh_common_args``, and ``ssh_extra_args`` for parsing the ``ProxyCommand``
+  (https://github.com/ansible/ansible/issues/78750)
--- a/changelogs/fragments/78781-fix-apt-only_upgrade-behavior.yml
+++ b/changelogs/fragments/78781-fix-apt-only_upgrade-behavior.yml
@ -0,0 +1,4 @@
+bugfixes:
+- >-
+  apt - Fix module failure when a package is not installed and only_upgrade=True.
+  Skip that package and check the remaining requested packages for upgrades. (https://github.com/ansible/ansible/issues/78762)
--- a/changelogs/fragments/78878--fix-known-hosts-wrong-changed-status.yaml
+++ b/changelogs/fragments/78878--fix-known-hosts-wrong-changed-status.yaml
@ -0,0 +1,3 @@
+bugfixes:
+  - known_hosts - do not return changed status when a non-existing key is removed (https://github.com/ansible/ansible/issues/78598)
+  
--- a/changelogs/fragments/aix_chmod_255.yml
+++ b/changelogs/fragments/aix_chmod_255.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - Avoid 'unreachable' error when chmod on AIX has 255 as return code.
--- a/changelogs/fragments/ansible-connection_decode.yml
+++ b/changelogs/fragments/ansible-connection_decode.yml
@ -0,0 +1,3 @@
+bugfixes:
+  - ansible-connection - decrypt vaulted parameters before sending over the socket, as
+    vault secrets are not available on the other side.
--- a/changelogs/fragments/ansible-galaxy-collection-init-force.yml
+++ b/changelogs/fragments/ansible-galaxy-collection-init-force.yml
@ -0,0 +1,3 @@
+bugfixes:
+  - ansible-galaxy - Fix reinitializing the whole collection directory with ``ansible-galaxy collection init ns.coll --force``.
+    Now directories and files that are not included in the collection skeleton will be removed.
--- a/changelogs/fragments/ansible-test-ansible-doc-sanity-fqcn.yml
+++ b/changelogs/fragments/ansible-test-ansible-doc-sanity-fqcn.yml
@ -0,0 +1,3 @@
+bugfixes:
+  - ansible-test - ansible-doc sanity test - Correctly determine the fully-qualified collection name for plugins in 
+    subdirectories, resolving https://github.com/ansible/ansible/issues/78490.
--- a/changelogs/fragments/ansible-test-content-config.yml
+++ b/changelogs/fragments/ansible-test-content-config.yml
@ -0,0 +1,3 @@
+bugfixes:
+  - "ansible-test - Test configuration for collections is now parsed only once, prior to delegation.
+                    Fixes issue: https://github.com/ansible/ansible/issues/78334"
--- a/changelogs/fragments/ansible-test-filter-options.yml
+++ b/changelogs/fragments/ansible-test-filter-options.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Delegation now properly handles arguments given after ``--`` on the command line.
--- a/changelogs/fragments/ansible-test-integration-targets-filter.yml
+++ b/changelogs/fragments/ansible-test-integration-targets-filter.yml
@ -0,0 +1,4 @@
+bugfixes:
+  - ansible-test - Allow disabled, unsupported, unstable and destructive integration test targets to be selected using their respective prefixes.
+  - ansible-test - Allow unstable tests to run when targeted changes are made and the ``--allow-unstable-changed`` option is specified
+                   (resolves https://github.com/ansible/ansible/issues/74213).
--- a/changelogs/fragments/ansible-test-pip-bootstrap.yml
+++ b/changelogs/fragments/ansible-test-pip-bootstrap.yml
@ -0,0 +1,3 @@
+minor_changes:
+  - ansible-test - An improved error message is shown when the download of a pip bootstrap script fails.
+                   The download now uses ``urllib2`` instead of ``urllib`` on Python 2.
--- a/changelogs/fragments/ansible-test-self-change-classification.yml
+++ b/changelogs/fragments/ansible-test-self-change-classification.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Fix change detection for ansible-test's own integration tests.
--- a/changelogs/fragments/ansible-test-tty-output-handling.yml
+++ b/changelogs/fragments/ansible-test-tty-output-handling.yml
@ -0,0 +1,7 @@
+bugfixes:
+  - ansible-test - The ``shell`` command no longer requests a TTY when using delegation unless an interactive shell is being used.
+                   An interactive shell is the default behavior when no command is given to pass to the shell.
+  - ansible-test - The ``shell`` command no longer redirects all output to stdout when running a provided command.
+                   Any command output written to stderr will be mixed with the stderr output from ansible-test.
+  - ansible-test - Delegation for commands which generate output for programmatic consumption no longer redirect all output to stdout.
+                   The affected commands and options are ``shell``, ``sanity --lint``, ``sanity --list-tests``, ``integration --list-targets``, ``coverage analyze``
--- a/changelogs/fragments/apt_notb.yml
+++ b/changelogs/fragments/apt_notb.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - apt module should not traceback on invalid type given as package. issue 78663.
--- a/changelogs/fragments/atomic_cache_files.yml
+++ b/changelogs/fragments/atomic_cache_files.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - file backed cache plugins now handle concurrent access by making atomic updates to the files.
--- a/changelogs/fragments/config_error_origin.yml
+++ b/changelogs/fragments/config_error_origin.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - if a config setting prevents running ansible it should at least show it's "origin".
--- a/changelogs/fragments/dnf-fix-locale-language.yml
+++ b/changelogs/fragments/dnf-fix-locale-language.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - "dnf - fix output parsing on systems with ``LANGUAGE`` set to a language other than English (https://github.com/ansible/ansible/issues/78193)"
--- a/changelogs/fragments/fix_adoc_text.yml
+++ b/changelogs/fragments/fix_adoc_text.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-doc will not add 'website for' in ":ref:" substitutions as it made them confusing.
--- a/changelogs/fragments/password_lookup_fix.yml
+++ b/changelogs/fragments/password_lookup_fix.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - password lookup does not ignore k=v arguments anymore.
--- a/changelogs/fragments/permission-denied-spwd-module.yml
+++ b/changelogs/fragments/permission-denied-spwd-module.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - user - Fix error "Permission denied" in user module while generating SSH keys (https://github.com/ansible/ansible/issues/78017).
--- a/changelogs/fragments/plugin_loader_fix.yml
+++ b/changelogs/fragments/plugin_loader_fix.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - plugin loader, fix detection for existing configuration before initializing for a plugin
--- a/changelogs/fragments/self_referential.yml
+++ b/changelogs/fragments/self_referential.yml
@ -0,0 +1,2 @@
+bugfixes:
+  - Fix PluginLoader to mimic Python import machinery by adding module to sys.modules before exec
--- a/changelogs/fragments/type_shim_exception_swallow.yml
+++ b/changelogs/fragments/type_shim_exception_swallow.yml
@ -0,0 +1,2 @@
+bugfixes:
+- prevent type annotation shim failures from causing runtime failures (https://github.com/ansible/ansible/pull/77860)
--- a/changelogs/fragments/v2.13.1_summary.yaml
+++ b/changelogs/fragments/v2.13.1_summary.yaml
@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2022-06-20
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
--- a/changelogs/fragments/v2.13.2_summary.yaml
+++ b/changelogs/fragments/v2.13.2_summary.yaml
@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2022-07-18
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
--- a/changelogs/fragments/v2.13.2rc1_summary.yaml
+++ b/changelogs/fragments/v2.13.2rc1_summary.yaml
@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2022-07-11
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
--- a/changelogs/fragments/v2.13.3_summary.yaml
+++ b/changelogs/fragments/v2.13.3_summary.yaml
@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2022-08-15
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
--- a/changelogs/fragments/v2.13.3rc1_summary.yaml
+++ b/changelogs/fragments/v2.13.3rc1_summary.yaml
@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2022-08-08
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
--- a/changelogs/fragments/v2.13.4_summary.yaml
+++ b/changelogs/fragments/v2.13.4_summary.yaml
@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2022-09-12
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
--- a/changelogs/fragments/v2.13.4rc1_summary.yaml
+++ b/changelogs/fragments/v2.13.4rc1_summary.yaml
@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2022-09-06
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
--- a/changelogs/fragments/v2.13.5_summary.yaml
+++ b/changelogs/fragments/v2.13.5_summary.yaml
@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2022-10-10
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
--- a/changelogs/fragments/v2.13.5rc1_summary.yaml
+++ b/changelogs/fragments/v2.13.5rc1_summary.yaml
@ -0,0 +1,3 @@
+release_summary: |
+   | Release Date: 2022-10-03
+   | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__
--- a/docs/docsite/.templates/banner.html
+++ b/docs/docsite/.templates/banner.html
@ -15,19 +15,19 @@
    }
    var banner = '';
      var extra_banner = '';
-    /*use extra_banner for when marketing wants something extra, like a survey or AnsibleFest notice
+    /*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>' +
      '<p>' +
-        'You\'re invited to AnsibleFest 2021! ' +
+        'Immerse yourself in the automation experience October 18-19 in Chicago. ' +
      '<p>' +
-        'Explore ways to automate, innovate, and accelerate with our free virtual event September 29-30. ' +
+        'Join us for AnsibleFest 2022. ' +
      '<pr>' +
-        '<a href="https://reg.ansiblefest.redhat.com/flow/redhat/ansible21/regGenAttendee/login?sc_cid=7013a000002pemAAAQ">Register now!</a> ' +
+        '<a href="https://www.ansible.com/ansiblefest?intcmp=7013a000002tuDxAAI">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">' +
@ -46,7 +46,7 @@
        /* temp extra banner to advertise AnsibeFest2021 */
        banner += extra_banner;

-        msg += 'You are reading the <b>latest</b> (stable) community version of the Ansible documentation. Red Hat subscribers, select <b>2.9</b> in the version selection to the left for the most recent Red Hat release.';
+        msg += 'You are reading the <b>latest</b> (stable) community version of the Ansible documentation. If you are a Red Hat customer, refer to the <a href="https://access.redhat.com/support/policy/updates/ansible-automation-platform">Ansible Automation Platform Life Cycle</a> page for subscription details.';
      } else if (startsWith(current_url_path, "/ansible/2.9/")) {
        msg += 'You are reading the latest Red Hat released version of the Ansible documentation. Community users can use this version, or select <b>latest</b> from the version selector to the left for the most recent community version.';
      } else if (startsWith(current_url_path, "/ansible/devel/")) {
--- a/docs/docsite/Makefile
+++ b/docs/docsite/Makefile
@ -56,6 +56,7 @@ ifeq ($(findstring error,$(MAJOR_VERSION)), error)
 $(error "version_helper failed to determine major version")
 endif

+
 assertrst:
 ifndef rst
 	$(error specify document or pattern with rst=somefile.rst)
@ -67,6 +68,7 @@ docs: htmldocs

 coredocs: core_htmldocs

+
 generate_rst: collections_meta config cli keywords plugins testing
 core_generate_rst: collections_meta config cli keywords base_plugins testing

@ -74,7 +76,7 @@ core_generate_rst: collections_meta config cli keywords base_plugins testing
 # localisation effort. It will come at a later time.
 gettext_generate_rst: collections_meta config cli keywords testing

-# The following two symlinks are necessary to produce two different docsets
+# The following symlinks are necessary to produce two different docsets
 # from the same set of rst files (Ansible the package docs, and core docs).
 # Symlink the relevant index into place for building Ansible docs
 ansible_structure:
@ -96,9 +98,14 @@ core_structure:
 	@echo "Creating symlinks in core_structure"
 	-ln -sf ../rst/core_index.rst rst/index.rst
 	-ln -sf ../dev_guide/core_index.rst rst/dev_guide/index.rst
+# set up the correct core conf.py to use for English vs a translated language
+ifdef LANGOPTS
+	-ln -sf ../sphinx_conf/core_lang_conf.py rst/conf.py
+else
 	-ln -sf ../sphinx_conf/core_conf.py rst/conf.py
+endif

-# Symlink the relevant index into place for building core docs
+# Symlink the relevant index into place for building core translated docs
 gettext_structure:
 	@echo "Creating symlinks in gettext_structure"
 	-ln -sf ../rst/core_index.rst rst/index.rst
--- a/docs/docsite/ansible_4.inv
+++ b/docs/docsite/ansible_4.inv
--- a/docs/docsite/ansible_5.inv
+++ b/docs/docsite/ansible_5.inv
--- a/docs/docsite/ansible_6.inv
+++ b/docs/docsite/ansible_6.inv
--- a/docs/docsite/jinja2.inv
+++ b/docs/docsite/jinja2.inv
--- a/docs/docsite/python3.inv
+++ b/docs/docsite/python3.inv
--- a/docs/docsite/rst/community/collection_contributors/collection_release_with_branches.rst
+++ b/docs/docsite/rst/community/collection_contributors/collection_release_with_branches.rst
@ -203,7 +203,7 @@ Publishing the collection
  * Whether to add ignore entries to the corresponding ``tests/sanity/ignore-*.txt`` file and create issues, for example for removed features in ``modules/plugins``.

  Once the CI tests pass, merge the pull request. Make sure that this pull request is merged not too much later after the release
-  for ``verison_added`` sanity tests not to expect the wrong version for the new feature pull request.
+  for ``version_added`` sanity tests not to expect the wrong version for the new feature pull request.

 .. note::

--- a/docs/docsite/rst/community/contributions_collections.rst
+++ b/docs/docsite/rst/community/contributions_collections.rst
@ -31,3 +31,4 @@ Working with the Ansible collection repositories
 * How do I :ref:`rebase my PR <rebase_guide>`?
 * How do I learn about Ansible's :ref:`testing (CI) process <developing_testing>`?
 * How do I :ref:`deprecate a module <deprecating_modules>`?
+* See `Collection developer tutorials <https://www.ansible.com/products/ansible-community-training>`_ for a quick introduction on how to develop and test your collection contributions.
--- a/docs/docsite/rst/community/contributor_path.rst
+++ b/docs/docsite/rst/community/contributor_path.rst
@ -95,7 +95,7 @@ Become a steering committee member

  You do NOT have to be a programmer to become a steering committee member.

-The `Steering Committee <community_steering_committee>`_ member status reflects the highest level of trust which allows contributors to lead the project through making very important `decisions <https://github.com/ansible-community/community-topics/issues>`_ for the Ansible project. The Committee members are the community leaders who shape the project's future and the future of automation in the IT world in general.
+The :ref:`Steering Committee <community_steering_committee>` member status reflects the highest level of trust which allows contributors to lead the project through making very important `decisions <https://github.com/ansible-community/community-topics/issues>`_ for the Ansible project. The Committee members are the community leaders who shape the project's future and the future of automation in the IT world in general.

 To reach the status, as the current Committee members did before getting it, along with the things mentioned in this document, you should:

--- a/docs/docsite/rst/community/development_process.rst
+++ b/docs/docsite/rst/community/development_process.rst
@ -45,7 +45,7 @@ Here's an overview of the PR lifecycle:
 * Contributor addresses any feedback from reviewers
 * Developers, maintainers, community re-review
 * PR merged or closed
-* PR `backported <backport_process>`_ to one or more ``stable-X.Y`` branches (optional, bugfixes only)
+* PR :ref:`backported <backport_process>` to one or more ``stable-X.Y`` branches (optional, bugfixes only)

 Automated PR review: ansibullbot
 --------------------------------
@ -369,7 +369,7 @@ We do **not** backport features.
 .. code-block:: shell

       git fetch upstream
-       git checkout -b backport/2.12/[PR_NUMBER_FROM_DEVEL] upstream/stable-2.13
+       git checkout -b backport/2.13/[PR_NUMBER_FROM_DEVEL] upstream/stable-2.13

 #. Cherry pick the relevant commit SHA from the devel branch into your feature branch, handling merge conflicts as necessary:

--- a/docs/docsite/rst/community/maintainers_workflow.rst
+++ b/docs/docsite/rst/community/maintainers_workflow.rst
@ -8,8 +8,8 @@ Each collection community can set its own rules and workflow for managing pull r

 * :ref:`code_of_conduct`
 * :ref:`maintainer_requirements`
-* :ref:`Committer guidelines <committer_general_rules>`.
-* `PR review checklist <https://github.com/ansible/community-docs/blob/main/review_checklist.rst>`_
+* :ref:`Committer guidelines <committer_general_rules>`
+* :ref:`PR review checklist<review_checklist>`

 There can be two kinds of maintainers: :ref:`collection_maintainers` and :ref:`module_maintainers`.

@ -52,7 +52,7 @@ Collection maintainers are responsible for releasing new versions of a collectio
 #. Planning and announcement.
 #. Generating a changelog.
 #. Creating a release git tag and pushing it.
-#. Automaticly publishing the release tarball on `Ansible Galaxy <https://galaxy.ansible.com/>`_ through the `Zuul dashboard <https://dashboard.zuul.ansible.com/t/ansible/builds?pipeline=release>`_.
+#. Automatically publishing the release tarball on `Ansible Galaxy <https://galaxy.ansible.com/>`_ through the `Zuul dashboard <https://dashboard.zuul.ansible.com/t/ansible/builds?pipeline=release>`_.
 #. Final announcement.
 #. Optionally, `file a request to include a new collection into the Ansible package <https://github.com/ansible-collections/ansible-inclusion>`_.

--- a/docs/docsite/rst/core_index.rst
+++ b/docs/docsite/rst/core_index.rst
@ -65,6 +65,12 @@ This documentation covers the version of ``ansible-core`` noted in the upper lef

   dev_guide/index

+.. toctree::
+   :maxdepth: 2
+   :caption: Ansible Galaxy
+
+   galaxy/user_guide.rst
+   galaxy/dev_guide.rst

 .. toctree::
   :maxdepth: 1
--- a/docs/docsite/rst/dev_guide/developing_collections.rst
+++ b/docs/docsite/rst/dev_guide/developing_collections.rst
@ -16,6 +16,7 @@ You can create a collection and publish it to `Ansible Galaxy <https://galaxy.an
   developing_collections_shared
   developing_collections_testing
   developing_collections_distributing
+   developing_collections_documenting

 .. toctree::
   :maxdepth: 2
--- a/docs/docsite/rst/dev_guide/developing_collections_creating.rst
+++ b/docs/docsite/rst/dev_guide/developing_collections_creating.rst
@ -22,16 +22,18 @@ A user can then install your collection on their systems.
 Creating a collection skeleton
 ==============================

-To start a new collection:
+To start a new collection, run the following command in your collections directory:

 .. code-block:: bash

-    collection_dir#> ansible-galaxy collection init my_namespace.my_collection
+    ansible_collections#> ansible-galaxy collection init my_namespace.my_collection

 .. note::

 	Both the namespace and collection names use the same strict set of requirements. See `Galaxy namespaces <https://galaxy.ansible.com/docs/contributing/namespaces.html#galaxy-namespaces>`_ on the Galaxy docsite for those requirements.

+It will create the structure ``[my_namespace]/[my_collection]/[collection skeleton]``.
+.. hint:: If Git is used for version control, the corresponding repository should be initialized in the collection directory.
 Once the skeleton exists, you can populate the directories with the content you want inside the collection. See `ansible-collections <https://github.com/ansible-collections/>`_ GitHub Org to get a better idea of what you can place inside a collection.

 Reference: the ``ansible-galaxy collection`` command
--- a/docs/docsite/rst/dev_guide/developing_collections_distributing.rst
+++ b/docs/docsite/rst/dev_guide/developing_collections_distributing.rst
@ -6,15 +6,16 @@ Distributing collections

 A collection is a distribution format for Ansible content. A typical collection contains modules and other plugins that address a set of related use cases. For example, a collection might automate administering a particular database. A collection can also contain roles and playbooks.

-To distribute your collection and allow others to use it, you can publish your collection on one or more distribution servers. Distribution servers include:
+To distribute your collection and allow others to use it, you can publish your collection on one or more :term:`distribution server`. Distribution servers include:

-================================= ========================================================
+================================= ===================================================================
 Distribution server               Collections accepted
-================================= ========================================================
+================================= ===================================================================
 Ansible Galaxy                    All collections
-Red Hat Automation Hub            Only collections certified by Red Hat
+:term:`Pulp 3 Galaxy`             All collections, supports signed collections
+Red Hat Automation Hub            Only collections certified by Red Hat, supports signed collections
 Privately hosted Automation Hub   Collections authorized by the owners
-================================= ========================================================
+================================= ===================================================================

 Distributing collections involves four major steps:

@ -179,6 +180,22 @@ For more information on the :file:`galaxy.yml` file, see :ref:`collections_galax
 .. note::
     The ``build_ignore`` feature is only supported with ``ansible-galaxy collection build`` in Ansible 2.10 or newer.

+
+.. _signing_collections:
+
+Signing a collection
+--------------------------
+
+You can include a GnuPG signature with your collection on a :term:`Pulp 3 Galaxy` server. See `Enabling collection signing <https://galaxyng.netlify.app/config/collection_signing/>`_ for details.
+
+You can manually generate detached signatures for a collection using the ``gpg`` CLI using the following step. This step assume you have generated a GPG private key, but do not cover this process.
+
+.. code-block:: bash
+
+   ansible-galaxy collection build
+   tar -Oxzf namespace-name-1.0.0.tar.gz MANIFEST.json | gpg --output namespace-name-1.0.0.asc --detach-sign --armor --local-user email@example.com -
+
+
 .. _trying_collection_locally:

 Preparing to publish your collection
--- a/docs/docsite/rst/dev_guide/developing_collections_documenting.rst
+++ b/docs/docsite/rst/dev_guide/developing_collections_documenting.rst
@ -0,0 +1,30 @@
+.. _documenting_collections:
+
+***********************
+Documenting collections
+***********************
+
+Documenting modules and plugins
+===============================
+
+Documenting modules is thoroughly documented in :ref:`module_documenting`. Plugins can be documented the same way as modules, that is with ``DOCUMENTATION``, ``EXAMPLES``, and ``RETURN`` blocks.
+
+Documenting roles
+=================
+
+To document a role, you have to add a role argument spec by creating a file ``meta/argument_specs.yml`` in your role. As an example, you can look at `the argument specs file <https://github.com/sensu/sensu-go-ansible/blob/master/roles/install/meta/argument_specs.yml>`_ of the :ref:`sensu.sensu_go.install role <ansible_collections.sensu.sensu_go.install_role>` on GitHub.
+
+.. _build_collection_docsite:
+
+Build a docsite with antsibull-docs
+===================================
+
+You can use `antsibull-docs <https://pypi.org/project/antsibull-docs>`_ to build a Sphinx-based docsite for your collection:
+
+#. Create your collection and make sure you can use it with ansible-core by adding it to your :ref:`COLLECTIONS_PATHS`.
+#. Create a directory ``dest`` and run ``antsibull-docs sphinx-init --use-current --dest-dir dest namespace.name``, where ``namespace.name`` is the name of your collection.
+#. Go into ``dest`` and run ``pip install -r requirements.txt``. You might want to create a venv and activate it first to avoid installing this globally.
+#. Then run ``./build.sh``.
+#. Open ``build/html/index.html`` in a browser of your choice.
+
+If you want to add additional documentation to your collection next to the plugin, module, and role documentation, see :ref:`collections_doc_dir`.
--- a/docs/docsite/rst/dev_guide/developing_modules_documenting.rst
+++ b/docs/docsite/rst/dev_guide/developing_modules_documenting.rst
@ -33,28 +33,24 @@ Begin your Ansible module with ``#!/usr/bin/python`` - this "shebang" allows ``a
 Copyright and license
 =====================

-After the shebang and UTF-8 coding, add a `copyright line <https://www.gnu.org/licenses/gpl-howto.en.html>`_ with the original copyright holder and a license declaration. The license declaration should be ONLY one line, not the full GPL prefix.:
+After the shebang and UTF-8 coding, add a `copyright line <https://www.linuxfoundation.org/blog/copyright-notices-in-open-source-software-projects/>`_ with the original copyright holder and a license declaration. The license declaration should be ONLY one line, not the full GPL prefix.:

 .. code-block:: python

    #!/usr/bin/python
    # -*- coding: utf-8 -*-

-    # Copyright: (c) 2018, Terry Jones <terry.jones@example.org>
+    # Copyright: Contributors to the Ansible project
    # GNU General Public License v3.0+ (see COPYING or https://www.gnu.org/licenses/gpl-3.0.txt)

-Major additions to the module (for instance, rewrites) may add additional copyright lines. Any legal review will include the source control history, so an exhaustive copyright header is not necessary.
-Please do not edit the existing copyright year. This simplifies project administration and is unlikely to cause any interesting legal issues.
-When adding a second copyright line for a significant feature or rewrite, add the newer line above the older one:
+Additions to the module (for instance, rewrites) are not permitted to add additional copyright lines other than the default copyright statement if missing:

 .. code-block:: python

-    #!/usr/bin/python
-    # -*- coding: utf-8 -*-
-
-    # Copyright: (c) 2017, [New Contributor(s)]
-    # Copyright: (c) 2015, [Original Contributor(s)]
-    # GNU General Public License v3.0+ (see COPYING or https://www.gnu.org/licenses/gpl-3.0.txt)
+    # Copyright: Contributors to the Ansible project
+    
+Any legal review will include the source control history, so an exhaustive copyright header is not necessary.
+Please do not include a copyright year. If the existing copyright statement includes a year, do not edit the existing copyright year. Any existing copyright header should not be modified without permission from the copyright author.

 .. _ansible_metadata_block:

@ -451,4 +447,4 @@ The use of "wildcard" imports such as ``from module_utils.basic import *`` is no
 Testing module documentation
 ============================

-To test Ansible documentation locally please :ref:`follow instruction<testing_module_documentation>`.
+To test Ansible documentation locally please :ref:`follow instruction<testing_module_documentation>`. To test documentation in collections, please see :ref:`build_collection_docsite`.
--- a/docs/docsite/rst/dev_guide/developing_modules_general.rst
+++ b/docs/docsite/rst/dev_guide/developing_modules_general.rst
@ -80,13 +80,13 @@ The simplest way is to use ``ansible`` adhoc command:

 .. code:: shell

-    ansible -m library/my_test.py -a 'name=hello new=true' remotehost
+    ANSIBLE_LIBRARY=./library ansible -m my_test -a 'name=hello new=true' remotehost

 If your module does not need to target a remote host, you can quickly and easily exercise your code locally like this:

 .. code:: shell

-    ansible -m library/my_test.py -a 'name=hello new=true' localhost
+    ANSIBLE_LIBRARY=./library ansible -m my_test -a 'name=hello new=true' localhost

 -  If for any reason (pdb, using print(), faster iteration, etc) you want to avoid going through Ansible,
   another way is to create an arguments file, a basic JSON config file that passes parameters to your module so that you can run it.
--- a/docs/docsite/rst/dev_guide/developing_python_3.rst
+++ b/docs/docsite/rst/dev_guide/developing_python_3.rst
@ -4,7 +4,7 @@
 Ansible and Python 3
 ********************

-The ``ansible-core`` code runs Python 3 (for specific versions check `Control Node Requirements <:ref:control-node-requirements>`_.
+The ``ansible-core`` code runs Python 3 (for specific versions check :ref:`Control Node Requirements <control_node_requirements>`
 Contributors to ``ansible-core`` and to Ansible Collections should be aware of the tips in this document so that they can write code
 that will run on the same versions of Python as the rest of Ansible.

@ -25,7 +25,7 @@ However, the three types of code do not use the same string strategy. If you're
 Minimum version of Python 3.x and Python 2.x
 ============================================

-See `Control Node Requirements <:ref:control-node-requirements>`_ and `Managed Node Requirements <:ref:managed-node-requirements>`_ for the
+See :ref:`Control Node Requirements <control_node_requirements>` and `Managed Node Requirements <:ref:managed-node-requirements>`_ for the
 specific versions supported.

 Your custom modules can support any version of Python (or other languages) you want, but the above are the requirements for the code contributed to the Ansible project.
--- a/docs/docsite/rst/dev_guide/platforms/vmware_rest_guidelines.rst
+++ b/docs/docsite/rst/dev_guide/platforms/vmware_rest_guidelines.rst
@ -4,108 +4,4 @@
 Guidelines for VMware REST module development
 *********************************************

-The Ansible VMware REST collection (on `Galaxy <https://galaxy.ansible.com/vmware/vmware_rest>`_, source code `repository <https://github.com/ansible-collections/vmware.vmware_rest>`_) is maintained by Red Hat and the community.
-
-.. contents::
-   :local:
-
-Contribution process
-====================
-
-The modules of the vmware_rest collection are autogenerated by another tool called `vmware_rest_code_generator <https://github.com/ansible-collections/vmware_rest_code_generator>`.
-
-If you would like to contribute a change, we would appreciate if you:
-
- submit a Github Pull Request (PR) against the vmware_rest_code_generator project
- but also ensure the generated modules are compliant with our quality criteria.
-
-Requirements
-============
-
-You will need:
-
- Python 3.6 or greater
- the `tox <https://tox.readthedocs.io/en/latest/install.html>` command
-
-
-vmware_rest_code_generator
-==========================
-
-Your contribution should follow the coding style of `Black <https://github.com/psf/black>`.
-To run the code formatter, just run:
-
-.. code-block:: shell
-
-    tox -e black
-
-To regenerate the vmware_rest collection, you can use the following commands:
-
-.. code-block:: shell
-
-    tox -e refresh_modules -- --target-dir ~/.ansible/collections/ansible_collections/vmware/vmware_rest
-
-If you also want to update the EXAMPLE section of the modules, run:
-
-.. code-block:: shell
-
-    tox -e refresh_examples -- --target-dir ~/.ansible/collections/ansible_collections/vmware/vmware_rest
-
-Testing with ansible-test
-=========================
-
-All the modules are covered by a functional test. The tests are located in the :file:`tests/integration/targets/`.
-
-To run the tests, you will need a vcenter instance and an ESXi.
-
-black code formatter
-^^^^^^^^^^^^^^^^^^^^
-
-We follow the coding style of `Black <https://github.com/psf/black>`.
-You can run the code formatter with the following command.
-
-
-.. code-block:: shell
-
-    tox -e black
-
-sanity tests
-^^^^^^^^^^^^
-
-Here we use Python 3.8, the minimal version is 3.6.
-
-.. code-block:: shell
-
-    tox -e black
-    ansible-test sanity --debug --requirements --local --skip-test future-import-boilerplate --skip-test metaclass-boilerplate --python 3.8 -vvv
-
-
-integration tests
-^^^^^^^^^^^^^^^^^
-
-These tests should be run against your test environment.
-
-..warning:: The test suite will delete all the existing DC from your test environment. 
-
-First, prepare a configuration file, we call it :file:`/tmp/inventory-vmware_rest` in
-this example:
-
-.. code-block:: ini
-
-    [vmware_rest]
-    localhost ansible_connection=local ansible_python_interpreter=python
-    
-    [vmware_rest:vars]
-    vcenter_hostname=vcenter.test
-    vcenter_username=administrator@vsphere.local
-    vcenter_password=kLRy|FXwZSHXW0w?Q:sO
-    esxi1_hostname=esxi1.test
-    esxi1_username=zuul
-    esxi1_password=f6QYNi65k05kv8m56
-
-
-To run the tests, use the following command. You may want to adjust the Python version.
-
-.. code-block:: shell
-
-    ansible-test network-integration --diff --no-temp-workdir --python 3.8 --inventory /tmp/inventory-vmware_rest zuul/
-
+This guide has moved to :ref:`ansible_collections.vmware.vmware_rest.docsite.vmware_rest_devguide`.
--- a/docs/docsite/rst/dev_guide/shared_snippets/licensing.txt
+++ b/docs/docsite/rst/dev_guide/shared_snippets/licensing.txt
@ -7,3 +7,6 @@
      * All other ``module_utils`` must be licensed under BSD, so GPL-licensed third-party and Galaxy modules can use them.
      * If there's doubt about the appropriate license for a file in ``module_utils``, the Ansible Core Team will decide during an Ansible Core Community Meeting.
   * All other files shipped with Ansible, including all modules, must be licensed under the GPL license (GPLv3 or later).
+   * Existing license requirements still apply to content in ansible/ansible (ansible-core).
+   * Content that was previously in ansible/ansible or a collection and has moved to a new collection must retain the license it had in its prior repository.
+   * Copyright entries by previous committers must also be kept in any moved files.
--- a/docs/docsite/rst/dev_guide/style_guide/resources.rst
+++ b/docs/docsite/rst/dev_guide/style_guide/resources.rst
@ -7,4 +7,5 @@ Resources
  * `AP Stylebook <https://www.apstylebook.com>`_
  * `Chicago Manual of Style <https://www.chicagomanualofstyle.org/home.html>`_
  * `Strunk and White's Elements of Style <https://www.crockford.com/wrrrld/style.html>`_
+  * `Google developer documentation style guide <https://developers.google.com/style/highlights>`_

--- a/docs/docsite/rst/dev_guide/testing.rst
+++ b/docs/docsite/rst/dev_guide/testing.rst
@ -41,16 +41,6 @@ At a high level we have the following classifications of tests:
  * Tests directly against individual parts of the code base.


-If you're a developer, one of the most valuable things you can do is look at the GitHub
-issues list and help fix bugs.  We almost always prioritize bug fixing over feature
-development.
-
-Even for non developers, helping to test pull requests for bug fixes and features is still
-immensely valuable.  Ansible users who understand writing playbooks and roles should be
-able to add integration tests and so GitHub pull requests with integration tests that show
-bugs in action will also be a great way to help.
-
-
 Testing within GitHub & Azure Pipelines
 =======================================

--- a/docs/docsite/rst/dev_guide/testing/sanity/ignores.rst
+++ b/docs/docsite/rst/dev_guide/testing/sanity/ignores.rst
@ -74,7 +74,7 @@ If the named test uses error codes then the error code to ignore must be appende
 Below are some example ignore entries for an Ansible collection::

    roles/my_role/files/my_script.sh shellcheck:SC2154 # ignore undefined variable
-    plugins/modules/my_module.py validate-modules:E105 # ignore license check
+    plugins/modules/my_module.py validate-modules:missing-gplv3-license # ignore license check
    plugins/modules/my_module.py import-3.8 # needs update to support collections.abc on Python 3.8+

 It is also possible to skip a sanity test for a specific file.
@ -86,6 +86,8 @@ Below are some example skip entries for an Ansible collection::
    plugins/module_utils/my_util.py validate-modules!skip # waiting for bug fix in module validator
    plugins/lookup/my_plugin.py compile-2.6!skip # Python 2.6 is not supported on the controller

+See the full list of :ref:`sanity tests <all_sanity_tests>`, which details the various tests and details how to fix identified issues.
+
 Ignore File Errors
 ------------------

--- a/docs/docsite/rst/galaxy/user_guide.rst
+++ b/docs/docsite/rst/galaxy/user_guide.rst
@ -492,3 +492,6 @@ Use ``remove`` to delete a role from *roles_path*:
    Shareable collections of modules, playbooks and roles
  :ref:`playbooks_reuse_roles`
    Reusable tasks, handlers, and other files in a known directory structure
+  :ref:`command_line_tools`
+    Perform other related operations
+
--- a/docs/docsite/rst/images/ansible_basic.svg
+++ b/docs/docsite/rst/images/ansible_basic.svg
@ -24,15 +24,15 @@
     inkscape:deskcolor="#d1d1d1"
     inkscape:document-units="px"
     showgrid="false"
-     inkscape:zoom="0.84096521"
-     inkscape:cx="332.3562"
-     inkscape:cy="355.54384"
+     inkscape:zoom="0.5946522"
+     inkscape:cx="298.49381"
+     inkscape:cy="538.12968"
     inkscape:window-width="1920"
     inkscape:window-height="979"
     inkscape:window-x="0"
     inkscape:window-y="32"
     inkscape:window-maximized="1"
-     inkscape:current-layer="layer1" /><defs
+     inkscape:current-layer="g10676" /><defs
     id="defs345"><marker
       style="overflow:visible"
       id="marker10543"
@ -48,7 +48,7 @@
       preserveAspectRatio="xMidYMid"><path
         transform="scale(0.7)"
         d="m -0.21114562,-4.1055728 6.42229122,3.21114561 a 1,1 90 0 1 0,1.78885438 L -0.21114562,4.1055728 A 1.236068,1.236068 31.717474 0 1 -2,3 v -6 a 1.236068,1.236068 148.28253 0 1 1.78885438,-1.1055728 z"
-         style="fill:#4d4d4dff;fill-rule:evenodd;stroke:none"
+         style="fill-rule:evenodd;stroke:none"
         id="path10541" /></marker><marker
       style="overflow:visible"
       id="RoundedArrow"
@ -64,7 +64,7 @@
       preserveAspectRatio="xMidYMid"><path
         transform="scale(0.7)"
         d="m -0.21114562,-4.1055728 6.42229122,3.21114561 a 1,1 90 0 1 0,1.78885438 L -0.21114562,4.1055728 A 1.236068,1.236068 31.717474 0 1 -2,3 v -6 a 1.236068,1.236068 148.28253 0 1 1.78885438,-1.1055728 z"
-         style="fill:#4d4d4dff;fill-rule:evenodd;stroke:none"
+         style="fill-rule:evenodd;stroke:none"
         id="path1367" /></marker></defs><g
     inkscape:label="control node"
     inkscape:groupmode="layer"
@ -189,144 +189,145 @@
     id="layer3"
     inkscape:label="arrows"
     transform="translate(-143.23061,-11.064939)"><g
-       id="g10723"
+       id="g10676"
       transform="translate(-12.170833)"><g
-         id="g10676"><g
-           id="g10119"
-           transform="translate(7.625169,40.10635)"><g
-             id="g10026"
-             transform="translate(39.687516,-33.86668)"><g
-               aria-label="Managed node 1"
-               id="text2650-6"
+         id="g1528"><g
+           id="g10026"
+           transform="translate(47.312685,6.23967)"><g
+             aria-label="Managed node 1"
+             id="text2650-6"
+             style="font-size:7.7611px;line-height:1.25;-inkscape-font-specification:sans-serif;text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;stroke-width:0.264583"><path
+               d="m 170.84965,134.92073 h 1.14067 l 1.44384,3.85023 1.45142,-3.85023 h 1.14066 v 5.65787 h -0.74655 v -4.96817 l -1.45899,3.88055 h -0.76929 l -1.459,-3.88055 v 4.96817 h -0.74276 z"
+               id="path10856" /><path
+               d="m 179.44446,138.44505 q -0.84508,0 -1.17098,0.19327 -0.32591,0.19327 -0.32591,0.65939 0,0.37138 0.24254,0.59118 0.24632,0.21601 0.66697,0.21601 0.5798,0 0.92845,-0.40928 0.35243,-0.41307 0.35243,-1.09519 v -0.15538 z m 1.39079,-0.28801 v 2.42156 h -0.69729 v -0.64423 q -0.23874,0.38654 -0.59497,0.57223 -0.35622,0.1819 -0.87161,0.1819 -0.65181,0 -1.03835,-0.36381 -0.38274,-0.36759 -0.38274,-0.9815 0,-0.71624 0.47748,-1.08004 0.48128,-0.3638 1.43247,-0.3638 h 0.97772 v -0.0682 q 0,-0.48128 -0.31833,-0.74276 -0.31453,-0.26528 -0.88676,-0.26528 -0.3638,0 -0.70866,0.0872 -0.34485,0.0872 -0.66318,0.26148 v -0.64423 q 0.38275,-0.1478 0.74276,-0.2198 0.36002,-0.0758 0.70108,-0.0758 0.92087,0 1.37562,0.47749 0.45476,0.47749 0.45476,1.44762 z"
+               id="path10858" /><path
+               d="m 185.79962,138.01683 v 2.56177 h -0.69728 v -2.53903 q 0,-0.60255 -0.23496,-0.90193 -0.23496,-0.29938 -0.70487,-0.29938 -0.56465,0 -0.89055,0.36002 -0.32591,0.36001 -0.32591,0.9815 v 2.39882 h -0.70107 v -4.24435 h 0.70107 v 0.65939 q 0.25012,-0.38275 0.58739,-0.57223 0.34106,-0.18948 0.78445,-0.18948 0.73139,0 1.10656,0.45475 0.37517,0.45096 0.37517,1.33015 z"
+               id="path10860" /><path
+               d="m 189.11931,138.44505 q -0.84508,0 -1.17098,0.19327 -0.32591,0.19327 -0.32591,0.65939 0,0.37138 0.24253,0.59118 0.24633,0.21601 0.66697,0.21601 0.57981,0 0.92846,-0.40928 0.35243,-0.41307 0.35243,-1.09519 v -0.15538 z m 1.39078,-0.28801 v 2.42156 h -0.69728 v -0.64423 q -0.23875,0.38654 -0.59497,0.57223 -0.35622,0.1819 -0.87161,0.1819 -0.65181,0 -1.03835,-0.36381 -0.38275,-0.36759 -0.38275,-0.9815 0,-0.71624 0.47749,-1.08004 0.48128,-0.3638 1.43247,-0.3638 h 0.97772 v -0.0682 q 0,-0.48128 -0.31833,-0.74276 -0.31453,-0.26528 -0.88676,-0.26528 -0.36381,0 -0.70866,0.0872 -0.34485,0.0872 -0.66318,0.26148 v -0.64423 q 0.38275,-0.1478 0.74276,-0.2198 0.36001,-0.0758 0.70108,-0.0758 0.92087,0 1.37562,0.47749 0.45475,0.47749 0.45475,1.44762 z"
+               id="path10862" /><path
+               d="m 194.73929,138.40716 q 0,-0.75792 -0.31454,-1.17478 -0.31075,-0.41685 -0.8754,-0.41685 -0.56086,0 -0.87539,0.41685 -0.31075,0.41686 -0.31075,1.17478 0,0.75413 0.31075,1.17098 0.31453,0.41686 0.87539,0.41686 0.56465,0 0.8754,-0.41686 0.31454,-0.41685 0.31454,-1.17098 z m 0.69728,1.64468 q 0,1.08383 -0.48128,1.61058 -0.48127,0.53055 -1.47415,0.53055 -0.36759,0 -0.6935,-0.0568 -0.3259,-0.0531 -0.63286,-0.16674 v -0.67834 q 0.30696,0.16675 0.60634,0.24633 0.29938,0.0796 0.61012,0.0796 0.68592,0 1.02698,-0.36001 0.34107,-0.35623 0.34107,-1.08004 v -0.34485 q -0.21601,0.37517 -0.55328,0.56086 -0.33728,0.18569 -0.80719,0.18569 -0.78066,0 -1.25815,-0.59497 -0.47749,-0.59497 -0.47749,-1.57647 0,-0.9853 0.47749,-1.58027 0.47749,-0.59496 1.25815,-0.59496 0.46991,0 0.80719,0.18569 0.33727,0.18569 0.55328,0.56086 v -0.64423 h 0.69728 z"
+               id="path10864" /><path
+               d="m 200.50327,138.2821 v 0.34106 h -3.206 q 0.0455,0.72003 0.43201,1.09899 0.39033,0.37517 1.08383,0.37517 0.40169,0 0.77686,-0.0985 0.37896,-0.0985 0.75035,-0.29559 v 0.65939 q -0.37517,0.15916 -0.76929,0.24254 -0.39412,0.0834 -0.79961,0.0834 -1.01561,0 -1.61058,-0.59118 -0.59118,-0.59118 -0.59118,-1.59921 0,-1.04214 0.56086,-1.65227 0.56466,-0.61391 1.51963,-0.61391 0.85645,0 1.35289,0.55328 0.50023,0.54949 0.50023,1.49689 z m -0.69729,-0.20464 q -0.008,-0.57223 -0.32211,-0.91329 -0.31075,-0.34107 -0.82614,-0.34107 -0.58359,0 -0.93603,0.3297 -0.34864,0.3297 -0.4017,0.92845 z"
+               id="path10866" /><path
+               d="m 204.44066,136.97848 v -2.2965 h 0.69729 v 5.89662 h -0.69729 v -0.63665 q -0.2198,0.37896 -0.55707,0.56465 -0.33348,0.1819 -0.80339,0.1819 -0.76929,0 -1.25436,-0.61392 -0.48128,-0.61391 -0.48128,-1.61437 0,-1.00045 0.48128,-1.61437 0.48507,-0.61391 1.25436,-0.61391 0.46991,0 0.80339,0.18569 0.33727,0.1819 0.55707,0.56086 z m -2.37608,1.48173 q 0,0.76929 0.31454,1.20888 0.31833,0.43581 0.87161,0.43581 0.55328,0 0.87161,-0.43581 0.31832,-0.43959 0.31832,-1.20888 0,-0.76929 -0.31832,-1.20509 -0.31833,-0.43959 -0.87161,-0.43959 -0.55328,0 -0.87161,0.43959 -0.31454,0.4358 -0.31454,1.20509 z"
+               id="path10868" /><path
+               d="m 178.83813,147.7182 v 2.56177 h -0.69729 v -2.53903 q 0,-0.60255 -0.23495,-0.90192 -0.23496,-0.29938 -0.70487,-0.29938 -0.56465,0 -0.89056,0.36001 -0.3259,0.36001 -0.3259,0.98151 v 2.39881 h -0.70108 v -4.24435 h 0.70108 v 0.65939 q 0.25011,-0.38275 0.58739,-0.57223 0.34106,-0.18948 0.78444,-0.18948 0.7314,0 1.10657,0.45475 0.37517,0.45097 0.37517,1.33015 z"
+               id="path10870" /><path
+               d="m 181.8736,146.52448 q -0.56086,0 -0.88677,0.43959 -0.32591,0.43581 -0.32591,1.19752 0,0.76171 0.32212,1.2013 0.32591,0.4358 0.89056,0.4358 0.55707,0 0.88297,-0.43959 0.32591,-0.43959 0.32591,-1.19751 0,-0.75413 -0.32591,-1.19373 -0.3259,-0.44338 -0.88297,-0.44338 z m 0,-0.59118 q 0.9095,0 1.42868,0.59118 0.51917,0.59118 0.51917,1.63711 0,1.04214 -0.51917,1.6371 -0.51918,0.59118 -1.42868,0.59118 -0.9133,0 -1.43247,-0.59118 -0.51539,-0.59496 -0.51539,-1.6371 0,-1.04593 0.51539,-1.63711 0.51917,-0.59118 1.43247,-0.59118 z"
+               id="path10872" /><path
+               d="m 187.77021,146.67985 v -2.29649 h 0.69729 v 5.89661 h -0.69729 v -0.63665 q -0.21979,0.37896 -0.55707,0.56465 -0.33348,0.1819 -0.80339,0.1819 -0.76929,0 -1.25436,-0.61391 -0.48128,-0.61392 -0.48128,-1.61437 0,-1.00046 0.48128,-1.61437 0.48507,-0.61392 1.25436,-0.61392 0.46991,0 0.80339,0.18569 0.33728,0.1819 0.55707,0.56086 z m -2.37608,1.48174 q 0,0.76929 0.31454,1.20888 0.31833,0.4358 0.87161,0.4358 0.55328,0 0.87161,-0.4358 0.31832,-0.43959 0.31832,-1.20888 0,-0.76929 -0.31832,-1.2051 -0.31833,-0.43959 -0.87161,-0.43959 -0.55328,0 -0.87161,0.43959 -0.31454,0.43581 -0.31454,1.2051 z"
+               id="path10874" /><path
+               d="m 193.53419,147.98348 v 0.34106 h -3.206 q 0.0455,0.72002 0.43202,1.09898 0.39033,0.37517 1.08382,0.37517 0.4017,0 0.77687,-0.0985 0.37896,-0.0985 0.75034,-0.29558 v 0.65939 q -0.37517,0.15916 -0.76929,0.24253 -0.39412,0.0834 -0.7996,0.0834 -1.01562,0 -1.61058,-0.59118 -0.59118,-0.59117 -0.59118,-1.59921 0,-1.04214 0.56086,-1.65226 0.56465,-0.61392 1.51963,-0.61392 0.85645,0 1.35289,0.55328 0.50022,0.5495 0.50022,1.4969 z m -0.69728,-0.20464 q -0.008,-0.57223 -0.32212,-0.9133 -0.31074,-0.34106 -0.82613,-0.34106 -0.5836,0 -0.93603,0.32969 -0.34864,0.3297 -0.4017,0.92846 z"
+               id="path10876" /><path
+               d="m 197.37685,149.63574 h 1.25057 v -4.31635 l -1.36047,0.27285 v -0.69729 l 1.35289,-0.27285 h 0.7655 v 5.01364 h 1.25056 v 0.64423 h -3.25905 z"
+               id="path10878" /></g><g
+             id="g9222"
+             style="fill:#4d4d4d"
+             transform="matrix(1.6265445,0,0,1.8941561,158.96282,108.29438)"><path
+               d="M 25,8.37 A 0.63,0.63 0 0 0 24.38,9 0.63,0.63 0 0 0 25.63,9 0.63,0.63 0 0 0 25,8.37 Z"
+               id="path9216"
+               style="fill:#4d4d4d" /><path
+               d="M 27,8.37 A 0.63,0.63 0 0 0 26.38,9 0.63,0.63 0 0 0 27.63,9 0.63,0.63 0 0 0 27,8.37 Z"
+               id="path9218"
+               style="fill:#4d4d4d" /><path
+               d="M 31,4.38 H 5 A 0.61,0.61 0 0 0 4.38,5 V 31 A 0.61,0.61 0 0 0 5,31.62 H 31 A 0.61,0.61 0 0 0 31.62,31 V 5 A 0.61,0.61 0 0 0 31,4.38 Z m -0.62,26 H 5.62 V 5.62 h 24.76 z"
+               id="path9220"
+               style="fill:#4d4d4d" /></g></g><g
+           id="g10042"
+           transform="translate(91.762715,58.098021)"><g
+             id="g10053"
+             transform="translate(8.9958322,1.5874998)"><g
+               aria-label="Managed node 2"
+               id="text10032"
               style="font-size:7.7611px;line-height:1.25;-inkscape-font-specification:sans-serif;text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;stroke-width:0.264583"><path
                 d="m 170.84965,134.92073 h 1.14067 l 1.44384,3.85023 1.45142,-3.85023 h 1.14066 v 5.65787 h -0.74655 v -4.96817 l -1.45899,3.88055 h -0.76929 l -1.459,-3.88055 v 4.96817 h -0.74276 z"
-                 id="path10856" /><path
+                 id="path10881" /><path
                 d="m 179.44446,138.44505 q -0.84508,0 -1.17098,0.19327 -0.32591,0.19327 -0.32591,0.65939 0,0.37138 0.24254,0.59118 0.24632,0.21601 0.66697,0.21601 0.5798,0 0.92845,-0.40928 0.35243,-0.41307 0.35243,-1.09519 v -0.15538 z m 1.39079,-0.28801 v 2.42156 h -0.69729 v -0.64423 q -0.23874,0.38654 -0.59497,0.57223 -0.35622,0.1819 -0.87161,0.1819 -0.65181,0 -1.03835,-0.36381 -0.38274,-0.36759 -0.38274,-0.9815 0,-0.71624 0.47748,-1.08004 0.48128,-0.3638 1.43247,-0.3638 h 0.97772 v -0.0682 q 0,-0.48128 -0.31833,-0.74276 -0.31453,-0.26528 -0.88676,-0.26528 -0.3638,0 -0.70866,0.0872 -0.34485,0.0872 -0.66318,0.26148 v -0.64423 q 0.38275,-0.1478 0.74276,-0.2198 0.36002,-0.0758 0.70108,-0.0758 0.92087,0 1.37562,0.47749 0.45476,0.47749 0.45476,1.44762 z"
-                 id="path10858" /><path
+                 id="path10883" /><path
                 d="m 185.79962,138.01683 v 2.56177 h -0.69728 v -2.53903 q 0,-0.60255 -0.23496,-0.90193 -0.23496,-0.29938 -0.70487,-0.29938 -0.56465,0 -0.89055,0.36002 -0.32591,0.36001 -0.32591,0.9815 v 2.39882 h -0.70107 v -4.24435 h 0.70107 v 0.65939 q 0.25012,-0.38275 0.58739,-0.57223 0.34106,-0.18948 0.78445,-0.18948 0.73139,0 1.10656,0.45475 0.37517,0.45096 0.37517,1.33015 z"
-                 id="path10860" /><path
+                 id="path10885" /><path
                 d="m 189.11931,138.44505 q -0.84508,0 -1.17098,0.19327 -0.32591,0.19327 -0.32591,0.65939 0,0.37138 0.24253,0.59118 0.24633,0.21601 0.66697,0.21601 0.57981,0 0.92846,-0.40928 0.35243,-0.41307 0.35243,-1.09519 v -0.15538 z m 1.39078,-0.28801 v 2.42156 h -0.69728 v -0.64423 q -0.23875,0.38654 -0.59497,0.57223 -0.35622,0.1819 -0.87161,0.1819 -0.65181,0 -1.03835,-0.36381 -0.38275,-0.36759 -0.38275,-0.9815 0,-0.71624 0.47749,-1.08004 0.48128,-0.3638 1.43247,-0.3638 h 0.97772 v -0.0682 q 0,-0.48128 -0.31833,-0.74276 -0.31453,-0.26528 -0.88676,-0.26528 -0.36381,0 -0.70866,0.0872 -0.34485,0.0872 -0.66318,0.26148 v -0.64423 q 0.38275,-0.1478 0.74276,-0.2198 0.36001,-0.0758 0.70108,-0.0758 0.92087,0 1.37562,0.47749 0.45475,0.47749 0.45475,1.44762 z"
-                 id="path10862" /><path
+                 id="path10887" /><path
                 d="m 194.73929,138.40716 q 0,-0.75792 -0.31454,-1.17478 -0.31075,-0.41685 -0.8754,-0.41685 -0.56086,0 -0.87539,0.41685 -0.31075,0.41686 -0.31075,1.17478 0,0.75413 0.31075,1.17098 0.31453,0.41686 0.87539,0.41686 0.56465,0 0.8754,-0.41686 0.31454,-0.41685 0.31454,-1.17098 z m 0.69728,1.64468 q 0,1.08383 -0.48128,1.61058 -0.48127,0.53055 -1.47415,0.53055 -0.36759,0 -0.6935,-0.0568 -0.3259,-0.0531 -0.63286,-0.16674 v -0.67834 q 0.30696,0.16675 0.60634,0.24633 0.29938,0.0796 0.61012,0.0796 0.68592,0 1.02698,-0.36001 0.34107,-0.35623 0.34107,-1.08004 v -0.34485 q -0.21601,0.37517 -0.55328,0.56086 -0.33728,0.18569 -0.80719,0.18569 -0.78066,0 -1.25815,-0.59497 -0.47749,-0.59497 -0.47749,-1.57647 0,-0.9853 0.47749,-1.58027 0.47749,-0.59496 1.25815,-0.59496 0.46991,0 0.80719,0.18569 0.33727,0.18569 0.55328,0.56086 v -0.64423 h 0.69728 z"
-                 id="path10864" /><path
+                 id="path10889" /><path
                 d="m 200.50327,138.2821 v 0.34106 h -3.206 q 0.0455,0.72003 0.43201,1.09899 0.39033,0.37517 1.08383,0.37517 0.40169,0 0.77686,-0.0985 0.37896,-0.0985 0.75035,-0.29559 v 0.65939 q -0.37517,0.15916 -0.76929,0.24254 -0.39412,0.0834 -0.79961,0.0834 -1.01561,0 -1.61058,-0.59118 -0.59118,-0.59118 -0.59118,-1.59921 0,-1.04214 0.56086,-1.65227 0.56466,-0.61391 1.51963,-0.61391 0.85645,0 1.35289,0.55328 0.50023,0.54949 0.50023,1.49689 z m -0.69729,-0.20464 q -0.008,-0.57223 -0.32211,-0.91329 -0.31075,-0.34107 -0.82614,-0.34107 -0.58359,0 -0.93603,0.3297 -0.34864,0.3297 -0.4017,0.92845 z"
-                 id="path10866" /><path
+                 id="path10891" /><path
                 d="m 204.44066,136.97848 v -2.2965 h 0.69729 v 5.89662 h -0.69729 v -0.63665 q -0.2198,0.37896 -0.55707,0.56465 -0.33348,0.1819 -0.80339,0.1819 -0.76929,0 -1.25436,-0.61392 -0.48128,-0.61391 -0.48128,-1.61437 0,-1.00045 0.48128,-1.61437 0.48507,-0.61391 1.25436,-0.61391 0.46991,0 0.80339,0.18569 0.33727,0.1819 0.55707,0.56086 z m -2.37608,1.48173 q 0,0.76929 0.31454,1.20888 0.31833,0.43581 0.87161,0.43581 0.55328,0 0.87161,-0.43581 0.31832,-0.43959 0.31832,-1.20888 0,-0.76929 -0.31832,-1.20509 -0.31833,-0.43959 -0.87161,-0.43959 -0.55328,0 -0.87161,0.43959 -0.31454,0.4358 -0.31454,1.20509 z"
-                 id="path10868" /><path
+                 id="path10893" /><path
                 d="m 178.83813,147.7182 v 2.56177 h -0.69729 v -2.53903 q 0,-0.60255 -0.23495,-0.90192 -0.23496,-0.29938 -0.70487,-0.29938 -0.56465,0 -0.89056,0.36001 -0.3259,0.36001 -0.3259,0.98151 v 2.39881 h -0.70108 v -4.24435 h 0.70108 v 0.65939 q 0.25011,-0.38275 0.58739,-0.57223 0.34106,-0.18948 0.78444,-0.18948 0.7314,0 1.10657,0.45475 0.37517,0.45097 0.37517,1.33015 z"
-                 id="path10870" /><path
+                 id="path10895" /><path
                 d="m 181.8736,146.52448 q -0.56086,0 -0.88677,0.43959 -0.32591,0.43581 -0.32591,1.19752 0,0.76171 0.32212,1.2013 0.32591,0.4358 0.89056,0.4358 0.55707,0 0.88297,-0.43959 0.32591,-0.43959 0.32591,-1.19751 0,-0.75413 -0.32591,-1.19373 -0.3259,-0.44338 -0.88297,-0.44338 z m 0,-0.59118 q 0.9095,0 1.42868,0.59118 0.51917,0.59118 0.51917,1.63711 0,1.04214 -0.51917,1.6371 -0.51918,0.59118 -1.42868,0.59118 -0.9133,0 -1.43247,-0.59118 -0.51539,-0.59496 -0.51539,-1.6371 0,-1.04593 0.51539,-1.63711 0.51917,-0.59118 1.43247,-0.59118 z"
-                 id="path10872" /><path
+                 id="path10897" /><path
                 d="m 187.77021,146.67985 v -2.29649 h 0.69729 v 5.89661 h -0.69729 v -0.63665 q -0.21979,0.37896 -0.55707,0.56465 -0.33348,0.1819 -0.80339,0.1819 -0.76929,0 -1.25436,-0.61391 -0.48128,-0.61392 -0.48128,-1.61437 0,-1.00046 0.48128,-1.61437 0.48507,-0.61392 1.25436,-0.61392 0.46991,0 0.80339,0.18569 0.33728,0.1819 0.55707,0.56086 z m -2.37608,1.48174 q 0,0.76929 0.31454,1.20888 0.31833,0.4358 0.87161,0.4358 0.55328,0 0.87161,-0.4358 0.31832,-0.43959 0.31832,-1.20888 0,-0.76929 -0.31832,-1.2051 -0.31833,-0.43959 -0.87161,-0.43959 -0.55328,0 -0.87161,0.43959 -0.31454,0.43581 -0.31454,1.2051 z"
-                 id="path10874" /><path
+                 id="path10899" /><path
                 d="m 193.53419,147.98348 v 0.34106 h -3.206 q 0.0455,0.72002 0.43202,1.09898 0.39033,0.37517 1.08382,0.37517 0.4017,0 0.77687,-0.0985 0.37896,-0.0985 0.75034,-0.29558 v 0.65939 q -0.37517,0.15916 -0.76929,0.24253 -0.39412,0.0834 -0.7996,0.0834 -1.01562,0 -1.61058,-0.59118 -0.59118,-0.59117 -0.59118,-1.59921 0,-1.04214 0.56086,-1.65226 0.56465,-0.61392 1.51963,-0.61392 0.85645,0 1.35289,0.55328 0.50022,0.5495 0.50022,1.4969 z m -0.69728,-0.20464 q -0.008,-0.57223 -0.32212,-0.9133 -0.31074,-0.34106 -0.82613,-0.34106 -0.5836,0 -0.93603,0.32969 -0.34864,0.3297 -0.4017,0.92846 z"
-                 id="path10876" /><path
-                 d="m 197.37685,149.63574 h 1.25057 v -4.31635 l -1.36047,0.27285 v -0.69729 l 1.35289,-0.27285 h 0.7655 v 5.01364 h 1.25056 v 0.64423 h -3.25905 z"
-                 id="path10878" /></g><g
-               id="g9222"
+                 id="path10901" /><path
+                 d="m 197.9036,149.63574 h 2.67167 v 0.64423 h -3.59254 v -0.64423 q 0.4358,-0.45096 1.18614,-1.20888 0.75413,-0.76171 0.9474,-0.98151 0.3676,-0.41306 0.5116,-0.69728 0.14779,-0.28801 0.14779,-0.56465 0,-0.45097 -0.31832,-0.73519 -0.31454,-0.28422 -0.82234,-0.28422 -0.36002,0 -0.76171,0.12506 -0.39791,0.12506 -0.85266,0.37896 v -0.77308 q 0.46233,-0.18569 0.86402,-0.28043 0.4017,-0.0947 0.73519,-0.0947 0.87918,0 1.40215,0.4396 0.52296,0.43959 0.52296,1.17477 0,0.34864 -0.13263,0.66318 -0.12885,0.31075 -0.4737,0.73518 -0.0947,0.1099 -0.60255,0.63666 -0.50781,0.52296 -1.43247,1.46657 z"
+                 id="path10903" /></g><g
+               id="g10040"
               style="fill:#4d4d4d"
               transform="matrix(1.6265445,0,0,1.8941561,158.96282,108.29438)"><path
                 d="M 25,8.37 A 0.63,0.63 0 0 0 24.38,9 0.63,0.63 0 0 0 25.63,9 0.63,0.63 0 0 0 25,8.37 Z"
-                 id="path9216"
+                 id="path10034"
                 style="fill:#4d4d4d" /><path
                 d="M 27,8.37 A 0.63,0.63 0 0 0 26.38,9 0.63,0.63 0 0 0 27.63,9 0.63,0.63 0 0 0 27,8.37 Z"
-                 id="path9218"
+                 id="path10036"
                 style="fill:#4d4d4d" /><path
                 d="M 31,4.38 H 5 A 0.61,0.61 0 0 0 4.38,5 V 31 A 0.61,0.61 0 0 0 5,31.62 H 31 A 0.61,0.61 0 0 0 31.62,31 V 5 A 0.61,0.61 0 0 0 31,4.38 Z m -0.62,26 H 5.62 V 5.62 h 24.76 z"
-                 id="path9220"
-                 style="fill:#4d4d4d" /></g></g><g
-             id="g10042"
-             transform="translate(84.137546,17.991671)"><g
-               id="g10053"
-               transform="translate(8.9958322,1.5874998)"><g
-                 aria-label="Managed node 2"
-                 id="text10032"
-                 style="font-size:7.7611px;line-height:1.25;-inkscape-font-specification:sans-serif;text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;stroke-width:0.264583"><path
-                   d="m 170.84965,134.92073 h 1.14067 l 1.44384,3.85023 1.45142,-3.85023 h 1.14066 v 5.65787 h -0.74655 v -4.96817 l -1.45899,3.88055 h -0.76929 l -1.459,-3.88055 v 4.96817 h -0.74276 z"
-                   id="path10881" /><path
-                   d="m 179.44446,138.44505 q -0.84508,0 -1.17098,0.19327 -0.32591,0.19327 -0.32591,0.65939 0,0.37138 0.24254,0.59118 0.24632,0.21601 0.66697,0.21601 0.5798,0 0.92845,-0.40928 0.35243,-0.41307 0.35243,-1.09519 v -0.15538 z m 1.39079,-0.28801 v 2.42156 h -0.69729 v -0.64423 q -0.23874,0.38654 -0.59497,0.57223 -0.35622,0.1819 -0.87161,0.1819 -0.65181,0 -1.03835,-0.36381 -0.38274,-0.36759 -0.38274,-0.9815 0,-0.71624 0.47748,-1.08004 0.48128,-0.3638 1.43247,-0.3638 h 0.97772 v -0.0682 q 0,-0.48128 -0.31833,-0.74276 -0.31453,-0.26528 -0.88676,-0.26528 -0.3638,0 -0.70866,0.0872 -0.34485,0.0872 -0.66318,0.26148 v -0.64423 q 0.38275,-0.1478 0.74276,-0.2198 0.36002,-0.0758 0.70108,-0.0758 0.92087,0 1.37562,0.47749 0.45476,0.47749 0.45476,1.44762 z"
-                   id="path10883" /><path
-                   d="m 185.79962,138.01683 v 2.56177 h -0.69728 v -2.53903 q 0,-0.60255 -0.23496,-0.90193 -0.23496,-0.29938 -0.70487,-0.29938 -0.56465,0 -0.89055,0.36002 -0.32591,0.36001 -0.32591,0.9815 v 2.39882 h -0.70107 v -4.24435 h 0.70107 v 0.65939 q 0.25012,-0.38275 0.58739,-0.57223 0.34106,-0.18948 0.78445,-0.18948 0.73139,0 1.10656,0.45475 0.37517,0.45096 0.37517,1.33015 z"
-                   id="path10885" /><path
-                   d="m 189.11931,138.44505 q -0.84508,0 -1.17098,0.19327 -0.32591,0.19327 -0.32591,0.65939 0,0.37138 0.24253,0.59118 0.24633,0.21601 0.66697,0.21601 0.57981,0 0.92846,-0.40928 0.35243,-0.41307 0.35243,-1.09519 v -0.15538 z m 1.39078,-0.28801 v 2.42156 h -0.69728 v -0.64423 q -0.23875,0.38654 -0.59497,0.57223 -0.35622,0.1819 -0.87161,0.1819 -0.65181,0 -1.03835,-0.36381 -0.38275,-0.36759 -0.38275,-0.9815 0,-0.71624 0.47749,-1.08004 0.48128,-0.3638 1.43247,-0.3638 h 0.97772 v -0.0682 q 0,-0.48128 -0.31833,-0.74276 -0.31453,-0.26528 -0.88676,-0.26528 -0.36381,0 -0.70866,0.0872 -0.34485,0.0872 -0.66318,0.26148 v -0.64423 q 0.38275,-0.1478 0.74276,-0.2198 0.36001,-0.0758 0.70108,-0.0758 0.92087,0 1.37562,0.47749 0.45475,0.47749 0.45475,1.44762 z"
-                   id="path10887" /><path
-                   d="m 194.73929,138.40716 q 0,-0.75792 -0.31454,-1.17478 -0.31075,-0.41685 -0.8754,-0.41685 -0.56086,0 -0.87539,0.41685 -0.31075,0.41686 -0.31075,1.17478 0,0.75413 0.31075,1.17098 0.31453,0.41686 0.87539,0.41686 0.56465,0 0.8754,-0.41686 0.31454,-0.41685 0.31454,-1.17098 z m 0.69728,1.64468 q 0,1.08383 -0.48128,1.61058 -0.48127,0.53055 -1.47415,0.53055 -0.36759,0 -0.6935,-0.0568 -0.3259,-0.0531 -0.63286,-0.16674 v -0.67834 q 0.30696,0.16675 0.60634,0.24633 0.29938,0.0796 0.61012,0.0796 0.68592,0 1.02698,-0.36001 0.34107,-0.35623 0.34107,-1.08004 v -0.34485 q -0.21601,0.37517 -0.55328,0.56086 -0.33728,0.18569 -0.80719,0.18569 -0.78066,0 -1.25815,-0.59497 -0.47749,-0.59497 -0.47749,-1.57647 0,-0.9853 0.47749,-1.58027 0.47749,-0.59496 1.25815,-0.59496 0.46991,0 0.80719,0.18569 0.33727,0.18569 0.55328,0.56086 v -0.64423 h 0.69728 z"
-                   id="path10889" /><path
-                   d="m 200.50327,138.2821 v 0.34106 h -3.206 q 0.0455,0.72003 0.43201,1.09899 0.39033,0.37517 1.08383,0.37517 0.40169,0 0.77686,-0.0985 0.37896,-0.0985 0.75035,-0.29559 v 0.65939 q -0.37517,0.15916 -0.76929,0.24254 -0.39412,0.0834 -0.79961,0.0834 -1.01561,0 -1.61058,-0.59118 -0.59118,-0.59118 -0.59118,-1.59921 0,-1.04214 0.56086,-1.65227 0.56466,-0.61391 1.51963,-0.61391 0.85645,0 1.35289,0.55328 0.50023,0.54949 0.50023,1.49689 z m -0.69729,-0.20464 q -0.008,-0.57223 -0.32211,-0.91329 -0.31075,-0.34107 -0.82614,-0.34107 -0.58359,0 -0.93603,0.3297 -0.34864,0.3297 -0.4017,0.92845 z"
-                   id="path10891" /><path
-                   d="m 204.44066,136.97848 v -2.2965 h 0.69729 v 5.89662 h -0.69729 v -0.63665 q -0.2198,0.37896 -0.55707,0.56465 -0.33348,0.1819 -0.80339,0.1819 -0.76929,0 -1.25436,-0.61392 -0.48128,-0.61391 -0.48128,-1.61437 0,-1.00045 0.48128,-1.61437 0.48507,-0.61391 1.25436,-0.61391 0.46991,0 0.80339,0.18569 0.33727,0.1819 0.55707,0.56086 z m -2.37608,1.48173 q 0,0.76929 0.31454,1.20888 0.31833,0.43581 0.87161,0.43581 0.55328,0 0.87161,-0.43581 0.31832,-0.43959 0.31832,-1.20888 0,-0.76929 -0.31832,-1.20509 -0.31833,-0.43959 -0.87161,-0.43959 -0.55328,0 -0.87161,0.43959 -0.31454,0.4358 -0.31454,1.20509 z"
-                   id="path10893" /><path
-                   d="m 178.83813,147.7182 v 2.56177 h -0.69729 v -2.53903 q 0,-0.60255 -0.23495,-0.90192 -0.23496,-0.29938 -0.70487,-0.29938 -0.56465,0 -0.89056,0.36001 -0.3259,0.36001 -0.3259,0.98151 v 2.39881 h -0.70108 v -4.24435 h 0.70108 v 0.65939 q 0.25011,-0.38275 0.58739,-0.57223 0.34106,-0.18948 0.78444,-0.18948 0.7314,0 1.10657,0.45475 0.37517,0.45097 0.37517,1.33015 z"
-                   id="path10895" /><path
-                   d="m 181.8736,146.52448 q -0.56086,0 -0.88677,0.43959 -0.32591,0.43581 -0.32591,1.19752 0,0.76171 0.32212,1.2013 0.32591,0.4358 0.89056,0.4358 0.55707,0 0.88297,-0.43959 0.32591,-0.43959 0.32591,-1.19751 0,-0.75413 -0.32591,-1.19373 -0.3259,-0.44338 -0.88297,-0.44338 z m 0,-0.59118 q 0.9095,0 1.42868,0.59118 0.51917,0.59118 0.51917,1.63711 0,1.04214 -0.51917,1.6371 -0.51918,0.59118 -1.42868,0.59118 -0.9133,0 -1.43247,-0.59118 -0.51539,-0.59496 -0.51539,-1.6371 0,-1.04593 0.51539,-1.63711 0.51917,-0.59118 1.43247,-0.59118 z"
-                   id="path10897" /><path
-                   d="m 187.77021,146.67985 v -2.29649 h 0.69729 v 5.89661 h -0.69729 v -0.63665 q -0.21979,0.37896 -0.55707,0.56465 -0.33348,0.1819 -0.80339,0.1819 -0.76929,0 -1.25436,-0.61391 -0.48128,-0.61392 -0.48128,-1.61437 0,-1.00046 0.48128,-1.61437 0.48507,-0.61392 1.25436,-0.61392 0.46991,0 0.80339,0.18569 0.33728,0.1819 0.55707,0.56086 z m -2.37608,1.48174 q 0,0.76929 0.31454,1.20888 0.31833,0.4358 0.87161,0.4358 0.55328,0 0.87161,-0.4358 0.31832,-0.43959 0.31832,-1.20888 0,-0.76929 -0.31832,-1.2051 -0.31833,-0.43959 -0.87161,-0.43959 -0.55328,0 -0.87161,0.43959 -0.31454,0.43581 -0.31454,1.2051 z"
-                   id="path10899" /><path
-                   d="m 193.53419,147.98348 v 0.34106 h -3.206 q 0.0455,0.72002 0.43202,1.09898 0.39033,0.37517 1.08382,0.37517 0.4017,0 0.77687,-0.0985 0.37896,-0.0985 0.75034,-0.29558 v 0.65939 q -0.37517,0.15916 -0.76929,0.24253 -0.39412,0.0834 -0.7996,0.0834 -1.01562,0 -1.61058,-0.59118 -0.59118,-0.59117 -0.59118,-1.59921 0,-1.04214 0.56086,-1.65226 0.56465,-0.61392 1.51963,-0.61392 0.85645,0 1.35289,0.55328 0.50022,0.5495 0.50022,1.4969 z m -0.69728,-0.20464 q -0.008,-0.57223 -0.32212,-0.9133 -0.31074,-0.34106 -0.82613,-0.34106 -0.5836,0 -0.93603,0.32969 -0.34864,0.3297 -0.4017,0.92846 z"
-                   id="path10901" /><path
-                   d="m 197.9036,149.63574 h 2.67167 v 0.64423 h -3.59254 v -0.64423 q 0.4358,-0.45096 1.18614,-1.20888 0.75413,-0.76171 0.9474,-0.98151 0.3676,-0.41306 0.5116,-0.69728 0.14779,-0.28801 0.14779,-0.56465 0,-0.45097 -0.31832,-0.73519 -0.31454,-0.28422 -0.82234,-0.28422 -0.36002,0 -0.76171,0.12506 -0.39791,0.12506 -0.85266,0.37896 v -0.77308 q 0.46233,-0.18569 0.86402,-0.28043 0.4017,-0.0947 0.73519,-0.0947 0.87918,0 1.40215,0.4396 0.52296,0.43959 0.52296,1.17477 0,0.34864 -0.13263,0.66318 -0.12885,0.31075 -0.4737,0.73518 -0.0947,0.1099 -0.60255,0.63666 -0.50781,0.52296 -1.43247,1.46657 z"
-                   id="path10903" /></g><g
-                 id="g10040"
-                 style="fill:#4d4d4d"
-                 transform="matrix(1.6265445,0,0,1.8941561,158.96282,108.29438)"><path
-                   d="M 25,8.37 A 0.63,0.63 0 0 0 24.38,9 0.63,0.63 0 0 0 25.63,9 0.63,0.63 0 0 0 25,8.37 Z"
-                   id="path10034"
-                   style="fill:#4d4d4d" /><path
-                   d="M 27,8.37 A 0.63,0.63 0 0 0 26.38,9 0.63,0.63 0 0 0 27.63,9 0.63,0.63 0 0 0 27,8.37 Z"
-                   id="path10036"
-                   style="fill:#4d4d4d" /><path
-                   d="M 31,4.38 H 5 A 0.61,0.61 0 0 0 4.38,5 V 31 A 0.61,0.61 0 0 0 5,31.62 H 31 A 0.61,0.61 0 0 0 31.62,31 V 5 A 0.61,0.61 0 0 0 31,4.38 Z m -0.62,26 H 5.62 V 5.62 h 24.76 z"
-                   id="path10038"
-                   style="fill:#4d4d4d" /></g></g></g><g
-             id="g10071"
-             transform="translate(137.05445,71.966704)"><g
-               id="g10069"
-               transform="translate(8.9958322,1.5874998)"><g
-                 aria-label="Managed node 2"
-                 id="text10059"
-                 style="font-size:7.7611px;line-height:1.25;-inkscape-font-specification:sans-serif;text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;stroke-width:0.264583"><path
-                   d="m 170.84965,134.92073 h 1.14067 l 1.44384,3.85023 1.45142,-3.85023 h 1.14066 v 5.65787 h -0.74655 v -4.96817 l -1.45899,3.88055 h -0.76929 l -1.459,-3.88055 v 4.96817 h -0.74276 z"
-                   id="path10906" /><path
-                   d="m 179.44446,138.44505 q -0.84508,0 -1.17098,0.19327 -0.32591,0.19327 -0.32591,0.65939 0,0.37138 0.24254,0.59118 0.24632,0.21601 0.66697,0.21601 0.5798,0 0.92845,-0.40928 0.35243,-0.41307 0.35243,-1.09519 v -0.15538 z m 1.39079,-0.28801 v 2.42156 h -0.69729 v -0.64423 q -0.23874,0.38654 -0.59497,0.57223 -0.35622,0.1819 -0.87161,0.1819 -0.65181,0 -1.03835,-0.36381 -0.38274,-0.36759 -0.38274,-0.9815 0,-0.71624 0.47748,-1.08004 0.48128,-0.3638 1.43247,-0.3638 h 0.97772 v -0.0682 q 0,-0.48128 -0.31833,-0.74276 -0.31453,-0.26528 -0.88676,-0.26528 -0.3638,0 -0.70866,0.0872 -0.34485,0.0872 -0.66318,0.26148 v -0.64423 q 0.38275,-0.1478 0.74276,-0.2198 0.36002,-0.0758 0.70108,-0.0758 0.92087,0 1.37562,0.47749 0.45476,0.47749 0.45476,1.44762 z"
-                   id="path10908" /><path
-                   d="m 185.79962,138.01683 v 2.56177 h -0.69728 v -2.53903 q 0,-0.60255 -0.23496,-0.90193 -0.23496,-0.29938 -0.70487,-0.29938 -0.56465,0 -0.89055,0.36002 -0.32591,0.36001 -0.32591,0.9815 v 2.39882 h -0.70107 v -4.24435 h 0.70107 v 0.65939 q 0.25012,-0.38275 0.58739,-0.57223 0.34106,-0.18948 0.78445,-0.18948 0.73139,0 1.10656,0.45475 0.37517,0.45096 0.37517,1.33015 z"
-                   id="path10910" /><path
-                   d="m 189.11931,138.44505 q -0.84508,0 -1.17098,0.19327 -0.32591,0.19327 -0.32591,0.65939 0,0.37138 0.24253,0.59118 0.24633,0.21601 0.66697,0.21601 0.57981,0 0.92846,-0.40928 0.35243,-0.41307 0.35243,-1.09519 v -0.15538 z m 1.39078,-0.28801 v 2.42156 h -0.69728 v -0.64423 q -0.23875,0.38654 -0.59497,0.57223 -0.35622,0.1819 -0.87161,0.1819 -0.65181,0 -1.03835,-0.36381 -0.38275,-0.36759 -0.38275,-0.9815 0,-0.71624 0.47749,-1.08004 0.48128,-0.3638 1.43247,-0.3638 h 0.97772 v -0.0682 q 0,-0.48128 -0.31833,-0.74276 -0.31453,-0.26528 -0.88676,-0.26528 -0.36381,0 -0.70866,0.0872 -0.34485,0.0872 -0.66318,0.26148 v -0.64423 q 0.38275,-0.1478 0.74276,-0.2198 0.36001,-0.0758 0.70108,-0.0758 0.92087,0 1.37562,0.47749 0.45475,0.47749 0.45475,1.44762 z"
-                   id="path10912" /><path
-                   d="m 194.73929,138.40716 q 0,-0.75792 -0.31454,-1.17478 -0.31075,-0.41685 -0.8754,-0.41685 -0.56086,0 -0.87539,0.41685 -0.31075,0.41686 -0.31075,1.17478 0,0.75413 0.31075,1.17098 0.31453,0.41686 0.87539,0.41686 0.56465,0 0.8754,-0.41686 0.31454,-0.41685 0.31454,-1.17098 z m 0.69728,1.64468 q 0,1.08383 -0.48128,1.61058 -0.48127,0.53055 -1.47415,0.53055 -0.36759,0 -0.6935,-0.0568 -0.3259,-0.0531 -0.63286,-0.16674 v -0.67834 q 0.30696,0.16675 0.60634,0.24633 0.29938,0.0796 0.61012,0.0796 0.68592,0 1.02698,-0.36001 0.34107,-0.35623 0.34107,-1.08004 v -0.34485 q -0.21601,0.37517 -0.55328,0.56086 -0.33728,0.18569 -0.80719,0.18569 -0.78066,0 -1.25815,-0.59497 -0.47749,-0.59497 -0.47749,-1.57647 0,-0.9853 0.47749,-1.58027 0.47749,-0.59496 1.25815,-0.59496 0.46991,0 0.80719,0.18569 0.33727,0.18569 0.55328,0.56086 v -0.64423 h 0.69728 z"
-                   id="path10914" /><path
-                   d="m 200.50327,138.2821 v 0.34106 h -3.206 q 0.0455,0.72003 0.43201,1.09899 0.39033,0.37517 1.08383,0.37517 0.40169,0 0.77686,-0.0985 0.37896,-0.0985 0.75035,-0.29559 v 0.65939 q -0.37517,0.15916 -0.76929,0.24254 -0.39412,0.0834 -0.79961,0.0834 -1.01561,0 -1.61058,-0.59118 -0.59118,-0.59118 -0.59118,-1.59921 0,-1.04214 0.56086,-1.65227 0.56466,-0.61391 1.51963,-0.61391 0.85645,0 1.35289,0.55328 0.50023,0.54949 0.50023,1.49689 z m -0.69729,-0.20464 q -0.008,-0.57223 -0.32211,-0.91329 -0.31075,-0.34107 -0.82614,-0.34107 -0.58359,0 -0.93603,0.3297 -0.34864,0.3297 -0.4017,0.92845 z"
-                   id="path10916" /><path
-                   d="m 204.44066,136.97848 v -2.2965 h 0.69729 v 5.89662 h -0.69729 v -0.63665 q -0.2198,0.37896 -0.55707,0.56465 -0.33348,0.1819 -0.80339,0.1819 -0.76929,0 -1.25436,-0.61392 -0.48128,-0.61391 -0.48128,-1.61437 0,-1.00045 0.48128,-1.61437 0.48507,-0.61391 1.25436,-0.61391 0.46991,0 0.80339,0.18569 0.33727,0.1819 0.55707,0.56086 z m -2.37608,1.48173 q 0,0.76929 0.31454,1.20888 0.31833,0.43581 0.87161,0.43581 0.55328,0 0.87161,-0.43581 0.31832,-0.43959 0.31832,-1.20888 0,-0.76929 -0.31832,-1.20509 -0.31833,-0.43959 -0.87161,-0.43959 -0.55328,0 -0.87161,0.43959 -0.31454,0.4358 -0.31454,1.20509 z"
-                   id="path10918" /><path
-                   d="m 178.83813,147.7182 v 2.56177 h -0.69729 v -2.53903 q 0,-0.60255 -0.23495,-0.90192 -0.23496,-0.29938 -0.70487,-0.29938 -0.56465,0 -0.89056,0.36001 -0.3259,0.36001 -0.3259,0.98151 v 2.39881 h -0.70108 v -4.24435 h 0.70108 v 0.65939 q 0.25011,-0.38275 0.58739,-0.57223 0.34106,-0.18948 0.78444,-0.18948 0.7314,0 1.10657,0.45475 0.37517,0.45097 0.37517,1.33015 z"
-                   id="path10920" /><path
-                   d="m 181.8736,146.52448 q -0.56086,0 -0.88677,0.43959 -0.32591,0.43581 -0.32591,1.19752 0,0.76171 0.32212,1.2013 0.32591,0.4358 0.89056,0.4358 0.55707,0 0.88297,-0.43959 0.32591,-0.43959 0.32591,-1.19751 0,-0.75413 -0.32591,-1.19373 -0.3259,-0.44338 -0.88297,-0.44338 z m 0,-0.59118 q 0.9095,0 1.42868,0.59118 0.51917,0.59118 0.51917,1.63711 0,1.04214 -0.51917,1.6371 -0.51918,0.59118 -1.42868,0.59118 -0.9133,0 -1.43247,-0.59118 -0.51539,-0.59496 -0.51539,-1.6371 0,-1.04593 0.51539,-1.63711 0.51917,-0.59118 1.43247,-0.59118 z"
-                   id="path10922" /><path
-                   d="m 187.77021,146.67985 v -2.29649 h 0.69729 v 5.89661 h -0.69729 v -0.63665 q -0.21979,0.37896 -0.55707,0.56465 -0.33348,0.1819 -0.80339,0.1819 -0.76929,0 -1.25436,-0.61391 -0.48128,-0.61392 -0.48128,-1.61437 0,-1.00046 0.48128,-1.61437 0.48507,-0.61392 1.25436,-0.61392 0.46991,0 0.80339,0.18569 0.33728,0.1819 0.55707,0.56086 z m -2.37608,1.48174 q 0,0.76929 0.31454,1.20888 0.31833,0.4358 0.87161,0.4358 0.55328,0 0.87161,-0.4358 0.31832,-0.43959 0.31832,-1.20888 0,-0.76929 -0.31832,-1.2051 -0.31833,-0.43959 -0.87161,-0.43959 -0.55328,0 -0.87161,0.43959 -0.31454,0.43581 -0.31454,1.2051 z"
-                   id="path10924" /><path
-                   d="m 193.53419,147.98348 v 0.34106 h -3.206 q 0.0455,0.72002 0.43202,1.09898 0.39033,0.37517 1.08382,0.37517 0.4017,0 0.77687,-0.0985 0.37896,-0.0985 0.75034,-0.29558 v 0.65939 q -0.37517,0.15916 -0.76929,0.24253 -0.39412,0.0834 -0.7996,0.0834 -1.01562,0 -1.61058,-0.59118 -0.59118,-0.59117 -0.59118,-1.59921 0,-1.04214 0.56086,-1.65226 0.56465,-0.61392 1.51963,-0.61392 0.85645,0 1.35289,0.55328 0.50022,0.5495 0.50022,1.4969 z m -0.69728,-0.20464 q -0.008,-0.57223 -0.32212,-0.9133 -0.31074,-0.34106 -0.82613,-0.34106 -0.5836,0 -0.93603,0.32969 -0.34864,0.3297 -0.4017,0.92846 z"
-                   id="path10926" /><path
-                   d="m 197.9036,149.63574 h 2.67167 v 0.64423 h -3.59254 v -0.64423 q 0.4358,-0.45096 1.18614,-1.20888 0.75413,-0.76171 0.9474,-0.98151 0.3676,-0.41306 0.5116,-0.69728 0.14779,-0.28801 0.14779,-0.56465 0,-0.45097 -0.31832,-0.73519 -0.31454,-0.28422 -0.82234,-0.28422 -0.36002,0 -0.76171,0.12506 -0.39791,0.12506 -0.85266,0.37896 v -0.77308 q 0.46233,-0.18569 0.86402,-0.28043 0.4017,-0.0947 0.73519,-0.0947 0.87918,0 1.40215,0.4396 0.52296,0.43959 0.52296,1.17477 0,0.34864 -0.13263,0.66318 -0.12885,0.31075 -0.4737,0.73518 -0.0947,0.1099 -0.60255,0.63666 -0.50781,0.52296 -1.43247,1.46657 z"
-                   id="path10928" /></g><g
-                 id="g10067"
-                 style="fill:#4d4d4d"
-                 transform="matrix(1.6265445,0,0,1.8941561,158.96282,108.29438)"><path
-                   d="M 25,8.37 A 0.63,0.63 0 0 0 24.38,9 0.63,0.63 0 0 0 25.63,9 0.63,0.63 0 0 0 25,8.37 Z"
-                   id="path10061"
-                   style="fill:#4d4d4d" /><path
-                   d="M 27,8.37 A 0.63,0.63 0 0 0 26.38,9 0.63,0.63 0 0 0 27.63,9 0.63,0.63 0 0 0 27,8.37 Z"
-                   id="path10063"
-                   style="fill:#4d4d4d" /><path
-                   d="M 31,4.38 H 5 A 0.61,0.61 0 0 0 4.38,5 V 31 A 0.61,0.61 0 0 0 5,31.62 H 31 A 0.61,0.61 0 0 0 31.62,31 V 5 A 0.61,0.61 0 0 0 31,4.38 Z m -0.62,26 H 5.62 V 5.62 h 24.76 z"
-                   id="path10065"
-                   style="fill:#4d4d4d" /></g></g></g></g><path
+                 id="path10038"
+                 style="fill:#4d4d4d" /></g></g></g><g
+           id="g10071"
+           transform="translate(144.67962,112.07305)"><g
+             id="g1465"><g
+               aria-label="Managed node 3"
+               id="text10059"
+               style="font-size:7.7611px;line-height:1.25;-inkscape-font-specification:sans-serif;text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;stroke-width:0.264583"
+               transform="translate(8.9958322,1.5874998)"><path
+                 d="m 170.84965,134.92073 h 1.14067 l 1.44384,3.85023 1.45142,-3.85023 h 1.14066 v 5.65787 h -0.74655 v -4.96817 l -1.45899,3.88055 h -0.76929 l -1.459,-3.88055 v 4.96817 h -0.74276 z"
+                 id="path10906" /><path
+                 d="m 179.44446,138.44505 q -0.84508,0 -1.17098,0.19327 -0.32591,0.19327 -0.32591,0.65939 0,0.37138 0.24254,0.59118 0.24632,0.21601 0.66697,0.21601 0.5798,0 0.92845,-0.40928 0.35243,-0.41307 0.35243,-1.09519 v -0.15538 z m 1.39079,-0.28801 v 2.42156 h -0.69729 v -0.64423 q -0.23874,0.38654 -0.59497,0.57223 -0.35622,0.1819 -0.87161,0.1819 -0.65181,0 -1.03835,-0.36381 -0.38274,-0.36759 -0.38274,-0.9815 0,-0.71624 0.47748,-1.08004 0.48128,-0.3638 1.43247,-0.3638 h 0.97772 v -0.0682 q 0,-0.48128 -0.31833,-0.74276 -0.31453,-0.26528 -0.88676,-0.26528 -0.3638,0 -0.70866,0.0872 -0.34485,0.0872 -0.66318,0.26148 v -0.64423 q 0.38275,-0.1478 0.74276,-0.2198 0.36002,-0.0758 0.70108,-0.0758 0.92087,0 1.37562,0.47749 0.45476,0.47749 0.45476,1.44762 z"
+                 id="path10908" /><path
+                 d="m 185.79962,138.01683 v 2.56177 h -0.69728 v -2.53903 q 0,-0.60255 -0.23496,-0.90193 -0.23496,-0.29938 -0.70487,-0.29938 -0.56465,0 -0.89055,0.36002 -0.32591,0.36001 -0.32591,0.9815 v 2.39882 h -0.70107 v -4.24435 h 0.70107 v 0.65939 q 0.25012,-0.38275 0.58739,-0.57223 0.34106,-0.18948 0.78445,-0.18948 0.73139,0 1.10656,0.45475 0.37517,0.45096 0.37517,1.33015 z"
+                 id="path10910" /><path
+                 d="m 189.11931,138.44505 q -0.84508,0 -1.17098,0.19327 -0.32591,0.19327 -0.32591,0.65939 0,0.37138 0.24253,0.59118 0.24633,0.21601 0.66697,0.21601 0.57981,0 0.92846,-0.40928 0.35243,-0.41307 0.35243,-1.09519 v -0.15538 z m 1.39078,-0.28801 v 2.42156 h -0.69728 v -0.64423 q -0.23875,0.38654 -0.59497,0.57223 -0.35622,0.1819 -0.87161,0.1819 -0.65181,0 -1.03835,-0.36381 -0.38275,-0.36759 -0.38275,-0.9815 0,-0.71624 0.47749,-1.08004 0.48128,-0.3638 1.43247,-0.3638 h 0.97772 v -0.0682 q 0,-0.48128 -0.31833,-0.74276 -0.31453,-0.26528 -0.88676,-0.26528 -0.36381,0 -0.70866,0.0872 -0.34485,0.0872 -0.66318,0.26148 v -0.64423 q 0.38275,-0.1478 0.74276,-0.2198 0.36001,-0.0758 0.70108,-0.0758 0.92087,0 1.37562,0.47749 0.45475,0.47749 0.45475,1.44762 z"
+                 id="path10912" /><path
+                 d="m 194.73929,138.40716 q 0,-0.75792 -0.31454,-1.17478 -0.31075,-0.41685 -0.8754,-0.41685 -0.56086,0 -0.87539,0.41685 -0.31075,0.41686 -0.31075,1.17478 0,0.75413 0.31075,1.17098 0.31453,0.41686 0.87539,0.41686 0.56465,0 0.8754,-0.41686 0.31454,-0.41685 0.31454,-1.17098 z m 0.69728,1.64468 q 0,1.08383 -0.48128,1.61058 -0.48127,0.53055 -1.47415,0.53055 -0.36759,0 -0.6935,-0.0568 -0.3259,-0.0531 -0.63286,-0.16674 v -0.67834 q 0.30696,0.16675 0.60634,0.24633 0.29938,0.0796 0.61012,0.0796 0.68592,0 1.02698,-0.36001 0.34107,-0.35623 0.34107,-1.08004 v -0.34485 q -0.21601,0.37517 -0.55328,0.56086 -0.33728,0.18569 -0.80719,0.18569 -0.78066,0 -1.25815,-0.59497 -0.47749,-0.59497 -0.47749,-1.57647 0,-0.9853 0.47749,-1.58027 0.47749,-0.59496 1.25815,-0.59496 0.46991,0 0.80719,0.18569 0.33727,0.18569 0.55328,0.56086 v -0.64423 h 0.69728 z"
+                 id="path10914" /><path
+                 d="m 200.50327,138.2821 v 0.34106 h -3.206 q 0.0455,0.72003 0.43201,1.09899 0.39033,0.37517 1.08383,0.37517 0.40169,0 0.77686,-0.0985 0.37896,-0.0985 0.75035,-0.29559 v 0.65939 q -0.37517,0.15916 -0.76929,0.24254 -0.39412,0.0834 -0.79961,0.0834 -1.01561,0 -1.61058,-0.59118 -0.59118,-0.59118 -0.59118,-1.59921 0,-1.04214 0.56086,-1.65227 0.56466,-0.61391 1.51963,-0.61391 0.85645,0 1.35289,0.55328 0.50023,0.54949 0.50023,1.49689 z m -0.69729,-0.20464 q -0.008,-0.57223 -0.32211,-0.91329 -0.31075,-0.34107 -0.82614,-0.34107 -0.58359,0 -0.93603,0.3297 -0.34864,0.3297 -0.4017,0.92845 z"
+                 id="path10916" /><path
+                 d="m 204.44066,136.97848 v -2.2965 h 0.69729 v 5.89662 h -0.69729 v -0.63665 q -0.2198,0.37896 -0.55707,0.56465 -0.33348,0.1819 -0.80339,0.1819 -0.76929,0 -1.25436,-0.61392 -0.48128,-0.61391 -0.48128,-1.61437 0,-1.00045 0.48128,-1.61437 0.48507,-0.61391 1.25436,-0.61391 0.46991,0 0.80339,0.18569 0.33727,0.1819 0.55707,0.56086 z m -2.37608,1.48173 q 0,0.76929 0.31454,1.20888 0.31833,0.43581 0.87161,0.43581 0.55328,0 0.87161,-0.43581 0.31832,-0.43959 0.31832,-1.20888 0,-0.76929 -0.31832,-1.20509 -0.31833,-0.43959 -0.87161,-0.43959 -0.55328,0 -0.87161,0.43959 -0.31454,0.4358 -0.31454,1.20509 z"
+                 id="path10918" /><path
+                 d="m 178.83813,147.7182 v 2.56177 h -0.69729 v -2.53903 q 0,-0.60255 -0.23495,-0.90192 -0.23496,-0.29938 -0.70487,-0.29938 -0.56465,0 -0.89056,0.36001 -0.3259,0.36001 -0.3259,0.98151 v 2.39881 h -0.70108 v -4.24435 h 0.70108 v 0.65939 q 0.25011,-0.38275 0.58739,-0.57223 0.34106,-0.18948 0.78444,-0.18948 0.7314,0 1.10657,0.45475 0.37517,0.45097 0.37517,1.33015 z"
+                 id="path10920" /><path
+                 d="m 181.8736,146.52448 q -0.56086,0 -0.88677,0.43959 -0.32591,0.43581 -0.32591,1.19752 0,0.76171 0.32212,1.2013 0.32591,0.4358 0.89056,0.4358 0.55707,0 0.88297,-0.43959 0.32591,-0.43959 0.32591,-1.19751 0,-0.75413 -0.32591,-1.19373 -0.3259,-0.44338 -0.88297,-0.44338 z m 0,-0.59118 q 0.9095,0 1.42868,0.59118 0.51917,0.59118 0.51917,1.63711 0,1.04214 -0.51917,1.6371 -0.51918,0.59118 -1.42868,0.59118 -0.9133,0 -1.43247,-0.59118 -0.51539,-0.59496 -0.51539,-1.6371 0,-1.04593 0.51539,-1.63711 0.51917,-0.59118 1.43247,-0.59118 z"
+                 id="path10922" /><path
+                 d="m 187.77021,146.67985 v -2.29649 h 0.69729 v 5.89661 h -0.69729 v -0.63665 q -0.21979,0.37896 -0.55707,0.56465 -0.33348,0.1819 -0.80339,0.1819 -0.76929,0 -1.25436,-0.61391 -0.48128,-0.61392 -0.48128,-1.61437 0,-1.00046 0.48128,-1.61437 0.48507,-0.61392 1.25436,-0.61392 0.46991,0 0.80339,0.18569 0.33728,0.1819 0.55707,0.56086 z m -2.37608,1.48174 q 0,0.76929 0.31454,1.20888 0.31833,0.4358 0.87161,0.4358 0.55328,0 0.87161,-0.4358 0.31832,-0.43959 0.31832,-1.20888 0,-0.76929 -0.31832,-1.2051 -0.31833,-0.43959 -0.87161,-0.43959 -0.55328,0 -0.87161,0.43959 -0.31454,0.43581 -0.31454,1.2051 z"
+                 id="path10924" /><path
+                 d="m 193.53419,147.98348 v 0.34106 h -3.206 q 0.0455,0.72002 0.43202,1.09898 0.39033,0.37517 1.08382,0.37517 0.4017,0 0.77687,-0.0985 0.37896,-0.0985 0.75034,-0.29558 v 0.65939 q -0.37517,0.15916 -0.76929,0.24253 -0.39412,0.0834 -0.7996,0.0834 -1.01562,0 -1.61058,-0.59118 -0.59118,-0.59117 -0.59118,-1.59921 0,-1.04214 0.56086,-1.65226 0.56465,-0.61392 1.51963,-0.61392 0.85645,0 1.35289,0.55328 0.50022,0.5495 0.50022,1.4969 z m -0.69728,-0.20464 q -0.008,-0.57223 -0.32212,-0.9133 -0.31074,-0.34106 -0.82613,-0.34106 -0.5836,0 -0.93603,0.32969 -0.34864,0.3297 -0.4017,0.92846 z"
+                 id="path10926" /><g
+                 aria-label="3"
+                 id="text1395"
+                 style="stroke-width:0.0700042"><path
+                   d="m 199.62715,147.22002 q 0.54949,0.11748 0.85645,0.48886 0.31074,0.37138 0.31074,0.91708 0,0.8375 -0.57601,1.29604 -0.57602,0.45854 -1.63711,0.45854 -0.35622,0 -0.73518,-0.072 -0.37517,-0.0682 -0.77687,-0.20843 v -0.73897 q 0.31832,0.18569 0.69728,0.28043 0.37896,0.0947 0.79203,0.0947 0.72002,0 1.09519,-0.28422 0.37896,-0.28422 0.37896,-0.82613 0,-0.50023 -0.35243,-0.78066 -0.34864,-0.28422 -0.97392,-0.28422 h -0.6594 v -0.62907 h 0.68971 q 0.56465,0 0.86403,-0.22359 0.29938,-0.22737 0.29938,-0.65181 0,-0.4358 -0.31075,-0.66697 -0.30696,-0.23495 -0.88297,-0.23495 -0.31454,0 -0.67455,0.0682 -0.36002,0.0682 -0.79203,0.21222 v -0.68213 q 0.4358,-0.12127 0.81476,-0.1819 0.38275,-0.0606 0.72003,-0.0606 0.87161,0 1.37941,0.39791 0.50781,0.39412 0.50781,1.06867 0,0.46991 -0.26906,0.79581 -0.26906,0.32212 -0.7655,0.44718 z"
+                   id="path1467" /></g></g><g
+               id="g10067"
+               style="fill:#4d4d4d"
+               transform="matrix(1.6265445,0,0,1.8941561,167.95865,109.88188)"><path
+                 d="M 25,8.37 A 0.63,0.63 0 0 0 24.38,9 0.63,0.63 0 0 0 25.63,9 0.63,0.63 0 0 0 25,8.37 Z"
+                 id="path10061"
+                 style="fill:#4d4d4d" /><path
+                 d="M 27,8.37 A 0.63,0.63 0 0 0 26.38,9 0.63,0.63 0 0 0 27.63,9 0.63,0.63 0 0 0 27,8.37 Z"
+                 id="path10063"
+                 style="fill:#4d4d4d" /><path
+                 d="M 31,4.38 H 5 A 0.61,0.61 0 0 0 4.38,5 V 31 A 0.61,0.61 0 0 0 5,31.62 H 31 A 0.61,0.61 0 0 0 31.62,31 V 5 A 0.61,0.61 0 0 0 31,4.38 Z m -0.62,26 H 5.62 V 5.62 h 24.76 z"
+                 id="path10065"
+                 style="fill:#4d4d4d" /></g></g></g><path
           style="fill:none;stroke:#4d4d4d;stroke-width:1.05833;stroke-linecap:butt;stroke-linejoin:miter;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#RoundedArrow)"
           d="m 180.75356,107.25614 c 0.92352,153.38601 1.30815,153.66466 1.30815,153.66466 l 130.02933,0.22295"
-           id="path10481" /></g><path
-         style="fill:none;stroke:#4d4d4d;stroke-width:1.05833;stroke-linecap:butt;stroke-linejoin:miter;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker10543)"
-         d="m 181.19235,147.58012 25.60095,-0.16364"
-         id="path10539" /><path
-         style="fill:none;stroke:#4d4d4d;stroke-width:1.05833;stroke-linecap:butt;stroke-linejoin:miter;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker10543)"
-         d="m 181.8194,203.74287 76.63107,-0.11344"
-         id="path10589" /></g></g></svg>
+           id="path10481" /></g></g><path
+       style="fill:none;stroke:#4d4d4d;stroke-width:1.05833;stroke-linecap:butt;stroke-linejoin:miter;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker10543)"
+       d="m 169.02152,147.58012 25.60095,-0.16364"
+       id="path10539" /><path
+       style="fill:none;stroke:#4d4d4d;stroke-width:1.05833;stroke-linecap:butt;stroke-linejoin:miter;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker10543)"
+       d="m 169.64857,203.74287 76.63107,-0.11344"
+       id="path10589" /></g></svg>
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/404.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/404.po
@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Ansible devel\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-02-23 10:50+0100\n"
+"POT-Creation-Date: 2022-04-14 14:48+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@ -24,6 +24,9 @@ msgstr "Oops!"
 msgid "The version of the Ansible documentation you were looking at doesn't contain that page."
 msgstr "参照している Ansible ドキュメントのバージョンには、そのページが含まれていません。"

+msgid "Cowsay 404"
+msgstr "Cowsay 404"
+
 #: ../../rst/404.rst:12
 msgid "Use the back button to return to the version you were browsing, or use the navigation at left to explore our latest release. Once you're on a non-404 page, you can use the version-changer to select a version."
 msgstr "戻るボタンを使用して閲覧していたバージョンに戻るか、左側のナビゲーションを使用して最新リリースを参照してください。404 以外のページでは、バージョン番号変更メニューを使用してバージョンを選択できます。"
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/cli.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/cli.po
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/community.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/community.po
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/dev_guide.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/dev_guide.po
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/galaxy.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/galaxy.po
@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Ansible devel\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-03-08 20:25+0100\n"
+"POT-Creation-Date: 2022-06-27 15:07+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@ -49,7 +49,7 @@ msgid "The above will create the following directory structure in the current wo
 msgstr "上記により、現在の作業ディレクトリーに以下のディレクトリー構造が作成されます。"

 #: ../../rst/galaxy/dev_guide.rst:57
-msgid "If you want to create a repository for the role the repository root should be `role_name`."
+msgid "If you want to create a repository for the role, the repository root should be `role_name`."
 msgstr "ロールのリポジトリーを作成する場合、リポジトリーのルートは `role_name` である必要があります。"

 #: ../../rst/galaxy/dev_guide.rst:60
@ -220,15 +220,15 @@ msgstr "``--remove`` オプションを使用して、Travis 統合を無効化
 msgid "Provide the ID of the integration to be disabled. You can find the ID by using the ``--list`` option."
 msgstr "無効にする統合の ID を指定します。``--list`` オプションを使用して ID を検索できます。"

-#: ../../rst/galaxy/dev_guide.rst:239 ../../rst/galaxy/user_guide.rst:486
+#: ../../rst/galaxy/dev_guide.rst:239 ../../rst/galaxy/user_guide.rst:491
 msgid ":ref:`collections`"
 msgstr ":ref:`collections`"

-#: ../../rst/galaxy/dev_guide.rst:240 ../../rst/galaxy/user_guide.rst:487
+#: ../../rst/galaxy/dev_guide.rst:240 ../../rst/galaxy/user_guide.rst:492
 msgid "Shareable collections of modules, playbooks and roles"
 msgstr "モジュール、Playbook、およびロールの共有可能なコレクション"

-#: ../../rst/galaxy/dev_guide.rst:241 ../../rst/galaxy/user_guide.rst:488
+#: ../../rst/galaxy/dev_guide.rst:241 ../../rst/galaxy/user_guide.rst:493
 msgid ":ref:`playbooks_reuse_roles`"
 msgstr ":ref:`playbooks_reuse_roles`"

@ -245,12 +245,12 @@ msgid "Questions? Help? Ideas?  Stop by the list on Google Groups"
 msgstr "ご質問はございますか。サポートが必要ですか。ご提案はございますか。Google グループの一覧をご覧ください。"

 #: ../../rst/galaxy/dev_guide.rst:245
-msgid "`irc.freenode.net <http://irc.freenode.net>`_"
-msgstr "`irc.freenode.net <http://irc.freenode.net>`_"
+msgid ":ref:`communication_irc`"
+msgstr ":ref:`communication_irc`"

 #: ../../rst/galaxy/dev_guide.rst:246
-msgid "#ansible IRC chat channel"
-msgstr "IRC チャットチャンネル (#ansible)"
+msgid "How to join Ansible chat channels"
+msgstr "Ansible チャットチャンネルへの参加方法"

 #: ../../rst/galaxy/user_guide.rst:6
 msgid "Galaxy User Guide"
@ -302,7 +302,7 @@ msgstr "デフォルトでは、``ansible-galaxy collection install`` は https:

 #: ../../rst/shared_snippets/installing_collections.txt:7
 msgid "See :ref:`Configuring the ansible-galaxy client <galaxy_server_config>` if you are using any other Galaxy server, such as Red Hat Automation Hub."
-msgstr "Red Hat Automation Hub などの他の Galaxy サーバーを使用している場合は、「:ref:`Configuring the ansible-galaxy client <galaxy_server_config>`」を参照してください。"
+msgstr "Red Hat Automation Hub などの他の Galaxy サーバーを使用している場合は、「:ref:`ansible-galaxy クライアントの設定 <galaxy_server_config>`」を参照してください。"

 #: ../../rst/shared_snippets/installing_collections.txt:9
 msgid "To install a collection hosted in Galaxy:"
@ -326,11 +326,11 @@ msgstr "名前空間ディレクトリーに複数のコレクションをイン

 #: ../../rst/shared_snippets/installing_collections.txt:51
 msgid "The install command automatically appends the path ``ansible_collections`` to the one specified  with the ``-p`` option unless the parent directory is already in a folder called ``ansible_collections``."
-msgstr "install コマンドは、親ディレクトリーが ``ansible_collections`` ディレクトリーに含まれている場合を除き、``-p`` オプションで指定したパスに、パス ``ansible_collections`` を自動的に追加します。"
+msgstr "install コマンドは、親ディレクトリーが ``ansible_collections`` ディレクトリーに含まれている場合を除き、``-p`` オプションで指定したものに、パス ``ansible_collections`` を自動的に追加します。"

 #: ../../rst/shared_snippets/installing_collections.txt:55
 msgid "When using the ``-p`` option to specify the install path, use one of the values configured in :ref:`COLLECTIONS_PATHS`, as this is where Ansible itself will expect to find collections. If you don't specify a path, ``ansible-galaxy collection install`` installs the collection to the first path defined in :ref:`COLLECTIONS_PATHS`, which by default is ``~/.ansible/collections``"
-msgstr "``-p`` オプションを使用してインストールパスを指定する場合は、Ansible 自体がコレクションを見つけることが予想される場所であるため、:ref:`COLLECTIONS_PATHS` に設定された値のいずれかを使用します。パスを指定しないと、``ansible-galaxy collection install`` は :ref:`COLLECTIONS_PATHS` で定義されている最初のパスにコレクションをインストールします。これは、デフォルトでは ``~/.ansible/collections`` です。"
+msgstr "``-p`` オプションを使用してインストールパスを指定する場合は、Ansible 自体がコレクションを見つけることが予想される場所であるため、:ref:`COLLECTIONS_PATHS` に設定された値のいずれかを使用します。パスを指定しないと、``ansible-galaxy collection install`` は、:ref:`COLLECTIONS_PATHS` で定義されている最初のパスにコレクションをインストールします。これは、デフォルトでは ``~/.ansible/collections`` です。"

 #: ../../rst/shared_snippets/installing_collections.txt:59
 msgid "You can also keep a collection adjacent to the current playbook, under a ``collections/ansible_collections/`` directory structure."
@ -340,6 +340,38 @@ msgstr "また、``collections/ansible_collections/`` ディレクトリー構
 msgid "See :ref:`collection_structure` for details on the collection directory structure."
 msgstr "コレクションディレクトリー構造の詳細は、「:ref:`collection_structure`」を参照してください。"

+#: ../../rst/shared_snippets/installing_collections.txt:73
+msgid "Collections signed by a Galaxy server can be verified during installation with GnuPG. To opt into signature verification, configure a keyring for ``ansible-galaxy`` with native GnuPG tooling and provide the file path with the ``--keyring`` CLI option or ref:`GALAXY_GPG_KEYRING`. Signatures provided by the Galaxy server will be used to verify the collection's ``MANIFEST.json``."
+msgstr "Galaxy サーバーによって署名されたコレクションは、GnuPG を使用したインストール時に検証できます。署名の検証を選択するには、ネイティブの GnuPG ツールで ``ansible-galaxy`` のキーリングを設定し、``--keyring`` CLI オプションまたは ref:`GALAXY_GPG_KEYRING` でファイルパスを指定します。Galaxy サーバーによって提供される署名は、コレクションの ``MANIFEST.json`` を検証するために使用されます。"
+
+#: ../../rst/shared_snippets/installing_collections.txt:75
+msgid "Use the ``--signature`` option to verify the collection's ``MANIFEST.json`` with additional signatures to those provided by the Galaxy server. Supplemental signatures should be provided as URIs."
+msgstr "``--signature`` オプションを使用して、Galaxy サーバーが提供する追加の署名と共にコレクションの ``MANIFEST.json`` を検証します。追加の署名は URI として指定する必要があります。"
+
+#: ../../rst/shared_snippets/installing_collections.txt:81
+msgid "GnuPG verification only occurs for collections installed from a Galaxy server. User-provided signatures are not used to verify collections installed from git repositories, source directories, or URLs/paths to tar.gz files."
+msgstr "GnuPG 検証は、Galaxy サーバーからインストールされたコレクションでのみ発生します。ユーザーが提供した署名は、git リポジトリー、ソースディレクトリー、または URL/tar.gzファイルへのパスからインストールされたコレクションの検証には使用されません。"
+
+#: ../../rst/shared_snippets/installing_collections.txt:83
+msgid "By default, verification is considered successful if a minimum of 1 signature successfully verifies the collection. The number of required signatures can be configured with ``--required-valid-signature-count`` or :ref:`GALAXY_REQUIRED_VALID_SIGNATURE_COUNT`. All signatures can be required by setting the option to ``all``. To fail signature verification if no valid signatures are found, prepend the value with ``+``, such as ``+all`` or ``+1``."
+msgstr "デフォルトでは、1 つ以上の署名がコレクションを正常に検証した場合に、検証が成功したとみなされます。必要な署名の数は、``--required-valid-signature-count`` または :ref:`GALAXY_REQUIRED_VALID_SIGNATURE_COUNT` で設定できます。オプションを ``all`` に設定して、すべての署名を要求できます。有効な署名が見つからない場合に、署名の検証に失敗するには、``+all`` や ``+1`` のように値の前に ``+`` を追加します。"
+
+#: ../../rst/shared_snippets/installing_collections.txt:91
+msgid "Certain GnuPG errors can be ignored with ``--ignore-signature-status-code`` or :ref:`GALAXY_REQUIRED_VALID_SIGNATURE_COUNT`. :ref:`GALAXY_REQUIRED_VALID_SIGNATURE_COUNT` should be a list, and ``--ignore-signature-status-code`` can be provided multiple times to ignore multiple additional error status codes."
+msgstr "特定の GnuPG エラーは ``--ignore-signature-status-code`` または :ref:`GALAXY_REQUIRED_VALID_SIGNATURE_COUNT` により無視できます。:ref:`GALAXY_REQUIRED_VALID_SIGNATURE_COUNT` は一覧である必要があり、``--ignore-signature-status-code`` を複数回指定して複数の追加エラーステータスコードを無視することができます。"
+
+#: ../../rst/shared_snippets/installing_collections.txt:93
+msgid "This example requires any signatures provided by the Galaxy server to verify the collection except if they fail due to NO_PUBKEY:"
+msgstr "NO_PUBKEY が原因で失敗しない限り、この例では、コレクションを検証するために Galaxy サーバーが提供する署名が必要です。"
+
+#: ../../rst/shared_snippets/installing_collections.txt:101
+msgid "If verification fails for the example above, only errors other than NO_PUBKEY will be displayed."
+msgstr "上記の例で検証に失敗すると、NO_PUBKEY 以外のエラーのみが表示されます。"
+
+#: ../../rst/shared_snippets/installing_collections.txt:103
+msgid "If verification is unsuccessful, the collection will not be installed. GnuPG signature verification can be disabled with ``--disable-gpg-verify`` or by configuring :ref:`GALAXY_DISABLE_GPG_VERIFY`."
+msgstr "検証に失敗した場合は、コレクションはインストールされません。GnuPG の署名検証は ``--disable-gpg-verify`` で、あるいは :ref:`GALAXY_DISABLE_GPG_VERIFY` を設定して無効にすることができます。"
+
 #: ../../rst/galaxy/user_guide.rst:44
 msgid "Downloading a collection from Automation Hub"
 msgstr "Automation Hub からのコレクションのダウンロード"
@ -349,8 +381,8 @@ msgid "You can download collections from Automation Hub at the command line. Aut
 msgstr "コマンドラインで Automation Hub からコレクションをダウンロードできます。Automation Hub コンテンツは、サブスクライバーのみで利用できるため、コレクションをダウンロードする前に API トークンをダウンロードし、ローカル環境を設定して提供する必要があります。``ansible-galaxy`` コマンドを使用して Automation Hub からコレクションをダウンロードするには、以下を実行します。"

 #: ../../rst/galaxy/user_guide.rst:48
-msgid "Get your Automation Hub API token. Go to https://cloud.redhat.com/ansible/automation-hub/token/ and click :guilabel:`Get API token` from the version dropdown to copy your API token."
-msgstr "Automation Hub API トークンを取得します。https://cloud.redhat.com/ansible/automation-hub/token/ に移動し、バージョンドロップダウンの :guilabel:`Get API token` をクリックして API トークンをコピーします。"
+msgid "Get your Automation Hub API token. Go to https://cloud.redhat.com/ansible/automation-hub/token/ and click :guilabel:`Load token` from the version dropdown to copy your API token."
+msgstr "Automation Hub API トークンを取得します。https://cloud.redhat.com/ansible/automation-hub/token/ に移動し、バージョンドロップダウンの :guilabel:`Load token` をクリックして API トークンをコピーします。"

 #: ../../rst/galaxy/user_guide.rst:49
 msgid "Configure Red Hat Automation Hub server in the ``server_list``  option under the ``[galaxy]`` section in your :file:`ansible.cfg` file."
@ -421,36 +453,68 @@ msgid "Install multiple collections with a requirements file"
 msgstr "要件ファイルを使用した複数のコレクションのインストール"

 #: ../../rst/shared_snippets/installing_multiple_collections.txt:2
-msgid "You can also setup a ``requirements.yml`` file to install multiple collections in one command. This file is a YAML file in the format:"
-msgstr "``requirements.yml`` ファイルを設定して、1 つのコマンドで複数のコレクションをインストールすることもできます。このファイルは、以下の形式の YAML ファイルです。"
+msgid "You can set up a ``requirements.yml`` file to install multiple collections in one command. This file is a YAML file in the format:"
+msgstr "``requirements.yml`` ファイルを設定して、1 つのコマンドで複数のコレクションをインストールできます。このファイルは、以下の形式の YAML ファイルです。"

 #: ../../rst/shared_snippets/installing_multiple_collections.txt:16
-msgid "The supported keys for collection requirement entries are ``name``, ``version``, ``source``, and ``type``."
-msgstr "コレクション要件エントリーでサポートされるキーは ``name``、``version``、``source``、および ``type`` です。"
+msgid "You can specify the following keys for each collection entry:"
+msgstr "各コレクションエントリーに以下のキーを指定できます。"

 #: ../../rst/shared_snippets/installing_multiple_collections.txt:18
-msgid "The ``version`` key can take in the same range identifier format documented above. If you're installing a collection from a git repository instead of a built collection artifact, the ``version`` key refers to a `git commit-ish <https://git-scm.com/docs/gitglossary#def_commit-ish>`_."
-msgstr "``version`` キーは、上記の範囲識別子の形式を取ることができます。ビルドコレクションアーティファクトではなく git リポジトリーからコレクションをインストールする場合は、``version`` キーは `git commit-ish <https://git-scm.com/docs/gitglossary#def_commit-ish>`_ を参照します。"
+msgid "``name``"
+msgstr "``name``"
+
+#: ../../rst/shared_snippets/installing_multiple_collections.txt:19
+msgid "``version``"
+msgstr "``version``"

 #: ../../rst/shared_snippets/installing_multiple_collections.txt:20
-msgid "The ``type`` key can be set to ``galaxy``, ``url``, ``file``, and ``git``. If ``type`` is omitted, the ``name`` key is used to implicitly determine the source of the collection."
-msgstr "``type`` キーは ``galaxy``、``url``、``file``、および ``git`` に設定できます。``type`` を省略すると、``name`` キーを使用してコレクションのソースを暗黙的に決定します。"
+msgid "``signatures``"
+msgstr "``signatures``"
+
+#: ../../rst/shared_snippets/installing_multiple_collections.txt:21
+msgid "``source``"
+msgstr "``source``"

 #: ../../rst/shared_snippets/installing_multiple_collections.txt:22
-msgid "Roles can also be specified and placed under the ``roles`` key. The values follow the same format as a requirements file used in older Ansible releases."
-msgstr "ロールは、``roles`` キーの下に指定して配置することもできます。この値は、古い Ansible リリースで使用される要件ファイルと同じ形式に従います。"
+msgid "``type``"
+msgstr "``type``"

-#: ../../rst/shared_snippets/installing_multiple_collections.txt:39
+#: ../../rst/shared_snippets/installing_multiple_collections.txt:24
+msgid "The ``version`` key uses the same range identifier format documented in :ref:`collections_older_version`."
+msgstr "``version`` キーは、:ref:`collections_older_version` に記載されているものと同じ範囲識別子形式を使用します。"
+
+#: ../../rst/shared_snippets/installing_multiple_collections.txt:26
+msgid "The ``signatures`` key accepts a list of signature sources that are used to supplement those found on the Galaxy server during collection installation and ``ansible-galaxy collection verify``. Signature sources should be URIs that contain the detached signature. The ``--keyring`` CLI option must be provided if signatures are specified."
+msgstr "``signatures`` キーは、コレクションのインストール時および``ansible-galaxy collection verify``時に Galaxy サーバーで見つけられたものを補足するために使用される署名ソースの一覧を受け入れます。署名ソースは、デタッチされた署名が含まれる URI である必要があります。署名が指定されている場合は、``--keyring`` CLI オプションを指定する必要があります。"
+
+#: ../../rst/shared_snippets/installing_multiple_collections.txt:28
+msgid "Signatures are only used to verify collections on Galaxy servers. User-provided signatures are not used to verify collections installed from git repositories, source directories, or URLs/paths to tar.gz files."
+msgstr "署名は、Galaxy サーバーのコレクションを検証するためにのみ使用されます。ユーザーが提供した署名は、git リポジトリー、ソースディレクトリー、または URL/tar.gzファイルへのパスからインストールされたコレクションの検証には使用されません。"
+
+#: ../../rst/shared_snippets/installing_multiple_collections.txt:40
+msgid "The ``type`` key can be set to ``file``, ``galaxy``, ``git``, ``url``, ``dir``, or ``subdirs``. If ``type`` is omitted, the ``name`` key is used to implicitly determine the source of the collection."
+msgstr "``type`` キーは ``file``、``galaxy``、``git``、``url``、``dir``、または ``subdirs`` に設定できます。``type`` を省略すると、``name`` キーを使用してコレクションのソースを暗黙的に決定します。"
+
+#: ../../rst/shared_snippets/installing_multiple_collections.txt:42
+msgid "When you install a collection with ``type: git``, the ``version`` key can refer to a branch or to a `git commit-ish <https://git-scm.com/docs/gitglossary#def_commit-ish>`_ object (commit or tag). For example:"
+msgstr "``type: git`` でコレクションをインストールする場合、``version`` キーはブランチまたは `git commit-ish <https://git-scm.com/docs/gitglossary#def_commit-ish>`_ オブジェクト（コミットまたはタグ）を参照できます。以下に例を示します。"
+
+#: ../../rst/shared_snippets/installing_multiple_collections.txt:51
+msgid "You can also add roles to a ``requirements.yml`` file, under the ``roles`` key. The values follow the same format as a requirements file used in older Ansible releases."
+msgstr "``roles``キーの下にある``requirements.yml``ファイルにロールを追加することもできます。この値は、古い Ansible リリースで使用される要件ファイルと同じ形式に従います。"
+
+#: ../../rst/shared_snippets/installing_multiple_collections.txt:67
 msgid "To install both roles and collections at the same time with one command, run the following:"
 msgstr "1 つのコマンドで、ロールとコレクションを同時にインストールするには、以下のコマンドを実行します。"

-#: ../../rst/shared_snippets/installing_multiple_collections.txt:45
+#: ../../rst/shared_snippets/installing_multiple_collections.txt:73
 msgid "Running ``ansible-galaxy collection install -r`` or ``ansible-galaxy role install -r`` will only install collections, or roles respectively."
 msgstr "``ansible-galaxy collection install -r`` または ``ansible-galaxy role install -r`` を実行すると、それぞれコレクションまたはロールがインストールされます。"

-#: ../../rst/shared_snippets/installing_multiple_collections.txt:49
+#: ../../rst/shared_snippets/installing_multiple_collections.txt:76
 msgid "Installing both roles and collections from the same requirements file will not work when specifying a custom collection or role install path. In this scenario the collections will be skipped and the command will process each like ``ansible-galaxy role install`` would."
-msgstr "カスタムコレクションまたはロールインストールパスを指定する場合は、同じ要件ファイルからロールとコレクションの両方をインストールすることはできません。今回の例では、コレクションは省略され、コマンドは ``ansible-galaxy role install`` のように処理されます。"
+msgstr "カスタムコレクションまたはロールインストールパスを指定する場合、同じ要件ファイルからロールとコレクションの両方をインストールすることはできません。今回の例では、コレクションは省略され、コマンドは ``ansible-galaxy role install`` のように処理されます。"

 #: ../../rst/galaxy/user_guide.rst:82
 msgid "Downloading a collection for offline use"
@ -473,72 +537,124 @@ msgid "You may also need to manually download any dependent collections."
 msgstr "また、依存するコレクションを手動でダウンロードする必要がある場合があります。"

 #: ../../rst/galaxy/user_guide.rst:87
+msgid "Installing a collection from source files"
+msgstr "ソースファイルからのコレクションのインストール"
+
+#: ../../rst/shared_snippets/installing_collections_file.rst:1
+msgid "Ansible can also install from a source directory in several ways:"
+msgstr "Ansible は、複数の方法でソースディレクトリーからインストールすることもできます。"
+
+#: ../../rst/shared_snippets/installing_collections_file.rst:14
+msgid "Ansible can also install a collection collected with ``ansible-galaxy collection build`` or downloaded from Galaxy for offline use by specifying the output file directly:"
+msgstr "出力ファイルを直接指定して、Ansible は``ansible-galaxy collection build`` で収集したコレクションまたは Galaxy からダウンロードしたコレクションをオフライン用にインストールすることもできます。"
+
+#: ../../rst/shared_snippets/installing_collections_file.rst:24
+msgid "Relative paths are calculated from the current working directory (where you are invoking ``ansible-galaxy install -r`` from). They are not taken relative to the ``requirements.yml`` file."
+msgstr "相対パスは、現在の作業ディレクトリー（``ansible-galaxy install -r`` を呼び出しているディレクトリー）から計算されます。これは、``requirements.yml`` ファイルからの相対パスではありません。"
+
+#: ../../rst/galaxy/user_guide.rst:92
 msgid "Installing a collection from a git repository"
 msgstr "git リポジトリーからのコレクションのインストール"

 #: ../../rst/shared_snippets/installing_collections_git_repo.txt:1
-msgid "You can install a collection in a git repository by providing the URI to the repository instead of a collection name or path to a ``tar.gz`` file. The collection must contain a ``galaxy.yml`` or ``MANIFEST.json`` file, which will be used to generate the would-be collection artifact data from the directory. The URI should be prefixed with ``git+`` (or with ``git@`` to use a private repository with ssh authentication) and optionally supports a comma-separated `git commit-ish <https://git-scm.com/docs/gitglossary#def_commit-ish>`_ version (for example, a commit or tag)."
-msgstr "コレクション名または ``tar.gz`` ファイルへのパスではなく、リポジトリーに URI を提供することにより、git リポジトリーにコレクションをインストールできます。コレクションには、``galaxy.yml`` ファイルまたは ``MANIFEST.json`` ファイルが必要です。このコレクションは、ディレクトリーからの will-be コレクションアーティファクトデータを生成するのに使用されます。URI の接頭辞には ``git+`` (または ssh 認証でプライベートリポジトリーを使用する ``git@``）を付け、必要に応じてコンマ区切りの `git commit-ish <https://git-scm.com/docs/gitglossary#def_commit-ish>`_ バージョン (コミットまたはタグなど) をサポートする必要があります。"
+msgid "You can install a collection from a git repository instead of from Galaxy or Automation Hub. As a developer, installing from a git repository lets you review your collection before you create the tarball and publish the collection. As a user, installing from a git repository lets you use collections or versions that are not in Galaxy or Automation Hub yet."
+msgstr "コレクションは、Galaxy または Automation Hub の代わりに git リポジトリーからインストールできます。開発者は、git リポジトリーからインストールし、tarball を作成してコレクションを公開する前にコレクションを確認できます。ユーザーとして git リポジトリーからインストールすることで、Galaxy または Automation Hub にないコレクションまたはバージョンを使用できます。"

-#: ../../rst/shared_snippets/installing_collections_git_repo.txt:5
-msgid "Embedding credentials into a git URI is not secure. Make sure to use safe auth options for security reasons. For example, use `SSH <https://help.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh>`_, `netrc <https://linux.die.net/man/5/netrc>`_ or `http.extraHeader <https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpextraHeader>`_/`url.<base>.pushInsteadOf <https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtpushInsteadOf>`_ in Git config to prevent your creds from being exposed in logs."
-msgstr "認証情報を git URI に埋め込むことは安全ではありません。セキュリティー上の理由から、安全な認証オプションを使用してください。たとえば、Git 設定の `SSH <https://help.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh>`_、`netrc <https://linux.die.net/man/5/netrc>`_、または `http.extraHeader <https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpextraHeader>`_/`url.<base>.pushInsteadOf <https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtpushInsteadOf>`_ で、クレジットがログに公開されないようにします。"
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:3
+msgid "The repository must contain a ``galaxy.yml`` or ``MANIFEST.json`` file. This file provides metadata such as the version number and namespace of the collection."
+msgstr "リポジトリーには ``galaxy.yml`` または ``MANIFEST.json`` ファイルが含まれている必要があります。このファイルは、コレクションのバージョン番号、namespace などのメタデータを提供します。"

-#: ../../rst/shared_snippets/installing_collections_git_repo.txt:18
-msgid "In a ``requirements.yml`` file, you can also use the ``type`` and ``version`` keys in addition to using the ``git+repo,version`` syntax for the collection name."
-msgstr "``requirements.yml`` ファイルでは、コレクション名の ``git+repo,version`` 構文を使用する他に、``type`` キーおよび ``version`` キーを使用することもできます。"
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:6
+msgid "Installing a collection from a git repository at the command line"
+msgstr "コマンドガイドで git リポジトリーからのコレクションのインストール"
+
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:8
+msgid "To install a collection from a git repository at the command line, use the URI of the repository instead of a collection name or path to a ``tar.gz`` file. Use the prefix ``git+``, unless you're using SSH authentication with the user ``git`` (for example, ``git@github.com:ansible-collections/ansible.windows.git``). You can specify a branch, commit, or tag using the comma-separated `git commit-ish <https://git-scm.com/docs/gitglossary#def_commit-ish>`_ syntax."
+msgstr "git リポジトリーからコレクションをインストールするには、コレクション名または ``tar.gz`` ファイルへのパスではなく、リポジトリーの URI を使用します。ユーザー``git``でSSH認証を使用していない限り、プレフィックス``git+``を使用します(例: ``git@github.com:ansible-collections/ansible.windows.git``)。コンマ区切りの `git コミットのような <https://git-scm.com/docs/gitglossary#def_commit-ish>`_ 構文を使用して、ブランチ、コミット、またはタグを指定できます。"
+
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:10
+msgid "For example:"
+msgstr "例:"
+
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:25
+msgid "Embedding credentials into a git URI is not secure. Use safe authentication options to prevent your credentials from being exposed in logs or elsewhere."
+msgstr "認証情報を git URI に埋め込むことは安全ではありません。安全な認証オプションを使用して、認証情報がログに公開されないようにします。"

 #: ../../rst/shared_snippets/installing_collections_git_repo.txt:27
-msgid "Git repositories can be used for collection dependencies as well. This can be helpful for local development and testing but built/published artifacts should only have dependencies on other artifacts."
-msgstr "git リポジトリーはコレクションの依存関係にも使用できます。これは、ローカル開発およびテストに役立ちますが、ビルド/公開されたアーティファクトには他のアーティファクトへの依存関係のみが必要です。"
+msgid "Use `SSH <https://help.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh>`_ authentication"
+msgstr "`SSH <https://help.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh>`_ 認証を使用する"

-#: ../../rst/shared_snippets/installing_collections_git_repo.txt:34
-msgid "Default repository search locations"
-msgstr "デフォルトのリポジトリー検索の場所"
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:28
+msgid "Use `netrc <https://linux.die.net/man/5/netrc>`_ authentication"
+msgstr "`netrc <https://linux.die.net/man/5/netrc>`_ 認証を使用する"

-#: ../../rst/shared_snippets/installing_collections_git_repo.txt:36
-msgid "There are two paths searched in a repository for collections by default."
-msgstr "デフォルトでは、コレクション用のリポジトリーで 2 つのパスが検索されます。"
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:29
+msgid "Use `http.extraHeader <https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpextraHeader>`_ in your git configuration"
+msgstr "お使いの git 設定で `http.extraHeader <https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpextraHeader>`_ を使用する"
+
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:30
+msgid "Use `url.<base>.pushInsteadOf <https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtpushInsteadOf>`_ in your git configuration"
+msgstr "お使いの git 設定で `url.<base>.pushInsteadOf <https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtpushInsteadOf>`_ を使用する"
+
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:33
+msgid "Specifying the collection location within the git repository"
+msgstr "git リポジトリー内でのコレクションの場所の指定"
+
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:35
+msgid "When you install a collection from a git repository, Ansible uses the collection ``galaxy.yml`` or ``MANIFEST.json`` metadata file to build the collection. By default, Ansible searches two paths for collection ``galaxy.yml`` or ``MANIFEST.json`` metadata files:"
+msgstr "git リポジトリーからコレクションをインストールする場合、Ansible はコレクション ``galaxy.yml`` または ``MANIFEST.json`` メタデータファイルを使用してコレクションを構築します。デフォルトでは、Ansible はコレクション ``galaxy.yml`` または ``MANIFEST.json`` メタデータファイルの 2 つのパスを検索します。"
+
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:37
+msgid "The top level of the repository."
+msgstr "リポジトリーのトップレベル。"

 #: ../../rst/shared_snippets/installing_collections_git_repo.txt:38
-msgid "The first is the ``galaxy.yml`` or ``MANIFEST.json`` file in the top level of the repository path. If the file exists it's used as the collection metadata and the individual collection will be installed."
-msgstr "1 つ目は、リポジトリーパスの最上位にある ``galaxy.yml`` ファイルまたは ``MANIFEST.json`` ファイルです。ファイルが存在する場合は、コレクションのメタデータとして使用され、個々のコレクションがインストールされます。"
+msgid "Each directory in the repository path (one level deep)."
+msgstr "リポジトリーパス内の各ディレクトリー（1 レベルの深さ）"

-#: ../../rst/shared_snippets/installing_collections_git_repo.txt:49
-msgid "The second is a ``galaxy.yml`` or ``MANIFEST.json`` file in each directory in the repository path (one level deep). In this scenario, each directory with a metadata file is installed as a collection."
-msgstr "2 つ目は、リポジトリーパス (1 レベルの深さ) の各ディレクトリーの ``galaxy.yml`` ファイルまたは ``MANIFEST.json`` ファイルです。ここでは、メタデータファイルが含まれる各ディレクトリーがコレクションとしてインストールされます)。"
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:40
+msgid "If a ``galaxy.yml`` or ``MANIFEST.json`` file exists in the top level of the repository, Ansible uses the collection metadata in that file to install an individual collection."
+msgstr "``galaxy.yml`` または ``MANIFEST.json`` ファイルがリポジトリーのトップレベルにある場合、Ansible はそのファイル内のコレクションメタデータを使用して個別のコレクションをインストールします。"

-#: ../../rst/shared_snippets/installing_collections_git_repo.txt:62
-msgid "Specifying the location to search for collections"
-msgstr "コレクションを検索する場所の指定"
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:51
+msgid "If a ``galaxy.yml`` or ``MANIFEST.json`` file exists in one or more directories in the repository path (one level deep), Ansible installs each directory with a metadata file as a collection. For example, Ansible installs both collection1 and collection2 from this repository structure by default:"
+msgstr "リポジトリーパス内の 1 つ以上のディレクトリーに ``galaxy.yml`` または ``MANIFEST.json`` ファイルが存在する場合は、Ansible はメタデータファイルを持つ各ディレクトリーをコレクションとしてインストールします。たとえば、Ansible は、デフォルトで、このリポジトリー構造から collection1 と collection2 の両方をインストールします。"

-#: ../../rst/shared_snippets/installing_collections_git_repo.txt:64
-msgid "If you have a different repository structure or only want to install a subset of collections, you can add a fragment to the end of your URI (before the optional comma-separated version) to indicate which path ansible-galaxy should inspect for metadata file(s). The path should be a directory to a collection or multiple collections (rather than the path to a ``galaxy.yml`` file or ``MANIFEST.json`` file)."
-msgstr "異なるリポジトリー構造がある場合や、コレクションのサブセットのみをインストールする場合は、URI の最後にフラグメントを追加して (任意のコンマ区切りバージョンの前）、ansible-galaxy がメタデータファイルを調べるパスを示すことができます。パスは、(``MANIFEST.json`` ファイルまたは ``galaxy.yml`` ファイルへのパスではなく) コレクションまたは複数のコレクションへのディレクトリーである必要があります。"
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:69
+msgid "If you have a different repository structure or only want to install a subset of collections, you can add a fragment to the end of your URI (before the optional comma-separated version) to indicate the location of the metadata file or files. The path should be a directory, not the metadata file itself. For example, to install only collection2 from the example repository with two collections:"
+msgstr "リポジトリ構造が異なる場合、またはコレクションのサブセットのみをインストールする場合は、URI の末尾（オプションのコンマ区切りバージョンの前）にフラグメントを追加して、メタデータファイルの場所を示すことができます。パスは、メタデータファイル自体ではなく、ディレクトリである必要があります。たとえば、2つのコレクションを持つサンプルリポジトリからcollection2のみをインストールするには、次のようにします。"

-#: ../../rst/galaxy/user_guide.rst:92
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:75
+msgid "In some repositories, the main directory corresponds to the namespace:"
+msgstr "リポジトリーによっては、メインのディレクトリーは名前空間に対応します。"
+
+#: ../../rst/shared_snippets/installing_collections_git_repo.txt:97
+msgid "You can install all collections in this repository, or install one collection from a specific commit:"
+msgstr "このリポジトリーのすべてのコレクションをインストールするか、特定のコミットから 1 つのコレクションをインストールできます。"
+
+#: ../../rst/galaxy/user_guide.rst:97
 msgid "Listing installed collections"
 msgstr "インストール済みコレクションの一覧表示"

-#: ../../rst/galaxy/user_guide.rst:94
+#: ../../rst/galaxy/user_guide.rst:99
 msgid "To list installed collections, run ``ansible-galaxy collection list``. See :ref:`collections_listing` for more details."
 msgstr "インストール済みのコレクションを一覧表示するには、``ansible-galaxy collection list`` を実行します。詳細は、「:ref:`collections_listing`」を参照してください。"

-#: ../../rst/galaxy/user_guide.rst:98
+#: ../../rst/galaxy/user_guide.rst:103
 msgid "Configuring the ``ansible-galaxy`` client"
 msgstr "``ansible-galaxy`` クライアントの設定"

 #: ../../rst/shared_snippets/galaxy_server_list.txt:3
 msgid "By default, ``ansible-galaxy`` uses https://galaxy.ansible.com as the Galaxy server (as listed in the :file:`ansible.cfg` file under :ref:`galaxy_server`)."
-msgstr "デフォルトでは、``ansible-galaxy`` は https://galaxy.ansible.com を Galaxy サーバーとして使用します (:ref:`galaxy_server` の :file:`ansible.cfg` ファイルに記載）。"
+msgstr "デフォルトでは、``ansible-galaxy`` は https://galaxy.ansible.com を Galaxy サーバーとして使用します (:ref:`galaxy_server` の :file:`ansible.cfg` ファイルに記載)。"

 #: ../../rst/shared_snippets/galaxy_server_list.txt:5
-msgid "You can use either option below to configure ``ansible-galaxy collection`` to use other servers (such as Red Hat Automation Hub or a custom Galaxy server):"
-msgstr "以下のオプションを使用して、他のサーバー (Red Hat Automation Hub、カスタムの Galaxy サーバーなど) を使用するように ``ansible-galaxy collection`` を設定できます。"
+msgid "You can use either option below to configure ``ansible-galaxy collection`` to use other servers (such as a custom Galaxy server):"
+msgstr "以下のオプションを使用して、他のサーバー (カスタムの Galaxy サーバーなど) を使用するように ``ansible-galaxy collection`` を設定できます。"

 #: ../../rst/shared_snippets/galaxy_server_list.txt:7
 msgid "Set the server list in the :ref:`galaxy_server_list` configuration option in :ref:`ansible_configuration_settings_locations`."
-msgstr "「:ref:`ansible_configuration_settings_locations`」の「:ref:`galaxy_server_list`」設定オプションにサーバーリストを設定します。"
+msgstr ":ref:`ansible_configuration_settings_locations` の :ref:`galaxy_server_list` 設定オプションにサーバーリストを設定します。"

 #: ../../rst/shared_snippets/galaxy_server_list.txt:8
 msgid "Use the ``--server`` command line argument to limit to an individual server."
@ -568,355 +684,351 @@ msgstr "必要に応じて、各サーバー名の API トークンを設定し
 msgid "The ``url`` option for each server name must end with a forward slash ``/``. If you do not set the API token in your Galaxy server list, use the ``--api-key`` argument to pass in the token to  the ``ansible-galaxy collection publish`` command."
 msgstr "各サーバー名の ``url`` オプションは、スラッシュ ``/`` で終了する必要があります。Galaxy サーバー一覧の API トークンを設定しない場合は、``--api-key`` 引数を使用してトークンを ``ansible-galaxy collection publish`` コマンドに渡します。"

-#: ../../rst/shared_snippets/galaxy_server_list.txt:21
-msgid "For Automation Hub, you additionally need to:"
-msgstr "Automation Hub の場合には、さらに以下の操作が必要です。"
-
-#: ../../rst/shared_snippets/galaxy_server_list.txt:23
-msgid "Set the ``auth_url`` option for each server name."
-msgstr "各サーバー名に ``auth_url`` オプションを設定します。"
-
-#: ../../rst/shared_snippets/galaxy_server_list.txt:24
-msgid "Set the API token for each server name. Go to https://cloud.redhat.com/ansible/automation-hub/token/ and click ::guilabel:`Get API token` from the version dropdown to copy your API token."
-msgstr "各サーバー名の API トークンを設定します。https://cloud.redhat.com/ansible/automation-hub/token/ に、バージョンドロップダウンリストから ::guilabel:`Get API token` をクリックして API トークンをコピーします。"
-
-#: ../../rst/shared_snippets/galaxy_server_list.txt:26
+#: ../../rst/shared_snippets/galaxy_server_list.txt:22
 msgid "The following example shows how to configure multiple servers:"
 msgstr "以下の例は、複数のサーバーを設定する方法を示しています。"

-#: ../../rst/shared_snippets/galaxy_server_list.txt:52
+#: ../../rst/shared_snippets/galaxy_server_list.txt:49
 msgid "You can use the ``--server`` command line argument to select an explicit Galaxy server in the ``server_list`` and the value of this argument should match the name of the server. To use a server not in the server list, set the value to the URL to access that server (all servers in the server list will be ignored). Also you cannot use the ``--api-key`` argument for any of the predefined servers. You can only use the ``api_key`` argument if you did not define a server list or if you specify a URL in the ``--server`` argument."
 msgstr "``--server`` コマンドライン引数を使用して ``server_list`` で明示的な Galaxy サーバーを選択し、この引数の値はサーバー名と一致する必要があります。サーバー一覧にないサーバーを使用する場合は、そのサーバーにアクセスする URL に値を設定します (サーバーリスト内のすべてのサーバーは無視されます)。また、事前定義されたサーバーのいずれかに ``--api-key`` 引数を使用することはできません。サーバーの一覧を定義していない場合、または ``--server`` に URL を指定した場合限り、``api_key`` 引数を使用できます。"

-#: ../../rst/shared_snippets/galaxy_server_list.txt:56
+#: ../../rst/shared_snippets/galaxy_server_list.txt:53
 msgid "**Galaxy server list configuration options**"
 msgstr "**Galaxy サーバー一覧設定オプション**"

-#: ../../rst/shared_snippets/galaxy_server_list.txt:58
+#: ../../rst/shared_snippets/galaxy_server_list.txt:55
 msgid "The :ref:`galaxy_server_list` option is a list of server identifiers in a prioritized order. When searching for a collection, the install process will search in that order, for example, ``automation_hub`` first, then ``my_org_hub``, ``release_galaxy``, and finally ``test_galaxy`` until the collection is found. The actual Galaxy instance is then defined under the section ``[galaxy_server.{{ id }}]`` where ``{{ id }}`` is the server identifier defined in the list. This section can then define the following keys:"
-msgstr ":ref:`galaxy_server_list` オプションは、優先順位が付けられたサーバー識別子の一覧です。コレクションを検索する場合、インストールプロセスは次の順序で検索します。たとえば、``automation_hub`` を検索してから、``my_org_hub``、``release_galaxy``、最後に ``test_galaxy`` で、コレクションが見つかるまで行います。次に、実際の Galaxy インスタンスが ``[galaxy_server.{{ id }}]`` セクションで定義され。ここでは、``{{ id }}`` は、一覧で定義されているサーバー識別子です。このセクションでは、次のキーを定義できます。"
+msgstr ":ref:`galaxy_server_list` オプションは、優先順位が付けられたサーバー識別子の一覧です。コレクションを検索する場合、インストールプロセスは次の順序で検索します。たとえば、``automation_hub`` を検索してから、``my_org_hub``、``release_galaxy``、最後に ``test_galaxy`` で、コレクションが見つかるまで行います。次に、実際の Galaxy インスタンスが ``[galaxy_server.{{ id }}]`` セクションで定義されます。``{{ id }}`` は、一覧で定義されているサーバー識別子です。このセクションでは、次のキーを定義できます。"

-#: ../../rst/shared_snippets/galaxy_server_list.txt:64
+#: ../../rst/shared_snippets/galaxy_server_list.txt:61
 msgid "``url``: The URL of the Galaxy instance to connect to. Required."
 msgstr "``url``: 接続する Galaxy インスタンスの URL。必須。"

-#: ../../rst/shared_snippets/galaxy_server_list.txt:65
+#: ../../rst/shared_snippets/galaxy_server_list.txt:62
 msgid "``token``: An API token key to use for authentication against the Galaxy instance. Mutually exclusive with ``username``."
 msgstr "``token``: Galaxy インスタンスに対する認証に使用する API トークンキー。``username`` と相互に排他的です。"

-#: ../../rst/shared_snippets/galaxy_server_list.txt:66
+#: ../../rst/shared_snippets/galaxy_server_list.txt:63
 msgid "``username``: The username to use for basic authentication against the Galaxy instance. Mutually exclusive with ``token``."
 msgstr "``username``: Galaxy インスタンスに対する Basic 認証に使用するユーザー名。``token`` と相互に排他的です。"

-#: ../../rst/shared_snippets/galaxy_server_list.txt:67
+#: ../../rst/shared_snippets/galaxy_server_list.txt:64
 msgid "``password``: The password to use, in conjunction with ``username``, for basic authentication."
 msgstr "``password``: Basic 認証に使用するパスワード。``username`` と併用します。"

-#: ../../rst/shared_snippets/galaxy_server_list.txt:68
-msgid "``auth_url``: The URL of a Keycloak server 'token_endpoint' if using SSO authentication (for example, Automation Hub). Mutually exclusive with ``username``. Requires ``token``."
-msgstr "``auth_url``: SSO 認証 (例: Automation Hub) を使用する場合は Keycloak サーバー「token_endpoint」の URL です。``username`` と相互に排他的です。``token`` が必要です。"
+#: ../../rst/shared_snippets/galaxy_server_list.txt:65
+msgid "``auth_url``: The URL of a Keycloak server 'token_endpoint' if using SSO authentication (for example, galaxyNG). Mutually exclusive with ``username``. Requires ``token``."
+msgstr "``auth_url``: SSO 認証 (例: galaxyNG) を使用する場合は Keycloak サーバー「token_endpoint」の URL です。``username`` と相互に排他的です。``token`` が必要です。"

-#: ../../rst/shared_snippets/galaxy_server_list.txt:70
+#: ../../rst/shared_snippets/galaxy_server_list.txt:66
+msgid "``validate_certs``: Whether or not to verify TLS certificates for the Galaxy server. This defaults to True unless the ``--ignore-certs`` option is provided or ``GALAXY_IGNORE_CERTS`` is configured to True."
+msgstr "``validate_certs``: Galaxy サーバーの TLS 証明書を検証するかどうか。これは、``--ignore-certs`` オプションが提供されるか、``GALAXY_IGNORE_CERTS`` が True に設定されている場合を除き、デフォルトで True に設定されます。"
+
+#: ../../rst/shared_snippets/galaxy_server_list.txt:67
+msgid "``client_id``: The Keycloak token's client_id to use for authentication. Requires ``auth_url`` and ``token``. The default ``client_id`` is cloud-services to work with Red Hat SSO."
+msgstr "``client_id``: 認証に使用する Keycloak トークンの client_id。``auth_url`` および ``token`` が必要です。デフォルトの ``client_id`` は、Red Hat SSO と連携するクラウドサービスです。"
+
+#: ../../rst/shared_snippets/galaxy_server_list.txt:69
 msgid "As well as defining these server options in the ``ansible.cfg`` file, you can also define them as environment variables. The environment variable is in the form ``ANSIBLE_GALAXY_SERVER_{{ id }}_{{ key }}`` where ``{{ id }}`` is the upper case form of the server identifier and ``{{ key }}`` is the key to define. For example I can define ``token`` for ``release_galaxy`` by setting ``ANSIBLE_GALAXY_SERVER_RELEASE_GALAXY_TOKEN=secret_token``."
 msgstr "これらのサーバーオプションを ``ansible.cfg`` ファイルで定義するだけでなく、それらを環境変数として定義することもできます。環境変数は ``ANSIBLE_GALAXY_SERVER_{{ id }}_{{ key }}`` の形式です。``{{ id }}`` はサーバー識別子の大文字形式であり、``{{ key }}`` は定義するキーです。たとえば、``ANSIBLE_GALAXY_SERVER_RELEASE_GALAXY_TOKEN=secret_token`` を設定することで、``release_galaxy`` に ``token`` を定義することができます。"

-#: ../../rst/shared_snippets/galaxy_server_list.txt:75
+#: ../../rst/shared_snippets/galaxy_server_list.txt:74
 msgid "For operations that use only one Galaxy server (for example, the ``publish``, ``info``, or ``install`` commands). the ``ansible-galaxy collection`` command uses the first entry in the ``server_list``, unless you pass in an explicit server with the ``--server`` argument."
 msgstr "Galaxy サーバー 1 つだけを使用する操作 (例: ``publish`` コマンド、``info`` コマンド、または ``install`` コマンド) の場合、``ansible-galaxy collection`` コマンドは、``--server`` 引数を使用して明示的なサーバーに渡しない限り、``server_list`` の最初のエントリーを使用します。"

-#: ../../rst/shared_snippets/galaxy_server_list.txt:79
+#: ../../rst/shared_snippets/galaxy_server_list.txt:78
 msgid "Once a collection is found, any of its requirements are only searched within the same Galaxy instance as the parent collection. The install process will not search for a collection requirement in a different Galaxy instance."
 msgstr "コレクションが見つかると、その要件は親コレクションと同じ Galaxy インスタンス内でのみ検索されます。インストールプロセスでは、別の Galaxy インスタンスでコレクション要件を検索しません。"

-#: ../../rst/galaxy/user_guide.rst:105
+#: ../../rst/galaxy/user_guide.rst:110
 msgid "Finding roles on Galaxy"
 msgstr "Galaxy でのロールの検索"

-#: ../../rst/galaxy/user_guide.rst:107
+#: ../../rst/galaxy/user_guide.rst:112
 msgid "Search the Galaxy database by tags, platforms, author and multiple keywords. For example:"
 msgstr "Galaxy データベースは、タグ、プラットフォーム、作成者、および複数のキーワードで検索します。以下は例になります。"

-#: ../../rst/galaxy/user_guide.rst:113
+#: ../../rst/galaxy/user_guide.rst:118
 msgid "The search command will return a list of the first 1000 results matching your search:"
 msgstr "search コマンドは、検索に一致する最初の 1000 個の結果を一覧で返します。"

-#: ../../rst/galaxy/user_guide.rst:126
+#: ../../rst/galaxy/user_guide.rst:131
 msgid "Get more information about a role"
 msgstr "ロールに関する詳細情報の取得"

-#: ../../rst/galaxy/user_guide.rst:128
+#: ../../rst/galaxy/user_guide.rst:133
 msgid "Use the ``info`` command to view more detail about a specific role:"
 msgstr "``info`` コマンドを使用して、特定のロールに関する詳細を表示します。"

-#: ../../rst/galaxy/user_guide.rst:134
+#: ../../rst/galaxy/user_guide.rst:139
 msgid "This returns everything found in Galaxy for the role:"
 msgstr "これは、ロールの Galaxy にあるすべてのものを返します。"

-#: ../../rst/galaxy/user_guide.rst:171
+#: ../../rst/galaxy/user_guide.rst:176
 msgid "Installing roles from Galaxy"
 msgstr "Galaxy からのロールのインストール"

-#: ../../rst/galaxy/user_guide.rst:173
+#: ../../rst/galaxy/user_guide.rst:178
 msgid "The ``ansible-galaxy`` command comes bundled with Ansible, and you can use it to install roles from Galaxy or directly from a git based SCM. You can also use it to create a new role, remove roles, or perform tasks on the Galaxy website."
 msgstr "``ansible-galaxy`` コマンドは Ansible とバンドルされ、Galaxy から、または git ベースの SCM から直接ロールをインストールするために使用できます。また、新しいロールの作成、ロールの削除、または Galaxy の Web サイトでタスクを実行することもできます。"

-#: ../../rst/galaxy/user_guide.rst:176
+#: ../../rst/galaxy/user_guide.rst:181
 msgid "The command line tool by default communicates with the Galaxy website API using the server address *https://galaxy.ansible.com*. If you run your own internal Galaxy server and want to use it instead of the default one, pass the ``--server`` option following the address of this galaxy server. You can set permanently this option by setting the Galaxy server value in your ``ansible.cfg`` file to use it . For information on setting the value in *ansible.cfg* see :ref:`galaxy_server`."
 msgstr "コマンドラインツールは、デフォルトでサーバーアドレス *https://galaxy.ansible.com* を使用して Galaxy Web サイト API と通信します。独自の内部 Galaxy サーバーを実行していて、デフォルトのサーバーの代わりにそれを使用したい場合は、この galaxy サーバーのアドレスの後に ``--server`` オプションを渡します。``ansible.cfg`` ファイルに Galaxy サーバーの値を設定することにより、このオプションを永続的に設定できます。*ansible.cfg* での値の設定については、「:ref:`galaxy_server`」を参照してください。"

-#: ../../rst/galaxy/user_guide.rst:182
+#: ../../rst/galaxy/user_guide.rst:187
 msgid "Installing roles"
 msgstr "ロールのインストール"

-#: ../../rst/galaxy/user_guide.rst:184
+#: ../../rst/galaxy/user_guide.rst:189
 msgid "Use the ``ansible-galaxy`` command to download roles from the `Galaxy website <https://galaxy.ansible.com>`_"
 msgstr "``ansible-galaxy`` コマンドを使用して、`Galaxy website <https://galaxy.ansible.com>`_ からロールをダウンロードします。"

-#: ../../rst/galaxy/user_guide.rst:191
+#: ../../rst/galaxy/user_guide.rst:196
 msgid "Setting where to install roles"
 msgstr "ロールをインストールする場所の設定"

-#: ../../rst/galaxy/user_guide.rst:193
+#: ../../rst/galaxy/user_guide.rst:198
 msgid "By default, Ansible downloads roles to the first writable directory in the default list of paths ``~/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles``. This installs roles in the home directory of the user running ``ansible-galaxy``."
 msgstr "デフォルトでは、Ansible はパスのデフォルトリスト ``~/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles`` にある最初に書き込み可能なディレクトリーにロールをダウンロードします。これは、``ansible-galaxy`` を実行するユーザーのホームディレクトリーにロールをインストールします。"

-#: ../../rst/galaxy/user_guide.rst:195
+#: ../../rst/galaxy/user_guide.rst:200
 msgid "You can override this with one of the following options:"
 msgstr "これは、以下のオプションのいずれかで上書きできます。"

-#: ../../rst/galaxy/user_guide.rst:197
+#: ../../rst/galaxy/user_guide.rst:202
 msgid "Set the environment variable :envvar:`ANSIBLE_ROLES_PATH` in your session."
 msgstr "セッションで環境変数 :envvar:`ANSIBLE_ROLES_PATH` を設定します。"

-#: ../../rst/galaxy/user_guide.rst:198
+#: ../../rst/galaxy/user_guide.rst:203
 msgid "Use the ``--roles-path`` option for the ``ansible-galaxy`` command."
 msgstr "``--roles-path`` コマンドに ``ansible-galaxy`` オプションを使用します。"

-#: ../../rst/galaxy/user_guide.rst:199
+#: ../../rst/galaxy/user_guide.rst:204
 msgid "Define ``roles_path`` in an ``ansible.cfg`` file."
 msgstr "``ansible.cfg`` ファイルで ``roles_path`` を定義します。"

-#: ../../rst/galaxy/user_guide.rst:201
+#: ../../rst/galaxy/user_guide.rst:206
 msgid "The following provides an example of using ``--roles-path`` to install the role into the current working directory:"
 msgstr "以下は、``--roles-path`` を使用して現在の作業ディレクトリーにロールをインストールする例を示しています。"

-#: ../../rst/galaxy/user_guide.rst:209
+#: ../../rst/galaxy/user_guide.rst:214
 msgid ":ref:`intro_configuration`"
 msgstr ":ref:`intro_configuration`"

-#: ../../rst/galaxy/user_guide.rst:210
+#: ../../rst/galaxy/user_guide.rst:215
 msgid "All about configuration files"
 msgstr "設定ファイルに関するすべて"

-#: ../../rst/galaxy/user_guide.rst:213
+#: ../../rst/galaxy/user_guide.rst:218
 msgid "Installing a specific version of a role"
 msgstr "ロールの特定バージョンのインストール"

-#: ../../rst/galaxy/user_guide.rst:215
+#: ../../rst/galaxy/user_guide.rst:220
 msgid "When the Galaxy server imports a role, it imports any git tags matching the `Semantic Version <https://semver.org/>`_ format as versions. In turn, you can download a specific version of a role by specifying one of the imported tags."
 msgstr "Galaxy サーバーがロールをインポートすると、`Semantic Version <https://semver.org/>`_ 形式に一致する git タグがバージョンとしてインポートされます。次に、インポートされたタグのいずれかを指定して、ロールの特定バージョンをダウンロードできます。"

-#: ../../rst/galaxy/user_guide.rst:218
+#: ../../rst/galaxy/user_guide.rst:223
 msgid "To see the available versions for a role:"
 msgstr "ロールで利用可能なバージョンを表示するには、以下を行います。"

-#: ../../rst/galaxy/user_guide.rst:220
+#: ../../rst/galaxy/user_guide.rst:225
 msgid "Locate the role on the Galaxy search page."
 msgstr "Galaxy 検索ページでロールを見つけます。"

-#: ../../rst/galaxy/user_guide.rst:221
+#: ../../rst/galaxy/user_guide.rst:226
 msgid "Click on the name to view more details, including the available versions."
 msgstr "利用可能なバージョンなど、名前をクリックして詳細情報を表示します。"

-#: ../../rst/galaxy/user_guide.rst:223
+#: ../../rst/galaxy/user_guide.rst:228
 msgid "You can also navigate directly to the role using the /<namespace>/<role name>. For example, to view the role geerlingguy.apache, go to `<https://galaxy.ansible.com/geerlingguy/apache>`_."
 msgstr "/<namespace>/<role name> を使用してロールに直接移動することもできます。たとえば、geerlingguy.apache ロールを表示するには、`<https://galaxy.ansible.com/geerlingguy/apache>`_ に移動します。"

-#: ../../rst/galaxy/user_guide.rst:225
+#: ../../rst/galaxy/user_guide.rst:230
 msgid "To install a specific version of a role from Galaxy, append a comma and the value of a GitHub release tag. For example:"
 msgstr "Galaxy から特定のバージョンのロールをインストールするには、コンマと GitHub リリースタグの値を追加します。以下に例を示します。"

-#: ../../rst/galaxy/user_guide.rst:231
+#: ../../rst/galaxy/user_guide.rst:236
 msgid "It is also possible to point directly to the git repository and specify a branch name or commit hash as the version. For example, the following will install a specific commit:"
 msgstr "git リポジトリーを直接参照して、バージョンとしてブランチ名またはコミットハッシュを指定することもできます。たとえば、以下は特定のコミットをインストールします。"

-#: ../../rst/galaxy/user_guide.rst:239
+#: ../../rst/galaxy/user_guide.rst:244
 msgid "Installing multiple roles from a file"
 msgstr "ファイルからの複数ロールのインストール"

-#: ../../rst/galaxy/user_guide.rst:241
+#: ../../rst/galaxy/user_guide.rst:246
 msgid "You can install multiple roles by including the roles in a :file:`requirements.yml` file. The format of the file is YAML, and the file extension must be either *.yml* or *.yaml*."
 msgstr ":file:`requirements.yml` ファイルにロールを追加して、複数のロールをインストールできます。ファイルのフォーマットは YAML で、ファイル拡張子は *.yml* または *.yaml* のいずれかでなければなりません。"

-#: ../../rst/galaxy/user_guide.rst:244
+#: ../../rst/galaxy/user_guide.rst:249
 msgid "Use the following command to install roles included in :file:`requirements.yml:`"
 msgstr "以下のコマンドを使用して、:file:`requirements.yml:` に含まれるロールをインストールします。"

-#: ../../rst/galaxy/user_guide.rst:250
+#: ../../rst/galaxy/user_guide.rst:255
 msgid "Again, the extension is important. If the *.yml* extension is left off, the ``ansible-galaxy`` CLI assumes the file is in an older, now deprecated, \"basic\" format."
 msgstr "拡張子は重要です。*.yml* 拡張子がオフのままの場合、``ansible-galaxy`` CLI は、ファイルが古いものと見なし、「basic」フォーマットが非推奨であると想定します。"

-#: ../../rst/galaxy/user_guide.rst:253
+#: ../../rst/galaxy/user_guide.rst:258
 msgid "Each role in the file will have one or more of the following attributes:"
 msgstr "このファイルの各ロールには、以下の属性が 1 つ以上あります。"

-#: ../../rst/galaxy/user_guide.rst:256
+#: ../../rst/galaxy/user_guide.rst:261
 msgid "src"
 msgstr "src"

-#: ../../rst/galaxy/user_guide.rst:256
+#: ../../rst/galaxy/user_guide.rst:261
 msgid "The source of the role. Use the format *namespace.role_name*, if downloading from Galaxy; otherwise, provide a URL pointing to a repository within a git based SCM. See the examples below. This is a required attribute."
 msgstr "ロールのソース。Galaxy からダウンロードする場合は、*namespace.role_name* の形式を使用します。それ以外の場合は、git ベースの SCM 内のリポジトリーを参照する URL を提供します。以下を参照してください。これは必須属性です。"

-#: ../../rst/galaxy/user_guide.rst:258
+#: ../../rst/galaxy/user_guide.rst:263
 msgid "scm"
 msgstr "scm"

-#: ../../rst/galaxy/user_guide.rst:259
+#: ../../rst/galaxy/user_guide.rst:264
 msgid "Specify the SCM. As of this writing only *git* or *hg* are allowed. See the examples below. Defaults to *git*."
 msgstr "SCM を指定します。本書の作成時点では、*git* または *hg* への書き込みのみが許可されます。以下の例を参照してください。デフォルトは *git* です。"

-#: ../../rst/galaxy/user_guide.rst:260
+#: ../../rst/galaxy/user_guide.rst:265
 msgid "version:"
 msgstr "version:"

-#: ../../rst/galaxy/user_guide.rst:261
+#: ../../rst/galaxy/user_guide.rst:266
 msgid "The version of the role to download. Provide a release tag value, commit hash, or branch name. Defaults to the branch set as a default in the repository, otherwise defaults to the *master*."
 msgstr "ダウンロードするロールのバージョン。リリースタグの値、コミットハッシュ、またはブランチ名を指定します。デフォルトではリポジトリーのデフォルトとして設定されたブランチに設定されます。それ以外の場合は、デフォルトで *master* に設定されます。"

-#: ../../rst/galaxy/user_guide.rst:264
+#: ../../rst/galaxy/user_guide.rst:269
 msgid "name:"
 msgstr "name:"

-#: ../../rst/galaxy/user_guide.rst:263
+#: ../../rst/galaxy/user_guide.rst:268
 msgid "Download the role to a specific name. Defaults to the Galaxy name when downloading from Galaxy, otherwise it defaults to the name of the repository."
 msgstr "ロールを特定の名前にダウンロードします。デフォルトでは Galaxy からダウンロードするときに Galaxy 名に設定されます。指定しない場合は、リポジトリーの名前に設定されます。"

-#: ../../rst/galaxy/user_guide.rst:266
+#: ../../rst/galaxy/user_guide.rst:271
 msgid "Use the following example as a guide for specifying roles in *requirements.yml*:"
 msgstr "以下の例を、*requirements.yml* でロールを指定するためのガイドとして使用してください。"

-#: ../../rst/galaxy/user_guide.rst:315
+#: ../../rst/galaxy/user_guide.rst:320
 msgid "Embedding credentials into a SCM URL is not secure. Make sure to use safe auth options for security reasons. For example, use `SSH <https://help.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh>`_, `netrc <https://linux.die.net/man/5/netrc>`_ or `http.extraHeader <https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpextraHeader>`_/`url.<base>.pushInsteadOf <https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtpushInsteadOf>`_ in Git config to prevent your creds from being exposed in logs."
 msgstr "認証情報を SCM URL に埋め込むことは安全ではありません。セキュリティー上の理由から、安全な認証オプションを使用してください。たとえば、Git 設定の `SSH <https://help.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh>`_、`netrc <https://linux.die.net/man/5/netrc>`_、または `http.extraHeader <https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpextraHeader>`_/`url.<base>.pushInsteadOf <https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtpushInsteadOf>`_ で、クレジットがログに公開されないようにします。"

-#: ../../rst/galaxy/user_guide.rst:318
+#: ../../rst/galaxy/user_guide.rst:323
 msgid "Installing roles and collections from the same requirements.yml file"
 msgstr "同じ requirements.yml ファイルからのロールおよびコレクションのインストール"

-#: ../../rst/galaxy/user_guide.rst:320
+#: ../../rst/galaxy/user_guide.rst:325
 msgid "You can install roles and collections from the same requirements files"
 msgstr "同じ要件ファイルからロールおよびコレクションをインストールできます。"

-#: ../../rst/galaxy/user_guide.rst:337
+#: ../../rst/galaxy/user_guide.rst:342
 msgid "Installing multiple roles from multiple files"
 msgstr "複数のファイルからの複数ロールのインストール"

-#: ../../rst/galaxy/user_guide.rst:339
+#: ../../rst/galaxy/user_guide.rst:344
 msgid "For large projects, the ``include`` directive in a :file:`requirements.yml` file provides the ability to split a large file into multiple smaller files."
 msgstr "大規模なプロジェクトの場合、:file:`requirements.yml` ファイルの ``include`` ディレクティブにより、大きなファイルを複数の小さなファイルに分割することができます。"

-#: ../../rst/galaxy/user_guide.rst:341
+#: ../../rst/galaxy/user_guide.rst:346
 msgid "For example, a project may have a :file:`requirements.yml` file, and a :file:`webserver.yml` file."
 msgstr "たとえば、プロジェクトには :file:`requirements.yml` ファイルと :file:`webserver.yml` ファイルが含まれる場合があります。"

-#: ../../rst/galaxy/user_guide.rst:343
+#: ../../rst/galaxy/user_guide.rst:348
 msgid "Below are the contents of the :file:`webserver.yml` file:"
 msgstr ":file:`webserver.yml` ファイルの内容を以下に示します。"

-#: ../../rst/galaxy/user_guide.rst:354
+#: ../../rst/galaxy/user_guide.rst:359
 msgid "The following shows the contents of the :file:`requirements.yml` file that now includes the :file:`webserver.yml` file:"
 msgstr ":file:`requirements.yml` ファイルが含まれる :file:`webserver.yml` ファイルの内容を以下に示します。"

-#: ../../rst/galaxy/user_guide.rst:362
+#: ../../rst/galaxy/user_guide.rst:367
 msgid "To install all the roles from both files, pass the root file, in this case :file:`requirements.yml` on the command line, as follows:"
 msgstr "両方のファイルからすべてのロールをインストールするには、以下のように root ファイルを渡します。この例では、以下のように、コマンドラインで :file:`requirements.yml` を指定します。"

-#: ../../rst/galaxy/user_guide.rst:372
+#: ../../rst/galaxy/user_guide.rst:377
 msgid "Dependencies"
 msgstr "依存関係"

-#: ../../rst/galaxy/user_guide.rst:374
+#: ../../rst/galaxy/user_guide.rst:379
 msgid "Roles can also be dependent on other roles, and when you install a role that has dependencies, those dependencies will automatically be installed to the ``roles_path``."
 msgstr "また、ロールは他のロールに依存し、依存関係のあるロールをインストールすると、それらの依存関係が自動的に ``roles_path`` にインストールされます。"

-#: ../../rst/galaxy/user_guide.rst:376
+#: ../../rst/galaxy/user_guide.rst:381
 msgid "There are two ways to define the dependencies of a role:"
 msgstr "ロールの依存関係を定義する方法は 2 つあります。"

-#: ../../rst/galaxy/user_guide.rst:378
+#: ../../rst/galaxy/user_guide.rst:383
 msgid "using ``meta/requirements.yml``"
 msgstr "``meta/requirements.yml`` の使用"

-#: ../../rst/galaxy/user_guide.rst:379
+#: ../../rst/galaxy/user_guide.rst:384
 msgid "using ``meta/main.yml``"
 msgstr "``meta/main.yml`` の使用"

-#: ../../rst/galaxy/user_guide.rst:382
+#: ../../rst/galaxy/user_guide.rst:387
 msgid "Using ``meta/requirements.yml``"
 msgstr "``meta/requirements.yml`` の使用"

-#: ../../rst/galaxy/user_guide.rst:386
+#: ../../rst/galaxy/user_guide.rst:391
 msgid "You can create the file ``meta/requirements.yml`` and define dependencies in the same format used for :file:`requirements.yml` described in the `Installing multiple roles from a file`_ section."
 msgstr "``meta/requirements.yml`` ファイルを作成し、「`ファイルから複数のロールのインストール`_」セクションで説明されている :file:`requirements.yml` に使用されるのと同じ形式で依存関係を定義できます。"

-#: ../../rst/galaxy/user_guide.rst:388
+#: ../../rst/galaxy/user_guide.rst:393
 msgid "From there, you can import or include the specified roles in your tasks."
 msgstr "そこから、指定のロールをタスクにインポートしたり、追加できます。"

-#: ../../rst/galaxy/user_guide.rst:391
+#: ../../rst/galaxy/user_guide.rst:396
 msgid "Using ``meta/main.yml``"
 msgstr "``meta/main.yml`` の使用"

-#: ../../rst/galaxy/user_guide.rst:393
+#: ../../rst/galaxy/user_guide.rst:398
 msgid "Alternatively, you can specify role dependencies in the ``meta/main.yml`` file by providing a list of roles under the ``dependencies`` section. If the source of a role is Galaxy, you can simply specify the role in the format ``namespace.role_name``. You can also use the more complex format in :file:`requirements.yml`, allowing you to provide ``src``, ``scm``, ``version``, and ``name``."
 msgstr "または、``dependencies`` セクションの下にロールの一覧を指定して、``meta/main.yml`` ファイルにロールの依存関係を指定できます。ロールのソースが Galaxy の場合には、``namespace.role_name`` 形式でロールを指定するだけです。さらに複雑な形式を :file:`requirements.yml` で使用することもできます。``src``、``scm``、``version``、および ``name`` を指定することもできます。"

-#: ../../rst/galaxy/user_guide.rst:396
+#: ../../rst/galaxy/user_guide.rst:401
 msgid "Dependencies installed that way, depending on other factors described below, will also be executed **before** this role is executed during play execution. To better understand how dependencies are handled during play execution, see :ref:`playbooks_reuse_roles`."
 msgstr "そのようにインストールされた依存関係は、以下で説明する他の要因に応じて、プレイの実行中にこのロールが実行される **前** にも実行されます。再生の実行中に依存関係がどのように処理されるかをよりよく理解するには、「:ref:`playbooks_reuse_roles`」を参照してください。"

-#: ../../rst/galaxy/user_guide.rst:399
+#: ../../rst/galaxy/user_guide.rst:404
 msgid "The following shows an example ``meta/main.yml`` file with dependent roles:"
 msgstr "依存するロールが指定された ``meta/main.yml`` ファイルの例を以下に示します。"

-#: ../../rst/galaxy/user_guide.rst:432
+#: ../../rst/galaxy/user_guide.rst:437
 msgid "Tags are inherited *down* the dependency chain. In order for tags to be applied to a role and all its dependencies, the tag should be applied to the role, not to all the tasks within a role."
 msgstr "タグは、依存関係チェーン *下* に継承されます。タグをロールに適用してすべての依存関係に適用するには、タグをロール内の全タスクに適用するのではなく、ロールに適用する必要があります。"

-#: ../../rst/galaxy/user_guide.rst:434
+#: ../../rst/galaxy/user_guide.rst:439
 msgid "Roles listed as dependencies are subject to conditionals and tag filtering, and may not execute fully depending on what tags and conditionals are applied."
 msgstr "依存関係として一覧表示されているロールは、条件とタグフィルタリングの対象であり、適用されるタグと条件によっては完全に実行されない場合があります。"

-#: ../../rst/galaxy/user_guide.rst:437
+#: ../../rst/galaxy/user_guide.rst:442
 msgid "If the source of a role is Galaxy, specify the role in the format *namespace.role_name*:"
 msgstr "ロールのソースが Galaxy の場合は、ロールを *namespace.role_name* 形式で指定します。"

-#: ../../rst/galaxy/user_guide.rst:446
+#: ../../rst/galaxy/user_guide.rst:451
 msgid "Alternately, you can specify the role dependencies in the complex form used in  :file:`requirements.yml` as follows:"
 msgstr "または、以下のように :file:`requirements.yml` で使用される複雑な形式でロールの依存関係を指定することもできます。"

-#: ../../rst/galaxy/user_guide.rst:458
+#: ../../rst/galaxy/user_guide.rst:463
 msgid "Galaxy expects all role dependencies to exist in Galaxy, and therefore dependencies to be specified in the ``namespace.role_name`` format. If you import a role with a dependency where the ``src`` value is a URL, the import process will fail."
 msgstr "Galaxy では、すべてのロールの依存関係が Galaxy に存在することが想定されるため、``namespace.role_name`` 形式で依存関係を指定します。``src`` の値が URL である依存関係でロールをインポートすると、インポートプロセスは失敗します。"

-#: ../../rst/galaxy/user_guide.rst:462
+#: ../../rst/galaxy/user_guide.rst:467
 msgid "List installed roles"
 msgstr "インストール済みロールの一覧表示"

-#: ../../rst/galaxy/user_guide.rst:464
+#: ../../rst/galaxy/user_guide.rst:469
 msgid "Use ``list`` to show the name and version of each role installed in the *roles_path*."
 msgstr "``list`` を使用して、*roles_path* にインストールされている各ロールの名前およびバージョンを表示します。"

-#: ../../rst/galaxy/user_guide.rst:476
+#: ../../rst/galaxy/user_guide.rst:481
 msgid "Remove an installed role"
 msgstr "インストールされたロールの削除"

-#: ../../rst/galaxy/user_guide.rst:478
+#: ../../rst/galaxy/user_guide.rst:483
 msgid "Use ``remove`` to delete a role from *roles_path*:"
 msgstr "``remove`` を使用して、*roles_path* からロールを削除します。"

-#: ../../rst/galaxy/user_guide.rst:489
+#: ../../rst/galaxy/user_guide.rst:494
 msgid "Reusable tasks, handlers, and other files in a known directory structure"
 msgstr "既知のディレクトリー構造の再利用可能なタスク、ハンドラー、およびその他のファイル"

@ -941,3 +1053,48 @@ msgstr "既知のディレクトリー構造の再利用可能なタスク、ハ
 #~ msgid "`.. versionadded:: 2.10`"
 #~ msgstr ""

+#~ msgid "`irc.freenode.net <http://irc.freenode.net>`_"
+#~ msgstr "`irc.freenode.net <http://irc.freenode.net>`_"
+
+#~ msgid "The supported keys for collection requirement entries are ``name``, ``version``, ``source``, and ``type``."
+#~ msgstr "コレクション要件エントリーでサポートされるキーは ``name``、``version``、``source``、および ``type`` です。"
+
+#~ msgid "The ``version`` key can take in the same range identifier format documented above. If you're installing a collection from a git repository instead of a built collection artifact, the ``version`` key refers to a `git commit-ish <https://git-scm.com/docs/gitglossary#def_commit-ish>`_."
+#~ msgstr "``version`` キーは、上記の範囲識別子の形式を取ることができます。ビルドコレクションアーティファクトではなく git リポジトリーからコレクションをインストールする場合は、``version`` キーは `git commit-ish <https://git-scm.com/docs/gitglossary#def_commit-ish>`_ を参照します。"
+
+#~ msgid "You can install a collection in a git repository by providing the URI to the repository instead of a collection name or path to a ``tar.gz`` file. The collection must contain a ``galaxy.yml`` or ``MANIFEST.json`` file, which will be used to generate the would-be collection artifact data from the directory. The URI should be prefixed with ``git+`` (or with ``git@`` to use a private repository with ssh authentication) and optionally supports a comma-separated `git commit-ish <https://git-scm.com/docs/gitglossary#def_commit-ish>`_ version (for example, a commit or tag)."
+#~ msgstr "コレクション名または ``tar.gz`` ファイルへのパスではなく、リポジトリーに URI を提供することにより、git リポジトリーにコレクションをインストールできます。コレクションには、``galaxy.yml`` ファイルまたは ``MANIFEST.json`` ファイルが必要です。このコレクションは、ディレクトリーからの will-be コレクションアーティファクトデータを生成するのに使用されます。URI の接頭辞には ``git+`` (または ssh 認証でプライベートリポジトリーを使用する ``git@``）を付け、必要に応じてコンマ区切りの `git commit-ish <https://git-scm.com/docs/gitglossary#def_commit-ish>`_ バージョン (コミットまたはタグなど) をサポートする必要があります。"
+
+#~ msgid "Embedding credentials into a git URI is not secure. Make sure to use safe auth options for security reasons. For example, use `SSH <https://help.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh>`_, `netrc <https://linux.die.net/man/5/netrc>`_ or `http.extraHeader <https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpextraHeader>`_/`url.<base>.pushInsteadOf <https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtpushInsteadOf>`_ in Git config to prevent your creds from being exposed in logs."
+#~ msgstr "認証情報を git URI に埋め込むことは安全ではありません。セキュリティー上の理由から、安全な認証オプションを使用してください。たとえば、Git 設定の `SSH <https://help.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh>`_、`netrc <https://linux.die.net/man/5/netrc>`_、または `http.extraHeader <https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpextraHeader>`_/`url.<base>.pushInsteadOf <https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtpushInsteadOf>`_ で、クレジットがログに公開されないようにします。"
+
+#~ msgid "In a ``requirements.yml`` file, you can also use the ``type`` and ``version`` keys in addition to using the ``git+repo,version`` syntax for the collection name."
+#~ msgstr "``requirements.yml`` ファイルでは、コレクション名の ``git+repo,version`` 構文を使用する他に、``type`` キーおよび ``version`` キーを使用することもできます。"
+
+#~ msgid "Git repositories can be used for collection dependencies as well. This can be helpful for local development and testing but built/published artifacts should only have dependencies on other artifacts."
+#~ msgstr "git リポジトリーはコレクションの依存関係にも使用できます。これは、ローカル開発およびテストに役立ちますが、ビルド/公開されたアーティファクトには他のアーティファクトへの依存関係のみが必要です。"
+
+#~ msgid "Default repository search locations"
+#~ msgstr "デフォルトのリポジトリー検索の場所"
+
+#~ msgid "There are two paths searched in a repository for collections by default."
+#~ msgstr "デフォルトでは、コレクション用のリポジトリーで 2 つのパスが検索されます。"
+
+#~ msgid "The second is a ``galaxy.yml`` or ``MANIFEST.json`` file in each directory in the repository path (one level deep). In this scenario, each directory with a metadata file is installed as a collection."
+#~ msgstr "2 つ目は、リポジトリーパス (1 レベルの深さ) の各ディレクトリーの ``galaxy.yml`` ファイルまたは ``MANIFEST.json`` ファイルです。ここでは、メタデータファイルが含まれる各ディレクトリーがコレクションとしてインストールされます)。"
+
+#~ msgid "Specifying the location to search for collections"
+#~ msgstr "コレクションを検索する場所の指定"
+
+#~ msgid "If you have a different repository structure or only want to install a subset of collections, you can add a fragment to the end of your URI (before the optional comma-separated version) to indicate which path ansible-galaxy should inspect for metadata file(s). The path should be a directory to a collection or multiple collections (rather than the path to a ``galaxy.yml`` file or ``MANIFEST.json`` file)."
+#~ msgstr "異なるリポジトリー構造がある場合や、コレクションのサブセットのみをインストールする場合は、URI の最後にフラグメントを追加して (任意のコンマ区切りバージョンの前）、ansible-galaxy がメタデータファイルを調べるパスを示すことができます。パスは、(``MANIFEST.json`` ファイルまたは ``galaxy.yml`` ファイルへのパスではなく) コレクションまたは複数のコレクションへのディレクトリーである必要があります。"
+
+#~ msgid "For Automation Hub, you additionally need to:"
+#~ msgstr "Automation Hub の場合には、さらに以下の操作が必要です。"
+
+#~ msgid "Set the ``auth_url`` option for each server name."
+#~ msgstr "各サーバー名に ``auth_url`` オプションを設定します。"
+
+#~ msgid "Set the API token for each server name. Go to https://cloud.redhat.com/ansible/automation-hub/token/ and click ::guilabel:`Get API token` from the version dropdown to copy your API token."
+#~ msgstr "各サーバー名の API トークンを設定します。https://cloud.redhat.com/ansible/automation-hub/token/ に、バージョンドロップダウンリストから ::guilabel:`Get API token` をクリックして API トークンをコピーします。"
+
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/getting_started.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/getting_started.po
@ -0,0 +1,383 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) Ansible project contributors
+# This file is distributed under the same license as the Ansible package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2022.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Ansible devel\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-06-27 15:07+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.9.0\n"
+
+#: ../../rst/getting_started/get_started_inventory.rst:5
+msgid "Building an inventory"
+msgstr "インベントリーのビルド"
+
+#: ../../rst/getting_started/get_started_inventory.rst:7
+msgid "Inventories organize managed nodes in centralized files that provide Ansible with system information and network locations. Using an inventory file, Ansible can manage a large number of hosts with a single command. Inventories also help you use Ansible more efficiently by reducing the number of command-line options you need to specify. For example, inventories usually contain the SSH user so you do not need to include the ``-u`` flag when running Ansible commands."
+msgstr "インベントリーは、Ansible にシステム情報やネットワークの場所を提供する一元化されたファイルに管理対象ノードを整理します。インベントリーファイルを使用すると、Ansible は 1 つのコマンドで多数のホストを管理できます。インベントリーを使用すると、指定する必要のあるコマンドラインオプションの数が減少するため、Ansible をより効率的に使用できます。たとえば、通常インベントリーには SSH ユーザーが含まれるため、Ansible コマンドの実行時に ``-u`` フラグを含める必要はありません。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:12
+msgid "In the previous section, you added managed nodes directly to the ``/etc/ansible/hosts`` file. Now let's create an inventory file that you can add to source control for flexibility, reuse, and for sharing with other users."
+msgstr "前のセクションでは、管理対象ノードを ``/etc/ansible/hosts`` ファイルに直接追加しました。次は、柔軟性の向上、再利用、他のユーザーとの共有を可能にするため、ソース管理に追加できるインベントリーファイルを作成します。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:16
+msgid "Inventory files can be in ``INI`` or ``YAML`` format. For demonstration purposes this section uses ``YAML`` format only."
+msgstr "インベントリーファイルは ``INI`` または ``YAML`` 形式を使用できます。デモンストレーションとして、ここでは ``YAML`` 形式のみを使用します。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:19
+#: ../../rst/getting_started/get_started_playbook.rst:25
+msgid "Complete the following steps:"
+msgstr "以下の手順を実行します。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:21
+#: ../../rst/getting_started/get_started_playbook.rst:27
+msgid "Open a terminal window on your control node."
+msgstr "コントロールノードでターミナルウィンドウを開きます。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:22
+msgid "Create a new inventory file named ``inventory.yaml`` in any directory and open it for editing."
+msgstr "任意のディレクトリーに ``inventory.yaml`` という名前の新しいインベントリーファイルを作成し、そのファイルを開いて編集します。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:23
+msgid "Add a new group for your hosts then specify the IP address or fully qualified domain name (FQDN) of each managed node with the ``ansible_host`` field. The following example adds the IP addresses of three virtual machines in KVM:"
+msgstr "ホストの新規グループを追加してから、``ansible_host`` フィールドで各管理対象ノードの IP アドレスまたは完全修飾ドメイン名( FQDN) を指定します。以下の例では、KVM に 3 つの仮想マシンの IP アドレスを追加します。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:29
+msgid "Verify your inventory. If you created your inventory in a directory other than your home directory, specify the full path with the ``-i`` option."
+msgstr "インベントリーを検証します。ホームディレクトリー以外のディレクトリーにインベントリーを作成した場合は、``-i`` オプションで完全パスを指定します。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:36
+msgid "Ping the managed nodes in your inventory. In this example, the group name is ``virtualmachines`` which you can specify with the ``ansible`` command instead of ``all``."
+msgstr "インベントリーの管理ノードに ping します。この例では、グループ名は ``virtualmachines`` で、``all`` ではなく ``ansible`` コマンドで指定できます。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:46
+msgid "Congratulations! You have successfully built an inventory."
+msgstr "おめでとうございます。インベントリーのビルドに成功しました。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:49
+msgid "Tips for building inventories"
+msgstr "インベントリーのビルドに関するヒント"
+
+#: ../../rst/getting_started/get_started_inventory.rst:51
+msgid "Ensure that group names are meaningful and unique. Group names are also case sensitive."
+msgstr "グループ名が意味を持ち、一意であることを確認します。グループ名でも大文字と小文字が区別されます。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:52
+msgid "Avoid spaces, hyphens, and preceding numbers (use ``floor_19``, not ``19th_floor``) in group names."
+msgstr "グループ名で、スペース、ハイフン、先行する数字 (``19th_floor``ではなく ``floor_19`` を使用) は使用しないでください。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:53
+msgid "Group hosts in your inventory logically according to their **What**, **Where**, and **When**."
+msgstr "**What**、**Where**、および **When** に従って、インベントリー内のホストを論理的にグループ化します。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:55
+msgid "What"
+msgstr "確認対象"
+
+#: ../../rst/getting_started/get_started_inventory.rst:56
+msgid "Group hosts according to the topology, for example: db, web, leaf, spine."
+msgstr "トポロジーに従ってホストを分類します (例: db、web、leaf、spine)。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:57
+msgid "Where"
+msgstr "Where"
+
+#: ../../rst/getting_started/get_started_inventory.rst:58
+msgid "Group hosts by geographic location, for example: datacenter, region, floor, building."
+msgstr "地理的な場所でホストを分類します (例: datacenter、region、floor、build)。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:60
+msgid "When"
+msgstr "When"
+
+#: ../../rst/getting_started/get_started_inventory.rst:60
+msgid "Group hosts by stage, for example: development, test, staging, production."
+msgstr "ステージごとにホストを分類します (例: development、test、staging、production)。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:63
+msgid "Use metagroups"
+msgstr "メタグループの使用"
+
+#: ../../rst/getting_started/get_started_inventory.rst:65
+msgid "Create a metagroup that organizes multiple groups in your inventory with the following syntax:"
+msgstr "以下の構文を使用して、インベントリー内に複数のグループを整理するメタグループを作成します。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:72
+msgid "The following inventory illustrates a basic structure for a data center. This example inventory contains a ``network`` metagroup that includes all network devices and a ``datacenter`` metagroup that includes the ``network`` group and all webservers."
+msgstr "以下のインベントリーは、データセンターの基本構造を示しています。このインベントリーの例には、すべてのネットワークデバイスを含む ``network`` メタグループと、``network`` グループとすべての Web サーバー含む ``datacenter`` メタグループが含まれます。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:79
+msgid "Create variables"
+msgstr "変数の作成"
+
+#: ../../rst/getting_started/get_started_inventory.rst:81
+msgid "Variables set values for managed nodes, such as the IP address, FQDN, operating system, and SSH user, so you do not need to pass them when running Ansible commands."
+msgstr "変数は、IP アドレス、FQDN、オペレーティングシステム、SSH ユーザーなどの管理対象ノードの値を設定するため、Ansible コマンドの実行時に渡す必要はありません。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:83
+msgid "Variables can apply to specific hosts."
+msgstr "変数は特定のホストに適用できます。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:88
+msgid "Variables can also apply to all hosts in a group."
+msgstr "変数は、グループ内のすべてのホストにも適用できます。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:93
+msgid "Now that you know how to build an inventory, continue by :ref:`learning how to create a playbook<get_started_playbook>`."
+msgstr "インベントリーのビルド方法を把握したので、:ref:`learning how to create a playbook<get_started_playbook>` に進みます。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:97
+msgid ":ref:`intro_inventory`"
+msgstr ":ref:`intro_inventory`"
+
+#: ../../rst/getting_started/get_started_inventory.rst:98
+msgid "Learn more about inventories in ``YAML`` or ``INI`` format."
+msgstr "インベントリーの詳細は、``YAML`` または ``INI`` 形式で確認します。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:99
+msgid ":ref:`variables_in_inventory`"
+msgstr ":ref:`variables_in_inventory`"
+
+#: ../../rst/getting_started/get_started_inventory.rst:100
+msgid "Find out more about inventory variables and their syntax."
+msgstr "インベントリー変数とその構文について詳細を確認します。"
+
+#: ../../rst/getting_started/get_started_inventory.rst:101
+msgid ":ref:`vault`"
+msgstr ":ref:`vault`"
+
+#: ../../rst/getting_started/get_started_inventory.rst:102
+msgid "Find out how to encrypt sensitive content in your inventory such as passwords and keys."
+msgstr "パスワードやキーなど、インベントリー内の機密コンテンツを暗号化する方法を確認します。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:5
+msgid "Creating a playbook"
+msgstr "Playbook の作成"
+
+#: ../../rst/getting_started/get_started_playbook.rst:7
+msgid "Playbooks are automation blueprints, in ``YAML`` format, that Ansible uses to deploy and configure managed nodes."
+msgstr "Playbook は、Ansible が管理ノードのデプロイおよび設定に使用する、``YAML`` 形式の自動 Blueprint です。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:10
+msgid "Playbook"
+msgstr "Playbook"
+
+#: ../../rst/getting_started/get_started_playbook.rst:10
+msgid "A list of plays that define the order in which Ansible performs operations, from top to bottom, to achieve an overall goal."
+msgstr "全体的な目標を達成するために、Ansible が上から下に操作を実行する順序を定義するプレイのリスト。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:13
+msgid "Play"
+msgstr "プレイ"
+
+#: ../../rst/getting_started/get_started_playbook.rst:13
+msgid "An ordered list of tasks that maps to managed nodes in an inventory."
+msgstr "インベントリーの管理対象ノードにマップするタスクの順序付きリスト。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:16
+msgid "Task"
+msgstr "タスク"
+
+#: ../../rst/getting_started/get_started_playbook.rst:16
+msgid "A list of one or more modules that defines the operations that Ansible performs."
+msgstr "Ansible が実行する操作を定義する 1 つ以上のモジュールの一覧。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:20
+msgid "Module"
+msgstr "モジュール"
+
+#: ../../rst/getting_started/get_started_playbook.rst:19
+msgid "A unit of code or binary that Ansible runs on managed nodes. Ansible modules are grouped in collections with a :term:`Fully Qualified Collection Name (FQCN)` for each module."
+msgstr "Ansible が管理対象ノードで実行するコードまたはバイナリーの単位。Ansible モジュールは、各モジュールの :term:`Fully Qualified Collection Name (FQCN)` でコレクションにグループ化されます。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:22
+msgid "In the previous section, you used the ``ansible`` command to ping hosts in your inventory. Now let's create a playbook that pings your hosts and also prints a \"Hello world\" message."
+msgstr "前のセクションでは、``ansible`` コマンドを使用してインベントリー内のホストに ping を送信しました。次に、ホストに ping し、「Hello world」というメッセージも出力する Playbook を作成してみましょう。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:28
+msgid "Create a new playbook file named ``playbook.yaml`` in any directory and open it for editing."
+msgstr "任意のディレクトリーに ``playbook.yaml`` という名前の新しい Playbook ファイルを作成し、そのファイルを開いて編集します。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:29
+msgid "Add the following content to ``playbook.yaml``:"
+msgstr "``playbook.yaml`` に以下の内容を追加します。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:34
+msgid "Run your playbook."
+msgstr "Playbook を実行します。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:40
+msgid "Ansible returns the following output:"
+msgstr "Ansible は次の出力を返します。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:45
+msgid "In this output you can see:"
+msgstr "この出力で、以下を確認できます。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:47
+msgid "The names that you give the play and each task. You should always use descriptive names that make it easy to verify and troubleshoot playbooks."
+msgstr "プレイと各タスクを指定する名前。Playbook の検証とトラブルシューティングを容易にする説明的な名前を常に使用する必要があります。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:50
+msgid "The ``Gather Facts`` task runs implicitly. By default Ansible gathers information about your inventory that it can use in the playbook."
+msgstr "``Gather Facts`` タスクは暗黙的に実行されます。デフォルトでは、Ansible は Playbook で使用できるインベントリーに関する情報を収集します。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:53
+msgid "The status of each task. Each task has a status of ``ok`` which means it ran successfully."
+msgstr "各タスクのステータス。各タスクのステータスは ``ok`` で、正常に実行されたことを意味します。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:56
+msgid "The play recap that summarizes results of all tasks in the playbook per host. In this example, there are three tasks so ``ok=3`` indicates that each task ran successfully."
+msgstr "ホストごとに Playbook のすべてのタスクの結果をまとめたプレイの要約。この例では、3 つのタスクがあり、``ok=3`` は各タスクが正常に実行されたことを示しています。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:59
+msgid "Congratulations! You have just created your first Ansible playbook."
+msgstr "おめでとうございます。最初の Ansible Playbook を作成しました。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:63
+msgid ":ref:`playbooks_intro`"
+msgstr ":ref:`playbooks_intro`"
+
+#: ../../rst/getting_started/get_started_playbook.rst:64
+msgid "Start building playbooks for real world scenarios."
+msgstr "実際のシナリオ用の Playbook のビルドを開始します。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:65
+msgid ":ref:`working_with_playbooks`"
+msgstr ":ref:`working_with_playbooks`"
+
+#: ../../rst/getting_started/get_started_playbook.rst:66
+msgid "Go into more detail with Ansible playbooks."
+msgstr "Ansible Playbook について詳しく説明します。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:67
+msgid ":ref:`playbooks_best_practices`"
+msgstr ":ref:`playbooks_best_practices`"
+
+#: ../../rst/getting_started/get_started_playbook.rst:68
+msgid "Get tips and tricks for using playbooks."
+msgstr "Playbook の使用に関するヒント。"
+
+#: ../../rst/getting_started/get_started_playbook.rst:69
+msgid ":ref:`vars_and_facts`"
+msgstr ":ref:`vars_and_facts`"
+
+#: ../../rst/getting_started/get_started_playbook.rst:70
+msgid "Learn more about the ``gather_facts`` keyword in playbooks."
+msgstr "Playbook の ``gather_facts`` キーワードの詳細を確認できます。"
+
+#: ../../rst/getting_started/index.rst:5
+msgid "Getting started with Ansible"
+msgstr "Ansible のスタートガイド"
+
+#: ../../rst/getting_started/index.rst:7
+msgid "Ansible automates the management of remote systems and controls their desired state. A basic Ansible environment has three main components:"
+msgstr "Ansible はリモートシステムの管理を自動化し、必要な状態を制御します。基本的な Ansible 環境には、以下の 3 つの主要コンポーネントがあります。"
+
+#: ../../rst/getting_started/index.rst:13
+msgid "Control node"
+msgstr "コントロールノード"
+
+#: ../../rst/getting_started/index.rst:12
+msgid "A system on which Ansible is installed. You run Ansible commands such as ``ansible`` or ``ansible-inventory`` on a control node."
+msgstr "Ansible がインストールされているシステム。コントロールノードで ``ansible`` や ``ansible-inventory`` などの Ansible コマンドを実行します。"
+
+#: ../../rst/getting_started/index.rst:16
+msgid "Managed node"
+msgstr "管理対象ノード"
+
+#: ../../rst/getting_started/index.rst:16
+msgid "A remote system, or host, that Ansible controls."
+msgstr "Ansible が制御するリモートシステムまたはホスト。"
+
+#: ../../rst/getting_started/index.rst:20
+msgid "Inventory"
+msgstr "インベントリー"
+
+#: ../../rst/getting_started/index.rst:19
+msgid "A list of managed nodes that are logically organized. You create an inventory on the control node to describe host deployments to Ansible."
+msgstr "論理的に編成される管理対象ノードの一覧。コントロールノードにインベントリーを作成し、Ansible にホストのデプロイメントを記述します。"
+
+msgid "Basic components of an Ansible environment include a control node, an inventory of managed nodes, and a module copied to each managed node."
+msgstr "Ansible 環境の基本コンポーネントには、コントロールノード、管理対象ノードのインベントリー、および各管理対象ノードにコピーされたモジュールが含まれます。"
+
+#: ../../rst/getting_started/index.rst:28
+msgid "Ready to start using Ansible? Complete the following steps to get up and running:"
+msgstr "Ansible の使用を開始する準備ができましたか。それでは、以下の手順を実行して起動しましょう。"
+
+#: ../../rst/getting_started/index.rst:31
+msgid "Install Ansible. Visit the :ref:`installation guide<installation_guide>` for complete details."
+msgstr "Ansible をインストールします。詳細は、:ref:`installation guide<installation_guide>` を参照してください。"
+
+#: ../../rst/getting_started/index.rst:37
+msgid "Create an inventory by adding the IP address or fully qualified domain name (FQDN) of one or more remote systems to ``/etc/ansible/hosts``. The following example adds the IP addresses of three virtual machines in KVM:"
+msgstr "1 つ以上のリモートシステムの IP アドレスまたは完全修飾ドメイン名 (FQDN) を ``/etc/ansible/hosts`` に追加してインベントリーを作成します。以下の例では、KVM に 3 つの仮想マシンの IP アドレスを追加します。"
+
+#: ../../rst/getting_started/index.rst:47
+msgid "Verify the hosts in your inventory."
+msgstr "インベントリー内のホストを確認します。"
+
+#: ../../rst/getting_started/index.rst:60
+msgid "Set up SSH connections so Ansible can connect to the managed nodes."
+msgstr "Ansible が管理対象ノードに接続できるように SSH 接続を設定します。"
+
+#: ../../rst/getting_started/index.rst:62
+msgid "Add your public SSH key to the ``authorized_keys`` file on each remote system."
+msgstr "公開 SSH キーを各リモートシステムの ``authorized_keys`` ファイルに追加します。"
+
+#: ../../rst/getting_started/index.rst:63
+msgid "Test the SSH connections, for example:"
+msgstr "SSH 接続をテストします。以下はその例です。"
+
+#: ../../rst/getting_started/index.rst:69
+msgid "If the username on the control node is different on the host, you need to pass the ``-u`` option with the ``ansible`` command."
+msgstr "コントロールノードのユーザー名がホストで異なる場合は、``ansible`` コマンドで ``-u`` オプションを指定する必要があります。"
+
+#: ../../rst/getting_started/index.rst:71
+msgid "Ping the managed nodes."
+msgstr "管理対象ノードを ping します。"
+
+#: ../../rst/getting_started/index.rst:80
+msgid "Congratulations! You are now using Ansible. Continue by :ref:`learning how to build an inventory<get_started_inventory>`."
+msgstr "おめでとうございます。これで Ansible を使用している状態になりました。:ref:`learning how to build an inventory<get_started_inventory>` に進んでください。"
+
+#: ../../rst/getting_started/index.rst:85
+msgid "`Ansible Demos <https://github.com/ansible/product-demos>`_"
+msgstr "`Ansible Demos <https://github.com/ansible/product-demos>`_"
+
+#: ../../rst/getting_started/index.rst:86
+msgid "Demonstrations of different Ansible usecases"
+msgstr "各種 Ansible のユースケースのデモ"
+
+#: ../../rst/getting_started/index.rst:87
+msgid "`RHEL Labs <https://katacoda.com/rhel-labs>`_"
+msgstr "`RHEL Labs <https://katacoda.com/rhel-labs>`_"
+
+#: ../../rst/getting_started/index.rst:88
+msgid "Labs to provide further knowledge on different topics"
+msgstr "さまざまなトピックでの詳細な知識を提供するラボ"
+
+#: ../../rst/getting_started/index.rst:89
+msgid "`Mailing List <https://groups.google.com/group/ansible-project>`_"
+msgstr "`Mailing List <https://groups.google.com/group/ansible-project>`_"
+
+#: ../../rst/getting_started/index.rst:90
+msgid "Questions? Help? Ideas?  Stop by the list on Google Groups"
+msgstr "ご質問はございますか。サポートが必要ですか。ご提案はございますか。Google グループの一覧をご覧ください。"
+
+#: ../../rst/getting_started/index.rst:91
+msgid ":ref:`communication_irc`"
+msgstr ":ref:`communication_irc`"
+
+#: ../../rst/getting_started/index.rst:92
+msgid "How to join Ansible chat channels"
+msgstr "Ansible チャットチャンネルへの参加方法"
+
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/index.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/index.po
@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Ansible devel\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-03-08 20:25+0100\n"
+"POT-Creation-Date: 2022-06-27 15:07+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@ -16,31 +16,35 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 "Generated-By: Babel 2.9.0\n"

-#: ../../rst/2.10_index.rst:23 ../../rst/ansible_index.rst:25
-#: ../../rst/core_index.rst:30
+#: ../../rst/ansible_index.rst:27 ../../rst/core_index.rst:34
+msgid "Ansible getting started"
+msgstr "Ansible スタートガイド"
+
+#: ../../rst/2.10_index.rst:23 ../../rst/ansible_index.rst:33
+#: ../../rst/core_index.rst:40
 msgid "Installation, Upgrade & Configuration"
 msgstr "インストール、アップグレード、および設定"

-#: ../../rst/core_index.rst:37
+#: ../../rst/core_index.rst:47
 msgid "Using Ansible Core"
 msgstr "Ansible Core の使用"

-#: ../../rst/core_index.rst:43
+#: ../../rst/core_index.rst:53
 msgid "Contributing to Ansible Core"
 msgstr "Ansible Core への貢献"

-#: ../../rst/2.10_index.rst:42 ../../rst/ansible_index.rst:44
-#: ../../rst/core_index.rst:49
+#: ../../rst/2.10_index.rst:42 ../../rst/ansible_index.rst:56
+#: ../../rst/core_index.rst:62
 msgid "Extending Ansible"
 msgstr "Ansible の拡張"

-#: ../../rst/2.10_index.rst:73 ../../rst/ansible_index.rst:75
-#: ../../rst/core_index.rst:56
+#: ../../rst/2.10_index.rst:73 ../../rst/ansible_index.rst:87
+#: ../../rst/core_index.rst:69
 msgid "Reference & Appendices"
 msgstr "参照および付録"

-#: ../../rst/2.10_index.rst:102 ../../rst/ansible_index.rst:100
-#: ../../rst/core_index.rst:80
+#: ../../rst/2.10_index.rst:102 ../../rst/ansible_index.rst:112
+#: ../../rst/core_index.rst:93
 msgid "Roadmaps"
 msgstr "ロードマップ"

@ -57,52 +61,66 @@ msgstr "ansible-core の概要"
 msgid "Ansible is an IT automation tool.  It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates."
 msgstr "Ansible は IT 自動化ツールです。このツールを使用すると、システムの構成、ソフトウェアの展開、より高度な IT タスク (継続的なデプロイメント、ダウンタイムなしのローリング更新など) のオーケストレーションが可能になります。"

-#: ../../rst/2.10_index.rst:11 ../../rst/ansible_index.rst:13
 #: ../../rst/core_index.rst:15
+msgid "Ansible core, or ``ansible-core`` is the main building block and architecture for Ansible, and includes:"
+msgstr "Ansible コアまたは ``ansible-core`` は Ansible の主要なビルディングブロックおよびアーキテクチャーであり、以下が含まれます。"
+
+#: ../../rst/core_index.rst:17
+msgid "CLI tools such as ``ansible-playbook``, ``ansible-doc``. and others for driving and interacting with automation."
+msgstr "自動化で動作や対話を行う ``ansible-playbook``、``ansible-doc`` などの CLI ツール"
+
+#: ../../rst/core_index.rst:18
+msgid "The Ansible language that uses YAML to create a set of rules for developing Ansible Playbooks and includes functions such as conditionals, blocks, includes, loops, and other Ansible imperatives."
+msgstr "YAML を使用して Ansible Playbook を開発するための一連のルールを作成し、conditional、block、include、include、その他の Ansible 命令などの関数を追加する Ansible 言語"
+
+#: ../../rst/core_index.rst:19
+msgid "An architectural framework that allows extensions through Ansible collections."
+msgstr "Ansible コレクションで拡張機能を可能にするアーキテクチャーフレームワーク"
+
+#: ../../rst/2.10_index.rst:11 ../../rst/ansible_index.rst:13
+#: ../../rst/core_index.rst:21
 msgid "Ansible's main goals are simplicity and ease-of-use. It also has a strong focus on security and reliability, featuring a minimum of moving parts, usage of OpenSSH for transport (with other transports and pull modes as alternatives), and a language that is designed around auditability by humans--even those not familiar with the program."
 msgstr "Ansible の主な目標は、簡単で使いやすいことです。また、セキュリティーおよび信頼性に重点を置いており、最小限の可動部品、トランスポート用の OpenSSH の使用 (代替として他のトランスポートとプルモードを使用)、およびプログラムに精通していない人でも監査を可能にする言語も備えています。"

 #: ../../rst/2.10_index.rst:13 ../../rst/ansible_index.rst:15
-#: ../../rst/core_index.rst:17
+#: ../../rst/core_index.rst:23
 msgid "We believe simplicity is relevant to all sizes of environments, so we design for busy users of all types: developers, sysadmins, release engineers, IT managers, and everyone in between. Ansible is appropriate for managing all environments, from small setups with a handful of instances to enterprise environments with many thousands of instances."
 msgstr "簡素化はあらゆる規模の環境に関連しており、開発者、システム管理者、リリースエンジニア、IT マネージャーなど、あらゆるタイプのビジーユーザー向けに設計されています。Ansible は、わずかなインスタンスしかない小規模のセットアップから、インスタンスが数千にもなるエンタープライズ環境まで、すべての環境を管理するのに適しています。"

 #: ../../rst/2.10_index.rst:15 ../../rst/ansible_index.rst:17
-#: ../../rst/core_index.rst:19
+#: ../../rst/core_index.rst:25
 msgid "You can learn more at `AnsibleFest <https://www.ansible.com/ansiblefest>`_, the annual event for all Ansible contributors, users, and customers hosted by Red Hat. AnsibleFest is the place to connect with others, learn new skills, and find a new friend to automate with."
 msgstr "詳細は、`AnsibleFest <https://www.ansible.com/ansiblefest>`_ (Red Hat が開催する、Ansible のすべての貢献者、ユーザー、および顧客のための毎年恒例のイベント) で学ぶことができます。AnsibleFest は、他の人とつながり、新しいスキルを学び、自動化に興味のある人達と知り合うためのイベントです。"

-#: ../../rst/2.10_index.rst:17 ../../rst/ansible_index.rst:19
-#: ../../rst/core_index.rst:21
+#: ../../rst/2.10_index.rst:17 ../../rst/core_index.rst:27
 msgid "Ansible manages machines in an agent-less manner. There is never a question of how to upgrade remote daemons or the problem of not being able to manage systems because daemons are uninstalled.  Because OpenSSH is one of the most peer-reviewed open source components, security exposure is greatly reduced. Ansible is decentralized--it relies on your existing OS credentials to control access to remote machines. If needed, Ansible can easily connect with Kerberos, LDAP, and other centralized authentication management systems."
 msgstr "Ansible は、エージェントを使用せずにマシンを管理します。リモートデーモンをアップグレードする方法や、デーモンがアンインストールされているためにシステムを管理できないという問題はありません。OpenSSH は、相互評価が最も行われるオープンソースコンポーネントの 1 つであるため、セキュリティーの危険性は大幅に軽減されます。Ansible は分散化されており、既存の OS 認証情報を使用して、リモートマシンへのアクセスを制御します。必要に応じて、Ansible は、Kerberos、LDAP、およびその他の集中認証管理システムに簡単に接続できます。"

-#: ../../rst/2.10_index.rst:19 ../../rst/ansible_index.rst:21
-#: ../../rst/core_index.rst:23
-msgid "This documentation covers the version of Ansible noted in the upper left corner of this page. We maintain multiple versions of Ansible and of the documentation, so please be sure you are using the version of the documentation that covers the version of Ansible you're using. For recent features, we note the version of Ansible where the feature was added."
-msgstr "本ドキュメントは、本ページの左上にある Ansible のバージョンを説明します。Red Hat は、複数のバージョンの Ansible とドキュメントを提供しているため、参照しているドキュメントが、お使いの Ansible のバージョンのものであることを確認してください。最新の機能については、この機能が追加された Ansible のバージョンを記載しています。"
+#: ../../rst/core_index.rst:29
+msgid "This documentation covers the version of ``ansible-core`` noted in the upper left corner of this page. We maintain multiple versions of ``ansible-core`` and of the documentation, so please be sure you are using the version of the documentation that covers the version of Ansible you're using. For recent features, we note the version of Ansible where the feature was added."
+msgstr "本ドキュメントは、本ページの左上に示されている ``ansible-core`` のバージョンについて説明します。Red Hat は、複数のバージョンの ``ansible-core`` とドキュメントを提供しているため、参照しているドキュメントが、お使いの Ansible のバージョンのものであることを確認してください。最新の機能については、その機能が追加された Ansible のバージョンが記載されています。"

-#: ../../rst/core_index.rst:26
+#: ../../rst/core_index.rst:32
 msgid "``ansible-core`` releases a new major release approximately twice a year. The core application evolves somewhat conservatively, valuing simplicity in language design and setup. Contributors develop and change modules and plugins, hosted in collections since version 2.10, much more quickly."
-msgstr "``ansible-core`` は、年に約 2 回、新しいメジャーリリースをリリースします。コアアプリケーションは、言語の設計および設定の単純性が重視され、その進化は若干保守的となります。貢献者はバージョン 2.10 以降のコレクションでホストされるモジュールとプラグインを、はるかに迅速に開発および変更します。"
+msgstr "``ansible-core`` は、年に約 2 回、新しいメジャーリリースをリリースします。コアアプリケーションは、言語の設計および設定の単純性が重視され、その進化は若干保守的となります。バージョン 2.10 以降のコレクションで提供されるモジュールとプラグインは、貢献者によりはるかに迅速に開発および変更されます。"

-#: ../../rst/2.10_index.rst:30 ../../rst/ansible_index.rst:32
+#: ../../rst/2.10_index.rst:30 ../../rst/ansible_index.rst:40
 msgid "Using Ansible"
 msgstr "Ansible の使用"

-#: ../../rst/2.10_index.rst:36 ../../rst/ansible_index.rst:38
+#: ../../rst/2.10_index.rst:36 ../../rst/ansible_index.rst:46
 msgid "Contributing to Ansible"
 msgstr "Ansible への貢献"

-#: ../../rst/2.10_index.rst:48 ../../rst/ansible_index.rst:50
+#: ../../rst/2.10_index.rst:48 ../../rst/ansible_index.rst:62
 msgid "Common Ansible Scenarios"
 msgstr "Ansible の一般的なシナリオ"

-#: ../../rst/2.10_index.rst:57 ../../rst/ansible_index.rst:59
+#: ../../rst/2.10_index.rst:57 ../../rst/ansible_index.rst:71
 msgid "Network Automation"
 msgstr "ネットワークの自動化"

-#: ../../rst/2.10_index.rst:65 ../../rst/ansible_index.rst:67
+#: ../../rst/2.10_index.rst:65 ../../rst/ansible_index.rst:79
 msgid "Ansible Galaxy"
 msgstr "Ansible Galaxy"

@ -114,11 +132,31 @@ msgstr "Ansible ドキュメント"
 msgid "About Ansible"
 msgstr "Ansible の概要"

-#: ../../rst/2.10_index.rst:21 ../../rst/ansible_index.rst:23
-msgid "Ansible releases a new major release approximately twice a year. The core application evolves somewhat conservatively, valuing simplicity in language design and setup. Contributors develop and change modules and plugins, hosted in collections since version 2.10, much more quickly."
-msgstr "Ansible は、年に約 2 回、新しいメジャーリリースをリリースします。コアアプリケーションは、言語の設計および設定の単純性が重視され、その進化は若干保守的となります。貢献者はバージョン 2.10 以降のコレクションでホストされるモジュールとプラグインを、はるかに迅速に開発および変更します。"
+#: ../../rst/ansible_index.rst:19
+msgid "Ansible manages machines in an agent-less manner. There is never a question of how to upgrade remote daemons or the problem of not being able to manage systems because daemons are uninstalled. Also, security exposure is greatly reduced because Ansible uses OpenSSH — the open source connectivity tool for remote login with the SSH (Secure Shell) protocol."
+msgstr "Ansible は、エージェントなしの方法でマシンを管理します。デーモンがアンインストールされているため、リモートデーモンのアップグレード方法に関する疑問や、システムを管理できないなどの問題は発生しません。また、Ansible は SSH (Secure Shell) プロトコルでのリモートログインに、オープンソース接続ツールである OpenSSH を使用するため、セキュリティー脆弱性が大幅に削減されます。"
+
+#: ../../rst/ansible_index.rst:21
+msgid "Ansible is decentralized--it relies on your existing OS credentials to control access to remote machines. And if needed, Ansible can easily connect with Kerberos, LDAP, and other centralized authentication management systems."
+msgstr "Ansible は分散化されており、既存の OS クレデンシャルに依存してリモートマシンへのアクセスを制御します。必要に応じて、Ansible は Kerberos、LDAP、およびその他の集中型認証管理システムに簡単に接続できます。"
+
+#: ../../rst/ansible_index.rst:23
+msgid "This documentation covers the version of Ansible noted in the upper left corner of this page. We maintain multiple versions of Ansible and the Ansible documentation, so please be sure you are using the documentation version that covers the version of Ansible you are using. For recent features, we note the version of Ansible where the feature was added."
+msgstr "このドキュメントは、このページの左上に示されている Ansible のバージョンについて説明します。Red Hat は、複数のバージョンの Ansible と Ansible ドキュメントを提供しているため、参照しているドキュメントが、お使いの Ansible のバージョンのものであることを確認してください。最新の機能については、その機能が追加された Ansible のバージョンが記載されています。"
+
+#: ../../rst/ansible_index.rst:25
+msgid "Ansible releases a new major release approximately twice a year. The core application evolves somewhat conservatively, valuing simplicity in language design and setup. Contributors develop and change modules and plugins hosted in collections since version 2.10 much more quickly."
+msgstr "Ansible は、年に約 2 回、新しいメジャーリリースをリリースします。コアアプリケーションは、言語の設計および設定の単純性が重視され、その進化は若干保守的となります。バージョン 2.10 以降のコレクションで提供されるモジュールとプラグインは、貢献者によりはるかに迅速に開発および変更されます。"

 #: ../../rst/2.10_index.rst:98
 msgid "Release Notes"
 msgstr "リリースノート"

+#: ../../rst/2.10_index.rst:19
+msgid "This documentation covers the version of Ansible noted in the upper left corner of this page. We maintain multiple versions of Ansible and of the documentation, so please be sure you are using the version of the documentation that covers the version of Ansible you're using. For recent features, we note the version of Ansible where the feature was added."
+msgstr "本ドキュメントは、本ページの左上に示されている Ansible のバージョンについて説明します。Red Hat は、複数のバージョンの Ansible とドキュメントを提供しているため、参照しているドキュメントが、お使いの Ansible のバージョンのものであることを確認してください。最新の機能については、その機能が追加された Ansible のバージョンが記載されています。"
+
+#: ../../rst/2.10_index.rst:21
+msgid "Ansible releases a new major release approximately twice a year. The core application evolves somewhat conservatively, valuing simplicity in language design and setup. Contributors develop and change modules and plugins, hosted in collections since version 2.10, much more quickly."
+msgstr "Ansible は、年に約 2 回、新しいメジャーリリースをリリースします。コアアプリケーションは、言語の設計および設定の単純性が重視され、その進化は若干保守的となります。バージョン 2.10 以降のコレクションで提供されるモジュールとプラグインは、貢献者によりはるかに迅速に開発および変更されます。"
+
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/installation_guide.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/installation_guide.po
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/network.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/network.po
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/plugins.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/plugins.po
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/porting_guides.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/porting_guides.po
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/reference_appendices.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/reference_appendices.po
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/roadmap.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/roadmap.po
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/scenario_guides.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/scenario_guides.po
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/shared_snippets.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/shared_snippets.po
@ -0,0 +1,30 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) Ansible project contributors
+# This file is distributed under the same license as the Ansible package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2022.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Ansible devel\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-04-14 14:48+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.9.0\n"
+
+#: ../../rst/shared_snippets/installing_collections_file.rst:1
+msgid "Ansible can also install from a source directory in several ways:"
+msgstr "Ansible は、複数の方法でソースディレクトリーからインストールすることもできます。"
+
+#: ../../rst/shared_snippets/installing_collections_file.rst:14
+msgid "Ansible can also install a collection collected with ``ansible-galaxy collection build`` or downloaded from Galaxy for offline use by specifying the output file directly:"
+msgstr "出力ファイルを直接指定して、Ansible は``ansible-galaxy collection build`` で収集したコレクションまたは Galaxy からダウンロードしたコレクションをオフライン用にインストールすることもできます。"
+
+#: ../../rst/shared_snippets/installing_collections_file.rst:24
+msgid "Relative paths are calculated from the current working directory (where you are invoking ``ansible-galaxy install -r`` from). They are not taken relative to the ``requirements.yml`` file."
+msgstr "相対パスは、現在の作業ディレクトリー（``ansible-galaxy install -r`` を呼び出しているディレクトリー）から計算されます。これは、``requirements.yml`` ファイルからの相対パスではありません。"
+
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/sphinx.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/sphinx.po
@ -0,0 +1,35 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) Ansible project contributors
+# This file is distributed under the same license as the Ansible package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2022.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: Ansible devel\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2022-04-14 14:48+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.9.0\n"
+
+#: ../../.templates/breadcrumbs.html:8 ../../.templates/breadcrumbs.html:26
+#: ../../.templates/breadcrumbs.html:28
+msgid "Edit on GitHub"
+msgstr "GitHub で編集"
+
+#: ../../.templates/breadcrumbs.html:34 ../../.templates/breadcrumbs.html:36
+msgid "Edit on Bitbucket"
+msgstr "Bitbucket で編集"
+
+#: ../../.templates/breadcrumbs.html:41 ../../.templates/breadcrumbs.html:43
+msgid "Edit on GitLab"
+msgstr "GitLab で編集"
+
+#: ../../.templates/breadcrumbs.html:46 ../../.templates/breadcrumbs.html:48
+msgid "View page source"
+msgstr "ページソースの表示"
+
--- a/docs/docsite/rst/locales/ja/LC_MESSAGES/user_guide.po
+++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/user_guide.po
--- a/docs/docsite/rst/plugins/inventory.rst
+++ b/docs/docsite/rst/plugins/inventory.rst
@ -23,13 +23,20 @@ In some circumstances, for example, if the inventory plugin does not use a YAML
   [inventory]
   enable_plugins = host_list, script, auto, yaml, ini, toml

-If the plugin is in a collection, use the fully qualified name:
+If the plugin is in a collection and is not being picked up by the `auto` statement, you can append the fully qualified name:

 .. code-block:: ini

   [inventory]
-   enable_plugins = namespace.collection_name.inventory_plugin_name
+   enable_plugins = host_list, script, auto, yaml, ini, toml, namespace.collection_name.inventory_plugin_name

+Or, if it is a local plugin, perhaps stored in the path set by :ref:`DEFAULT_INVENTORY_PLUGIN_PATH`, you could reference it as follows:
+
+.. code-block:: ini
+
+   [inventory]
+   enable_plugins = host_list, script, auto, yaml, ini, toml, my_plugin
+   
 If you use a plugin that supports a YAML configuration source, make sure that the name matches the name provided in the ``plugin`` entry of the inventory source file.

 .. _using_inventory:
@ -80,12 +87,24 @@ You can create dynamic groups using host variables with the constructed ``keyed_
      - key: tags.Name
        prefix: tag_Name_
        separator: ""
+      # If you have a tag called "Role" which has the value "Webserver", this will add the group
+      # role_Webserver and add any hosts that have that tag assigned to it.
+      - key: tags.Role
+        prefix: role
    groups:
      # add hosts to the group development if any of the dictionary's keys or values is the word 'devel'
      development: "'devel' in (tags|list)"
+      # add hosts to the "private_only" group if the host doesn't have a public IP associated to it
+      private_only: "public_ip_address is not defined"
    compose:
-      # set the ansible_host variable to connect with the private IP address without changing the hostname
-      ansible_host: private_ip_address
+      # use a private address where a public one isn't assigned
+      ansible_host: public_ip_address|default(private_ip_address)
+      # alternatively, set the ansible_host variable to connect with the private IP address without changing the hostname
+      # ansible_host: private_ip_address
+      # if you *must* set a string here (perhaps to identify the inventory source if you have multiple
+      # accounts you want to use as sources), you need to wrap this in two sets of quotes, either ' then "
+      # or " then '
+      some_inventory_wide_string: '"Yes, you need both types of quotes here"'

 Now the output of ``ansible-inventory -i demo.aws_ec2.yml --graph``:

@ -99,6 +118,8 @@ Now the output of ``ansible-inventory -i demo.aws_ec2.yml --graph``:
      |--@development:
      |  |--ec2-12-345-678-901.compute-1.amazonaws.com
      |  |--ec2-98-765-432-10.compute-1.amazonaws.com
+      |--@role_Webserver
+      |  |--ec2-12-345-678-901.compute-1.amazonaws.com
      |--@tag_Name_ECS_Instance:
      |  |--ec2-98-765-432-10.compute-1.amazonaws.com
      |--@tag_Name_Test_Server:
--- a/docs/docsite/rst/porting_guides/porting_guide_5.rst
+++ b/docs/docsite/rst/porting_guides/porting_guide_5.rst
@ -46,7 +46,7 @@ Playbook
 Python Interpreter Discovery
 ============================

-The default value of ``INTERPRETER_PYTHON_FALLBACK`` changed to ``auto``. The list of Python interpreters in ``INTERPRETER_PYTHON_FALLBACK`` changed to prefer Python 3 over Python 2. The combination of these two changes means the new default behavior is to quietly prefer Python 3 over Python 2 on remote hosts. Previously a deprecation warning was issued in situations where interpreter discovery would have used Python 3 but the interpreter was set to ``/usr/bin/python``.
+The default value of ``INTERPRETER_PYTHON`` changed to ``auto``. The list of Python interpreters in ``INTERPRETER_PYTHON_FALLBACK`` changed to prefer Python 3 over Python 2. The combination of these two changes means the new default behavior is to quietly prefer Python 3 over Python 2 on remote hosts. Previously a deprecation warning was issued in situations where interpreter discovery would have used Python 3 but the interpreter was set to ``/usr/bin/python``.

 ``INTERPRETER_PYTHON_FALLBACK`` can be changed from the default list of interpreters by setting the ``ansible_interpreter_python_fallback`` variable.

--- a/docs/docsite/rst/porting_guides/porting_guide_6.rst
+++ b/docs/docsite/rst/porting_guides/porting_guide_6.rst
@ -99,22 +99,85 @@ Networking

 No notable changes

-Porting Guide for v6.0.0rc1
-===========================
-
-Major Changes
-------------
-
- Add a ``ansible-community`` CLI tool that allows to print the version of the Ansible community distribution. Use ``ansible-community --version`` to print this version.
-
-Porting Guide for v6.0.0b1
-==========================
+Porting Guide for v6.4.0
+========================

 Added Collections
 -----------------

- cisco.dnac (version 6.4.0)
- community.sap_libs (version 1.1.0)
+- inspur.ispim (version 1.0.1)
+- vultr.cloud (version 1.1.0)
+
+Deprecated Features
+-------------------
+
+community.general
+~~~~~~~~~~~~~~~~~
+
+- proxmox - deprecated the current ``unprivileged`` default value, will be changed to ``true`` in community.general 7.0.0 (https://github.com/pull/5224).
+
+Porting Guide for v6.3.0
+========================
+
+Major Changes
+-------------
+
+community.mysql
+~~~~~~~~~~~~~~~
+
+- mysql_db - the ``pipefail`` argument's default value will be changed to ``true`` in community.mysql 4.0.0. If your target machines do not use ``bash`` as a default interpreter, set ``pipefail`` to ``false`` explicitly. However, we strongly recommend setting up ``bash`` as a default and ``pipefail=true`` as it will protect you from getting broken dumps you don't know about (https://github.com/ansible-collections/community.mysql/issues/407).
+
+fortinet.fortios
+~~~~~~~~~~~~~~~~
+
+- Support Diff feature in check_mode.
+- Support Fortios 7.2.0.
+
+Deprecated Features
+-------------------
+
+- The google.cloud collection is considered unmaintained and will be removed from Ansible 8 if no one starts maintaining it again before Ansible 8. See `the removal process for details on how this works <https://github.com/ansible-collections/overview/blob/main/removal_from_ansible.rst#cancelling-removal-of-an-unmaintained-collection>`__ (https://github.com/ansible-community/community-topics/issues/105).
+- The servicenow.servicenow collection has been deprecated by its maintainers (https://github.com/ServiceNowITOM/servicenow-ansible/pull/69) and will be removed from Ansible 7. It can still be installed manually, but it is suggested to swich to `servicenow.itsm <https://galaxy.ansible.com/servicenow/itsm>`__ instead (https://github.com/ansible-community/community-topics/issues/124).
+
+Porting Guide for v6.2.0
+========================
+
+Added Collections
+-----------------
+
+- ibm.spectrum_virtualize (version 1.9.0)
+
+Known Issues
+------------
+
+netapp.ontap
+~~~~~~~~~~~~
+
+- na_ontap_snapshot - added documentation to use UTC format for ``expiry_time``.
+
+Major Changes
+-------------
+
+community.postgresql
+~~~~~~~~~~~~~~~~~~~~
+
+- postgresql_user - the ``groups`` argument has been deprecated and will be removed in ``community.postgresql 3.0.0``. Please use the ``postgresql_membership`` module to specify group/role memberships instead (https://github.com/ansible-collections/community.postgresql/issues/277).
+
+Deprecated Features
+-------------------
+
+community.hashi_vault
+~~~~~~~~~~~~~~~~~~~~~
+
+- vault_kv2_get lookup - the ``engine_mount_point option`` in the ``vault_kv2_get`` lookup only will change its default from ``kv`` to ``secret`` in community.hashi_vault version 4.0.0 (https://github.com/ansible-collections/community.hashi_vault/issues/279).
+
+Porting Guide for v6.1.0
+========================
+
+Added Collections
+-----------------
+
+- purestorage.fusion (version 1.0.2)

 Known Issues
 ------------
@ -125,7 +188,6 @@ dellemc.openmanage
 - idrac_user - Issue(192043) The module may error out with the message ``unable to perform the import or export operation because there are pending attribute changes or a configuration job is in progress``. Wait for the job to complete and run the task again.
 - ome_application_alerts_smtp - Issue(212310) - The module does not provide a proper error message if the destination_address is more than 255 characters.
 - ome_application_alerts_syslog - Issue(215374) - The module does not provide a proper error message if the destination_address is more than 255 characters.
- ome_application_console_preferences - Issue(224690) - The module does not display a proper error message when an unsupported value is provided for the parameters report_row_limit, email_sender_settings, and metric_collection_settings, and the value is applied on OpenManage Enterprise.
 - ome_device_local_access_configuration - Issue(215035) - The module reports ``Successfully updated the local access setting`` if an unsupported value is provided for the parameter timeout_limit. However, this value is not actually applied on OpenManage Enterprise Modular.
 - ome_device_local_access_configuration - Issue(217865) - The module does not display a proper error message if an unsupported value is provided for the user_defined and lcd_language parameters.
 - ome_device_network_services - Issue(212681) - The module does not provide a proper error message if unsupported values are provided for the parameters- port_number, community_name, max_sessions, max_auth_retries, and idle_timeout.
@ -136,227 +198,67 @@ dellemc.openmanage
 Major Changes
 -------------

-cisco.dnac
-~~~~~~~~~~
-
- Adds _info plugins to query information from database.
- Adds new plugins related to DNA version 2.2.2.3.
- Adds plugins for resource's operations that have different structure in request/response bodies (ie. _create, _update, _delete plugins).
- Adds plugins without state that perform special operation on DNA Center.
- Adds resources for modules to manage CRUD operations.
- Moves the module parameters out of the inventory and places them inside the tasks themselves.
- Update dnacentersdk requirement from 2.4.4 to 2.4.5
- Update dnacentersdk requirement from 2.4.5 to 2.4.6
- Updates previous plugins to follow DNA version 2.2.2.3 specification.
- applications_health_info - new `applicationName` parameter.
- business_sda_wireless_controller_create - Removed 'deviceIPAddress' arguments.
- business_sda_wireless_controller_delete - Removed 'deviceName' and 'siteNameHierarchy' arguments.
- network_device - Removed 'managementIpAddress' arguments.
- network_device - change `isForceDelete` parameter to `cleanConfig` parameter.
- network_device - new `cleanConfig` parameter.
- network_device_lexicographically_sorted_info - change `limit` param type from str to int
- network_device_lexicographically_sorted_info - change `offset` param type from str to int
- reserve_ip_subpool - new `ipv4GateWay` parameter.
- reserve_ip_subpool_update - Removed 'type', 'ipv4GlobalPool', 'ipv4Prefix', 'ipv4PrefixLength', 'ipv4Subnet' and 'ipv4TotalHost' arguments.
- sda_device_info - change `deviceIPAddress` to `deviceManagementIpAddress` parameter.
- sda_fabric - remove `payload` parameter.
- sda_fabric_authentication_profile - add `authenticateTemplateName` parameter.
- sda_fabric_authentication_profile - add `authenticationOrder` parameter.
- sda_fabric_authentication_profile - add `dot1xToMabFallbackTimeout` parameter.
- sda_fabric_authentication_profile - add `numberOfHosts` parameter.
- sda_fabric_authentication_profile - add `wakeOnLan` parameter.
- sda_fabric_authentication_profile - remove `payload` parameter.
- sda_fabric_authentication_profile_info - add `authenticateTemplateName` parameter.
- sda_fabric_border_device - add `borderSessionType` parameter.
- sda_fabric_border_device - add `connectedToInternet` parameter.
- sda_fabric_border_device - add `deviceManagementIpAddress` parameter.
- sda_fabric_border_device - add `externalAutonomouSystemNumber` parameter.
- sda_fabric_border_device - add `externalConnectivityIpPoolName` parameter.
- sda_fabric_border_device - add `externalConnectivitySettings` parameter.
- sda_fabric_border_device - add `externalDomainRoutingProtocolName` parameter.
- sda_fabric_border_device - add `interfaceName` parameter.
- sda_fabric_border_device - add `internalAutonomouSystemNumber` parameter.
- sda_fabric_border_device - add `l3Handoff` parameter.
- sda_fabric_border_device - add `siteNameHierarchy` parameter.
- sda_fabric_border_device - add `virtualNetworkName` parameter.
- sda_fabric_border_device - add `virtualNetwork` parameter.
- sda_fabric_border_device - add `vlanId parameter.`
- sda_fabric_border_device - change `deviceIPAddress` to `deviceManagementIpAddress` parameter.
- sda_fabric_border_device - changes in externalConnectivitySettings from object to list.
- sda_fabric_border_device - remove `payload` parameter.
- sda_fabric_border_device_info - change `deviceIPAddress` to `deviceManagementIpAddress` parameter.
- sda_fabric_control_plane_device - add `siteNameHierarchy` parameter.
- sda_fabric_control_plane_device - change `deviceIPAddress` to `deviceManagementIpAddress` parameter.
- sda_fabric_control_plane_device - remove `payload` parameter.
- sda_fabric_control_plane_device_info - change `deviceIPAddress` to `deviceManagementIpAddress` parameter.
- sda_fabric_edge_device - add `siteNameHierarchy` parameter.
- sda_fabric_edge_device - change `deviceIPAddress` to `deviceManagementIpAddress` parameter.
- sda_fabric_edge_device - remove `payload` parameter.
- sda_fabric_edge_device_info - change `deviceIPAddress` to `deviceManagementIpAddress` parameter.
- sda_fabric_site - add `fabricName` parameter.
- sda_fabric_site - remove `payload` parameter.
- sda_multicast - change `fabricSiteNameHierarchy` to `siteNameHierarchy` parameter.
- sda_multicast_info - change `fabricSiteNameHierarchy` to `siteNameHierarchy` parameter.
- sda_port_assignment_for_access_point - add `authenticateTemplateName` parameter.
- sda_port_assignment_for_access_point - add `dataIpAddressPoolName` parameter.
- sda_port_assignment_for_access_point - add `deviceManagementIpAddress` parameter.
- sda_port_assignment_for_access_point - add `interfaceDescription` parameter.
- sda_port_assignment_for_access_point - add `siteNameHierarchy` parameter.
- sda_port_assignment_for_access_point - change `device_ip` to `deviceManagementIpAddress` parameter.
- sda_port_assignment_for_access_point - remove `payload` parameter.
- sda_port_assignment_for_access_point_info - change `device_ip` to `deviceManagementIpAddress` parameter.
- sda_port_assignment_for_user_device - add `authenticateTemplateName` parameter.
- sda_port_assignment_for_user_device - add `dataIpAddressPoolName` parameter.
- sda_port_assignment_for_user_device - add `interfaceDescription` parameter.
- sda_port_assignment_for_user_device - add `scalableGroupName` parameter.
- sda_port_assignment_for_user_device - add `siteNameHierarchy` parameter.
- sda_port_assignment_for_user_device - add `voiceIpAddressPoolName` parameter.
- sda_port_assignment_for_user_device - change `device_ip` to `deviceManagementIpAddress` parameter.
- sda_port_assignment_for_user_device - remove `payload` parameter.
- sda_port_assignment_for_user_device_info - change `device_ip` to `deviceManagementIpAddress` parameter.
- sda_virtual_network - remove `payload` parameter.
- sda_virtual_network_ip_pool - add `siteNameHierarchy`, `ipPoolName`, `trafficType`, `authenticationPolicyName`, `scalableGroupName`, `isL2FloodingEnabled`, `isThisCriticalPool`, `poolType`, `vlanName`, `isWirelessPool` parameters.
- sda_virtual_network_ip_pool - remove `payload` and `ipPoolName` parameter.
- service_provider_profile_delete - Rename argument from 'sp_profile_name' to 'spProfileName'.
- site_health_info - add `siteType`, `offset`, `limit` parameters
- snmpv2_read_community_credential - remove `id` and `instanceTenantId` parameter.
- snmpv2_write_community_credential - remove `id` and `instanceTenantId` parameter.
-
-community.network
-~~~~~~~~~~~~~~~~~
-
- The community.network collection no longer supports Ansible 2.9 and ansible-base 2.10. While we take no active measures to prevent usage, we will remove compatibility code and other compatility measures that will effectively prevent using most content from this collection with Ansible 2.9, and some content of this collection with ansible-base 2.10. Both Ansible 2.9 and ansible-base 2.10 will very soon be End of Life and if you are still using them, you should consider upgrading to ansible-core 2.11 or later as soon as possible (https://github.com/ansible-collections/community.network/pull/426).
-
-dellemc.openmanage
-~~~~~~~~~~~~~~~~~~
-
- idrac_server_config_profile - The module is enhanced to support export, import, and preview the SCP configuration using Redfish and added support for check mode.
-
-fortinet.fortios
-~~~~~~~~~~~~~~~~
-
- Support FortiOS 7.0.2, 7.0.3, 7.0.4, 7.0.5.
-
-Removed Features
----------------
-
-community.hashi_vault
+chocolatey.chocolatey
 ~~~~~~~~~~~~~~~~~~~~~

- aws_iam auth - the deprecated alias ``aws_iam_login`` for the ``aws_iam`` value of the ``auth_method`` option has been removed (https://github.com/ansible-collections/community.hashi_vault/issues/194).
- community.hashi_vault collection - support for Ansible 2.9 and ansible-base 2.10 has been removed (https://github.com/ansible-collections/community.hashi_vault/issues/189).
- hashi_vault lookup - the deprecated ``[lookup_hashi_vault]`` INI config section has been removed in favor of the collection-wide ``[hashi_vault_collection]`` section (https://github.com/ansible-collections/community.hashi_vault/issues/179).
+- win_chocolatey - Added bootstrap_script option to allow users to target a script URL for installing Chocolatey on clients.
+- win_chocolatey_facts - Added outdated packages list to data returned.

-community.network
-~~~~~~~~~~~~~~~~~
+infoblox.nios_modules
+~~~~~~~~~~~~~~~~~~~~~

- aireos modules - removed deprecated ``connection: local`` support. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
- aireos modules - removed deprecated ``provider`` option. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
- aruba modules - removed deprecated ``connection: local`` support. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
- aruba modules - removed deprecated ``provider`` option. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
- ce modules - removed deprecated ``connection: local`` support. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
- ce modules - removed deprecated ``provider`` option. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
- enos modules - removed deprecated ``connection: local`` support. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
- enos modules - removed deprecated ``provider`` option. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
- ironware modules - removed deprecated ``connection: local`` support. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
- ironware modules - removed deprecated ``provider`` option. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
- sros modules - removed deprecated ``connection: local`` support. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
- sros modules - removed deprecated ``provider`` option. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
+- Update `text` field of TXT Record `#128 <https://github.com/infobloxopen/infoblox-ansible/pull/128>`_
+- Update operation using `old_name` and `new_name` for the object with dummy name in `old_name` (which does not exist in system) will not create a new object in the system. An error will be thrown stating the object does not exist in the system `#129 <https://github.com/infobloxopen/infoblox-ansible/pull/129>`_

 Deprecated Features
 -------------------

- The collection ``community.sap`` has been renamed to ``community.sap_libs``. For now both collections are included in Ansible. The content in ``community.sap`` will be replaced with deprecated redirects to the new collection in Ansible 7.0.0, and these redirects will eventually be removed from Ansible. Please update your FQCNs for ``community.sap``.
+cisco.ios
+~~~~~~~~~
+
+- Deprecated ios_linkagg_module in favor of ios_lag_interfaces.
+
+community.aws
+~~~~~~~~~~~~~
+
+- aws_codebuild - The ``tags`` parameter currently uses a non-standard format and has been deprecated.  In release 6.0.0 this parameter will accept a simple key/value pair dictionary instead of the current list of dictionaries.  It is recommended to migrate to using the resource_tags parameter which already accepts the simple dictionary format (https://github.com/ansible-collections/community.aws/pull/1221).
+- route53_info - The CamelCase return values for ``HostedZones``, ``ResourceRecordSets``, and ``HealthChecks`` have been deprecated, in the future release you must use snake_case return values ``hosted_zones``, ``resource_record_sets``, and ``health_checks`` instead respectively".
+
+community.crypto
+~~~~~~~~~~~~~~~~
+
+- Support for Ansible 2.9 and ansible-base 2.10 is deprecated, and will be removed in the next major release (community.crypto 3.0.0). Some modules might still work with these versions afterwards, but we will no longer keep compatibility code that was needed to support them (https://github.com/ansible-collections/community.crypto/pull/460).

 community.docker
 ~~~~~~~~~~~~~~~~

- Support for Ansible 2.9 and ansible-base 2.10 is deprecated, and will be removed in the next major release (community.docker 3.0.0). Some modules might still work with these versions afterwards, but we will no longer keep compatibility code that was needed to support them (https://github.com/ansible-collections/community.docker/pull/361).
- The dependency on docker-compose for Execution Environments is deprecated and will be removed in community.docker 3.0.0. The `Python docker-compose library <https://pypi.org/project/docker-compose/>`__ is unmaintained and can cause dependency issues. You can manually still install it in an Execution Environment when needed (https://github.com/ansible-collections/community.docker/pull/373).
- Various modules - the default of ``tls_hostname`` that was supposed to be removed in community.docker 2.0.0 will now be removed in version 3.0.0 (https://github.com/ansible-collections/community.docker/pull/362).
- docker_stack - the return values ``out`` and ``err`` that were supposed to be removed in community.docker 2.0.0 will now be removed in version 3.0.0 (https://github.com/ansible-collections/community.docker/pull/362).
+- Support for Docker API version 1.20 to 1.24 has been deprecated and will be removed in community.docker 3.0.0. The first Docker version supporting API version 1.25 was Docker 1.13, released in January 2017. This affects the modules ``docker_container``, ``docker_container_exec``, ``docker_container_info``, ``docker_compose``, ``docker_login``, ``docker_image``, ``docker_image_info``, ``docker_image_load``, ``docker_host_info``, ``docker_network``, ``docker_network_info``, ``docker_node_info``, ``docker_swarm_info``, ``docker_swarm_service``, ``docker_swarm_service_info``, ``docker_volume_info``, and ``docker_volume``, whose minimally supported API version is between 1.20 and 1.24 (https://github.com/ansible-collections/community.docker/pull/396).
+- Support for Python 2.6 is deprecated and will be removed in the next major release (community.docker 3.0.0). Some modules might still work with Python 2.6, but we will no longer try to ensure compatibility (https://github.com/ansible-collections/community.docker/pull/388).

-community.hashi_vault
-~~~~~~~~~~~~~~~~~~~~~
+community.general
+~~~~~~~~~~~~~~~~~

- token_validate options - the shared auth option ``token_validate`` will change its default from ``true`` to ``false`` in community.hashi_vault version 4.0.0. The ``vault_login`` lookup and module will keep the default value of ``true`` (https://github.com/ansible-collections/community.hashi_vault/issues/248).
+- cmd_runner module utils - deprecated ``fmt`` in favour of ``cmd_runner_fmt`` as the parameter format object (https://github.com/ansible-collections/community.general/pull/4777).

-Porting Guide for v6.0.0a3
-==========================
+Porting Guide for v6.0.0
+========================

 Added Collections
 -----------------

+- cisco.dnac (version 6.4.0)
+- community.sap (version 1.0.0)
+- community.sap_libs (version 1.1.0)
 - vmware.vmware_rest (version 2.1.5)

-Breaking Changes
----------------
-
-community.general
-~~~~~~~~~~~~~~~~~
-
- lists_mergeby and groupby_as_dict filter plugins - adjust filter plugin filename. This change is not visible to end-users, it only affects possible other collections importing Python paths (https://github.com/ansible-collections/community.general/pull/4625).
- yarn - remove unsupported and unnecessary ``--no-emoji`` flag (https://github.com/ansible-collections/community.general/pull/4662).
-
-vmware.vmware_rest
-~~~~~~~~~~~~~~~~~~
-
- The vmware_rest 2.0.0 support vSphere 7.0.2 onwards.
- vcenter_vm_storage_policy - the format of the ``disks`` parameter has changed.
- vcenter_vm_storage_policy - the module has a new mandatory paramter: ``vm_home``.
-
-Major Changes
-------------
-
-cisco.asa
-~~~~~~~~~
-
- Minimum required ansible.netcommon version is 2.5.1.
- Updated base plugin references to ansible.netcommon.
-
-community.mysql
-~~~~~~~~~~~~~~~
-
- The community.mysql collection no longer supports ``Ansible 2.9`` and ``ansible-base 2.10``. While we take no active measures to prevent usage and there are no plans to introduce incompatible code to the modules, we will stop testing against ``Ansible 2.9`` and ``ansible-base 2.10``. Both will very soon be End of Life and if you are still using them, you should consider upgrading to the ``latest Ansible / ansible-core 2.11 or later`` as soon as possible (https://github.com/ansible-collections/community.mysql/pull/343).
-
-frr.frr
-~~~~~~~
-
- Minimum required ansible.netcommon version is 2.5.1.
- Updated base plugin references to ansible.netcommon.
-
-Deprecated Features
-------------------
-
-community.general
-~~~~~~~~~~~~~~~~~
-
- ansible_galaxy_install - deprecated support for ``ansible`` 2.9 and ``ansible-base`` 2.10 (https://github.com/ansible-collections/community.general/pull/4601).
- dig lookup plugin - the ``DLV`` record type has been decommissioned in 2017 and support for it will be removed from community.general 6.0.0 (https://github.com/ansible-collections/community.general/pull/4618).
-
-community.hashi_vault
-~~~~~~~~~~~~~~~~~~~~~
-
- token_validate options - the shared auth option ``token_validate`` will change its default from ``True`` to ``False`` in community.hashi_vault version 4.0.0. The ``vault_login`` lookup and module will keep the default value of ``True`` (https://github.com/ansible-collections/community.hashi_vault/issues/248).
-
-community.network
-~~~~~~~~~~~~~~~~~
-
- Support for Ansible 2.9 and ansible-base 2.10 is deprecated, and will be removed in the next major release (community.network 4.0.0) this spring. While most content will probably still work with ansible-base 2.10, we will remove symbolic links for modules and action plugins, which will make it impossible to use them with Ansible 2.9 anymore. Please use community.network 3.x.y with Ansible 2.9 and ansible-base 2.10, as these releases will continue to support Ansible 2.9 and ansible-base 2.10 even after they are End of Life (https://github.com/ansible-community/community-topics/issues/50, https://github.com/ansible-collections/community.network/pull/382).
-
-vmware.vmware_rest
-~~~~~~~~~~~~~~~~~~
-
- vcenter_vm_storage_policy_compliance - drop the module, it returns 404 error.
- vcenter_vm_tools - remove the ``upgrade`` state.
- vcenter_vm_tools_installer - remove the module from the collection.
-
-Porting Guide for v6.0.0a2
-==========================
-
 Known Issues
 ------------

+Ansible-core
+~~~~~~~~~~~~
+
+- get_url - document ``check_mode`` correctly with unreliable changed status (https://github.com/ansible/ansible/issues/65687).
+
 ansible.netcommon
 ~~~~~~~~~~~~~~~~~

@ -371,192 +273,6 @@ community.general
 dellemc.openmanage
 ~~~~~~~~~~~~~~~~~~

- idrac_user - Issue(192043) The module may error out with the message ``unable to perform the import or export operation because there are pending attribute changes or a configuration job is in progress``. Wait for the job to complete and run the task again.
- ome_application_alerts_smtp - Issue(212310) - The module does not provide a proper error message if the destination_address is more than 255 characters.
- ome_application_alerts_syslog - Issue(215374) - The module does not provide a proper error message if the destination_address is more than 255 characters.
- ome_application_console_preferences - Issue(224690) - The module does not display a proper error message when an unsupported value is provided for the parameters report_row_limit, email_sender_settings, and metric_collection_settings, and the value is applied on OpenManage Enterprise.
- ome_device_local_access_configuration - Issue(215035) - The module reports ``Successfully updated the local access setting`` if an unsupported value is provided for the parameter timeout_limit. However, this value is not actually applied on OpenManage Enterprise Modular.
- ome_device_local_access_configuration - Issue(217865) - The module does not display a proper error message if an unsupported value is provided for the user_defined and lcd_language parameters.
- ome_device_network_services - Issue(212681) - The module does not provide a proper error message if unsupported values are provided for the parameters- port_number, community_name, max_sessions, max_auth_retries, and idle_timeout.
- ome_device_power_settings - Issue(212679) - The module displays the following message if the value provided for the parameter ``power_cap`` is not within the supported range of 0 to 32767, ``Unable to complete the request because PowerCap does not exist or is not applicable for the resource URI.``
- ome_device_quick_deploy - Issue(216352) - The module does not display a proper error message if an unsupported value is provided for the ipv6_prefix_length and vlan_id parameters.
- ome_smart_fabric_uplink - Issue(186024) - The module does not allow the creation of multiple uplinks of the same name even though it is supported by OpenManage Enterprise Modular. If an uplink is created using the same name as an existing uplink, the existing uplink is modified.
-
-Breaking Changes
----------------
-
-ansible.netcommon
-~~~~~~~~~~~~~~~~~
-
- httpapi - Change default value of ``import_modules`` option from ``no`` to ``yes``
- netconf - Change default value of ``import_modules`` option from ``no`` to ``yes``
- network_cli - Change default value of ``import_modules`` option from ``no`` to ``yes``
-
-arista.eos
-~~~~~~~~~~
-
- httpapi - the ``eos_use_sessions`` option is now a boolean instead of an integer.
-
-community.general
-~~~~~~~~~~~~~~~~~
-
- Parts of this collection do not work with ansible-core 2.11 on Python 3.12+. Please either upgrade to ansible-core 2.12+, or use Python 3.11 or earlier (https://github.com/ansible-collections/community.general/pull/3988).
- The symbolic links used to implement flatmapping for all modules were removed and replaced by ``meta/runtime.yml`` redirects. This effectively breaks compatibility with Ansible 2.9 for all modules (without using their "long" names, which is discouraged and which can change without previous notice since they are considered an implementation detail) (https://github.com/ansible-collections/community.general/pull/4548).
- a_module test plugin - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
- archive - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
- git_config - remove Ansible 2.9 and early ansible-base 2.10 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
- java_keystore - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
- lists_mergeby filter plugin - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
- maven_artifact - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
- memcached cache plugin - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
- path_join filter plugin shim - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
- redis cache plugin - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
-
-Major Changes
-------------
-
-ansible.netcommon
-~~~~~~~~~~~~~~~~~
-
- cli_parse - this module has been moved to the ansible.utils collection. ``ansible.netcommon.cli_parse`` will continue to work to reference the module in its new location, but this redirect will be removed in a future release
- network_cli - Change default value of `ssh_type` option from `paramiko` to `auto`. This value will use libssh if the ansible-pylibssh module is installed, otherwise will fallback to paramiko.
-
-arista.eos
-~~~~~~~~~~
-
- Minimum required ansible.netcommon version is 2.5.1.
- Updated base plugin references to ansible.netcommon.
- `eos_facts` - change default gather_subset to `min` from `!config` (https://github.com/ansible-collections/arista.eos/issues/306).
-
-cisco.ios
-~~~~~~~~~
-
- Minimum required ansible.netcommon version is 2.5.1.
- Updated base plugin references to ansible.netcommon.
- `facts` - default value for `gather_subset` is changed to min instead of !config.
-
-cisco.iosxr
-~~~~~~~~~~~
-
- Minimum required ansible.netcommon version is 2.5.1.
- Updated base plugin references to ansible.netcommon.
- `facts` - default value for `gather_subset` is changed to min instead of !config.
-
-cisco.nxos
-~~~~~~~~~~
-
- The minimum required ansible.netcommon version has been bumped to v2.6.1.
- Updated base plugin references to ansible.netcommon.
- `nxos_facts` - change default gather_subset to `min` from `!config` (https://github.com/ansible-collections/cisco.nxos/issues/418).
- nxos_file_copy has been rewritten as a module. This change also removes the dependency on pexpect for file_pull operation. Since this now uses AnsibleModule class for argspec validation, the validation messages will be slighlty different. Expect changes in the return payload in some cases. All functionality remains unchanged.
-
-community.general
-~~~~~~~~~~~~~~~~~
-
- The community.general collection no longer supports Ansible 2.9 and ansible-base 2.10. While we take no active measures to prevent usage, we will remove a lot of compatibility code and other compatility measures that will effectively prevent using most content from this collection with Ansible 2.9, and some content of this collection with ansible-base 2.10. Both Ansible 2.9 and ansible-base 2.10 will very soon be End of Life and if you are still using them, you should consider upgrading to ansible-core 2.11 or later as soon as possible (https://github.com/ansible-collections/community.general/pull/4548).
-
-community.postgresql
-~~~~~~~~~~~~~~~~~~~~
-
- The community.postgresql collection no longer supports ``Ansible 2.9`` and ``ansible-base 2.10``. While we take no active measures to prevent usage and there are no plans to introduce incompatible code to the modules, we will stop testing against ``Ansible 2.9`` and ``ansible-base 2.10``. Both will very soon be End of Life and if you are still using them, you should consider upgrading to the ``latest Ansible / ansible-core 2.11 or later`` as soon as possible (https://github.com/ansible-collections/community.postgresql/pull/245).
-
-community.vmware
-~~~~~~~~~~~~~~~~
-
- Drop VCSIM as a test target (https://github.com/ansible-collections/community.vmware/pull/1294).
-
-ibm.qradar
-~~~~~~~~~~
-
- Minimum required ansible.netcommon version is 2.5.1.
- Updated base plugin references to ansible.netcommon.
-
-junipernetworks.junos
-~~~~~~~~~~~~~~~~~~~~~
-
- Minimum required ansible.netcommon version is 2.5.1.
- Updated base plugin references to ansible.netcommon.
- `junos_facts` - change default gather_subset to `min` from `!config`.
-
-splunk.es
-~~~~~~~~~
-
- Minimum required ansible.netcommon version is 2.5.1.
- Updated base plugin references to ansible.netcommon.
-
-vyos.vyos
-~~~~~~~~~
-
- Minimum required ansible.netcommon version is 2.5.1.
- Updated base plugin references to ansible.netcommon.
- `vyos_facts` - change default gather_subset to `min` from `!config` (https://github.com/ansible-collections/vyos.vyos/issues/231).
-
-Removed Collections
-------------------
-
- community.kubernetes (previously included version: 2.0.1)
- community.kubevirt (previously included version: 1.0.0)
-
-Removed Features
----------------
-
- The community.kubernetes collection has been removed from Ansible 6. It has been deprecated since Ansible 4.2, and version 2.0.0 included since Ansible 5 is only a set of deprecated redirects from community.kubernetes to kubernetes.core. If you still need the redirects, you can manually install community.kubernetes with ``ansible-galaxy collection install community.kubernetes`` (https://github.com/ansible-community/community-topics/issues/93).
- The community.kubevirt collection has been removed from Ansible 6. It has not been working with the community.kubernetes collection included since Ansible 5.0.0, and unfortunately nobody managed to adjust the collection to work with kubernetes.core >= 2.0.0. If you need to use this collection, you need to manually install community.kubernetes < 2.0.0 together with community.kubevirt with ``ansible-galaxy collection install community.kubevirt 'community.kubernetes:<2.0.0'`` (https://github.com/ansible-community/community-topics/issues/92).
-
-community.general
-~~~~~~~~~~~~~~~~~
-
- ali_instance_info - removed the options ``availability_zone``, ``instance_ids``, and ``instance_names``. Use filter item ``zone_id`` instead of ``availability_zone``, filter item ``instance_ids`` instead of ``instance_ids``, and filter item ``instance_name`` instead of ``instance_names`` (https://github.com/ansible-collections/community.general/pull/4516).
- apt_rpm - removed the deprecated alias ``update-cache`` of ``update_cache`` (https://github.com/ansible-collections/community.general/pull/4516).
- compose - removed various deprecated aliases. Use the version with ``_`` instead of ``-`` instead (https://github.com/ansible-collections/community.general/pull/4516).
- dnsimple - remove support for dnsimple < 2.0.0 (https://github.com/ansible-collections/community.general/pull/4516).
- github_deploy_key - removed the deprecated alias ``2fa_token`` of ``otp`` (https://github.com/ansible-collections/community.general/pull/4516).
- homebrew, homebrew_cask - removed the deprecated alias ``update-brew`` of ``update_brew`` (https://github.com/ansible-collections/community.general/pull/4516).
- linode - removed the ``backupsenabled`` option. Use ``backupweeklyday`` or ``backupwindow`` to enable backups (https://github.com/ansible-collections/community.general/pull/4516).
- opkg - removed the deprecated alias ``update-cache`` of ``update_cache`` (https://github.com/ansible-collections/community.general/pull/4516).
- pacman - if ``update_cache=true`` is used with ``name`` or ``upgrade``, the changed state will now also indicate if only the cache was updated. To keep the old behavior - only indicate ``changed`` when a package was installed/upgraded -, use ``changed_when`` as indicated in the module examples (https://github.com/ansible-collections/community.general/pull/4516).
- pacman - removed the deprecated alias ``update-cache`` of ``update_cache`` (https://github.com/ansible-collections/community.general/pull/4516).
- proxmox, proxmox_kvm, proxmox_snap - no longer allow to specify a VM name that matches multiple VMs. If this happens, the modules now fail (https://github.com/ansible-collections/community.general/pull/4516).
- serverless - removed the ``functions`` option. It was not used by the module (https://github.com/ansible-collections/community.general/pull/4516).
- slackpkg - removed the deprecated alias ``update-cache`` of ``update_cache`` (https://github.com/ansible-collections/community.general/pull/4516).
- urpmi - removed the deprecated alias ``no-recommends`` of ``no_recommends`` (https://github.com/ansible-collections/community.general/pull/4516).
- urpmi - removed the deprecated alias ``update-cache`` of ``update_cache`` (https://github.com/ansible-collections/community.general/pull/4516).
- xbps - removed the deprecated alias ``update-cache`` of ``update_cache`` (https://github.com/ansible-collections/community.general/pull/4516).
- xfconf - the ``get`` state has been removed. Use the ``xfconf_info`` module instead (https://github.com/ansible-collections/community.general/pull/4516).
-
-Deprecated Features
-------------------
-
-community.general
-~~~~~~~~~~~~~~~~~
-
- gem - the default of the ``norc`` option has been deprecated and will change to ``true`` in community.general 6.0.0. Explicitly specify a value to avoid a deprecation warning (https://github.com/ansible-collections/community.general/pull/4517).
- mail callback plugin - not specifying ``sender`` is deprecated and will be disallowed in community.general 6.0.0 (https://github.com/ansible-collections/community.general/pull/4140).
- module_helper module utils - deprecated the attribute ``ModuleHelper.VarDict`` (https://github.com/ansible-collections/community.general/pull/3801).
- nmcli - deprecate default hairpin mode for a bridge. This so we can change it to ``false`` in community.general 7.0.0, as this is also the default in ``nmcli`` (https://github.com/ansible-collections/community.general/pull/4334).
- pacman - from community.general 5.0.0 on, the ``changed`` status of ``update_cache`` will no longer be ignored if ``name`` or ``upgrade`` is specified. To keep the old behavior, add something like ``register: result`` and ``changed_when: result.packages | length > 0`` to your task (https://github.com/ansible-collections/community.general/pull/4329).
- proxmox inventory plugin - the current default ``true`` of the ``want_proxmox_nodes_ansible_host`` option has been deprecated. The default will change to ``false`` in community.general 6.0.0. To keep the current behavior, explicitly set ``want_proxmox_nodes_ansible_host`` to ``true`` in your inventory configuration. We suggest to already switch to the new behavior by explicitly setting it to ``false``, and by using ``compose:`` to set ``ansible_host`` to the correct value. See the examples in the plugin documentation for details (https://github.com/ansible-collections/community.general/pull/4466).
- vmadm - deprecated module parameter ``debug`` that was not used anywhere (https://github.com/ansible-collections/community.general/pull/4580).
-
-Porting Guide for v6.0.0a1
-==========================
-
-Added Collections
-----------------
-
- community.sap (version 1.0.0)
-
-Known Issues
------------
-
-Ansible-core
-~~~~~~~~~~~~
-
- get_url - document ``check_mode`` correctly with unreliable changed status (https://github.com/ansible/ansible/issues/65687).
-
-dellemc.openmanage
-~~~~~~~~~~~~~~~~~~
-
 - idrac_user - Issue(192043) The module may error out with the message ``unable to perform the import or export operation because there are pending attribute changes or a configuration job is in progress``. Wait for the job to complete and run the task again.
 - ome_application_alerts_smtp - Issue(212310) - The module does not provide a proper error message if the destination_address is more than 255 characters.
 - ome_application_alerts_syslog - Issue(215374) - The module does not provide a proper error message if the destination_address is more than 255 characters.
@ -604,10 +320,18 @@ amazon.aws
 - ec2_vpc_route_table_facts - Remove deprecated ``ec2_vpc_route_table_facts`` alias.  Please use ``ec2_vpc_route_table_info`` instead.
 - ec2_vpc_subnet_facts - Remove deprecated ``ec2_vpc_subnet_facts`` alias.  Please use ``ec2_vpc_subnet_info`` instead.

+ansible.netcommon
+~~~~~~~~~~~~~~~~~
+
+- httpapi - Change default value of ``import_modules`` option from ``no`` to ``yes``
+- netconf - Change default value of ``import_modules`` option from ``no`` to ``yes``
+- network_cli - Change default value of ``import_modules`` option from ``no`` to ``yes``
+
 arista.eos
 ~~~~~~~~~~

 - eos_command - new suboption ``version`` of parameter ``command``, which controls the JSON response version. Previously the value was assumed to be "latest" for network_cli and "1" for httpapi, but the default will now be "latest" for both connections. This option is also available for use in modules making their own device requests with ``plugins.module_utils.network.eos.eos.run_commands()`` with the same new default behavior. (https://github.com/ansible-collections/arista.eos/pull/258).
+- httpapi - the ``eos_use_sessions`` option is now a boolean instead of an integer.

 community.aws
 ~~~~~~~~~~~~~
@ -654,6 +378,23 @@ community.aws
 - redshift_facts -  Remove deprecated alias ``redshift_facts``.  Please use ``redshift_info`` instead.
 - route53_facts -  Remove deprecated alias ``route53_facts``.  Please use ``route53_info`` instead.

+community.general
+~~~~~~~~~~~~~~~~~
+
+- Parts of this collection do not work with ansible-core 2.11 on Python 3.12+. Please either upgrade to ansible-core 2.12+, or use Python 3.11 or earlier (https://github.com/ansible-collections/community.general/pull/3988).
+- The symbolic links used to implement flatmapping for all modules were removed and replaced by ``meta/runtime.yml`` redirects. This effectively breaks compatibility with Ansible 2.9 for all modules (without using their "long" names, which is discouraged and which can change without previous notice since they are considered an implementation detail) (https://github.com/ansible-collections/community.general/pull/4548).
+- a_module test plugin - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
+- archive - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
+- git_config - remove Ansible 2.9 and early ansible-base 2.10 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
+- java_keystore - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
+- lists_mergeby and groupby_as_dict filter plugins - adjust filter plugin filename. This change is not visible to end-users, it only affects possible other collections importing Python paths (https://github.com/ansible-collections/community.general/pull/4625).
+- lists_mergeby filter plugin - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
+- maven_artifact - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
+- memcached cache plugin - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
+- path_join filter plugin shim - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
+- redis cache plugin - remove Ansible 2.9 compatibility code (https://github.com/ansible-collections/community.general/pull/4548).
+- yarn - remove unsupported and unnecessary ``--no-emoji`` flag (https://github.com/ansible-collections/community.general/pull/4662).
+
 community.mysql
 ~~~~~~~~~~~~~~~

@ -688,6 +429,8 @@ theforeman.foreman
 Major Changes
 -------------

+- Add a ``ansible-community`` CLI tool that allows to print the version of the Ansible community distribution. Use ``ansible-community --version`` to print this version.
+
 Ansible-core
 ~~~~~~~~~~~~

@ -699,11 +442,44 @@ amazon.aws

 - amazon.aws collection - The amazon.aws collection has dropped support for ``botocore<1.19.0`` and ``boto3<1.16.0``. Most modules will continue to work with older versions of the AWS SDK, however compatability with older versions of the SDK is not guaranteed and will not be tested. When using older versions of the SDK a warning will be emitted by Ansible (https://github.com/ansible-collections/amazon.aws/pull/574).

+ansible.netcommon
+~~~~~~~~~~~~~~~~~
+
+- cli_parse - this module has been moved to the ansible.utils collection. ``ansible.netcommon.cli_parse`` will continue to work to reference the module in its new location, but this redirect will be removed in a future release
+- network_cli - Change default value of `ssh_type` option from `paramiko` to `auto`. This value will use libssh if the ansible-pylibssh module is installed, otherwise will fallback to paramiko.
+
+arista.eos
+~~~~~~~~~~
+
+- Minimum required ansible.netcommon version is 2.5.1.
+- Updated base plugin references to ansible.netcommon.
+- `eos_facts` - change default gather_subset to `min` from `!config` (https://github.com/ansible-collections/arista.eos/issues/306).
+
 chocolatey.chocolatey
 ~~~~~~~~~~~~~~~~~~~~~

 - win_chocolatey - Added choco_args option to pass additional arguments directly to Chocolatey.

+cisco.asa
+~~~~~~~~~
+
+- Minimum required ansible.netcommon version is 2.5.1.
+- Updated base plugin references to ansible.netcommon.
+
+cisco.ios
+~~~~~~~~~
+
+- Minimum required ansible.netcommon version is 2.5.1.
+- Updated base plugin references to ansible.netcommon.
+- `facts` - default value for `gather_subset` is changed to min instead of !config.
+
+cisco.iosxr
+~~~~~~~~~~~
+
+- Minimum required ansible.netcommon version is 2.5.1.
+- Updated base plugin references to ansible.netcommon.
+- `facts` - default value for `gather_subset` is changed to min instead of !config.
+
 cisco.ise
 ~~~~~~~~~

@ -760,20 +536,49 @@ cisco.meraki

 - meraki_mr_radio - New module

+cisco.nxos
+~~~~~~~~~~
+
+- The minimum required ansible.netcommon version has been bumped to v2.6.1.
+- Updated base plugin references to ansible.netcommon.
+- `nxos_facts` - change default gather_subset to `min` from `!config` (https://github.com/ansible-collections/cisco.nxos/issues/418).
+- nxos_file_copy has been rewritten as a module. This change also removes the dependency on pexpect for file_pull operation. Since this now uses AnsibleModule class for argspec validation, the validation messages will be slighlty different. Expect changes in the return payload in some cases. All functionality remains unchanged.
+
 community.aws
 ~~~~~~~~~~~~~

 - community.aws collection - The community.aws collection has dropped support for ``botocore<1.19.0`` and ``boto3<1.16.0``. Most modules will continue to work with older versions of the AWS SDK, however compatability with older versions of the SDK is not guaranteed and will not be tested. When using older versions of the SDK a warning will be emitted by Ansible (https://github.com/ansible-collections/community.aws/pull/809).
 - s3_bucket_notifications - refactor module to support SNS / SQS targets as well as the existing support for Lambda functions (https://github.com/ansible-collections/community.aws/issues/140).

+community.general
+~~~~~~~~~~~~~~~~~
+
+- The community.general collection no longer supports Ansible 2.9 and ansible-base 2.10. While we take no active measures to prevent usage, we will remove a lot of compatibility code and other compatility measures that will effectively prevent using most content from this collection with Ansible 2.9, and some content of this collection with ansible-base 2.10. Both Ansible 2.9 and ansible-base 2.10 will very soon be End of Life and if you are still using them, you should consider upgrading to ansible-core 2.11 or later as soon as possible (https://github.com/ansible-collections/community.general/pull/4548).
+
+community.mysql
+~~~~~~~~~~~~~~~
+
+- The community.mysql collection no longer supports ``Ansible 2.9`` and ``ansible-base 2.10``. While we take no active measures to prevent usage and there are no plans to introduce incompatible code to the modules, we will stop testing against ``Ansible 2.9`` and ``ansible-base 2.10``. Both will very soon be End of Life and if you are still using them, you should consider upgrading to the ``latest Ansible / ansible-core 2.11 or later`` as soon as possible (https://github.com/ansible-collections/community.mysql/pull/343).
+
+community.network
+~~~~~~~~~~~~~~~~~
+
+- The community.network collection no longer supports Ansible 2.9 and ansible-base 2.10. While we take no active measures to prevent usage, we will remove compatibility code and other compatility measures that will effectively prevent using most content from this collection with Ansible 2.9, and some content of this collection with ansible-base 2.10. Both Ansible 2.9 and ansible-base 2.10 will very soon be End of Life and if you are still using them, you should consider upgrading to ansible-core 2.11 or later as soon as possible (https://github.com/ansible-collections/community.network/pull/426).
+
 community.postgresql
 ~~~~~~~~~~~~~~~~~~~~

+- The community.postgresql collection no longer supports ``Ansible 2.9`` and ``ansible-base 2.10``. While we take no active measures to prevent usage and there are no plans to introduce incompatible code to the modules, we will stop testing against ``Ansible 2.9`` and ``ansible-base 2.10``. Both will very soon be End of Life and if you are still using them, you should consider upgrading to the ``latest Ansible / ansible-core 2.11 or later`` as soon as possible (https://github.com/ansible-collections/community.postgresql/pull/245).
 - postgresql_privs - the ``usage_on_types`` feature have been deprecated and will be removed in ``community.postgresql 3.0.0``. Please use the ``type`` option with the ``type`` value to explicitly grant/revoke privileges on types (https://github.com/ansible-collections/community.postgresql/issues/207).
 - postgresql_query - the ``path_to_script`` and ``as_single_query`` options as well as the ``query_list`` and ``query_all_results`` return values have been deprecated and will be removed in ``community.postgresql 3.0.0``. Please use the ``community.postgresql.postgresql_script`` module to execute statements from scripts (https://github.com/ansible-collections/community.postgresql/issues/189).
 - postgresql_query - the default value of the ``as_single_query`` option changes to ``yes``. If the related behavior of your tasks where the module is involved changes, please adjust the parameter's value correspondingly (https://github.com/ansible-collections/community.postgresql/issues/85).
 - postgresql_user - the ``priv`` argument has been deprecated and will be removed in ``community.postgresql 3.0.0``. Please use the ``postgresql_privs`` module to grant/revoke privileges instead (https://github.com/ansible-collections/community.postgresql/issues/212).

+community.vmware
+~~~~~~~~~~~~~~~~
+
+- Drop VCSIM as a test target (https://github.com/ansible-collections/community.vmware/pull/1294).
+
 containers.podman
 ~~~~~~~~~~~~~~~~~

@ -785,6 +590,7 @@ dellemc.openmanage

 - All modules can read custom or organizational CA signed certificate from the environment variables. Please refer to `SSL Certificate Validation <https://github.com/dell/dellemc-openmanage-ansible-modules#ssl-certificate-validation>`_ section in the `README.md <https://github.com/dell/dellemc-openmanage-ansible-modules/blob/collections/README.md#SSL-Certificate-Validation>`_ for modification to existing playbooks or setting environment variable.
 - All modules now support SSL over HTTPS and socket level timeout.
+- idrac_server_config_profile - The module is enhanced to support export, import, and preview the SCP configuration using Redfish and added support for check mode.

 f5networks.f5_modules
 ~~~~~~~~~~~~~~~~~~~~~
@ -792,19 +598,61 @@ f5networks.f5_modules
 - bigip_device_info - pagination logic has also been added to help with api stability.
 - bigip_device_info - the module no longer gathers information from all partitions on device. This change will stabalize the module by gathering resources only from the given partition and prevent the module from gathering way too much information that might result in crashing.

+fortinet.fortios
+~~~~~~~~~~~~~~~~
+
+- Support FortiOS 7.0.2, 7.0.3, 7.0.4, 7.0.5.
+
+frr.frr
+~~~~~~~
+
+- Minimum required ansible.netcommon version is 2.5.1.
+- Updated base plugin references to ansible.netcommon.
+
+ibm.qradar
+~~~~~~~~~~
+
+- Minimum required ansible.netcommon version is 2.5.1.
+- Updated base plugin references to ansible.netcommon.
+
+junipernetworks.junos
+~~~~~~~~~~~~~~~~~~~~~
+
+- Minimum required ansible.netcommon version is 2.5.1.
+- Updated base plugin references to ansible.netcommon.
+- `junos_facts` - change default gather_subset to `min` from `!config`.
+
 ovirt.ovirt
 ~~~~~~~~~~~

 - manageiq - role removed (https://github.com/oVirt/ovirt-ansible-collection/pull/375).

+splunk.es
+~~~~~~~~~
+
+- Minimum required ansible.netcommon version is 2.5.1.
+- Updated base plugin references to ansible.netcommon.
+
 vyos.vyos
 ~~~~~~~~~

 - Add 'pool' as value to server key in ntp_global.
+- Minimum required ansible.netcommon version is 2.5.1.
+- Updated base plugin references to ansible.netcommon.
+- `vyos_facts` - change default gather_subset to `min` from `!config` (https://github.com/ansible-collections/vyos.vyos/issues/231).
+
+Removed Collections
+-------------------
+
+- community.kubernetes (previously included version: 2.0.1)
+- community.kubevirt (previously included version: 1.0.0)

 Removed Features
 ----------------

+- The community.kubernetes collection has been removed from Ansible 6. It has been deprecated since Ansible 4.2, and version 2.0.0 included since Ansible 5 is only a set of deprecated redirects from community.kubernetes to kubernetes.core. If you still need the redirects, you can manually install community.kubernetes with ``ansible-galaxy collection install community.kubernetes`` (https://github.com/ansible-community/community-topics/issues/93).
+- The community.kubevirt collection has been removed from Ansible 6. It has not been working with the community.kubernetes collection included since Ansible 5.0.0, and unfortunately nobody managed to adjust the collection to work with kubernetes.core >= 2.0.0. If you need to use this collection, you need to manually install community.kubernetes < 2.0.0 together with community.kubevirt with ``ansible-galaxy collection install community.kubevirt 'community.kubernetes:<2.0.0'`` (https://github.com/ansible-community/community-topics/issues/92).
+
 Ansible-core
 ~~~~~~~~~~~~

@ -814,11 +662,51 @@ Ansible-core
 - psrp - Removed fallback on ``put_file`` with older ``pypsrp`` versions. Users must have at least ``pypsrp>=0.4.0``.
 - url_argument_spec - remove deprecated ``thirsty`` alias for ``get_url`` and ``uri`` modules (https://github.com/ansible/ansible/issues/75825, https://github.com/ansible/ansible/issues/75826)

+community.general
+~~~~~~~~~~~~~~~~~
+
+- ali_instance_info - removed the options ``availability_zone``, ``instance_ids``, and ``instance_names``. Use filter item ``zone_id`` instead of ``availability_zone``, filter item ``instance_ids`` instead of ``instance_ids``, and filter item ``instance_name`` instead of ``instance_names`` (https://github.com/ansible-collections/community.general/pull/4516).
+- apt_rpm - removed the deprecated alias ``update-cache`` of ``update_cache`` (https://github.com/ansible-collections/community.general/pull/4516).
+- compose - removed various deprecated aliases. Use the version with ``_`` instead of ``-`` instead (https://github.com/ansible-collections/community.general/pull/4516).
+- dnsimple - remove support for dnsimple < 2.0.0 (https://github.com/ansible-collections/community.general/pull/4516).
+- github_deploy_key - removed the deprecated alias ``2fa_token`` of ``otp`` (https://github.com/ansible-collections/community.general/pull/4516).
+- homebrew, homebrew_cask - removed the deprecated alias ``update-brew`` of ``update_brew`` (https://github.com/ansible-collections/community.general/pull/4516).
+- linode - removed the ``backupsenabled`` option. Use ``backupweeklyday`` or ``backupwindow`` to enable backups (https://github.com/ansible-collections/community.general/pull/4516).
+- opkg - removed the deprecated alias ``update-cache`` of ``update_cache`` (https://github.com/ansible-collections/community.general/pull/4516).
+- pacman - if ``update_cache=true`` is used with ``name`` or ``upgrade``, the changed state will now also indicate if only the cache was updated. To keep the old behavior - only indicate ``changed`` when a package was installed/upgraded -, use ``changed_when`` as indicated in the module examples (https://github.com/ansible-collections/community.general/pull/4516).
+- pacman - removed the deprecated alias ``update-cache`` of ``update_cache`` (https://github.com/ansible-collections/community.general/pull/4516).
+- proxmox, proxmox_kvm, proxmox_snap - no longer allow to specify a VM name that matches multiple VMs. If this happens, the modules now fail (https://github.com/ansible-collections/community.general/pull/4516).
+- serverless - removed the ``functions`` option. It was not used by the module (https://github.com/ansible-collections/community.general/pull/4516).
+- slackpkg - removed the deprecated alias ``update-cache`` of ``update_cache`` (https://github.com/ansible-collections/community.general/pull/4516).
+- urpmi - removed the deprecated alias ``no-recommends`` of ``no_recommends`` (https://github.com/ansible-collections/community.general/pull/4516).
+- urpmi - removed the deprecated alias ``update-cache`` of ``update_cache`` (https://github.com/ansible-collections/community.general/pull/4516).
+- xbps - removed the deprecated alias ``update-cache`` of ``update_cache`` (https://github.com/ansible-collections/community.general/pull/4516).
+- xfconf - the ``get`` state has been removed. Use the ``xfconf_info`` module instead (https://github.com/ansible-collections/community.general/pull/4516).
+
 community.hashi_vault
 ~~~~~~~~~~~~~~~~~~~~~

+- aws_iam auth - the deprecated alias ``aws_iam_login`` for the ``aws_iam`` value of the ``auth_method`` option has been removed (https://github.com/ansible-collections/community.hashi_vault/issues/194).
+- community.hashi_vault collection - support for Ansible 2.9 and ansible-base 2.10 has been removed (https://github.com/ansible-collections/community.hashi_vault/issues/189).
+- hashi_vault lookup - the deprecated ``[lookup_hashi_vault]`` INI config section has been removed in favor of the collection-wide ``[hashi_vault_collection]`` section (https://github.com/ansible-collections/community.hashi_vault/issues/179).
 - the "legacy" integration test setup has been removed; this does not affect end users and is only relevant to contributors (https://github.com/ansible-collections/community.hashi_vault/pull/191).

+community.network
+~~~~~~~~~~~~~~~~~
+
+- aireos modules - removed deprecated ``connection: local`` support. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
+- aireos modules - removed deprecated ``provider`` option. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
+- aruba modules - removed deprecated ``connection: local`` support. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
+- aruba modules - removed deprecated ``provider`` option. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
+- ce modules - removed deprecated ``connection: local`` support. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
+- ce modules - removed deprecated ``provider`` option. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
+- enos modules - removed deprecated ``connection: local`` support. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
+- enos modules - removed deprecated ``provider`` option. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
+- ironware modules - removed deprecated ``connection: local`` support. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
+- ironware modules - removed deprecated ``provider`` option. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
+- sros modules - removed deprecated ``connection: local`` support. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
+- sros modules - removed deprecated ``provider`` option. Use ``connection: network_cli`` instead (https://github.com/ansible-collections/community.network/pull/440).
+
 community.vmware
 ~~~~~~~~~~~~~~~~

@ -864,6 +752,8 @@ community.vmware
 Deprecated Features
 -------------------

+- The collection ``community.sap`` has been renamed to ``community.sap_libs``. For now both collections are included in Ansible. The content in ``community.sap`` will be replaced with deprecated redirects to the new collection in Ansible 7.0.0, and these redirects will eventually be removed from Ansible. Please update your FQCNs for ``community.sap``.
+
 Ansible-core
 ~~~~~~~~~~~~

@ -893,11 +783,39 @@ cisco.nxos
 - Deprecated nxos_snmp_traps module.
 - Deprecated nxos_snmp_user module.

+community.docker
+~~~~~~~~~~~~~~~~
+
+- Support for Ansible 2.9 and ansible-base 2.10 is deprecated, and will be removed in the next major release (community.docker 3.0.0). Some modules might still work with these versions afterwards, but we will no longer keep compatibility code that was needed to support them (https://github.com/ansible-collections/community.docker/pull/361).
+- The dependency on docker-compose for Execution Environments is deprecated and will be removed in community.docker 3.0.0. The `Python docker-compose library <https://pypi.org/project/docker-compose/>`__ is unmaintained and can cause dependency issues. You can manually still install it in an Execution Environment when needed (https://github.com/ansible-collections/community.docker/pull/373).
+- Various modules - the default of ``tls_hostname`` that was supposed to be removed in community.docker 2.0.0 will now be removed in version 3.0.0 (https://github.com/ansible-collections/community.docker/pull/362).
+- docker_stack - the return values ``out`` and ``err`` that were supposed to be removed in community.docker 2.0.0 will now be removed in version 3.0.0 (https://github.com/ansible-collections/community.docker/pull/362).
+
+community.general
+~~~~~~~~~~~~~~~~~
+
+- ansible_galaxy_install - deprecated support for ``ansible`` 2.9 and ``ansible-base`` 2.10 (https://github.com/ansible-collections/community.general/pull/4601).
+- dig lookup plugin - the ``DLV`` record type has been decommissioned in 2017 and support for it will be removed from community.general 6.0.0 (https://github.com/ansible-collections/community.general/pull/4618).
+- gem - the default of the ``norc`` option has been deprecated and will change to ``true`` in community.general 6.0.0. Explicitly specify a value to avoid a deprecation warning (https://github.com/ansible-collections/community.general/pull/4517).
+- mail callback plugin - not specifying ``sender`` is deprecated and will be disallowed in community.general 6.0.0 (https://github.com/ansible-collections/community.general/pull/4140).
+- module_helper module utils - deprecated the attribute ``ModuleHelper.VarDict`` (https://github.com/ansible-collections/community.general/pull/3801).
+- nmcli - deprecate default hairpin mode for a bridge. This so we can change it to ``false`` in community.general 7.0.0, as this is also the default in ``nmcli`` (https://github.com/ansible-collections/community.general/pull/4334).
+- pacman - from community.general 5.0.0 on, the ``changed`` status of ``update_cache`` will no longer be ignored if ``name`` or ``upgrade`` is specified. To keep the old behavior, add something like ``register: result`` and ``changed_when: result.packages | length > 0`` to your task (https://github.com/ansible-collections/community.general/pull/4329).
+- proxmox inventory plugin - the current default ``true`` of the ``want_proxmox_nodes_ansible_host`` option has been deprecated. The default will change to ``false`` in community.general 6.0.0. To keep the current behavior, explicitly set ``want_proxmox_nodes_ansible_host`` to ``true`` in your inventory configuration. We suggest to already switch to the new behavior by explicitly setting it to ``false``, and by using ``compose:`` to set ``ansible_host`` to the correct value. See the examples in the plugin documentation for details (https://github.com/ansible-collections/community.general/pull/4466).
+- vmadm - deprecated module parameter ``debug`` that was not used anywhere (https://github.com/ansible-collections/community.general/pull/4580).
+
 community.hashi_vault
 ~~~~~~~~~~~~~~~~~~~~~

 - Support for Ansible 2.9 and ansible-base 2.10 is deprecated, and will be removed in the next major release (community.hashi_vault 3.0.0) next spring (https://github.com/ansible-community/community-topics/issues/50, https://github.com/ansible-collections/community.hashi_vault/issues/189).
 - aws_iam_login auth method - the ``aws_iam_login`` method has been renamed to ``aws_iam``. The old name will be removed in collection version ``3.0.0``. Until then both names will work, and a warning will be displayed when using the old name (https://github.com/ansible-collections/community.hashi_vault/pull/193).
+- token_validate options - the shared auth option ``token_validate`` will change its default from ``True`` to ``False`` in community.hashi_vault version 4.0.0. The ``vault_login`` lookup and module will keep the default value of ``True`` (https://github.com/ansible-collections/community.hashi_vault/issues/248).
+- token_validate options - the shared auth option ``token_validate`` will change its default from ``true`` to ``false`` in community.hashi_vault version 4.0.0. The ``vault_login`` lookup and module will keep the default value of ``true`` (https://github.com/ansible-collections/community.hashi_vault/issues/248).
+
+community.network
+~~~~~~~~~~~~~~~~~
+
+- Support for Ansible 2.9 and ansible-base 2.10 is deprecated, and will be removed in the next major release (community.network 4.0.0) this spring. While most content will probably still work with ansible-base 2.10, we will remove symbolic links for modules and action plugins, which will make it impossible to use them with Ansible 2.9 anymore. Please use community.network 3.x.y with Ansible 2.9 and ansible-base 2.10, as these releases will continue to support Ansible 2.9 and ansible-base 2.10 even after they are End of Life (https://github.com/ansible-community/community-topics/issues/50, https://github.com/ansible-collections/community.network/pull/382).

 junipernetworks.junos
 ~~~~~~~~~~~~~~~~~~~~~
--- a/docs/docsite/rst/porting_guides/porting_guide_core_2.12.rst
+++ b/docs/docsite/rst/porting_guides/porting_guide_core_2.12.rst
@ -44,7 +44,7 @@ Playbook
 Python Interpreter Discovery
 ============================

-The default value of ``INTERPRETER_PYTHON_FALLBACK`` changed to ``auto``. The list of Python interpreters in ``INTERPRETER_PYTHON_FALLBACK`` changed to prefer Python 3 over Python 2. The combination of these two changes means the new default behavior is to quietly prefer Python 3 over Python 2 on remote hosts. Previously a deprecation warning was issued in situations where interpreter discovery would have used Python 3 but the interpreter was set to ``/usr/bin/python``.
+The default value of ``INTERPRETER_PYTHON`` changed to ``auto``. The list of Python interpreters in ``INTERPRETER_PYTHON_FALLBACK`` changed to prefer Python 3 over Python 2. The combination of these two changes means the new default behavior is to quietly prefer Python 3 over Python 2 on remote hosts. Previously a deprecation warning was issued in situations where interpreter discovery would have used Python 3 but the interpreter was set to ``/usr/bin/python``.

 ``INTERPRETER_PYTHON_FALLBACK`` can be changed from the default list of interpreters by setting the ``ansible_interpreter_python_fallback`` variable.

--- a/docs/docsite/rst/reference_appendices/faq.rst
+++ b/docs/docsite/rst/reference_appendices/faq.rst
@ -23,6 +23,15 @@ Where did this specific module go?

 IF you are searching for a specific module, you can check the `runtime.yml <https://github.com/ansible/ansible/blob/devel/lib/ansible/config/ansible_builtin_runtime.yml>`_ file, which lists the first destination for each module that we extracted from the main ansible/ansible repository. Some modules have moved again since then. You can also search on `Ansible Galaxy <https://galaxy.ansible.com/>`_ or ask on one of our :ref:`chat channels <communication_irc>`.

+.. _slow_install:
+
+How can I speed up Ansible on systems with slow disks?
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+Ansible may feel sluggish on systems with slow disks, such as Raspberry PI. See `Ansible might be running slow if libyaml is not available <https://www.jeffgeerling.com/blog/2021/ansible-might-be-running-slow-if-libyaml-not-available>`_ for hints on how to improve this.
+
+
+
 .. _set_environment:

 How can I set the PATH or any other environment variable for a task or entire play?
@ -709,15 +718,6 @@ To determine if a keyword requires ``{{ }}`` or even supports templating, use ``
 this will return documentation on the keyword including a ``template`` field with the values ``explicit`` (requires ``{{ }}``),
 ``implicit`` (assumes ``{{ }}``, so no needed) or ``static`` (no templating supported, all characters will be interpreted literally)

-.. _why_no_wheel:
-
-Why don't you ship ansible in wheel format (or other packaging format) ?
-++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-
-In most cases it has to do with maintainability. There are many ways to ship software and we do not have
-the resources to release Ansible on every platform.
-In some cases there are technical issues. For example, our dependencies are not present on Python Wheels.
-
 .. _ansible_host_delegated:

 How do I get the original ansible_host when I delegate a task?
@ -811,6 +811,31 @@ and backups, which most file based modules also support:
             path: "{{ updated['backup_file'] }}"
             state: absent

+.. _jinja2_faqs:
+
+Why does the ``regex_search`` filter return `None` instead of an empty string?
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+Until the jinja2 2.10 release, Jinja was only able to return strings, but Ansible needed Python objects in some cases. Ansible uses ``safe_eval`` and  only sends strings that look like certain types of Python objects through this function. With ``regex_search`` that does not find a match, the result (``None``) is converted to the string "None" which is not useful in non-native jinja2.
+
+The following example of a single templating action shows this behavior:
+
+.. code-block:: Jinja
+
+  {{ 'ansible' | regex_search('foobar') }}
+
+This example does not result in a Python ``None``, so Ansible historically converted it to "" (empty string).
+
+The native jinja2 functionality actually allows us to return full Python objects, that are always represented as Python objects everywhere, and as such the result of a single templating action with ``regex_search`` can result in the Python ``None``.
+
+.. note::
+
+  Native jinja2 functionality is not needed when ``regex_search`` is used as an intermediate result that is then compared to the jinja2 ``none`` test.
+
+  .. code-block:: Jinja
+
+     {{ 'ansible' | regex_search('foobar') is none }}
+

 .. _docs_contributions:

@ -820,6 +845,35 @@ How do I submit a change to the documentation?
 Documentation for Ansible is kept in the main project git repository, and complete instructions
 for contributing can be found in the docs README `viewable on GitHub <https://github.com/ansible/ansible/blob/devel/docs/docsite/README.md>`_. Thanks!

+
+.. _legacy_vs_builtin:
+
+What is the difference between ``ansible.legacy`` and ``ansible.builtin`` collections?
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+Neither is a real collection. They are virtually constructed by the core engine (synthetic collections).
+
+The ``ansible.builtin`` collection only refers to plugins that ship with ``ansible-core``.
+
+The ``ansible.legacy`` collection is a superset of  ``ansible.builtin`` (you can reference the plugins from builtin  through ``ansible.legacy``). You also get the ability to
+add 'custom' plugins in the :ref:`configured paths and adjacent directories <ansible_search_path>`, with the ability to override the builtin plugins that have the same name.
+
+Also, ``ansible.legacy`` is what you get by default when you do not specify an FQCN.
+So this:
+
+    .. code-block:: yaml
+
+        - shell: echo hi
+
+Is really equivalent to:
+
+    .. code-block:: yaml
+
+        - ansible.legacy.shell: echo hi
+
+Though, if you do not override the ``shell`` module, you can also just write it as ``ansible.builtin.shell``, since legacy will resolve to the builtin collection.
+
+
 .. _i_dont_see_my_question:

 I don't see my question here
--- a/Show More
+++ b/Show More