diff options
| author | Lee Garrett <lgarrett@rocketjump.eu> | 2022-03-06 17:56:03 +0100 |
|---|---|---|
| committer | Lee Garrett <lgarrett@rocketjump.eu> | 2022-03-06 17:56:03 +0100 |
| commit | 37d585600d2e2d1c64e33ffaaadce57e4c8407bd (patch) | |
| tree | 75af9ca60f59e065776d037d1b151eebbf3589bd | |
| parent | b1739f3e93dadd7d8fa794644ceedc24bddc8388 (diff) | |
| download | debian-ansible-core-37d585600d2e2d1c64e33ffaaadce57e4c8407bd.zip | |
New upstream version 2.12.3
214 files changed, 8594 insertions, 8619 deletions
@@ -1,6 +1,6 @@ Metadata-Version: 1.2 Name: ansible-core -Version: 2.12.0 +Version: 2.12.3 Summary: Radically simple IT automation Home-page: https://ansible.com/ Author: Ansible, Inc. diff --git a/SYMLINK_CACHE.json b/SYMLINK_CACHE.json index 0e287086..a9c81f15 100644 --- a/SYMLINK_CACHE.json +++ b/SYMLINK_CACHE.json @@ -1 +1 @@ -{"script": {"ansible": ["ansible-config", "ansible-console", "ansible-doc", "ansible-galaxy", "ansible-inventory", "ansible-playbook", "ansible-pull", "ansible-vault"]}, "library": {"../release.py": ["ansible/module_utils/ansible_release.py"], "../_util/target/common/constants.py": ["ansible_test/_internal/constants.py"], "main.py": ["ansible_test/_util/controller/sanity/validate-modules/validate-modules"]}}
\ No newline at end of file +{"script": {"ansible": ["ansible-config", "ansible-console", "ansible-doc", "ansible-galaxy", "ansible-inventory", "ansible-playbook", "ansible-pull", "ansible-vault"]}, "library": {"../release.py": ["ansible/module_utils/ansible_release.py"], "main.py": ["ansible_test/_util/controller/sanity/validate-modules/validate-modules"]}}
\ No newline at end of file diff --git a/changelogs/CHANGELOG-v2.12.rst b/changelogs/CHANGELOG-v2.12.rst index 4ec8923e..71250127 100644 --- a/changelogs/CHANGELOG-v2.12.rst +++ b/changelogs/CHANGELOG-v2.12.rst @@ -5,6 +5,120 @@ ansible-core 2.12 "Dazed and Confused" Release Notes .. contents:: Topics +v2.12.3 +======= + +Release Summary +--------------- + +| Release Date: 2022-02-28 +| `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__ + + +Minor Changes +------------- + +- The collection loader now reports a Python warning if an attempt is made to install the Ansible collection loader a second time. Previously this condition was reported using an Ansible warning. +- ansible-test - Installation of ``cryptography`` is no longer version constrained when ``openssl`` 1.1.0 or later is installed. +- ansible-test - Requirements for the plugin import test are now frozen. +- ansible-test - The ``pip`` and ``wheel`` packages are removed from all sanity test virtual environments after installation completes to reduce their size. Previously they were only removed from the environments used for the ``import`` sanity test. +- ansible-test - The hash for all managed sanity test virtual environments has changed. Containers that include ``ansible-test sanity --prime-venvs`` will need to be rebuilt to continue using primed virtual environments. +- ansible-test - Update ``pip`` used to bootstrap remote FreeBSD instances from version 20.3.4 to 21.3.1. +- ansible-test - Update the ``alpine`` container to version 3.3.0. This updates the base image from 3.14.2 to 3.15.0, which includes support for installing binary wheels using pip. +- ansible-test - Update the ``galaxy`` test plugin to get its container from a copy on quay.io. +- ansible-test - Update the ``openshift`` test plugin to get its container from a copy on quay.io. +- junit callback - Add support for replacing the directory portion of out-of-tree relative task paths with a placeholder. + +Bugfixes +-------- + +- ansible-test - All virtual environments managed by ansible-test are marked as usable after being bootstrapped, to avoid errors caused by use of incomplete environments. Previously this was only done for sanity tests. Existing environments from previous versions of ansible-test will be recreated on demand due to lacking the new marker. +- ansible-test - Fix the ``validate-modules`` sanity test to avoid double-loading the collection loader and possibly failing on import of the ``packaging`` module. +- ansible-test - Import ``yaml.cyaml.CParser`` instead of ``_yaml.CParser`` in the ``yamllint`` sanity test. +- ansible-test - Replace the directory portion of out-of-tree paths in JUnit files from integration tests with the ``out-of-tree:`` prefix. +- ansible-test - Sanity tests run with the ``--requirements` option for Python 2.x now install ``virtualenv`` when it is missing or too old. Previously it was only installed if missing. Version 16.7.12 is now installed instead of the latest version on Python 2.7. +- ansible-test - The ``import`` sanity test no longer reports errors about ``packaging`` being missing when testing collections. +- ansible-test - Update the ``default`` containers to version 4.2.0. +- ansible-test - Use https://ci-files.testing.ansible.com/ for instance bootstrapping instead of an S3 endpoint. +- ansible-test - Use relative paths in JUnit files generated during integration test runs. +- ansible-test - Virtual environments managed by ansible-test now use consistent versions of ``pip``, ``setuptools`` and ``wheel``. This avoids issues with virtual environments containing outdated or dysfunctional versions of these tools. The initial bootstrapping of ``pip`` is done by ansible-test from an HTTPS endpoint instead of creating the virtual environment with it already present. +- cleaning facts will now only warn about the variable name and not post the content, which can be undesireable to disclose +- correctly inherit vars from parent in block (https://github.com/ansible/ansible/issues/75286). +- gather_facts action now handles the move of base connection plugin types into collections to add/prevent subset argument correctly +- junit callback - Fix traceback during automatic fact gathering when using relative paths. +- junit callback - Fix unicode error when handling non-ASCII task paths. +- ssh connection now uses more correct host source as play_context can ignore loop/delegation variations. +- task_executor reverts the change to push facts into delegated vars on loop finalization as result managing code already handles this and was duplicating effort to wrong result. +- template lookup - restore inadvertently deleted default for ``convert_data`` (https://github.com/ansible/ansible/issues/77004) +- unarchive - Make extraction work when the LANGUAGE environment variable is set to a non-English locale. + +v2.12.2 +======= + +Release Summary +--------------- + +| Release Date: 2022-01-31 +| `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__ + + +Bugfixes +-------- + +- Fix ``AttributeError`` when providing password file via ``--connection-password-file`` (https://github.com/ansible/ansible/issues/76530) +- Fix ``end_play`` to end the current play only (https://github.com/ansible/ansible/issues/76672) +- Templating - Ensure we catch exceptions when getting ``.filters`` and ``.tests`` attributes on their respective plugins and properly error, instead of aborting which results in no filters being added to the jinja2 environment +- ``Templar.copy_with_new_env`` - set the ``finalize`` method of the new ``Templar`` object for the new environment (https://github.com/ansible/ansible/issues/76379) +- ansible-config avoid showing _terms and _input when --only-changed. +- ansible-galaxy - Fix using the '--ignore-certs' option when there is no server-specific configuration for the Galaxy server. +- ansible-galaxy collection build - Ignore any existing ``MANIFEST.json`` and ``FILES.json`` in the root directory when building a collection. +- ansible-test - Fix the ``import`` sanity test to work properly when Ansible's built-in vendoring support is in use. +- ansible-test - Fix traceback in the ``validate-modules`` sanity test when testing an Ansible module without any callables. +- ansible-test - Fix traceback when running from an install and delegating execution to a different Python interpreter. +- ansible-test - Show an error message instead of a traceback when running outside of a supported directory. +- ansible-test - Update help links to reference ``ansible-core`` instead of ``ansible``. +- ansible-test - Update unit tests to use the ``--forked`` option instead of the deprecated ``--boxed`` option. +- async - Improve performance of sending async callback events by never sending the full task through the queue (https://github.com/ansible/ansible/issues/76729) +- default callback - Ensure we compare FQCN also in lockstep logic, to ensure using the FQCN of a strategy plugin triggers the correct behavior in the default callback plugin. (https://github.com/ansible/ansible/issues/76782) +- hostname - Do not require SystemdStrategy subclasses for every distro (https://github.com/ansible/ansible/issues/76792) +- include_vars, properly initialize variable as there is corner case in which it can end up referenced and not defined +- ssh connection - properly quote controlpersist path given by user to avoid issues with spaces and other characters +- ssh connection avoid parsing ssh cli debug lines as they can match expected output at high verbosities. +- sudo become plugin, fix handling of non interactive flags, previous substitution was too naive +- unarchive - Fix zip archive file listing that caused issues with content postprocessing (https://github.com/ansible/ansible/issues/76067). +- yum - prevent storing unnecessary cache data by running `yum makecache fast` (https://github.com/ansible/ansible/issues/76336) + +v2.12.1 +======= + +Release Summary +--------------- + +| Release Date: 2021-12-06 +| `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__ + + +Minor Changes +------------- + +- jinja2_native - keep same behavior on Python 3.10. + +Bugfixes +-------- + +- Ansible.ModuleUtils.LinkUtil - Ignore the ``LIB`` environment variable when loading the ``LinkUtil`` code +- ansible-test - Automatic target requirements installation is now based on the target environment instead of the controller environment. +- ansible-test - Fix Python real prefix detection when running in a ``venv`` virtual environment. +- ansible-test - Fix installation and usage of ``pyyaml`` requirement for the ``import`` sanity test for collections. +- ansible-test - Fix traceback in ``import`` sanity test on Python 2.7 when ``pip`` is not available. +- ansible-test - Relocate constants to eliminate symlink. +- ansible-test - Target integration test requirements are now correctly installed for target environments running on the controller. +- ansible-test - Update the ``default`` containers to version 4.1.1, which includes the updated ``import`` sanity test requirements. +- ansible-test - Use the legacy collection loader for ``import`` sanity tests on target-only Python versions. +- set_fact/include_vars correctly handle delegation assignments within loops +- setup - detect docker container with check for ./dockerenv or ./dockinit (https://github.com/ansible/ansible/pull/74349). +- validate_argument_spec - Skip suboption validation if the top level option is an invalid type (https://github.com/ansible/ansible/issues/75612). + v2.12.0 ======= diff --git a/changelogs/changelog.yaml b/changelogs/changelog.yaml index 7e14bc45..16b9241e 100644 --- a/changelogs/changelog.yaml +++ b/changelogs/changelog.yaml @@ -1083,3 +1083,264 @@ releases: fragments: - v2.12.0rc1_summary.yaml release_date: '2021-10-18' + 2.12.1: + changes: + release_summary: '| Release Date: 2021-12-06 + + | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__ + + ' + codename: Dazed and Confused + fragments: + - v2.12.1_summary.yaml + release_date: '2021-12-06' + 2.12.1rc1: + changes: + bugfixes: + - Ansible.ModuleUtils.LinkUtil - Ignore the ``LIB`` environment variable when + loading the ``LinkUtil`` code + - ansible-test - Automatic target requirements installation is now based on + the target environment instead of the controller environment. + - ansible-test - Fix Python real prefix detection when running in a ``venv`` + virtual environment. + - ansible-test - Fix installation and usage of ``pyyaml`` requirement for the + ``import`` sanity test for collections. + - ansible-test - Fix traceback in ``import`` sanity test on Python 2.7 when + ``pip`` is not available. + - ansible-test - Relocate constants to eliminate symlink. + - ansible-test - Target integration test requirements are now correctly installed + for target environments running on the controller. + - ansible-test - Update the ``default`` containers to version 4.1.1, which includes + the updated ``import`` sanity test requirements. + - ansible-test - Use the legacy collection loader for ``import`` sanity tests + on target-only Python versions. + - set_fact/include_vars correctly handle delegation assignments within loops + - setup - detect docker container with check for ./dockerenv or ./dockinit (https://github.com/ansible/ansible/pull/74349). + - validate_argument_spec - Skip suboption validation if the top level option + is an invalid type (https://github.com/ansible/ansible/issues/75612). + minor_changes: + - jinja2_native - keep same behavior on Python 3.10. + release_summary: '| Release Date: 2021-11-29 + + | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__ + + ' + codename: Dazed and Confused + fragments: + - 74349-improve-docker-detection.yml + - 75635-fix-role-argspec-suboption-validation.yml + - ansible-test-default-containers-4.1.1.yml + - ansible-test-relocate-constants.yaml + - ansible-test-requirements-target.yaml + - ansible-test-sanity-import-loader.yml + - ansible-test-sanity-import-no-pip.yml + - ansible-test-sanity-import.yml + - ansible-test-venv-real-prefix.yaml + - jinja2_native-literal_eval-py310.yml + - set_fact_delegation.yml + - v2.12.1rc1_summary.yaml + - win_LinkUtil-ignore-LIB.yml + release_date: '2021-11-29' + 2.12.2: + changes: + bugfixes: + - ansible-test - Show an error message instead of a traceback when running outside + of a supported directory. + release_summary: '| Release Date: 2022-01-31 + + | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__ + + ' + codename: Dazed and Confused + fragments: + - ansible-test-unsupported-directory-traceback.yaml + - v2.12.2_summary.yaml + release_date: '2022-01-31' + 2.12.2rc1: + changes: + bugfixes: + - Fix ``AttributeError`` when providing password file via ``--connection-password-file`` + (https://github.com/ansible/ansible/issues/76530) + - Fix ``end_play`` to end the current play only (https://github.com/ansible/ansible/issues/76672) + - Templating - Ensure we catch exceptions when getting ``.filters`` and ``.tests`` + attributes on their respective plugins and properly error, instead of aborting + which results in no filters being added to the jinja2 environment + - '``Templar.copy_with_new_env`` - set the ``finalize`` method of the new ``Templar`` + object for the new environment (https://github.com/ansible/ansible/issues/76379)' + - ansible-config avoid showing _terms and _input when --only-changed. + - ansible-galaxy - Fix using the '--ignore-certs' option when there is no server-specific + configuration for the Galaxy server. + - ansible-galaxy collection build - Ignore any existing ``MANIFEST.json`` and + ``FILES.json`` in the root directory when building a collection. + - ansible-test - Fix the ``import`` sanity test to work properly when Ansible's + built-in vendoring support is in use. + - ansible-test - Fix traceback in the ``validate-modules`` sanity test when + testing an Ansible module without any callables. + - ansible-test - Fix traceback when running from an install and delegating execution + to a different Python interpreter. + - ansible-test - Update help links to reference ``ansible-core`` instead of + ``ansible``. + - ansible-test - Update unit tests to use the ``--forked`` option instead of + the deprecated ``--boxed`` option. + - async - Improve performance of sending async callback events by never sending + the full task through the queue (https://github.com/ansible/ansible/issues/76729) + - default callback - Ensure we compare FQCN also in lockstep logic, to ensure + using the FQCN of a strategy plugin triggers the correct behavior in the default + callback plugin. (https://github.com/ansible/ansible/issues/76782) + - hostname - Do not require SystemdStrategy subclasses for every distro (https://github.com/ansible/ansible/issues/76792) + - include_vars, properly initialize variable as there is corner case in which + it can end up referenced and not defined + - ssh connection - properly quote controlpersist path given by user to avoid + issues with spaces and other characters + - ssh connection avoid parsing ssh cli debug lines as they can match expected + output at high verbosities. + - sudo become plugin, fix handling of non interactive flags, previous substitution + was too naive + - unarchive - Fix zip archive file listing that caused issues with content postprocessing + (https://github.com/ansible/ansible/issues/76067). + - yum - prevent storing unnecessary cache data by running `yum makecache fast` + (https://github.com/ansible/ansible/issues/76336) + release_summary: '| Release Date: 2022-01-24 + + | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__ + + ' + codename: Dazed and Confused + fragments: + - 74127-bad-filter-2.yml + - 76069-fix-unarchive-file-listing-in-zip.yaml + - 76336-yum-makecache-fast.yml + - 76379-set-finalize-on-new-env.yml + - 76530-connection-password-file-tb-fix.yml + - 76672-fix-end_play-multiple_plays.yml + - 76729-async-callback-perf.yml + - 76735-ansible-galaxy-fix-ignore-certs.yaml + - 76782-fqcn-compare-lockstep-strategies.yml + - 76792-hostname-all-systemd.yml + - ansible-test-delegation-pythonpath.yml + - ansible-test-links.yml + - ansible-test-pytest-forked.yml + - ansible-test-sanity-vendoring.yml + - ansible-test-validate-modules-no-callable.yml + - config_fix_terms.yml + - fix_sudo_flag_mangling.yml + - galaxy-build-files-ignore.yml + - include_vars_failed.yml + - ssh_debug_noparse.yml + - ssh_quote_cp.yml + - v2.12.2rc1_summary.yaml + release_date: '2022-01-24' + 2.12.3: + changes: + release_summary: '| Release Date: 2022-02-28 + + | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__ + + ' + codename: Dazed and Confused + fragments: + - v2.12.3_summary.yaml + release_date: '2022-02-28' + 2.12.3rc1: + changes: + bugfixes: + - ansible-test - All virtual environments managed by ansible-test are marked + as usable after being bootstrapped, to avoid errors caused by use of incomplete + environments. Previously this was only done for sanity tests. Existing environments + from previous versions of ansible-test will be recreated on demand due to + lacking the new marker. + - ansible-test - Fix the ``validate-modules`` sanity test to avoid double-loading + the collection loader and possibly failing on import of the ``packaging`` + module. + - ansible-test - Import ``yaml.cyaml.CParser`` instead of ``_yaml.CParser`` + in the ``yamllint`` sanity test. + - ansible-test - Replace the directory portion of out-of-tree paths in JUnit + files from integration tests with the ``out-of-tree:`` prefix. + - ansible-test - Sanity tests run with the ``--requirements` option for Python + 2.x now install ``virtualenv`` when it is missing or too old. Previously it + was only installed if missing. Version 16.7.12 is now installed instead of + the latest version on Python 2.7. + - ansible-test - The ``import`` sanity test no longer reports errors about ``packaging`` + being missing when testing collections. + - ansible-test - Update the ``default`` containers to version 4.2.0. + - ansible-test - Use https://ci-files.testing.ansible.com/ for instance bootstrapping + instead of an S3 endpoint. + - ansible-test - Use relative paths in JUnit files generated during integration + test runs. + - ansible-test - Virtual environments managed by ansible-test now use consistent + versions of ``pip``, ``setuptools`` and ``wheel``. This avoids issues with + virtual environments containing outdated or dysfunctional versions of these + tools. The initial bootstrapping of ``pip`` is done by ansible-test from an + HTTPS endpoint instead of creating the virtual environment with it already + present. + - cleaning facts will now only warn about the variable name and not post the + content, which can be undesireable to disclose + - correctly inherit vars from parent in block (https://github.com/ansible/ansible/issues/75286). + - gather_facts action now handles the move of base connection plugin types into + collections to add/prevent subset argument correctly + - junit callback - Fix traceback during automatic fact gathering when using + relative paths. + - junit callback - Fix unicode error when handling non-ASCII task paths. + - ssh connection now uses more correct host source as play_context can ignore + loop/delegation variations. + - task_executor reverts the change to push facts into delegated vars on loop + finalization as result managing code already handles this and was duplicating + effort to wrong result. + - template lookup - restore inadvertently deleted default for ``convert_data`` + (https://github.com/ansible/ansible/issues/77004) + - unarchive - Make extraction work when the LANGUAGE environment variable is + set to a non-English locale. + minor_changes: + - The collection loader now reports a Python warning if an attempt is made to + install the Ansible collection loader a second time. Previously this condition + was reported using an Ansible warning. + - ansible-test - Installation of ``cryptography`` is no longer version constrained + when ``openssl`` 1.1.0 or later is installed. + - ansible-test - Requirements for the plugin import test are now frozen. + - ansible-test - The ``pip`` and ``wheel`` packages are removed from all sanity + test virtual environments after installation completes to reduce their size. + Previously they were only removed from the environments used for the ``import`` + sanity test. + - ansible-test - The hash for all managed sanity test virtual environments has + changed. Containers that include ``ansible-test sanity --prime-venvs`` will + need to be rebuilt to continue using primed virtual environments. + - ansible-test - Update ``pip`` used to bootstrap remote FreeBSD instances from + version 20.3.4 to 21.3.1. + - ansible-test - Update the ``alpine`` container to version 3.3.0. This updates + the base image from 3.14.2 to 3.15.0, which includes support for installing + binary wheels using pip. + - ansible-test - Update the ``galaxy`` test plugin to get its container from + a copy on quay.io. + - ansible-test - Update the ``openshift`` test plugin to get its container from + a copy on quay.io. + - junit callback - Add support for replacing the directory portion of out-of-tree + relative task paths with a placeholder. + release_summary: '| Release Date: 2022-02-23 + + | `Porting Guide <https://docs.ansible.com/ansible/devel/porting_guides.html>`__ + + ' + codename: Dazed and Confused + fragments: + - 76542-fix-unarchive-on-nenglish-locales.yml + - 77004-restore-missing-default.yml + - ansible-test-alpine3-update.yaml + - ansible-test-bootstrap-pip.yml + - ansible-test-ci-files.yaml + - ansible-test-container-images.yml + - ansible-test-default-containers-4.2.0.yml + - ansible-test-import-collections.yml + - ansible-test-junit-relative-paths.yml + - ansible-test-managed-venv.yml + - ansible-test-pyopenssl.yaml + - ansible-test-sanity-requirements-update.yml + - ansible-test-validate-modules-collection-loader.yml + - ansible-test-yaml-import.yaml + - clean_facts_values.yml + - fix_block_var_inh.yml + - fix_fax_delegation_loops.yml + - gather_facts_collections.yml + - junit-callback-task-path-unicode.yml + - ssh_use_right_host.yml + - v2.12.3rc1_summary.yaml + release_date: '2022-02-23' diff --git a/docs/docsite/ansible_4.inv b/docs/docsite/ansible_4.inv Binary files differindex 6a2a46c7..11f3b195 100644 --- a/docs/docsite/ansible_4.inv +++ b/docs/docsite/ansible_4.inv diff --git a/docs/docsite/ansible_5.inv b/docs/docsite/ansible_5.inv Binary files differnew file mode 100644 index 00000000..f10685b6 --- /dev/null +++ b/docs/docsite/ansible_5.inv diff --git a/docs/docsite/python3.inv b/docs/docsite/python3.inv Binary files differindex e1db2aba..85c4a3f3 100644 --- a/docs/docsite/python3.inv +++ b/docs/docsite/python3.inv diff --git a/docs/docsite/rst/dev_guide/developing_collections_distributing.rst b/docs/docsite/rst/dev_guide/developing_collections_distributing.rst index 1fa1e158..d0406680 100644 --- a/docs/docsite/rst/dev_guide/developing_collections_distributing.rst +++ b/docs/docsite/rst/dev_guide/developing_collections_distributing.rst @@ -54,7 +54,7 @@ You can create additional namespaces on Ansible Galaxy if you choose. For Red Ha * To create a namespace on Galaxy, see `Galaxy namespaces <https://galaxy.ansible.com/docs/contributing/namespaces.html#galaxy-namespaces>`_ on the Galaxy docsite for details. * To create a namespace on Red Hat Automation Hub, see the `Ansible Certified Content FAQ <https://access.redhat.com/articles/4916901>`_. -Specify the namespace in the :file:`galaxy.yaml` file for each collection. For more information on the :file:`galaxy.yaml` file, see :ref:`collections_galaxy_meta`. +Specify the namespace in the :file:`galaxy.yml` file for each collection. For more information on the :file:`galaxy.yml` file, see :ref:`collections_galaxy_meta`. .. _galaxy_get_token: @@ -124,7 +124,7 @@ Building your collection tarball After configuring one or more distribution servers, build a collection tarball. The collection tarball is the published artifact, the object that you upload and other users download to install your collection. To build a collection tarball: -#. Review the version number in your :file:`galaxy.yaml` file. Each time you publish your collection, it must have a new version number. You cannot make changes to existing versions of your collection on a distribution server. If you try to upload the same collection version more than once, the distribution server returns the error ``Code: conflict.collection_exists``. Collections follow semantic versioning rules. For more information on versions, see :ref:`collection_versions`. For more information on the :file:`galaxy.yaml` file, see :ref:`collections_galaxy_meta`. +#. Review the version number in your :file:`galaxy.yml` file. Each time you publish your collection, it must have a new version number. You cannot make changes to existing versions of your collection on a distribution server. If you try to upload the same collection version more than once, the distribution server returns the error ``Code: conflict.collection_exists``. Collections follow semantic versioning rules. For more information on versions, see :ref:`collection_versions`. For more information on the :file:`galaxy.yml` file, see :ref:`collections_galaxy_meta`. #. Run ``ansible-galaxy collection build`` from inside the top-level directory of the collection. For example: .. code-block:: bash diff --git a/docs/docsite/rst/dev_guide/developing_modules_documenting.rst b/docs/docsite/rst/dev_guide/developing_modules_documenting.rst index 2932e4f8..f620d352 100644 --- a/docs/docsite/rst/dev_guide/developing_modules_documenting.rst +++ b/docs/docsite/rst/dev_guide/developing_modules_documenting.rst @@ -244,6 +244,8 @@ You can link from your module documentation to other module docs, other resource * ``L()`` for links with a heading. For example: ``See L(Ansible Automation Platform,https://www.ansible.com/products/automation-platform).`` As of Ansible 2.10, do not use ``L()`` for relative links between Ansible documentation and collection documentation. * ``U()`` for URLs. For example: ``See U(https://www.ansible.com/products/automation-platform) for an overview.`` +* ``R()`` for cross-references with a heading (added in Ansible 2.10). For example: ``See R(Cisco IOS Platform Guide,ios_platform_options)``. Use the RST anchor for the cross-reference. See :ref:`adding_anchors_rst` for details. +* ``M()`` for module names. For example: ``See also M(ansible.builtin.yum) or M(community.general.apt_rpm)``. There are also some macros which do not create links but we use them to display certain types of content in a uniform way: @@ -256,12 +258,17 @@ content in a uniform way: .. note:: - For links between modules and documentation within a collection, you can use either of the options above. Use ``U()`` or ``L()`` with full URLs (not relative links). + Cross-references with ``R()`` currently **do not work** inside option and return value documentations. They do work however in the global description, notes, and ``seealso`` descriptions. .. note:: - - When a collection is not the right granularity, use ``C(..)``: - - ``The C(win_*) modules (spread across several collections) allow you to manage various aspects of windows hosts.`` + For links between modules and documentation within a collection, you can use any of the options above. For links outside of your collection, use ``R()`` if available. Otherwise, use ``U()`` or ``L()`` with full URLs (not relative links). For modules, use ``M()`` with the FQCN or ``ansible.builtin`` as shown in the example. If you are creating your own documentation site, you will need to use the `intersphinx extension <https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html>`_ to convert ``R()`` and ``M()`` to the correct links. + +.. note:: + To refer to a group of modules in a collection, use ``R()``. When a collection is not the right granularity, use ``C(..)``: + + - ``Refer to the R(kubernetes.core collection, plugins_in_kubernetes.core) for information on managing kubernetes clusters.`` + - ``The C(win_*) modules (spread across several collections) allow you to manage various aspects of windows hosts.`` .. note:: diff --git a/docs/docsite/rst/galaxy/user_guide.rst b/docs/docsite/rst/galaxy/user_guide.rst index 6c8c0ef2..0a22b165 100644 --- a/docs/docsite/rst/galaxy/user_guide.rst +++ b/docs/docsite/rst/galaxy/user_guide.rst @@ -83,6 +83,11 @@ Downloading a collection for offline use .. include:: ../shared_snippets/download_tarball_collections.txt +Installing a collection from source files +----------------------------------------- + +.. include:: ../shared_snippets/installing_collections_file.rst + Installing a collection from a git repository --------------------------------------------- diff --git a/docs/docsite/rst/locales/ja/LC_MESSAGES/community.po b/docs/docsite/rst/locales/ja/LC_MESSAGES/community.po index b7cbf020..85a77e1e 100644 --- a/docs/docsite/rst/locales/ja/LC_MESSAGES/community.po +++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/community.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Ansible devel\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-10-05 13:53+0200\n" +"POT-Creation-Date: 2021-11-09 14:07+0100\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" @@ -515,190 +515,190 @@ msgid "bridging from Matrix" msgstr "Matrixã‹ã‚‰ã®ãƒ–リッジ" #: ../../rst/community/communication.rst:74 -msgid "Our IRC channels may require you to register your IRC nickname. If you receive an error when you connect or when posting a message, see `libera.chat's Nickname Registration guide <https://libera.chat/guides/registration>`_ for instructions. To find all ``ansible`` specific channels on the libera.chat network, use the following command in your IRC client::" +msgid "Our IRC channels may require you to register your IRC nickname. If you receive an error when you connect or when posting a message, see `libera.chat's Nickname Registration guide <https://libera.chat/guides/registration>`_ for instructions. To find all ``ansible`` specific channels on the libera.chat network, use the following command in your IRC client:" msgstr "ã“ã® IRC ãƒãƒ£ãƒ³ãƒãƒ«ã§ã¯ã€IRCã®ãƒ‹ãƒƒã‚¯ãƒãƒ¼ãƒ ã®ç™»éŒ²ãŒå¿…è¦ã«ãªã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚接続時ã¾ãŸã¯ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã®æŠ•ç¨¿æ™‚ã«ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã™ã‚‹å ´åˆã¯ã€ã€Œ`libera.chat's Nickname Registration guide <https://libera.chat/guides/registration>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。libera.chatãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã®``ansible``固有ã®ãƒãƒ£ãƒãƒ«ã‚’ã™ã¹ã¦ã‚’見ã¤ã‘ã‚‹ã«ã¯ã€IRCクライアントã§æ¬¡ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/community/communication.rst:78 +#: ../../rst/community/communication.rst:80 msgid "as described in the `libera.chat docs <https://libera.chat/guides/findingchannels>`_." msgstr "`libera.chat ドã‚ュメント <https://libera.chat/guides/findingchannels>`_ ã«è¨˜è¼‰ã®ã¨ãŠã‚Šã€‚" -#: ../../rst/community/communication.rst:81 +#: ../../rst/community/communication.rst:83 msgid "General channels" msgstr "一般的ãªãƒãƒ£ãƒ³ãƒãƒ«" -#: ../../rst/community/communication.rst:83 +#: ../../rst/community/communication.rst:85 msgid "The clickable links will take you directly to the relevant Matrix room in your browser; room/channel information is also given for use in other clients:" msgstr "クリックå¯èƒ½ãªãƒªãƒ³ã‚¯ã‚’クリックã™ã‚‹ã¨ã€ãƒ–ラウザã§é–¢é€£ã™ã‚‹Matrixルームã«ç›´æŽ¥ç§»å‹•ã—ã¾ã™ã€‚ãƒãƒ£ãƒƒãƒˆãƒ«ãƒ¼ãƒ /ãƒãƒ£ãƒ³ãƒãƒ«æƒ…å ±ã¯ã€ä»–ã®ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã§ä½¿ç”¨ã™ã‚‹ãŸã‚ã«ã‚‚æä¾›ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/community/communication.rst:85 +#: ../../rst/community/communication.rst:87 msgid "`General usage and support questions <https://matrix.to:/#/#users:ansible.im>`_ - ``Matrix: #users:ansible.im | IRC: #ansible``" msgstr "`General usage and support questions <https://matrix.to:/#/#users:ansible.im>`_ - ``Matrix: #users:ansible.im | IRC: #ansible``" -#: ../../rst/community/communication.rst:86 +#: ../../rst/community/communication.rst:88 msgid "`Discussions on developer topics and code related to features or bugs <https://matrix.to/#/#devel:ansible.im>`_ - ``Matrix: #devel:ansible.im | IRC: #ansible-devel``" msgstr "`Discussions on developer topics and code related to features or bugs <https://matrix.to/#/#devel:ansible.im>`_ - ``Matrix: #devel:ansible.im | IRC: #ansible-devel``" -#: ../../rst/community/communication.rst:87 +#: ../../rst/community/communication.rst:89 msgid "`Discussions on community and collections related topics <https://matrix.to:/#/#community:ansible.im>`_ - ``Matrix: #community:ansible.im | IRC: #ansible-community``" msgstr "`Discussions on community and collections related topics <https://matrix.to:/#/#community:ansible.im>`_ - ``Matrix: #community:ansible.im | IRC: #ansible-community``" -#: ../../rst/community/communication.rst:89 +#: ../../rst/community/communication.rst:91 msgid "`For public community meetings <https://matrix.to/#/#meeting:ansible.im>`_ - ``Matrix: #meeting:ansible.im | IRC: #ansible-meeting``" msgstr "`For public community meetings <https://matrix.to/#/#meeting:ansible.im>`_ - ``Matrix: #meeting:ansible.im | IRC: #ansible-meeting``" -#: ../../rst/community/communication.rst:89 +#: ../../rst/community/communication.rst:91 msgid "We will generally announce these on one or more of the above mailing lists. See the `meeting schedule and agenda page <https://github.com/ansible/community/blob/master/meetings/README.md>`_" msgstr "通常ã¯ã€ä¸Šè¨˜ã®ãƒ¡ãƒ¼ãƒªãƒ³ã‚°ãƒªã‚¹ãƒˆã§å‘ŠçŸ¥ã•ã‚Œã¾ã™ã€‚「`meeting schedule and agenda page <https://github.com/ansible/community/blob/master/meetings/README.md>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/community/communication.rst:94 +#: ../../rst/community/communication.rst:96 msgid "Working groups" msgstr "ワーã‚ンググループ" -#: ../../rst/community/communication.rst:96 +#: ../../rst/community/communication.rst:98 msgid "Many of our community `Working Groups <https://github.com/ansible/community/wiki#working-groups>`_ meet in chat. If you want to get involved in a working group, join the Matrix room or IRC channel where it meets or comment on the agenda." msgstr "Ansible コミュニティー㮠`Working Groups <https://github.com/ansible/community/wiki#working-groups>`_ ã®å¤šããŒã€ãƒãƒ£ãƒƒãƒˆã§æ´»å‹•ã—ã¦ã„ã¾ã™ã€‚ワーã‚ンググループã«å‚åŠ ã—ãŸã„å ´åˆã¯ã€ãã®ãƒ¯ãƒ¼ã‚ンググループãŒæ´»å‹•ã—ã¦ã„ã‚‹Matrixã®ãƒãƒ£ãƒƒãƒˆãƒ«ãƒ¼ãƒ ã¾ãŸã¯IRCãƒãƒ£ãƒ³ãƒãƒ«ã«å‚åŠ ã—ãŸã‚Šã€è°é¡Œã«ã‚³ãƒ¡ãƒ³ãƒˆã—ãŸã‚Šã—ã¦ãã ã•ã„。" -#: ../../rst/community/communication.rst:98 +#: ../../rst/community/communication.rst:100 msgid "`Amazon (AWS) Working Group <https://github.com/ansible/community/wiki/AWS>`_ - Matrix: `#aws:ansible.im <https://matrix.to:/#/#aws:ansible.im>`_ | IRC: ``#ansible-aws``" msgstr "`Amazon (AWS) Working Group <https://github.com/ansible/community/wiki/AWS>`_ - Matrix: `#aws:ansible.im <https://matrix.to:/#/#aws:ansible.im>`_ | IRC: ``#ansible-aws``" -#: ../../rst/community/communication.rst:99 +#: ../../rst/community/communication.rst:101 msgid "`Ansible Lockdown Working Group <https://github.com/ansible/community/wiki/Lockdown>`_ (`Security playbooks/roles <https://github.com/ansible/ansible-lockdown>`_) - Matrix: `#lockdown:ansible.im <https://matrix.to:/#/#lockdown:ansible.im>`_ | IRC: ``#ansible-lockdown``" msgstr "`Ansible Lockdown Working Group <https://github.com/ansible/community/wiki/Lockdown>`_ (`Security playbooks/roles <https://github.com/ansible/ansible-lockdown>`_) - Matrix: `#lockdown:ansible.im <https://matrix.to:/#/#lockdown:ansible.im>`_ | IRC: ``#ansible-lockdown``" -#: ../../rst/community/communication.rst:100 +#: ../../rst/community/communication.rst:102 msgid "`AWX Working Group <https://github.com/ansible/awx>`_ - Matrix: `#awx:ansible.im <https://matrix.to:/#/#awx:ansible.im>`_ | IRC: ``#ansible-awx``" msgstr "`AWX Working Group <https://github.com/ansible/awx>`_ - Matrix: `#awx:ansible.im <https://matrix.to:/#/#awx:ansible.im>`_ | IRC: ``#ansible-awx``" -#: ../../rst/community/communication.rst:101 +#: ../../rst/community/communication.rst:103 msgid "`Azure Working Group <https://github.com/ansible/community/wiki/Azure>`_ - Matrix: `#azure:ansible.im <https://matrix.to:/#/#azure:ansible.im>`_ | IRC: ``#ansible-azure``" msgstr "`Azure Working Group <https://github.com/ansible/community/wiki/Azure>`_ - Matrix: `#azure:ansible.im <https://matrix.to:/#/#azure:ansible.im>`_ | IRC: ``#ansible-azure``" -#: ../../rst/community/communication.rst:102 +#: ../../rst/community/communication.rst:104 msgid "`Community Working Group <https://github.com/ansible/community/wiki/Community>`_ (including Meetups) - Matrix: `#community:ansible.im <https://matrix.to:/#/#community:ansible.im>`_ | IRC: ``#ansible-community``" msgstr "`Community Working Group <https://github.com/ansible/community/wiki/Community>`_ (Meetupã‚’å«ã‚€) - Matrix: `#community:ansible.im <https://matrix.to:/#/#community:ansible.im>`_ | IRC: ``#ansible-community``" -#: ../../rst/community/communication.rst:103 +#: ../../rst/community/communication.rst:105 msgid "`Container Working Group <https://github.com/ansible/community/wiki/Container>`_ - Matrix: `#container:ansible.im <https://matrix.to:/#/#container:ansible.im>`_ | IRC: ``#ansible-container``" msgstr "`Container Working Group <https://github.com/ansible/community/wiki/Container>`_ - Matrix: `#container:ansible.im <https://matrix.to:/#/#container:ansible.im>`_ | IRC: ``#ansible-container``" -#: ../../rst/community/communication.rst:104 +#: ../../rst/community/communication.rst:106 msgid "`Contributor Experience Working Group <https://github.com/ansible/community/wiki/Contributor-Experience>`_ - Matrix: `#community:ansible.im <https://matrix.to:/#/#community:ansible.im>`_ | IRC: ``#ansible-community``" msgstr "`Contributor Experience Working Group <https://github.com/ansible/community/wiki/Contributor-Experience>`_ - Matrix: `#community:ansible.im <https://matrix.to:/#/#community:ansible.im>`_ | IRC: ``#ansible-community``" -#: ../../rst/community/communication.rst:105 +#: ../../rst/community/communication.rst:107 msgid "`DigitalOcean Working Group <https://github.com/ansible/community/wiki/Digital-Ocean>`_ - Matrix: `#digitalocean:ansible.im <https://matrix.to:/#/#digitalocean:ansible.im>`_ | IRC: ``#ansible-digitalocean``" msgstr "`DigitalOcean Working Group <https://github.com/ansible/community/wiki/Digital-Ocean>`_ - Matrix: `#digitalocean:ansible.im <https://matrix.to:/#/#digitalocean:ansible.im>`_ | IRC: ``#ansible-digitalocean``" -#: ../../rst/community/communication.rst:106 +#: ../../rst/community/communication.rst:108 msgid "`Diversity Working Group <https://github.com/ansible/community/wiki/Diversity>`_ - Matrix: `#diversity:ansible.im <https://matrix.to:/#/#diversity:ansible.im>`_ | IRC: ``#ansible-diversity``" msgstr "`Diversity Working Group <https://github.com/ansible/community/wiki/Diversity>`_ - Matrix: `#diversity:ansible.im <https://matrix.to:/#/#diversity:ansible.im>`_ | IRC: ``#ansible-diversity``" -#: ../../rst/community/communication.rst:107 +#: ../../rst/community/communication.rst:109 msgid "`Docker Working Group <https://github.com/ansible/community/wiki/Docker>`_ - Matrix: `#devel:ansible.im <https://matrix.to:/#/#devel:ansible.im>`_ | IRC: ``#ansible-devel``" msgstr "`Docker Working Group <https://github.com/ansible/community/wiki/Docker>`_ - Matrix: `#devel:ansible.im <https://matrix.to:/#/#devel:ansible.im>`_ | IRC: ``#ansible-devel``" -#: ../../rst/community/communication.rst:108 +#: ../../rst/community/communication.rst:110 msgid "`Documentation Working Group <https://github.com/ansible/community/wiki/Docs>`_ - Matrix: `#docs:ansible.im <https://matrix.to:/#/#docs:ansible.im>`_ | IRC: ``#ansible-docs``" msgstr "`Documentation Working Group <https://github.com/ansible/community/wiki/Docs>`_ - Matrix: `#docs:ansible.im <https://matrix.to:/#/#docs:ansible.im>`_ | IRC: ``#ansible-docs``" -#: ../../rst/community/communication.rst:109 +#: ../../rst/community/communication.rst:111 msgid "`Galaxy Working Group <https://github.com/ansible/community/wiki/Galaxy>`_ - Matrix: `#galaxy:ansible.im <https://matrix.to:/#/#galaxy:ansible.im>`_ | IRC: ``#ansible-galaxy``" msgstr "`Galaxy Working Group <https://github.com/ansible/community/wiki/Galaxy>`_ - Matrix: `#galaxy:ansible.im <https://matrix.to:/#/#galaxy:ansible.im>`_ | IRC: ``#ansible-galaxy``" -#: ../../rst/community/communication.rst:110 +#: ../../rst/community/communication.rst:112 msgid "`JBoss Working Group <https://github.com/ansible/community/wiki/JBoss>`_ - Matrix: `#jboss:ansible.im <https://matrix.to:/#/#jboss:ansible.im>`_ | IRC: ``#ansible-jboss``" msgstr "`JBoss Working Group <https://github.com/ansible/community/wiki/JBoss>`_ - Matrix: `#jboss:ansible.im <https://matrix.to:/#/#jboss:ansible.im>`_ | IRC: ``#ansible-jboss``" -#: ../../rst/community/communication.rst:111 +#: ../../rst/community/communication.rst:113 msgid "`Kubernetes Working Group <https://github.com/ansible/community/wiki/Kubernetes>`_ - Matrix: `#kubernetes:ansible.im <https://matrix.to:/#/#kubernetes:ansible.im>`_ | IRC: ``#ansible-kubernetes``" msgstr "`Kubernetes Working Group <https://github.com/ansible/community/wiki/Kubernetes>`_ - Matrix: `#kubernetes:ansible.im <https://matrix.to:/#/#kubernetes:ansible.im>`_ | IRC: ``#ansible-kubernetes``" -#: ../../rst/community/communication.rst:112 +#: ../../rst/community/communication.rst:114 msgid "`Linode Working Group <https://github.com/ansible/community/wiki/Linode>`_ - Matrix: `#linode:ansible.im <https://matrix.to:/#/#linode:ansible.im>`_ | IRC: ``#ansible-linode``" msgstr "`Linode Working Group <https://github.com/ansible/community/wiki/Linode>`_ - Matrix: `#linode:ansible.im <https://matrix.to:/#/#linode:ansible.im>`_ | IRC: ``#ansible-linode``" -#: ../../rst/community/communication.rst:113 +#: ../../rst/community/communication.rst:115 msgid "`Molecule Working Group <https://github.com/ansible/community/wiki/Molecule>`_ (`testing platform for Ansible playbooks and roles <https://molecule.readthedocs.io>`_) - Matrix: `#molecule:ansible.im <https://matrix.to:/#/#molecule:ansible.im>`_ | IRC: ``#ansible-molecule``" msgstr "`Molecule Working Group <https://github.com/ansible/community/wiki/Molecule>`_ (`testing platform for Ansible playbooks and roles <https://molecule.readthedocs.io>`_) - Matrix: `#molecule:ansible.im <https://matrix.to:/#/#molecule:ansible.im>`_ | IRC: ``#ansible-molecule``" -#: ../../rst/community/communication.rst:114 +#: ../../rst/community/communication.rst:116 msgid "`Network Working Group <https://github.com/ansible/community/wiki/Network>`_ - Matrix: `#network:ansible.im <https://matrix.to:/#/#network:ansible.im>`_ | IRC: ``#ansible-network``" msgstr "`Network Working Group <https://github.com/ansible/community/wiki/Network>`_ - Matrix: `#network:ansible.im <https://matrix.to:/#/#network:ansible.im>`_ | IRC: ``#ansible-network``" -#: ../../rst/community/communication.rst:115 +#: ../../rst/community/communication.rst:117 msgid "`Remote Management Working Group <https://github.com/ansible/community/issues/409>`_ - Matrix: `#devel:ansible.im <https://matrix.to:/#/#devel:ansible.im>`_ | IRC: ``#ansible-devel``" msgstr "`Remote Management Working Group <https://github.com/ansible/community/issues/409>`_ - Matrix: `#devel:ansible.im <https://matrix.to:/#/#devel:ansible.im>`_ | IRC: ``#ansible-devel``" -#: ../../rst/community/communication.rst:116 +#: ../../rst/community/communication.rst:118 msgid "`Testing Working Group <https://github.com/ansible/community/wiki/Testing>`_ - Matrix: `#devel:ansible.im <https://matrix.to:/#/#devel:ansible.im>`_ | IRC: ``#ansible-devel``" msgstr "`Testing Working Group <https://github.com/ansible/community/wiki/Testing>`_ - Matrix: `#devel:ansible.im <https://matrix.to:/#/#devel:ansible.im>`_ | IRC: ``#ansible-devel``" -#: ../../rst/community/communication.rst:117 +#: ../../rst/community/communication.rst:119 msgid "`VMware Working Group <https://github.com/ansible/community/wiki/VMware>`_ - Matrix: `#vmware:ansible.im <https://matrix.to:/#/#vmware:ansible.im>`_ | IRC: ``#ansible-vmware``" msgstr "`VMware Working Group <https://github.com/ansible/community/wiki/VMware>`_ - Matrix: `#vmware:ansible.im <https://matrix.to:/#/#vmware:ansible.im>`_ | IRC: ``#ansible-vmware``" -#: ../../rst/community/communication.rst:118 +#: ../../rst/community/communication.rst:120 msgid "`Windows Working Group <https://github.com/ansible/community/wiki/Windows>`_ - Matrix: `#windows:ansible.im <https://matrix.to:/#/#windows:ansible.im>`_ | IRC: ``#ansible-windows``" msgstr "`Windows Working Group <https://github.com/ansible/community/wiki/Windows>`_ - Matrix: `#windows:ansible.im <https://matrix.to:/#/#windows:ansible.im>`_ | IRC: ``#ansible-windows``" -#: ../../rst/community/communication.rst:120 +#: ../../rst/community/communication.rst:122 msgid "Want to `form a new Working Group <https://github.com/ansible/community/blob/master/WORKING-GROUPS.md>`_?" msgstr "`æ–°ã—ã„ワーã‚ンググループを作りãŸã„ <https://github.com/ansible/community/blob/master/WORKING-GROUPS.md>`_ ã§ã™ã‹?" -#: ../../rst/community/communication.rst:123 +#: ../../rst/community/communication.rst:125 msgid "Regional and Language-specific channels" msgstr "地域ãŠã‚ˆã³è¨€èªžå›ºæœ‰ã®ãƒãƒ£ãƒ³ãƒãƒ«" -#: ../../rst/community/communication.rst:125 +#: ../../rst/community/communication.rst:127 msgid "Comunidad Ansible en español - Matrix: `#espanol:ansible.im <https://matrix.to:/#/#espanol:ansible.im>`_ | IRC: ``#ansible-es``" msgstr "スペイン語ã®Ansibleコミュニティー - Matrix: `#espanol:ansible.im <https://matrix.to:/#/#espanol:ansible.im>`_ | IRC: ``#ansible-es``" -#: ../../rst/community/communication.rst:126 +#: ../../rst/community/communication.rst:128 msgid "Communauté française d'Ansible - Matrix: `#francais:ansible.im <https://matrix.to:/#/#francais:ansible.im>`_ | IRC: ``#ansible-fr``" msgstr "フランス語ã®Ansibleコミュニティー - Matrix: `#francais:ansible.im <https://matrix.to:/#/#francais:ansible.im>`_ | IRC: ``#ansible-fr``" -#: ../../rst/community/communication.rst:127 +#: ../../rst/community/communication.rst:129 msgid "Communauté suisse d'Ansible - Matrix: `#suisse:ansible.im <https://matrix.to:/#/#suisse:ansible.im>`_ | IRC: ``#ansible-zh``" msgstr "スイスã®Ansibleコミュニティー - Matrix: `#suisse:ansible.im <https://matrix.to:/#/#suisse:ansible.im>`_ | IRC: ``#ansible-zh``" -#: ../../rst/community/communication.rst:128 +#: ../../rst/community/communication.rst:130 msgid "European Ansible Community - Matrix: `#europe:ansible.im <https://matrix.to:/#/#europe:ansible.im>`_ | IRC: ``#ansible-eu``" msgstr "ヨーãƒãƒƒãƒ‘ã®Ansibleコミュニティー - Matrix: `#europe:ansible.im <https://matrix.to:/#/#europe:ansible.im>`_ | IRC: ``#ansible-eu``" -#: ../../rst/community/communication.rst:131 +#: ../../rst/community/communication.rst:133 msgid "Meetings on chat" msgstr "ãƒãƒ£ãƒƒãƒˆã§ã®ä¼šè°" -#: ../../rst/community/communication.rst:133 +#: ../../rst/community/communication.rst:135 msgid "The Ansible community holds regular meetings on various topics on Matrix/IRC, and anyone who is interested is invited to participate. For more information about Ansible meetings, consult the `meeting schedule and agenda page <https://github.com/ansible/community/blob/master/meetings/README.md>`_." msgstr "Ansible コミュニティーã¯ã€Matrix/IRCã§ã•ã¾ã–ã¾ãªãƒˆãƒ”ックã«é–¢ã™ã‚‹å®šæœŸçš„ãªãƒŸãƒ¼ãƒ†ã‚£ãƒ³ã‚°ã‚’é–‹ã„ã¦ãŠã‚Šã€èˆˆå‘³ã®ã‚る人ã¯èª°ã§ã‚‚å‚åŠ ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚Ansible ミーティングã®è©³ç´°ã¯ã€ã€Œ`meeting schedule and agenda page <https://github.com/ansible/community/blob/master/meetings/README.md>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/community/communication.rst:136 +#: ../../rst/community/communication.rst:138 msgid "Ansible Automation Platform support questions" msgstr "Ansible Automation Platform サãƒãƒ¼ãƒˆã«é–¢ã™ã‚‹è³ªå•" -#: ../../rst/community/communication.rst:138 +#: ../../rst/community/communication.rst:140 msgid "Red Hat Ansible `Automation Platform <https://www.ansible.com/products/automation-platform>`_ is a subscription that contains support, certified content, and tooling for Ansible including content management, a controller, UI and REST API." msgstr "Red Hat Ansible `Automation Platform <https://www.ansible.com/products/automation-platform>`_ ã¯ã€ã‚³ãƒ³ãƒ†ãƒ³ãƒ„管ç†ã€ã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©ãƒ¼ã€UI ãŠã‚ˆã³ REST API ãªã©ã® Ansible ã®ã‚µãƒãƒ¼ãƒˆã€èªå®šã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã€ãŠã‚ˆã³ãƒ„ールãŒå«ã¾ã‚Œã‚‹ã‚µãƒ–スクリプションã§ã™ã€‚" -#: ../../rst/community/communication.rst:140 +#: ../../rst/community/communication.rst:142 msgid "If you have a question about Ansible Automation Platform, visit `Red Hat support <https://access.redhat.com/products/red-hat-ansible-automation-platform/>`_ rather than using a chat channel or the general project mailing list." msgstr "Ansible Automation Platform ã«é–¢ã™ã‚‹ã”質å•ã¯ã€ãƒãƒ£ãƒƒãƒˆãƒãƒ£ãƒ³ãƒãƒ«ã¾ãŸã¯ä¸€èˆ¬çš„ãªãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆãƒ¡ãƒ¼ãƒªãƒ³ã‚°ãƒªã‚¹ãƒˆã§ã¯ãªãã€`Red Hat support <https://access.redhat.com/products/red-hat-ansible-automation-platform/>`_ ã«ãŠå•ã„åˆã‚ã›ãã ã•ã„。" -#: ../../rst/community/communication.rst:143 +#: ../../rst/community/communication.rst:145 msgid "The Bullhorn" msgstr "The Bullhorn" -#: ../../rst/community/communication.rst:145 +#: ../../rst/community/communication.rst:147 msgid "**The Bullhorn** is our newsletter for the Ansible developer community. If you have any questions or content you would like to share, please reach out to us at the-bullhorn@redhat.com, or directly `contribute/suggest content <https://github.com/ansible/community/issues/546>`_ for upcoming issues." msgstr "**The Bullhorn** ã¯ã€Ansible 開発者コミュニティーã®ãƒ‹ãƒ¥ãƒ¼ã‚¹ãƒ¬ã‚¿ãƒ¼ã§ã™ã€‚共有ã—ãŸã„質å•ã‚„コンテンツãŒã‚ã‚‹å ´åˆã¯ã€Red Hat ã«ã‚¢ã‚¯ã‚»ã‚¹ã—ã¦ãã ã•ã„ (the-bullhorn@redhat.com,)。ã¾ãŸã€ä»Šå¾Œç™ºè¡Œã™ã‚‹ç‰ˆã«ã¤ã„ã¦ã¯ã€`contribute/suggest content <https://github.com/ansible/community/issues/546>`_ ã«ç›´æŽ¥ãŠå•ã„åˆã‚ã›ãã ã•ã„。" -#: ../../rst/community/communication.rst:148 +#: ../../rst/community/communication.rst:150 msgid "Read past issues `here <https://github.com/ansible/community/wiki/News>`_." msgstr "ã“ã‚Œã¾ã§ç™ºè¡Œã—ãŸç‰ˆã«ã¤ã„ã¦ã¯ã€`ã“ã¡ã‚‰ <https://github.com/ansible/community/wiki/News>`_ ã‚’ãŠèªã¿ãã ã•ã„。" -#: ../../rst/community/communication.rst:150 +#: ../../rst/community/communication.rst:152 msgid "`Subscribe <https://eepurl.com/gZmiEP>`_ to receive it." msgstr "ã“れをå—ã‘å–ã‚‹ã«ã¯ã€`Subscribe <https://eepurl.com/gZmiEP>`_ ã—ã¾ã™ã€‚" @@ -1319,8 +1319,8 @@ msgid "Here are some examples:" msgstr "以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" #: ../../rst/community/development_process.rst:246 -msgid "You can find more example changelog fragments in the `changelog directory <https://github.com/ansible/ansible/tree/stable-2.11/changelogs/fragments>`_ for the 2.11 release." -msgstr "changelog フラグメントã®ä¾‹ã¯ã€2.11 リリース㮠`changelog ディレクトリー <https://github.com/ansible/ansible/tree/stable-2.11/changelogs/fragments>`_ ã«ã‚‚ã‚ã‚Šã¾ã™ã€‚" +msgid "You can find more example changelog fragments in the `changelog directory <https://github.com/ansible/ansible/tree/stable-2.12/changelogs/fragments>`_ for the 2.12 release." +msgstr "changelog フラグメントã®ä¾‹ã¯ã€2.12 リリース㮠`changelog directory <https://github.com/ansible/ansible/tree/stable-2.12/changelogs/fragments>`_ ã«ã‚‚ã‚ã‚Šã¾ã™ã€‚" #: ../../rst/community/development_process.rst:248 msgid "After you have written the changelog fragment for your PR, commit the file and include it with the pull request." @@ -1351,8 +1351,8 @@ msgid "These instructions assume that:" msgstr "ã“れらã®æ‰‹é †ã¯ã€ä»¥ä¸‹ã‚’å‰æã¨ã—ã¦ã„ã¾ã™ã€‚" #: ../../rst/community/development_process.rst:310 -msgid "``stable-2.11`` is the targeted release branch for the backport" -msgstr "``stable-2.11`` ã¯ã€ãƒãƒƒã‚¯ãƒãƒ¼ãƒˆã®ã‚¿ãƒ¼ã‚²ãƒƒãƒˆãƒªãƒªãƒ¼ã‚¹ãƒ–ランãƒã§ã™ã€‚" +msgid "``stable-2.12`` is the targeted release branch for the backport" +msgstr "``stable-2.12`` ã¯ã€ãƒãƒƒã‚¯ãƒãƒ¼ãƒˆã®ã‚¿ãƒ¼ã‚²ãƒƒãƒˆãƒªãƒªãƒ¼ã‚¹ãƒ–ランãƒã§ã™ã€‚" #: ../../rst/community/development_process.rst:311 msgid "``https://github.com/ansible/ansible.git`` is configured as a ``git remote`` named ``upstream``. If you do not use a ``git remote`` named ``upstream``, adjust the instructions accordingly." @@ -1379,16 +1379,16 @@ msgid "Push your feature branch to your fork on GitHub:" msgstr "feature ブランãƒã‚’ GitHub ã®ãƒ•ã‚©ãƒ¼ã‚¯ã«ãƒ—ッシュã—ã¾ã™ã€‚" #: ../../rst/community/development_process.rst:335 -msgid "Submit the pull request for ``backport/2.11/[PR_NUMBER_FROM_DEVEL]`` against the ``stable-2.11`` branch" -msgstr "``stable-2.11`` ブランãƒã«ã€``backport/2.11/[PR_NUMBER_FROM_DEVEL]`` ã®ãƒ—ルè¦æ±‚ã‚’é€ä¿¡ã—ã¾ã™ã€‚" +msgid "Submit the pull request for ``backport/2.12/[PR_NUMBER_FROM_DEVEL]`` against the ``stable-2.12`` branch" +msgstr "``stable-2.12`` ブランãƒã«ã€``backport/2.12/[PR_NUMBER_FROM_DEVEL]`` ã®ãƒ—ルè¦æ±‚ã‚’é€ä¿¡ã—ã¾ã™ã€‚" #: ../../rst/community/development_process.rst:337 msgid "The Release Manager will decide whether to merge the backport PR before the next minor release. There isn't any need to follow up. Just ensure that the automated tests (CI) are green." msgstr "次ã®ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ã¾ã§ã«ãƒãƒƒã‚¯ãƒãƒ¼ãƒˆã®ãƒ—ルè¦æ±‚をマージã™ã‚‹ã‹ã©ã†ã‹ã¯ãƒªãƒªãƒ¼ã‚¹ãƒžãƒãƒ¼ã‚¸ãƒ£ãƒ¼ãŒåˆ¤æ–ã—ã¾ã™ã€‚フォãƒãƒ¼ã‚¢ãƒƒãƒ—ã®å¿…è¦ã¯ã‚ã‚Šã¾ã›ã‚“。自動テスト (CI) ã«å•é¡ŒãŒç™ºç”Ÿã—ã¦ã„ãªã„ã“ã¨ã‚’確èªã™ã‚‹ã ã‘ã§ã™ã€‚" #: ../../rst/community/development_process.rst:341 -msgid "The branch name ``backport/2.11/[PR_NUMBER_FROM_DEVEL]`` is somewhat arbitrary, but conveys meaning about the purpose of the branch. This branch name format is not required, but it can be helpful, especially when making multiple backport PRs for multiple stable branches." -msgstr "ブランãƒå ``backport/2.11/[PR_NUMBER_FROM_DEVEL]`` ã¯ã‚„ã‚„æ£æ„çš„ã§ã™ãŒã€ãƒ–ランãƒã®ç›®çš„ã«ã¤ã„ã¦ã®æ„味をä¼ãˆã¾ã™ã€‚ã“ã®ãƒ–ランãƒåã®å½¢å¼ã¯å¿…é ˆã§ã¯ã‚ã‚Šã¾ã›ã‚“ãŒã€ç‰¹ã«è¤‡æ•°ã®å®‰å®šã—ãŸãƒ–ランãƒã«å¯¾ã—ã¦è¤‡æ•°ã®ãƒãƒƒã‚¯ãƒãƒ¼ãƒˆãƒ—ルè¦æ±‚を作æˆã™ã‚‹å ´åˆã«å½¹ç«‹ã¡ã¾ã™ã€‚" +msgid "The branch name ``backport/2.12/[PR_NUMBER_FROM_DEVEL]`` is somewhat arbitrary, but conveys meaning about the purpose of the branch. This branch name format is not required, but it can be helpful, especially when making multiple backport PRs for multiple stable branches." +msgstr "ブランãƒå ``backport/2.12/[PR_NUMBER_FROM_DEVEL]`` ã¯ã‚„ã‚„æ£æ„çš„ã§ã™ãŒã€ãƒ–ランãƒã®ç›®çš„ã«ã¤ã„ã¦ã®æ„味をä¼ãˆã¾ã™ã€‚ã“ã®ãƒ–ランãƒåã®å½¢å¼ã¯å¿…é ˆã§ã¯ã‚ã‚Šã¾ã›ã‚“ãŒã€ç‰¹ã«è¤‡æ•°ã®å®‰å®šã—ãŸãƒ–ランãƒã«å¯¾ã—ã¦è¤‡æ•°ã®ãƒãƒƒã‚¯ãƒãƒ¼ãƒˆãƒ—ルè¦æ±‚を作æˆã™ã‚‹å ´åˆã«å½¹ç«‹ã¡ã¾ã™ã€‚" #: ../../rst/community/development_process.rst:345 msgid "If you prefer, you can use CPython's cherry-picker tool (``pip install --user 'cherry-picker >= 1.3.2'``) to backport commits from devel to stable branches in Ansible. Take a look at the `cherry-picker documentation <https://pypi.org/p/cherry-picker#cherry-picking>`_ for details on installing, configuring, and using it." diff --git a/docs/docsite/rst/locales/ja/LC_MESSAGES/dev_guide.po b/docs/docsite/rst/locales/ja/LC_MESSAGES/dev_guide.po index e9809221..67430486 100644 --- a/docs/docsite/rst/locales/ja/LC_MESSAGES/dev_guide.po +++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/dev_guide.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Ansible devel\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-10-05 13:53+0200\n" +"POT-Creation-Date: 2021-11-09 14:07+0100\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" @@ -289,9 +289,9 @@ msgstr "コレクションを開発ã™ã‚‹ã‹ã€ã¾ãŸã¯å¤‰æ›´ã—ã¾ã™ã€‚" #: ../../rst/dev_guide/collections_galaxy_meta.rst:331 #: ../../rst/dev_guide/developing_api.rst:40 -#: ../../rst/dev_guide/developing_inventory.rst:468 +#: ../../rst/dev_guide/developing_inventory.rst:475 #: ../../rst/dev_guide/developing_plugins.rst:542 -#: ../../rst/dev_guide/testing_units_modules.rst:545 +#: ../../rst/dev_guide/testing_units_modules.rst:571 msgid ":ref:`developing_modules_general`" msgstr ":ref:`developing_modules_general`" @@ -303,7 +303,7 @@ msgstr "Ansible モジュールã®ä½œæˆæ–¹æ³•ã«ã¤ã„ã¦" #: ../../rst/dev_guide/collections_galaxy_meta.rst:333 #: ../../rst/dev_guide/developing_collections.rst:39 #: ../../rst/dev_guide/developing_collections_changelogs.rst:73 -#: ../../rst/dev_guide/developing_collections_contributing.rst:52 +#: ../../rst/dev_guide/developing_collections_contributing.rst:58 #: ../../rst/dev_guide/developing_collections_creating.rst:50 #: ../../rst/dev_guide/developing_collections_distributing.rst:293 #: ../../rst/dev_guide/developing_collections_migrating.rst:129 @@ -313,7 +313,7 @@ msgstr ":ref:`collections`" #: ../../rst/dev_guide/collections_galaxy_meta.rst:334 #: ../../rst/dev_guide/developing_collections_changelogs.rst:74 -#: ../../rst/dev_guide/developing_collections_contributing.rst:53 +#: ../../rst/dev_guide/developing_collections_contributing.rst:59 #: ../../rst/dev_guide/developing_collections_creating.rst:51 #: ../../rst/dev_guide/developing_collections_distributing.rst:294 #: ../../rst/dev_guide/developing_collections_migrating.rst:130 @@ -324,13 +324,13 @@ msgstr "コレクションã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«æ–¹æ³•ãŠã‚ˆã³ä½¿ç”¨æ–¹æ³•ã¯ã“ #: ../../rst/dev_guide/collections_galaxy_meta.rst:335 #: ../../rst/dev_guide/developing_collections.rst:45 #: ../../rst/dev_guide/developing_collections_changelogs.rst:77 -#: ../../rst/dev_guide/developing_collections_contributing.rst:56 +#: ../../rst/dev_guide/developing_collections_contributing.rst:62 #: ../../rst/dev_guide/developing_collections_creating.rst:54 #: ../../rst/dev_guide/developing_collections_distributing.rst:297 #: ../../rst/dev_guide/developing_collections_migrating.rst:133 #: ../../rst/dev_guide/developing_collections_shared.rst:91 -#: ../../rst/dev_guide/developing_collections_structure.rst:277 -#: ../../rst/dev_guide/developing_collections_testing.rst:80 +#: ../../rst/dev_guide/developing_collections_structure.rst:279 +#: ../../rst/dev_guide/developing_collections_testing.rst:92 #: ../../rst/dev_guide/developing_core.rst:18 #: ../../rst/dev_guide/developing_modules.rst:48 #: ../../rst/dev_guide/developing_plugins.rst:544 @@ -340,13 +340,13 @@ msgstr "`メーリングリスト <https://groups.google.com/group/ansible-devel #: ../../rst/dev_guide/collections_galaxy_meta.rst:336 #: ../../rst/dev_guide/developing_collections.rst:46 #: ../../rst/dev_guide/developing_collections_changelogs.rst:78 -#: ../../rst/dev_guide/developing_collections_contributing.rst:57 +#: ../../rst/dev_guide/developing_collections_contributing.rst:63 #: ../../rst/dev_guide/developing_collections_creating.rst:55 #: ../../rst/dev_guide/developing_collections_distributing.rst:298 #: ../../rst/dev_guide/developing_collections_migrating.rst:134 #: ../../rst/dev_guide/developing_collections_shared.rst:92 -#: ../../rst/dev_guide/developing_collections_structure.rst:278 -#: ../../rst/dev_guide/developing_collections_testing.rst:81 +#: ../../rst/dev_guide/developing_collections_structure.rst:280 +#: ../../rst/dev_guide/developing_collections_testing.rst:93 #: ../../rst/dev_guide/developing_core.rst:19 #: ../../rst/dev_guide/developing_plugins.rst:545 msgid "The development mailing list" @@ -510,38 +510,38 @@ msgstr "モジュール開発を始ã‚ã‚‹" #: ../../rst/dev_guide/developing_api.rst:42 #: ../../rst/dev_guide/developing_core.rst:16 -#: ../../rst/dev_guide/developing_inventory.rst:470 +#: ../../rst/dev_guide/developing_inventory.rst:477 msgid ":ref:`developing_plugins`" msgstr ":ref:`developing_plugins`" #: ../../rst/dev_guide/developing_api.rst:43 -#: ../../rst/dev_guide/developing_inventory.rst:471 +#: ../../rst/dev_guide/developing_inventory.rst:478 msgid "How to develop plugins" msgstr "プラグインã®é–‹ç™ºæ–¹æ³•" #: ../../rst/dev_guide/developing_api.rst:44 -#: ../../rst/dev_guide/developing_inventory.rst:474 -#: ../../rst/dev_guide/testing_units_modules.rst:553 +#: ../../rst/dev_guide/developing_inventory.rst:481 +#: ../../rst/dev_guide/testing_units_modules.rst:579 msgid "`Development Mailing List <https://groups.google.com/group/ansible-devel>`_" msgstr "`Development Mailing List <https://groups.google.com/group/ansible-devel>`_" #: ../../rst/dev_guide/developing_api.rst:45 -#: ../../rst/dev_guide/developing_inventory.rst:475 -#: ../../rst/dev_guide/testing_units_modules.rst:554 +#: ../../rst/dev_guide/developing_inventory.rst:482 +#: ../../rst/dev_guide/testing_units_modules.rst:580 msgid "Mailing list for development topics" msgstr "開発トピックã®ãƒ¡ãƒ¼ãƒªãƒ³ã‚°ãƒªã‚¹ãƒˆ" #: ../../rst/dev_guide/developing_api.rst:46 #: ../../rst/dev_guide/developing_collections.rst:47 #: ../../rst/dev_guide/developing_collections_changelogs.rst:79 -#: ../../rst/dev_guide/developing_collections_contributing.rst:58 +#: ../../rst/dev_guide/developing_collections_contributing.rst:64 #: ../../rst/dev_guide/developing_collections_creating.rst:56 #: ../../rst/dev_guide/developing_collections_distributing.rst:299 #: ../../rst/dev_guide/developing_collections_migrating.rst:135 #: ../../rst/dev_guide/developing_collections_shared.rst:93 -#: ../../rst/dev_guide/developing_collections_structure.rst:279 -#: ../../rst/dev_guide/developing_collections_testing.rst:82 -#: ../../rst/dev_guide/developing_inventory.rst:476 +#: ../../rst/dev_guide/developing_collections_structure.rst:281 +#: ../../rst/dev_guide/developing_collections_testing.rst:94 +#: ../../rst/dev_guide/developing_inventory.rst:483 #: ../../rst/dev_guide/developing_modules.rst:50 #: ../../rst/dev_guide/developing_plugins.rst:546 msgid ":ref:`communication_irc`" @@ -550,14 +550,14 @@ msgstr ":ref:`communication_irc`" #: ../../rst/dev_guide/developing_api.rst:47 #: ../../rst/dev_guide/developing_collections.rst:48 #: ../../rst/dev_guide/developing_collections_changelogs.rst:80 -#: ../../rst/dev_guide/developing_collections_contributing.rst:59 +#: ../../rst/dev_guide/developing_collections_contributing.rst:65 #: ../../rst/dev_guide/developing_collections_creating.rst:57 #: ../../rst/dev_guide/developing_collections_distributing.rst:300 #: ../../rst/dev_guide/developing_collections_migrating.rst:136 #: ../../rst/dev_guide/developing_collections_shared.rst:94 -#: ../../rst/dev_guide/developing_collections_structure.rst:280 -#: ../../rst/dev_guide/developing_collections_testing.rst:83 -#: ../../rst/dev_guide/developing_inventory.rst:477 +#: ../../rst/dev_guide/developing_collections_structure.rst:282 +#: ../../rst/dev_guide/developing_collections_testing.rst:95 +#: ../../rst/dev_guide/developing_inventory.rst:484 #: ../../rst/dev_guide/developing_modules.rst:51 #: ../../rst/dev_guide/developing_plugins.rst:547 msgid "How to join Ansible chat channels" @@ -597,21 +597,21 @@ msgstr "Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã§ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストール㗠#: ../../rst/dev_guide/developing_collections.rst:41 #: ../../rst/dev_guide/developing_collections_changelogs.rst:75 -#: ../../rst/dev_guide/developing_collections_contributing.rst:54 +#: ../../rst/dev_guide/developing_collections_contributing.rst:60 #: ../../rst/dev_guide/developing_collections_migrating.rst:131 #: ../../rst/dev_guide/developing_collections_shared.rst:89 -#: ../../rst/dev_guide/developing_collections_structure.rst:275 -#: ../../rst/dev_guide/developing_collections_testing.rst:78 +#: ../../rst/dev_guide/developing_collections_structure.rst:277 +#: ../../rst/dev_guide/developing_collections_testing.rst:90 msgid ":ref:`contributing_maintained_collections`" msgstr ":ref:`contributing_maintained_collections`" #: ../../rst/dev_guide/developing_collections.rst:42 #: ../../rst/dev_guide/developing_collections_changelogs.rst:76 -#: ../../rst/dev_guide/developing_collections_contributing.rst:55 +#: ../../rst/dev_guide/developing_collections_contributing.rst:61 #: ../../rst/dev_guide/developing_collections_migrating.rst:132 #: ../../rst/dev_guide/developing_collections_shared.rst:90 -#: ../../rst/dev_guide/developing_collections_structure.rst:276 -#: ../../rst/dev_guide/developing_collections_testing.rst:79 +#: ../../rst/dev_guide/developing_collections_structure.rst:278 +#: ../../rst/dev_guide/developing_collections_testing.rst:91 msgid "Guidelines for contributing to selected collections" msgstr "é¸æŠžã—ãŸã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«è²¢çŒ®ã™ã‚‹ã‚¬ã‚¤ãƒ‰ãƒ©ã‚¤ãƒ³" @@ -756,7 +756,7 @@ msgid "This example uses the `community.general collection <https://github.com/a msgstr "ã“ã®ä¾‹ã§ã¯ã€`community.general コレクション <https://github.com/ansible-collections/community.general/>`_ を使用ã—ã¦ã„ã¾ã™ã€‚åŒã˜ GitHub Org ã®ä»–ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«è²¢çŒ®ã™ã‚‹ãŸã‚ã«ã€ãƒ•ã‚©ãƒ«ãƒ€ãƒ¼å ``community`` ãŠã‚ˆã³ ``general`` ã‚’ã€åˆ¥ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®åå‰ç©ºé–“ãŠã‚ˆã³ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³åã«ç½®ãæ›ãˆã¾ã™ã€‚" #: ../../rst/dev_guide/developing_collections_contributing.rst:18 -#: ../../rst/dev_guide/testing_integration.rst:55 +#: ../../rst/dev_guide/testing_integration.rst:59 msgid "Prerequisites" msgstr "è¦ä»¶" @@ -773,30 +773,30 @@ msgid "Creating a PR" msgstr "PR ã®ä½œæˆ" #: ../../rst/dev_guide/developing_collections_contributing.rst:28 -msgid "Create the directory ``~/dev/ansible/collections/ansible_collections/community``::" +msgid "Create the directory ``~/dev/ansible/collections/ansible_collections/community``:" msgstr "``~/dev/ansible/collections/ansible_collections/community`` ディレクトリーを作æˆã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_contributing.rst:32 -msgid "Clone `the community.general Git repository <https://github.com/ansible-collections/community.general/>`_ or a fork of it into the directory ``general``::" -msgstr "`community.general Git リãƒã‚¸ãƒˆãƒªãƒ¼ <https://github.com/ansible-collections/community.general/>`_ ã®ã‚¯ãƒãƒ¼ãƒ³ã‚’作æˆã™ã‚‹ã‹ã€ãれを ``general`` ディレクトリーã«ãƒ•ã‚©ãƒ¼ã‚¯ã—ã¾ã™ã€‚" +#: ../../rst/dev_guide/developing_collections_contributing.rst:34 +msgid "Clone `the community.general Git repository <https://github.com/ansible-collections/community.general/>`_ or a fork of it into the directory ``general``:" +msgstr "`community.general Git レãƒã‚¸ãƒˆãƒªãƒ¼ <https://github.com/ansible-collections/community.general/>`_ ã®ã‚¯ãƒãƒ¼ãƒ³ã‚’作æˆã™ã‚‹ã‹ã€ãれを ``general`` ディレクトリーã«ãƒ•ã‚©ãƒ¼ã‚¯ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_contributing.rst:37 -msgid "If you clone from a fork, add the original repository as a remote ``upstream``::" +#: ../../rst/dev_guide/developing_collections_contributing.rst:41 +msgid "If you clone from a fork, add the original repository as a remote ``upstream``:" msgstr "フォークã®ã‚¯ãƒãƒ¼ãƒ³ã‚’作æˆã—ãŸã‚‰ã€å…ƒã®ãƒªãƒã‚¸ãƒˆãƒªãƒ¼ã‚’リモート㮠``upstream`` ã¨ã—ã¦è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_contributing.rst:42 +#: ../../rst/dev_guide/developing_collections_contributing.rst:48 msgid "Create a branch and commit your changes on the branch." msgstr "ブランãƒã‚’作æˆã—ã€ãƒ–ランãƒã§å¤‰æ›´ã‚’コミットã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_contributing.rst:44 +#: ../../rst/dev_guide/developing_collections_contributing.rst:50 msgid "Remember to add tests for your changes, see :ref:`testing_collections`." msgstr "変更ã«ãƒ†ã‚¹ãƒˆã‚’è¿½åŠ ã™ã‚‹ã®ã‚’忘れãªã„よã†ã«ã—ã¦ãã ã•ã„。:ref:`testing_collections` ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_collections_contributing.rst:46 +#: ../../rst/dev_guide/developing_collections_contributing.rst:52 msgid "Push your changes to your fork of the collection and create a Pull Request." msgstr "変更をコレクションã®ãƒ•ã‚©ãƒ¼ã‚¯ã«ãƒ—ッシュã—ã€ãƒ—ルè¦æ±‚を作æˆã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_contributing.rst:48 +#: ../../rst/dev_guide/developing_collections_contributing.rst:54 msgid "You can test your changes by using this checkout of ``community.general`` in playbooks and roles with whichever version of Ansible you have installed locally, including a local checkout of ``ansible/ansible``'s ``devel`` branch." msgstr "ã“ã‚Œã§ã€``ansible/ansible`` ã® ``devel`` ブランãƒã®ãƒãƒ¼ã‚«ãƒ«ãƒã‚§ãƒƒã‚¯ã‚¢ã‚¦ãƒˆã‚’å«ã‚ã€ãƒãƒ¼ã‚«ãƒ«ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ãŸã©ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Ansible ã§ã‚‚ã€Playbook ã‚„ãƒãƒ¼ãƒ«ã§ ``community.general`` ã®ãƒã‚§ãƒƒã‚¯ã‚¢ã‚¦ãƒˆã‚’使用ã—ã¦å¤‰æ›´ã‚’テストã§ãã¾ã™ã€‚" @@ -1624,7 +1624,7 @@ msgid "plugin" msgstr "プラグイン" #: ../../rst/dev_guide/developing_collections_migrating.rst:117 -#: ../../rst/dev_guide/developing_collections_structure.rst:98 +#: ../../rst/dev_guide/developing_collections_structure.rst:100 msgid "module_utils" msgstr "モジュールユーティリティー" @@ -1734,198 +1734,198 @@ msgid "Collection directories and files" msgstr "コレクションディレクトリーãŠã‚ˆã³ãƒ•ã‚¡ã‚¤ãƒ«" #: ../../rst/dev_guide/developing_collections_structure.rst:16 -msgid "A collection can contain these directories and files::" +msgid "A collection can contain these directories and files:" msgstr "コレクションã«ã¯ã€ã“れらã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ãŠã‚ˆã³ãƒ•ã‚¡ã‚¤ãƒ«ã‚’å«ã‚ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:41 +#: ../../rst/dev_guide/developing_collections_structure.rst:43 msgid "Ansible only accepts ``.md`` extensions for the :file:`README` file and any files in the :file:`/docs` folder." msgstr "Ansible ã¯ã€:file:`README` ファイルãŠã‚ˆã³ :file:`/docs` フォルダー内ã®ã™ã¹ã¦ã®ãƒ•ã‚¡ã‚¤ãƒ«ã® ``.md`` æ‹¡å¼µåã®ã¿ã‚’å—ã‘入れã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:42 +#: ../../rst/dev_guide/developing_collections_structure.rst:44 msgid "See the `ansible-collections <https://github.com/ansible-collections/>`_ GitHub Org for examples of collection structure." msgstr "ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³æ§‹é€ ã®ä¾‹ã¯ã€`ansible-collections <https://github.com/ansible-collections/>`_ GitHub Org ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_collections_structure.rst:43 +#: ../../rst/dev_guide/developing_collections_structure.rst:45 msgid "Not all directories are currently in use. Those are placeholders for future features." msgstr "ç¾åœ¨ã€ã™ã¹ã¦ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ãŒä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹ã‚ã‘ã§ã¯ã‚ã‚Šã¾ã›ã‚“。ã“れらã¯ã€å°†æ¥ã®æ©Ÿèƒ½ã®ãƒ—レースホルダーã§ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:48 +#: ../../rst/dev_guide/developing_collections_structure.rst:50 msgid "galaxy.yml" msgstr "galaxy.yml" -#: ../../rst/dev_guide/developing_collections_structure.rst:50 +#: ../../rst/dev_guide/developing_collections_structure.rst:52 msgid "A collection must have a ``galaxy.yml`` file that contains the necessary information to build a collection artifact. See :ref:`collections_galaxy_meta` for details." msgstr "コレクションã«ã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚¢ãƒ¼ãƒ†ã‚£ãƒ•ã‚¡ã‚¯ãƒˆã‚’構築ã™ã‚‹ãŸã‚ã«å¿…è¦ãªæƒ…å ±ãŒå«ã¾ã‚Œã‚‹ ``galaxy.yml`` ファイルãŒå¿…è¦ã§ã™ã€‚詳細ã¯ã€ã€Œ:ref:`collections_galaxy_meta`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_collections_structure.rst:55 +#: ../../rst/dev_guide/developing_collections_structure.rst:57 msgid "docs directory" msgstr "docs ディレクトリー" -#: ../../rst/dev_guide/developing_collections_structure.rst:57 +#: ../../rst/dev_guide/developing_collections_structure.rst:59 msgid "Use the ``docs`` folder to describe how to use the roles and plugins the collection provides, role requirements, and so on." msgstr "``docs`` フォルダを使用ã—ã¦ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãŒæä¾›ã™ã‚‹ãƒãƒ¼ãƒ«ã¨ãƒ—ラグインã®ä½¿ç”¨æ–¹æ³•ã€ãƒãƒ¼ãƒ«ã®è¦ä»¶ãªã©ã‚’説明ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:59 +#: ../../rst/dev_guide/developing_collections_structure.rst:61 msgid "For certified collections, Automation Hub displays documents written in markdown in the main ``docs`` directory with no subdirectories. This will not display on https://docs.ansible.com." msgstr "èªå®šã•ã‚ŒãŸã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€Automation Hubã¯ã€ã‚µãƒ–ディレクトリをæŒãŸãªã„メインã®``docs`` ディレクトリã«ãƒžãƒ¼ã‚¯ãƒ€ã‚¦ãƒ³ã§æ›¸ã‹ã‚ŒãŸãƒ‰ã‚ュメントを表示ã—ã¾ã™ã€‚ã“ã‚Œã¯ã€https://docs.ansible.com.ã«ã¯è¡¨ç¤ºã•ã‚Œã¾ã›ã‚“。" -#: ../../rst/dev_guide/developing_collections_structure.rst:61 +#: ../../rst/dev_guide/developing_collections_structure.rst:63 msgid "For community collections included in the Ansible PyPI package, docs.ansible.com displays documents written in reStructuredText (.rst) in a docsite/rst/ subdirectory. Define the structure of your extra documentation in ``docs/docsite/extra-docs.yml``:" msgstr "Ansibleã®PyPIパッケージã«å«ã¾ã‚Œã‚‹ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®å ´åˆã€docs.ansible.comã¯reStructuredText（.rst）ã§æ›¸ã‹ã‚ŒãŸãƒ‰ã‚ュメントをdocsite/rst/サブディレクトリã«è¡¨ç¤ºã—ã¾ã™ã€‚``docs/docsite/extra-docs.yml`` ã§è¿½åŠ ドã‚ュメントã®æ§‹é€ を定義ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:71 +#: ../../rst/dev_guide/developing_collections_structure.rst:73 msgid "The index page of the documentation for your collection displays the title you define in ``docs/docsite/extra-docs.yml`` with a link to your extra documentation. For an example, see the `community.docker collection repo <https://github.com/ansible-collections/community.docker/tree/main/docs/docsite>`_ and the `community.docker collection documentation <https://docs.ansible.com/ansible/latest/collections/community/docker/index.html>`_." msgstr "コレクションã®ãƒ‰ã‚ュメントã®ã‚¤ãƒ³ãƒ‡ãƒƒã‚¯ã‚¹ãƒšãƒ¼ã‚¸ã«ã¯ã€``docs/docsite/extra-docs.yml`` ã§å®šç¾©ã—ãŸã‚¿ã‚¤ãƒˆãƒ«ã¨ã€è¿½åŠ ドã‚ュメントã¸ã®ãƒªãƒ³ã‚¯ãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚例ã¨ã—ã¦ã¯ã€`community.docker collection repo <https://github.com/ansible-collections/community.docker/tree/main/docs/docsite>`_ ã¨`community.docker collection documentation <https://docs.ansible.com/ansible/latest/collections/community/docker/index.html>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_collections_structure.rst:74 +#: ../../rst/dev_guide/developing_collections_structure.rst:76 msgid "Plugin and module documentation" msgstr "プラグインã¨ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ‰ã‚ュメント" -#: ../../rst/dev_guide/developing_collections_structure.rst:76 +#: ../../rst/dev_guide/developing_collections_structure.rst:78 msgid "Keep the specific documentation for plugins and modules embedded as Python docstrings. Use ``ansible-doc`` to view documentation for plugins inside a collection:" msgstr "Python ドã‚ュメント文å—列ã¨ã—ã¦åŸ‹ã‚è¾¼ã¾ã‚ŒãŸãƒ—ラグインãŠã‚ˆã³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«é–¢ã™ã‚‹ç‰¹å®šã®ãƒ‰ã‚ュメントをä¿æŒã—ã¾ã™ã€‚コレクション内ã®ãƒ—ラグインã®ãƒ‰ã‚ュメントを表示ã™ã‚‹ã«ã¯``ansible-doc`` を使用ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_collections_structure.rst:82 +#: ../../rst/dev_guide/developing_collections_structure.rst:84 msgid "The ``ansible-doc`` command requires the fully qualified collection name (FQCN) to display specific plugin documentation. In this example, ``my_namespace`` is the Galaxy namespace and ``my_collection`` is the collection name within that namespace." msgstr "特定ã®ãƒ—ラグインã®ãƒ‰ã‚ュメントを表示ã™ã‚‹ã«ã¯ã€``ansible-doc`` コマンドã«å®Œå…¨ä¿®é£¾ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³å (FQCN) ãŒå¿…è¦ã§ã™ã€‚ã“ã®ä¾‹ã§ã¯ã€``my_namespace`` 㯠Galaxy åå‰ç©ºé–“ã¨ãªã‚Šã€``my_collection`` ã¯ãã®åå‰ç©ºé–“内ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³åã¨ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:84 +#: ../../rst/dev_guide/developing_collections_structure.rst:86 msgid "The Galaxy namespace of an Ansible collection is defined in the ``galaxy.yml`` file. It can be different from the GitHub organization or repository name." msgstr "Ansible コレクション㮠Galaxy åå‰ç©ºé–“㯠``galaxy.yml`` ファイルã§å®šç¾©ã•ã‚Œã¾ã™ã€‚GitHub ã®çµ„ç¹”ã¾ãŸã¯ãƒªãƒã‚¸ãƒˆãƒªãƒ¼åã¨ã¯ç•°ãªã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:89 +#: ../../rst/dev_guide/developing_collections_structure.rst:91 msgid "plugins directory" msgstr "plugins ディレクトリー" -#: ../../rst/dev_guide/developing_collections_structure.rst:91 +#: ../../rst/dev_guide/developing_collections_structure.rst:93 msgid "Add a 'per plugin type' specific subdirectory here, including ``module_utils`` which is usable not only by modules, but by most plugins by using their FQCN. This is a way to distribute modules, lookups, filters, and so on without having to import a role in every play." msgstr "「プラグインタイプã”ã¨ã€ã®ç‰¹æœ‰ã‚µãƒ–ディレクトリーをã“ã“ã«è¿½åŠ ã—ã¾ã™ã€‚ã“ã‚Œã«ã¯ã€ãã® FQCN を使用ã—ã¦ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã§ã ã‘ã§ãªãã»ã¨ã‚“ã©ã®ãƒ—ラグインã§ä½¿ç”¨ã§ãã‚‹ ``module_utils`` ãŒå«ã¾ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ã€ã™ã¹ã¦ã®ãƒ—レイã§ãƒãƒ¼ãƒ«ã‚’インãƒãƒ¼ãƒˆã™ã‚‹ã“ã¨ãªãモジュールã€æ¤œç´¢ã€ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ãªã©ã‚’分散ã™ã‚‹æ–¹æ³•ã§ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:93 +#: ../../rst/dev_guide/developing_collections_structure.rst:95 msgid "Vars plugins are unsupported in collections. Cache plugins may be used in collections for fact caching, but are not supported for inventory plugins." msgstr "コレクションã§ã¯ã€vars プラグインã¯ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã¾ã›ã‚“。cache プラグインã¯ãƒ•ã‚¡ã‚¯ãƒˆã‚ャッシュã®ãŸã‚ã«ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã§ä½¿ç”¨ã§ãã¾ã™ãŒã€inventory プラグインã§ã¯ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã¾ã›ã‚“。" -#: ../../rst/dev_guide/developing_collections_structure.rst:100 +#: ../../rst/dev_guide/developing_collections_structure.rst:102 msgid "When coding with ``module_utils`` in a collection, the Python ``import`` statement needs to take into account the FQCN along with the ``ansible_collections`` convention. The resulting Python import will look like ``from ansible_collections.{namespace}.{collection}.plugins.module_utils.{util} import {something}``" msgstr "コレクション㧠``module_utils`` を使用ã—ã¦ã‚³ãƒ¼ãƒ‡ã‚£ãƒ³ã‚°ã™ã‚‹å ´åˆã€Python ã® ``import`` ステートメント㯠``ansible_collections`` è¦å‰‡ã¨ã¨ã‚‚ã« FQCN を考慮ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚作æˆã•ã‚Œã‚‹ Python インãƒãƒ¼ãƒˆã¯ ``from ansible_collections.{namespace}.{collection}.plugins.module_utils.{util} import {something}`` ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:102 +#: ../../rst/dev_guide/developing_collections_structure.rst:104 msgid "The following example snippets show a Python and PowerShell module using both default Ansible ``module_utils`` and those provided by a collection. In this example the namespace is ``community``, the collection is ``test_collection``. In the Python example the ``module_util`` in question is called ``qradar`` such that the FQCN is ``community.test_collection.plugins.module_utils.qradar``:" msgstr "以下ã®ã‚¹ãƒ‹ãƒšãƒƒãƒˆã®ä¾‹ã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã® Ansible ``module_utils`` ã¨ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ä¸¡æ–¹ã‚’使用ã™ã‚‹ Python ãŠã‚ˆã³ PowerShell モジュールを示ã—ã¦ã„ã¾ã™ã€‚ã“ã®ä¾‹ã§ã¯ã€åå‰ç©ºé–“㯠``community`` ã§ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã¯ ``test_collection`` ã§ã™ã€‚Python ã®ä¾‹ã§ã¯ã€å•é¡Œã® ``module_util`` 㯠``qradar`` ã¨å‘¼ã°ã‚Œã€FQCN ㌠``community.test_collection.plugins.module_utils.qradar`` ã¨ãªã£ã¦ã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:132 +#: ../../rst/dev_guide/developing_collections_structure.rst:134 msgid "Note that importing something from an ``__init__.py`` file requires using the file name:" msgstr "``__init__.py`` ファイルã‹ã‚‰ä½•ã‹ã‚’インãƒãƒ¼ãƒˆã™ã‚‹å ´åˆã¯ã€ãƒ•ã‚¡ã‚¤ãƒ«åを使用ã™ã‚‹å¿…è¦ãŒã‚ã‚‹ã“ã¨ã«æ³¨æ„ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_collections_structure.rst:138 +#: ../../rst/dev_guide/developing_collections_structure.rst:140 msgid "In the PowerShell example the ``module_util`` in question is called ``hyperv`` such that the FQCN is ``community.test_collection.plugins.module_utils.hyperv``:" msgstr "PowerShell ã®ä¾‹ã§ã¯ã€å•é¡Œã® ``module_util`` 㯠``hyperv`` ã¨å‘¼ã°ã‚Œã€FQCN ㌠``community.test_collection.plugins.module_utils.hyperv`` ã¨ãªã£ã¦ã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:160 +#: ../../rst/dev_guide/developing_collections_structure.rst:162 msgid "roles directory" msgstr "roles ディレクトリー" -#: ../../rst/dev_guide/developing_collections_structure.rst:162 +#: ../../rst/dev_guide/developing_collections_structure.rst:164 msgid "Collection roles are mostly the same as existing roles, but with a couple of limitations:" msgstr "コレクションãƒãƒ¼ãƒ«ã¯æ—¢å˜ãƒãƒ¼ãƒ«ã¨ã»ã¼åŒã˜ã§ã™ãŒã€ã„ãã¤ã‹åˆ¶é™ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:164 +#: ../../rst/dev_guide/developing_collections_structure.rst:166 msgid "Role names are now limited to contain only lowercase alphanumeric characters, plus ``_`` and start with an alpha character." msgstr "ãƒãƒ¼ãƒ«åã¯ã€å°æ–‡å—ã®è‹±æ•°å—㨠``_`` ã®ã¿ã‚’å«ã¿ã€è‹±å—ã§é–‹å§‹ã™ã‚‹ã‚ˆã†ã«åˆ¶é™ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:165 +#: ../../rst/dev_guide/developing_collections_structure.rst:167 msgid "Roles in a collection cannot contain plugins any more. Plugins must live in the collection ``plugins`` directory tree. Each plugin is accessible to all roles in the collection." msgstr "コレクション内ã®ãƒãƒ¼ãƒ«ã«ã¯ãƒ—ラグインをå«ã‚ã‚‹ã“ã¨ãŒã§ãã¾ã›ã‚“。プラグインã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``plugins`` ディレクトリーツリーã§æŒç¶šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚å„プラグインã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³å†…ã®ã™ã¹ã¦ã®ãƒãƒ¼ãƒ«ã‹ã‚‰ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:167 +#: ../../rst/dev_guide/developing_collections_structure.rst:169 msgid "The directory name of the role is used as the role name. Therefore, the directory name must comply with the above role name rules. The collection import into Galaxy will fail if a role name does not comply with these rules." msgstr "ãƒãƒ¼ãƒ«ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼åã¯ãƒãƒ¼ãƒ«åã¨ã—ã¦ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚ãã®ãŸã‚ã€ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼åã¯ä¸Šè¨˜ã®ãƒãƒ¼ãƒ«åルールã«å¾“ã†å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚Galaxy ã¸ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ã‚¤ãƒ³ãƒãƒ¼ãƒˆã¯ã€ãƒãƒ¼ãƒ«åãŒã“れらã®ãƒ«ãƒ¼ãƒ«ã«æº–æ‹ ã—ã¦ã„ãªã„ã¨å¤±æ•—ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:169 +#: ../../rst/dev_guide/developing_collections_structure.rst:171 msgid "You can migrate 'traditional roles' into a collection but they must follow the rules above. You may need to rename roles if they don't conform. You will have to move or link any role-based plugins to the collection specific directories." msgstr "「従æ¥ã®ãƒãƒ¼ãƒ«ã€ã‚’コレクションã«ç§»è¡Œã§ãã¾ã™ãŒã€ä¸Šè¨˜ã®ãƒ«ãƒ¼ãƒ«ã«å¾“ã†å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚éµå®ˆã—ã¦ã„ãªã„å ´åˆã¯ã€ãƒãƒ¼ãƒ«ã®åå‰ã‚’変更ã—ãªã‘ã‚Œã°ãªã‚‰ãªã„å ´åˆã‚‚ã‚ã‚Šã¾ã™ã€‚ãƒãƒ¼ãƒ«ãƒ™ãƒ¼ã‚¹ã®ãƒ—ラグインをコレクション固有ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ç§»å‹•ã™ã‚‹ã‹ã€ãƒªãƒ³ã‚¯ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:173 +#: ../../rst/dev_guide/developing_collections_structure.rst:175 msgid "For roles imported into Galaxy directly from a GitHub repository, setting the ``role_name`` value in the role's metadata overrides the role name used by Galaxy. For collections, that value is ignored. When importing a collection, Galaxy uses the role directory as the name of the role and ignores the ``role_name`` metadata value." msgstr "ãƒãƒ¼ãƒ«ãŒ GitHub リãƒã‚¸ãƒˆãƒªãƒ¼ã‹ã‚‰ Galaxy ã«ç›´æŽ¥ã‚¤ãƒ³ãƒãƒ¼ãƒˆã•ã‚ŒãŸå ´åˆã¯ã€ãƒãƒ¼ãƒ«ã®ãƒ¡ã‚¿ãƒ‡ãƒ¼ã‚¿ã« ``role_name`` 値をè¨å®šã™ã‚‹ã¨ã€Galaxy ãŒä½¿ç”¨ã™ã‚‹ãƒãƒ¼ãƒ«åãŒä¸Šæ›¸ãã•ã‚Œã¾ã™ã€‚コレクションã®å ´åˆã€ã“ã®å€¤ã¯ç„¡è¦–ã•ã‚Œã¾ã™ã€‚コレクションをインãƒãƒ¼ãƒˆã™ã‚‹ã¨ã€Galaxy ã¯ãƒãƒ¼ãƒ«ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã‚’ãƒãƒ¼ãƒ«åã¨ã—ã¦ä½¿ç”¨ã—ã€``role_name`` メタデータã®å€¤ã‚’無視ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:176 +#: ../../rst/dev_guide/developing_collections_structure.rst:178 msgid "playbooks directory" msgstr "playbooks ディレクトリー" -#: ../../rst/dev_guide/developing_collections_structure.rst:178 +#: ../../rst/dev_guide/developing_collections_structure.rst:180 msgid "In prior releases, you could reference playbooks in this directory using the full path to the playbook file from the command line. In ansible-core 2.11 and later, you can use the FQCN, ``namespace.collection.playbook`` (with or without extension), to reference the playbooks from the command line or from ``import_playbook``. This will keep the playbook in 'collection context', as if you had added ``collections: [ namespace.collection ]`` to it." msgstr "以å‰ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã‹ã‚‰Playbookファイルã®ãƒ•ãƒ«ãƒ‘スを使用ã—ã¦ã€ã“ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã®Playbookã‚’å‚ç…§ã™ã‚‹ã“ã¨ãŒã§ãã¾ã—ãŸã€‚ansible-core 2.11以é™ã§ã¯ã€FQCNã§ã‚ã‚‹``namespace.collection.playbook`` （拡張åã‚ã‚Šã€ãªã—）を使ã£ã¦ã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã¾ãŸã¯``import_playbook`` ã‹ã‚‰Playbookã‚’å‚ç…§ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ã‚ãŸã‹ã‚‚``collections: [ namespace.collection ]`` ã‚’è¿½åŠ ã—ãŸã‹ã®ã‚ˆã†ã«ã€PlaybookãŒã€Œã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚³ãƒ³ãƒ†ã‚ストã€ã«ä¿ãŸã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:182 +#: ../../rst/dev_guide/developing_collections_structure.rst:184 msgid "You can have most of the subdirectories you would expect, such ``files/``, ``vars/`` or ``templates/`` but no ``roles/`` since those are handled already in the collection." msgstr "``files/`` ã€``vars/`` ã€``templates/`` ãªã©ã€æœŸå¾…ã•ã‚Œã‚‹ã»ã¨ã‚“ã©ã®ã‚µãƒ–ディレクトリをæŒã¤ã“ã¨ãŒã§ãã¾ã™ãŒã€``roles/`` ã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã§ã™ã§ã«æ‰±ã‚ã‚Œã¦ã„ã‚‹ãŸã‚ã€æŒã¤ã“ã¨ã¯ã§ãã¾ã›ã‚“。" -#: ../../rst/dev_guide/developing_collections_structure.rst:187 +#: ../../rst/dev_guide/developing_collections_structure.rst:189 msgid "tests directory" msgstr "tests ディレクトリー" -#: ../../rst/dev_guide/developing_collections_structure.rst:189 +#: ../../rst/dev_guide/developing_collections_structure.rst:191 msgid "Ansible Collections are tested much like Ansible itself, by using the `ansible-test` utility which is released as part of Ansible, version 2.9.0 and newer. Because Ansible Collections are tested using the same tooling as Ansible itself, via `ansible-test`, all Ansible developer documentation for testing is applicable for authoring Collections Tests with one key concept to keep in mind." msgstr "Ansible Collection ã¯ã€Ansible 自体ã¨åŒã˜ã‚ˆã†ã«ã€Ansible ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.9.0 以é™ã«åŒæ¢±ã•ã‚Œã‚‹ `ansible-test` ユーティリティーを使用ã—ã¦ãƒ†ã‚¹ãƒˆã•ã‚Œã¾ã™ã€‚Ansible コレクション㯠Ansible 自体ã¨åŒã˜ãƒ„ールを使用ã—ã¦ãƒ†ã‚¹ãƒˆã•ã‚Œã‚‹ãŸã‚ã€`ansible-test` を介ã—ã¦ã€ãƒ†ã‚¹ãƒˆç”¨ã®ã™ã¹ã¦ã® Ansible 開発者å‘ã‘ドã‚ュメントã¯ã€è¦šãˆã¦ãŠãã¹ã 1 ã¤ã®é‡è¦ãªæ¦‚念を使用ã—ã¦ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãƒ†ã‚¹ãƒˆã‚’作æˆã™ã‚‹ãŸã‚ã«é©ç”¨ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:191 +#: ../../rst/dev_guide/developing_collections_structure.rst:193 msgid "See :ref:`testing_collections` for specific information on how to test collections with ``ansible-test``." msgstr "``ansible-test`` ã§ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’テストã™ã‚‹æ–¹æ³•ã¯ã€ã€Œ:ref:`testing_collections`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_collections_structure.rst:193 +#: ../../rst/dev_guide/developing_collections_structure.rst:195 msgid "When reading the :ref:`developing_testing` documentation, there will be content that applies to running Ansible from source code via a git clone, which is typical of an Ansible developer. However, it's not always typical for an Ansible Collection author to be running Ansible from source but instead from a stable release, and to create Collections it is not necessary to run Ansible from source. Therefore, when references of dealing with `ansible-test` binary paths, command completion, or environment variables are presented throughout the :ref:`developing_testing` documentation; keep in mind that it is not needed for Ansible Collection Testing because the act of installing the stable release of Ansible containing `ansible-test` is expected to setup those things for you." msgstr ":ref:`developing_testing` ã®ãƒ‰ã‚ュメントをèªã‚€éš›ã€Ansible 開発者ã®å…¸åž‹çš„㪠git clone を使用ã—ã¦ã€ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã‹ã‚‰ Ansible を実行ã™ã‚‹ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ãŒã‚ã‚Šã¾ã™ã€‚ãŸã ã—ã€Ansible Collection ã®ä½œæˆè€…ãŒã‚½ãƒ¼ã‚¹ã‹ã‚‰ Ansible を実行ã™ã‚‹ã“ã¨ã¯å¸¸ã«ä¸€èˆ¬çš„ã§ã¯ãªãã€å®‰å®šã—ãŸãƒªãƒªãƒ¼ã‚¹ã‹ã‚‰ã§ã¯ãªãã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’作æˆã™ã‚‹ã«ã¯ã€ã‚½ãƒ¼ã‚¹ã‹ã‚‰ Ansible を実行ã™ã‚‹å¿…è¦ã¯ã‚ã‚Šã¾ã›ã‚“。ãã®ãŸã‚ã€`ansible-test` ãƒã‚¤ãƒŠãƒªãƒ¼ãƒ‘スã€ã‚³ãƒžãƒ³ãƒ‰è£œå®Œã€ã¾ãŸã¯ç’°å¢ƒå¤‰æ•°ã«ã¤ã„ã¦ã¯ã€:ref:`developing_testing` ドã‚ュメントã§æ示ã•ã‚Œã¾ã™ã€‚Ansible Collection Testing ã§ã¯ã“ã‚ŒãŒå¿…è¦ã‚ã‚Šã¾ã›ã‚“。`ansible-test` ã‚’å«ã‚€ Ansible ã®å®‰å®šã—ãŸãƒªãƒªãƒ¼ã‚¹ã‚’インストールã™ã‚‹ã«ã¯ã€ã“れらをセットアップã™ã‚‹ã“ã¨ãŒäºˆæƒ³ã•ã‚Œã‚‹ãŸã‚ã§ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:198 +#: ../../rst/dev_guide/developing_collections_structure.rst:200 msgid "meta directory" msgstr "meta ディレクトリー" -#: ../../rst/dev_guide/developing_collections_structure.rst:200 +#: ../../rst/dev_guide/developing_collections_structure.rst:202 msgid "A collection can store some additional metadata in a ``runtime.yml`` file in the collection's ``meta`` directory. The ``runtime.yml`` file supports the top level keys:" msgstr "コレクションã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``meta`` ディレクトリー㮠``runtime.yml`` ファイルã«è¿½åŠ ã®ãƒ¡ã‚¿ãƒ‡ãƒ¼ã‚¿ã‚’ä¿å˜ã§ãã¾ã™ã€‚``runtime.yml`` ファイルã¯ã€æœ€ä¸Šä½ã®ã‚ーをサãƒãƒ¼ãƒˆã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:202 +#: ../../rst/dev_guide/developing_collections_structure.rst:204 msgid "*requires_ansible*:" msgstr "*requires_ansible*:" -#: ../../rst/dev_guide/developing_collections_structure.rst:204 -msgid "The version of Ansible required to use the collection. Multiple versions can be separated with a comma." -msgstr "コレクションを使用ã™ã‚‹ãŸã‚ã«å¿…è¦ãª Ansible ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã€‚複数ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯ã‚³ãƒ³ãƒžã§åŒºåˆ‡ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" +#: ../../rst/dev_guide/developing_collections_structure.rst:206 +msgid "The version of Ansible Core (ansible-core) required to use the collection. Multiple versions can be separated with a comma." +msgstr "コレクションを使用ã™ã‚‹ãŸã‚ã«å¿…è¦ãª Ansible Core (ansible-core)ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã€‚複数ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯ã‚³ãƒ³ãƒžã§åŒºåˆ‡ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:210 +#: ../../rst/dev_guide/developing_collections_structure.rst:212 msgid "although the version is a `PEP440 Version Specifier <https://www.python.org/dev/peps/pep-0440/#version-specifiers>`_ under the hood, Ansible deviates from PEP440 behavior by truncating prerelease segments from the Ansible version. This means that Ansible 2.11.0b1 is compatible with something that ``requires_ansible: \">=2.11\"``." msgstr "ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯ `PEP440 ãƒãƒ¼ã‚¸ãƒ§ãƒ³æŒ‡å®šå <https://www.python.org/dev/peps/pep-0440/#version-specifiers>`_ ã§ã™ãŒã€å†…部ã§ã¯ã€Ansible ã¯ãƒ—レリリースセグメントを Ansible ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‹ã‚‰åˆ‡ã‚Šæ¨ã¦ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€PEP440 ã®å‹•ä½œã‹ã‚‰é€¸è„±ã—ã¦ã„ã¾ã™ã€‚ã“ã‚Œã¯ã€Ansible2.11.0b1 ㌠``requires_ansible: \">=2.11\"`` ã§ã‚ã‚‹ã‚‚ã®ã¨äº’æ›æ€§ãŒã‚ã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:212 +#: ../../rst/dev_guide/developing_collections_structure.rst:214 msgid "*plugin_routing*:" msgstr "*plugin_routing*:" -#: ../../rst/dev_guide/developing_collections_structure.rst:214 +#: ../../rst/dev_guide/developing_collections_structure.rst:216 msgid "Content in a collection that Ansible needs to load from another location or that has been deprecated/removed. The top level keys of ``plugin_routing`` are types of plugins, with individual plugin names as subkeys. To define a new location for a plugin, set the ``redirect`` field to another name. To deprecate a plugin, use the ``deprecation`` field to provide a custom warning message and the removal version or date. If the plugin has been renamed or moved to a new location, the ``redirect`` field should also be provided. If a plugin is being removed entirely, ``tombstone`` can be used for the fatal error message and removal version or date." msgstr "Ansible ãŒåˆ¥ã®å ´æ‰€ã‹ã‚‰èªã¿è¾¼ã‚€å¿…è¦ãŒã‚るコレクション内ã®ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã€ã‚‚ã—ãã¯éžæŽ¨å¥¨ã¨ãªã£ãŸã‹å‰Šé™¤ã•ã‚Œã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ã‚³ãƒ³ãƒ†ãƒ³ãƒ„。``plugin_routing`` ã®æœ€ä¸Šä½ã®ã‚ーã¯ãƒ—ラグインã®ã‚¿ã‚¤ãƒ—ã§ã€å€‹ã€…ã®ãƒ—ラグインåをサブã‚ーã¨ã—ã¦ä½¿ç”¨ã—ã¾ã™ã€‚プラグインã®æ–°ã—ã„å ´æ‰€ã‚’å®šç¾©ã™ã‚‹ã«ã¯ã€``redirect`` フィールドを別ã®åå‰ã«è¨å®šã—ã¾ã™ã€‚プラグインをéžæŽ¨å¥¨ã«ã™ã‚‹ã«ã¯ã€``deprecation`` フィールドを使用ã—ã¦ã‚«ã‚¹ã‚¿ãƒ è¦å‘Šãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã¨å‰Šé™¤ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¾ãŸã¯æ—¥ä»˜ã‚’指定ã—ã¾ã™ã€‚プラグインã®åå‰ãŒå¤‰æ›´ã™ã‚‹ã‹æ–°ã—ã„å ´æ‰€ã«ç§»å‹•ã™ã‚‹å ´åˆã¯ã€``redirect`` フィールドも入力ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚プラグインãŒå®Œå…¨ã«å‰Šé™¤ã•ã‚Œã‚‹å ´åˆã€``tombstone`` ã¯è‡´å‘½çš„ãªã‚¨ãƒ©ãƒ¼ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã€ãŠã‚ˆã³å‰Šé™¤ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¾ãŸã¯æ—¥ä»˜ã«ä½¿ç”¨ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:243 +#: ../../rst/dev_guide/developing_collections_structure.rst:245 msgid "*import_redirection*" msgstr "*import_redirection*" -#: ../../rst/dev_guide/developing_collections_structure.rst:245 +#: ../../rst/dev_guide/developing_collections_structure.rst:247 msgid "A mapping of names for Python import statements and their redirected locations." msgstr "Python インãƒãƒ¼ãƒˆã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆã®åå‰ã¨ãã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã•ã‚ŒãŸå ´æ‰€ã®ãƒžãƒƒãƒ”ング。" -#: ../../rst/dev_guide/developing_collections_structure.rst:253 +#: ../../rst/dev_guide/developing_collections_structure.rst:255 msgid "*action_groups*" msgstr "*action_groups*" -#: ../../rst/dev_guide/developing_collections_structure.rst:255 +#: ../../rst/dev_guide/developing_collections_structure.rst:257 msgid "A mapping of groups and the list of action plugin and module names they contain. They may also have a special 'metadata' dictionary in the list, which can be used to include actions from other groups." msgstr "グループã¨ã€ãã‚Œã«å«ã¾ã‚Œã‚‹ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ãƒ—ラグインãŠã‚ˆã³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«åã®ãƒªã‚¹ãƒˆã®ãƒžãƒƒãƒ”ングã§ã™ã€‚ã¾ãŸã€ãƒªã‚¹ãƒˆã®ä¸ã«ç‰¹åˆ¥ãªã€Œãƒ¡ã‚¿ãƒ‡ãƒ¼ã‚¿ã€ãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼ã‚’æŒã£ã¦ã„ã‚‹å ´åˆã‚‚ã‚ã‚Šã€ã“れを使ã£ã¦ä»–ã®ã‚°ãƒ«ãƒ¼ãƒ—ã®ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ã‚’å«ã‚ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_structure.rst:273 +#: ../../rst/dev_guide/developing_collections_structure.rst:275 msgid ":ref:`distributing_collections`" msgstr ":ref:`distributing_collections`" -#: ../../rst/dev_guide/developing_collections_structure.rst:274 +#: ../../rst/dev_guide/developing_collections_structure.rst:276 msgid "Learn how to package and publish your collection" msgstr "コレクションをパッケージ化ã—ã€å…¬é–‹ã™ã‚‹æ–¹æ³•ã‚’説明ã—ã¾ã™ã€‚" @@ -1954,87 +1954,87 @@ msgid "Compile and sanity tests" msgstr "コンパイルã¨å¥å…¨æ€§ãƒ†ã‚¹ãƒˆ" #: ../../rst/dev_guide/developing_collections_testing.rst:23 -msgid "To run all compile and sanity tests::" +msgid "To run all compile and sanity tests:" msgstr "ã™ã¹ã¦ã®ã‚³ãƒ³ãƒ‘イルãŠã‚ˆã³å¥å…¨æ€§ãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_testing.rst:27 +#: ../../rst/dev_guide/developing_collections_testing.rst:29 msgid "See :ref:`testing_compile` and :ref:`testing_sanity` for more information. See the :ref:`full list of sanity tests <all_sanity_tests>` for details on the sanity tests and how to fix identified issues." msgstr "詳細ã¯ã€:ref:`testing_compile` ãŠã‚ˆã³ :ref:`testing_sanity` ã‚’å‚ç…§ã—ã¦ãã ã•ã„。å¥å…¨æ€§ãƒ†ã‚¹ãƒˆã®è©³ç´°ã¨ã€ç‰¹å®šã•ã‚ŒãŸå•é¡Œã‚’ä¿®æ£ã™ã‚‹æ–¹æ³•ã¯ã€ã€Œ:ref:`å¥å…¨æ€§ãƒ†ã‚¹ãƒˆã®å®Œå…¨ãƒªã‚¹ãƒˆ <all_sanity_tests>`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_collections_testing.rst:30 -#: ../../rst/dev_guide/developing_modules_general.rst:193 +#: ../../rst/dev_guide/developing_collections_testing.rst:32 +#: ../../rst/dev_guide/developing_modules_general.rst:195 msgid "Adding unit tests" msgstr "ユニットテストã®è¿½åŠ " -#: ../../rst/dev_guide/developing_collections_testing.rst:32 +#: ../../rst/dev_guide/developing_collections_testing.rst:34 msgid "You must place unit tests in the appropriate ``tests/unit/plugins/`` directory. For example, you would place tests for ``plugins/module_utils/foo/bar.py`` in ``tests/unit/plugins/module_utils/foo/test_bar.py`` or ``tests/unit/plugins/module_utils/foo/bar/test_bar.py``. For examples, see the `unit tests in community.general <https://github.com/ansible-collections/community.general/tree/master/tests/unit/>`_." msgstr "ユニットテストをé©åˆ‡ãª ``tests/unit/plugins/`` ディレクトリーã«ç½®ãå¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€``tests/unit/plugins/module_utils/foo/test_bar.py`` ã¾ãŸã¯ ``tests/unit/plugins/module_utils/foo/bar/test_bar.py`` ã® ``plugins/module_utils/foo/bar.py`` ã«ãƒ†ã‚¹ãƒˆã‚’ç½®ãã¾ã™ã€‚ãŸã¨ãˆã°ã€`unit tests in community.general <https://github.com/ansible-collections/community.general/tree/master/tests/unit/>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_collections_testing.rst:34 -msgid "To run all unit tests for all supported Python versions::" +#: ../../rst/dev_guide/developing_collections_testing.rst:36 +msgid "To run all unit tests for all supported Python versions:" msgstr "サãƒãƒ¼ãƒˆã•ã‚Œã‚‹ã™ã¹ã¦ã® Python ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«å¯¾ã—ã¦ã€ã™ã¹ã¦ã®ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_testing.rst:38 -msgid "To run all unit tests only for a specific Python version::" +#: ../../rst/dev_guide/developing_collections_testing.rst:42 +msgid "To run all unit tests only for a specific Python version:" msgstr "特定㮠Python ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«å¯¾ã—ã¦ã®ã¿ã€ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã‚’ã™ã¹ã¦å®Ÿè¡Œã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_testing.rst:42 -msgid "To run only a specific unit test::" +#: ../../rst/dev_guide/developing_collections_testing.rst:48 +msgid "To run only a specific unit test:" msgstr "特定ã®ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã®ã¿ã‚’実行ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_testing.rst:46 +#: ../../rst/dev_guide/developing_collections_testing.rst:54 msgid "You can specify Python requirements in the ``tests/unit/requirements.txt`` file. See :ref:`testing_units` for more information, especially on fixture files." msgstr "``tests/unit/requirements.txt`` ファイル㧠Python è¦ä»¶ã‚’指定ã§ãã¾ã™ã€‚詳細 (特ã«ãƒ•ã‚£ã‚¯ã‚¹ãƒãƒ£ãƒ¼ãƒ•ã‚¡ã‚¤ãƒ«ã®è©³ç´°) ã¯ã€ã€Œ:ref:`testing_units`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_collections_testing.rst:49 +#: ../../rst/dev_guide/developing_collections_testing.rst:57 msgid "Adding integration tests" msgstr "çµ±åˆãƒ†ã‚¹ãƒˆã®è¿½åŠ " -#: ../../rst/dev_guide/developing_collections_testing.rst:51 +#: ../../rst/dev_guide/developing_collections_testing.rst:59 msgid "You must place integration tests in the appropriate ``tests/integration/targets/`` directory. For module integration tests, you can use the module name alone. For example, you would place integration tests for ``plugins/modules/foo.py`` in a directory called ``tests/integration/targets/foo/``. For non-module plugin integration tests, you must add the plugin type to the directory name. For example, you would place integration tests for ``plugins/connections/bar.py`` in a directory called ``tests/integration/targets/connection_bar/``. For lookup plugins, the directory must be called ``lookup_foo``, for inventory plugins, ``inventory_foo``, and so on." msgstr "çµ±åˆãƒ†ã‚¹ãƒˆã¯ã€é©åˆ‡ãª ``tests/integration/targets/`` ディレクトリーã«ç½®ãå¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚モジュールã®çµ±åˆãƒ†ã‚¹ãƒˆã§ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«åã ã‘を使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€``plugins/modules/foo.py`` ã®çµ±åˆãƒ†ã‚¹ãƒˆã‚’ ``tests/integration/targets/foo/`` ã¨ã„ã†ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ç½®ãã“ã¨ã«ãªã‚Šã¾ã™ã€‚モジュール以外ã®ãƒ—ラグインã®çµ±åˆãƒ†ã‚¹ãƒˆã§ã¯ã€ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼åã«ãƒ—ãƒ©ã‚°ã‚¤ãƒ³ã‚¿ã‚¤ãƒ—ã‚’è¿½åŠ ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€``plugins/connections/bar.py`` ã®çµ±åˆãƒ†ã‚¹ãƒˆã¯ã€``tests/integration/targets/connection_bar/`` ã¨ã„ã†ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ç½®ãã“ã¨ã«ãªã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€ãƒ«ãƒƒã‚¯ã‚¢ãƒƒãƒ—プラグインã®å ´åˆã€ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼å㯠``lookup_foo`` ã¨ãªã‚Šã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ—ラグインã®å ´åˆã¯ã€``inventory_foo`` ã¨ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_testing.rst:53 +#: ../../rst/dev_guide/developing_collections_testing.rst:61 msgid "You can write two different kinds of integration tests:" msgstr "2 種類ã®çµ±åˆãƒ†ã‚¹ãƒˆã‚’作æˆã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_testing.rst:55 +#: ../../rst/dev_guide/developing_collections_testing.rst:63 msgid "Ansible role tests run with ``ansible-playbook`` and validate various aspects of the module. They can depend on other integration tests (usually named ``prepare_bar`` or ``setup_bar``, which prepare a service or install a requirement named ``bar`` in order to test module ``foo``) to set-up required resources, such as installing required libraries or setting up server services." msgstr "Ansible ãƒãƒ¼ãƒ«ãƒ†ã‚¹ãƒˆã¯ã€``ansible-playbook`` ã§å®Ÿè¡Œã•ã‚Œã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ã•ã¾ã–ã¾ãªå´é¢ã‚’検証ã—ã¾ã™ã€‚ã“れらã®ãƒ†ã‚¹ãƒˆã¯ã€ä»–ã®çµ±åˆãƒ†ã‚¹ãƒˆ (通常 ``prepare_bar`` ã¾ãŸã¯ ``setup_bar`` ã¨å‘¼ã°ã‚Œã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``foo`` をテストã™ã‚‹ãŸã‚ã«ã‚µãƒ¼ãƒ“スを準備ã—ãŸã‚Šã€``bar`` ã¨ã„ã†è¦ä»¶ã‚’インストールã—ãŸã‚Šã™ã‚‹) ã«ä¾å˜ã—ã¦ã€å¿…è¦ãªãƒ©ã‚¤ãƒ–ラリーã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã‚„サーãƒãƒ¼ã‚µãƒ¼ãƒ“スã®è¨å®šãªã©ã€å¿…è¦ãªãƒªã‚½ãƒ¼ã‚¹ã‚’è¨å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_testing.rst:56 +#: ../../rst/dev_guide/developing_collections_testing.rst:64 msgid "``runme.sh`` tests run directly as scripts. They can set up inventory files, and execute ``ansible-playbook`` or ``ansible-inventory`` with various settings." msgstr "``runme.sh`` テストã¯ã€ç›´æŽ¥ã‚¹ã‚¯ãƒªãƒ—トã¨ã—ã¦å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚インベントリーファイルをè¨å®šã—ã€ã•ã¾ã–ã¾ãªè¨å®šã§ ``ansible-playbook`` ã¾ãŸã¯ ``ansible-inventory`` を実行ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_testing.rst:58 +#: ../../rst/dev_guide/developing_collections_testing.rst:66 msgid "For examples, see the `integration tests in community.general <https://github.com/ansible-collections/community.general/tree/master/tests/integration/targets/>`_. See also :ref:`testing_integration` for more details." msgstr "例ã«ã¤ã„ã¦ã¯ã€ã€Œ`community.general ã®çµ±åˆãƒ†ã‚¹ãƒˆ <https://github.com/ansible-collections/community.general/tree/master/tests/integration/targets/>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。詳細ã¯ã€ã€Œ:ref:`testing_integration`ã€ã‚‚å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_collections_testing.rst:60 +#: ../../rst/dev_guide/developing_collections_testing.rst:68 msgid "Since integration tests can install requirements, and set-up, start and stop services, we recommended running them in docker containers or otherwise restricted environments whenever possible. By default, ``ansible-test`` supports Docker images for several operating systems. See the `list of supported docker images <https://github.com/ansible/ansible/blob/devel/test/lib/ansible_test/_data/completion/docker.txt>`_ for all options. Use the ``default`` image mainly for platform-independent integration tests, such as those for cloud modules. The following examples use the ``centos8`` image." msgstr "çµ±åˆãƒ†ã‚¹ãƒˆã¯ã€è¦ä»¶ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã‚„ã€ã‚µãƒ¼ãƒ“スã®è¨å®šã€é–‹å§‹ã€ãŠã‚ˆã³åœæ¢ã‚’è¡Œã†ã“ã¨ãŒã§ãã‚‹ãŸã‚ã€å¯èƒ½ãªé™ã‚Šã€Docker コンテナーやã€åˆ¶é™ã•ã‚ŒãŸç’°å¢ƒã§å®Ÿè¡Œã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚デフォルトã§ã¯ã€``ansible-test`` ã¯è¤‡æ•°ã®ã‚ªãƒšãƒ¬ãƒ¼ãƒ†ã‚£ãƒ³ã‚°ã‚·ã‚¹ãƒ†ãƒ ã® Docker イメージをサãƒãƒ¼ãƒˆã—ã¾ã™ã€‚ã™ã¹ã¦ã®ã‚ªãƒ—ション㯠`サãƒãƒ¼ãƒˆå¯¾è±¡ã® docker イメージ <https://github.com/ansible/ansible/blob/devel/test/lib/ansible_test/_data/completion/docker.txt>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。クラウドモジュール用ãªã©ã®ãƒ—ラットフォームã«ä¾å˜ã—ãªã„çµ±åˆãƒ†ã‚¹ãƒˆã«ã¯ã€ä¸»ã« ``default`` イメージを使用ã—ã¾ã™ã€‚以下ã®ä¾‹ã§ã¯ã€``centos8`` イメージãŒä½¿ç”¨ã•ã‚Œã¦ã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_testing.rst:62 -msgid "To execute all integration tests for a collection::" +#: ../../rst/dev_guide/developing_collections_testing.rst:70 +msgid "To execute all integration tests for a collection:" msgstr "コレクションã«å¯¾ã—ã¦çµ±åˆãƒ†ã‚¹ãƒˆã‚’ã™ã¹ã¦å®Ÿè¡Œã™ã‚‹ã«ã¯ã€æ¬¡ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_testing.rst:66 +#: ../../rst/dev_guide/developing_collections_testing.rst:76 msgid "If you want more detailed output, run the command with ``-vvv`` instead of ``-v``. Alternatively, specify ``--retry-on-error`` to automatically re-run failed tests with higher verbosity levels." msgstr "より詳細ãªå‡ºåŠ›ãŒå¿…è¦ãªå ´åˆã¯ã€``-v`` ã§ã¯ãªãã€``-vvv`` ã§ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚ã‚‚ã—ãã¯ã€``--retry-on-error`` を指定ã—ã¦ã€å¤±æ•—ã—ãŸãƒ†ã‚¹ãƒˆã‚’ã€è©³ç´°ãƒ¬ãƒ™ãƒ«ã‚’ã‚ã’ã¦è‡ªå‹•çš„ã«å†å®Ÿè¡Œã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_testing.rst:68 -msgid "To execute only the integration tests in a specific directory::" +#: ../../rst/dev_guide/developing_collections_testing.rst:78 +msgid "To execute only the integration tests in a specific directory:" msgstr "特定ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã§çµ±åˆãƒ†ã‚¹ãƒˆã®ã¿ã‚’実行ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_testing.rst:72 +#: ../../rst/dev_guide/developing_collections_testing.rst:84 msgid "You can specify multiple target names. Each target name is the name of a directory in ``tests/integration/targets/``." msgstr "複数ã®ã‚¿ãƒ¼ã‚²ãƒƒãƒˆåを指定ã§ãã¾ã™ã€‚ターゲットå㯠``tests/integration/targets/`` ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã®åå‰ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_collections_testing.rst:76 +#: ../../rst/dev_guide/developing_collections_testing.rst:88 msgid ":ref:`developing_testing`" msgstr ":ref:`developing_testing`" -#: ../../rst/dev_guide/developing_collections_testing.rst:77 +#: ../../rst/dev_guide/developing_collections_testing.rst:89 msgid "More resources on testing Ansible" msgstr "Ansible ã®ãƒ†ã‚¹ãƒˆã«é–¢ã™ã‚‹ãã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹" @@ -2047,7 +2047,7 @@ msgid "Although ``ansible-core`` (the code hosted in the `ansible/ansible reposi msgstr "``ansible-core`` (GitHub ã® `ansible/ansible リãƒã‚¸ãƒˆãƒªãƒ¼ <https://github.com/ansible/ansible>`_ ã§ãƒ›ã‚¹ãƒˆã•ã‚Œã‚‹ã‚³ãƒ¼ãƒ‰) ã«ã¯ã€Playbook ディレクティブã¾ãŸã¯è¨å®šã‚’介ã—ã¦ã‚¹ãƒ¯ãƒƒãƒ—ã§ãるプラグインãŒå«ã¾ã‚Œã¦ã„ã¾ã™ãŒã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«åŒ–ã•ã‚Œãªã„コードãŒå¤šãã‚ã‚Šã¾ã™ã€‚ã¾ãŸã€``ansible-core`` ã®ä¸€éƒ¨ãŒé€£æºã™ã‚‹æ–¹æ³•ã«é–¢ã™ã‚‹ãƒ‰ã‚ュメントã§ã™ã€‚" #: ../../rst/dev_guide/developing_core.rst:14 -#: ../../rst/dev_guide/developing_inventory.rst:466 +#: ../../rst/dev_guide/developing_inventory.rst:473 #: ../../rst/dev_guide/developing_plugins.rst:538 msgid ":ref:`developing_api`" msgstr ":ref:`developing_api`" @@ -2337,62 +2337,62 @@ msgid "Inventory scripts must accept the ``--list`` and ``--host <hostname>`` ar msgstr "インベントリースクリプトã§ã¯ã€å¼•æ•° ``--list`` ãŠã‚ˆã³ ``--host <hostname>`` を使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ä»–ã®å¼•æ•°ã¯è¨å®šã§ãã¾ã™ãŒã€Ansible ã¯ãれらを使用ã—ã¾ã›ã‚“。ã“ã®ã‚ˆã†ãªå¼•æ•°ã¯ã€ã‚¹ã‚¯ãƒªãƒ—トを直接実行ã™ã‚‹ã®ã«å½¹ç«‹ã¤å ´åˆãŒã‚ã‚Šã¾ã™ã€‚" #: ../../rst/dev_guide/developing_inventory.rst:363 -msgid "When the script is called with the single argument ``--list``, the script must output to stdout a JSON object that contains all the groups to be managed. Each group's value should be either an object containing a list of each host, any child groups, and potential group variables, or simply a list of hosts::" +msgid "When the script is called with the single argument ``--list``, the script must output to stdout a JSON object that contains all the groups to be managed. Each group's value should be either an object containing a list of each host, any child groups, and potential group variables, or simply a list of hosts:" msgstr "スクリプトãŒå˜ä¸€ã®å¼•æ•° ``--list`` ã§å‘¼ã³å‡ºã•ã‚Œã‚‹ã¨ã€ã‚¹ã‚¯ãƒªãƒ—トã¯ã€æ¨™æº–出力ã«ã€ç®¡ç†ã™ã‚‹ã™ã¹ã¦ã®ã‚°ãƒ«ãƒ¼ãƒ—ãŒå«ã¾ã‚Œã‚‹ JSON オブジェクトを出力ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚å„グループã®å€¤ã¯ã€å„ホストã€åグループã€ãŠã‚ˆã³æ½œåœ¨çš„ãªã‚°ãƒ«ãƒ¼ãƒ—変数ã®ä¸€è¦§ã‚’å«ã‚€ã‚ªãƒ–ジェクトã€ã¾ãŸã¯ç°¡å˜ã«ãƒ›ã‚¹ãƒˆã®ä¸€è¦§ã«ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_inventory.rst:384 +#: ../../rst/dev_guide/developing_inventory.rst:386 msgid "If any of the elements of a group are empty, they may be omitted from the output." msgstr "グループã®ã„ãšã‚Œã‹ã®è¦ç´ ãŒç©ºã®å ´åˆã¯ã€å‡ºåŠ›ã‹ã‚‰çœç•¥ã•ã‚Œã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_inventory.rst:386 -msgid "When called with the argument ``--host <hostname>`` (where <hostname> is a host from above), the script must print a JSON object, either empty or containing variables to make them available to templates and playbooks. For example::" +#: ../../rst/dev_guide/developing_inventory.rst:388 +msgid "When called with the argument ``--host <hostname>`` (where <hostname> is a host from above), the script must print a JSON object, either empty or containing variables to make them available to templates and playbooks. For example:" msgstr "引数 ``--host <hostname>`` ã§å‘¼ã³å‡ºã•ã‚Œã‚‹å ´åˆ (<hostname> ã¯ä¸Šè¨˜ã®ãƒ›ã‚¹ãƒˆ) ã§å‘¼ã³å‡ºã•ã‚Œã‚‹ã¨ã€ã‚¹ã‚¯ãƒªãƒ—トã¯ã€ç©ºã‹ã€å¤‰æ•°ã‚’å«ã‚€ JSON オブジェクトを出力ã—ã¦ã€ãƒ†ãƒ³ãƒ—レート㨠Playbook ã§åˆ©ç”¨å¯èƒ½ã«ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_inventory.rst:394 +#: ../../rst/dev_guide/developing_inventory.rst:397 msgid "Printing variables is optional. If the script does not print variables, it should print an empty JSON object." msgstr "変数ã®å‡ºåŠ›ã¯ä»»æ„ã§ã™ã€‚スクリプトãŒå¤‰æ•°ã‚’出力ã—ãªã„å ´åˆã¯ã€ç©ºã® JSON オブジェクトを出力ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_inventory.rst:399 +#: ../../rst/dev_guide/developing_inventory.rst:402 msgid "Tuning the external inventory script" msgstr "外部インベントリースクリプトã®ãƒãƒ¥ãƒ¼ãƒ‹ãƒ³ã‚°" -#: ../../rst/dev_guide/developing_inventory.rst:403 +#: ../../rst/dev_guide/developing_inventory.rst:406 msgid "The stock inventory script system mentioned above works for all versions of Ansible, but calling ``--host`` for every host can be rather inefficient, especially if it involves API calls to a remote subsystem." msgstr "上記ã®ã‚¹ãƒˆãƒƒã‚¯ã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚¹ã‚¯ãƒªãƒ—トシステムã¯ã€ã™ã¹ã¦ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Ansible ã«å¯¾ã—ã¦å‹•ä½œã—ã¾ã™ãŒã€ç‰¹ã«ãƒªãƒ¢ãƒ¼ãƒˆã‚µãƒ–システムã¸ã® API 呼ã³å‡ºã—ãŒå¿…è¦ã«ãªã‚‹å ´åˆã¯ã€ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã«å¯¾ã—㦠``--host`` を呼ã³å‡ºã™ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_inventory.rst:405 +#: ../../rst/dev_guide/developing_inventory.rst:408 msgid "To avoid this inefficiency, if the inventory script returns a top-level element called \"_meta\", it is possible to return all the host variables in a single script execution. When this meta element contains a value for \"hostvars\", the inventory script will not be invoked with ``--host`` for each host. This behavior results in a significant performance increase for large numbers of hosts." msgstr "ã“れを回é¿ã™ã‚‹ã«ã¯ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚¹ã‚¯ãƒªãƒ—トãŒã€Œ_metaã€ã¨ã„ã†æœ€ä¸Šä½ã®è¦ç´ ã‚’è¿”ã™å ´åˆã«ã¯ã€å˜ä¸€ã‚¹ã‚¯ãƒªãƒ—トã®å®Ÿè¡Œã§ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆå¤‰æ•°ã‚’è¿”ã™ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã®ãƒ¡ã‚¿è¦ç´ ã«ã€Œhostvarsã€ã®å€¤ãŒå«ã¾ã‚Œã¦ã„ã‚‹ã¨ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚¹ã‚¯ãƒªãƒ—トã¯å„ホストã«å¯¾ã—㦠``--host`` ã§å‘¼ã³å‡ºã•ã‚Œã¾ã›ã‚“。ã“ã®å‹•ä½œã¯ã€å¤šæ•°ã®ãƒ›ã‚¹ãƒˆã®ãƒ‘フォーマンスを大幅ã«å‘上ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_inventory.rst:407 -msgid "The data to be added to the top-level JSON object looks like this::" +#: ../../rst/dev_guide/developing_inventory.rst:410 +msgid "The data to be added to the top-level JSON object looks like this:" msgstr "レベル㮠JSON オブジェクトã«è¿½åŠ ã™ã‚‹ãƒ‡ãƒ¼ã‚¿ã¯æ¬¡ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_inventory.rst:426 -msgid "To satisfy the requirements of using ``_meta``, to prevent ansible from calling your inventory with ``--host`` you must at least populate ``_meta`` with an empty ``hostvars`` object. For example::" +#: ../../rst/dev_guide/developing_inventory.rst:431 +msgid "To satisfy the requirements of using ``_meta``, to prevent ansible from calling your inventory with ``--host`` you must at least populate ``_meta`` with an empty ``hostvars`` object. For example:" msgstr "Ansible ㌠``--host`` ã§ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚’呼ã³å‡ºã™ã®ã‚’防ããŸã‚ã« ``_meta`` を使用ã™ã‚‹è¦ä»¶ã‚’満ãŸã™ã«ã¯ã€å°‘ãªãã¨ã‚‚空㮠``hostvars`` オブジェクト㧠``_meta`` を埋ã‚ãªã‘ã‚Œã°ãªã‚Šã¾ã›ã‚“。以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_inventory.rst:442 +#: ../../rst/dev_guide/developing_inventory.rst:449 msgid "If you intend to replace an existing static inventory file with an inventory script, it must return a JSON object which contains an 'all' group that includes every host in the inventory as a member and every group in the inventory as a child. It should also include an 'ungrouped' group which contains all hosts which are not members of any other group. A skeleton example of this JSON object is:" msgstr "æ—¢å˜ã®é™çš„インベントリーファイルをインベントリースクリプトã«ç½®ãæ›ãˆã‚‹å ´åˆã¯ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼å†…ã®ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã‚’メンãƒãƒ¼ã¨ã—ã¦ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼å†…ã®ã™ã¹ã¦ã®ã‚°ãƒ«ãƒ¼ãƒ—ã‚’åã¨ã—ã¦å«ã‚€ã€Œã™ã¹ã¦ã€ã®ã‚°ãƒ«ãƒ¼ãƒ—ã‚’å«ã‚€ JSON オブジェクトを返ã™å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã¾ãŸã€ä»–ã®ã‚°ãƒ«ãƒ¼ãƒ—ã®ãƒ¡ãƒ³ãƒãƒ¼ã§ã¯ãªã„ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã‚’å«ã‚€ã€Œã‚°ãƒ«ãƒ¼ãƒ—化ã•ã‚Œã¦ã„ãªã„ã€ã‚°ãƒ«ãƒ¼ãƒ—ã‚‚å«ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã® JSON オブジェクトã®ã‚¹ã‚±ãƒ«ãƒˆãƒ³ã®ä¾‹ã¯æ¬¡ã®ã¨ãŠã‚Šã§ã™ã€‚" -#: ../../rst/dev_guide/developing_inventory.rst:462 +#: ../../rst/dev_guide/developing_inventory.rst:469 msgid "An easy way to see how this should look is using :ref:`ansible-inventory`, which also supports ``--list`` and ``--host`` parameters like an inventory script would." msgstr "ã“ã‚ŒãŒã©ã®ã‚ˆã†ã«è¦‹ãˆã‚‹ã‹ã‚’確èªã™ã‚‹ç°¡å˜ãªæ–¹æ³•ã¯ã€:ref:`ansible-inventory` を使用ã™ã‚‹ã“ã¨ã§ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚¹ã‚¯ãƒªãƒ—トã®ã‚ˆã†ã« ``--list`` パラメーターãŠã‚ˆã³ ``--host`` パラメーターãŒã‚µãƒãƒ¼ãƒˆã•ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_inventory.rst:467 +#: ../../rst/dev_guide/developing_inventory.rst:474 msgid "Python API to Playbooks and Ad Hoc Task Execution" msgstr "Playbook ãŠã‚ˆã³ã‚¢ãƒ‰ãƒ›ãƒƒã‚¯ã‚¿ã‚¹ã‚¯å®Ÿè¡Œã®ãŸã‚ã® Python API" -#: ../../rst/dev_guide/developing_inventory.rst:469 +#: ../../rst/dev_guide/developing_inventory.rst:476 msgid "Get started with developing a module" msgstr "モジュールã®é–‹ç™ºã‚’始ã‚ã‚‹" -#: ../../rst/dev_guide/developing_inventory.rst:472 +#: ../../rst/dev_guide/developing_inventory.rst:479 msgid "`AWX <https://github.com/ansible/awx>`_" msgstr "`AWX <https://github.com/ansible/awx>`_" -#: ../../rst/dev_guide/developing_inventory.rst:473 +#: ../../rst/dev_guide/developing_inventory.rst:480 msgid "REST API endpoint and GUI for Ansible, syncs with dynamic inventory" msgstr "Ansible ã® REST API エンドãƒã‚¤ãƒ³ãƒˆãŠã‚ˆã³ GUI (動的インベントリーã¨åŒæœŸ)" @@ -2621,50 +2621,50 @@ msgid "Using and developing module utilities" msgstr "モジュールユーティリティーã®ä½¿ç”¨ãŠã‚ˆã³é–‹ç™º" #: ../../rst/dev_guide/developing_module_utilities.rst:7 -msgid "Ansible provides a number of module utilities, or snippets of shared code, that provide helper functions you can use when developing your own modules. The ``basic.py`` module utility provides the main entry point for accessing the Ansible library, and all Python Ansible modules must import something from ``ansible.module_utils``. A common option is to import ``AnsibleModule``::" +msgid "Ansible provides a number of module utilities, or snippets of shared code, that provide helper functions you can use when developing your own modules. The ``basic.py`` module utility provides the main entry point for accessing the Ansible library, and all Python Ansible modules must import something from ``ansible.module_utils``. A common option is to import ``AnsibleModule``:" msgstr "Ansible ã¯ã€ç‹¬è‡ªã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«é–‹ç™ºæ™‚ã«ä½¿ç”¨ã§ãるヘルパー関数をæä¾›ã™ã‚‹å¤šãã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ã€ã¾ãŸã¯å…±æœ‰ã‚³ãƒ¼ãƒ‰ã®ã‚¹ãƒ‹ãƒšãƒƒãƒˆã‚’æä¾›ã—ã¾ã™ã€‚``basic.py`` モジュールユーティリティーã¯ã€Ansible ライブラリーã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ãŸã‚ã®ãƒ¡ã‚¤ãƒ³ã®ã‚¨ãƒ³ãƒˆãƒªãƒ¼ãƒã‚¤ãƒ³ãƒˆã‚’æä¾›ã—ã¾ã™ã€‚ã¾ãŸã€ã™ã¹ã¦ã® Python Ansible モジュール㯠``ansible.module_utils`` ã‹ã‚‰ã‚¤ãƒ³ãƒãƒ¼ãƒˆã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚一般的ãªã‚ªãƒ—ションã§ã¯ã€``AnsibleModule`` をインãƒãƒ¼ãƒˆã™ã‚‹ã®ãŒä¸€èˆ¬çš„ã§ã™ã€‚" -#: ../../rst/dev_guide/developing_module_utilities.rst:15 +#: ../../rst/dev_guide/developing_module_utilities.rst:17 msgid "The ``ansible.module_utils`` namespace is not a plain Python package: it is constructed dynamically for each task invocation, by extracting imports and resolving those matching the namespace against a :ref:`search path <ansible_search_path>` derived from the active configuration." msgstr "``ansible.module_utils`` åå‰ç©ºé–“ã¯å˜ç´”㪠Python パッケージã§ã¯ã‚ã‚Šã¾ã›ã‚“。ã“ã‚Œã¯ã€ã‚¤ãƒ³ãƒãƒ¼ãƒˆã‚’抽出ã—ã€ã‚¢ã‚¯ãƒ†ã‚£ãƒ–ãªè¨å®šã‹ã‚‰æ´¾ç”Ÿã™ã‚‹ :ref:`検索パス <ansible_search_path>` ã«å¯¾ã—ã¦ä¸€è‡´ã™ã‚‹åå‰ç©ºé–“を解決ã™ã‚‹ã“ã¨ã§ã€å„タスク呼ã³å‡ºã—用ã«å‹•çš„ã«æ§‹ç¯‰ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_module_utilities.rst:20 +#: ../../rst/dev_guide/developing_module_utilities.rst:22 msgid "To reduce the maintenance burden in a collection or in local modules, you can extract duplicated code into one or more module utilities and import them into your modules. For example, if you have your own custom modules that import a ``my_shared_code`` library, you can place that into a ``./module_utils/my_shared_code.py`` file like this::" msgstr "コレクションã¾ãŸã¯ãƒãƒ¼ã‚«ãƒ«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹è² è·ã‚’軽減ã™ã‚‹ã«ã¯ã€é‡è¤‡ã‚³ãƒ¼ãƒ‰ã‚’ 1 ã¤ä»¥ä¸Šã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ã«æŠ½å‡ºã—ã¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚¤ãƒ³ãƒãƒ¼ãƒˆã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€``my_shared_code`` ライブラリーをインãƒãƒ¼ãƒˆã™ã‚‹ç‹¬è‡ªã®ã‚«ã‚¹ã‚¿ãƒ モジュールãŒã‚ã‚‹å ´åˆã¯ã€ã“れをã€ä»¥ä¸‹ã®ã‚ˆã†ã« ``./module_utils/my_shared_code.py`` ファイルã«é…ç½®ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_module_utilities.rst:25 +#: ../../rst/dev_guide/developing_module_utilities.rst:27 msgid "When you run ``ansible-playbook``, Ansible will merge any files in your local ``module_utils`` directories into the ``ansible.module_utils`` namespace in the order defined by the :ref:`Ansible search path <ansible_search_path>`." msgstr "``ansible-playbook`` を実行ã™ã‚‹ã¨ã€Ansible 㯠:ref:`Ansible 検索パス <ansible_search_path>` ã§å®šç¾©ã•ã‚Œã¦ã„ã‚‹é †åºã§ãƒãƒ¼ã‚«ãƒ«ã® ``module_utils`` ディレクトリーã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’ ``ansible.module_utils`` åå‰ç©ºé–“ã«ãƒžãƒ¼ã‚¸ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_module_utilities.rst:28 +#: ../../rst/dev_guide/developing_module_utilities.rst:30 msgid "Naming and finding module utilities" msgstr "モジュールユーティリティーã®å‘½åãŠã‚ˆã³æ¤œç´¢" -#: ../../rst/dev_guide/developing_module_utilities.rst:30 +#: ../../rst/dev_guide/developing_module_utilities.rst:32 msgid "You can generally tell what a module utility does from its name and/or its location. Generic utilities (shared code used by many different kinds of modules) live in the main ansible/ansible codebase, in the ``common`` subdirectory or in the root directory of ``lib/ansible/module_utils``. Utilities used by a particular set of modules generally live in the same collection as those modules. For example:" msgstr "通常ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ãŒåå‰ã‚„ãã®å ´æ‰€ã‹ã‚‰å‹•ä½œã™ã‚‹ã‚ˆã†ã«ã§ãã¾ã™ã€‚汎用ユーティリティー (ã•ã¾ã–ã¾ãªç¨®é¡žã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã§ä½¿ç”¨ã•ã‚Œã‚‹å…±æœ‰ã‚³ãƒ¼ãƒ‰) ã¯ã€ãƒ¡ã‚¤ãƒ³ã® ansible/ansible コードベースã«ã‚ã‚Šã¾ã™ã€‚``common`` サブディレクトリーã€ã¾ãŸã¯ ``lib/ansible/module_utils`` ã®ãƒ«ãƒ¼ãƒˆãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ã‚ã‚Šã¾ã™ã€‚特定ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚»ãƒƒãƒˆã§ä½¿ç”¨ã•ã‚Œã‚‹ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ã¯ã€é€šå¸¸ã€ãれらã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¨åŒã˜ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«å˜åœ¨ã—ã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_module_utilities.rst:32 +#: ../../rst/dev_guide/developing_module_utilities.rst:34 msgid "``lib/ansible/module_utils/urls.py`` contains shared code for parsing URLs" msgstr "``lib/ansible/module_utils/urls.py`` ã¯ã€URL を解æžã™ã‚‹ãŸã‚ã®å…±æœ‰ã‚³ãƒ¼ãƒ‰ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_module_utilities.rst:33 +#: ../../rst/dev_guide/developing_module_utilities.rst:35 msgid "``openstack.cloud.plugins.module_utils.openstack.py`` contains utilities for modules that work with OpenStack instances" msgstr "``openstack.cloud.plugins.module_utils.openstack.py`` ã«ã¯ã€OpenStack インスタンスã¨é€£æºã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ãŒå«ã¾ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_module_utilities.rst:34 +#: ../../rst/dev_guide/developing_module_utilities.rst:36 msgid "``ansible.netcommon.plugins.module_utils.network.common.config.py`` contains utility functions for use by networking modules" msgstr "``ansible.netcommon.plugins.module_utils.network.common.config.py`` ã¯ã€ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚ˆã£ã¦ä½¿ç”¨ã•ã‚Œã‚‹è¨å®šãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ã®æ©Ÿèƒ½ãŒå«ã¾ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_module_utilities.rst:36 +#: ../../rst/dev_guide/developing_module_utilities.rst:38 msgid "Following this pattern with your own module utilities makes everything easy to find and use." msgstr "ã“ã®ãƒ‘ターンを独自ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ã§è¡Œã†ã¨ã€ã‚らゆるもã®ã‚’見ã¤ã‘ã€ä½¿ç”¨ã™ã‚‹ã“ã¨ãŒå®¹æ˜“ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_module_utilities.rst:41 +#: ../../rst/dev_guide/developing_module_utilities.rst:43 msgid "Standard module utilities" msgstr "標準ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼" -#: ../../rst/dev_guide/developing_module_utilities.rst:43 +#: ../../rst/dev_guide/developing_module_utilities.rst:45 msgid "Ansible ships with an extensive library of ``module_utils`` files. You can find the module utility source code in the ``lib/ansible/module_utils`` directory under your main Ansible path. We describe the most widely used utilities below. For more details on any specific module utility, please see the `source code for module_utils <https://github.com/ansible/ansible/tree/devel/lib/ansible/module_utils>`_." msgstr "Ansible ã«ã¯ã€``module_utils`` ファイルã®åºƒç¯„ãªãƒ©ã‚¤ãƒ–ラリーãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚モジュールユーティリティーã®ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã¯ã€ãƒ¡ã‚¤ãƒ³ã® Ansible パス下㮠``lib/ansible/module_utils`` ディレクトリーã«ã‚ã‚Šã¾ã™ã€‚ã¾ãŸã€ä»¥ä¸‹ã§æœ€ã‚‚広ã使用ã•ã‚Œã¦ã„るユーティリティーãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚特定ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ã®è©³ç´°ã¯ã€ã€Œ`モジュールユーティリティーã®ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ <https://github.com/ansible/ansible/tree/devel/lib/ansible/module_utils>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" @@ -2692,83 +2692,83 @@ msgstr "``module_utils`` ã®ãƒ•ã‚¡ã‚¤ãƒ«ã«é©åˆ‡ãªãƒ©ã‚¤ã‚»ãƒ³ã‚¹ã«ã¤ã„ã¦ç msgid "All other files shipped with Ansible, including all modules, must be licensed under the GPL license (GPLv3 or later)." msgstr "ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’å«ã‚€ Ansible ã«åŒæ¢±ã•ã‚Œã‚‹ä»–ã®ã™ã¹ã¦ã®ãƒ•ã‚¡ã‚¤ãƒ«ã¯ã€GPL ライセンス (GPLv3 以é™) ã§ãƒ©ã‚¤ã‚»ãƒ³ã‚¹ã‚’å–å¾—ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_module_utilities.rst:47 +#: ../../rst/dev_guide/developing_module_utilities.rst:49 msgid "``api.py`` - Supports generic API modules" msgstr "``api.py`` - 汎用 API モジュールã®ã‚µãƒãƒ¼ãƒˆ" -#: ../../rst/dev_guide/developing_module_utilities.rst:48 +#: ../../rst/dev_guide/developing_module_utilities.rst:50 msgid "``basic.py`` - General definitions and helper utilities for Ansible modules" msgstr "``basic.py`` - Ansible モジュールã®ä¸€èˆ¬çš„ãªå®šç¾©ãŠã‚ˆã³ãƒ˜ãƒ«ãƒ‘ーユーティリティー" -#: ../../rst/dev_guide/developing_module_utilities.rst:49 +#: ../../rst/dev_guide/developing_module_utilities.rst:51 msgid "``common/dict_transformations.py`` - Helper functions for dictionary transformations" msgstr "``common/dict_transformations.py`` - ディクショナリー変æ›ã®ãƒ˜ãƒ«ãƒ‘ー関数" -#: ../../rst/dev_guide/developing_module_utilities.rst:50 +#: ../../rst/dev_guide/developing_module_utilities.rst:52 msgid "``common/file.py`` - Helper functions for working with files" msgstr "``common/file.py`` - ファイルをæ“作ã™ã‚‹ãƒ˜ãƒ«ãƒ‘ー関数" -#: ../../rst/dev_guide/developing_module_utilities.rst:51 +#: ../../rst/dev_guide/developing_module_utilities.rst:53 msgid "``common/text/`` - Helper functions for converting and formatting text" msgstr "``common/text/`` - テã‚ストã®å¤‰æ›ãŠã‚ˆã³ãƒ•ã‚©ãƒ¼ãƒžãƒƒãƒˆã‚’è¡Œã†ãŸã‚ã®ãƒ˜ãƒ«ãƒ‘ー関数" -#: ../../rst/dev_guide/developing_module_utilities.rst:52 +#: ../../rst/dev_guide/developing_module_utilities.rst:54 msgid "``common/parameters.py`` - Helper functions for dealing with module parameters" msgstr "``common/parameters.py`` - モジュールパラメーターを処ç†ã™ã‚‹ãƒ˜ãƒ«ãƒ‘ー関数" -#: ../../rst/dev_guide/developing_module_utilities.rst:53 +#: ../../rst/dev_guide/developing_module_utilities.rst:55 msgid "``common/sys_info.py`` - Functions for getting distribution and platform information" msgstr "``common/sys_info.py`` - ディストリビューションãŠã‚ˆã³ãƒ—ãƒ©ãƒƒãƒˆãƒ•ã‚©ãƒ¼ãƒ æƒ…å ±ã‚’å–å¾—ã™ã‚‹æ©Ÿèƒ½" -#: ../../rst/dev_guide/developing_module_utilities.rst:54 +#: ../../rst/dev_guide/developing_module_utilities.rst:56 msgid "``common/validation.py`` - Helper functions for validating module parameters against a module argument spec" msgstr "``common/validation.py`` - モジュール引数仕様ã«å¯¾ã—ã¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ‘ラメーターを検証ã™ã‚‹ãŸã‚ã®ãƒ˜ãƒ«ãƒ‘ー関数" -#: ../../rst/dev_guide/developing_module_utilities.rst:55 +#: ../../rst/dev_guide/developing_module_utilities.rst:57 msgid "``facts/`` - Directory of utilities for modules that return facts. See `PR 23012 <https://github.com/ansible/ansible/pull/23012>`_ for more information" msgstr "``facts/`` - ファクトを返ã™ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã€‚詳細ã¯ã€`PR 23012 <https://github.com/ansible/ansible/pull/23012>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_module_utilities.rst:56 +#: ../../rst/dev_guide/developing_module_utilities.rst:58 msgid "``json_utils.py`` - Utilities for filtering unrelated output around module JSON output, like leading and trailing lines" msgstr "``json_utils.py`` - å…ˆé 行や末尾行ãªã©ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« JSON 出力ã«é–¢ã™ã‚‹é–¢é€£ã®ãªã„出力をフィルターをè¨å®šã™ã‚‹ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼" -#: ../../rst/dev_guide/developing_module_utilities.rst:57 +#: ../../rst/dev_guide/developing_module_utilities.rst:59 msgid "``powershell/`` - Directory of definitions and helper functions for Windows PowerShell modules" msgstr "``powershell/`` - Windows PowerShell モジュールã®å®šç¾©ãŠã‚ˆã³ãƒ˜ãƒ«ãƒ‘ー関数ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼" -#: ../../rst/dev_guide/developing_module_utilities.rst:58 +#: ../../rst/dev_guide/developing_module_utilities.rst:60 msgid "``pycompat24.py`` - Exception workaround for Python 2.4" msgstr "``pycompat24.py`` - Python 2.4 ã®ä¾‹å¤–回é¿ç–" -#: ../../rst/dev_guide/developing_module_utilities.rst:59 +#: ../../rst/dev_guide/developing_module_utilities.rst:61 msgid "``service.py`` - Utilities to enable modules to work with Linux services (placeholder, not in use)" msgstr "``service.py`` - モジュール㌠Linux サービスã¨é€£æºã§ãるよã†ã«ã™ã‚‹ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ (未使用ã®ãƒ—レースホルダー)" -#: ../../rst/dev_guide/developing_module_utilities.rst:60 +#: ../../rst/dev_guide/developing_module_utilities.rst:62 msgid "``six/__init__.py`` - Bundled copy of the `Six Python library <https://pypi.org/project/six/>`_ to aid in writing code compatible with both Python 2 and Python 3" msgstr "``six/__init__.py`` - Python 2 㨠Python 3 ã®ä¸¡æ–¹ã¨äº’æ›æ€§ã®ã‚るコードを書ã込む際ã«åŠ©ã‘ã¨ãªã‚‹ `Six Python ライブラリー <https://pypi.org/project/six/>`_ ã®ãƒãƒ³ãƒ‰ãƒ«ã‚³ãƒ”ー" -#: ../../rst/dev_guide/developing_module_utilities.rst:61 +#: ../../rst/dev_guide/developing_module_utilities.rst:63 msgid "``splitter.py`` - String splitting and manipulation utilities for working with Jinja2 templates" msgstr "``splitter.py`` - Jinja2 テンプレートを使用ã™ã‚‹æ–‡å—列分割ãŠã‚ˆã³æ“作ユーティリティー" -#: ../../rst/dev_guide/developing_module_utilities.rst:62 +#: ../../rst/dev_guide/developing_module_utilities.rst:64 msgid "``urls.py`` - Utilities for working with http and https requests" msgstr "``urls.py`` - http ãŠã‚ˆã³ https リクエストをæ“作ã™ã‚‹ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼" -#: ../../rst/dev_guide/developing_module_utilities.rst:64 +#: ../../rst/dev_guide/developing_module_utilities.rst:66 msgid "Several commonly-used utilities migrated to collections in Ansible 2.10, including:" msgstr "一般的ã«ä½¿ç”¨ã•ã‚Œã‚‹ã„ãã¤ã‹ã®ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ã¯ã€Ansible 2.10 ã§ã¯ä»¥ä¸‹ã®ã‚ˆã†ãªã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«ç§»è¡Œã•ã‚Œã¦ã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_module_utilities.rst:66 +#: ../../rst/dev_guide/developing_module_utilities.rst:68 msgid "``ismount.py`` migrated to ``ansible.posix.plugins.module_utils.mount.py`` - Single helper function that fixes os.path.ismount" msgstr "``ansible.posix.plugins.module_utils.mount.py`` ã«ç§»è¡Œã—㟠``ismount.py`` - os.path.ismount ã‚’ä¿®æ£ã™ã‚‹å˜ä¸€ã®ãƒ˜ãƒ«ãƒ‘ー関数" -#: ../../rst/dev_guide/developing_module_utilities.rst:67 +#: ../../rst/dev_guide/developing_module_utilities.rst:69 msgid "``known_hosts.py`` migrated to ``community.general.plugins.module_utils.known_hosts.py`` - utilities for working with known_hosts file" msgstr "``community.general.plugins.module_utils.known_hosts.py`` ã«ç§»è¡Œã—㟠``known_hosts.py`` - known_hosts ファイルã§ä½œæ¥ã™ã‚‹ãŸã‚ã®ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼" -#: ../../rst/dev_guide/developing_module_utilities.rst:69 +#: ../../rst/dev_guide/developing_module_utilities.rst:71 msgid "For a list of migrated content with destination collections, see https://github.com/ansible/ansible/blob/devel/lib/ansible/config/ansible_builtin_runtime.yml." msgstr "宛先コレクションã§ç§»è¡Œã•ã‚ŒãŸã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã®ä¸€è¦§ã¯ã€https://github.com/ansible/ansible/blob/devel/lib/ansible/config/ansible_builtin_runtime.yml ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" @@ -2849,8 +2849,8 @@ msgid "I want to :ref:`document my module <developing_modules_documenting>`." msgstr ":ref:`作æˆã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’ドã‚ュメント化 <developing_modules_documenting>` ã—ãŸã„ã§ã™ã€‚" #: ../../rst/dev_guide/developing_modules.rst:39 -msgid "I want to :ref:`contribute my module back to Ansible Core <developing_modules_checklist>`." -msgstr ":ref:`作æˆã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’ Ansible Core ã«è²¢çŒ® <developing_modules_checklist>` ã—ãŸã„ã§ã™ã€‚" +msgid "I want to :ref:`contribute my module to an existing Ansible collection <developing_modules_checklist>`." +msgstr ":ref:`自分ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã§æ—¢å˜ã® Ansible コレクションã«è²¢çŒ® <developing_modules_checklist>` ã—ãŸã„ã§ã™ã€‚" #: ../../rst/dev_guide/developing_modules.rst:40 msgid "I want to :ref:`add unit and integration tests to my module <developing_testing>`." @@ -3737,147 +3737,155 @@ msgstr "Ansible 2.10 以é™ã§ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¸ã®å‚照㌠``ansible-cor msgid "A reference can be one of the following formats:" msgstr "å‚ç…§ã«ã¯ã€ä»¥ä¸‹ã®å½¢å¼ã®ã„ãšã‚Œã‹ã‚’使用ã§ãã¾ã™ã€‚" +#: ../../rst/dev_guide/developing_modules_documenting.rst:230 +msgid "If you use ``ref:`` to link to an anchor that is not associated with a title, you must add a title to the ref for the link to work correctly." +msgstr "``ref:`` を使用ã—ã¦ã‚¿ã‚¤ãƒˆãƒ«ã¨é–¢é€£ä»˜ã‘られã¦ã„ãªã„アンカーã«ãƒªãƒ³ã‚¯ã™ã‚‹å ´åˆã¯ã€ãƒªãƒ³ã‚¯ãŒæ£ã—ã機能ã™ã‚‹ã‚ˆã†ã« ref ã«ã‚¿ã‚¤ãƒˆãƒ«ã‚’è¿½åŠ ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" + +#: ../../rst/dev_guide/developing_modules_documenting.rst:231 +msgid "You can link to non-module plugins with ``ref:`` using the rST anchor, but plugin and module anchors are never associated with a title, so you must supply a title when you link to them. For example ``ref: namespace.collection.plugin_name lookup plugin <ansible_collections.namespace.collection.plugin_name_lookup>``." +msgstr "rST アンカーを使用ã—㦠``ref:`` ã§ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ä»¥å¤–ã®ãƒ—ラグインã«ãƒªãƒ³ã‚¯ã§ãã¾ã™ãŒã€ãƒ—ラグインãŠã‚ˆã³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚¢ãƒ³ã‚«ãƒ¼ã¯ã‚¿ã‚¤ãƒˆãƒ«ã¨é–¢é€£ä»˜ã‘られãªã„ãŸã‚ã€ãƒªãƒ³ã‚¯ã™ã‚‹éš›ã«ã‚¿ã‚¤ãƒˆãƒ«ã‚’指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€``ref: namespace.collection.plugin_name lookup plugin <ansible_collections.namespace.collection.plugin_name_lookup>`` ã¨ãªã‚Šã¾ã™ã€‚" + #: ../../rst/dev_guide/developing_modules_documenting.rst msgid "notes" msgstr "notes" -#: ../../rst/dev_guide/developing_modules_documenting.rst:227 +#: ../../rst/dev_guide/developing_modules_documenting.rst:236 msgid "Details of any important information that doesn't fit in one of the above sections." msgstr "上記ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã®ã„ãšã‚Œã‹ã«è©²å½“ã—ãªã„é‡è¦ãªæƒ…å ±ã®è©³ç´°ã§ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:228 +#: ../../rst/dev_guide/developing_modules_documenting.rst:237 msgid "For example, whether ``check_mode`` is or is not supported." msgstr "ãŸã¨ãˆã°ã€``check_mode`` ãŒã‚µãƒãƒ¼ãƒˆã•ã‚Œã‚‹ã‹ã©ã†ã‹ãªã©ã§ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:232 +#: ../../rst/dev_guide/developing_modules_documenting.rst:241 msgid "Linking and other format macros within module documentation" msgstr "モジュールドã‚ュメント内ã®ãƒªãƒ³ã‚¯ãŠã‚ˆã³ãã®ä»–ã®å½¢å¼ãƒžã‚¯ãƒ" -#: ../../rst/dev_guide/developing_modules_documenting.rst:234 +#: ../../rst/dev_guide/developing_modules_documenting.rst:243 msgid "You can link from your module documentation to other module docs, other resources on docs.ansible.com, and resources elsewhere on the internet with the help of some pre-defined macros. The correct formats for these macros are:" msgstr "モジュールドã‚ュメントã‹ã‚‰ä»–ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ‰ã‚ュメントã€docs.ansible.com ã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹ã€ä¸€éƒ¨ã®äº‹å‰è¨å®šãƒžã‚¯ãƒã§ã‚¤ãƒ³ã‚¿ãƒ¼ãƒãƒƒãƒˆä¸Šã®ä»–ã®ãƒªã‚½ãƒ¼ã‚¹ã«ãƒªãƒ³ã‚¯ã§ãã¾ã™ã€‚ã“れらã®ãƒžã‚¯ãƒã®æ£ã—ã„å½¢å¼ã¯æ¬¡ã®ã¨ãŠã‚Šã§ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:236 +#: ../../rst/dev_guide/developing_modules_documenting.rst:245 msgid "``L()`` for links with a heading. For example: ``See L(Ansible Automation Platform,https://www.ansible.com/products/automation-platform).`` As of Ansible 2.10, do not use ``L()`` for relative links between Ansible documentation and collection documentation." msgstr "``L()`` 見出ã—ã¸ã®ãƒªãƒ³ã‚¯ã€‚ãŸã¨ãˆã°ã€``See L(Ansible Automation Platform,https://www.ansible.com/products/automation-platform).`` ã¨ãªã‚Šã¾ã™ã€‚Ansible 2.10 以é™ã€Ansible ドã‚ュメントã¨ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒ‰ã‚ュメントã®ç›¸å¯¾ãƒªãƒ³ã‚¯ã«ã¯ ``L()`` を使用ã—ãªã„ã§ãã ã•ã„。" -#: ../../rst/dev_guide/developing_modules_documenting.rst:237 +#: ../../rst/dev_guide/developing_modules_documenting.rst:246 msgid "``U()`` for URLs. For example: ``See U(https://www.ansible.com/products/automation-platform) for an overview.``" msgstr "URL ã®å ´åˆã¯ ``U()``。ãŸã¨ãˆã°ã€``See U(https://www.ansible.com/products/automation-platform) for an overview.`` ã¨ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:239 +#: ../../rst/dev_guide/developing_modules_documenting.rst:248 msgid "There are also some macros which do not create links but we use them to display certain types of content in a uniform way:" msgstr "リンクを作æˆã—ãªã„ã‚‚ã®ã®ã€ãã®ãƒžã‚¯ãƒã‚’使用ã—ã¦ã€ç‰¹å®šã®ã‚¿ã‚¤ãƒ—ã®ã‚³ãƒ³ãƒ†ãƒ³ãƒ„を統一ã—ã¦è¡¨ç¤ºã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:242 +#: ../../rst/dev_guide/developing_modules_documenting.rst:251 msgid "``I()`` for option names. For example: ``Required if I(state=present).`` This is italicized in the documentation." msgstr "オプションåã®å ´åˆã¯ ``I()``。ãŸã¨ãˆã° ``Required if I(state=present).`` ã§ã™ã€‚ã“ã‚Œã¯ã€ãƒ‰ã‚ュメントã§ã¯ã‚¤ã‚¿ãƒªãƒƒã‚¯ä½“ã§ç¤ºã•ã‚Œã¦ã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:244 +#: ../../rst/dev_guide/developing_modules_documenting.rst:253 msgid "``C()`` for files, option values, and inline code. For example: ``If not set the environment variable C(ACME_PASSWORD) will be used.`` or ``Use C(var | foo.bar.my_filter) to transform C(var) into the required format.`` This displays with a mono-space font in the documentation." msgstr "ファイルã€ã‚ªãƒ—ション値ã€ãŠã‚ˆã³ã‚¤ãƒ³ãƒ©ã‚¤ãƒ³ã‚³ãƒ¼ãƒ‰ã®å ´åˆã¯ ``C()`` (例 ``If not set the environment variable C(ACME_PASSWORD) will be used.`` ã¾ãŸã¯ ``Use C(var | foo.bar.my_filter) to transform C(var) into the required format.``)。ã“ã‚Œã¯ã€ãƒ‰ã‚ュメントã§ã¯ Monospace フォントã¨è¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:245 +#: ../../rst/dev_guide/developing_modules_documenting.rst:254 msgid "``B()`` currently has no standardized usage. It is displayed in boldface in the documentation." msgstr "``B()`` ã¯ã€ç¾åœ¨ã€æ¨™æº–化ã•ã‚ŒãŸä½¿ç”¨ã¯ã‚ã‚Šã¾ã›ã‚“。ã“ã®ãƒ‰ã‚ュメントã«ã¯å¤ªå—ãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:246 +#: ../../rst/dev_guide/developing_modules_documenting.rst:255 msgid "``HORIZONTALLINE`` is used sparingly as a separator in long descriptions. It becomes a horizontal rule (the ``<hr>`` html tag) in the documentation." msgstr "``HORIZONTALLINE`` ã¯ã€é•·ã„説明ã§ã¯ã€åŒºåˆ‡ã‚Šæ–‡å—ã¨ã—ã¦æ…Žé‡ã«ä½¿ç”¨ã•ã‚Œã¦ãŠã‚Šã€ãƒ‰ã‚ュメント内ã®æ°´å¹³ãƒ«ãƒ¼ãƒ« (``<hr>`` html ã‚¿ã‚°) ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:250 +#: ../../rst/dev_guide/developing_modules_documenting.rst:259 msgid "For links between modules and documentation within a collection, you can use either of the options above. Use ``U()`` or ``L()`` with full URLs (not relative links)." msgstr "コレクション内ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¨ãƒ‰ã‚ュメント間ã®ãƒªãƒ³ã‚¯ã«ã¯ã€ä¸Šè¨˜ã®ã‚ªãƒ—ションã®ã„ãšã‚Œã‹ã‚’使用ã§ãã¾ã™ã€‚``U()`` ã¾ãŸã¯``L()`` をフル URL ã§ä½¿ç”¨ã—ã¦ãã ã•ã„（相対リンクã§ã¯ã‚ã‚Šã¾ã›ã‚“）。" -#: ../../rst/dev_guide/developing_modules_documenting.rst:253 +#: ../../rst/dev_guide/developing_modules_documenting.rst:262 msgid "When a collection is not the right granularity, use ``C(..)``:" msgstr "コレクションãŒé©åˆ‡ãªç²’度ã§ã¯ãªã„å ´åˆã¯ã€``C(..)`` を使用ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:255 +#: ../../rst/dev_guide/developing_modules_documenting.rst:264 msgid "``The C(win_*) modules (spread across several collections) allow you to manage various aspects of windows hosts.``" msgstr "``The C(win_*) modules (spread across several collections) allow you to manage various aspects of windows hosts.``" -#: ../../rst/dev_guide/developing_modules_documenting.rst:259 +#: ../../rst/dev_guide/developing_modules_documenting.rst:268 msgid "Because it stands out better, use ``seealso`` for general references over the use of notes or adding links to the description." msgstr "``seealso`` ã®æ–¹ãŒç›®ç«‹ã¤ãŸã‚ã€ä¸€èˆ¬çš„ãªå‚ç…§ã«ã¯ãƒŽãƒ¼ãƒˆã®ä½¿ç”¨ã‚„説明ã¸ã®ãƒªãƒ³ã‚¯ã‚ˆã‚Šã‚‚ã€``seealso`` を使用ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:264 +#: ../../rst/dev_guide/developing_modules_documenting.rst:273 msgid "Documentation fragments" msgstr "ドã‚ュメントフラグメント" -#: ../../rst/dev_guide/developing_modules_documenting.rst:266 +#: ../../rst/dev_guide/developing_modules_documenting.rst:275 msgid "If you are writing multiple related modules, they may share common documentation, such as authentication details, file mode settings, ``notes:`` or ``seealso:`` entries. Rather than duplicate that information in each module's ``DOCUMENTATION`` block, you can save it once as a doc_fragment plugin and use it in each module's documentation. In Ansible, shared documentation fragments are contained in a ``ModuleDocFragment`` class in `lib/ansible/plugins/doc_fragments/ <https://github.com/ansible/ansible/tree/devel/lib/ansible/plugins/doc_fragments>`_ or the equivalent directory in a collection. To include a documentation fragment, add ``extends_documentation_fragment: FRAGMENT_NAME`` in your module documentation. Use the fully qualified collection name for the FRAGMENT_NAME (for example, ``kubernetes.core.k8s_auth_options``)." msgstr "複数ã®é–¢é€£ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’記述ã—ã¦ã„ã‚‹å ´åˆã¯ã€èªè¨¼ã®è©³ç´°ã‚„ファイルモードã®è¨å®šã€``notes:`` ã‚„ ``seealso:`` ã®ã‚¨ãƒ³ãƒˆãƒªãƒ¼ãªã©ã€å…±é€šã®ãƒ‰ã‚ュメントを共有ã—ã¦ã„ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ãã®ã‚ˆã†ãªæƒ…å ±ã‚’å„モジュール㮠``DOCUMENTATION`` ブãƒãƒƒã‚¯ã«è¤‡è£½ã™ã‚‹ã®ã§ã¯ãªãã€doc_fragment プラグインã¨ã—ã¦ä¸€åº¦ä¿å˜ã—ã€å„モジュールã®ãƒ‰ã‚ュメントã§ä½¿ç”¨ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚Ansible ã§ã¯ã€å…±æœ‰ãƒ‰ã‚ュメントフラグメントã¯ã€`lib/ansible/plugins/doc_fragments/ <https://github.com/ansible/ansible/tree/devel/lib/ansible/plugins/doc_fragments>`_ ã® ``ModuleDocFragment`` クラスã€ã¾ãŸã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®åŒç‰ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«å«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ドã‚ュメントフラグメントをå«ã‚ã‚‹ã«ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ‰ã‚ュメント㫠``extends_documentation_fragment: FRAGMENT_NAME`` ã‚’è¿½åŠ ã—ã¾ã™ã€‚FRAGMENT_NAME ã«ã¯ã€å®Œå…¨ä¿®é£¾ã•ã‚ŒãŸã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³åを使用ã—ã¾ã™ (例: ``kubernetes.core.k8s_auth_options``)。" -#: ../../rst/dev_guide/developing_modules_documenting.rst:268 +#: ../../rst/dev_guide/developing_modules_documenting.rst:277 msgid "Modules should only use items from a doc fragment if the module will implement all of the interface documented there in a manner that behaves the same as the existing modules which import that fragment. The goal is that items imported from the doc fragment will behave identically when used in another module that imports the doc fragment." msgstr "モジュールãŒãƒ‰ã‚ュメントフラグメントã®ã‚¢ã‚¤ãƒ†ãƒ を使用ã™ã‚‹ã®ã¯ã€ãã®ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã‚’インãƒãƒ¼ãƒˆã™ã‚‹æ—¢å˜ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¨åŒã˜ã‚ˆã†ã«å‹•ä½œã—ã¦ã€ãƒ‰ã‚ュメント化ã•ã‚ŒãŸã™ã¹ã¦ã®ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ã‚’モジュールãŒå®Ÿè£…ã™ã‚‹å ´åˆã®ã¿ã§ã™ã€‚目標ã¯ã€ãƒ‰ã‚ュメントフラグメントã‹ã‚‰ã‚¤ãƒ³ãƒãƒ¼ãƒˆã•ã‚ŒãŸã‚¢ã‚¤ãƒ†ãƒ ãŒã€ãƒ‰ã‚ュメントフラグメントをインãƒãƒ¼ãƒˆã™ã‚‹åˆ¥ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã§ä½¿ç”¨ã•ã‚ŒãŸå ´åˆã¨åŒã˜ã‚ˆã†ã«å‹•ä½œã™ã‚‹ã“ã¨ã§ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:270 +#: ../../rst/dev_guide/developing_modules_documenting.rst:279 msgid "By default, only the ``DOCUMENTATION`` property from a doc fragment is inserted into the module documentation. It is possible to define additional properties in the doc fragment in order to import only certain parts of a doc fragment or mix and match as appropriate. If a property is defined in both the doc fragment and the module, the module value overrides the doc fragment." msgstr "デフォルトã§ã¯ã€ãƒ‰ã‚ュメントフラグメント㮠``DOCUMENTATION`` プãƒãƒ‘ティーãŒãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ‰ã‚ュメントã«æŒ¿å…¥ã•ã‚Œã¾ã™ã€‚ドã‚ュメントフラグメントã®ç‰¹å®šã®éƒ¨åˆ†ã®ã¿ã‚’インãƒãƒ¼ãƒˆã™ã‚‹ãŸã‚ã€ã¾ãŸã¯å¿…è¦ã«å¿œã˜ã¦çµ„ã¿åˆã‚ã›ã¦ä¸€è‡´ã•ã›ã‚‹ãŸã‚ã«ã€ãƒ‰ã‚ュメントフラグメントã«è¿½åŠ ã®ãƒ—ãƒãƒ‘ティーを定義ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚プãƒãƒ‘ティーãŒãƒ‰ã‚ュメントフラグメントã¨ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ä¸¡æ–¹ã§å®šç¾©ã•ã‚Œã¦ã„ã‚‹å ´åˆã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«å€¤ã¯ãƒ‰ã‚ュメントフラグメントを上書ãã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:272 +#: ../../rst/dev_guide/developing_modules_documenting.rst:281 msgid "Here is an example doc fragment named ``example_fragment.py``:" msgstr "以下ã¯ã€``example_fragment.py`` ã¨ã„ã†åå‰ã®ãƒ‰ã‚ュメントフラグメントã®ä¾‹ã§ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:290 +#: ../../rst/dev_guide/developing_modules_documenting.rst:299 msgid "To insert the contents of ``OTHER`` in a module:" msgstr "``OTHER`` ã®å†…容をモジュールã«æŒ¿å…¥ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:296 +#: ../../rst/dev_guide/developing_modules_documenting.rst:305 msgid "Or use both :" msgstr "ã¾ãŸã¯ã€ä»¥ä¸‹ã®ä¸¡æ–¹ã‚’使用ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_modules_documenting.rst:309 +#: ../../rst/dev_guide/developing_modules_documenting.rst:318 msgid "Since Ansible 2.8, you can have user-supplied doc_fragments by using a ``doc_fragments`` directory adjacent to play or role, just like any other plugin." msgstr "Ansible 2.8 以é™ã€ãã®ä»–ã®ãƒ—ラグインã¨åŒæ§˜ã«ã€ãƒ—レイやãƒãƒ¼ãƒ«ã«éš£æŽ¥ã™ã‚‹ ``doc_fragments`` ディレクトリーを使用ã™ã‚‹ã“ã¨ã§ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒæä¾›ã™ã‚‹ãƒ‰ã‚ュメントフラグメントをè¨å®šã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:311 +#: ../../rst/dev_guide/developing_modules_documenting.rst:320 msgid "For example, all AWS modules should include:" msgstr "ãŸã¨ãˆã°ã€ã™ã¹ã¦ã® AWS モジュールã«ã¯ä»¥ä¸‹ã‚’å«ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:319 +#: ../../rst/dev_guide/developing_modules_documenting.rst:328 msgid ":ref:`docfragments_collections` describes how to incorporate documentation fragments in a collection." msgstr "「:ref:`docfragments_collections`ã€ã§ã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«ãƒ‰ã‚ュメントã®ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã‚’組ã¿è¾¼ã‚€æ–¹æ³•ã‚’説明ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:324 +#: ../../rst/dev_guide/developing_modules_documenting.rst:333 msgid "EXAMPLES block" msgstr "EXAMPLES ブãƒãƒƒã‚¯" -#: ../../rst/dev_guide/developing_modules_documenting.rst:326 +#: ../../rst/dev_guide/developing_modules_documenting.rst:335 msgid "After the shebang, the UTF-8 coding, the copyright line, the license section, and the ``DOCUMENTATION`` block comes the ``EXAMPLES`` block. Here you show users how your module works with real-world examples in multi-line plain-text YAML format. The best examples are ready for the user to copy and paste into a playbook. Review and update your examples with every change to your module." msgstr "ã‚·ãƒãƒ³ã®å¾Œã€UTF-8 コーディングã€è‘—作権表示ã€ãƒ©ã‚¤ã‚»ãƒ³ã‚¹ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã€ãŠã‚ˆã³ ``DOCUMENTATION`` ブãƒãƒƒã‚¯ã®å¾Œã« ``EXAMPLES`` ブãƒãƒƒã‚¯ãŒç¶šãã¾ã™ã€‚ã“ã“ã§ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒå®Ÿéš›ã®ä¾‹ã§è¤‡æ•°è¡Œã®ãƒ—レーンテã‚スト YAML å½¢å¼ã§ã©ã®ã‚ˆã†ã«æ©Ÿèƒ½ã™ã‚‹ã‹ã‚’ユーザーã«ç¤ºã—ã¾ã™ã€‚最良ã®ä¾‹ã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒã‚³ãƒ”ーã—㦠Playbook ã«è²¼ã‚Šä»˜ã‘る準備ãŒã§ãã¦ã„ã¾ã™ã€‚モジュールã«å¤‰æ›´ã‚’åŠ ãˆã‚‹ãŸã³ã«ã€ä¾‹ã‚’確èªã—ã¦æ›´æ–°ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_modules_documenting.rst:328 -msgid "Per playbook best practices, each example should include a ``name:`` line::" +#: ../../rst/dev_guide/developing_modules_documenting.rst:337 +msgid "Per playbook best practices, each example should include a ``name:`` line:" msgstr "Playbook ã®ãƒ™ã‚¹ãƒˆãƒ—ラクティスã«åŸºã¥ãã€å„例ã«ã¯ ``name:`` è¡ŒãŒå¿…è¦ã§ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:337 +#: ../../rst/dev_guide/developing_modules_documenting.rst:348 msgid "The ``name:`` line should be capitalized and not include a trailing dot." msgstr "``name:`` è¡Œã¯å¤§æ–‡å—ã«ã—ã€æœ«å°¾ã®ãƒ‰ãƒƒãƒˆã¯å«ã‚ãªã„ã§ãã ã•ã„。" -#: ../../rst/dev_guide/developing_modules_documenting.rst:339 +#: ../../rst/dev_guide/developing_modules_documenting.rst:350 msgid "Use a fully qualified collection name (FQCN) as a part of the module's name like in the example above. For modules in ``ansible-core``, use the ``ansible.builtin.`` identifier, for example ``ansible.builtin.debug``." msgstr "上記ã®ä¾‹ã®ã‚ˆã†ã«ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«åã®ä¸€éƒ¨ã¨ã—ã¦å®Œå…¨ä¿®é£¾ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³å (FQCN) を使用ã—ã¾ã™ã€‚``ansible-core`` ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®å ´åˆã¯ã€``ansible.builtin.`` è˜åˆ¥å (ãŸã¨ãˆã° ``ansible.builtin.debug``) を使用ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:341 +#: ../../rst/dev_guide/developing_modules_documenting.rst:352 msgid "If your examples use boolean options, use yes/no values. Since the documentation generates boolean values as yes/no, having the examples use these values as well makes the module documentation more consistent." msgstr "サンプルã§ãƒ–ール値オプションを使用ã™ã‚‹å ´åˆã¯ã€yes/no ã®å€¤ã‚’使用ã—ã¾ã™ã€‚ドã‚ュメントã«ã‚ˆã‚Šãƒ–ール値㌠yes/no ã¨ã—ã¦ç”Ÿæˆã•ã‚Œã‚‹ãŸã‚ã€ã“ã®ã‚µãƒ³ãƒ—ルã§ã¯ã“れらã®å€¤ãŒä½¿ç”¨ã•ã‚Œã¦ãŠã‚Šã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ‰ã‚ュメントã®ä¸€è²«æ€§ãŒä¿ãŸã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:343 +#: ../../rst/dev_guide/developing_modules_documenting.rst:354 msgid "If your module returns facts that are often needed, an example of how to use them can be helpful." msgstr "モジュールãŒå¿…è¦ãªãƒ•ã‚¡ã‚¯ãƒˆã‚’è¿”ã™ã¨ã€ãã®ä½¿ç”¨æ–¹æ³•ã®ä¾‹ãŒä¾¿åˆ©ã§ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:348 +#: ../../rst/dev_guide/developing_modules_documenting.rst:359 msgid "RETURN block" msgstr "RETURN ブãƒãƒƒã‚¯" -#: ../../rst/dev_guide/developing_modules_documenting.rst:350 +#: ../../rst/dev_guide/developing_modules_documenting.rst:361 msgid "After the shebang, the UTF-8 coding, the copyright line, the license section, ``DOCUMENTATION`` and ``EXAMPLES`` blocks comes the ``RETURN`` block. This section documents the information the module returns for use by other modules." msgstr "ã‚·ãƒãƒ³ã€UTF-8コーディングã€è‘—作権表示ã€ãƒ©ã‚¤ã‚»ãƒ³ã‚¹ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã€``DOCUMENTATION`` ブãƒãƒƒã‚¯ãŠã‚ˆã³ ``EXAMPLES`` ブãƒãƒƒã‚¯ã®å¾Œã«ã€``RETURN`` ブãƒãƒƒã‚¯ãŒç¶šãã¾ã™ã€‚ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒä»–ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã§ä½¿ç”¨ã™ã‚‹ãŸã‚ã«è¿”ã™æƒ…å ±ã‚’èª¬æ˜Žã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:352 +#: ../../rst/dev_guide/developing_modules_documenting.rst:363 msgid "If your module doesn't return anything (apart from the standard returns), this section of your module should read: ``RETURN = r''' # '''`` Otherwise, for each value returned, provide the following fields. All fields are required unless specified otherwise." msgstr "モジュールãŒä½•ã‚‚è¿”ã•ãªã„å ´åˆã¯ (標準ã®æˆ»ã‚Šå€¤ã¨ã¯ç•°ãªã‚Š)ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã¯ ``RETURN = r''' # '''`` ã‚’èªã¿å–ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ãれ以外ã®å ´åˆã¯ã€è¿”ã•ã‚ŒãŸå„値ã«ä»¥ä¸‹ã®ãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ã‚’指定ã—ã¾ã™ã€‚特ã«æŒ‡å®šãŒãªã„å ´åˆã¯ã™ã¹ã¦ã®ãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ãŒå¿…è¦ã«ãªã‚Šã¾ã™ã€‚" @@ -3885,11 +3893,11 @@ msgstr "モジュールãŒä½•ã‚‚è¿”ã•ãªã„å ´åˆã¯ (標準ã®æˆ»ã‚Šå€¤ã¨ã¯ç msgid "return name" msgstr "return name" -#: ../../rst/dev_guide/developing_modules_documenting.rst:356 +#: ../../rst/dev_guide/developing_modules_documenting.rst:367 msgid "Name of the returned field." msgstr "è¿”ã•ã‚Œã‚‹ãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ã®åå‰ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:359 +#: ../../rst/dev_guide/developing_modules_documenting.rst:370 msgid "Detailed description of what this value represents. Capitalized and with trailing dot." msgstr "ã“ã®å€¤ãŒè¡¨ã™å†…容ã®è©³ç´°ãªèª¬æ˜Žã€‚大文å—ã§ã€æœ«å°¾ã®ãƒ‰ãƒƒãƒˆã‚’使用ã—ã¾ã™ã€‚" @@ -3897,15 +3905,15 @@ msgstr "ã“ã®å€¤ãŒè¡¨ã™å†…容ã®è©³ç´°ãªèª¬æ˜Žã€‚大文å—ã§ã€æœ«å°¾ã®ãƒ‰ msgid "returned" msgstr "returned" -#: ../../rst/dev_guide/developing_modules_documenting.rst:361 +#: ../../rst/dev_guide/developing_modules_documenting.rst:372 msgid "When this value is returned, such as ``always``, ``changed`` or ``success``. This is a string and can contain any human-readable content." msgstr "``always``ã€``changed``ã€``success`` ãªã©ã®ã“ã®å€¤ãŒè¿”ã•ã‚Œã‚‹ã¨ã€ã“ã‚Œã¯æ–‡å—列ã¨ãªã‚Šã€äººé–“ãŒåˆ¤èªã§ãるコンテンツをå«ã‚ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:363 +#: ../../rst/dev_guide/developing_modules_documenting.rst:374 msgid "Data type." msgstr "データ型。" -#: ../../rst/dev_guide/developing_modules_documenting.rst:365 +#: ../../rst/dev_guide/developing_modules_documenting.rst:376 msgid "If ``type='list'``, specifies the data type of the list's elements." msgstr "``type='list'`` ã®å ´åˆã¯ã€ãƒªã‚¹ãƒˆã®è¦ç´ ã®ãƒ‡ãƒ¼ã‚¿ã‚¿ã‚¤ãƒ—を指定ã—ã¾ã™ã€‚" @@ -3913,11 +3921,11 @@ msgstr "``type='list'`` ã®å ´åˆã¯ã€ãƒªã‚¹ãƒˆã®è¦ç´ ã®ãƒ‡ãƒ¼ã‚¿ã‚¿ã‚¤ãƒ—ã‚ msgid "sample" msgstr "sample" -#: ../../rst/dev_guide/developing_modules_documenting.rst:367 +#: ../../rst/dev_guide/developing_modules_documenting.rst:378 msgid "One or more examples." msgstr "1 ã¤ä»¥ä¸Šã®ä¾‹ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:369 +#: ../../rst/dev_guide/developing_modules_documenting.rst:380 msgid "Only needed if this return was extended after initial Ansible release, in other words, this is greater than the top level `version_added` field. This is a string, and not a float, for example, ``version_added: '2.3'``." msgstr "ã“ã‚Œã¯ã€æœ€åˆã® Ansible リリースã®å¾Œã«ã“ã®è¿”ã•ã‚ŒãŸå ´åˆã«ã®ã¿å¿…è¦ã§ã™ã€‚ã¤ã¾ã‚Šã€ã“ã‚Œã¯æœ€ä¸Šä½ãƒ¬ãƒ™ãƒ«ã® `version_added` フィールドよりも大ãããªã‚Šã¾ã™ã€‚ã“ã‚Œã¯æµ®å‹•å°æ•°ç‚¹ã§ã¯ãªãã€æ–‡å—列ã§ã™ (例: ``version_added: '2.3'``)。" @@ -3925,32 +3933,32 @@ msgstr "ã“ã‚Œã¯ã€æœ€åˆã® Ansible リリースã®å¾Œã«ã“ã®è¿”ã•ã‚ŒãŸå ´ msgid "contains" msgstr "contains" -#: ../../rst/dev_guide/developing_modules_documenting.rst:372 +#: ../../rst/dev_guide/developing_modules_documenting.rst:383 msgid "Optional. To describe nested return values, set ``type: dict``, or ``type: list``/``elements: dict``, or if you really have to, ``type: complex``, and repeat the elements above for each sub-field." msgstr "ä»»æ„ã§ã™ã€‚ãƒã‚¹ãƒˆã•ã‚ŒãŸæˆ»ã‚Šå€¤ã‚’記述ã™ã‚‹ã«ã¯ã€``type: dict`` ã¾ãŸã¯ ``type: list``/``elements: dict`` ã‚’è¨å®šã™ã‚‹ã‹ã€æœ¬å½“ã«å¿…è¦ã§ã‚れ㰠``type: complex`` ã‚’è¨å®šã—ã€å„サブフィールドã«å¯¾ã—ã¦ä¸Šè¨˜ã®è¦ç´ ã‚’ç¹°ã‚Šè¿”ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:374 -msgid "Here are two example ``RETURN`` sections, one with three simple fields and one with a complex nested field::" +#: ../../rst/dev_guide/developing_modules_documenting.rst:385 +msgid "Here are two example ``RETURN`` sections, one with three simple fields and one with a complex nested field:" msgstr "以下ã®ä¾‹ã¯ã€``RETURN`` セクションを 3 ã¤ã®å˜ç´”ãªãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ã¨ã€è¤‡é›‘ãªãƒã‚¹ãƒˆã•ã‚ŒãŸãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ã‚’æŒã¤ 2 ã¤ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:422 +#: ../../rst/dev_guide/developing_modules_documenting.rst:435 msgid "Python imports" msgstr "Python ã®ã‚¤ãƒ³ãƒãƒ¼ãƒˆ" -#: ../../rst/dev_guide/developing_modules_documenting.rst:424 +#: ../../rst/dev_guide/developing_modules_documenting.rst:437 msgid "After the shebang, the UTF-8 coding, the copyright line, the license, and the sections for ``DOCUMENTATION``, ``EXAMPLES``, and ``RETURN``, you can finally add the python imports. All modules must use Python imports in the form:" msgstr "ã‚·ãƒãƒ³ã®å¾Œã«ã¯ã€UTF-8 コード行ã€è‘—作権行ã€ãƒ©ã‚¤ã‚»ãƒ³ã‚¹ã€ãŠã‚ˆã³ ``DOCUMENTATION``ã€``EXAMPLES``ã€ãŠã‚ˆã³ ``RETURN`` ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ãŒæœ€å¾Œã« python インãƒãƒ¼ãƒˆã‚’è¿½åŠ ã§ãã¾ã™ã€‚ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€ã“ã®å½¢å¼ã® Python インãƒãƒ¼ãƒˆã‚’使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:430 +#: ../../rst/dev_guide/developing_modules_documenting.rst:443 msgid "The use of \"wildcard\" imports such as ``from module_utils.basic import *`` is no longer allowed." msgstr "``from module_utils.basic import *`` ãªã©ã®ã€Œãƒ¯ã‚¤ãƒ«ãƒ‰ã‚«ãƒ¼ãƒ‰ã€ã‚¤ãƒ³ãƒãƒ¼ãƒˆã®ä½¿ç”¨ã¯è¨±å¯ã•ã‚Œãªããªã‚Šã¾ã—ãŸã€‚" -#: ../../rst/dev_guide/developing_modules_documenting.rst:435 +#: ../../rst/dev_guide/developing_modules_documenting.rst:448 #: ../../rst/dev_guide/testing_documentation.rst:7 msgid "Testing module documentation" msgstr "モジュールドã‚ュメンテーションã®ãƒ†ã‚¹ãƒˆ" -#: ../../rst/dev_guide/developing_modules_documenting.rst:437 +#: ../../rst/dev_guide/developing_modules_documenting.rst:450 msgid "To test Ansible documentation locally please :ref:`follow instruction<testing_module_documentation>`." msgstr "Ansible ドã‚ュメントをãƒãƒ¼ã‚«ãƒ«ã§ãƒ†ã‚¹ãƒˆã™ã‚‹ã«ã¯ã€ã€Œ:ref:`指示ã«å¾“ã†<testing_module_documentation>`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" @@ -4160,108 +4168,107 @@ msgid "Create a playbook in any directory: ``$ touch testmod.yml``" msgstr "ä»»æ„ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã« Playbook を作æˆã—ã¾ã™ (``$ touch testmod.yml``)。" #: ../../rst/dev_guide/developing_modules_general.rst:156 -#: ../../rst/dev_guide/developing_modules_general_windows.rst:522 -msgid "Add the following to the new playbook file::" +msgid "Add the following to the new playbook file:" msgstr "以下を新ã—ã„ Playbook ファイルã«è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general.rst:170 +#: ../../rst/dev_guide/developing_modules_general.rst:172 msgid "Run the playbook and analyze the output: ``$ ansible-playbook ./testmod.yml``" msgstr "Playbook を実行ã—ã€å‡ºåŠ›ã‚’分æžã—ã¾ã™ (``$ ansible-playbook ./testmod.yml``)。" -#: ../../rst/dev_guide/developing_modules_general.rst:173 +#: ../../rst/dev_guide/developing_modules_general.rst:175 msgid "Testing your newly-created module" msgstr "æ–°ãŸã«ä½œæˆã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ†ã‚¹ãƒˆ" -#: ../../rst/dev_guide/developing_modules_general.rst:175 +#: ../../rst/dev_guide/developing_modules_general.rst:177 msgid "The following two examples will get you started with testing your module code. Please review our :ref:`testing <developing_testing>` section for more detailed information, including instructions for :ref:`testing module documentation <testing_module_documentation>`, adding :ref:`integration tests <testing_integration>`, and more." msgstr "以下㮠2 ã¤ã®ä¾‹ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚³ãƒ¼ãƒ‰ã®ãƒ†ã‚¹ãƒˆã‚’開始ã—ã¾ã™ã€‚:ref:`モジュールã®ãƒ†ã‚¹ãƒˆã®ãƒ‰ã‚ュメント <testing_module_documentation>` ã®æ‰‹é †ã€:ref:`çµ±åˆãƒ†ã‚¹ãƒˆ <testing_integration>` ã®è¿½åŠ ãªã©ã®è©³ç´°ãªæƒ…å ±ã¯ã€:ref:`テスト <developing_testing>` ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_modules_general.rst:179 +#: ../../rst/dev_guide/developing_modules_general.rst:181 #: ../../rst/dev_guide/testing_integration.rst:20 msgid "Every new module and plugin should have integration tests, even if the tests cannot be run on Ansible CI infrastructure. In this case, the tests should be marked with the ``unsupported`` alias in `aliases file <https://docs.ansible.com/ansible/latest/dev_guide/testing/sanity/integration-aliases.html>`_." msgstr "テストを Ansible CI インフラストラクãƒãƒ£ãƒ¼ã§å®Ÿè¡Œã§ããªã„å ´åˆã§ã‚‚ã€æ–°ã—ã„モジュールã¨ãƒ—ラグインã«ã¯çµ±åˆãƒ†ã‚¹ãƒˆãŒå¿…è¦ã§ã™ã€‚ã“ã®å ´åˆã€ãƒ†ã‚¹ãƒˆã¯ `aliases ファイル <https://docs.ansible.com/ansible/latest/dev_guide/testing/sanity/integration-aliases.html>`_ ã® ``unsupported`` エイリアスã§ãƒžãƒ¼ã‚¯ä»˜ã‘ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general.rst:183 +#: ../../rst/dev_guide/developing_modules_general.rst:185 msgid "Performing sanity tests" msgstr "å¥å…¨æ€§ãƒ†ã‚¹ãƒˆã®å®Ÿè¡Œ" -#: ../../rst/dev_guide/developing_modules_general.rst:185 +#: ../../rst/dev_guide/developing_modules_general.rst:187 msgid "You can run through Ansible's sanity checks in a container:" msgstr "Ansible ã®å¥å…¨æ€§ãƒã‚§ãƒƒã‚¯ã‚’コンテナーã§å®Ÿè¡Œã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general.rst:187 +#: ../../rst/dev_guide/developing_modules_general.rst:189 msgid "``$ ansible-test sanity -v --docker --python 2.7 MODULE_NAME``" msgstr "``$ ansible-test sanity -v --docker --python 2.7 MODULE_NAME``" -#: ../../rst/dev_guide/developing_modules_general.rst:190 +#: ../../rst/dev_guide/developing_modules_general.rst:192 msgid "Note that this example requires Docker to be installed and running. If you'd rather not use a container for this, you can choose to use ``--venv`` instead of ``--docker``." msgstr "ã“ã®ä¾‹ã§ã¯ã€Docker をインストールã—ã¦å®Ÿè¡Œã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚コンテナーを使用ã—ãªã„å ´åˆã¯ã€``--docker`` ã®ä»£ã‚ã‚Šã« ``--venv`` を使用ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general.rst:195 +#: ../../rst/dev_guide/developing_modules_general.rst:197 msgid "You can add unit tests for your module in ``./test/units/modules``. You must first set up your testing environment. In this example, we're using Python 3.5." msgstr "モジュールã®ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã¯ ``./test/units/modules`` ã§è¿½åŠ ã§ãã¾ã™ã€‚ã¾ãšãƒ†ã‚¹ãƒˆç’°å¢ƒã‚’è¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®ä¾‹ã§ã¯ã€Python 3.5 を使用ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general.rst:197 +#: ../../rst/dev_guide/developing_modules_general.rst:199 msgid "Install the requirements (outside of your virtual environment): ``$ pip3 install -r ./test/lib/ansible_test/_data/requirements/units.txt``" msgstr "(仮想環境外ã«) è¦ä»¶ã‚’インストールã—ã¾ã™ (``$ pip3 install -r ./test/lib/ansible_test/_data/requirements/units.txt``)。" -#: ../../rst/dev_guide/developing_modules_general.rst:198 +#: ../../rst/dev_guide/developing_modules_general.rst:200 msgid "Run ``. hacking/env-setup``" msgstr "``. hacking/env-setup`` を実行ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general.rst:199 +#: ../../rst/dev_guide/developing_modules_general.rst:201 msgid "To run all tests do the following: ``$ ansible-test units --python 3.5``. If you are using a CI environment, these tests will run automatically." msgstr "ã™ã¹ã¦ã®ãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã«ã¯ã€``$ ansible-test units --python 3.5`` を実行ã—ã¾ã™ã€‚CI 環境を使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ã“れらã®ãƒ†ã‚¹ãƒˆãŒè‡ªå‹•çš„ã«å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general.rst:201 +#: ../../rst/dev_guide/developing_modules_general.rst:203 msgid "Ansible uses pytest for unit testing." msgstr "Ansible ã¯ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã« pytest を使用ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general.rst:203 +#: ../../rst/dev_guide/developing_modules_general.rst:205 msgid "To run pytest against a single test module, you can run the following command. Ensure that you are providing the correct path of the test module:" msgstr "å˜ä¸€ã®ãƒ†ã‚¹ãƒˆãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«å¯¾ã—㦠pytest を実行ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚テストモジュールã®æ£ã—ã„パスをæä¾›ã—ã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_modules_general.rst:205 +#: ../../rst/dev_guide/developing_modules_general.rst:207 msgid "``$ pytest -r a --cov=. --cov-report=html --fulltrace --color yes test/units/modules/.../test/my_test.py``" msgstr "``$ pytest -r a --cov=. --cov-report=html --fulltrace --color yes test/units/modules/.../test/my_test.py``" -#: ../../rst/dev_guide/developing_modules_general.rst:209 +#: ../../rst/dev_guide/developing_modules_general.rst:211 msgid "Contributing back to Ansible" msgstr "Ansible ã¸ã®è²¢çŒ®" -#: ../../rst/dev_guide/developing_modules_general.rst:211 +#: ../../rst/dev_guide/developing_modules_general.rst:213 msgid "If you would like to contribute to ``ansible-core`` by adding a new feature or fixing a bug, `create a fork <https://help.github.com/articles/fork-a-repo/>`_ of the ansible/ansible repository and develop against a new feature branch using the ``devel`` branch as a starting point. When you have a good working code change, you can submit a pull request to the Ansible repository by selecting your feature branch as a source and the Ansible devel branch as a target." msgstr "æ–°ã—ã„æ©Ÿèƒ½ã‚’è¿½åŠ ã—ãŸã‚Šãƒã‚°ã‚’ä¿®æ£ã—ãŸã‚Šã—ã¦ã€``ansible-core`` ã«è²¢çŒ®ã™ã‚‹å ´åˆã¯ã€ansible/ansible リãƒã‚¸ãƒˆãƒªãƒ¼ã® `フォークã®ä½œæˆ <https://help.github.com/articles/fork-a-repo/>`_ ã—ã€é–‹å§‹ç‚¹ã¨ã—㦠``devel`` ブランãƒã‚’使用ã—ã¦æ–°æ©Ÿèƒ½ãƒ–ランãƒã«å¯¾ã—ã¦é–‹ç™ºã—ã¾ã™ã€‚é©åˆ‡ãªä½œæ¥ã‚³ãƒ¼ãƒ‰ã‚‚変更ãŒã‚ã‚‹å ´åˆã¯ã€æ©Ÿèƒ½ãƒ–ランãƒã‚’ソースã¨ã—ã¦ã€ãŠã‚ˆã³ Ansible devel ブランãƒã‚’ターゲットã¨ã—ã¦é¸æŠžã—ã€Ansible リãƒã‚¸ãƒˆãƒªãƒ¼ã«ãƒ—ルè¦æ±‚ã‚’é€ä¿¡ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general.rst:213 +#: ../../rst/dev_guide/developing_modules_general.rst:215 msgid "If you want to contribute a module to an :ref:`Ansible collection <contributing_maintained_collections>`, review our :ref:`submission checklist <developing_modules_checklist>`, :ref:`programming tips <developing_modules_best_practices>`, and :ref:`strategy for maintaining Python 2 and Python 3 compatibility <developing_python_3>`, as well as information about :ref:`testing <developing_testing>` before you open a pull request." msgstr "モジュールを :ref:`Ansible コレクション <contributing_maintained_collections>` ã«æä¾›ã™ã‚‹å ´åˆã¯ã€ã€Œ:ref:`æ出ã®ãƒã‚§ãƒƒã‚¯ã‚¢ã‚¦ãƒˆ <developing_modules_checklist>`ã€ã€ã€Œ:ref:`プãƒã‚°ãƒ©ãƒ ã®ãƒ’ント <developing_modules_best_practices>`ã€ã€ãªã‚‰ã³ã«ã€Œ:ref:`Python 2 ãŠã‚ˆã³ Python 3 ã®äº’æ›æ€§ã‚’ç¶æŒã™ã‚‹ã‚¹ãƒˆãƒ©ãƒ†ã‚¸ãƒ¼ <developing_python_3>`ã€ã‚’確èªã—ã¦ãã ã•ã„。プルè¦æ±‚を作æˆã™ã‚‹å‰ã«ã€:ref:`テスト <developing_testing>` ã«é–¢ã™ã‚‹æƒ…å ±ã‚‚ä½µã›ã¦å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/developing_modules_general.rst:215 +#: ../../rst/dev_guide/developing_modules_general.rst:217 msgid "The :ref:`Community Guide <ansible_community_guide>` covers how to open a pull request and what happens next." msgstr "『:ref:`コミュニティーガイド <ansible_community_guide>`ã€ã§ã¯ã€ãƒ—ルè¦æ±‚ã‚’é–‹ã方法ã¨ã€æ¬¡ã«å®Ÿè¡Œã™ã‚‹ã“ã¨ã‚’説明ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general.rst:219 +#: ../../rst/dev_guide/developing_modules_general.rst:221 msgid "Communication and development support" msgstr "通信ãŠã‚ˆã³é–‹ç™ºã®ã‚µãƒãƒ¼ãƒˆ" -#: ../../rst/dev_guide/developing_modules_general.rst:221 +#: ../../rst/dev_guide/developing_modules_general.rst:223 msgid "Join the ``#ansible-devel`` chat channel (using Matrix at ansible.im or using IRC at `irc.libera.chat <https://libera.chat/>`_) for discussions surrounding Ansible development." msgstr "``#ansible-devel`` ãƒãƒ£ãƒƒãƒˆãƒãƒ£ãƒ³ãƒãƒ«ï¼ˆansible.imã§Matrixを使用ã€ã¾ãŸã¯`irc.libera.chat <https://libera.chat/>`ã§IRCを使用）ã«å‚åŠ ã—ã¦ã€Ansible ã®é–‹ç™ºã«é–¢ã™ã‚‹è°è«–ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general.rst:223 +#: ../../rst/dev_guide/developing_modules_general.rst:225 msgid "For questions and discussions pertaining to using the Ansible product, join the ``#ansible`` channel." msgstr "Ansible 製å“ã®ä½¿ç”¨ã«é–¢ã™ã‚‹è³ªå•ãŠã‚ˆã³è²¢çŒ®ã«ã¤ã„ã¦ã¯ã€``#ansible`` ãƒãƒ£ãƒ³ãƒãƒ«ã«å‚åŠ ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general.rst:225 +#: ../../rst/dev_guide/developing_modules_general.rst:227 msgid "To find other topic-specific chat channels, look at :ref:`Community Guide, Communicating <communication_irc>`." msgstr "ä»–ã®ãƒˆãƒ”ック固有ã®ãƒãƒ£ãƒƒãƒˆãƒãƒ£ãƒ³ãƒãƒ«ã‚’探ã™ã«ã¯ã€:ref:`Community Guide, Communicating <communication_irc>` ã‚’ã”覧ãã ã•ã„。" -#: ../../rst/dev_guide/developing_modules_general.rst:228 +#: ../../rst/dev_guide/developing_modules_general.rst:230 msgid "Credit" msgstr "è¬è¾ž" -#: ../../rst/dev_guide/developing_modules_general.rst:230 +#: ../../rst/dev_guide/developing_modules_general.rst:232 msgid "Thank you to Thomas Stringer (`@trstringer <https://github.com/trstringer>`_) for contributing source material for this topic." msgstr "ã“ã®ãƒˆãƒ”ックã®å…ƒã¨ãªã‚‹è³‡æ–™ã‚’æä¾›ã—ã¦ã„ãŸã ã„㟠Thomas Stringer (`@trstringer <https://github.com/trstringer>`_) æ°ã«æ„Ÿè¬ã®æ„を示ã—ã¾ã™ã€‚" @@ -4492,14 +4499,14 @@ msgid "**module_object**: The particular object for this class, for example ``AC msgstr "**module_object**: ã“ã®ã‚¯ãƒ©ã‚¹ã®ç‰¹å®šã®ã‚ªãƒ–ジェクト (例: ``ACME``)" #: ../../rst/dev_guide/developing_modules_general_aci.rst:162 -#: ../../rst/dev_guide/developing_program_flow_modules.rst:597 -#: ../../rst/dev_guide/developing_program_flow_modules.rst:636 -#: ../../rst/dev_guide/developing_program_flow_modules.rst:650 -#: ../../rst/dev_guide/developing_program_flow_modules.rst:750 -#: ../../rst/dev_guide/developing_program_flow_modules.rst:767 -#: ../../rst/dev_guide/developing_program_flow_modules.rst:781 -#: ../../rst/dev_guide/developing_program_flow_modules.rst:808 -#: ../../rst/dev_guide/developing_program_flow_modules.rst:825 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:599 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:638 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:652 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:752 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:769 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:783 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:810 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:827 #: ../../rst/dev_guide/testing_units_modules.rst:90 #: ../../rst/dev_guide/testing_units_modules.rst:109 msgid "Example:" @@ -5397,6 +5404,10 @@ msgstr "åŒã˜ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ ``touch hosts`` ã«ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ•ã msgid "Populate the inventory file with the variables required to connect to a Windows host(s)." msgstr "Windows ホストã¸ã®æŽ¥ç¶šã«å¿…è¦ãªå¤‰æ•°ã‚’指定ã—ã¦ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ•ã‚¡ã‚¤ãƒ«ã‚’è¨å®šã—ã¾ã™ã€‚" +#: ../../rst/dev_guide/developing_modules_general_windows.rst:522 +msgid "Add the following to the new playbook file::" +msgstr "以下を新ã—ã„ Playbook ファイルã«è¿½åŠ ã—ã¾ã™ã€‚" + #: ../../rst/dev_guide/developing_modules_general_windows.rst:532 msgid "Run the playbook ``ansible-playbook -i hosts testmodule.yml``" msgstr "Playbook ``ansible-playbook -i hosts testmodule.yml`` を実行ã—ã¾ã™ã€‚" @@ -5430,102 +5441,102 @@ msgid "Add the following to the start of the module script that was copied to th msgstr "以下をã€ã‚µãƒ¼ãƒãƒ¼ã«ã‚³ãƒ”ーã•ã‚ŒãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚¹ã‚¯ãƒªãƒ—トã®å…ˆé ã«è¿½åŠ ã—ã¾ã™ã€‚" #: ../../rst/dev_guide/developing_modules_general_windows.rst:581 -msgid "You can add more args to ``$complex_args`` as required by the module or define the module options through a JSON file with the structure::" +msgid "You can add more args to ``$complex_args`` as required by the module or define the module options through a JSON file with the structure:" msgstr "モジュールã«å¿…è¦ãªå ´åˆã¯ ``$complex_args`` ã«ã•ã‚‰ã«å¼•æ•°ã‚’è¿½åŠ ã—ãŸã‚Šã€ãã®æ§‹é€ ã‚’æŒã¤ JSON ファイルã§ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚ªãƒ—ションを定義ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:593 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:595 msgid "There are multiple IDEs that can be used to debug a Powershell script, two of the most popular ones are" msgstr "Powershell スクリプトã®ãƒ‡ãƒãƒƒã‚°ã«ä½¿ç”¨ã§ãã‚‹ IDE ãŒè¤‡æ•°ã‚ã‚Šã€ä»¥ä¸‹ã® 2 ã¤ãŒæœ€ã‚‚一般的ãªã‚‚ã®ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:596 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:598 msgid "`Powershell ISE`_" msgstr "`Powershell ISE`_" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:597 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:599 msgid "`Visual Studio Code`_" msgstr "`Visual Studio Code`_" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:602 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:604 msgid "To be able to view the arguments as passed by Ansible to the module follow these steps." msgstr "Ansible ãŒãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«æ¸¡ã—ãŸå¼•æ•°ã‚’表示ã™ã‚‹ã«ã¯ã€æ¬¡ã®æ‰‹é †ã«å¾“ã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:605 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:607 msgid "Prefix the Ansible command with :envvar:`ANSIBLE_KEEP_REMOTE_FILES=1<ANSIBLE_KEEP_REMOTE_FILES>` to specify that Ansible should keep the exec files on the server." msgstr "Ansible コマンドã®å‰ã« :envvar:`ANSIBLE_KEEP_REMOTE_FILES=1<ANSIBLE_KEEP_REMOTE_FILES>` を付ã‘ã¦ã€Ansible ㌠exec ファイルをサーãƒä¸Šã«ä¿æŒã™ã‚‹ã‚ˆã†ã«æŒ‡å®šã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:606 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:608 msgid "Log onto the Windows server using the same user account that Ansible used to execute the module." msgstr "Ansible ãŒãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®å®Ÿè¡Œã«ä½¿ç”¨ã—ãŸã®ã¨åŒã˜ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã‚’使用ã—㦠Windows サーãƒãƒ¼ã«ãƒã‚°ã‚¤ãƒ³ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:607 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:609 msgid "Navigate to ``%TEMP%\\..``. It should contain a folder starting with ``ansible-tmp-``." msgstr "``%TEMP%\\..`` ã«ç§»å‹•ã—ã¾ã™ã€‚ã“ã‚Œã«ã¯ã€``ansible-tmp-`` ã§å§‹ã¾ã‚‹ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ãŒå«ã¾ã‚Œã‚‹ã¯ãšã§ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:608 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:610 msgid "Inside this folder, open the PowerShell script for the module." msgstr "ã“ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼å†…ã§ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã® PowerShell スクリプトを開ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:609 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:611 msgid "In this script is a raw JSON script under ``$json_raw`` which contains the module arguments under ``module_args``. These args can be assigned manually to the ``$complex_args`` variable that is defined on your debug script or put in the ``args.json`` file." msgstr "ã“ã®ã‚¹ã‚¯ãƒªãƒ—トã¯ã€``$json_raw`` ã«ã‚る生㮠JSON スクリプトã§ã€``module_args`` ã®ä¸‹ã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«å¼•æ•°ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ã“れらã®å¼•æ•°ã¯ã€ãƒ‡ãƒãƒƒã‚°ã‚¹ã‚¯ãƒªãƒ—トã§å®šç¾©ã•ã‚Œã‚‹ ``$complex_args`` 変数ã«æ‰‹å‹•ã§å‰²ã‚Šå½“ã¦ãŸã‚Šã€``args.json`` ファイルã«ç½®ã„ãŸã‚Šã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:613 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:615 msgid "Windows unit testing" msgstr "Windows ユニットテスト" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:615 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:617 msgid "Currently there is no mechanism to run unit tests for Powershell modules under Ansible CI." msgstr "ç¾åœ¨ã€Ansible CI 㧠Powershell モジュールã®ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ãƒ¡ã‚«ãƒ‹ã‚ºãƒ ã¯ã‚ã‚Šã¾ã›ã‚“。" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:619 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:621 msgid "Windows integration testing" msgstr "Windows çµ±åˆãƒ†ã‚¹ãƒˆ" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:621 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:623 msgid "Integration tests for Ansible modules are typically written as Ansible roles. These test roles are located in ``./test/integration/targets``. You must first set up your testing environment, and configure a test inventory for Ansible to connect to." msgstr "Ansible モジュールã®çµ±åˆãƒ†ã‚¹ãƒˆã¯é€šå¸¸ Ansible ãƒãƒ¼ãƒ«ã¨ã—ã¦è¨˜è¿°ã•ã‚Œã¾ã™ã€‚ã“れらã®ãƒ†ã‚¹ãƒˆãƒãƒ¼ãƒ«ã¯ ``./test/integration/targets`` ã«ã‚ã‚Šã¾ã™ã€‚ã¾ãšã€ãƒ†ã‚¹ãƒˆç’°å¢ƒã‚’è¨å®šã—ã¦ã€Ansible ãŒæŽ¥ç¶šã§ãるよã†ã«ãƒ†ã‚¹ãƒˆã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚’è¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:625 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:627 msgid "In this example we will set up a test inventory to connect to two hosts and run the integration tests for win_stat:" msgstr "ã“ã®ä¾‹ã§ã¯ã€2 ã¤ã®ãƒ›ã‚¹ãƒˆã«æŽ¥ç¶šã—ã€win_stat ã®çµ±åˆãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ãŸã‚ã®ãƒ†ã‚¹ãƒˆã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚’è¨å®šã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:628 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:630 msgid "Run the command ``source ./hacking/env-setup`` to prepare environment." msgstr "環境を準備ã™ã‚‹ã«ã¯ã€``source ./hacking/env-setup`` コマンドを実行ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:629 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:631 msgid "Create a copy of ``./test/integration/inventory.winrm.template`` and name it ``inventory.winrm``." msgstr "``./test/integration/inventory.winrm.template`` ã®ã‚³ãƒ”ーを作æˆã—ã€``inventory.winrm`` ã¨ã„ã†åå‰ã‚’指定ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:630 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:632 msgid "Fill in entries under ``[windows]`` and set the required variables that are needed to connect to the host." msgstr "``[windows]`` ã®ä¸‹ã«ã‚¨ãƒ³ãƒˆãƒªãƒ¼ã‚’入力ã—ã€ãƒ›ã‚¹ãƒˆã¸ã®æŽ¥ç¶šã«å¿…è¦ãªå¤‰æ•°ã‚’è¨å®šã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:631 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:633 msgid ":ref:`Install the required Python modules <windows_winrm>` to support WinRM and a configured authentication method." msgstr "WinRM ã¨ã€è¨å®šã•ã‚ŒãŸèªè¨¼æ–¹æ³•ã‚’サãƒãƒ¼ãƒˆã™ã‚‹ã®ã« :ref:`å¿…è¦ãª Python モジュールをインストール <windows_winrm>` ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:632 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:634 msgid "To execute the integration tests, run ``ansible-test windows-integration win_stat``; you can replace ``win_stat`` with the role you want to test." msgstr "çµ±åˆãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã«ã¯ã€``ansible-test windows-integration win_stat`` を実行ã—ã¾ã™ã€‚``win_stat`` ã¯ã€ãƒ†ã‚¹ãƒˆã™ã‚‹ãƒãƒ¼ãƒ«ã«ç½®ãæ›ãˆã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:634 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:636 msgid "This will execute all the tests currently defined for that role. You can set the verbosity level using the ``-v`` argument just as you would with ansible-playbook." msgstr "ã“ã‚Œã«ã‚ˆã‚Šã€ãã®ãƒãƒ¼ãƒ«ã«å¯¾ã—ã¦ç¾åœ¨å®šç¾©ã•ã‚Œã¦ã„ã‚‹ã™ã¹ã¦ã®ãƒ†ã‚¹ãƒˆãŒå®Ÿè¡Œã•ã‚Œã¾ã™ã€‚ansible-playbook ã®å ´åˆã¨åŒã˜ã‚ˆã†ã«ã€``-v`` 引数を使用ã—ã¦è©³ç´°ãƒ¬ãƒ™ãƒ«ã‚’è¨å®šã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:638 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:640 msgid "When developing tests for a new module, it is recommended to test a scenario once in check mode and twice not in check mode. This ensures that check mode does not make any changes but reports a change, as well as that the second run is idempotent and does not report changes. For example:" msgstr "æ–°ã—ã„モジュールã®ãƒ†ã‚¹ãƒˆã‚’開発ã™ã‚‹ã¨ãã¯ã€ã‚·ãƒŠãƒªã‚ªã‚’ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã§ 1 回ã€ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ä»¥å¤–㧠2 回テストã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã§ã¯å¤‰æ›´ã¯è¡Œã‚ã‚Œãšã€å¤‰æ›´ãŒå ±å‘Šã•ã‚Œã¾ã™ã€‚ã¾ãŸã€2 回目ã®å®Ÿè¡Œã¯å†ªç‰ã§ã‚ã‚Šã€å¤‰æ›´ã¯å ±å‘Šã•ã‚Œã¾ã›ã‚“。以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:691 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:693 msgid "Windows communication and development support" msgstr "Windows ã®é€šä¿¡ãŠã‚ˆã³é–‹ç™ºã‚µãƒãƒ¼ãƒˆ" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:693 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:695 msgid "Join the ``#ansible-devel`` or ``#ansible-windows`` chat channels (using Matrix at ansible.im or using IRC at `irc.libera.chat <https://libera.chat/>`_) for discussions about Ansible development for Windows." msgstr "``#ansible-devel`` ã¾ãŸã¯``#ansible-windows``ãƒãƒ£ãƒƒãƒˆãƒãƒ£ãƒ³ãƒãƒ«ï¼ˆansible.imã§Matrixを使用ã€ã¾ãŸã¯`irc.libera.chat <https://libera.chat/>`ã§IRCを使用）ã«å‚åŠ ã—ã¦ã€Windowså‘ã‘ã®Ansible 開発ã«é–¢ã™ã‚‹è°è«–ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_modules_general_windows.rst:695 +#: ../../rst/dev_guide/developing_modules_general_windows.rst:697 msgid "For questions and discussions pertaining to using the Ansible product, use the ``#ansible`` channel." msgstr "Ansible 製å“ã®ä½¿ç”¨ã«é–¢ã™ã‚‹è³ªå•ãŠã‚ˆã³è²¢çŒ®ã«ã¤ã„ã¦ã¯ã€``#ansible`` ãƒãƒ£ãƒ³ãƒãƒ«ã‚’使用ã—ã¾ã™ã€‚" @@ -5995,8 +6006,8 @@ msgid "Vars plugins inject additional variable data into Ansible runs that did n msgstr "vars プラグインã¯ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚½ãƒ¼ã‚¹ã€Playbookã€ã¾ãŸã¯ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã«çµ„ã¿è¾¼ã¾ã‚Œã¦ã„ãªã„ Ansible ã®å®Ÿè¡Œã«ã€å¤‰æ•°ãƒ‡ãƒ¼ã‚¿ã‚’è¿½åŠ ã—ã¾ã™ã€‚「host_varsã€ã‚„「group_varsã€ã®ã‚ˆã†ãª Playbook ã®æ§‹æˆè¦ç´ ã¯ã€vars プラグインを使用ã—ã¾ã™ã€‚" #: ../../rst/dev_guide/developing_plugins.rst:476 -msgid "Vars plugins were partially implemented in Ansible 2.0 and rewritten to be fully implemented starting with Ansible 2.4. Vars plugins are unsupported by collections." -msgstr "vars プラグイン㯠Ansible 2.0 ã«éƒ¨åˆ†çš„ã«å®Ÿè£…ã•ã‚Œã€Ansible 2.4 以é™ã§ã¯ã€å®Œå…¨å®Ÿè£…ã«ãªã‚‹ã‚ˆã†ã«æ›¸ãç›´ã•ã‚Œã¾ã—ãŸã€‚vars プラグインã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ã‚µãƒãƒ¼ãƒˆå¯¾è±¡å¤–ã¨ãªã‚Šã¾ã™ã€‚" +msgid "Vars plugins were partially implemented in Ansible 2.0 and rewritten to be fully implemented starting with Ansible 2.4. Vars plugins are supported by collections starting with Ansible 2.10." +msgstr "vars プラグイン㯠Ansible 2.0 ã«éƒ¨åˆ†çš„ã«å®Ÿè£…ã•ã‚Œã€Ansible 2.4 以é™ã§ã¯ã€å®Œå…¨å®Ÿè£…ã«ãªã‚‹ã‚ˆã†ã«æ›¸ãç›´ã•ã‚Œã¾ã—ãŸã€‚vars プラグインã¯Ansible 2.10以é™ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ã‚µãƒãƒ¼ãƒˆå¯¾è±¡ã¨ãªã‚Šã¾ã™ã€‚" #: ../../rst/dev_guide/developing_plugins.rst:478 msgid "Older plugins used a ``run`` method as their main body/work:" @@ -6411,179 +6422,179 @@ msgid "_ansible_selinux_special_fs" msgstr "_ansible_selinux_special_fs" #: ../../rst/dev_guide/developing_program_flow_modules.rst:426 -msgid "List. Names of filesystems which should have a special SELinux context. They are used by the `AnsibleModule` methods which operate on files (changing attributes, moving, and copying). To set, add a comma separated string of filesystem names in :file:`ansible.cfg`::" +msgid "List. Names of filesystems which should have a special SELinux context. They are used by the `AnsibleModule` methods which operate on files (changing attributes, moving, and copying). To set, add a comma separated string of filesystem names in :file:`ansible.cfg`:" msgstr "一覧。特別㪠SELinux コンテã‚ストをæŒã¤å¿…è¦ãŒã‚るファイルシステムã®åå‰ã€‚åå‰ã¯ãƒ•ã‚¡ã‚¤ãƒ« (属性ã®å¤‰æ›´ã€ç§»å‹•ã€ã‚³ãƒ”ー) ã§æ“作ã™ã‚‹ `AnsibleModule` メソッドã«ã‚ˆã£ã¦ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚è¨å®šã™ã‚‹ã«ã¯ã€:file:`ansible.cfg` ã«ã€ãƒ•ã‚¡ã‚¤ãƒ«åã®ã‚³ãƒ³ãƒžåŒºåˆ‡ã‚Šã®æ–‡å—åˆ—ã‚’è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:434 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:436 msgid "Most modules can use the built-in ``AnsibleModule`` methods to manipulate files. To access in a module that needs to know about these special context filesystems, instantiate an ``AnsibleModule`` and examine the list in :attr:`AnsibleModule._selinux_special_fs`." msgstr "ã»ã¨ã‚“ã©ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€ãƒ•ã‚¡ã‚¤ãƒ«ã‚’æ“作ã™ã‚‹çµ„ã¿è¾¼ã¿ ``AnsibleModule`` メソッドを使用ã§ãã¾ã™ã€‚ã“れらã®ç‰¹åˆ¥ãªã‚³ãƒ³ãƒ†ã‚ストファイルシステムã«ã¤ã„ã¦çŸ¥ã‚‹å¿…è¦ãŒã‚るモジュールã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ã«ã¯ã€``AnsibleModule`` をインスタンス化ã—ã€:attr:`AnsibleModule._selinux_special_fs` ã§ãƒªã‚¹ãƒˆã‚’調ã¹ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:438 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:440 msgid "This replaces :attr:`ansible.module_utils.basic.SELINUX_SPECIAL_FS` from :ref:`module_replacer`. In module replacer it was a comma separated string of filesystem names. Under Ansiballz it's an actual list." msgstr "ã“ã‚Œã«ã‚ˆã‚Šã€:ref:`module_replacer` ã® :attr:`ansible.module_utils.basic.SELINUX_SPECIAL_FS` ã‚’ç½®ãæ›ãˆã¾ã™ã€‚モジュール置æ›ã¯ã€ãƒ•ã‚¡ã‚¤ãƒ«åã®ã‚³ãƒ³ãƒžåŒºåˆ‡ã‚Šã®æ–‡å—列ã§ã—ãŸã€‚Ansiballz ã¯ã€å®Ÿéš›ã®ãƒªã‚¹ãƒˆã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:445 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:447 msgid "_ansible_syslog_facility" msgstr "_ansible_syslog_facility" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:447 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:449 msgid "This parameter controls which syslog facility Ansible module logs to. To set, change the ``syslog_facility`` value in :file:`ansible.cfg`. Most modules should just use :meth:`AnsibleModule.log` which will then make use of this. If a module has to use this on its own, it should instantiate an `AnsibleModule` and then retrieve the name of the syslog facility from :attr:`AnsibleModule._syslog_facility`. The Ansiballz code is less hacky than the old :ref:`module_replacer` code:" msgstr "ã“ã®ãƒ‘ラメーターã¯ã€Ansible モジュールãŒã©ã® syslog 機能ã«ãƒã‚°ã‚’記録ã™ã‚‹ã‹ã‚’制御ã—ã¾ã™ã€‚è¨å®šã™ã‚‹ã«ã¯ã€:file:`ansible.cfg` ã® ``syslog_facility`` ã®å€¤ã‚’変更ã—ã¾ã™ã€‚多ãã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€ã“れを利用ã™ã‚‹ :meth:`AnsibleModule.log` ã®ã¿ã‚’使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚モジュールãŒç‹¬è‡ªã«ã“れを使用ã™ã‚‹å¿…è¦ãŒã‚ã‚‹å ´åˆã¯ã€`AnsibleModule` をインスタンス化ã—ã¦ã€:attr:`AnsibleModule._syslog_facility` ã‹ã‚‰ syslog 機能ã®åå‰ã‚’å–å¾—ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚Ansiballz コードã¯å¤ã„ :ref:`module_replacer` コードよりもãƒãƒƒã‚ングã•ã‚Œã¾ã›ã‚“。" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:468 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:470 msgid "_ansible_version" msgstr "_ansible_version" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:470 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:472 msgid "This parameter passes the version of Ansible that runs the module. To access it, a module should instantiate an `AnsibleModule` and then retrieve it from :attr:`AnsibleModule.ansible_version`. This replaces :attr:`ansible.module_utils.basic.ANSIBLE_VERSION` from :ref:`module_replacer`." msgstr "ã“ã®ãƒ‘ラメーターã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’実行ã™ã‚‹ Ansible ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’渡ã—ã¾ã™ã€‚ã“ã‚Œã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ãŸã‚ã«ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ `AnsibleModule` をインスタンス化ã—ã€:attr:`AnsibleModule.ansible_version` ã‹ã‚‰å–å¾—ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€:ref:`module_replacer` ã® :attr:`ansible.module_utils.basic.ANSIBLE_VERSION` ã‚’ç½®ãæ›ãˆã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:482 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:484 msgid "Module return values & Unsafe strings" msgstr "モジュール戻り値ã¨å®‰å…¨ã§ãªã„æ–‡å—列" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:484 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:486 msgid "At the end of a module's execution, it formats the data that it wants to return as a JSON string and prints the string to its stdout. The normal action plugin receives the JSON string, parses it into a Python dictionary, and returns it to the executor." msgstr "モジュールã®å®Ÿè¡Œã®æœ€å¾Œã«ã€è¿”ã—ãŸã„データを JSON æ–‡å—列ã¨ã—ã¦å½¢å¼åŒ–ã—ã€ãã®æ–‡å—列を標準出力 (stdout) ã«å‡ºåŠ›ã—ã¾ã™ã€‚通常㮠action プラグイン㯠JSON æ–‡å—列をå—ã‘å–ã‚Šã€Python ディクショナリーã«è§£æžã—ã¦ã‚¨ã‚¯ã‚¼ã‚ューターã«è¿”ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:486 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:488 msgid "If Ansible templated every string return value, it would be vulnerable to an attack from users with access to managed nodes. If an unscrupulous user disguised malicious code as Ansible return value strings, and if those strings were then templated on the controller, Ansible could execute arbitrary code. To prevent this scenario, Ansible marks all strings inside returned data as ``Unsafe``, emitting any Jinja2 templates in the strings verbatim, not expanded by Jinja2." msgstr "Ansible ãŒã™ã¹ã¦ã®æ–‡å—列ã®æˆ»ã‚Šå€¤ã‚’テンプレート化ã™ã‚‹ã¨ã€ç®¡ç†ãƒŽãƒ¼ãƒ‰ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãるユーザーã‹ã‚‰ã®æ”»æ’ƒã«å¯¾ã—ã¦è„†å¼±ã«ãªã‚Šã¾ã™ã€‚悪æ„ã®ã‚るユーザーãŒæ‚ªæ„ã®ã‚るコードを Ansible ã®æˆ»ã‚Šå€¤ã®æ–‡å—列ã¨ã—ã¦å½è£…ã—ã€ãã®ã‚ˆã†ãªæ–‡å—列ãŒã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©ãƒ¼ä¸Šã§ãƒ†ãƒ³ãƒ—レート化ã•ã‚Œã‚‹ã¨ã€Ansible ãŒä»»æ„ã®ã‚³ãƒ¼ãƒ‰ã‚’実行ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®ã‚·ãƒŠãƒªã‚ªã‚’防ããŸã‚ã«ã€Ansible ã¯æˆ»ã‚Šå€¤ã®ãƒ‡ãƒ¼ã‚¿å†…ã®ã™ã¹ã¦ã®æ–‡å—列を ``Unsafe`` ã¨è¡¨ç¤ºã—ã€æ–‡å—列内㮠Jinja2 テンプレートを Jinja2 ã§å±•é–‹ã›ãšã«ãã®ã¾ã¾ã‚¨ãƒŸãƒƒãƒˆã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:488 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:490 msgid "Strings returned by invoking a module through ``ActionPlugin._execute_module()`` are automatically marked as ``Unsafe`` by the normal action plugin. If another action plugin retrieves information from a module through some other means, it must mark its return data as ``Unsafe`` on its own." msgstr "``ActionPlugin._execute_module()`` を介ã—ã¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’呼ã³å‡ºã—ã¦è¿”ã•ã‚ŒãŸæ–‡å—列ã«ã¯ã€é€šå¸¸ã® action プラグインã«ã‚ˆã£ã¦è‡ªå‹•çš„ã« ``Unsafe`` ã¨ã„ã†ãƒžãƒ¼ã‚¯ãŒä»˜ãã¾ã™ã€‚別㮠action プラグインãŒä»–ã®æ–¹æ³•ã§ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‹ã‚‰æƒ…å ±ã‚’å–å¾—ã—ãŸå ´åˆã¯ã€ãã® action プラグイン自身ãŒãã®æˆ»ã‚Šå€¤ã« ``Unsafe`` ã¨è¡¨ç¤ºã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:490 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:492 msgid "In case a poorly-coded action plugin fails to mark its results as \"Unsafe,\" Ansible audits the results again when they are returned to the executor, marking all strings as ``Unsafe``. The normal action plugin protects itself and any other code that it calls with the result data as a parameter. The check inside the executor protects the output of all other action plugins, ensuring that subsequent tasks run by Ansible will not template anything from those results either." msgstr "ä¸é©åˆ‡ã«ã‚³ãƒ¼ãƒ‡ã‚£ãƒ³ã‚°ã•ã‚ŒãŸ action プラグインãŒçµæžœã‚’「Unsafeã€ã¨è¡¨ç¤ºã—ãªã‹ã£ãŸå ´åˆã€Ansible ã¯ã‚¨ã‚°ã‚¼ã‚ューターã«è¿”ã•ã‚Œã‚‹éš›ã«çµæžœã‚’å†åº¦ç›£æŸ»ã—ã€ã™ã¹ã¦ã®æ–‡å—列を ``Unsafe`` ã¨è¡¨ç¤ºã—ã¾ã™ã€‚通常㮠action プラグインã¯ã€è‡ªèº«ã¨ã€çµæžœãƒ‡ãƒ¼ã‚¿ã‚’パラメーターã¨ã—ã¦å‘¼ã³å‡ºã™ãã®ä»–ã®ã‚³ãƒ¼ãƒ‰ã‚’ä¿è·ã—ã¾ã™ã€‚エクゼã‚ュータ内ã®ãƒã‚§ãƒƒã‚¯ã¯ã€ä»–ã®ã™ã¹ã¦ã® action プラグインã®å‡ºåŠ›ã‚’ä¿è·ã—ã€Ansible ãŒå®Ÿè¡Œã™ã‚‹å¾Œç¶šã®ã‚¿ã‚¹ã‚¯ãŒã“れらã®çµæžœã‹ã‚‰ä½•ã‹ã‚’テンプレート化ã™ã‚‹ã“ã¨ãŒãªã„よã†ã«ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:496 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:498 msgid "Special considerations" msgstr "特別ãªè€ƒæ…®äº‹é …" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:501 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:503 msgid "Pipelining" msgstr "パイプライン" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:503 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:505 msgid "Ansible can transfer a module to a remote machine in one of two ways:" msgstr "Ansible ã¯ã€ä»¥ä¸‹ã®ã„ãšã‚Œã‹ã®æ–¹æ³•ã§ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’リモートマシンã«è»¢é€ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:505 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:507 msgid "it can write out the module to a temporary file on the remote host and then use a second connection to the remote host to execute it with the interpreter that the module needs" msgstr "ã“ã‚Œã¯ã€ãƒªãƒ¢ãƒ¼ãƒˆãƒ›ã‚¹ãƒˆã®ä¸€æ™‚ファイルã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’書ã込むã“ã¨ãŒã§ãã€æ¬¡ã«ãƒªãƒ¢ãƒ¼ãƒˆãƒ›ã‚¹ãƒˆã¸ã® 2 番目ã®æŽ¥ç¶šã‚’使用ã—ã¦ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒå¿…è¦ã¨ã™ã‚‹ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ—リターã§ã“れを実行ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:508 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:510 msgid "or it can use what's known as pipelining to execute the module by piping it into the remote interpreter's stdin." msgstr "ã¾ãŸã¯ã€ãƒ‘イプラインã¨å‘¼ã°ã‚Œã‚‹ã‚‚ã®ã‚’使用ã—ã¦ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’リモートインタープリター㮠stdin ã«ãƒ‘イプã™ã‚‹ã“ã¨ã§ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’実行ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:511 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:513 msgid "Pipelining only works with modules written in Python at this time because Ansible only knows that Python supports this mode of operation. Supporting pipelining means that whatever format the module payload takes before being sent over the wire must be executable by Python via stdin." msgstr "パイプライン処ç†ã¯ã€ç¾æ™‚点ã§ã¯ Python ã§è¨˜è¿°ã•ã‚ŒãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã§ã®ã¿æ©Ÿèƒ½ã—ã¾ã™ã€‚ã“ã‚Œã¯ã€Python ãŒã“ã®æ“作モードをサãƒãƒ¼ãƒˆã—ã¦ã„ã‚‹ã“ã¨ã®ã¿ã‚’ Ansible ãŒèªè˜ã—ã¦ã„ã‚‹ãŸã‚ã§ã™ã€‚パイプライン化をサãƒãƒ¼ãƒˆã™ã‚‹ã¨ã„ã†ã“ã¨ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒšã‚¤ãƒãƒ¼ãƒ‰ãŒãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯çµŒç”±ã§é€ä¿¡ã•ã‚Œã‚‹å‰ã«å–ã‚‹å½¢å¼ãŒä½•ã§ã‚ã‚Œã€Python ㌠stdin を介ã—ã¦å®Ÿè¡Œå¯èƒ½ã§ãªã‘ã‚Œã°ãªã‚‰ãªã„ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:519 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:521 msgid "Why pass args over stdin?" msgstr "標準入力 (stdin) ã§å¼•æ•°ã‚’渡ã™ç†ç”±" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:521 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:523 msgid "Passing arguments via stdin was chosen for the following reasons:" msgstr "以下ã®ç†ç”±ã«ã‚ˆã‚Šã€æ¨™æº–入力ã§å¼•æ•°ã‚’渡ã™ã“ã¨ãŒé¸æŠžã•ã‚Œã¾ã—ãŸã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:523 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:525 msgid "When combined with :ref:`ANSIBLE_PIPELINING`, this keeps the module's arguments from temporarily being saved onto disk on the remote machine. This makes it harder (but not impossible) for a malicious user on the remote machine to steal any sensitive information that may be present in the arguments." msgstr ":ref:`ANSIBLE_PIPELINING` ã¨çµ„ã¿åˆã‚ã›ã‚‹ã¨ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®å¼•æ•°ã‚’リモートマシン上ã®ãƒ‡ã‚£ã‚¹ã‚¯ã«ä¸€æ™‚çš„ã«ä¿å˜ã—ãŸã¾ã¾ã«ã—ã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ãƒªãƒ¢ãƒ¼ãƒˆãƒžã‚·ãƒ³ä¸Šã®æ‚ªæ„ã®ã‚るユーザーãŒå¼•æ•°ã«å˜åœ¨ã™ã‚‹å¯èƒ½æ€§ã®ã‚ã‚‹æ©Ÿå¯†æƒ…å ±ã‚’ç›—ã‚€ã®ãŒå›°é›£ã«ãªã‚Šã¾ã™ (ä¸å¯èƒ½ã§ã¯ã‚ã‚Šã¾ã›ã‚“)。" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:527 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:529 msgid "Command line arguments would be insecure as most systems allow unprivileged users to read the full commandline of a process." msgstr "ã»ã¨ã‚“ã©ã®ã‚·ã‚¹ãƒ†ãƒ ã§ã¯ã€æ¨©é™ã®ãªã„ユーザーãŒãƒ—ãƒã‚»ã‚¹ã®ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³å…¨ä½“ã‚’èªã‚€ã“ã¨ã‚’許å¯ã•ã‚Œã¦ã„ã‚‹ãŸã‚ã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³å¼•æ•°ã¯å®‰å…¨ã§ã¯ã‚ã‚Šã¾ã›ã‚“。" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:529 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:531 msgid "Environment variables are usually more secure than the commandline but some systems limit the total size of the environment. This could lead to truncation of the parameters if we hit that limit." msgstr "環境変数ã¯é€šå¸¸ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã‚ˆã‚Šå®‰å…¨ã§ã™ãŒã€ç’°å¢ƒã®åˆè¨ˆã‚µã‚¤ã‚ºã‚’制é™ã™ã‚‹ã‚·ã‚¹ãƒ†ãƒ ã‚‚ã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ãƒ‘ラメーターãŒä¸Šé™ã«é”ã™ã‚‹ã¨ã€ãƒ‘ラメーターãŒåˆ‡ã‚Šæ¨ã¦ã‚‰ã‚Œã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:537 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:539 msgid "AnsibleModule" msgstr "AnsibleModule" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:542 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:544 msgid "Argument spec" msgstr "引数ã®ä»•æ§˜" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:544 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:546 msgid "The ``argument_spec`` provided to ``AnsibleModule`` defines the supported arguments for a module, as well as their type, defaults and more." msgstr "``AnsibleModule`` ã«æä¾›ã•ã‚Œã‚‹ ``argument_spec`` ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã§ã‚µãƒãƒ¼ãƒˆã•ã‚Œã‚‹å¼•æ•°ã€ãã®åž‹ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãªã©ã‚’定義ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:546 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:548 msgid "Example ``argument_spec``:" msgstr "``argument_spec`` ã®ä¾‹:" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:562 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:564 msgid "This section will discuss the behavioral attributes for arguments:" msgstr "本セクションã§ã¯ã€å¼•æ•°ã®å‹•ä½œå±žæ€§ã‚’説明ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:566 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:568 msgid "``type`` allows you to define the type of the value accepted for the argument. The default value for ``type`` is ``str``. Possible values are:" msgstr "``type`` ã§ã¯ã€å¼•æ•°ã«å—ã‘入れられる値ã®åž‹ã‚’定義ã§ãã¾ã™ã€‚``type`` ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã¯ ``str`` ã§ã™ã€‚å¯èƒ½ãªå€¤ã¯æ¬¡ã®ã¨ãŠã‚Šã§ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:568 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:570 msgid "str" msgstr "str" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:569 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:571 msgid "list" msgstr "list" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:570 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:572 msgid "dict" msgstr "dict" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:571 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:573 msgid "bool" msgstr "bool" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:572 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:574 msgid "int" msgstr "int" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:573 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:575 msgid "float" msgstr "float" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:574 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:576 msgid "path" msgstr "path" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:575 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:577 msgid "raw" msgstr "raw" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:576 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:578 msgid "jsonarg" msgstr "jsonarg" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:577 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:579 #: ../../rst/dev_guide/style_guide/index.rst:150 msgid "json" msgstr "json" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:578 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:580 msgid "bytes" msgstr "bytes" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:579 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:581 msgid "bits" msgstr "bits" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:581 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:583 msgid "The ``raw`` type, performs no type validation or type casting, and maintains the type of the passed value." msgstr "``raw`` åž‹ã§ã€åž‹ã®æ¤œè¨¼ã‚„åž‹ã‚ャストを行ã‚ãšã€æ¸¡ã•ã‚ŒãŸå€¤ã®åž‹ã‚’ä¿æŒã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:585 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:587 msgid "``elements`` works in combination with ``type`` when ``type='list'``. ``elements`` can then be defined as ``elements='int'`` or any other type, indicating that each element of the specified list should be of that type." msgstr "``elements`` ã¯ã€``type='list'`` ã®æ™‚ã« ``type`` ã¨çµ„ã¿åˆã‚ã›ã¦å‹•ä½œã—ã¾ã™ã€‚``elements`` 㯠``elements='int'`` ãªã©ã®åž‹ã§å®šç¾©ã™ã‚‹ã“ã¨ãŒã§ãã€æŒ‡å®šã•ã‚ŒãŸãƒªã‚¹ãƒˆã®å„è¦ç´ ãŒãã®åž‹ã§ã‚ã‚‹ã“ã¨ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:589 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:591 msgid "The ``default`` option allows sets a default value for the argument for the scenario when the argument is not provided to the module. When not specified, the default value is ``None``." msgstr "``default`` オプションã¯ã€å¼•æ•°ãŒãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«æä¾›ã•ã‚Œã¦ã„ãªã„å ´åˆã®ã‚·ãƒŠãƒªã‚ªã®å¼•æ•°ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã‚’è¨å®šã—ã¾ã™ã€‚指定ã—ãªã„å ´åˆã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã¯ ``None`` ã§ã™ã€‚" @@ -6591,19 +6602,19 @@ msgstr "``default`` オプションã¯ã€å¼•æ•°ãŒãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«æä¾›ã•ã‚Œ msgid "fallback" msgstr "fallback" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:593 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:595 msgid "``fallback`` accepts a ``tuple`` where the first argument is a callable (function) that will be used to perform the lookup, based on the second argument. The second argument is a list of values to be accepted by the callable." msgstr "``fallback`` ã¯ã€ç¬¬ 1 引数ã«ã€ç¬¬ 2 引数ã«åŸºã¥ã„ã¦æ¤œç´¢ã‚’実行ã™ã‚‹ã®ã«ä½¿ç”¨ã™ã‚‹ callable (関数) ã® ``tuple`` ã‚’å—ã‘入れã¾ã™ã€‚2 ã¤ç›®ã®å¼•æ•°ã¯ã€callable オブジェクトã«ã‚ˆã£ã¦å—ã‘入れられる値ã®ãƒªã‚¹ãƒˆã§ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:595 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:597 msgid "The most common callable used is ``env_fallback`` which will allow an argument to optionally use an environment variable when the argument is not supplied." msgstr "最も一般的ã«ä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹ callable 㯠``env_fallback`` ã§ã€ã“ã‚Œã¯å¼•æ•°ãŒè¨å®šã•ã‚Œã¦ã„ãªã„å ´åˆã«ä»»æ„ã§ç’°å¢ƒå¤‰æ•°ã‚’使用ã§ãるよã†ã«ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:605 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:607 msgid "``choices`` accepts a list of choices that the argument will accept. The types of ``choices`` should match the ``type``." msgstr "``choices`` ã¯ã€å¼•æ•°ãŒå—ã‘入れるé¸æŠžè‚¢ã®ãƒªã‚¹ãƒˆã‚’å—ã‘入れã¾ã™ã€‚``choices`` ã®åž‹ã¯ã€``type`` ã¨ä¸€è‡´ã—ã¦ã„ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:609 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:611 msgid "``required`` accepts a boolean, either ``True`` or ``False`` that indicates that the argument is required. When not specified, ``required`` defaults to ``False``. This should not be used in combination with ``default``." msgstr "``required`` ブール値 (``True`` ã¾ãŸã¯ ``False`` ã®ã„ãšã‚Œã‹) ã‚‚å—ã‘入れã¾ã™ã€‚ã“ã‚Œã¯ã€å¼•æ•°ãŒå¿…è¦ã§ã‚ã‚‹ã“ã¨ã‚’示ã—ã¦ã„ã¾ã™ã€‚指定ã—ãªã„å ´åˆã€``required`` ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã¯ ``False`` ã«ãªã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€``default`` ã¨çµ„ã¿åˆã‚ã›ã¦ä½¿ç”¨ã—ãªã„ã§ãã ã•ã„。" @@ -6611,19 +6622,19 @@ msgstr "``required`` ブール値 (``True`` ã¾ãŸã¯ ``False`` ã®ã„ãšã‚Œã‹) msgid "no_log" msgstr "no_log" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:613 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:615 msgid "``no_log`` accepts a boolean, either ``True`` or ``False``, that indicates explicitly whether or not the argument value should be masked in logs and output." msgstr "``no_log`` ã«ã¯ã€å¼•æ•°ã®å€¤ãŒãƒã‚°ã‚„出力ã§ãƒžã‚¹ã‚¯ã•ã‚Œã‚‹ã¹ãã‹ã©ã†ã‹ã‚’明示的ã«ç¤ºã™ãƒ–ール値 (``True`` ã¾ãŸã¯ ``False``) を使用ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:616 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:618 msgid "In the absence of ``no_log``, if the parameter name appears to indicate that the argument value is a password or passphrase (such as \"admin_password\"), a warning will be shown and the value will be masked in logs but **not** output. To disable the warning and masking for parameters that do not contain sensitive information, set ``no_log`` to ``False``." msgstr "``no_log`` ãŒãªã„å ´åˆã¯ã€ãƒ‘ラメーターåãŒã€å¼•æ•°ã®å€¤ãŒãƒ‘スワードやパスフレーズã§ã‚ã‚‹ã“ã¨ã‚’示ã—ã¦ã„るよã†ã«è¦‹ãˆã‚‹å ´åˆ (「admin_passwordã€ãªã©)ã€è¦å‘ŠãŒè¡¨ç¤ºã•ã‚Œã€å€¤ã¯ãƒã‚°ã§ãƒžã‚¹ã‚¯ã•ã‚Œã¾ã™ãŒã€**出力ã•ã‚Œã¾ã›ã‚“**ã€‚æ©Ÿå¯†æƒ…å ±ã‚’å«ã¾ãªã„パラメーターã®è¦å‘Šã¨ãƒžã‚¹ã‚ングを無効ã«ã™ã‚‹ã«ã¯ã€``no_log`` ã‚’ ``False`` ã«è¨å®šã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:620 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:622 msgid "``aliases`` accepts a list of alternative argument names for the argument, such as the case where the argument is ``name`` but the module accepts ``aliases=['pkg']`` to allow ``pkg`` to be interchangeably with ``name``" msgstr "``aliases`` ã§ã¯ã€å¼•æ•°ã®ä»£æ›¿å¼•æ•°åã®ãƒªã‚¹ãƒˆãŒä½¿ç”¨ã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€å¼•æ•°ã¯ ``name`` ã§ã™ãŒã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒ ``aliases=['pkg']`` ã‚’å—ã‘付ã‘ã¦ã€``pkg`` ã‚’ ``name`` ã¨äº’æ›æ€§ã‚’æŒãŸã›ã‚‹ã‚ˆã†ã«ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:624 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:626 msgid "``options`` implements the ability to create a sub-argument_spec, where the sub options of the top level argument are also validated using the attributes discussed in this section. The example at the top of this section demonstrates use of ``options``. ``type`` or ``elements`` should be ``dict`` is this case." msgstr "``options`` ã¯ã€ä¸Šä½ãƒ¬ãƒ™ãƒ«ã®å¼•æ•°ã®ã‚µãƒ–オプションもã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§èª¬æ˜Žã—ãŸå±žæ€§ã‚’使用ã—ã¦æ¤œè¨¼ã•ã‚Œã‚‹ sub-argument_spec を作æˆã™ã‚‹æ©Ÿèƒ½ã‚’実装ã—ã¦ã„ã¾ã™ã€‚ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã®å†’é ã«ã‚る例ã¯ã€``options`` ã®ä½¿ç”¨ã‚’示ã—ã¦ã„ã¾ã™ã€‚ã“ã“ã§ã¯ã€``type`` ã¾ãŸã¯ ``elements`` 㯠``dict`` ã§ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" @@ -6631,11 +6642,11 @@ msgstr "``options`` ã¯ã€ä¸Šä½ãƒ¬ãƒ™ãƒ«ã®å¼•æ•°ã®ã‚µãƒ–オプションも㓠msgid "apply_defaults" msgstr "apply_defaults" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:628 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:630 msgid "``apply_defaults`` works alongside ``options`` and allows the ``default`` of the sub-options to be applied even when the top-level argument is not supplied." msgstr "``apply_defaults`` ã¯ã€``options`` ã¨ä¸¦ã‚“ã§å‹•ä½œã—ã€ä¸Šä½ãƒ¬ãƒ™ãƒ«ã®å¼•æ•°ãŒæŒ‡å®šã•ã‚Œã¦ã„ãªã„å ´åˆã§ã‚‚サブオプション㮠``デフォルト`` ã‚’é©ç”¨ã§ãるよã†ã«ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:630 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:632 msgid "In the example of the ``argument_spec`` at the top of this section, it would allow ``module.params['top_level']['second_level']`` to be defined, even if the user does not provide ``top_level`` when calling the module." msgstr "ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã®å†’é ã«ã‚ã‚‹ ``argument_spec`` ã®ä¾‹ã§ã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’呼ã³å‡ºã™ã¨ãã« ``top_level`` を指定ã—ãªã‹ã£ãŸå ´åˆã§ã‚‚ã€``module.params['top_level']['second_level']`` を定義ã§ãるよã†ã«ã—ã¾ã™ã€‚" @@ -6643,7 +6654,7 @@ msgstr "ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã®å†’é ã«ã‚ã‚‹ ``argument_spec`` ã®ä¾‹ã§ã¯ã€ msgid "removed_in_version" msgstr "removed_in_version" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:634 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:636 msgid "``removed_in_version`` indicates which version of ansible-core or a collection a deprecated argument will be removed in. Mutually exclusive with ``removed_at_date``, and must be used with ``removed_from_collection``." msgstr "``removed_in_version`` ã¯ã€éžæŽ¨å¥¨ã®å¼•æ•°ãŒå‰Šé™¤ã•ã‚Œã‚‹ ansible-core ã¾ãŸã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’示ã—ã¾ã™ã€‚``removed_at_date`` ã§ç›¸äº’ã«æŽ’ä»–ã¨ãªã‚Šã€``removed_from_collection`` ã§ä½¿ç”¨ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" @@ -6651,7 +6662,7 @@ msgstr "``removed_in_version`` ã¯ã€éžæŽ¨å¥¨ã®å¼•æ•°ãŒå‰Šé™¤ã•ã‚Œã‚‹ ansibl msgid "removed_at_date" msgstr "removed_at_date" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:648 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:650 msgid "``removed_at_date`` indicates that a deprecated argument will be removed in a minor ansible-core release or major collection release after this date. Mutually exclusive with ``removed_in_version``, and must be used with ``removed_from_collection``." msgstr "``removed_at_date`` ã¯ã€éžæŽ¨å¥¨ã®å¼•æ•°ãŒã€ã“ã®æ—¥ä»˜ä»¥é™ã®ãƒžã‚¤ãƒŠãƒ¼ãª ansible-core リリースã¾ãŸã¯ãƒ¡ã‚¸ãƒ£ãƒ¼ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã‚‹ã“ã¨ã‚’示ã—ã¾ã™ã€‚``removed_in_version`` ã¨ç›¸äº’ã«æŽ’ä»–çš„ã§ã‚ã‚Šã€``removed_from_collection`` ã¨ä¸€ç·’ã«ä½¿ç”¨ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" @@ -6659,7 +6670,7 @@ msgstr "``removed_at_date`` ã¯ã€éžæŽ¨å¥¨ã®å¼•æ•°ãŒã€ã“ã®æ—¥ä»˜ä»¥é™ã®ã msgid "removed_from_collection" msgstr "removed_from_collection" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:662 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:664 msgid "Specifies which collection (or ansible-core) deprecates this deprecated argument. Specify ``ansible.builtin`` for ansible-core, or the collection's name (format ``foo.bar``). Must be used with ``removed_in_version`` or ``removed_at_date``." msgstr "ã“ã®éžæŽ¨å¥¨ã®å¼•æ•°ã‚’éžæŽ¨å¥¨ã«ã™ã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (ã¾ãŸã¯ ansible-core) を指定ã—ã¾ã™ã€‚ansible-core ã«ã¯ ``ansible.builtin``ã€ã¾ãŸã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®åå‰ (``foo.bar`` ã®å½¢å¼) を指定ã—ã¾ã™ã€‚``removed_in_version`` ã¾ãŸã¯ ``removed_at_date`` ã¨å…±ã«ä½¿ç”¨ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" @@ -6667,7 +6678,7 @@ msgstr "ã“ã®éžæŽ¨å¥¨ã®å¼•æ•°ã‚’éžæŽ¨å¥¨ã«ã™ã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (ã¾ãŸã msgid "deprecated_aliases" msgstr "deprecated_aliases" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:666 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:668 msgid "Deprecates aliases of this argument. Must contain a list or tuple of dictionaries having some the following keys:" msgstr "ã“ã®å¼•æ•°ã®ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã‚’éžæŽ¨å¥¨ã«ã—ã¾ã™ã€‚以下ã®ã‚ーをæŒã¤ãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼ã®ãƒªã‚¹ãƒˆã¾ãŸã¯ã‚¿ãƒ—ルãŒå«ã¾ã‚Œã¾ã™ã€‚" @@ -6675,7 +6686,7 @@ msgstr "ã“ã®å¼•æ•°ã®ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã‚’éžæŽ¨å¥¨ã«ã—ã¾ã™ã€‚以下ã®ã‚ー msgid "name" msgstr "name" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:670 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:672 msgid "The name of the alias to deprecate. (Required.)" msgstr "éžæŽ¨å¥¨ã«ã™ã‚‹ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã®åå‰ (å¿…é ˆ)" @@ -6684,7 +6695,7 @@ msgstr "éžæŽ¨å¥¨ã«ã™ã‚‹ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã®åå‰ (å¿…é ˆ)" msgid "version" msgstr "version" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:674 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:676 msgid "The version of ansible-core or the collection this alias will be removed in. Either ``version`` or ``date`` must be specified." msgstr "ansible-coreã€ã¾ãŸã¯ã“ã®ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã¯å‰Šé™¤ã•ã‚Œã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã€‚``version`` ã¾ãŸã¯ ``date`` ã®ã„ãšã‚Œã‹ã‚’指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" @@ -6692,7 +6703,7 @@ msgstr "ansible-coreã€ã¾ãŸã¯ã“ã®ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã¯å‰Šé™¤ã•ã‚Œã‚‹ã‚³ãƒ¬ã‚¯ msgid "date" msgstr "date" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:678 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:680 msgid "The a date after which a minor release of ansible-core or a major collection release will no longer contain this alias.. Either ``version`` or ``date`` must be specified." msgstr "ansible-core ã®ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ã¾ãŸã¯ãƒ¡ã‚¸ãƒ£ãƒ¼ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãƒªãƒªãƒ¼ã‚¹ã«ã“ã®ã‚¨ã‚¤ãƒªã‚¢ã‚¹ãŒå«ã¾ã‚Œãªããªã£ãŸæ—¥ä»˜ã€‚``version`` ã¾ãŸã¯ ``date`` ã®ã„ãšã‚Œã‹ã‚’指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" @@ -6700,11 +6711,11 @@ msgstr "ansible-core ã®ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ã¾ãŸã¯ãƒ¡ã‚¸ãƒ£ãƒ¼ã‚³ãƒ¬ã‚¯ã‚ msgid "collection_name" msgstr "collection_name" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:682 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:684 msgid "Specifies which collection (or ansible-core) deprecates this deprecated alias. Specify ``ansible.builtin`` for ansible-core, or the collection's name (format ``foo.bar``). Must be used with ``version`` or ``date``." msgstr "ã“ã®éžæŽ¨å¥¨ã®ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã‚’éžæŽ¨å¥¨ã«ã™ã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (ã¾ãŸã¯ ansible-core) を指定ã—ã¾ã™ã€‚ansible-core ã«ã¯ ``ansible.builtin``ã€ã¾ãŸã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®åå‰ (``foo.bar`` ã®å½¢å¼) を指定ã—ã¾ã™ã€‚``version`` ã¾ãŸã¯ ``date`` ã¨å…±ã«ä½¿ç”¨ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:684 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:686 msgid "Examples:" msgstr "例:" @@ -6712,7 +6723,7 @@ msgstr "例:" msgid "mutually_exclusive" msgstr "mutually_exclusive" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:708 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:710 msgid "If ``options`` is specified, ``mutually_exclusive`` refers to the sub-options described in ``options`` and behaves as in :ref:`argument_spec_dependencies`." msgstr "``options`` を指定ã™ã‚‹ã¨ã€``mutually_exclusive`` 㯠``options`` ã§èª¬æ˜Žã•ã‚Œã¦ã„るサブオプションをå‚ç…§ã—ã€:ref:`argument_spec_dependencies` ã®ã‚ˆã†ã«å‹•ä½œã—ã¾ã™ã€‚" @@ -6720,7 +6731,7 @@ msgstr "``options`` を指定ã™ã‚‹ã¨ã€``mutually_exclusive`` 㯠``options`` msgid "required_together" msgstr "required_together" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:712 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:714 msgid "If ``options`` is specified, ``required_together`` refers to the sub-options described in ``options`` and behaves as in :ref:`argument_spec_dependencies`." msgstr "``options`` を指定ã™ã‚‹ã¨ã€``required_together`` 㯠``options`` ã§èª¬æ˜Žã•ã‚Œã¦ã„るサブオプションをå‚ç…§ã—ã€:ref:`argument_spec_dependencies` ã®ã‚ˆã†ã«å‹•ä½œã—ã¾ã™ã€‚" @@ -6728,7 +6739,7 @@ msgstr "``options`` を指定ã™ã‚‹ã¨ã€``required_together`` 㯠``options`` ã msgid "required_one_of" msgstr "required_one_of" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:716 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:718 msgid "If ``options`` is specified, ``required_one_of`` refers to the sub-options described in ``options`` and behaves as in :ref:`argument_spec_dependencies`." msgstr "``options`` を指定ã™ã‚‹ã¨ã€``required_one_of`` 㯠``options`` ã§èª¬æ˜Žã•ã‚Œã¦ã„るサブオプションをå‚ç…§ã—ã€:ref:`argument_spec_dependencies` ã®ã‚ˆã†ã«å‹•ä½œã—ã¾ã™ã€‚" @@ -6736,7 +6747,7 @@ msgstr "``options`` を指定ã™ã‚‹ã¨ã€``required_one_of`` 㯠``options`` 㧠msgid "required_if" msgstr "required_if" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:720 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:722 msgid "If ``options`` is specified, ``required_if`` refers to the sub-options described in ``options`` and behaves as in :ref:`argument_spec_dependencies`." msgstr "``options`` を指定ã™ã‚‹ã¨ã€``required_if`` 㯠``options`` ã§èª¬æ˜Žã•ã‚Œã¦ã„るサブオプションをå‚ç…§ã—ã€:ref:`argument_spec_dependencies` ã®ã‚ˆã†ã«å‹•ä½œã—ã¾ã™ã€‚" @@ -6744,103 +6755,103 @@ msgstr "``options`` を指定ã™ã‚‹ã¨ã€``required_if`` 㯠``options`` ã§èª¬æ msgid "required_by" msgstr "required_by" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:724 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:726 msgid "If ``options`` is specified, ``required_by`` refers to the sub-options described in ``options`` and behaves as in :ref:`argument_spec_dependencies`." msgstr "``options`` を指定ã™ã‚‹ã¨ã€``required_by`` 㯠``options`` ã§èª¬æ˜Žã•ã‚Œã¦ã„るサブオプションをå‚ç…§ã—ã€:ref:`argument_spec_dependencies` ã®ã‚ˆã†ã«å‹•ä½œã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:730 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:732 msgid "Dependencies between module options" msgstr "モジュールオプションã®ä¾å˜é–¢ä¿‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:732 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:734 msgid "The following are optional arguments for ``AnsibleModule()``:" msgstr "以下ã¯ã€``AnsibleModule()`` ã®ä»»æ„ã®å¼•æ•°ã§ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:748 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:750 msgid "Must be a sequence (list or tuple) of sequences of strings. Every sequence of strings is a list of option names which are mutually exclusive. If more than one options of a list are specified together, Ansible will fail the module with an error." msgstr "æ–‡å—列シーケンスã®ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ (リストã¾ãŸã¯ã‚¿ãƒ—ル) ã§ã™ã€‚æ–‡å—列ã®ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ã¯ç›¸äº’排他的ãªã‚ªãƒ—ションåã®ãƒªã‚¹ãƒˆã§ã™ã€‚リストã®è¤‡æ•°ã®ã‚ªãƒ—ションを指定ã™ã‚‹ã¨ã€Ansible ã¯ã‚¨ãƒ©ãƒ¼ã‚’出ã—ã¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«å¤±æ•—ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:759 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:761 msgid "In this example, the options ``path`` and ``content`` must not specified at the same time. Also the options ``repository_url`` and ``repository_filename`` must not be specified at the same time. But specifying ``path`` and ``repository_url`` is accepted." msgstr "ã“ã®ä¾‹ã§ã¯ã€``path`` オプション㨠``content`` オプションã¯åŒæ™‚ã«æŒ‡å®šã—ãªã„ã§ãã ã•ã„。``repository_url`` オプション㨠``repository_filename`` オプションをåŒæ™‚ã«æŒ‡å®šã™ã‚‹ã“ã¨ã¯ã§ãã¾ã›ã‚“。ãŸã ã—ã€``path`` ãŠã‚ˆã³ ``repository_url`` を指定ã™ã‚‹ã“ã¨ã¯ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:761 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:763 msgid "To ensure that precisely one of two (or more) options is specified, combine ``mutually_exclusive`` with ``required_one_of``." msgstr "æ£ç¢ºã« 2 ã¤ã®ã‚ªãƒ—ション (ã¾ãŸã¯è¤‡æ•°ã®) オプションã®ã„ãšã‚Œã‹ã‚’指定ã™ã‚‹ã‚ˆã†ã«ã™ã‚‹ã«ã¯ã€``mutually_exclusive`` 㨠``required_one_of`` を組ã¿åˆã‚ã›ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:765 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:767 msgid "Must be a sequence (list or tuple) of sequences of strings. Every sequence of strings is a list of option names which are must be specified together. If at least one of these options are specified, the other ones from the same sequence must all be present." msgstr "æ–‡å—列ã®ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ã®ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ (リストã¾ãŸã¯ã‚¿ãƒ—ル) ã§ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚æ–‡å—列ã®ã™ã¹ã¦ã®ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ã¯ã€ä¸€ç·’ã«æŒ‡å®šã™ã‚‹å¿…è¦ãŒã‚るオプションåã®ãƒªã‚¹ãƒˆã§ã™ã€‚ã“れらã®ã‚ªãƒ—ションãŒå°‘ãªãã¨ã‚‚ 1 ã¤æŒ‡å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€åŒã˜ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ã®ä»–ã®ã‚ªãƒ—ションãŒã™ã¹ã¦å˜åœ¨ã—ã¦ã„ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:775 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:777 msgid "In this example, if one of the options ``file_path`` or ``file_hash`` is specified, Ansible will fail the module with an error if the other one is not specified." msgstr "ã“ã®ä¾‹ã§ã¯ã€``file_path`` ã¾ãŸã¯ ``file_hash`` ã®ã„ãšã‚Œã‹ã®ã‚ªãƒ—ションを指定ã—ã€ä»–ã®ã‚ªãƒ—ションãŒæŒ‡å®šã—ã¦ã„ãªã„ã¨ã€Ansible ã¯ã‚¨ãƒ©ãƒ¼ã‚’出ã—ã¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«å¤±æ•—ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:779 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:781 msgid "Must be a sequence (list or tuple) of sequences of strings. Every sequence of strings is a list of option names from which at least one must be specified. If none one of these options are specified, Ansible will fail module execution." msgstr "æ–‡å—列ã®ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ã®ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ (リストã¾ãŸã¯ã‚¿ãƒ—ル) ã§ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚æ–‡å—列ã®ã™ã¹ã¦ã®ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ã¯ã€å°‘ãªãã¨ã‚‚ 1 ã¤ã‚’指定ã™ã‚‹å¿…è¦ãŒã‚るオプションåã®ãƒªã‚¹ãƒˆã§ã™ã€‚ã“れらã®ã‚ªãƒ—ションãŒã„ãšã‚Œã‚‚指定ã•ã‚Œã¦ã„ãªã„å ´åˆã€Ansible ã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®å®Ÿè¡Œã«å¤±æ•—ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:789 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:791 msgid "In this example, at least one of ``path`` and ``content`` must be specified. If none are specified, execution will fail. Specifying both is explicitly allowed; to prevent this, combine ``required_one_of`` with ``mutually_exclusive``." msgstr "ã“ã®ä¾‹ã§ã¯ã€``path`` ãŠã‚ˆã³ ``content`` ã®ã„ãšã‚Œã‹ã‚’指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚指定ã—ãªã„ã¨ã€å®Ÿè¡ŒãŒå¤±æ•—ã—ã¾ã™ã€‚両方ã®å€¤ã‚’指定ã™ã‚‹ã¨ã€æ˜Žç¤ºçš„ã«è¨±å¯ã•ã‚Œã¾ã™ã€‚ã“れを回é¿ã™ã‚‹ã«ã¯ã€``required_one_of`` 㨠``mutually_exclusive`` を組ã¿åˆã‚ã›ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:793 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:795 msgid "Must be a sequence of sequences. Every inner sequence describes one conditional dependency. Every sequence must have three or four values. The first two values are the option's name and the option's value which describes the condition. The further elements of the sequence are only needed if the option of that name has precisely this value." msgstr "一連ã®ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ã®ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ã§ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã™ã¹ã¦ã®å†…部シーケンスã§ã¯ã€æ¡ä»¶ã®ä¾å˜é–¢ä¿‚ã‚’ 1 ã¤èª¬æ˜Žã—ã¾ã™ã€‚ã™ã¹ã¦ã®ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ã«ã¯ã€å€¤ãŒ 3 ã¤ã¾ãŸã¯ 4 ã¤å¿…è¦ã§ã™ã€‚最åˆã® 2 ã¤ã®å€¤ã¯ã€ã‚ªãƒ—ションåã¨ã€ãã®æ¡ä»¶ã‚’説明ã™ã‚‹ã‚ªãƒ—ションã®å€¤ã§ã™ã€‚シーケンスã®è¿½åŠ è¦ç´ ã¯ã€ãã®åå‰ã®ã‚ªãƒ—ションãŒæ£ç¢ºã«ã“ã®å€¤ã‚’æŒã£ã¦ã„ã‚‹å ´åˆã«ã®ã¿å¿…è¦ã§ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:795 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:797 msgid "If you want that all options in a list of option names are specified if the condition is met, use one of the following forms:" msgstr "æ¡ä»¶ãŒæº€ãŸã•ã‚ŒãŸå ´åˆã«ã‚ªãƒ—ションåã®ãƒªã‚¹ãƒˆå†…ã®ã‚ªãƒ—ションをã™ã¹ã¦æŒ‡å®šã™ã‚‹å ´åˆã¯ã€æ¬¡ã®ã„ãšã‚Œã‹ã®å½¢å¼ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:802 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:804 msgid "If you want that at least one option of a list of option names is specified if the condition is met, use the following form:" msgstr "æ¡ä»¶ãŒæº€ãŸã•ã‚ŒãŸå ´åˆã«ã‚ªãƒ—ションåã®ä¸€è¦§ã®ã‚ªãƒ—ションを 1 ã¤ä»¥ä¸ŠæŒ‡å®šã™ã‚‹å ´åˆã¯ã€ä»¥ä¸‹ã®å½¢å¼ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:817 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:819 msgid "In this example, if the user specifies ``state=present``, at least one of the options ``path`` and ``content`` must be supplied (or both). To make sure that precisely one can be specified, combine ``required_if`` with ``mutually_exclusive``." msgstr "ã“ã®ä¾‹ã§ã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒ ``state=present`` を指定ã—ã¦ã„ã‚‹å ´åˆã¯ã€``path`` 㨠``content`` ã®ã„ãšã‚Œã‹ (ã¾ãŸã¯ä¸¡æ–¹) ã®ã‚ªãƒ—ションを指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚å¿…ãšæŒ‡å®šã™ã‚‹ã‚ˆã†ã«ã™ã‚‹ã«ã¯ã€``required_if`` 㨠``mutually_exclusive`` を組ã¿åˆã‚ã›ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:819 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:821 msgid "On the other hand, if ``force`` (a boolean parameter) is set to ``true``, ``yes`` etc., both ``force_reason`` and ``force_code`` must be specified." msgstr "一方ã€``force`` (ブール値パラメーター) ㌠``true``ã€``yes`` ãªã©ã«è¨å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€``force_reason`` 㨠``force_code`` ã®ä¸¡æ–¹ã‚’指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:823 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:825 msgid "Must be a dictionary mapping option names to sequences of option names. If the option name in a dictionary key is specified, the option names it maps to must all also be specified. Note that instead of a sequence of option names, you can also specify one single option name." msgstr "オプションåã®ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ã¸ã®ãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼ãƒžãƒƒãƒ”ングオプションåã§ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ディクショナリーã‚ーã§ã‚ªãƒ—ションåを指定ã™ã‚‹ã¨ã€ãã®ã‚ªãƒ—ションåã‚’ã™ã¹ã¦æŒ‡å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚オプションåã®ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ã®ä»£ã‚ã‚Šã«ã€ã‚ªãƒ—ションã®åå‰ã‚’ 1 ã¤æŒ‡å®šã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:834 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:836 msgid "In the example, if ``force`` is specified, ``force_reason`` must also be specified. Also, if ``path`` is specified, then three three options ``mode``, ``owner`` and ``group`` also must be specified." msgstr "ã“ã®ä¾‹ã§ã¯ã€``force`` ãŒæŒ‡å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€``force_reason`` も指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã¾ãŸã€``path`` ãŒæŒ‡å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€3 ã¤ã®ã‚ªãƒ—ション ``mode``ã€``owner``ã€ãŠã‚ˆã³ ``group`` も指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:837 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:839 msgid "Declaring check mode support" msgstr "ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã®ã‚µãƒãƒ¼ãƒˆã®å®£è¨€" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:839 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:841 msgid "To declare that a module supports check mode, supply ``supports_check_mode=True`` to the ``AnsibleModule()`` call:" msgstr "モジュールãŒç¢ºèªãƒ¢ãƒ¼ãƒ‰ã‚’サãƒãƒ¼ãƒˆã™ã‚‹ã“ã¨ã‚’宣言ã™ã‚‹ã«ã¯ã€``AnsibleModule()`` 呼ã³å‡ºã—ã« ``supports_check_mode=True`` を指定ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:845 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:847 msgid "The module can determine whether it is called in check mode by checking the boolean value ``module.check_mode``. If it evaluates to ``True``, the module must take care not to do any modification." msgstr "モジュールã¯ã€ãƒ–ール値 ``module.check_mode`` を確èªã™ã‚‹ã“ã¨ã§ã€ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã§å‘¼ã³å‡ºã•ã‚Œã‚‹ã‹ã©ã†ã‹ã‚’判æ–ã§ãã¾ã™ã€‚``True`` ã«è©•ä¾¡ã™ã‚‹å ´åˆã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯å¤‰æ›´ã‚’è¡Œã‚ãªã„よã†ã«ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:847 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:849 msgid "If ``supports_check_mode=False`` is specified, which is the default value, the module will exit in check mode with ``skipped=True`` and message ``remote module (<insert module name here>) does not support check mode``." msgstr "``supports_check_mode=False`` ãŒæŒ‡å®šã•ã‚Œã¦ã„ã‚‹å ´åˆ (デフォルト値)ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã§ ``skipped=True`` ãŠã‚ˆã³ ``remote module (<insert module name here>) does not support check mode`` メッセージã§çµ‚了ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:850 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:852 msgid "Adding file options" msgstr "ファイルオプションã®è¿½åŠ " -#: ../../rst/dev_guide/developing_program_flow_modules.rst:852 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:854 msgid "To declare that a module should add support for all common file options, supply ``add_file_common_args=True`` to the ``AnsibleModule()`` call:" msgstr "モジュールãŒã™ã¹ã¦ã®å…±é€šãƒ•ã‚¡ã‚¤ãƒ«ã‚ªãƒ—ションã®ã‚µãƒãƒ¼ãƒˆã‚’è¿½åŠ ã™ã‚‹ã“ã¨ã‚’宣言ã™ã‚‹ã«ã¯ã€``add_file_common_args=True`` ã‚’ ``AnsibleModule()`` 呼ã³å‡ºã—ã«æŒ‡å®šã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:858 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:860 msgid "You can find `a list of all file options here <https://github.com/ansible/ansible/blob/devel/lib/ansible/plugins/doc_fragments/files.py>`_. It is recommended that you make your ``DOCUMENTATION`` extend the doc fragment ``ansible.builtin.files`` (see :ref:`module_docs_fragments`) in this case, to make sure that all these fields are correctly documented." msgstr "`ã“ã“ã§ã€ãƒ•ã‚¡ã‚¤ãƒ«ã‚ªãƒ—ションã®ä¸€è¦§ <https://github.com/ansible/ansible/blob/devel/lib/ansible/plugins/doc_fragments/files.py>`_ を確èªã§ãã¾ã™ã€‚今回ã¯ã€``DOCUMENTATION`` ãŒãƒ‰ã‚ュメントフラグメント ``ansible.builtin.files`` (:ref:`module_docs_fragments` ã‚’å‚ç…§) ã‚’æ‹¡å¼µã—ã€ã“れらã®ãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ãŒã™ã¹ã¦æ£ã—ã文書化ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_program_flow_modules.rst:860 +#: ../../rst/dev_guide/developing_program_flow_modules.rst:862 msgid "The helper functions ``module.load_file_common_arguments()`` and ``module.set_fs_attributes_if_different()`` can be used to handle these arguments for you:" msgstr "ヘルパー関数 ``module.load_file_common_arguments()`` ãŠã‚ˆã³ ``module.set_fs_attributes_if_different()`` を使用ã—ã¦ã€ä»¥ä¸‹ã®å¼•æ•°ã‚’扱ã†ã“ã¨ãŒã§ãã¾ã™ã€‚" @@ -7228,70 +7239,70 @@ msgid "Configuring your remotes" msgstr "リモートã®è¨å®š" #: ../../rst/dev_guide/developing_rebasing.rst:17 -msgid "Before you can rebase your PR, you need to make sure you have the proper remotes configured. These instructions apply to any repository on GitHub, including collections repositories. On other platforms (bitbucket, gitlab), the same principles and commands apply but the syntax may be different. We use the ansible/ansible repository here as an example. In other repositories, the branch names may be different. Assuming you cloned your fork in the usual fashion, the ``origin`` remote will point to your fork::" -msgstr "PR をリベースã™ã‚‹å‰ã«ã€é©åˆ‡ãªãƒªãƒ¢ãƒ¼ãƒˆãŒè¨å®šã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®æ‰‹é †ã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãƒªãƒã‚¸ãƒˆãƒªãƒ¼ã‚’å«ã‚€ GitHub ã®ã™ã¹ã¦ã®ãƒªãƒã‚¸ãƒˆãƒªãƒ¼ã«é©ç”¨ã•ã‚Œã¾ã™ã€‚ä»–ã®ãƒ—ラットフォーム(bitbucket ã‚„ gitlab) ã§ã‚‚åŒæ§˜ã®åŽŸå‰‡ã¨ã‚³ãƒžãƒ³ãƒ‰ãŒé©ç”¨ã•ã‚Œã¾ã™ãŒã€æ§‹æ–‡ãŒç•°ãªã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚ã“ã“ã§ã¯ã€ansible/ansible ã®ãƒªãƒã‚¸ãƒˆãƒªãƒ¼ã‚’例ã«æŒ™ã’ã¦ã„ã¾ã™ã€‚ä»–ã®ãƒªãƒã‚¸ãƒˆãƒªãƒ¼ã§ã¯ã€ãƒ–ランãƒåãŒç•°ãªã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚通常ã®æ–¹æ³•ã§ãƒ•ã‚©ãƒ¼ã‚¯ã‚’クãƒãƒ¼ãƒ³ã—ãŸã¨ä»®å®šã™ã‚‹ã¨ã€``origin`` ã®ãƒªãƒ¢ãƒ¼ãƒˆã¯æ“作ã—ãŸãƒ¦ãƒ¼ã‚¶ãƒ¼ã®ãƒ•ã‚©ãƒ¼ã‚¯ã‚’指ã™ã“ã¨ã«ãªã‚Šã¾ã™::" +msgid "Before you can rebase your PR, you need to make sure you have the proper remotes configured. These instructions apply to any repository on GitHub, including collections repositories. On other platforms (bitbucket, gitlab), the same principles and commands apply but the syntax may be different. We use the ansible/ansible repository here as an example. In other repositories, the branch names may be different. Assuming you cloned your fork in the usual fashion, the ``origin`` remote will point to your fork:" +msgstr "PR をリベースã™ã‚‹å‰ã«ã€é©åˆ‡ãªãƒªãƒ¢ãƒ¼ãƒˆãŒè¨å®šã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®æ‰‹é †ã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãƒªãƒã‚¸ãƒˆãƒªãƒ¼ã‚’å«ã‚€ GitHub ã®ã™ã¹ã¦ã®ãƒªãƒã‚¸ãƒˆãƒªãƒ¼ã«é©ç”¨ã•ã‚Œã¾ã™ã€‚ä»–ã®ãƒ—ラットフォーム(bitbucket ã‚„ gitlab) ã§ã‚‚åŒæ§˜ã®åŽŸå‰‡ã¨ã‚³ãƒžãƒ³ãƒ‰ãŒé©ç”¨ã•ã‚Œã¾ã™ãŒã€æ§‹æ–‡ãŒç•°ãªã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚ã“ã“ã§ã¯ã€ansible/ansible ã®ãƒªãƒã‚¸ãƒˆãƒªãƒ¼ã‚’例ã«æŒ™ã’ã¦ã„ã¾ã™ã€‚ä»–ã®ãƒªãƒã‚¸ãƒˆãƒªãƒ¼ã§ã¯ã€ãƒ–ランãƒåãŒç•°ãªã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚通常ã®æ–¹æ³•ã§ãƒ•ã‚©ãƒ¼ã‚¯ã‚’クãƒãƒ¼ãƒ³ã—ãŸã¨ä»®å®šã™ã‚‹ã¨ã€``origin`` ã®ãƒªãƒ¢ãƒ¼ãƒˆã¯æ“作ã—ãŸãƒ¦ãƒ¼ã‚¶ãƒ¼ã®ãƒ•ã‚©ãƒ¼ã‚¯ã‚’指ã™ã“ã¨ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_rebasing.rst:23 -msgid "However, you also need to add a remote which points to the upstream repository::" +#: ../../rst/dev_guide/developing_rebasing.rst:25 +msgid "However, you also need to add a remote which points to the upstream repository:" msgstr "ãŸã ã—ã€ã‚¢ãƒƒãƒ—ストリームã®ãƒªãƒã‚¸ãƒˆãƒªãƒ¼ã‚’å‚ç…§ã™ã‚‹ãƒªãƒ¢ãƒ¼ãƒˆã‚’è¿½åŠ ã™ã‚‹å¿…è¦ã‚‚ã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_rebasing.rst:27 -msgid "Which should leave you with the following remotes::" +#: ../../rst/dev_guide/developing_rebasing.rst:31 +msgid "Which should leave you with the following remotes:" msgstr "次ã®ãƒªãƒ¢ãƒ¼ãƒˆã‚’残ã™å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_rebasing.rst:35 -msgid "Checking the status of your branch should show your fork is up-to-date with the ``origin`` remote::" +#: ../../rst/dev_guide/developing_rebasing.rst:41 +msgid "Checking the status of your branch should show your fork is up-to-date with the ``origin`` remote:" msgstr "ブランãƒã®ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã‚’確èªã™ã‚‹ã¨ã€``origin`` ã®ãƒªãƒ¢ãƒ¼ãƒˆã®ãƒ•ã‚©ãƒ¼ã‚¯ãŒæœ€æ–°ã®çŠ¶æ…‹ã§ã‚ã‚‹ã“ã¨ã‚’ç†è§£ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_rebasing.rst:43 +#: ../../rst/dev_guide/developing_rebasing.rst:51 msgid "Rebasing your branch" msgstr "ブランãƒã®ãƒªãƒ™ãƒ¼ã‚¹" -#: ../../rst/dev_guide/developing_rebasing.rst:45 -msgid "Once you have an ``upstream`` remote configured, you can rebase the branch for your PR::" +#: ../../rst/dev_guide/developing_rebasing.rst:53 +msgid "Once you have an ``upstream`` remote configured, you can rebase the branch for your PR:" msgstr "``upstream`` ã®ãƒªãƒ¢ãƒ¼ãƒˆã‚’è¨å®šã—ãŸã‚‰ã€PR ã®ãƒ–ランãƒã‚’リベースã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_rebasing.rst:49 +#: ../../rst/dev_guide/developing_rebasing.rst:59 msgid "This will replay the changes in your branch on top of the changes made in the upstream ``devel`` branch. If there are merge conflicts, you will be prompted to resolve those before you can continue." msgstr "ã“ã‚Œã«ã‚ˆã‚Šã€ã‚¢ãƒƒãƒ—ストリーム㮠``devel`` ブランãƒã§å¤‰æ›´ã—ãŸãƒ–ランãƒã«å¤‰æ›´ãŒå†ç”Ÿã•ã‚Œã¾ã™ã€‚マージã®ç«¶åˆãŒç™ºç”Ÿã—ãŸå ´åˆã¯ã€ç¶šè¡Œã™ã‚‹å‰ã«è§£æ±ºã™ã‚‹ã‚ˆã†ã«æ±‚ã‚られã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_rebasing.rst:52 -msgid "After you rebase, the status of your branch changes::" +#: ../../rst/dev_guide/developing_rebasing.rst:62 +msgid "After you rebase, the status of your branch changes:" msgstr "リベース後ã«ã€ãƒ–ランãƒã®ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ãŒå¤‰æ›´ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_rebasing.rst:61 +#: ../../rst/dev_guide/developing_rebasing.rst:73 msgid "Don't worry, this is normal after a rebase. You should ignore the ``git status`` instructions to use ``git pull``. We'll cover what to do next in the following section." msgstr "リベースã®å¾Œã€ã“ã‚Œã¯é€šå¸¸é€šã‚Šã¨ãªã‚Šã¾ã™ã€‚``git pull`` を使用ã™ã‚‹ ``git status`` 命令ã¯ç„¡è¦–ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚次ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€æ¬¡ã«ä½•ã‚’ã™ã‚‹ã‹ã«ã¤ã„ã¦èª¬æ˜Žã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_rebasing.rst:64 +#: ../../rst/dev_guide/developing_rebasing.rst:76 msgid "Updating your pull request" msgstr "プルè¦æ±‚ã®æ›´æ–°" -#: ../../rst/dev_guide/developing_rebasing.rst:66 +#: ../../rst/dev_guide/developing_rebasing.rst:78 msgid "Now that you've rebased your branch, you need to push your changes to GitHub to update your PR." msgstr "ブランãƒã‚’リベースã—ãŸã‚‰ã€å¤‰æ›´ã‚’ GitHub ã«ãƒ—ッシュã—ã¦ã€PR ã‚’æ›´æ–°ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_rebasing.rst:68 -msgid "Since rebasing re-writes git history, you will need to use a force push::" +#: ../../rst/dev_guide/developing_rebasing.rst:80 +msgid "Since rebasing re-writes git history, you will need to use a force push:" msgstr "リベースã¯ã€git å±¥æ´ã‚’å†æ›¸ãè¾¼ã¿ã™ã‚‹ãŸã‚ã€å¼·åˆ¶çš„ã«ãƒ—ッシュã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_rebasing.rst:72 +#: ../../rst/dev_guide/developing_rebasing.rst:86 msgid "Your PR on GitHub has now been updated. This will automatically trigger testing of your changes. You should check in on the status of your PR after tests have completed to see if further changes are required." msgstr "GitHub ã® PR ãŒæ›´æ–°ã•ã‚Œã¾ã—ãŸã€‚ã“ã‚Œã«ã‚ˆã‚Šã€å¤‰æ›´ã®ãƒ†ã‚¹ãƒˆãŒè‡ªå‹•çš„ã«ç™ºç”Ÿã—ã¾ã™ã€‚テスト完了後㫠PR ã®ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã‚’確èªã—ã€ã•ã‚‰ãªã‚‹å¤‰æ›´ãŒå¿…è¦ã§ã‚ã‚‹ã‹ã©ã†ã‹ã‚’確èªã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/developing_rebasing.rst:76 +#: ../../rst/dev_guide/developing_rebasing.rst:90 msgid "Getting help rebasing" msgstr "リベースã®ãƒ˜ãƒ«ãƒ—" -#: ../../rst/dev_guide/developing_rebasing.rst:78 +#: ../../rst/dev_guide/developing_rebasing.rst:92 msgid "For help with rebasing your PR, or other development related questions, join us on the #ansible-devel chat channel (using Matrix at ansible.im or using IRC at `irc.libera.chat <https://libera.chat/>`_)." msgstr "PR ã¾ãŸã¯ãã®ä»–ã®é–‹ç™ºé–¢é€£ã®è³ªå•ã‚’å†è¨å®šã™ã‚‹éš›ã«ã¯ã€ãƒãƒ£ãƒƒãƒˆãƒãƒ£ãƒ³ãƒãƒ« #ansible-devel ã«å‚åŠ ã—ã¾ã™ï¼ˆansible.imã§Matrixを使用ã€ã¾ãŸã¯`irc.libera.chat <https://libera.chat/>`ã§IRCを使用）。" -#: ../../rst/dev_guide/developing_rebasing.rst:82 +#: ../../rst/dev_guide/developing_rebasing.rst:96 msgid ":ref:`community_development_process`" msgstr ":ref:`community_development_process`" -#: ../../rst/dev_guide/developing_rebasing.rst:83 +#: ../../rst/dev_guide/developing_rebasing.rst:97 msgid "Information on roadmaps, opening PRs, Ansibullbot, and more" msgstr "ãƒãƒ¼ãƒ‰ãƒžãƒƒãƒ—ã€ã‚ªãƒ¼ãƒ—ン PRSã€Ansibullbot ãªã©ã«é–¢ã™ã‚‹æƒ…å ±" @@ -7961,74 +7972,74 @@ msgid "If there's another source of truth in your infrastructure, Ansible can al msgstr "インフラストラクãƒãƒ£ãƒ¼ã«ä¿¡é ¼ã§ãる別ã®ã‚½ãƒ¼ã‚¹ãŒã‚ã‚‹å ´åˆã¯ã€Ansible ã‚‚ã“ã‚Œã«æŽ¥ç¶šã§ãã¾ã™ã€‚Ansible ã¯ã€EC2ã€Rackspaceã€OpenStack ãªã©ã®ã‚½ãƒ¼ã‚¹ã‹ã‚‰ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã€ã‚°ãƒ«ãƒ¼ãƒ—ã€ãŠã‚ˆã³å¤‰æ•°æƒ…å ±ã‚’å–り出ã™ã“ã¨ãŒã§ãã¾ã™ã€‚" #: ../../rst/dev_guide/overview_architecture.rst:43 -msgid "Here's what a plain text inventory file looks like::" +msgid "Here's what a plain text inventory file looks like:" msgstr "プレーンテã‚ストã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ•ã‚¡ã‚¤ãƒ«ã¯æ¬¡ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/overview_architecture.rst:54 +#: ../../rst/dev_guide/overview_architecture.rst:56 msgid "Once inventory hosts are listed, variables can be assigned to them in simple text files (in a subdirectory called 'group_vars/' or 'host_vars/' or directly in the inventory file." msgstr "インベントリーホストã®ä¸€è¦§ãŒä½œæˆã•ã‚Œã‚‹ã¨ã€å˜ç´”ãªãƒ†ã‚ストファイル形å¼ã§ (「group_vars/ã€ã¾ãŸã¯ã€Œhost_vars/ã€ã¨ã„ã†åå‰ã®ã‚µãƒ–ディレクトリー内ã€ã¾ãŸã¯ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ•ã‚¡ã‚¤ãƒ«ã«ç›´æŽ¥) 割り当ã¦ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/overview_architecture.rst:56 +#: ../../rst/dev_guide/overview_architecture.rst:58 msgid "Or, as already mentioned, use a dynamic inventory to pull your inventory from data sources like EC2, Rackspace, or OpenStack." msgstr "ã¾ãŸã¯ã€ä¸Šè¿°ã®ã‚ˆã†ã«ã€å‹•çš„インベントリーを使用ã—ã¦ã€EC2ã€Rackspaceã€OpenStack ã®ã‚ˆã†ãªãƒ‡ãƒ¼ã‚¿ã‚½ãƒ¼ã‚¹ã‹ã‚‰ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚’プルã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/overview_architecture.rst:59 +#: ../../rst/dev_guide/overview_architecture.rst:61 msgid "Playbooks" msgstr "Playbook" -#: ../../rst/dev_guide/overview_architecture.rst:61 +#: ../../rst/dev_guide/overview_architecture.rst:63 msgid "Playbooks can finely orchestrate multiple slices of your infrastructure topology, with very detailed control over how many machines to tackle at a time. This is where Ansible starts to get most interesting." msgstr "Playbook ã¯ã€ã‚¤ãƒ³ãƒ•ãƒ©ã‚¹ãƒˆãƒ©ã‚¯ãƒãƒ£ãƒ¼ãƒˆãƒãƒã‚¸ãƒ¼ã®è¤‡æ•°ã®ã‚¹ãƒ©ã‚¤ã‚¹ã‚’ç´°ã‹ã調整 (オーケストレーション) ã™ã‚‹ã“ã¨ãŒã§ãã€åŒæ™‚ã«å–り組むマシンã®æ•°ã‚’éžå¸¸ã«ç´°ã‹ã制御ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã“ã‹ã‚‰ãŒã€Ansible ã§æœ€ã‚‚é…力的ãªç‚¹ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/overview_architecture.rst:63 +#: ../../rst/dev_guide/overview_architecture.rst:65 msgid "Ansible's approach to orchestration is one of finely-tuned simplicity, as we believe your automation code should make perfect sense to you years down the road and there should be very little to remember about special syntax or features." msgstr "Ansible ã®ã‚ªãƒ¼ã‚±ã‚¹ãƒˆãƒ¬ãƒ¼ã‚·ãƒ§ãƒ³ã¸ã®ã‚¢ãƒ—ãƒãƒ¼ãƒã¯ã€ç´°ã‹ã調整ã•ã‚ŒãŸç°¡ç´ 化㮠1 ã¤ã§ã™ã€‚通常ã€è‡ªå‹•åŒ–コードã¯ä»Šå¾Œä½•å¹´ã«ã‚‚渡ã£ã¦å®Œå…¨ã«ç†è§£ã§ãã‚‹ã‚‚ã®ã§ã‚ã‚Šã€ç‰¹åˆ¥ãªæ§‹æ–‡ã‚„機能ã«ã¤ã„ã¦è¦šãˆã¦ãŠãã¹ãã“ã¨ã¯ã»ã¨ã‚“ã©ãªã„ãŸã‚ã§ã™ã€‚" -#: ../../rst/dev_guide/overview_architecture.rst:65 -msgid "Here's what a simple playbook looks like::" +#: ../../rst/dev_guide/overview_architecture.rst:67 +msgid "Here's what a simple playbook looks like:" msgstr "以下ã¯å˜ç´”㪠Playbook ã®ä¾‹ã§ã™ã€‚" -#: ../../rst/dev_guide/overview_architecture.rst:82 +#: ../../rst/dev_guide/overview_architecture.rst:86 msgid "The Ansible search path" msgstr "Ansible 検索パス" -#: ../../rst/dev_guide/overview_architecture.rst:84 +#: ../../rst/dev_guide/overview_architecture.rst:88 msgid "Modules, module utilities, plugins, playbooks, and roles can live in multiple locations. If you write your own code to extend Ansible's core features, you may have multiple files with similar or the same names in different locations on your Ansible control node. The search path determines which of these files Ansible will discover and use on any given playbook run." msgstr "モジュールã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ã€ãƒ—ラグインã€Playbookã€ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã¯è¤‡æ•°ã®å ´æ‰€ã«ç½®ãã“ã¨ãŒã§ãã¾ã™ã€‚Ansible ã®ã‚³ã‚¢æ©Ÿèƒ½ã‚’æ‹¡å¼µã™ã‚‹ãŸã‚ã«ç‹¬è‡ªã®ã‚³ãƒ¼ãƒ‰ã‚’作æˆã™ã‚‹å ´åˆã¯ã€Ansible コントãƒãƒ¼ãƒ«ãƒŽãƒ¼ãƒ‰ã®ç•°ãªã‚‹å ´æ‰€ã«åŒã˜åå‰ã¾ãŸã¯é¡žä¼¼ã™ã‚‹åå‰ã‚’æŒã¤ãƒ•ã‚¡ã‚¤ãƒ«ãŒè¤‡æ•°å˜åœ¨ã™ã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚検索パスã«ã‚ˆã‚Šã€Ansible ãŒç‰¹å®šã® Playbook ã®å®Ÿè¡Œã§æ¤œå‡ºã—ã¦ä½¿ç”¨ã™ã‚‹ã“れらã®ãƒ•ã‚¡ã‚¤ãƒ«ãŒæ±ºã¾ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/overview_architecture.rst:87 +#: ../../rst/dev_guide/overview_architecture.rst:91 msgid "Ansible's search path grows incrementally over a run. As Ansible finds each playbook and role included in a given run, it appends any directories related to that playbook or role to the search path. Those directories remain in scope for the duration of the run, even after the playbook or role has finished executing. Ansible loads modules, module utilities, and plugins in this order:" msgstr "Ansible ã®æ¤œç´¢ãƒ‘スã¯ã€å®Ÿè¡Œä¸ã«å¾ã€…ã«å¤§ãããªã‚Šã¾ã™ã€‚Ansible ã¯ã€ç‰¹å®šã®å®Ÿè¡Œã«å«ã¾ã‚Œã‚‹å„ Playbook ã¨ãƒãƒ¼ãƒ«ã‚’見ã¤ã‘ã‚‹ã¨ã€ãã® Playbook ã¾ãŸã¯ãƒãƒ¼ãƒ«ã«é–¢é€£ã™ã‚‹ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã‚’検索パスã«è¿½åŠ ã—ã¾ã™ã€‚ã“れらã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã¯ã€Playbook ã¾ãŸã¯ãƒãƒ¼ãƒ«ã®å®Ÿè¡ŒãŒçµ‚了ã—ãŸå¾Œã§ã‚‚ã€å®Ÿè¡Œä¸ã¯ã‚¹ã‚³ãƒ¼ãƒ—内ã«ç•™ã¾ã‚Šã¾ã™ã€‚Ansible ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ã€ãŠã‚ˆã³ãƒ—ラグインを次ã®é †åºã§èªã¿è¾¼ã¿ã¾ã™ã€‚" -#: ../../rst/dev_guide/overview_architecture.rst:93 +#: ../../rst/dev_guide/overview_architecture.rst:97 msgid "Directories adjacent to a playbook specified on the command line. If you run Ansible with ``ansible-playbook /path/to/play.yml``, Ansible appends these directories if they exist:" msgstr "コマンドラインã§æŒ‡å®šã—㟠Playbook ã«éš£æŽ¥ã™ã‚‹ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã€‚``ansible-playbook /path/to/play.yml`` 㧠Ansible を実行ã—ã€ãã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ãŒå˜åœ¨ã™ã‚‹å ´åˆã¯ã€Ansible ãŒãã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã‚’è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/overview_architecture.rst:101 +#: ../../rst/dev_guide/overview_architecture.rst:105 msgid "Directories adjacent to a playbook that is statically imported by a playbook specified on the command line. If ``play.yml`` includes ``- import_playbook: /path/to/subdir/play1.yml``, Ansible appends these directories if they exist:" msgstr "コマンドラインã§æŒ‡å®šã•ã‚ŒãŸ Playbook ã«ã‚ˆã£ã¦é™çš„ã«ã‚¤ãƒ³ãƒãƒ¼ãƒˆã•ã‚Œã‚‹ Playbook ã«éš£æŽ¥ã™ã‚‹ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã€‚``play.yml`` ã« ``- import_playbook: /path/to/subdir/play1.yml`` ãŒå«ã¾ã‚Œã¦ã„ã¦ã€ã“れらã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ãŒå˜åœ¨ã™ã‚‹å ´åˆã¯ã€Ansible ãŒãã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã‚’è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/overview_architecture.rst:111 +#: ../../rst/dev_guide/overview_architecture.rst:115 msgid "Subdirectories of a role directory referenced by a playbook. If ``play.yml`` runs ``myrole``, Ansible appends these directories if they exist:" msgstr "Playbook ã«ã‚ˆã£ã¦å‚ç…§ã•ã‚Œã‚‹ãƒãƒ¼ãƒ«ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã®ã‚µãƒ–ディレクトリー。``play.yml`` ㌠``myrole`` を実行ã—ã€æ¬¡ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ãŒå˜åœ¨ã™ã‚‹å ´åˆã¯ã€Ansible ãŒãã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã‚’è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/overview_architecture.rst:120 +#: ../../rst/dev_guide/overview_architecture.rst:124 msgid "Directories specified as default paths in ``ansible.cfg`` or by the related environment variables, including the paths for the various plugin types. See :ref:`ansible_configuration_settings` for more information. Sample ``ansible.cfg`` fields:" msgstr "``ansible.cfg`` ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãƒ‘スã¨ã—ã¦ã€ã¾ãŸã¯ã•ã¾ã–ã¾ãªãƒ—ラグインタイプã®ãƒ‘スãªã©ã€é–¢é€£ã™ã‚‹ç’°å¢ƒå¤‰æ•°ã«ã‚ˆã‚ŠæŒ‡å®šã•ã‚ŒãŸãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã€‚詳細ã¯ã€ã€Œ:ref:`ansible_configuration_settings`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。サンプル㮠``ansible.cfg`` フィールドã¯ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/overview_architecture.rst:131 +#: ../../rst/dev_guide/overview_architecture.rst:135 msgid "Sample environment variables:" msgstr "以下ã¯ã€ç’°å¢ƒå¤‰æ•°ã®ä¾‹ã¨ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/overview_architecture.rst:140 +#: ../../rst/dev_guide/overview_architecture.rst:144 msgid "The standard directories that ship as part of the Ansible distribution." msgstr "Ansible ディストリビューションã«åŒæ¢±ã•ã‚Œã‚‹æ¨™æº–ディレクトリー。" -#: ../../rst/dev_guide/overview_architecture.rst:144 +#: ../../rst/dev_guide/overview_architecture.rst:148 msgid "Modules, module utilities, and plugins in user-specified directories will override the standard versions. This includes some files with generic names. For example, if you have a file named ``basic.py`` in a user-specified directory, it will override the standard ``ansible.module_utils.basic``." msgstr "ユーザーãŒæŒ‡å®šã—ãŸãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ã‚るモジュールã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ã€ãŠã‚ˆã³ãƒ—ラグインã¯æ¨™æº–ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’上書ãã—ã¾ã™ã€‚ã“ã‚Œã«ã¯ã€ä¸€èˆ¬çš„ãªåå‰ã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚‚å«ã¾ã‚Œã¾ã™ã€‚ãŸã¨ãˆã°ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼æŒ‡å®šã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã« ``basic.py`` ã¨ã„ã†åå‰ã®ãƒ•ã‚¡ã‚¤ãƒ«ãŒã‚ã‚‹å ´åˆã¯ã€æ¨™æº–ã® ``ansible.module_utils.basic`` を上書ãã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/overview_architecture.rst:149 +#: ../../rst/dev_guide/overview_architecture.rst:153 msgid "If you have more than one module, module utility, or plugin with the same name in different user-specified directories, the order of commands at the command line and the order of includes and roles in each play will affect which one is found and used on that particular play." msgstr "åŒã˜åå‰ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ã€ã¾ãŸã¯ãƒ—ラグインãŒè¤‡æ•°ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼æŒ‡å®šãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ã‚ã‚‹å ´åˆã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã§ã®ã‚³ãƒžãƒ³ãƒ‰ã®é †åºã‚„ã€å„プレイã§ã®ã‚¤ãƒ³ã‚¯ãƒ«ãƒ¼ãƒ‰ã¨ãƒãƒ¼ãƒ«ã®é †åºã¯ã€ãã®ç‰¹å®šã®ãƒ—レイã§ã©ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒè¦‹ã¤ã‹ã‚Šã€ä½¿ç”¨ã•ã‚Œã‚‹ã‹ã«ã‚ˆã£ã¦ç•°ãªã‚Šã¾ã™ã€‚" @@ -11150,7 +11161,7 @@ msgid "units" msgstr "ユニット" #: ../../rst/dev_guide/testing.rst:40 -#: ../../rst/dev_guide/testing_units_modules.rst:541 +#: ../../rst/dev_guide/testing_units_modules.rst:567 msgid ":ref:`testing_units`" msgstr ":ref:`testing_units`" @@ -11179,206 +11190,206 @@ msgid "When Pull Requests (PRs) are created they are tested using Azure Pipeline msgstr "プルè¦æ±‚ (PR: Pull Requests) ãŒä½œæˆã•ã‚Œã‚‹ã¨ã€ç¶™ç¶šçš„çµ±åˆ (CI) ツールã§ã‚ã‚‹ Azure Pipeline を使用ã—ã¦ãƒ†ã‚¹ãƒˆãŒè¡Œã‚ã‚Œã¾ã™ã€‚çµæžœã¯ã™ã¹ã¦ã® PR ã®æœ€å¾Œã«è¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" #: ../../rst/dev_guide/testing.rst:63 -msgid "When Azure Pipelines detects an error and it can be linked back to a file that has been modified in the PR then the relevant lines will be added as a GitHub comment. For example::" +msgid "When Azure Pipelines detects an error and it can be linked back to a file that has been modified in the PR then the relevant lines will be added as a GitHub comment. For example:" msgstr "Azure Pipeline ãŒã‚¨ãƒ©ãƒ¼ã‚’検出ã—ã€ãれ㌠PR ã§å¤‰æ›´ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã«ãƒªãƒ³ã‚¯ã•ã‚Œã‚‹ã¨ã€é–¢é€£ã™ã‚‹è¡ŒãŒ GitHub ã®ã‚³ãƒ¡ãƒ³ãƒˆã¨ã—ã¦è¿½åŠ ã•ã‚Œã¾ã™ã€‚ãŸã¨ãˆã°ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:72 +#: ../../rst/dev_guide/testing.rst:74 msgid "From the above example we can see that ``--test pep8`` and ``--test validate-modules`` have identified an issue. The commands given allow you to run the same tests locally to ensure you've fixed all issues without having to push your changes to GitHub and wait for Azure Pipelines, for example:" msgstr "上記ã®ä¾‹ã‹ã‚‰ã€``--test pep8`` ãŠã‚ˆã³ ``--test validate-modules`` ãŒå•é¡Œã‚’特定ã—ãŸã“ã¨ãŒåˆ†ã‹ã‚Šã¾ã™ã€‚指定ã•ã‚ŒãŸã‚³ãƒžãƒ³ãƒ‰ã‚’使用ã™ã‚‹ã¨ã€åŒã˜ãƒ†ã‚¹ãƒˆã‚’ãƒãƒ¼ã‚«ãƒ«ã§å®Ÿè¡Œã—ã¦ã€å¤‰æ›´ã‚’ GitHub ã«ãƒ—ッシュã—㦠Azure Pipeline ã‚’å¾…ã¤ã“ã¨ãªãã€ã™ã¹ã¦ã®å•é¡Œã‚’ä¿®æ£ã—ãŸã“ã¨ã‚’確èªã§ãã¾ã™ã€‚次ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:74 -msgid "If you haven't already got Ansible available, use the local checkout by running::" +#: ../../rst/dev_guide/testing.rst:76 +msgid "If you haven't already got Ansible available, use the local checkout by running:" msgstr "Ansible ãŒã¾ã 利用ã§ãるよã†ã«ãªã£ã¦ã„ãªã„å ´åˆã¯ã€ãƒãƒ¼ã‚«ãƒ«ã§ãƒã‚§ãƒƒã‚¯ã‚¢ã‚¦ãƒˆã‚’実行ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/testing.rst:78 -msgid "Then run the tests detailed in the GitHub comment::" +#: ../../rst/dev_guide/testing.rst:82 +msgid "Then run the tests detailed in the GitHub comment:" msgstr "次ã«ã€GitHub コメントã§èª¬æ˜Žã™ã‚‹ãƒ†ã‚¹ãƒˆã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:83 +#: ../../rst/dev_guide/testing.rst:89 msgid "If there isn't a GitHub comment stating what's failed you can inspect the results by clicking on the \"Details\" button under the \"checks have failed\" message at the end of the PR." msgstr "GitHub ã®ã‚³ãƒ¡ãƒ³ãƒˆã«ä½•ãŒå¤±æ•—ã—ãŸã‹ãŒæ›¸ã‹ã‚Œã¦ã„ãªã„å ´åˆã¯ã€PR ã®æœ«å°¾ã«ã‚る「checks have failedã€ã¨ã„ã†ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã®ä¸‹ã«ã‚る「Detailsã€ãƒœã‚¿ãƒ³ã‚’クリックã—ã¦çµæžœã‚’確èªã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:86 +#: ../../rst/dev_guide/testing.rst:92 msgid "Rerunning a failing CI job" msgstr "失敗ã—㟠CI ジョブã®å†å®Ÿè¡Œ" -#: ../../rst/dev_guide/testing.rst:88 +#: ../../rst/dev_guide/testing.rst:94 msgid "Occasionally you may find your PR fails due to a reason unrelated to your change. This could happen for several reasons, including:" msgstr "時折ã€å¤‰æ›´ã¨ã¯é–¢ä¿‚ã®ãªã„ç†ç”±ã§ PR ãŒå¤±æ•—ã™ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã«ã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ãªç†ç”±ãŒè€ƒãˆã‚‰ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:90 +#: ../../rst/dev_guide/testing.rst:96 msgid "a temporary issue accessing an external resource, such as a yum or git repo" msgstr "yum ã‚„ git リãƒã‚¸ãƒˆãƒªãƒ¼ãªã©ã®å¤–部リソースã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹éš›ã«ä¸€æ™‚çš„ã«å•é¡ŒãŒç™ºç”Ÿã—ãŸå ´åˆã€‚" -#: ../../rst/dev_guide/testing.rst:91 +#: ../../rst/dev_guide/testing.rst:97 msgid "a timeout creating a virtual machine to run the tests on" msgstr "テストを実行ã™ã‚‹ãŸã‚ã®ä»®æƒ³ãƒžã‚·ãƒ³ã‚’作æˆã™ã‚‹ã‚¿ã‚¤ãƒ アウト。" -#: ../../rst/dev_guide/testing.rst:93 +#: ../../rst/dev_guide/testing.rst:99 msgid "If either of these issues appear to be the case, you can rerun the Azure Pipelines test by:" msgstr "ã“れらã®å•é¡Œã®ã„ãšã‚Œã‹ãŒã‚±ãƒ¼ã‚¹ã¨ã—ã¦è¡¨ç¤ºã•ã‚Œã‚‹å ´åˆã¯ã€ä»¥ä¸‹ã‚’実行ã—㦠Azure Pipelines テストをå†å®Ÿè¡Œã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:95 +#: ../../rst/dev_guide/testing.rst:101 msgid "adding a comment with ``/rebuild`` (full rebuild) or ``/rebuild_failed`` (rebuild only failed CI nodes) to the PR" msgstr "``/rebuild`` (完全ãªå†æ§‹ç¯‰) ã¾ãŸã¯ ``/rebuild_failed`` (構築ã«å¤±æ•—ã—㟠CI ノードã®ã¿ã®å†æ§‹ç¯‰) ã§ã®ã‚³ãƒ¡ãƒ³ãƒˆã‚’è¿½åŠ ã™ã‚‹" -#: ../../rst/dev_guide/testing.rst:96 +#: ../../rst/dev_guide/testing.rst:102 msgid "closing and re-opening the PR (full rebuild)" msgstr "PR ã‚’é–‰ã˜ã¦å†åº¦é–‹ã (完全ãªå†æ§‹ç¯‰)" -#: ../../rst/dev_guide/testing.rst:97 +#: ../../rst/dev_guide/testing.rst:103 msgid "making another change to the PR and pushing to GitHub" msgstr "PR ã«ä½•ã‚‰ã‹ã®å¤‰æ›´ã‚’åŠ ãˆã¦ GitHub ã«ãƒ—ッシュã™ã‚‹" -#: ../../rst/dev_guide/testing.rst:99 +#: ../../rst/dev_guide/testing.rst:105 msgid "If the issue persists, please contact us in the ``#ansible-devel`` chat channel (using Matrix at ansible.im or using IRC at `irc.libera.chat <https://libera.chat/>`_)." msgstr "ãã‚Œã§ã‚‚å•é¡ŒãŒè§£æ±ºã—ãªã„å ´åˆã¯ã€``#ansible-devel`` ãƒãƒ£ãƒƒãƒˆãƒãƒ£ãƒ³ãƒãƒ«ã§ãŠå•ã„åˆã‚ã›ãã ã•ã„（ansible.imã§Matrixを使用ã€ã¾ãŸã¯`irc.libera.chat <https://libera.chat/>`_ã§IRCを使用）。" -#: ../../rst/dev_guide/testing.rst:103 +#: ../../rst/dev_guide/testing.rst:109 msgid "How to test a PR" msgstr "PR をテストã™ã‚‹æ–¹æ³•" -#: ../../rst/dev_guide/testing.rst:105 +#: ../../rst/dev_guide/testing.rst:111 msgid "Ideally, code should add tests that prove that the code works. That's not always possible and tests are not always comprehensive, especially when a user doesn't have access to a wide variety of platforms, or is using an API or web service. In these cases, live testing against real equipment can be more valuable than automation that runs against simulated interfaces. In any case, things should always be tested manually the first time as well." msgstr "ç†æƒ³çš„ã«ã¯ã€ã‚³ãƒ¼ãƒ‰ãŒæ©Ÿèƒ½ã™ã‚‹ã“ã¨ã‚’証明ã™ã‚‹ãƒ†ã‚¹ãƒˆã‚’è¿½åŠ ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚特ã«ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒã•ã¾ã–ã¾ãªãƒ—ラットフォームã«ã‚¢ã‚¯ã‚»ã‚¹ã§ããªã„å ´åˆã€ã¾ãŸã¯ API ã‚„ Web サービスを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ã“ã‚ŒãŒå¿…ãšã—ã‚‚å¯èƒ½ã§ã¯ãªãã€ãƒ†ã‚¹ãƒˆã‚‚å¿…ãšã—も包括的ã§ã¯ã‚ã‚Šã¾ã›ã‚“。ã“ã®ã‚ˆã†ãªå ´åˆã¯ã€ã‚·ãƒŸãƒ¥ãƒ¬ãƒ¼ã‚·ãƒ§ãƒ³ã•ã‚ŒãŸã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ã«å¯¾ã—ã¦å®Ÿè¡Œã•ã‚Œã‚‹è‡ªå‹•åŒ–よりもã€å®Ÿéš›ã®æ©Ÿå™¨ã‚’使用ã—ãŸãƒ©ã‚¤ãƒ–テストã®æ–¹ãŒæœ‰ç›Šã¨ãªã‚Šã¾ã™ã€‚ã„ãšã‚Œã«ã›ã‚ˆã€æœ€åˆã®æ®µéšŽã§ã‚‚常ã«æ‰‹å‹•ã§ãƒ†ã‚¹ãƒˆã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:107 +#: ../../rst/dev_guide/testing.rst:113 msgid "Thankfully, helping to test Ansible is pretty straightforward, assuming you are familiar with how Ansible works." msgstr "Ansible ã®å‹•ä½œã‚’熟知ã—ã¦ã„ã‚Œã°ã€Ansible ã®ãƒ†ã‚¹ãƒˆã‚’手ä¼ã†ã“ã¨ã¯éžå¸¸ã«ç°¡å˜ã§ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:110 +#: ../../rst/dev_guide/testing.rst:116 msgid "Setup: Checking out a Pull Request" msgstr "è¨å®š: プルè¦æ±‚ã®ãƒã‚§ãƒƒã‚¯ã‚¢ã‚¦ãƒˆ" -#: ../../rst/dev_guide/testing.rst:112 +#: ../../rst/dev_guide/testing.rst:118 msgid "You can do this by:" msgstr "ã“ã‚Œã¯ã€ä»¥ä¸‹ã®æ–¹æ³•ã§å®Ÿè¡Œã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:114 +#: ../../rst/dev_guide/testing.rst:120 msgid "checking out Ansible" msgstr "Ansible ã®ãƒã‚§ãƒƒã‚¯ã‚¢ã‚¦ãƒˆ" -#: ../../rst/dev_guide/testing.rst:115 +#: ../../rst/dev_guide/testing.rst:121 msgid "fetching the proposed changes into a test branch" msgstr "æ案ã•ã‚ŒãŸå¤‰æ›´ã‚’テストブランãƒã«å–å¾—" -#: ../../rst/dev_guide/testing.rst:116 +#: ../../rst/dev_guide/testing.rst:122 msgid "testing" msgstr "テスト" -#: ../../rst/dev_guide/testing.rst:117 +#: ../../rst/dev_guide/testing.rst:123 msgid "commenting on that particular issue on GitHub" msgstr "GitHub ã«ç‰¹å®šã®å•é¡Œã«ã¤ã„ã¦ã®ã‚³ãƒ¡ãƒ³ãƒˆ" -#: ../../rst/dev_guide/testing.rst:119 +#: ../../rst/dev_guide/testing.rst:125 msgid "Here's how:" msgstr "以下ã«ã€å®Ÿè¡Œã™ã‚‹æ–¹æ³•ã‚’説明ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:122 +#: ../../rst/dev_guide/testing.rst:128 msgid "Testing source code from GitHub pull requests sent to us does have some inherent risk, as the source code sent may have mistakes or malicious code that could have a negative impact on your system. We recommend doing all testing on a virtual machine, whether a cloud instance, or locally. Some users like Vagrant or Docker for this, but they are optional. It is also useful to have virtual machines of different Linux or other flavors, since some features (for example, package managers such as apt or yum) are specific to those OS versions." msgstr "GitHub ã®ãƒ—ルè¦æ±‚ã‹ã‚‰é€ã‚‰ã‚Œã¦ããŸã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã‚’テストã™ã‚‹ã“ã¨ã«ã¯ãƒªã‚¹ã‚¯ãŒä¼´ã„ã¾ã™ã€‚é€ã‚‰ã‚Œã¦ããŸã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã«ã¯ã€é–“é•ã„や悪æ„ã®ã‚るコードãŒå«ã¾ã‚Œã¦ã„ã¦ã€ã‚·ã‚¹ãƒ†ãƒ ã«å½±éŸ¿ã‚’åŠã¼ã™å¯èƒ½æ€§ãŒã‚ã‚‹ã‹ã‚‰ã§ã™ã€‚ã™ã¹ã¦ã®ãƒ†ã‚¹ãƒˆã¯ã€ä»®æƒ³ãƒžã‚·ãƒ³ä¸Šã§è¡Œã†ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚クラウドインスタンスã§ã‚‚ãƒãƒ¼ã‚«ãƒ«ã§ã‚‚ã‹ã¾ã„ã¾ã›ã‚“。ã“ã®ãŸã‚ã« Vagrant ã‚„ Docker を好むユーザーもã„ã¾ã™ãŒã€ã“れらã¯ä»»æ„ã§ã™ã€‚ã¾ãŸã€ã„ãã¤ã‹ã®æ©Ÿèƒ½ (ãŸã¨ãˆã°ã€apt ã‚„ yum ãªã©ã®ãƒ‘ッケージマãƒãƒ¼ã‚¸ãƒ£ãƒ¼) ã¯ã€ãれら㮠OS ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«å›ºæœ‰ã®ã‚‚ã®ã§ã‚ã‚‹ãŸã‚ã€ç•°ãªã‚‹ Linux ã‚„ãã®ä»–ã®ãƒ•ãƒ¬ãƒ¼ãƒãƒ¼ã®ä»®æƒ³ãƒžã‚·ãƒ³ã‚’用æ„ã—ã¦ãŠãã¨ä¾¿åˆ©ã§ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:129 -msgid "Create a fresh area to work::" +#: ../../rst/dev_guide/testing.rst:135 +msgid "Create a fresh area to work:" msgstr "作æ¥ç”¨ã«æ–°ã—ã„é ˜åŸŸã‚’ä½œæˆã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:135 +#: ../../rst/dev_guide/testing.rst:142 msgid "Next, find the pull request you'd like to test and make note of its number. It will look something like this::" msgstr "次ã«ã€ãƒ†ã‚¹ãƒˆã™ã‚‹ãƒ—ルè¦æ±‚を見ã¤ã‘ã¦ã€ãã®ç•ªå·ã‚’書ãç•™ã‚ã¾ã™ã€‚次ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:139 +#: ../../rst/dev_guide/testing.rst:146 msgid "Only test ``ansible:devel``" msgstr "``ansible:devel`` ã®ã¿ã‚’テストã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:141 +#: ../../rst/dev_guide/testing.rst:148 msgid "It is important that the PR request target be ``ansible:devel``, as we do not accept pull requests into any other branch. Dot releases are cherry-picked manually by Ansible staff." msgstr "ä»–ã®ãƒ–ランãƒã¸ã®ãƒ—ルè¦æ±‚ã¯ä½¿ç”¨ã§ããªã„ãŸã‚ã€PR è¦æ±‚ã®ã‚¿ãƒ¼ã‚²ãƒƒãƒˆã¯ ``ansible:devel`` ã«ã™ã‚‹ã“ã¨ãŒé‡è¦ã§ã™ã€‚ドットリリースã¯ã€Ansible ã®ã‚¹ã‚¿ãƒƒãƒ•ãŒå…¥å¿µã«é¸æŠžã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:143 -msgid "Use the pull request number when you fetch the proposed changes and create your branch for testing::" +#: ../../rst/dev_guide/testing.rst:150 +msgid "Use the pull request number when you fetch the proposed changes and create your branch for testing:" msgstr "æ案ã•ã‚ŒãŸå¤‰æ›´ã‚’å–å¾—ã—ã€ãƒ†ã‚¹ãƒˆç”¨ã«ãƒ–ランãƒã‚’作æˆã™ã‚‹ã¨ãã«ãƒ—ルè¦æ±‚番å·ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:148 +#: ../../rst/dev_guide/testing.rst:157 msgid "The first command fetches the proposed changes from the pull request and creates a new branch named ``testing_PRXXXX``, where the XXXX is the actual number associated with the pull request (for example, 65381). The second command checks out the newly created branch." msgstr "1 ã¤ç›®ã®ã‚³ãƒžãƒ³ãƒ‰ã¯ãƒ—ルè¦æ±‚ã‹ã‚‰æ案ã•ã‚ŒãŸå¤‰æ›´ã‚’å–å¾—ã—ã€``testing_PRXXXX`` ã¨ã„ã†åå‰ã®æ–°è¦ãƒ–ランãƒã‚’作æˆã—ã¾ã™ã€‚XXXX ã¯ãƒ—ルè¦æ±‚ã«é–¢é€£ã™ã‚‹å®Ÿéš›ã®ç•ªå· (例: 65381) ã§ã™ã€‚2 ã¤ç›®ã®ã‚³ãƒžãƒ³ãƒ‰ã¯ã€æ–°ãŸã«ä½œæˆã•ã‚ŒãŸãƒ–ランãƒã‚’ãƒã‚§ãƒƒã‚¯ã‚¢ã‚¦ãƒˆã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:151 +#: ../../rst/dev_guide/testing.rst:160 msgid "If the GitHub user interface shows that the pull request will not merge cleanly, we do not recommend proceeding if you are not somewhat familiar with git and coding, as you will have to resolve a merge conflict. This is the responsibility of the original pull request contributor." msgstr "GitHub ユーザーインターフェースã§ã€ãƒ—ルè¦æ±‚ãŒæ£å¸¸ã«ãƒžãƒ¼ã‚¸ã•ã‚Œãªã„ã¨ç¤ºã•ã‚ŒãŸå ´åˆã¯ã€ãƒžãƒ¼ã‚¸ã®ç«¶åˆã‚’解決ã—ãªã‘ã‚Œã°ãªã‚‰ãªã„ãŸã‚ã€git ãŠã‚ˆã³ã‚³ãƒ¼ãƒ‡ã‚£ãƒ³ã‚°ã«ã‚ã¾ã‚Šç²¾é€šã—ã¦ã„ãªã„å ´åˆã¯ã€ç¶šè¡Œã—ãªã„ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ã€å…ƒã®ãƒ—ルè¦æ±‚ã®æŠ•ç¨¿è€…ã®è²¬ä»»ã§ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:154 +#: ../../rst/dev_guide/testing.rst:163 msgid "Some users do not create feature branches, which can cause problems when they have multiple, unrelated commits in their version of ``devel``. If the source looks like ``someuser:devel``, make sure there is only one commit listed on the pull request." msgstr "一部ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã¯æ©Ÿèƒ½ãƒ–ランãƒã‚’作æˆã—ãªã„ãŸã‚ã€``devel`` ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«é–¢é€£æ€§ã®ãªã„コミットãŒè¤‡æ•°ã‚ã‚‹å ´åˆã«ã€å•é¡ŒãŒç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚ソース㌠``someuser:devel`` ã®ã‚ˆã†ã«è¡¨ç¤ºã•ã‚Œã‚‹å ´åˆã¯ã€ãƒ—ルè¦æ±‚ã«è¨˜è¼‰ã•ã‚Œã¦ã„るコミット㌠1 ã¤ã ã‘ã§ã‚ã‚‹ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/testing.rst:156 +#: ../../rst/dev_guide/testing.rst:165 msgid "The Ansible source includes a script that allows you to use Ansible directly from source without requiring a full installation that is frequently used by developers on Ansible." msgstr "Ansible ã®ã‚½ãƒ¼ã‚¹ã«ã¯ã€Ansible ã®é–‹ç™ºè€…ãŒé »ç¹ã«ä½¿ç”¨ã™ã‚‹ãƒ•ãƒ«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã‚’å¿…è¦ã¨ã›ãšã€ã‚½ãƒ¼ã‚¹ã‹ã‚‰ç›´æŽ¥ Ansible を使用ã™ã‚‹ã‚ˆã†ã«ã™ã‚‹ã‚¹ã‚¯ãƒªãƒ—トãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:159 -msgid "Simply source it (to use the Linux/Unix terminology) to begin using it immediately::" +#: ../../rst/dev_guide/testing.rst:168 +msgid "Simply source it (to use the Linux/Unix terminology) to begin using it immediately:" msgstr "ソースを作æˆã™ã‚‹ã ã‘ (Linux/Unix ã®ç”¨èªžã‚’使用ã™ã‚‹ãŸã‚ã«) ã§ã€ã™ãã«ä½¿ã„始ã‚ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:163 +#: ../../rst/dev_guide/testing.rst:174 msgid "This script modifies the ``PYTHONPATH`` environment variables (along with a few other things), which will be temporarily set as long as your shell session is open." msgstr "ã“ã®ã‚¹ã‚¯ãƒªãƒ—トã¯ã€``PYTHONPATH`` 環境変数を変更ã—ã¾ã™ (ä»–ã«ã‚‚ã„ãã¤ã‹ã‚ã‚Šã¾ã™)。ã“ã‚Œã¯ã€ã‚·ã‚§ãƒ«ã‚»ãƒƒã‚·ãƒ§ãƒ³ãŒé–‹ã„ã¦ã„ã‚‹é–“ã¯ä¸€æ™‚çš„ã«è¨å®šã•ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:167 +#: ../../rst/dev_guide/testing.rst:178 msgid "Testing the Pull Request" msgstr "プルè¦æ±‚ã®ãƒ†ã‚¹ãƒˆ" -#: ../../rst/dev_guide/testing.rst:169 +#: ../../rst/dev_guide/testing.rst:180 msgid "At this point, you should be ready to begin testing!" msgstr "ã“ã®æ™‚点ã§ãƒ†ã‚¹ãƒˆã‚’開始ã™ã‚‹æº–å‚™ãŒæ•´ã„ã¾ã—ãŸã€‚" -#: ../../rst/dev_guide/testing.rst:171 +#: ../../rst/dev_guide/testing.rst:182 msgid "Some ideas of what to test are:" msgstr "何をテストã™ã‚‹ã‹ã®ã‚¢ã‚¤ãƒ‡ã‚¢ã‚’ã„ãã¤ã‹æŒ™ã’ã¦ã¿ã¾ã—ょã†ã€‚" -#: ../../rst/dev_guide/testing.rst:173 +#: ../../rst/dev_guide/testing.rst:184 msgid "Create a test Playbook with the examples in and check if they function correctly" msgstr "例題をå«ã‚€ãƒ†ã‚¹ãƒˆ Playbook を作æˆã—ã€ãれらãŒæ£ã—ã機能ã™ã‚‹ã‹ã©ã†ã‹ã‚’確èªã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:174 +#: ../../rst/dev_guide/testing.rst:185 msgid "Test to see if any Python backtraces returned (that's a bug)" msgstr "Python ã®ãƒãƒƒã‚¯ãƒˆãƒ¬ãƒ¼ã‚¹ãŒè¿”ã•ã‚Œã¦ã„ã‚‹ã‹ã©ã†ã‹ã‚’テストã—ã¾ã™ (ã“ã‚Œã¯ãƒã‚°ã§ã™)。" -#: ../../rst/dev_guide/testing.rst:175 +#: ../../rst/dev_guide/testing.rst:186 msgid "Test on different operating systems, or against different library versions" msgstr "ç•°ãªã‚‹ã‚ªãƒšãƒ¬ãƒ¼ãƒ†ã‚£ãƒ³ã‚°ã‚·ã‚¹ãƒ†ãƒ ã§ã€ã¾ãŸã¯ç•°ãªã‚‹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒ©ã‚¤ãƒ–ラリーã«å¯¾ã—ã¦ãƒ†ã‚¹ãƒˆã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:178 +#: ../../rst/dev_guide/testing.rst:189 msgid "Run sanity tests" msgstr "å¥å…¨æ€§ãƒ†ã‚¹ãƒˆã®å®Ÿè¡Œ" -#: ../../rst/dev_guide/testing.rst:184 +#: ../../rst/dev_guide/testing.rst:195 msgid "More information: :ref:`testing_sanity`" msgstr "è©³ç´°æƒ…å ±: :ref:`testing_sanity`" -#: ../../rst/dev_guide/testing.rst:187 +#: ../../rst/dev_guide/testing.rst:198 msgid "Run unit tests" msgstr "ユニットテストã®å®Ÿè¡Œ" -#: ../../rst/dev_guide/testing.rst:193 +#: ../../rst/dev_guide/testing.rst:204 msgid "More information: :ref:`testing_units`" msgstr "è©³ç´°æƒ…å ±: :ref:`testing_units`" -#: ../../rst/dev_guide/testing.rst:196 +#: ../../rst/dev_guide/testing.rst:207 msgid "Run integration tests" msgstr "çµ±åˆãƒ†ã‚¹ãƒˆã®å®Ÿè¡Œ" -#: ../../rst/dev_guide/testing.rst:202 +#: ../../rst/dev_guide/testing.rst:213 msgid "More information: :ref:`testing_integration`" msgstr "è©³ç´°æƒ…å ±: :ref:`testing_integration`" -#: ../../rst/dev_guide/testing.rst:204 +#: ../../rst/dev_guide/testing.rst:215 msgid "Any potential issues should be added as comments on the pull request (and it's acceptable to comment if the feature works as well), remembering to include the output of ``ansible --version``" msgstr "潜在的ãªå•é¡ŒãŒã‚ã‚Œã°ã€ãƒ—ルè¦æ±‚ã«ã‚³ãƒ¡ãƒ³ãƒˆã‚’è¿½åŠ ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (機能ãŒæ£å¸¸ã«å‹•ä½œã™ã‚‹å ´åˆã‚‚コメントã—ã¦ã‚‚ã‹ã¾ã„ã¾ã›ã‚“)。忘れãšã« ``ansible --version`` ã®å‡ºåŠ›ã‚’転載ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/testing.rst:206 +#: ../../rst/dev_guide/testing.rst:217 msgid "Example::" msgstr "例:" -#: ../../rst/dev_guide/testing.rst:210 +#: ../../rst/dev_guide/testing.rst:221 msgid "If the PR does not resolve the issue, or if you see any failures from the unit/integration tests, just include that output instead:" msgstr "PR ãŒå•é¡Œã‚’解決ã—ãªã„å ´åˆã‚„ã€ãƒ¦ãƒ‹ãƒƒãƒˆ/çµ±åˆãƒ†ã‚¹ãƒˆã§ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã—ãŸå ´åˆã¯ã€ä»£ã‚ã‚Šã«ãã®å‡ºåŠ›ã‚’転載ã—ã¦ãã ã•ã„。" @@ -11406,23 +11417,23 @@ msgstr "StackTrace" msgid "some other output" msgstr "some other output" -#: ../../rst/dev_guide/testing.rst:223 +#: ../../rst/dev_guide/testing.rst:234 msgid "Code Coverage Online" msgstr "オンラインã®ã‚³ãƒ¼ãƒ‰ã‚«ãƒãƒ¬ãƒ¼ã‚¸" -#: ../../rst/dev_guide/testing.rst:225 +#: ../../rst/dev_guide/testing.rst:236 msgid "`The online code coverage reports <https://codecov.io/gh/ansible/ansible>`_ are a good way to identify areas for testing improvement in Ansible. By following red colors you can drill down through the reports to find files which have no tests at all. Adding both integration and unit tests which show clearly how code should work, verify important Ansible functions and increase testing coverage in areas where there is none is a valuable way to help improve Ansible." msgstr "`オンラインコードカãƒãƒ¬ãƒ¼ã‚¸ãƒ¬ãƒãƒ¼ãƒˆ <https://codecov.io/gh/ansible/ansible>`_ ã¯ã€Ansible ã§ãƒ†ã‚¹ãƒˆãŒå‘上ã™ã‚‹é ˜åŸŸã‚’特定ã™ã‚‹ã®ãŒé©åˆ‡ãªæ–¹æ³•ã§ã™ã€‚赤ã„色ã«å¾“ã†ã“ã¨ã§ã€ãƒ¬ãƒãƒ¼ãƒˆã‚’掘り下ã’ã¦ã€ãƒ†ã‚¹ãƒˆãŒã¾ã£ãŸããªã„ファイルを見ã¤ã‘ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚コードãŒã©ã®ã‚ˆã†ã«æ©Ÿèƒ½ã™ã‚‹ã‹ã‚’明確ã«ç¤ºã™çµ±åˆãƒ†ã‚¹ãƒˆã¨ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã®ä¸¡æ–¹ã‚’è¿½åŠ ã—ã€é‡è¦ãª Ansible 関数を検証ã—ã€å˜åœ¨ã—ãªã„é ˜åŸŸã§ãƒ†ã‚¹ãƒˆç¯„囲を拡大ã™ã‚‹ã“ã¨ã¯ã€Ansible ã®æ”¹å–„ã«å½¹ç«‹ã¤è²´é‡ãªæ–¹æ³•ã§ã™ã€‚" -#: ../../rst/dev_guide/testing.rst:232 +#: ../../rst/dev_guide/testing.rst:243 msgid "The code coverage reports only cover the ``devel`` branch of Ansible where new feature development takes place. Pull requests and new code will be missing from the codecov.io coverage reports so local reporting is needed. Most ``ansible-test`` commands allow you to collect code coverage, this is particularly useful to indicate where to extend testing. See :ref:`testing_running_locally` for more information." msgstr "コードカãƒãƒ¬ãƒƒã‚¸ãƒ¬ãƒãƒ¼ãƒˆã¯ã€æ–°ã—ã„機能開発ãŒè¡Œã‚れる Ansible ã® ``devel`` ブランãƒã®ã¿ã‚’対象ã¨ã—ã¾ã™ã€‚プルè¦æ±‚ãŠã‚ˆã³æ–°è¦ã‚³ãƒ¼ãƒ‰ã¯ codecov.io ã®ã‚«ãƒãƒ¬ãƒƒã‚¸ãƒ¬ãƒãƒ¼ãƒˆã«å«ã¾ã‚Œãªã„ãŸã‚ã€ãƒãƒ¼ã‚«ãƒ«ãƒ¬ãƒãƒ¼ãƒˆãŒå¿…è¦ã«ãªã‚‹ã‚ˆã†ã§ã™ã€‚ã»ã¨ã‚“ã©ã® ``ansible-test`` コマンドã§ã¯ã€ã‚³ãƒ¼ãƒ‰ã‚«ãƒãƒ¬ãƒƒã‚¸ã‚’åŽé›†ã§ãã¾ã™ã€‚ã“ã‚Œã¯ã€ãƒ†ã‚¹ãƒˆã‚’æ‹¡å¼µã™ã‚‹å ´æ‰€ã‚’示ã™ã®ã«ç‰¹ã«å½¹ã«ç«‹ã¡ã¾ã™ã€‚詳細ã¯ã€ã€Œ:ref:`testing_running_locally`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/testing.rst:240 +#: ../../rst/dev_guide/testing.rst:251 msgid "Want to know more about testing?" msgstr "テストã«é–¢ã™ã‚‹è©³ç´°æƒ…å ±" -#: ../../rst/dev_guide/testing.rst:242 +#: ../../rst/dev_guide/testing.rst:253 msgid "If you'd like to know more about the plans for improving testing Ansible then why not join the `Testing Working Group <https://github.com/ansible/community/blob/master/meetings/README.md>`_." msgstr "Ansible テストを改善ã™ã‚‹è©³ç´°ãªè¨ˆç”»ã‚’確èªã—ãŸã„å ´åˆã¯ã€`テストワーã‚ンググループ <https://github.com/ansible/community/blob/master/meetings/README.md>`_ ã«ã”å‚åŠ ãã ã•ã„。" @@ -12459,10 +12470,10 @@ msgid "As of Ansible 2.8, ``Display`` should no longer be imported from ``__main msgstr "Ansible 2.8 以é™ã€``Display`` 㯠``__main__`` ã‹ã‚‰ã‚¤ãƒ³ãƒãƒ¼ãƒˆã—ãªã„よã†ã«ã—ã¦ãã ã•ã„。" #: ../../rst/dev_guide/testing/sanity/no-main-display.rst:6 -msgid "``Display`` is now a singleton and should be utilized like the following::" +msgid "``Display`` is now a singleton and should be utilized like the following:" msgstr "``Display`` ã¯ã‚·ãƒ³ã‚°ãƒ«ãƒˆãƒ³ã§ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ä½¿ç”¨ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing/sanity/no-main-display.rst:11 +#: ../../rst/dev_guide/testing/sanity/no-main-display.rst:13 msgid "There is no longer a need to attempt ``from __main__ import display`` inside a ``try/except`` block." msgstr "``try/except`` ブãƒãƒƒã‚¯å†…㧠``from __main__ import display`` を試行ã™ã‚‹å¿…è¦ãŒãªããªã‚Šã¾ã—ãŸã€‚" @@ -12936,7 +12947,7 @@ msgid "For advanced usage see the help:" msgstr "高度ãªä½¿ç”¨æ–¹æ³•ã¯ã€ãƒ˜ãƒ«ãƒ—ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" #: ../../rst/dev_guide/testing_compile.rst:58 -#: ../../rst/dev_guide/testing_units.rst:66 +#: ../../rst/dev_guide/testing_units.rst:68 msgid "Installing dependencies" msgstr "ä¾å˜é–¢ä¿‚ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" @@ -13078,265 +13089,261 @@ msgid "ansible-test command" msgstr "ansible-test コマンド" #: ../../rst/dev_guide/testing_integration.rst:35 -msgid "The example below assumes ``bin/`` is in your ``$PATH``. An easy way to achieve that is to initialize your environment with the ``env-setup`` command::" +msgid "The example below assumes ``bin/`` is in your ``$PATH``. An easy way to achieve that is to initialize your environment with the ``env-setup`` command:" msgstr "以下ã®ä¾‹ã§ã¯ã€``bin/`` ㌠``$PATH`` ã§ã‚ã‚‹ã“ã¨ã‚’å‰æã¨ã—ã¦ã„ã¾ã™ã€‚ã“ã‚Œã¯ã€``env-setup`` コマンドã§ç’°å¢ƒã‚’åˆæœŸåŒ–ã™ã‚‹ç°¡å˜ãªæ–¹æ³•ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:41 -msgid "You can also call ``ansible-test`` with the full path::" +#: ../../rst/dev_guide/testing_integration.rst:43 +msgid "You can also call ``ansible-test`` with the full path:" msgstr "完全パス㧠``ansible-test`` を呼ã³å‡ºã™ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:46 +#: ../../rst/dev_guide/testing_integration.rst:50 msgid "integration_config.yml" msgstr "integration_config.yml" -#: ../../rst/dev_guide/testing_integration.rst:48 +#: ../../rst/dev_guide/testing_integration.rst:52 msgid "Making your own version of ``integration_config.yml`` can allow for setting some tunable parameters to help run the tests better in your environment. Some tests (for example, cloud tests) will only run when access credentials are provided. For more information about supported credentials, refer to the various ``cloud-config-*.template`` files in the ``test/integration/`` directory." msgstr "自身ã§ä½œæˆã—㟠``integration_config.yml`` ãŒã‚ã‚‹ã¨ã€ä¸€éƒ¨ã®èª¿æ•´å¯èƒ½ãªãƒ‘ラメーターをè¨å®šã—ã¦ã€ç’°å¢ƒã«ã‚ˆã‚Šé©åˆ‡ã«ãƒ†ã‚¹ãƒˆã‚’実行ã§ãã¾ã™ã€‚一部ã®ãƒ†ã‚¹ãƒˆ (クラウドテストãªã©) ã¯ã€ã‚¢ã‚¯ã‚»ã‚¹èªè¨¼æƒ…å ±ãŒæä¾›ã•ã‚Œã¦ã„ã‚‹å ´åˆã«ã®ã¿å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚サãƒãƒ¼ãƒˆå¯¾è±¡ã®èªè¨¼æƒ…å ±ã®è©³ç´°ã¯ã€``test/integration/`` ディレクトリーã§ã•ã¾ã–ã¾ãª ``cloud-config-*.template`` ファイルをå‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/testing_integration.rst:57 +#: ../../rst/dev_guide/testing_integration.rst:61 msgid "Some tests assume things like hg, svn, and git are installed, and in path. Some tests (such as those for Amazon Web Services) need separate definitions, which will be covered later in this document." msgstr "一部ã®ãƒ†ã‚¹ãƒˆã§ã¯ã€hgã€svnã€git ãªã©ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã€ãƒ‘スã«ã‚ã‚‹ã“ã¨ã‚’å‰æã¨ã—ã¦ã„ã¾ã™ã€‚一部ã®ãƒ†ã‚¹ãƒˆ (Amazon Web Services ã®ãƒ†ã‚¹ãƒˆãªã©) ã«ã¯å€‹åˆ¥ã®å®šç¾©ãŒå¿…è¦ã§ã™ã€‚ã“ã‚Œã«ã¤ã„ã¦ã¯ã€ã“ã®ãƒ‰ã‚ュメントã®å¾ŒåŠã§èª¬æ˜Žã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:61 +#: ../../rst/dev_guide/testing_integration.rst:65 msgid "(Complete list pending)" msgstr "(完全ã¯ãƒªã‚¹ãƒˆã¯å¾Œæ—¥è¿½åŠ ã•ã‚Œã¾ã™)" -#: ../../rst/dev_guide/testing_integration.rst:64 +#: ../../rst/dev_guide/testing_integration.rst:68 msgid "Non-destructive Tests" msgstr "éžç ´å£Šãƒ†ã‚¹ãƒˆ" -#: ../../rst/dev_guide/testing_integration.rst:66 +#: ../../rst/dev_guide/testing_integration.rst:70 msgid "These tests will modify files in subdirectories, but will not do things that install or remove packages or things outside of those test subdirectories. They will also not reconfigure or bounce system services." msgstr "ã“れらã®ãƒ†ã‚¹ãƒˆã¯ã‚µãƒ–ディレクトリー内ã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’ä¿®æ£ã—ã¾ã™ãŒã€ãƒ‘ッケージやテストã®ã‚µãƒ–ディレクトリー以外ã«ã‚ã‚‹ã‚‚ã®ã‚’インストールã—ãŸã‚Šå‰Šé™¤ã—ãŸã‚Šã™ã‚‹ã‚ˆã†ãªã“ã¨ã¯ã—ã¾ã›ã‚“。ã¾ãŸã€ã‚·ã‚¹ãƒ†ãƒ サービスã®å†è¨å®šã‚„ãƒã‚¦ãƒ³ã‚¹ã‚‚è¡Œã„ã¾ã›ã‚“。" -#: ../../rst/dev_guide/testing_integration.rst:69 -msgid "Running integration tests within Docker" -msgstr "Docker 内ã§ã®çµ±åˆãƒ†ã‚¹ãƒˆã®å®Ÿè¡Œ" - -#: ../../rst/dev_guide/testing_integration.rst:71 -msgid "To protect your system from any potential changes caused by integration tests, and to ensure a sensible set of dependencies are available we recommend that you always run integration tests with the ``--docker`` option, for example ``--docker centos8``. See the `list of supported docker images <https://github.com/ansible/ansible/blob/devel/test/lib/ansible_test/_data/completion/docker.txt>`_ for options (the ``default`` image is used for sanity and unit tests, as well as for platform independent integration tests such as those for cloud modules)." -msgstr "çµ±åˆãƒ†ã‚¹ãƒˆã«ã‚ˆã‚‹æ½œåœ¨çš„ãªå¤‰æ›´ã‹ã‚‰ã‚·ã‚¹ãƒ†ãƒ を守りã€é©åˆ‡ãªä¾å˜é–¢ä¿‚セットãŒåˆ©ç”¨å¯èƒ½ã«ãªã‚‹ã‚ˆã†ã«ã™ã‚‹ã«ã¯ã€å¸¸ã« ``--docker`` オプションをã¤ã‘ã¦çµ±åˆãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ (``--docker centos8`` ãªã©)。オプションã«ã¤ã„ã¦ã¯ã€ã€Œ`サãƒãƒ¼ãƒˆå¯¾è±¡å¤–ã® docker イメージã®ä¸€è¦§ <https://github.com/ansible/ansible/blob/devel/test/lib/ansible_test/_data/completion/docker.txt>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„ (``default``イメージã¯ã€å¥å…¨æ€§ãƒ†ã‚¹ãƒˆã¨ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã€ãŠã‚ˆã³ã‚¯ãƒ©ã‚¦ãƒ‰ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãªã©ã®ãƒ—ラットフォームã«ä¾å˜ã—ãªã„çµ±åˆãƒ†ã‚¹ãƒˆã«ä½¿ç”¨ã•ã‚Œã¾ã™)。" - #: ../../rst/dev_guide/testing_integration.rst:73 -msgid "Avoiding pulling new Docker images" -msgstr "æ–°è¦ Docker イメージã®ãƒ—ルã®å›žé¿" +msgid "Running integration tests within containers" +msgstr "コンテナー内ã§ã®çµ±åˆãƒ†ã‚¹ãƒˆã®å®Ÿè¡Œ" #: ../../rst/dev_guide/testing_integration.rst:75 -msgid "Use the ``--docker-no-pull`` option to avoid pulling the latest container image. This is required when using custom local images that are not available for download." -msgstr "最新ã®ã‚³ãƒ³ãƒ†ãƒŠãƒ¼ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’プルã—ãªã„よã†ã«ã™ã‚‹ã«ã¯ã€``--docker-no-pull`` オプションを使用ã—ã¾ã™ã€‚ã“ã‚Œã¯ã€ãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰ã«åˆ©ç”¨ã§ããªã„カスタムã®ãƒãƒ¼ã‚«ãƒ«ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’使用ã™ã‚‹å ´åˆã«å¿…è¦ã§ã™ã€‚" +msgid "To protect your system from any potential changes caused by integration tests, and to ensure a sensible set of dependencies are available we recommend that you always run integration tests with the ``--docker`` option, for example ``--docker centos8``. See the `list of supported container images <https://github.com/ansible/ansible/blob/devel/test/lib/ansible_test/_data/completion/docker.txt>`_ for options (the ``default`` image is used for sanity and unit tests, as well as for platform independent integration tests such as those for cloud modules)." +msgstr "çµ±åˆãƒ†ã‚¹ãƒˆã«ã‚ˆã‚‹æ½œåœ¨çš„ãªå¤‰æ›´ã‹ã‚‰ã‚·ã‚¹ãƒ†ãƒ を守りã€é©åˆ‡ãªä¾å˜é–¢ä¿‚セットãŒåˆ©ç”¨å¯èƒ½ã«ãªã‚‹ã‚ˆã†ã«ã™ã‚‹ã«ã¯ã€å¸¸ã« ``--docker`` オプションをã¤ã‘ã¦çµ±åˆãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ (``--docker centos8`` ãªã©)。オプションã«ã¤ã„ã¦ã¯ã€`サãƒãƒ¼ãƒˆã•ã‚Œã‚‹ã‚³ãƒ³ãƒ†ãƒŠãƒ¼ã‚¤ãƒ¡ãƒ¼ã‚¸ã®ãƒªã‚¹ãƒˆ <https://github.com/ansible/ansible/blob/devel/test/lib/ansible_test/_data/completion/docker.txt>`_ã‚’å‚ç…§ã—ã¦ãã ã•ã„ (``default``イメージã¯ã€å¥å…¨æ€§ãƒ†ã‚¹ãƒˆã¨ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã€ãŠã‚ˆã³ã‚¯ãƒ©ã‚¦ãƒ‰ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãªã©ã®ãƒ—ラットフォームã«ä¾å˜ã—ãªã„çµ±åˆãƒ†ã‚¹ãƒˆã«ä½¿ç”¨ã•ã‚Œã¾ã™)。" #: ../../rst/dev_guide/testing_integration.rst:77 -msgid "Run as follows for all POSIX platform tests executed by our CI system in a fedora32 docker container::" -msgstr "fedora32 docker コンテナー㧠CI システムã«ã‚ˆã£ã¦å®Ÿè¡Œã•ã‚Œã‚‹ã™ã¹ã¦ã® POSIX プラットフォームテストã«å¯¾ã—ã¦æ¬¡ã®ã‚ˆã†ã«å®Ÿè¡Œã—ã¾ã™ã€‚" +msgid "Run as follows for all POSIX platform tests executed by our CI system in a Fedora 34 container:" +msgstr "Fedora 34 コンテナー㧠CI システムã«ã‚ˆã£ã¦å®Ÿè¡Œã•ã‚Œã‚‹ã™ã¹ã¦ã® POSIX プラットフォームテストã«å¯¾ã—ã¦æ¬¡ã®ã‚ˆã†ã«å®Ÿè¡Œã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:81 -msgid "You can target a specific tests as well, such as for individual modules::" +#: ../../rst/dev_guide/testing_integration.rst:83 +msgid "You can target a specific tests as well, such as for individual modules:" msgstr "個々ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãªã©ã€ç‰¹å®šã®ãƒ†ã‚¹ãƒˆã‚’対象ã¨ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:85 -msgid "You can use the ``-v`` option to make the output more verbose::" +#: ../../rst/dev_guide/testing_integration.rst:89 +msgid "You can use the ``-v`` option to make the output more verbose:" msgstr "``-v`` オプションを使用ã™ã‚‹ã¨ã€å‡ºåŠ›ã‚’ã•ã‚‰ã«è©³ç´°ã«ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:89 -msgid "Use the following command to list all the available targets::" +#: ../../rst/dev_guide/testing_integration.rst:95 +msgid "Use the following command to list all the available targets:" msgstr "利用å¯èƒ½ãªã‚¿ãƒ¼ã‚²ãƒƒãƒˆã®ä¸€è¦§ã‚’表示ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:93 +#: ../../rst/dev_guide/testing_integration.rst:101 msgid "Bash users" msgstr "Bash ユーザー" -#: ../../rst/dev_guide/testing_integration.rst:95 +#: ../../rst/dev_guide/testing_integration.rst:103 msgid "If you use ``bash`` with ``argcomplete``, obtain a full list by doing: ``ansible-test integration <tab><tab>``" msgstr "``bash`` ã‚’ ``argcomplete`` ã¨ã¨ã‚‚ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€``ansible-test integration <tab><tab>`` を実行ã—ã¦å®Œå…¨ãªä¸€è¦§ã‚’å–å¾—ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:98 +#: ../../rst/dev_guide/testing_integration.rst:106 msgid "Destructive Tests" msgstr "ç ´å£Šãƒ†ã‚¹ãƒˆ" -#: ../../rst/dev_guide/testing_integration.rst:100 -msgid "These tests are allowed to install and remove some trivial packages. You will likely want to devote these to a virtual environment, such as Docker. They won't reformat your filesystem::" +#: ../../rst/dev_guide/testing_integration.rst:108 +msgid "These tests are allowed to install and remove some trivial packages. You will likely want to devote these to a virtual environment, such as Docker. They won't reformat your filesystem:" msgstr "ã“れらã®ãƒ†ã‚¹ãƒˆã§ã¯ã€ã„ãã¤ã‹ã®ç°¡å˜ãªãƒ‘ッケージをインストールãŠã‚ˆã³å‰Šé™¤ã§ãã¾ã™ã€‚ã“れらを Docker ãªã©ã®ä»®æƒ³ç’°å¢ƒå°‚用ã«ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚ã“れらã¯ã€ãƒ•ã‚¡ã‚¤ãƒ«ã‚·ã‚¹ãƒ†ãƒ ã‚’å†ãƒ•ã‚©ãƒ¼ãƒžãƒƒãƒˆã—ã¾ã›ã‚“。" -#: ../../rst/dev_guide/testing_integration.rst:106 +#: ../../rst/dev_guide/testing_integration.rst:116 msgid "Windows Tests" msgstr "Windows テスト" -#: ../../rst/dev_guide/testing_integration.rst:108 +#: ../../rst/dev_guide/testing_integration.rst:118 msgid "These tests exercise the ``winrm`` connection plugin and Windows modules. You'll need to define an inventory with a remote Windows 2008 or 2012 Server to use for testing, and enable PowerShell Remoting to continue." msgstr "ã“れらã®ãƒ†ã‚¹ãƒˆã¯ã€``winrm`` connection プラグイン㨠Windows モジュールã«å¾“ã„ã¾ã™ã€‚テストã«ä½¿ç”¨ã™ã‚‹ãƒªãƒ¢ãƒ¼ãƒˆ Windows 2008 Server ã¾ãŸã¯ 2012 Server ã‚’æŒã¤ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚’定義ã—ã€PowerShell Remoting を継続ã§ãるよã†ã«ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:112 +#: ../../rst/dev_guide/testing_integration.rst:122 msgid "Running these tests may result in changes to your Windows host, so don't run them against a production/critical Windows environment." msgstr "ã“れらã®ãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã¨ã€Windows ホストãŒå¤‰æ›´ã«ãªã‚‹å¯èƒ½æ€§ãŒã‚ã‚‹ãŸã‚ã€å®Ÿç¨¼åƒç’°å¢ƒã‚„é‡è¦ãª Windows 環境ã§ã¯å®Ÿè¡Œã—ãªã„ã§ãã ã•ã„。" -#: ../../rst/dev_guide/testing_integration.rst:115 -msgid "Enable PowerShell Remoting (run on the Windows host via Remote Desktop)::" +#: ../../rst/dev_guide/testing_integration.rst:125 +msgid "Enable PowerShell Remoting (run on the Windows host via Remote Desktop):" msgstr "PowerShell Remoting を有効ã«ã—ã¾ã™ (リモートデスクトップを介ã—㦠Windows ホストã§å®Ÿè¡Œã—ã¾ã™)。" -#: ../../rst/dev_guide/testing_integration.rst:119 -msgid "Define Windows inventory::" +#: ../../rst/dev_guide/testing_integration.rst:131 +msgid "Define Windows inventory:" msgstr "Windows インベントリーを定義ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:124 -msgid "Run the Windows tests executed by our CI system::" +#: ../../rst/dev_guide/testing_integration.rst:138 +msgid "Run the Windows tests executed by our CI system:" msgstr "CI システムã§å®Ÿè¡Œã™ã‚‹ Windows テストを実行ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:129 -msgid "Tests in Docker containers" -msgstr "Docker コンテナーã§ã®ãƒ†ã‚¹ãƒˆ" +#: ../../rst/dev_guide/testing_integration.rst:145 +msgid "Tests in containers" +msgstr "コンテナーã§ã®ãƒ†ã‚¹ãƒˆ" -#: ../../rst/dev_guide/testing_integration.rst:131 -msgid "If you have a Linux system with Docker installed, running integration tests using the same Docker containers used by the Ansible continuous integration (CI) system is recommended." -msgstr "Docker ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚ŒãŸ Linux システムをãŠæŒã¡ã®å ´åˆã¯ã€Ansible ã®ç¶™ç¶šçš„çµ±åˆ (CI) システムã§ä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹ã‚‚ã®ã¨åŒã˜ Docker コンテナーを使用ã—ã¦çµ±åˆãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" +#: ../../rst/dev_guide/testing_integration.rst:147 +msgid "If you have a Linux system with Docker or Podman installed, running integration tests using the same containers used by the Ansible continuous integration (CI) system is recommended." +msgstr "Dockerã¾ãŸã¯Podman ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚ŒãŸ Linux システムをãŠæŒã¡ã®å ´åˆã¯ã€Ansible ã®ç¶™ç¶šçš„çµ±åˆ (CI) システムã§ä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹ã‚‚ã®ã¨åŒã˜ã‚³ãƒ³ãƒ†ãƒŠãƒ¼ã‚’使用ã—ã¦çµ±åˆãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" + +#: ../../rst/dev_guide/testing_integration.rst:150 +msgid "Podman" +msgstr "Podman" -#: ../../rst/dev_guide/testing_integration.rst:134 +#: ../../rst/dev_guide/testing_integration.rst:152 +msgid "By default, Podman will only be used if the Docker CLI is not installed. If you have Docker installed but want to use Podman, you can change this behavior by setting the environment variable ``ANSIBLE_TEST_PREFER_PODMAN``." +msgstr "デフォルトã§ã€Podman 㯠Docker CLI ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„å ´åˆã«ã®ã¿ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚Docker ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„㦠Podman を使用ã™ã‚‹å¿…è¦ãŒã‚ã‚‹å ´åˆã¯ã€ç’°å¢ƒå¤‰æ•° ``ANSIBLE_TEST_PREFER_PODMAN`` ã‚’è¨å®šã—ã¦ã“ã®å‹•ä½œã‚’変更ã§ãã¾ã™ã€‚" + +#: ../../rst/dev_guide/testing_integration.rst:155 msgid "Docker on non-Linux" msgstr "Linux 以外㮠Docker" -#: ../../rst/dev_guide/testing_integration.rst:136 +#: ../../rst/dev_guide/testing_integration.rst:157 msgid "Using Docker Engine to run Docker on a non-Linux host (such as macOS) is not recommended. Some tests may fail, depending on the image used for testing. Using the ``--docker-privileged`` option when running ``integration`` (not ``network-integration`` or ``windows-integration``) may resolve the issue." msgstr "Docker Engine を使用ã—㦠(macOS ãªã©ã®) Linux 以外ã®ãƒ›ã‚¹ãƒˆã§ Docker を実行ã™ã‚‹ã“ã¨ã¯æŽ¨å¥¨ã•ã‚Œã¾ã›ã‚“。テストã«ä½¿ç”¨ã•ã‚Œã‚‹ã‚¤ãƒ¡ãƒ¼ã‚¸ã«ã‚ˆã£ã¦ã¯ã€ä¸€éƒ¨ã®ãƒ†ã‚¹ãƒˆãŒå¤±æ•—ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚(``network-integration`` ã¾ãŸã¯ ``windows-integration``ã§ã¯ãªã) ``integration`` ã®å®Ÿè¡Œæ™‚ã« ``--docker-privileged`` オプションを使用ã™ã‚‹ã¨å•é¡ŒãŒè§£æ±ºã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:141 +#: ../../rst/dev_guide/testing_integration.rst:162 msgid "Running Integration Tests" msgstr "çµ±åˆãƒ†ã‚¹ãƒˆã®å®Ÿè¡Œ" -#: ../../rst/dev_guide/testing_integration.rst:143 -msgid "To run all CI integration test targets for POSIX platforms in a Ubuntu 18.04 container::" +#: ../../rst/dev_guide/testing_integration.rst:164 +msgid "To run all CI integration test targets for POSIX platforms in a Ubuntu 18.04 container:" msgstr "Ubuntu 18.04 コンテナー内㮠POSIX プラットフォーム㫠CI çµ±åˆãƒ†ã‚¹ãƒˆã‚¿ãƒ¼ã‚²ãƒƒãƒˆã™ã¹ã¦ã‚’実行ã™ã‚‹ã«ã¯ã€æ¬¡ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:147 -msgid "You can also run specific tests or select a different Linux distribution. For example, to run tests for the ``ping`` module on a Ubuntu 18.04 container::" +#: ../../rst/dev_guide/testing_integration.rst:170 +msgid "You can also run specific tests or select a different Linux distribution. For example, to run tests for the ``ping`` module on a Ubuntu 18.04 container:" msgstr "特定ã®ãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã“ã¨ã‚‚ã€åˆ¥ã® Linux ディストリビューションをé¸æŠžã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€Ubuntu 18.04 コンテナー㧠``ping`` モジュールã®ãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã«ã¯ã€æ¬¡ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:153 +#: ../../rst/dev_guide/testing_integration.rst:178 msgid "Container Images" msgstr "コンテナーイメージ" -#: ../../rst/dev_guide/testing_integration.rst:156 -msgid "Python 2" -msgstr "Python 2" - -#: ../../rst/dev_guide/testing_integration.rst:158 -msgid "Most container images are for testing with Python 2:" -msgstr "ã»ã¨ã‚“ã©ã®ã‚³ãƒ³ãƒ†ãƒŠãƒ¼ã‚¤ãƒ¡ãƒ¼ã‚¸ã¯ã€Python 2 ã§ãƒ†ã‚¹ãƒˆã™ã‚‹ãŸã‚ã®ã‚‚ã®ã§ã™ã€‚" - -#: ../../rst/dev_guide/testing_integration.rst:160 -msgid "centos6" -msgstr "centos6" - -#: ../../rst/dev_guide/testing_integration.rst:161 -msgid "centos7" -msgstr "centos7" - -#: ../../rst/dev_guide/testing_integration.rst:162 -msgid "opensuse15py2" -msgstr "opensuse15py2" - -#: ../../rst/dev_guide/testing_integration.rst:165 +#: ../../rst/dev_guide/testing_integration.rst:181 msgid "Python 3" msgstr "Python 3" -#: ../../rst/dev_guide/testing_integration.rst:167 -msgid "To test with Python 3 use the following images:" -msgstr "Python 3 ã§ãƒ†ã‚¹ãƒˆã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’使用ã—ã¾ã™ã€‚" +#: ../../rst/dev_guide/testing_integration.rst:183 +msgid "Most container images are for testing with Python 3:" +msgstr "ã»ã¨ã‚“ã©ã®ã‚³ãƒ³ãƒ†ãƒŠãƒ¼ã‚¤ãƒ¡ãƒ¼ã‚¸ã¯ã€Python 3 ã§ãƒ†ã‚¹ãƒˆã™ã‚‹ãŸã‚ã®ã‚‚ã®ã§ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:169 +#: ../../rst/dev_guide/testing_integration.rst:185 msgid "alpine3" msgstr "alpine3" -#: ../../rst/dev_guide/testing_integration.rst:170 +#: ../../rst/dev_guide/testing_integration.rst:186 msgid "centos8" msgstr "centos8" -#: ../../rst/dev_guide/testing_integration.rst:171 -msgid "fedora32" -msgstr "fedora32" - -#: ../../rst/dev_guide/testing_integration.rst:172 +#: ../../rst/dev_guide/testing_integration.rst:187 msgid "fedora33" msgstr "fedora33" -#: ../../rst/dev_guide/testing_integration.rst:173 +#: ../../rst/dev_guide/testing_integration.rst:188 +msgid "fedora34" +msgstr "fedora34" + +#: ../../rst/dev_guide/testing_integration.rst:189 msgid "opensuse15" msgstr "opensuse15" -#: ../../rst/dev_guide/testing_integration.rst:174 +#: ../../rst/dev_guide/testing_integration.rst:190 msgid "ubuntu1804" msgstr "ubuntu1804" -#: ../../rst/dev_guide/testing_integration.rst:175 +#: ../../rst/dev_guide/testing_integration.rst:191 msgid "ubuntu2004" msgstr "ubuntu2004" -#: ../../rst/dev_guide/testing_integration.rst:179 +#: ../../rst/dev_guide/testing_integration.rst:194 +msgid "Python 2" +msgstr "Python 2" + +#: ../../rst/dev_guide/testing_integration.rst:196 +msgid "To test with Python 2 use the following images:" +msgstr "Python 2 ã§ãƒ†ã‚¹ãƒˆã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’使用ã—ã¾ã™ã€‚" + +#: ../../rst/dev_guide/testing_integration.rst:198 +msgid "centos7" +msgstr "centos7" + +#: ../../rst/dev_guide/testing_integration.rst:199 +msgid "opensuse15py2" +msgstr "opensuse15py2" + +#: ../../rst/dev_guide/testing_integration.rst:203 msgid "Legacy Cloud Tests" msgstr "レガシーã®ã‚¯ãƒ©ã‚¦ãƒ‰ãƒ†ã‚¹ãƒˆ" -#: ../../rst/dev_guide/testing_integration.rst:181 +#: ../../rst/dev_guide/testing_integration.rst:205 msgid "Some of the cloud tests run as normal integration tests, and others run as legacy tests; see the :ref:`testing_integration_legacy` page for more information." msgstr "一部ã®ã‚¯ãƒ©ã‚¦ãƒ‰ãƒ†ã‚¹ãƒˆã¯é€šå¸¸ã®çµ±åˆãƒ†ã‚¹ãƒˆã¨ã—ã¦å®Ÿè¡Œã—ã€ãã®ä»–ã¯ãƒ¬ã‚¬ã‚·ãƒ¼ãƒ†ã‚¹ãƒˆã¨ã—ã¦å®Ÿè¡Œã—ã¾ã™ã€‚詳細ã¯ã€ã€Œ:ref:`testing_integration_legacy`ã€ã®ãƒ‰ã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/testing_integration.rst:186 +#: ../../rst/dev_guide/testing_integration.rst:210 msgid "Other configuration for Cloud Tests" msgstr "クラウドテストã®ãã®ä»–ã®è¨å®š" -#: ../../rst/dev_guide/testing_integration.rst:188 +#: ../../rst/dev_guide/testing_integration.rst:212 msgid "In order to run some tests, you must provide access credentials in a file named ``cloud-config-aws.yml`` or ``cloud-config-cs.ini`` in the test/integration directory. Corresponding .template files are available for for syntax help. The newer AWS tests now use the file test/integration/cloud-config-aws.yml" msgstr "test/integration ディレクトリーã«ã‚ã‚‹ ``cloud-config-aws.yml`` ã¾ãŸã¯ ``cloud-config-cs.ini`` ã¨ã„ã†åå‰ã®ãƒ•ã‚¡ã‚¤ãƒ«ã«ã‚るアクセスèªè¨¼æƒ…å ±ã‚’æŒ‡å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚構文ヘルプã§ã¯ã€å¯¾å¿œã™ã‚‹ .template ファイルを利用ã§ãã¾ã™ã€‚æ–°ã—ã„ AWS テストã§ã¯ã€test/integration/cloud-config-aws.yml ファイルãŒä½¿ç”¨ã•ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" -#: ../../rst/dev_guide/testing_integration.rst:194 -#: ../../rst/dev_guide/testing_integration_legacy.rst:58 +#: ../../rst/dev_guide/testing_integration.rst:218 +#: ../../rst/dev_guide/testing_integration_legacy.rst:60 msgid "IAM policies for AWS" msgstr "AWS ã® IAM ãƒãƒªã‚·ãƒ¼" -#: ../../rst/dev_guide/testing_integration.rst:196 +#: ../../rst/dev_guide/testing_integration.rst:220 msgid "Ansible needs fairly wide ranging powers to run the tests in an AWS account. This rights can be provided to a dedicated user. These need to be configured before running the test." msgstr "Ansible ã¯ã€AWS アカウントã§ãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ãŸã‚ã«éžå¸¸ã«å¹…広ã„権é™ãŒå¿…è¦ã«ãªã‚Šã¾ã™ã€‚ã“ã®æ¨©é™ã¯å°‚用ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«æä¾›ã§ãã¾ã™ã€‚ã“れらã®æ¨©é™ã¯ã€ãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹å‰ã«è¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:199 +#: ../../rst/dev_guide/testing_integration.rst:223 msgid "testing-policies" msgstr "testing-policies" -#: ../../rst/dev_guide/testing_integration.rst:201 +#: ../../rst/dev_guide/testing_integration.rst:225 msgid "The GitHub repository `mattclay/aws-terminator <https://github.com/mattclay/aws-terminator/>`_ contains two sets of policies used for all existing AWS module integratoin tests. The `hacking/aws_config/setup_iam.yml` playbook can be used to setup two groups:" msgstr "GitHub リãƒã‚¸ãƒˆãƒªãƒ¼ `mattclay/aws-terminator <https://github.com/mattclay/aws-terminator/>`_ ã«ã¯ã€æ—¢å˜ã® AWS モジュールã®çµ±åˆãƒ†ã‚¹ãƒˆã«ä½¿ç”¨ã™ã‚‹ãƒãƒªã‚·ãƒ¼ã®ã‚»ãƒƒãƒˆãŒ 2 ã¤å«ã¾ã‚Œã¾ã™ã€‚Playbook `hacking/aws_config/setup_iam.yml` を使用ã™ã‚‹ã¨ã€2 ã¤ã®ã‚°ãƒ«ãƒ¼ãƒ—ã‚’è¨å®šã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:205 +#: ../../rst/dev_guide/testing_integration.rst:229 msgid "`ansible-integration-ci` will have the policies applied necessary to run any integration tests not marked as `unsupported` and are designed to mirror those used by Ansible's CI." msgstr "`ansible-integration-ci` ã¯ã€çµ±åˆãƒ†ã‚¹ãƒˆã®å®Ÿè¡Œã«å¿…è¦ã¨ãªã‚‹ãƒãƒªã‚·ãƒ¼ã‚’é©ç”¨ã™ã‚‹ã¨å…±ã«ã€`unsupported` ã¨è˜åˆ¥ã•ã‚Œãšã€Ansible ã® CI ã§ä½¿ç”¨ã•ã‚Œã‚‹ãƒŸãƒ©ãƒ¼ãƒªãƒ³ã‚°ç”¨ã«è¨è¨ˆã•ã‚Œã¦ã„ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:208 +#: ../../rst/dev_guide/testing_integration.rst:232 msgid "`ansible-integration-unsupported` will have the additional policies applied necessary to run the integration tests marked as `unsupported` including tests for managing IAM roles, users and groups." msgstr "`ansible-integration-unsupported` ã¯ã€IAM ãƒãƒ¼ãƒ«ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ã€ãŠã‚ˆã³ã‚°ãƒ«ãƒ¼ãƒ—を管ç†ã™ã‚‹ãŸã‚ã®ãƒ†ã‚¹ãƒˆã‚’å«ã‚€ `unsupported` ã¨ãƒžãƒ¼ã‚¯ã•ã‚ŒãŸçµ±åˆãƒ†ã‚¹ãƒˆã®å®Ÿè¡Œã«å¿…è¦ãªè¿½åŠ ã®ãƒãƒªã‚·ãƒ¼ãŒé©ç”¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:212 +#: ../../rst/dev_guide/testing_integration.rst:236 msgid "Once the groups have been created, you'll need to create a user and make the user a member of these groups. The policies are designed to minimize the rights of that user. Please note that while this policy does limit the user to one region, this does not fully restrict the user (primarily due to the limitations of the Amazon ARN notation). The user will still have wide privileges for viewing account definitions, and will also able to manage some resources that are not related to testing (for example, AWS lambdas with different names). Tests should not be run in a primary production account in any case." msgstr "グループãŒä½œæˆã•ã‚ŒãŸã‚‰ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚’作æˆã—ã¦ã€ãã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚’ã“れらã®ã‚°ãƒ«ãƒ¼ãƒ—ã®ãƒ¡ãƒ³ãƒãƒ¼ã«ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ãƒãƒªã‚·ãƒ¼ã¯ã€ãã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã®æ¨©åˆ©ã‚’最å°é™ã«ã™ã‚‹ãŸã‚ã®ã‚‚ã®ã§ã™ã€‚ã“ã®ãƒãƒªã‚·ãƒ¼ã§ã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚’ 1 ã¤ã®åœ°åŸŸã«é™å®šã—ã¦ã„ã¾ã™ãŒã€ã“ã‚Œã¯ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚’完全ã«ã¯åˆ¶é™ã—ã¦ã„ãªã„ã“ã¨ã«æ³¨æ„ã—ã¦ãã ã•ã„ (主㫠Amazon ARN 表記ã®åˆ¶é™ã«ã‚ˆã‚‹ã‚‚ã®ã§ã™)。ã“ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã¯ã€ã‚¢ã‚«ã‚¦ãƒ³ãƒˆå®šç¾©ã‚’閲覧ã™ã‚‹ãŸã‚ã®åºƒã„権é™ã‚’æŒã£ã¦ãŠã‚Šã€ãƒ†ã‚¹ãƒˆã«é–¢ä¿‚ã®ãªã„ã„ãã¤ã‹ã®ãƒªã‚½ãƒ¼ã‚¹ (ãŸã¨ãˆã°ã€ç•°ãªã‚‹åå‰ã® AWS ラムダ) を管ç†ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚ã©ã®ã‚ˆã†ãªå ´åˆã§ã‚‚ã€ãƒ†ã‚¹ãƒˆã‚’実稼åƒç’°å¢ƒç”¨ã®ãƒ—ライマリーアカウントã§å®Ÿè¡Œã™ã¹ãã§ã¯ã‚ã‚Šã¾ã›ã‚“。" -#: ../../rst/dev_guide/testing_integration.rst:220 -#: ../../rst/dev_guide/testing_integration_legacy.rst:76 +#: ../../rst/dev_guide/testing_integration.rst:244 +#: ../../rst/dev_guide/testing_integration_legacy.rst:78 msgid "Other Definitions required" msgstr "ãã®ä»–ã«å¿…è¦ãªå®šç¾©" -#: ../../rst/dev_guide/testing_integration.rst:222 -#: ../../rst/dev_guide/testing_integration_legacy.rst:78 +#: ../../rst/dev_guide/testing_integration.rst:246 +#: ../../rst/dev_guide/testing_integration_legacy.rst:80 msgid "Apart from installing the policy and giving it to the user identity running the tests, a lambda role `ansible_integration_tests` has to be created which has lambda basic execution privileges." msgstr "ãƒãƒªã‚·ãƒ¼ã‚’インストールã—ã¦ã€ãƒ†ã‚¹ãƒˆã‚’実行ã—ã¦ã„るユーザ ID ã«ãれを付与ã™ã‚‹ã“ã¨ã¨ã¯åˆ¥ã«ã€ãƒ©ãƒ ダãƒãƒ¼ãƒ« `ansible_integration_tests` を作æˆã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€ãƒ©ãƒ ダã®åŸºæœ¬çš„ãªå®Ÿè¡Œæ¨©é™ã‚’æŒã¡ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration.rst:228 +#: ../../rst/dev_guide/testing_integration.rst:252 msgid "Network Tests" msgstr "ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ†ã‚¹ãƒˆ" -#: ../../rst/dev_guide/testing_integration.rst:230 +#: ../../rst/dev_guide/testing_integration.rst:254 msgid "For guidance on writing network test see :ref:`testing_resource_modules`." msgstr "ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ†ã‚¹ãƒˆã®æ›¸ãè¾¼ã¿ã«é–¢ã™ã‚‹æƒ…å ±ã¯ã€ã€Œ:ref:`testing_resource_modules`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/testing_integration.rst:234 +#: ../../rst/dev_guide/testing_integration.rst:258 msgid "Where to find out more" msgstr "ãã®ä»–ã®è©³ç´°æƒ…å ±" -#: ../../rst/dev_guide/testing_integration.rst:236 +#: ../../rst/dev_guide/testing_integration.rst:260 msgid "If you'd like to know more about the plans for improving testing Ansible, join the `Testing Working Group <https://github.com/ansible/community/blob/master/meetings/README.md>`_." msgstr "Ansible テストを改善ã™ã‚‹è©³ç´°ãªè¨ˆç”»ã‚’確èªã—ãŸã„å ´åˆã¯ã€`テストã®ãƒ¯ãƒ¼ã‚ンググループ <https://github.com/ansible/community/blob/master/meetings/README.md>`_ ã«ã”å‚åŠ ãã ã•ã„。" @@ -13417,51 +13424,51 @@ msgid "In order to run cloud tests, you must provide access credentials in a fil msgstr "クラウドテストを実行ã™ã‚‹ã«ã¯ã€``credentials.yml`` ã¨ã„ã†åå‰ã®ãƒ•ã‚¡ã‚¤ãƒ«ã§ã‚¢ã‚¯ã‚»ã‚¹èªè¨¼æƒ…å ±ã‚’æŒ‡å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚構文ヘルプã«ã¯ã€``credentials.template`` ã¨åå‰ã®ä»˜ã„ãŸã‚µãƒ³ãƒ—ルèªè¨¼æƒ…å ±ãƒ•ã‚¡ã‚¤ãƒ«ã‚’åˆ©ç”¨ã§ãã¾ã™ã€‚" #: ../../rst/dev_guide/testing_integration_legacy.rst:44 -msgid "Provide cloud credentials::" +msgid "Provide cloud credentials:" msgstr "クラウドèªè¨¼ã‚’æä¾›ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration_legacy.rst:51 +#: ../../rst/dev_guide/testing_integration_legacy.rst:53 msgid "Other configuration" msgstr "ãã®ä»–ã®è¨å®š" -#: ../../rst/dev_guide/testing_integration_legacy.rst:53 +#: ../../rst/dev_guide/testing_integration_legacy.rst:55 msgid "In order to run some tests, you must provide access credentials in a file named ``credentials.yml``. A sample credentials file named ``credentials.template`` is available for syntax help." msgstr "ã„ãã¤ã‹ã®ãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã«ã¯ã€``credentials.yml`` ã¨ã„ã†åå‰ã®ãƒ•ã‚¡ã‚¤ãƒ«ã§ã‚¢ã‚¯ã‚»ã‚¹èªè¨¼æƒ…å ±ã‚’æŒ‡å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚構文ヘルプã«ã¯ã€``credentials.template`` ã¨åå‰ã®ä»˜ã„ãŸã‚µãƒ³ãƒ—ルèªè¨¼æƒ…å ±ãƒ•ã‚¡ã‚¤ãƒ«ã‚’åˆ©ç”¨ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration_legacy.rst:60 +#: ../../rst/dev_guide/testing_integration_legacy.rst:62 msgid "In order to run the tests in an AWS account ansible needs fairly wide ranging powers which can be provided to a dedicated user or temporary credentials using a specific policy configured in the AWS account." msgstr "AWS アカウントã§ãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã«ã¯ã€Ansible ã«ã€AWS アカウントã§è¨å®šã•ã‚ŒãŸç‰¹å®šã®ãƒãƒªã‚·ãƒ¼ã‚’使用ã—ã¦ã€å°‚用ã®ãƒ¦ãƒ¼ã‚¶ã‚„一時的ãªèªè¨¼æƒ…å ±ã«æä¾›ã§ãã‚‹ã€ã‹ãªã‚Šåºƒç¯„囲ã®æ¨©é™ãŒå¿…è¦ã¨ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration_legacy.rst:65 +#: ../../rst/dev_guide/testing_integration_legacy.rst:67 msgid "testing-iam-policy.json.j2" msgstr "testing-iam-policy.json.j2" -#: ../../rst/dev_guide/testing_integration_legacy.rst:67 +#: ../../rst/dev_guide/testing_integration_legacy.rst:69 msgid "The testing-iam-policy.json.j2 file contains a policy which can be given to the user running the tests to give close to minimum rights required to run the tests. Please note that this does not fully restrict the user; The user has wide privileges for viewing account definitions and is also able to manage some resources that are not related to testing (for example, AWS lambdas with different names) primarily due to the limitations of the Amazon ARN notation. At the very least the policy limits the user to one region, however tests should not be run in a primary production account in any case." msgstr "testing-iam-policy.json.j2 ファイルã«ã¯ã€ãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«ä»˜ä¸Žã™ã‚‹ãƒãƒªã‚·ãƒ¼ãŒå«ã¾ã‚Œã¦ãŠã‚Šã€ãƒ†ã‚¹ãƒˆã®å®Ÿè¡Œã«å¿…è¦ãªæœ€ä½Žé™ã®æ¨©é™ã«è¿‘ã„ã‚‚ã®ã‚’付与ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãªãŠã€ã“ã‚Œã¯å®Œå…¨ãªåˆ¶é™ã§ã¯ãªã„ãŸã‚注æ„ã—ã¦ãã ã•ã„。ã“ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã¯ã€ã‚¢ã‚«ã‚¦ãƒ³ãƒˆå®šç¾©ã‚’閲覧ã™ã‚‹å¹…広ã„権é™ã‚’æŒã¡ã€ä¸»ã« Amazon ARN 表記ã®åˆ¶é™ã«ã‚ˆã‚Šã€ãƒ†ã‚¹ãƒˆã«é–¢ä¿‚ã®ãªã„一部ã®ãƒªã‚½ãƒ¼ã‚¹ (ãŸã¨ãˆã°ã€ç•°ãªã‚‹åå‰ã® AWS ラムダ) を管ç†ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚å°‘ãªãã¨ã‚‚ã€ã“ã®ãƒãƒªã‚·ãƒ¼ã§ã¯ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚’ 1 ã¤ã®ãƒªãƒ¼ã‚¸ãƒ§ãƒ³ã«é™å®šã—ã¦ã„ã¾ã™ãŒã€ã„ã‹ãªã‚‹å ´åˆã§ã‚‚ã€ãƒ†ã‚¹ãƒˆã¯å®Ÿç¨¼åƒç’°å¢ƒã®ãƒ—ライマリーアカウントã§å®Ÿè¡Œã™ã¹ãã§ã¯ã‚ã‚Šã¾ã›ã‚“。" -#: ../../rst/dev_guide/testing_integration_legacy.rst:84 +#: ../../rst/dev_guide/testing_integration_legacy.rst:86 #: ../../rst/dev_guide/testing_units.rst:24 msgid "Running Tests" msgstr "テストã®å®Ÿè¡Œ" -#: ../../rst/dev_guide/testing_integration_legacy.rst:86 +#: ../../rst/dev_guide/testing_integration_legacy.rst:88 msgid "The tests are invoked via a ``Makefile``." msgstr "テスト㯠``Makefile`` 経由ã§å‘¼ã³å‡ºã•ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration_legacy.rst:88 -msgid "If you haven't already got Ansible available use the local checkout by doing::" +#: ../../rst/dev_guide/testing_integration_legacy.rst:90 +msgid "If you haven't already got Ansible available use the local checkout by doing:" msgstr "Ansible ãŒã¾ã 利用å¯èƒ½ã§ãªã„å ´åˆã¯ã€ä»¥ä¸‹ã®æ–¹æ³•ã§ãƒãƒ¼ã‚«ãƒ«ãƒã‚§ãƒƒã‚¯ã‚¢ã‚¦ãƒˆã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration_legacy.rst:92 -msgid "Run the tests by doing::" +#: ../../rst/dev_guide/testing_integration_legacy.rst:96 +msgid "Run the tests by doing:" msgstr "以下を実行ã—ã¦ãƒ†ã‚¹ãƒˆã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_integration_legacy.rst:102 +#: ../../rst/dev_guide/testing_integration_legacy.rst:108 msgid "Possible cost of running cloud tests" msgstr "クラウドテストã«ã‹ã‹ã‚‹å¯èƒ½æ€§ã®ã‚るコスト" -#: ../../rst/dev_guide/testing_integration_legacy.rst:104 +#: ../../rst/dev_guide/testing_integration_legacy.rst:110 msgid "Running cloud integration tests will create and destroy cloud resources. Running these tests may result in additional fees associated with your cloud account. Care is taken to ensure that created resources are removed. However, it is advisable to inspect your AWS console to ensure no unexpected resources are running." msgstr "クラウド統åˆãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã¨ã€ã‚¯ãƒ©ã‚¦ãƒ‰ãƒªã‚½ãƒ¼ã‚¹ãŒä½œæˆãŠã‚ˆã³ç ´æ£„ã•ã‚Œã¾ã™ã€‚ã“ã®ã‚ˆã†ãªãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã¨ã€ã‚¯ãƒ©ã‚¦ãƒ‰ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã«é–¢é€£ã™ã‚‹è¿½åŠ 料金ãŒç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚作æˆã•ã‚ŒãŸãƒªã‚½ãƒ¼ã‚¹ãŒç¢ºå®Ÿã«å‰Šé™¤ã•ã‚Œã‚‹ã‚ˆã†ã«æ³¨æ„ãŒæ‰•ã‚ã‚Œã¾ã™ã€‚ãŸã ã—ã€AWS コンソールを調ã¹ã¦ã€äºˆæœŸã—ãªã„リソースãŒå®Ÿè¡Œã—ã¦ã„ãªã„ã“ã¨ã‚’確èªã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" @@ -13566,31 +13573,31 @@ msgid "Code coverage reports make it easy to identify untested code for which mo msgstr "コードã®å¯¾è±¡ç¯„囲レãƒãƒ¼ãƒˆã¯ã€ã‚ˆã‚Šå¤šãã®ãƒ†ã‚¹ãƒˆãŒè¨˜è¿°ã•ã‚Œã‚‹ã¹ã未テストã®ã‚³ãƒ¼ãƒ‰ã‚’ç°¡å˜ã«è˜åˆ¥ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚オンラインレãƒãƒ¼ãƒˆãŒåˆ©ç”¨ã§ãã¾ã™ãŒã€``devel`` ブランãƒã®ã¿ã‚’扱ã„ã¾ã™ (:ref:`developing_testing` ã‚’å‚ç…§)。新è¦ã‚³ãƒ¼ãƒ‰ã®ãƒãƒ¼ã‚«ãƒ«ãƒ¬ãƒãƒ¼ãƒˆãŒå¿…è¦ãªå ´åˆã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" #: ../../rst/dev_guide/testing_running_locally.rst:70 -msgid "Add the ``--coverage`` option to any test command to collect code coverage data. If you aren't using the ``--venv`` or ``--docker`` options which create an isolated python environment then you may have to use the ``--requirements`` option to ensure that the correct version of the coverage module is installed::" +msgid "Add the ``--coverage`` option to any test command to collect code coverage data. If you aren't using the ``--venv`` or ``--docker`` options which create an isolated python environment then you may have to use the ``--requirements`` option to ensure that the correct version of the coverage module is installed:" msgstr "コードカãƒãƒ¬ãƒƒã‚¸ãƒ‡ãƒ¼ã‚¿ã‚’åŽé›†ã™ã‚‹ãƒ†ã‚¹ãƒˆã‚³ãƒžãƒ³ãƒ‰ã« ``--coverage`` ã‚ªãƒ—ã‚·ãƒ§ãƒ³ã‚’è¿½åŠ ã—ã¾ã™ã€‚分離ã—㟠python 環境を作æˆã™ã‚‹ ``--venv`` オプションã¾ãŸã¯ ``--docker`` オプションを使用ã—ã¦ã„ãªã„å ´åˆã¯ã€``--requirements`` オプションを使用ã—ã¦ã‚«ãƒãƒ¬ãƒƒã‚¸ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®æ£ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_running_locally.rst:81 -#: ../../rst/dev_guide/testing_units.rst:191 +#: ../../rst/dev_guide/testing_running_locally.rst:83 +#: ../../rst/dev_guide/testing_units.rst:197 msgid "Reports can be generated in several different formats:" msgstr "Report ã¯ã€è¤‡æ•°ã®å½¢å¼ã§ç”Ÿæˆã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_running_locally.rst:83 -#: ../../rst/dev_guide/testing_units.rst:193 +#: ../../rst/dev_guide/testing_running_locally.rst:85 +#: ../../rst/dev_guide/testing_units.rst:199 msgid "``ansible-test coverage report`` - Console report." msgstr "``ansible-test coverage report`` - コンソールレãƒãƒ¼ãƒˆã€‚" -#: ../../rst/dev_guide/testing_running_locally.rst:84 -#: ../../rst/dev_guide/testing_units.rst:194 +#: ../../rst/dev_guide/testing_running_locally.rst:86 +#: ../../rst/dev_guide/testing_units.rst:200 msgid "``ansible-test coverage html`` - HTML report." msgstr "``ansible-test coverage html`` - HTML レãƒãƒ¼ãƒˆã€‚" -#: ../../rst/dev_guide/testing_running_locally.rst:85 -#: ../../rst/dev_guide/testing_units.rst:195 +#: ../../rst/dev_guide/testing_running_locally.rst:87 +#: ../../rst/dev_guide/testing_units.rst:201 msgid "``ansible-test coverage xml`` - XML report." msgstr "``ansible-test coverage xml`` - XML レãƒãƒ¼ãƒˆã€‚" -#: ../../rst/dev_guide/testing_running_locally.rst:87 -msgid "To clear data between test runs, use the ``ansible-test coverage erase`` command. For a full list of features see the online help::" +#: ../../rst/dev_guide/testing_running_locally.rst:89 +msgid "To clear data between test runs, use the ``ansible-test coverage erase`` command. For a full list of features see the online help:" msgstr "テスト実行間ã®ãƒ‡ãƒ¼ã‚¿ã‚’消去ã™ã‚‹ã«ã¯ã€``ansible-test coverage erase`` コマンドを使用ã—ã¾ã™ã€‚機能ã®å…¨ä¸€è¦§ã«ã¤ã„ã¦ã¯ã€ã‚ªãƒ³ãƒ©ã‚¤ãƒ³ãƒ˜ãƒ«ãƒ—ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" #: ../../rst/dev_guide/testing_sanity.rst:11 @@ -13651,166 +13658,166 @@ msgid "If you are running unit tests against things other than modules, such as msgstr "モジュールユーティリティーãªã©ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ä»¥å¤–ã®ã‚‚ã®ã«å¯¾ã—ã¦ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã‚’実行ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒ•ã‚¡ã‚¤ãƒ«ãƒ‘ス全体を指定ã—ã¾ã™ã€‚" #: ../../rst/dev_guide/testing_units.rst:56 -msgid "For advanced usage see the online help::" +msgid "For advanced usage see the online help:" msgstr "高度ãªä½¿ç”¨æ–¹æ³•ã¯ã€ã‚ªãƒ³ãƒ©ã‚¤ãƒ³ãƒ˜ãƒ«ãƒ—ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/testing_units.rst:60 +#: ../../rst/dev_guide/testing_units.rst:62 msgid "You can also run tests in Ansible's continuous integration system by opening a pull request. This will automatically determine which tests to run based on the changes made in your pull request." msgstr "プルè¦æ±‚ã‚’é–‹ã„ã¦ã€Ansible ã®ç¶™ç¶šçš„çµ±åˆã‚·ã‚¹ãƒ†ãƒ ã§ãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ãƒ—ルè¦æ±‚ã§å®Ÿè¡Œã•ã‚ŒãŸå¤‰æ›´ã«åŸºã¥ã„ã¦ã€å®Ÿè¡Œã•ã‚Œã‚‹ãƒ†ã‚¹ãƒˆãŒè‡ªå‹•çš„ã«æ±ºå®šã•ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:68 +#: ../../rst/dev_guide/testing_units.rst:70 msgid "If you are running ``ansible-test`` with the ``--docker`` or ``--venv`` option you do not need to install dependencies manually." msgstr "``--docker`` オプションã¾ãŸã¯ ``--venv`` オプションを指定ã—㦠``ansible-test`` を実行ã—ã¦ã„ã‚‹å ´åˆã¯ã€ä¾å˜é–¢ä¿‚を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã™ã‚‹å¿…è¦ã¯ã‚ã‚Šã¾ã›ã‚“。" -#: ../../rst/dev_guide/testing_units.rst:70 +#: ../../rst/dev_guide/testing_units.rst:72 msgid "Otherwise you can install dependencies using the ``--requirements`` option, which will install all the required dependencies needed for unit tests. For example:" msgstr "ãれ以外ã®å ´åˆã¯ã€``--requirements`` オプションを使用ã—ã¦ä¾å˜é–¢ä¿‚をインストールã—ã€ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã«å¿…è¦ãªä¾å˜é–¢ä¿‚ã‚’ã™ã¹ã¦ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:78 +#: ../../rst/dev_guide/testing_units.rst:80 msgid "The list of unit test requirements can be found at `test/units/requirements.txt <https://github.com/ansible/ansible/tree/devel/test/units/requirements.txt>`_." msgstr "ユニットテストã®è¦ä»¶ä¸€è¦§ã¯ã€`test/units/requirements.txt <https://github.com/ansible/ansible/tree/devel/test/units/requirements.txt>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/testing_units.rst:81 +#: ../../rst/dev_guide/testing_units.rst:83 msgid "This does not include the list of unit test requirements for ``ansible-test`` itself, which can be found at `test/lib/ansible_test/_data/requirements/units.txt <https://github.com/ansible/ansible/tree/devel/test/lib/ansible_test/_data/requirements/units.txt>`_." msgstr "ã“ã‚Œã«ã¯ã€``ansible-test`` ã®ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆè¦ä»¶ã®ãƒªã‚¹ãƒˆã¯å«ã¾ã‚Œã¦ã„ã¾ã›ã‚“。ãã‚Œã¯ã€`test/lib/ansible_test/_data/requirements/units.txt <https://github.com/ansible/ansible/tree/devel/test/lib/ansible_test/_data/requirements/units.txt>`_ ã§è¦‹ã¤ã‘ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:85 +#: ../../rst/dev_guide/testing_units.rst:87 msgid "See also the `constraints <https://github.com/ansible/ansible/blob/devel/test/lib/ansible_test/_data/requirements/constraints.txt>`_ applicable to all test commands." msgstr "ã™ã¹ã¦ã®ã‚³ãƒžãƒ³ãƒ‰ã«é©ç”¨å¯èƒ½ãªã€Œ`制約 <https://github.com/ansible/ansible/blob/devel/test/lib/ansible_test/_data/requirements/constraints.txt>`_ã€ã‚‚å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/testing_units.rst:91 +#: ../../rst/dev_guide/testing_units.rst:93 msgid "Extending unit tests" msgstr "ユニットテストã®æ‹¡å¼µ" -#: ../../rst/dev_guide/testing_units.rst:94 +#: ../../rst/dev_guide/testing_units.rst:96 msgid "What a unit test isn't" msgstr "ユニットテスト以外ã®ã‚‚ã®" -#: ../../rst/dev_guide/testing_units.rst:96 +#: ../../rst/dev_guide/testing_units.rst:98 msgid "If you start writing a test that requires external services then you may be writing an integration test, rather than a unit test." msgstr "外部サービスを必è¦ã¨ã™ã‚‹ãƒ†ã‚¹ãƒˆã‚’書ã始ã‚ã‚‹ã¨ã€ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã§ã¯ãªãçµ±åˆãƒ†ã‚¹ãƒˆã‚’書ãã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:101 +#: ../../rst/dev_guide/testing_units.rst:103 msgid "Structuring Unit Tests" msgstr "ユニットテストã®æ§‹é€ " -#: ../../rst/dev_guide/testing_units.rst:103 +#: ../../rst/dev_guide/testing_units.rst:105 msgid "Ansible drives unit tests through `pytest <https://docs.pytest.org/en/latest/>`_. This means that tests can either be written a simple functions which are included in any file name like ``test_<something>.py`` or as classes." msgstr "Ansible ã¯ã€`pytest <https://docs.pytest.org/en/latest/>`_ ã§ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã‚’è¡Œã„ã¾ã™ã€‚ã“ã‚Œã¯ã€ãƒ†ã‚¹ãƒˆã¯ã€``test_<something>.py`` ã®ãƒ•ã‚¡ã‚¤ãƒ«åã¾ãŸã¯ã‚¯ãƒ©ã‚¹ã¨ã—ã¦å«ã¾ã‚Œã‚‹å˜ç´”ãªé–¢æ•°ã‚’記述ã§ãã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:107 -msgid "Here is an example of a function::" +#: ../../rst/dev_guide/testing_units.rst:109 +msgid "Here is an example of a function:" msgstr "以下ã¯ã€é–¢æ•°ã®ä¾‹ã§ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:117 -msgid "Here is an example of a class::" +#: ../../rst/dev_guide/testing_units.rst:121 +msgid "Here is an example of a class:" msgstr "以下ã¯ã‚¯ãƒ©ã‚¹ã®ä¾‹ã§ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:137 +#: ../../rst/dev_guide/testing_units.rst:143 msgid "Both methods work fine in most circumstances; the function-based interface is simpler and quicker and so that's probably where you should start when you are just trying to add a few basic tests for a module. The class-based test allows more tidy set up and tear down of pre-requisites, so if you have many test cases for your module you may want to refactor to use that." msgstr "ã©ã¡ã‚‰ã®æ–¹æ³•ã‚‚ã€ã»ã¨ã‚“ã©ã®çŠ¶æ³ã§æ£å¸¸ã«æ©Ÿèƒ½ã—ã¾ã™ã€‚関数ベースã®ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ã®æ–¹ãŒã‚·ãƒ³ãƒ—ルã§é€Ÿã„ãŸã‚ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã„ãã¤ã‹ã®åŸºæœ¬çš„ãªãƒ†ã‚¹ãƒˆã‚’è¿½åŠ ã—よã†ã¨ã—ã¦ã„ã‚‹å ´åˆã¯ã€ã“ã“ã‹ã‚‰å§‹ã‚ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚クラスベースã®ãƒ†ã‚¹ãƒˆã§ã¯ã€å‰ææ¡ä»¶ã®è¨å®šã‚„分解をより整然ã¨è¡Œã†ã“ã¨ãŒã§ãã‚‹ãŸã‚ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«å¤šãã®ãƒ†ã‚¹ãƒˆã‚±ãƒ¼ã‚¹ãŒã‚ã‚‹å ´åˆã¯ã€ãれを使用ã™ã‚‹ã‚ˆã†ã«ãƒªãƒ•ã‚¡ã‚¯ã‚¿ãƒªãƒ³ã‚°ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:143 +#: ../../rst/dev_guide/testing_units.rst:149 msgid "Assertions using the simple ``assert`` function inside the tests will give full information on the cause of the failure with a trace-back of functions called during the assertion. This means that plain asserts are recommended over other external assertion libraries." msgstr "テスト内ã®ç°¡å˜ãª ``assert`` 関数を使用ã™ã‚‹ã‚¢ã‚µãƒ¼ã‚·ãƒ§ãƒ³ã«ã‚ˆã‚Šã€ã‚¢ã‚µãƒ¼ã‚·ãƒ§ãƒ³ä¸ã«å‘¼ã³å‡ºã•ã‚Œã‚‹é–¢æ•°ã®ãƒˆãƒ¬ãƒ¼ã‚¹ãƒãƒƒã‚¯ã§éšœå®³ã«é–¢ã™ã‚‹å®Œå…¨ãªæƒ…å ±ãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ã€ä»–ã®å¤–部アサーションライブラリーよりもã€ãƒ—レーンアサートãŒæŽ¨å¥¨ã•ã‚Œã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:148 +#: ../../rst/dev_guide/testing_units.rst:154 msgid "A number of the unit test suites include functions that are shared between several modules, especially in the networking arena. In these cases a file is created in the same directory, which is then included directly." msgstr "多ãã®ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã‚¹ã‚¤ãƒ¼ãƒˆã«ã¯ã€ç‰¹ã«ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã®åˆ†é‡Žã§ã¯ã€è¤‡æ•°ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã§å…±æœ‰ã•ã‚Œã‚‹é–¢æ•°ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ã“ã®å ´åˆã¯ã€åŒã˜ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ãƒ•ã‚¡ã‚¤ãƒ«ãŒä½œæˆã•ã‚Œã¾ã™ã€‚ã“ã®ãƒ•ã‚¡ã‚¤ãƒ«ã¯ã€ç›´æŽ¥å«ã¾ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:154 +#: ../../rst/dev_guide/testing_units.rst:160 msgid "Module test case common code" msgstr "モジュールテストケースã®å…±é€šã‚³ãƒ¼ãƒ‰" -#: ../../rst/dev_guide/testing_units.rst:156 +#: ../../rst/dev_guide/testing_units.rst:162 msgid "Keep common code as specific as possible within the `test/units/` directory structure. Don't import common unit test code from directories outside the current or parent directories." msgstr "`test/units/` ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼æ§‹é€ å†…ã§å¯èƒ½ãªé™ã‚Šå…·ä½“çš„ã«å…±é€šã‚³ãƒ¼ãƒ‰ã‚’ç¶æŒã—ã¾ã™ã€‚ç¾åœ¨ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã¾ãŸã¯è¦ªãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ä»¥å¤–ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã‹ã‚‰å…±é€šã®ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã‚³ãƒ¼ãƒ‰ã‚’インãƒãƒ¼ãƒˆã—ãªã„ã§ãã ã•ã„。" -#: ../../rst/dev_guide/testing_units.rst:159 +#: ../../rst/dev_guide/testing_units.rst:165 msgid "Don't import other unit tests from a unit test. Any common code should be in dedicated files that aren't themselves tests." msgstr "ユニットテストã‹ã‚‰ä»–ã®ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã‚’インãƒãƒ¼ãƒˆã—ãªã„ã§ãã ã•ã„。共通ã®ã‚³ãƒ¼ãƒ‰ã¯ã€ãƒ†ã‚¹ãƒˆè‡ªä½“ã§ã¯ãªã„専用ã®ãƒ•ã‚¡ã‚¤ãƒ«ã«å«ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:164 +#: ../../rst/dev_guide/testing_units.rst:170 msgid "Fixtures files" msgstr "Fixtures ファイル" -#: ../../rst/dev_guide/testing_units.rst:166 +#: ../../rst/dev_guide/testing_units.rst:172 msgid "To mock out fetching results from devices, or provide other complex data structures that come from external libraries, you can use ``fixtures`` to read in pre-generated data." msgstr "デãƒã‚¤ã‚¹ã‹ã‚‰ã®çµæžœã®å–得を模倣ã—ãŸã‚Šã€å¤–部ライブラリーã‹ã‚‰å–å¾—ã—ãŸä»–ã®è¤‡é›‘ãªãƒ‡ãƒ¼ã‚¿æ§‹é€ ã‚’æä¾›ã™ã‚‹ãŸã‚ã«ã€``fixtures`` を使用ã—ã¦äº‹å‰ã«ç”Ÿæˆã•ã‚ŒãŸãƒ‡ãƒ¼ã‚¿ã‚’èªã¿è¾¼ã‚€ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:169 +#: ../../rst/dev_guide/testing_units.rst:175 msgid "You can check how `fixtures <https://github.com/ansible/ansible/tree/devel/test/units/module_utils/facts/fixtures/cpuinfo>`_ are used in `cpuinfo fact tests <https://github.com/ansible/ansible/blob/9f72ff80e3fe173baac83d74748ad87cb6e20e64/test/units/module_utils/facts/hardware/linux_data.py#L384>`_" msgstr "`cpuinfo ファクトテスト <https://github.com/ansible/ansible/blob/9f72ff80e3fe173baac83d74748ad87cb6e20e64/test/units/module_utils/facts/hardware/linux_data.py#L384>`_ ã§ã€`fixtures <https://github.com/ansible/ansible/tree/devel/test/units/module_utils/facts/fixtures/cpuinfo>`_ ãŒä½¿ç”¨ã•ã‚Œã‚‹æ–¹æ³•ã‚’確èªã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:172 +#: ../../rst/dev_guide/testing_units.rst:178 msgid "If you are simulating APIs you may find that Python placebo is useful. See :ref:`testing_units_modules` for more information." msgstr "API ã®ã‚·ãƒŸãƒ¥ãƒ¬ãƒ¼ã‚·ãƒ§ãƒ³ã‚’ã—ã¦ã„ã‚‹ã®ã§ã‚ã‚Œã°ã€Python ã®ãƒ—ラシーボãŒå½¹ã«ç«‹ã¤ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“。詳細ã¯ã€ã€Œ:ref:`testing_units_modules`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/testing_units.rst:177 +#: ../../rst/dev_guide/testing_units.rst:183 msgid "Code Coverage For New or Updated Unit Tests" msgstr "æ–°è¦ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã¾ãŸã¯æ›´æ–°ã•ã‚ŒãŸãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆç”¨ã®ã‚³ãƒ¼ãƒ‰å¯¾å¿œ" -#: ../../rst/dev_guide/testing_units.rst:178 +#: ../../rst/dev_guide/testing_units.rst:184 msgid "New code will be missing from the codecov.io coverage reports (see :ref:`developing_testing`), so local reporting is needed. Most ``ansible-test`` commands allow you to collect code coverage; this is particularly useful when to indicate where to extend testing." msgstr "codecov.io ã‚«ãƒãƒ¬ãƒƒã‚¸ãƒ¬ãƒãƒ¼ãƒˆã‹ã‚‰æ–°ã—ã„コードãŒæ¬ è½ã— (:ref:`developing_testing`ã‚’å‚ç…§)ã€ãƒãƒ¼ã‚«ãƒ«ãƒ¬ãƒãƒ¼ãƒˆãŒå¿…è¦ã§ã™ã€‚ã»ã¨ã‚“ã©ã® ``ansible-test`` コマンドを使用ã™ã‚‹ã¨ã€ã‚³ãƒ¼ãƒ‰ã‚«ãƒãƒ¬ãƒƒã‚¸ã‚’åŽé›†ã§ãã¾ã™ã€‚ã“ã‚Œã¯ã€ãƒ†ã‚¹ãƒˆã‚’æ‹¡å¼µã™ã‚‹å ´æ‰€ã‚’示ã™ã¨ãã«ç‰¹ã«å½¹ç«‹ã¡ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:182 +#: ../../rst/dev_guide/testing_units.rst:188 msgid "To collect coverage data add the ``--coverage`` argument to your ``ansible-test`` command line:" msgstr "ã‚«ãƒãƒ¬ãƒ¼ã‚¸ãƒ‡ãƒ¼ã‚¿ã‚’åŽé›†ã™ã‚‹ã«ã¯ã€``--coverage`` 引数を ``ansible-test`` コマンドラインã«è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:189 +#: ../../rst/dev_guide/testing_units.rst:195 msgid "Results will be written to ``test/results/reports/coverage/index.html``" msgstr "çµæžœã¯ ``test/results/reports/coverage/index.html`` ã«æ›¸ãè¾¼ã¾ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units.rst:197 +#: ../../rst/dev_guide/testing_units.rst:203 msgid "To clear data between test runs, use the ``ansible-test coverage erase`` command. See :ref:`testing_running_locally` for more information about generating coverage reports." msgstr "テスト実行間ã®ãƒ‡ãƒ¼ã‚¿ã‚’消去ã™ã‚‹ã«ã¯ã€``ansible-test coverage erase`` コマンドを使用ã—ã¾ã™ã€‚ã‚«ãƒãƒ¬ãƒƒã‚¸ãƒ¬ãƒãƒ¼ãƒˆã®ç”Ÿæˆã®è©³ç´°ã¯ã€ã€Œ:ref:`testing_running_locally`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/testing_units.rst:204 +#: ../../rst/dev_guide/testing_units.rst:210 msgid ":ref:`testing_units_modules`" msgstr ":ref:`testing_units_modules`" -#: ../../rst/dev_guide/testing_units.rst:205 +#: ../../rst/dev_guide/testing_units.rst:211 msgid "Special considerations for unit testing modules" msgstr "ユニットテストモジュールã«é–¢ã™ã‚‹ç‰¹åˆ¥ãªè€ƒæ…®äº‹é …" -#: ../../rst/dev_guide/testing_units.rst:206 -#: ../../rst/dev_guide/testing_units_modules.rst:543 +#: ../../rst/dev_guide/testing_units.rst:212 +#: ../../rst/dev_guide/testing_units_modules.rst:569 msgid ":ref:`testing_running_locally`" msgstr ":ref:`testing_running_locally`" -#: ../../rst/dev_guide/testing_units.rst:207 -#: ../../rst/dev_guide/testing_units_modules.rst:544 +#: ../../rst/dev_guide/testing_units.rst:213 +#: ../../rst/dev_guide/testing_units_modules.rst:570 msgid "Running tests locally including gathering and reporting coverage data" msgstr "ã‚«ãƒãƒ¬ãƒ¼ã‚¸ãƒ‡ãƒ¼ã‚¿ã®åŽé›†ã¨ãƒ¬ãƒãƒ¼ãƒˆã‚’å«ã‚€ã€ãƒãƒ¼ã‚«ãƒ«ã§ã®ãƒ†ã‚¹ãƒˆã®å®Ÿè¡Œ" -#: ../../rst/dev_guide/testing_units.rst:208 -#: ../../rst/dev_guide/testing_units_modules.rst:547 +#: ../../rst/dev_guide/testing_units.rst:214 +#: ../../rst/dev_guide/testing_units_modules.rst:573 msgid "`Python 3 documentation - 26.4. unittest — Unit testing framework <https://docs.python.org/3/library/unittest.html>`_" msgstr "`Python 3 documentation - 26.4. unittest — Unit testing framework <https://docs.python.org/3/library/unittest.html>`_" -#: ../../rst/dev_guide/testing_units.rst:209 -#: ../../rst/dev_guide/testing_units_modules.rst:548 +#: ../../rst/dev_guide/testing_units.rst:215 +#: ../../rst/dev_guide/testing_units_modules.rst:574 msgid "The documentation of the unittest framework in python 3" msgstr "Python 3 ã«ãŠã‘るユニットテストフレームワークã®ãƒ‰ã‚ュメント" -#: ../../rst/dev_guide/testing_units.rst:210 -#: ../../rst/dev_guide/testing_units_modules.rst:549 +#: ../../rst/dev_guide/testing_units.rst:216 +#: ../../rst/dev_guide/testing_units_modules.rst:575 msgid "`Python 2 documentation - 25.3. unittest — Unit testing framework <https://docs.python.org/3/library/unittest.html>`_" msgstr "`Python 2 documentation - 25.3. unittest — Unit testing framework <https://docs.python.org/3/library/unittest.html>`_" -#: ../../rst/dev_guide/testing_units.rst:211 -#: ../../rst/dev_guide/testing_units_modules.rst:550 +#: ../../rst/dev_guide/testing_units.rst:217 +#: ../../rst/dev_guide/testing_units_modules.rst:576 msgid "The documentation of the earliest supported unittest framework - from Python 2.6" msgstr "サãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã‚‹åˆæœŸã®ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆãƒ•ãƒ¬ãƒ¼ãƒ ワークã®ãƒ‰ã‚ュメント (Python 2.6)" -#: ../../rst/dev_guide/testing_units.rst:212 -#: ../../rst/dev_guide/testing_units_modules.rst:551 +#: ../../rst/dev_guide/testing_units.rst:218 +#: ../../rst/dev_guide/testing_units_modules.rst:577 msgid "`pytest: helps you write better programs <https://docs.pytest.org/en/latest/>`_" msgstr "`pytest: helps you write better programs <https://docs.pytest.org/en/latest/>`_" -#: ../../rst/dev_guide/testing_units.rst:213 -#: ../../rst/dev_guide/testing_units_modules.rst:552 +#: ../../rst/dev_guide/testing_units.rst:219 +#: ../../rst/dev_guide/testing_units_modules.rst:578 msgid "The documentation of pytest - the framework actually used to run Ansible unit tests" msgstr "pytest ã®ãƒ‰ã‚ュメント - Ansible ユニットテストã®å®Ÿè¡Œã«å®Ÿéš›ã«ä½¿ç”¨ã•ã‚Œã¦ã„るフレームワーク" @@ -13967,226 +13974,226 @@ msgid "Ensuring failure cases are visible with mock objects" msgstr "モックオブジェクトã§éšœå®³ã‚±ãƒ¼ã‚¹ã‚’確実ã«å¯è¦–化" #: ../../rst/dev_guide/testing_units_modules.rst:168 -msgid "Functions like :meth:`module.fail_json` are normally expected to terminate execution. When you run with a mock module object this doesn't happen since the mock always returns another mock from a function call. You can set up the mock to raise an exception as shown above, or you can assert that these functions have not been called in each test. For example::" +msgid "Functions like :meth:`module.fail_json` are normally expected to terminate execution. When you run with a mock module object this doesn't happen since the mock always returns another mock from a function call. You can set up the mock to raise an exception as shown above, or you can assert that these functions have not been called in each test. For example:" msgstr ":meth:`module.fail_json` ãªã©ã®é–¢æ•°ã¯ã€é€šå¸¸ã€å®Ÿè¡Œã‚’終了ã™ã‚‹ã“ã¨ãŒæœŸå¾…ã•ã‚Œã¾ã™ã€‚モックモジュールオブジェクトを使用ã—ã¦å®Ÿè¡Œã™ã‚‹ã¨ã€ãƒ¢ãƒƒã‚¯ã¯å¸¸ã«é–¢æ•°å‘¼ã³å‡ºã—ã‹ã‚‰åˆ¥ã®ãƒ¢ãƒƒã‚¯ã‚’è¿”ã™ãŸã‚ã€ã“ã®ã‚ˆã†ãªã“ã¨ã¯èµ·ã“ã‚Šã¾ã›ã‚“。上記ã®ã‚ˆã†ã«ä¾‹å¤–を発生ã•ã›ã‚‹ã‚ˆã†ã«ãƒ¢ãƒƒã‚¯ã‚’è¨å®šã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã—ã€å„テストã§ã“れらã®é–¢æ•°ãŒå‘¼ã³å‡ºã•ã‚Œã¦ã„ãªã„ã“ã¨ã‚’アサートã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:177 +#: ../../rst/dev_guide/testing_units_modules.rst:179 msgid "This applies not only to calling the main module but almost any other function in a module which gets the module object." msgstr "ã“ã‚Œã¯ã€ãƒ¡ã‚¤ãƒ³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’呼ã³å‡ºã™å ´åˆã ã‘ã§ãªãã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚ªãƒ–ジェクトをå–å¾—ã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«å†…ã®ä»–ã®ã»ã¨ã‚“ã©ã®é–¢æ•°ã‚’呼ã³å‡ºã™å ´åˆã«ã‚‚é©ç”¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:182 +#: ../../rst/dev_guide/testing_units_modules.rst:184 msgid "Mocking of the actual module" msgstr "実際ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ¢ãƒƒã‚¯åŒ–" -#: ../../rst/dev_guide/testing_units_modules.rst:184 -msgid "The setup of an actual module is quite complex (see `Passing Arguments`_ below) and often isn't needed for most functions which use a module. Instead you can use a mock object as the module and create any module attributes needed by the function you are testing. If you do this, beware that the module exit functions need special handling as mentioned above, either by throwing an exception or ensuring that they haven't been called. For example::" -msgstr "実際ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®è¨å®šã¯éžå¸¸ã«è¤‡é›‘㧠(以下㮠`Passing Arguments`_ ã‚’å‚ç…§)ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã™ã‚‹ã»ã¨ã‚“ã©ã®æ©Ÿèƒ½ã«ã¯å¿…è¦ã‚ã‚Šã¾ã›ã‚“。モックオブジェクトをモジュールã¨ã—ã¦ä½¿ç”¨ã™ã‚‹ä»£ã‚ã‚Šã«ã€ãƒ†ã‚¹ãƒˆã™ã‚‹é–¢æ•°ã§å¿…è¦ãªãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«å±žæ€§ã‚’作æˆã§ãã¾ã™ã€‚ã“ã®å ´åˆã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®çµ‚了関数ã¯ã€ä¸Šè¿°ã®ã‚ˆã†ã«ã€ä¾‹å¤–を発生ã•ã›ã‚‹ã‹ã€å‘¼ã³å‡ºã•ã‚Œã¦ã„ãªã„ã“ã¨ã‚’確èªã™ã‚‹ãªã©ã€ç‰¹åˆ¥ãªå‡¦ç†ãŒå¿…è¦ã«ãªã‚‹ã“ã¨ã«æ³¨æ„ã—ã¦ãã ã•ã„。以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" +#: ../../rst/dev_guide/testing_units_modules.rst:186 +msgid "The setup of an actual module is quite complex (see `Passing Arguments`_ below) and often isn't needed for most functions which use a module. Instead you can use a mock object as the module and create any module attributes needed by the function you are testing. If you do this, beware that the module exit functions need special handling as mentioned above, either by throwing an exception or ensuring that they haven't been called. For example:" +msgstr "実際ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®è¨å®šã¯éžå¸¸ã«è¤‡é›‘㧠(以下㮠`引数ã®æ¸¡ã—æ–¹`_ ã‚’å‚ç…§)ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã™ã‚‹ã»ã¨ã‚“ã©ã®æ©Ÿèƒ½ã«ã¯å¿…è¦ã‚ã‚Šã¾ã›ã‚“。モックオブジェクトをモジュールã¨ã—ã¦ä½¿ç”¨ã™ã‚‹ä»£ã‚ã‚Šã«ã€ãƒ†ã‚¹ãƒˆã™ã‚‹é–¢æ•°ã§å¿…è¦ãªãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«å±žæ€§ã‚’作æˆã§ãã¾ã™ã€‚ã“ã®å ´åˆã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®çµ‚了関数ã¯ã€ä¸Šè¿°ã®ã‚ˆã†ã«ã€ä¾‹å¤–を発生ã•ã›ã‚‹ã‹ã€å‘¼ã³å‡ºã•ã‚Œã¦ã„ãªã„ã“ã¨ã‚’確èªã™ã‚‹ãªã©ã€ç‰¹åˆ¥ãªå‡¦ç†ãŒå¿…è¦ã«ãªã‚‹ã“ã¨ã«æ³¨æ„ã—ã¦ãã ã•ã„。以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:203 +#: ../../rst/dev_guide/testing_units_modules.rst:207 msgid "API definition with unit test cases" msgstr "ユニットテストケースã§ã® API 定義" -#: ../../rst/dev_guide/testing_units_modules.rst:205 +#: ../../rst/dev_guide/testing_units_modules.rst:209 msgid "API interaction is usually best tested with the function tests defined in Ansible's integration testing section, which run against the actual API. There are several cases where the unit tests are likely to work better." msgstr "API ã®å¯¾è©±ã¯é€šå¸¸ã€å®Ÿéš›ã® API ã«å¯¾ã—ã¦å®Ÿè¡Œã™ã‚‹ Ansible ã®çµ±åˆãƒ†ã‚¹ãƒˆã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§å®šç¾©ã•ã‚ŒãŸé–¢æ•°ãƒ†ã‚¹ãƒˆã§ãƒ†ã‚¹ãƒˆã‚’è¡Œã†ã®ãŒæœ€é©ã§ã™ã€‚ユニットテストãŒé©åˆ‡ã«æ©Ÿèƒ½ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:210 +#: ../../rst/dev_guide/testing_units_modules.rst:214 msgid "Defining a module against an API specification" msgstr "API ã®ä»•æ§˜ã«å¯¾ã—ã¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’定義" -#: ../../rst/dev_guide/testing_units_modules.rst:212 +#: ../../rst/dev_guide/testing_units_modules.rst:216 msgid "This case is especially important for modules interacting with web services, which provide an API that Ansible uses but which are beyond the control of the user." msgstr "ã“ã®ã‚±ãƒ¼ã‚¹ã¯ã€Ansible ãŒä½¿ç”¨ã™ã‚‹ API ã‚’æä¾›ã—ã¦ã„ã‚‹ãŒã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ã®åˆ¶å¾¡ãŒåŠã°ãªã„ Web サービスã¨å¯¾è©±ã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã¨ã£ã¦ç‰¹ã«é‡è¦ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:215 +#: ../../rst/dev_guide/testing_units_modules.rst:219 msgid "By writing a custom emulation of the calls that return data from the API, we can ensure that only the features which are clearly defined in the specification of the API are present in the message. This means that we can check that we use the correct parameters and nothing else." msgstr "API ã‹ã‚‰ãƒ‡ãƒ¼ã‚¿ã‚’è¿”ã™å‘¼ã³å‡ºã—ã®ã‚«ã‚¹ã‚¿ãƒ エミュレーションを書ãã“ã¨ã§ã€API ã®ä»•æ§˜ã§æ˜Žç¢ºã«å®šç¾©ã•ã‚Œã¦ã„る機能ã®ã¿ãŒãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã«å«ã¾ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã§ãã¾ã™ã€‚ã¤ã¾ã‚Šã€æ£ã—ã„パラメーターを使用ã—ã¦ã„ã‚‹ã‹ã©ã†ã‹ã‚’確èªã—ã€ãれ以外ã¯ä½•ã‚‚使用ã—ã¦ã„ãªã„ã“ã¨ã‚’確èªã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:221 -msgid "*Example: in rds_instance unit tests a simple instance state is defined*::" -msgstr "*例: rds_instance ユニットテストã§ã¯ã€å˜ç´”ãªã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã®çŠ¶æ…‹ãŒå®šç¾©ã•ã‚Œã¦ã„ã¾ã™*::" +#: ../../rst/dev_guide/testing_units_modules.rst:225 +msgid "*Example: in rds_instance unit tests a simple instance state is defined*:" +msgstr "*例: rds_instance ユニットテストã§ã¯ã€å˜ç´”ãªã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã®çŠ¶æ…‹ãŒå®šç¾©ã•ã‚Œã¦ã„ã¾ã™*。" -#: ../../rst/dev_guide/testing_units_modules.rst:229 -msgid "This is then used to create a list of states::" +#: ../../rst/dev_guide/testing_units_modules.rst:235 +msgid "This is then used to create a list of states:" msgstr "次ã«ã€ã“れを使用ã—ã¦çŠ¶æ…‹ã®ãƒªã‚¹ãƒˆã‚’作æˆã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:244 -msgid "These states are then used as returns from a mock object to ensure that the ``await`` function waits through all of the states that would mean the RDS instance has not yet completed configuration::" +#: ../../rst/dev_guide/testing_units_modules.rst:252 +msgid "These states are then used as returns from a mock object to ensure that the ``await`` function waits through all of the states that would mean the RDS instance has not yet completed configuration:" msgstr "ã“れらã®çŠ¶æ…‹ã¯ã€ãƒ¢ãƒƒã‚¯ã‚ªãƒ–ジェクトã‹ã‚‰ã®æˆ»ã‚Šå€¤ã¨ã—ã¦ä½¿ç”¨ã•ã‚Œã€``await`` 関数ã¯ã€RDS インスタンスãŒã¾ã è¨å®šã‚’完了ã—ãªã„ã“ã¨ã‚’æ„味ã™ã‚‹ã™ã¹ã¦ã®çŠ¶æ…‹ã‚’å¾…æ©Ÿã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:252 +#: ../../rst/dev_guide/testing_units_modules.rst:262 msgid "By doing this we check that the ``await`` function will keep waiting through potentially unusual that it would be impossible to reliably trigger through the integration tests but which happen unpredictably in reality." msgstr "ã“れを実行ã™ã‚‹ã“ã¨ã§ã€çµ±åˆãƒ†ã‚¹ãƒˆã§ã¯ç¢ºå®Ÿã«èª˜ç™ºã•ã›ã‚‹ã“ã¨ãŒã§ããªã„ã«ã‚‚ã‹ã‹ã‚らãšã€ç¾å®Ÿã«ã¯äºˆæ¸¬ã§ããªã„よã†ãªã€æ½œåœ¨çš„ã«ç•°å¸¸ãªã“ã¨ãŒèµ·ã“ã‚‹å¯èƒ½æ€§ãŒã‚ã‚‹å ´åˆã« ``await`` 関数ãŒå¾…æ©Ÿã—続ã‘ã‚‹ã‹ã©ã†ã‹ã‚’確èªã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:257 +#: ../../rst/dev_guide/testing_units_modules.rst:267 msgid "Defining a module to work against multiple API versions" msgstr "複数㮠API ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«å¯¾ã—ã¦å‹•ä½œã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®å®šç¾©" -#: ../../rst/dev_guide/testing_units_modules.rst:259 +#: ../../rst/dev_guide/testing_units_modules.rst:269 msgid "This case is especially important for modules interacting with many different versions of software; for example, package installation modules that might be expected to work with many different operating system versions." msgstr "ã“ã®ã‚±ãƒ¼ã‚¹ã¯ã€å¤šãã®ç•°ãªã‚‹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ã¨å¯¾è©±ã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã¨ã£ã¦ç‰¹ã«é‡è¦ã§ã™ã€‚ãŸã¨ãˆã°ã€ã•ã¾ã–ã¾ãªã‚ªãƒšãƒ¬ãƒ¼ãƒ†ã‚£ãƒ³ã‚°ã‚·ã‚¹ãƒ†ãƒ ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¨å‹•ä½œã™ã‚‹ã“ã¨ãŒæƒ³å®šã•ã‚Œã‚‹ãƒ‘ッケージインストールモジュールãªã©ã§ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:263 +#: ../../rst/dev_guide/testing_units_modules.rst:273 msgid "By using previously stored data from various versions of an API we can ensure that the code is tested against the actual data which will be sent from that version of the system even when the version is very obscure and unlikely to be available during testing." msgstr "ã•ã¾ã–ã¾ãªãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® API ã‹ã‚‰ã€ä»¥å‰ã«ä¿å˜ã•ã‚ŒãŸãƒ‡ãƒ¼ã‚¿ã‚’使用ã™ã‚‹ã“ã¨ã§ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒéžå¸¸ã«æ›–昧ã§ãƒ†ã‚¹ãƒˆä¸ã«åˆ©ç”¨ã§ããã†ã«ãªã„å ´åˆã§ã‚‚ã€ãã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ã‚·ã‚¹ãƒ†ãƒ ã‹ã‚‰é€ä¿¡ã•ã‚Œã‚‹å®Ÿéš›ã®ãƒ‡ãƒ¼ã‚¿ã«å¯¾ã—ã¦ã‚³ãƒ¼ãƒ‰ãŒãƒ†ã‚¹ãƒˆã§ãるよã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:268 +#: ../../rst/dev_guide/testing_units_modules.rst:278 msgid "Ansible special cases for unit testing" msgstr "Ansible ユニットテストã®ç‰¹æ®Šãªã‚±ãƒ¼ã‚¹" -#: ../../rst/dev_guide/testing_units_modules.rst:270 +#: ../../rst/dev_guide/testing_units_modules.rst:280 msgid "There are a number of special cases for unit testing the environment of an Ansible module. The most common are documented below, and suggestions for others can be found by looking at the source code of the existing unit tests or asking on the Ansible chat channel or mailing lists. For more information on joining chat channels and subscribing to mailing lists, see :ref:`communication`." msgstr "Ansible モジュールã®ç’°å¢ƒã«å¯¾ã—ã¦ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã‚’è¡Œã†ãŸã‚ã®ç‰¹åˆ¥ãªã‚±ãƒ¼ã‚¹ãŒã„ãã¤ã‹ã‚ã‚Šã¾ã™ã€‚最も一般的ãªã‚‚ã®ã‚’以下ã«ç¤ºã—ã¾ã™ã€‚ä»–ã®äººã¸ã®æ案ã¯ã€æ—¢å˜ã®ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã®ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã‚’確èªã™ã‚‹ã‹ã€Ansible ãƒãƒ£ãƒƒãƒˆãƒãƒ£ãƒ³ãƒãƒ«ã¾ãŸã¯ãƒ¡ãƒ¼ãƒªãƒ³ã‚°ãƒªã‚¹ãƒˆã§è³ªå•ã™ã‚‹ã“ã¨ã§è¦‹ã¤ã‘ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãƒãƒ£ãƒƒãƒˆãƒãƒ£ãƒ³ãƒãƒ«ã¸ã®å‚åŠ ãŠã‚ˆã³ãƒ¡ãƒ¼ãƒªãƒ³ã‚°ãƒªã‚¹ãƒˆã®ã‚µãƒ–スクライブã®è©³ç´°ã«ã¤ã„ã¦ã¯ã€:ref:`communication`ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/testing_units_modules.rst:276 +#: ../../rst/dev_guide/testing_units_modules.rst:286 msgid "Module argument processing" msgstr "モジュール引数処ç†" -#: ../../rst/dev_guide/testing_units_modules.rst:278 +#: ../../rst/dev_guide/testing_units_modules.rst:288 msgid "There are two problems with running the main function of a module:" msgstr "モジュールã®ä¸»ãªé–¢æ•°ã®å®Ÿè¡Œã«ã¯ã€ä»¥ä¸‹ã® 2 ã¤ã®å•é¡ŒãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:280 +#: ../../rst/dev_guide/testing_units_modules.rst:290 msgid "Since the module is supposed to accept arguments on ``STDIN`` it is a bit difficult to set up the arguments correctly so that the module will get them as parameters." msgstr "モジュール㯠``STDIN`` ã§å¼•æ•°ã‚’å—ã‘入れる必è¦ãŒã‚ã‚‹ãŸã‚ã€å¼•æ•°ã‚’æ£ã—ãè¨å®šã—ã¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒãƒ‘ラメーターã¨ã—ã¦å—ã‘å–るよã†ã«ã™ã‚‹ã®ã¯å°‘ã—難ã—ããªã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:282 +#: ../../rst/dev_guide/testing_units_modules.rst:292 msgid "All modules should finish by calling either the :meth:`module.fail_json` or :meth:`module.exit_json`, but these won't work correctly in a testing environment." msgstr "ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€:meth:`module.fail_json` ã¾ãŸã¯ :meth:`module.exit_json` を呼ã³å‡ºã—ã¦çµ‚了ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ãŒã€ãƒ†ã‚¹ãƒˆç’°å¢ƒã§ã¯æ£å¸¸ã«å‹•ä½œã—ã¾ã›ã‚“。" -#: ../../rst/dev_guide/testing_units_modules.rst:286 +#: ../../rst/dev_guide/testing_units_modules.rst:296 msgid "Passing Arguments" msgstr "引数ã®æ¸¡ã—æ–¹" -#: ../../rst/dev_guide/testing_units_modules.rst:291 -msgid "To pass arguments to a module correctly, use the ``set_module_args`` method which accepts a dictionary as its parameter. Module creation and argument processing is handled through the :class:`AnsibleModule` object in the basic section of the utilities. Normally this accepts input on ``STDIN``, which is not convenient for unit testing. When the special variable is set it will be treated as if the input came on ``STDIN`` to the module. Simply call that function before setting up your module::" +#: ../../rst/dev_guide/testing_units_modules.rst:301 +msgid "To pass arguments to a module correctly, use the ``set_module_args`` method which accepts a dictionary as its parameter. Module creation and argument processing is handled through the :class:`AnsibleModule` object in the basic section of the utilities. Normally this accepts input on ``STDIN``, which is not convenient for unit testing. When the special variable is set it will be treated as if the input came on ``STDIN`` to the module. Simply call that function before setting up your module:" msgstr "モジュールã«æ£ã—ã引数を渡ã™ã«ã¯ã€ãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼ã‚’パラメーターã¨ã—ã¦å—ã‘付ã‘ã‚‹ ``set_module_args`` メソッドを使用ã—ã¾ã™ã€‚モジュールã®ä½œæˆã¨å¼•æ•°ã®å‡¦ç†ã¯ã€ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ãƒ¼ã®åŸºæœ¬ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã«ã‚ã‚‹ :class:`AnsibleModule` オブジェクトã«ã‚ˆã£ã¦å‡¦ç†ã•ã‚Œã¾ã™ã€‚通常㯠``STDIN`` ã§å…¥åŠ›ã‚’å—ã‘付ã‘ã¾ã™ãŒã€ã“ã‚Œã¯ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã«ã¯ä¸ä¾¿ã§ã™ã€‚特殊変数ãŒè¨å®šã•ã‚Œã‚‹ã¨ã€ã‚ãŸã‹ã‚‚入力㌠``STDIN`` ã§ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«æ¥ãŸã‹ã®ã‚ˆã†ã«æ‰±ã‚ã‚Œã¾ã™ã€‚モジュールをセットアップã™ã‚‹å‰ã«ã“ã®é–¢æ•°ã‚’呼ã³å‡ºã™ã ã‘ã§ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:309 +#: ../../rst/dev_guide/testing_units_modules.rst:321 msgid "Handling exit correctly" msgstr "終了をé©åˆ‡ã«å‡¦ç†" -#: ../../rst/dev_guide/testing_units_modules.rst:314 -msgid "The :meth:`module.exit_json` function won't work properly in a testing environment since it writes error information to ``STDOUT`` upon exit, where it is difficult to examine. This can be mitigated by replacing it (and :meth:`module.fail_json`) with a function that raises an exception::" +#: ../../rst/dev_guide/testing_units_modules.rst:326 +msgid "The :meth:`module.exit_json` function won't work properly in a testing environment since it writes error information to ``STDOUT`` upon exit, where it is difficult to examine. This can be mitigated by replacing it (and :meth:`module.fail_json`) with a function that raises an exception:" msgstr ":meth:`module.exit_json` 関数ã¯ã€çµ‚了時ã«ã‚¨ãƒ©ãƒ¼æƒ…å ±ã‚’ ``STDOUT`` ã«æ›¸ã込むãŸã‚ã€ãƒ†ã‚¹ãƒˆç’°å¢ƒã§é©åˆ‡ã«å‹•ä½œã—ã¾ã›ã‚“。ã“ã‚Œã¯æ¤œè¨¼ãŒå›°é›£ã§ã™ã€‚ã“ã‚Œã¯ã€ã“ã®é–¢æ•° (ãŠã‚ˆã³ :meth:`module.fail_json`) ã‚’ã€ä¾‹å¤–を発生ã•ã›ã‚‹é–¢æ•°ã«ç½®ãæ›ãˆã‚‹ã“ã¨ã§è»½æ¸›ã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:324 -msgid "Now you can ensure that the first function called is the one you expected simply by testing for the correct exception::" +#: ../../rst/dev_guide/testing_units_modules.rst:338 +msgid "Now you can ensure that the first function called is the one you expected simply by testing for the correct exception:" msgstr "ã“ã‚Œã§ã€æ£ã—ã„例外をテストã™ã‚‹ã ã‘ã§ã€æœ€åˆã«å‘¼ã³å‡ºã•ã‚ŒãŸé–¢æ•°ãŒæœŸå¾…ã—ãŸã‚‚ã®ã§ã‚ã‚‹ã“ã¨ã‚’確èªã§ãるよã†ã«ãªã‚Šã¾ã—ãŸã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:337 +#: ../../rst/dev_guide/testing_units_modules.rst:353 msgid "The same technique can be used to replace :meth:`module.fail_json` (which is used for failure returns from modules) and for the ``aws_module.fail_json_aws()`` (used in modules for Amazon Web Services)." msgstr "åŒã˜ãƒ†ã‚¯ãƒ‹ãƒƒã‚¯ã‚’使用ã—ã¦ã€:meth:`module.fail_json` (モジュールã‹ã‚‰è¿”る障害ã«ä½¿ç”¨) ãŠã‚ˆã³ ``aws_module.fail_json_aws()`` (Amazon Web Services ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ä½¿ç”¨) ã«ç½®ãæ›ãˆã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:342 +#: ../../rst/dev_guide/testing_units_modules.rst:358 msgid "Running the main function" msgstr "主ãªé–¢æ•°ã®å®Ÿè¡Œ" -#: ../../rst/dev_guide/testing_units_modules.rst:344 -msgid "If you do want to run the actual main function of a module you must import the module, set the arguments as above, set up the appropriate exit exception and then run the module::" +#: ../../rst/dev_guide/testing_units_modules.rst:360 +msgid "If you do want to run the actual main function of a module you must import the module, set the arguments as above, set up the appropriate exit exception and then run the module:" msgstr "モジュールã«ãŠã‘る主ãªå®Ÿé–¢æ•°ã‚’実行ã™ã‚‹å ´åˆã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’インãƒãƒ¼ãƒˆã—ã€ä¸Šè¨˜ã®ã‚ˆã†ã«å¼•æ•°ã‚’è¨å®šã—ã€é©åˆ‡ãªçµ‚了例外をè¨å®šã—ã¦ã‹ã‚‰ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’実行ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:362 +#: ../../rst/dev_guide/testing_units_modules.rst:380 msgid "Handling calls to external executables" msgstr "外部実行ファイルã¸ã®å‘¼ã³å‡ºã—ã®å‡¦ç†" -#: ../../rst/dev_guide/testing_units_modules.rst:364 +#: ../../rst/dev_guide/testing_units_modules.rst:382 msgid "Module must use :meth:`AnsibleModule.run_command` in order to execute an external command. This method needs to be mocked:" msgstr "モジュールã¯ã€å¤–部コマンドを実行ã™ã‚‹ã®ã« :meth:`AnsibleModule.run_command` を使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®ãƒ¡ã‚½ãƒƒãƒ‰ã‚’モックã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:367 -msgid "Here is a simple mock of :meth:`AnsibleModule.run_command` (taken from :file:`test/units/modules/packaging/os/test_rhn_register.py`)::" +#: ../../rst/dev_guide/testing_units_modules.rst:385 +msgid "Here is a simple mock of :meth:`AnsibleModule.run_command` (taken from :file:`test/units/modules/packaging/os/test_rhn_register.py`):" msgstr "以下ã¯ã€:meth:`AnsibleModule.run_command` (:file:`test/units/modules/packaging/os/test_rhn_register.py` ã‹ã‚‰å–å¾—) ã®ç°¡å˜ãªãƒ¢ãƒƒã‚¯ã§ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:381 +#: ../../rst/dev_guide/testing_units_modules.rst:401 msgid "A Complete Example" msgstr "完全ãªä¾‹" -#: ../../rst/dev_guide/testing_units_modules.rst:383 -msgid "The following example is a complete skeleton that reuses the mocks explained above and adds a new mock for :meth:`Ansible.get_bin_path`::" +#: ../../rst/dev_guide/testing_units_modules.rst:403 +msgid "The following example is a complete skeleton that reuses the mocks explained above and adds a new mock for :meth:`Ansible.get_bin_path`:" msgstr "次ã®ä¾‹ã¯ã€ä¸Šè¨˜ã§èª¬æ˜Žã—ãŸãƒ¢ãƒƒã‚¯ã‚’å†åˆ©ç”¨ã—ã€:meth:`Ansible.get_bin_path` ã®æ–°ã—ã„ãƒ¢ãƒƒã‚¯ã‚’è¿½åŠ ã™ã‚‹å®Œå…¨ãªã‚¹ã‚±ãƒ«ãƒˆãƒ³ã§ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:469 +#: ../../rst/dev_guide/testing_units_modules.rst:491 msgid "Restructuring modules to enable testing module set up and other processes" msgstr "モジュールã®ã‚»ãƒƒãƒˆã‚¢ãƒƒãƒ—ã‚„ãã®ä»–ã®ãƒ—ãƒã‚»ã‚¹ã®ãƒ†ã‚¹ãƒˆã‚’å¯èƒ½ã«ã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®å†æ§‹ç¯‰" -#: ../../rst/dev_guide/testing_units_modules.rst:471 -msgid "Often modules have a ``main()`` function which sets up the module and then performs other actions. This can make it difficult to check argument processing. This can be made easier by moving module configuration and initialization into a separate function. For example::" +#: ../../rst/dev_guide/testing_units_modules.rst:493 +msgid "Often modules have a ``main()`` function which sets up the module and then performs other actions. This can make it difficult to check argument processing. This can be made easier by moving module configuration and initialization into a separate function. For example:" msgstr "多ãã®å ´åˆã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’セットアップã—ã€ä»–ã®ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ã‚’実行ã™ã‚‹ ``main()`` 関数ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€å¼•æ•°å‡¦ç†ã‚’確èªã™ã‚‹ã®ãŒå›°é›£ã«ãªã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚モジュールã®è¨å®šã¨åˆæœŸåŒ–を別ã®é–¢æ•°ã«ç§»ã™ã“ã¨ã§ç°¡å˜ã«ã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:501 -msgid "This now makes it possible to run tests against the module initiation function::" +#: ../../rst/dev_guide/testing_units_modules.rst:525 +msgid "This now makes it possible to run tests against the module initiation function:" msgstr "ã“ã‚Œã«ã‚ˆã‚Šã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®é–‹å§‹é–¢æ•°ã«å¯¾ã—ã¦ãƒ†ã‚¹ãƒˆã‚’実行ã§ãるよã†ã«ãªã‚Šã¾ã—ãŸã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:513 +#: ../../rst/dev_guide/testing_units_modules.rst:539 msgid "See also ``test/units/module_utils/aws/test_rds.py``" msgstr "「``test/units/module_utils/aws/test_rds.py``ã€ã‚‚å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/testing_units_modules.rst:515 +#: ../../rst/dev_guide/testing_units_modules.rst:541 msgid "Note that the ``argument_spec`` dictionary is visible in a module variable. This has advantages, both in allowing explicit testing of the arguments and in allowing the easy creation of module objects for testing." msgstr "``argument_spec`` ディクショナリーã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«å¤‰æ•°ã«è¡¨ç¤ºã•ã‚Œã¾ã™ã€‚ã“ã‚Œã«ã¯ã€å¼•æ•°ã®æ˜Žç¤ºçš„ãªãƒ†ã‚¹ãƒˆã‚’許å¯ã—ã€ãƒ†ã‚¹ãƒˆç”¨ã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚ªãƒ–ジェクトã®ä½œæˆã‚’ç°¡å˜ã«è¡Œãˆã‚‹ã‚ˆã†ã«ã™ã‚‹åˆ©ç‚¹ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:519 +#: ../../rst/dev_guide/testing_units_modules.rst:545 msgid "The same restructuring technique can be valuable for testing other functionality, such as the part of the module which queries the object that the module configures." msgstr "ã“ã®å†æ§‹ç¯‰ã®æ‰‹æ³•ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒè¨å®šã—ãŸã‚ªãƒ–ジェクトをå•ã„åˆã‚ã›ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®éƒ¨åˆ†ãªã©ã€ãã®ä»–ã®æ©Ÿèƒ½ã‚’テストã™ã‚‹å ´åˆã«ã‚‚å½¹ã«ç«‹ã¡ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:522 +#: ../../rst/dev_guide/testing_units_modules.rst:548 msgid "Traps for maintaining Python 2 compatibility" msgstr "Python 2 ã®äº’æ›æ€§ã‚’ç¶æŒã™ã‚‹ãŸã‚ã®ãƒˆãƒ©ãƒƒãƒ—" -#: ../../rst/dev_guide/testing_units_modules.rst:524 +#: ../../rst/dev_guide/testing_units_modules.rst:550 msgid "If you use the ``mock`` library from the Python 2.6 standard library, a number of the assert functions are missing but will return as if successful. This means that test cases should take great care *not* use functions marked as _new_ in the Python 3 documentation, since the tests will likely always succeed even if the code is broken when run on older versions of Python." msgstr "Python 2.6 標準ライブラリー㮠``mock`` ライブラリーを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€å¤šãã® assert 関数ãŒæ¬ è½ã—ã¦ã„ã¾ã™ãŒã€æˆåŠŸã—ãŸã‹ã®ã‚ˆã†ã«è¿”ã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ã€ãƒ†ã‚¹ãƒˆã‚±ãƒ¼ã‚¹ãŒã€Python 3 ã®ãƒ‰ã‚ュメント㧠_new_ ã¨ãªã£ã¦ã„る関数を使用ã—ãªã„よã†ã€ç´°å¿ƒã®æ³¨æ„を払ã†ã¹ãã§ã‚ã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚ãªãœãªã‚‰ã€å¤ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Python ã§å®Ÿè¡Œã•ã‚ŒãŸã‚³ãƒ¼ãƒ‰ãŒå£Šã‚Œã¦ã„ã¦ã‚‚ã€ãƒ†ã‚¹ãƒˆã¯å¸¸ã«æˆåŠŸã™ã‚‹ã‹ã‚‰ã§ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:529 +#: ../../rst/dev_guide/testing_units_modules.rst:555 msgid "A helpful development approach to this should be to ensure that all of the tests have been run under Python 2.6 and that each assertion in the test cases has been checked to work by breaking the code in Ansible to trigger that failure." msgstr "ã“ã‚Œã«å½¹ç«‹ã¤é–‹ç™ºã‚¢ãƒ—ãƒãƒ¼ãƒã¯ã€ã™ã¹ã¦ã®ãƒ†ã‚¹ãƒˆãŒ Python 2.6 ã§å®Ÿè¡Œã•ã‚Œã¦ã„ã‚‹ã“ã¨ã¨ã€ãƒ†ã‚¹ãƒˆã‚±ãƒ¼ã‚¹å†…ã®å„アサーション㌠Ansible ã§ã‚³ãƒ¼ãƒ‰ã‚’壊ã—ã¦ãã®å¤±æ•—を誘発ã™ã‚‹ã“ã¨ã§å‹•ä½œã™ã‚‹ã“ã¨ãŒç¢ºèªã•ã‚Œã¦ã„ã‚‹ã¨ã„ã†ç‚¹ã‚’確èªã™ã‚‹ã“ã¨ã§ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:533 +#: ../../rst/dev_guide/testing_units_modules.rst:559 msgid "Maintain Python 2.6 compatibility" msgstr "Python 2.6 互æ›æ€§ã®ç¶æŒ" -#: ../../rst/dev_guide/testing_units_modules.rst:535 +#: ../../rst/dev_guide/testing_units_modules.rst:561 msgid "Please remember that modules need to maintain compatibility with Python 2.6 so the unittests for modules should also be compatible with Python 2.6." msgstr "モジュール㯠Python 2.6 ã¨ã®äº’æ›æ€§ã‚’ç¶æŒã™ã‚‹å¿…è¦ãŒã‚ã‚‹ãŸã‚ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã‚‚ã€Python 2.6 ã¨ã®äº’æ›æ€§ã‚’ç¶æŒã™ã‚‹å¿…è¦ãŒã‚ã‚‹ã“ã¨ã«æ³¨æ„ã—ã¦ãã ã•ã„。" -#: ../../rst/dev_guide/testing_units_modules.rst:542 +#: ../../rst/dev_guide/testing_units_modules.rst:568 msgid "Ansible unit tests documentation" msgstr "Ansible ユニットテストドã‚ュメント" -#: ../../rst/dev_guide/testing_units_modules.rst:546 +#: ../../rst/dev_guide/testing_units_modules.rst:572 msgid "Get started developing a module" msgstr "モジュール開発を始ã‚ã‚‹" -#: ../../rst/dev_guide/testing_units_modules.rst:555 +#: ../../rst/dev_guide/testing_units_modules.rst:581 msgid "`Testing Your Code (from The Hitchhiker's Guide to Python!) <https://docs.python-guide.org/writing/tests/>`_" msgstr "`Testing Your Code (from The Hitchhiker's Guide to Python!) <https://docs.python-guide.org/writing/tests/>`_" -#: ../../rst/dev_guide/testing_units_modules.rst:556 +#: ../../rst/dev_guide/testing_units_modules.rst:582 msgid "General advice on testing Python code" msgstr "Python コードã®ãƒ†ã‚¹ãƒˆã«é–¢ã™ã‚‹ä¸€èˆ¬çš„ãªã‚¢ãƒ‰ãƒã‚¤ã‚¹" -#: ../../rst/dev_guide/testing_units_modules.rst:558 +#: ../../rst/dev_guide/testing_units_modules.rst:584 msgid "`Uncle Bob's many videos on YouTube <https://www.youtube.com/watch?v=QedpQjxBPMA&list=PLlu0CT-JnSasQzGrGzddSczJQQU7295D2>`_" msgstr "`Uncle Bob's many videos on YouTube <https://www.youtube.com/watch?v=QedpQjxBPMA&list=PLlu0CT-JnSasQzGrGzddSczJQQU7295D2>`_" -#: ../../rst/dev_guide/testing_units_modules.rst:558 +#: ../../rst/dev_guide/testing_units_modules.rst:584 msgid "Unit testing is a part of the of various philosophies of software development, including Extreme Programming (XP), Clean Coding. Uncle Bob talks through how to benefit from this" msgstr "ユニットテストã¯ã€Extreme Programming (XP)ã€ã‚¯ãƒªãƒ¼ãƒ³ã‚³ãƒ¼ãƒ‡ã‚£ãƒ³ã‚°ã‚’å«ã‚€ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢é–‹ç™ºã®ã•ã¾ã–ã¾ãªå“²å¦ã®ä¸€éƒ¨ã§ã™ã€‚Uncle Bob ã¯ã€ã©ã®ã‚ˆã†ã«ã—ã¦ã“ã®æ©æµã‚’å—ã‘ã‚‹ã“ã¨ãŒã§ãã‚‹ã®ã‹ã‚’説明ã—ã¾ã™ã€‚" -#: ../../rst/dev_guide/testing_units_modules.rst:560 +#: ../../rst/dev_guide/testing_units_modules.rst:586 msgid "`\"Why Most Unit Testing is Waste\" <https://rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdf>`_" msgstr "`\"Why Most Unit Testing is Waste\" <https://rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdf>`_" -#: ../../rst/dev_guide/testing_units_modules.rst:561 +#: ../../rst/dev_guide/testing_units_modules.rst:587 msgid "An article warning against the costs of unit testing" msgstr "ユニットテストã®å¤§åŠãŒç„¡é§„ã§ã‚ã‚‹ç†ç”±" -#: ../../rst/dev_guide/testing_units_modules.rst:562 +#: ../../rst/dev_guide/testing_units_modules.rst:588 msgid "`'A Response to \"Why Most Unit Testing is Waste\"' <https://henrikwarne.com/2014/09/04/a-response-to-why-most-unit-testing-is-waste/>`_" msgstr "`'A Response to \"Why Most Unit Testing is Waste\"' <https://henrikwarne.com/2014/09/04/a-response-to-why-most-unit-testing-is-waste/>`_" -#: ../../rst/dev_guide/testing_units_modules.rst:563 +#: ../../rst/dev_guide/testing_units_modules.rst:589 msgid "An response pointing to how to maintain the value of unit tests" msgstr "ユニットテストã®ä¾¡å€¤ã‚’ç¶æŒã™ã‚‹æ–¹æ³•ã‚’指摘ã—ãŸå›žç”" @@ -15616,3 +15623,15 @@ msgstr "セマンティックãƒãƒ¼ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°ä»•æ§˜ (https://semver.org/)) #~ msgid "Did not find a call to ``main()`` (or ``removed_module()`` in the case of deprecated & docs only modules)" #~ msgstr "``main()`` ã¸ã®å‘¼å‡ºã—ãŒè¦‹ã¤ã‹ã‚‰ãªã‹ã£ãŸ (éžæŽ¨å¥¨ã¾ãŸã¯ãƒ‰ã‚ュメントã®ã¿ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®å ´åˆã¯ ``removed_module()``)。" +#~ msgid "Avoiding pulling new Docker images" +#~ msgstr "æ–°è¦ Docker イメージã®ãƒ—ルã®å›žé¿" + +#~ msgid "Use the ``--docker-no-pull`` option to avoid pulling the latest container image. This is required when using custom local images that are not available for download." +#~ msgstr "最新ã®ã‚³ãƒ³ãƒ†ãƒŠãƒ¼ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’プルã—ãªã„よã†ã«ã™ã‚‹ã«ã¯ã€``--docker-no-pull`` オプションを使用ã—ã¾ã™ã€‚ã“ã‚Œã¯ã€ãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰ã«åˆ©ç”¨ã§ããªã„カスタムã®ãƒãƒ¼ã‚«ãƒ«ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’使用ã™ã‚‹å ´åˆã«å¿…è¦ã§ã™ã€‚" + +#~ msgid "centos6" +#~ msgstr "centos6" + +#~ msgid "fedora32" +#~ msgstr "fedora32" + diff --git a/docs/docsite/rst/locales/ja/LC_MESSAGES/installation_guide.po b/docs/docsite/rst/locales/ja/LC_MESSAGES/installation_guide.po index 87cf5bb8..30d94452 100644 --- a/docs/docsite/rst/locales/ja/LC_MESSAGES/installation_guide.po +++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/installation_guide.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Ansible devel\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-10-05 13:53+0200\n" +"POT-Creation-Date: 2021-11-09 14:07+0100\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" @@ -238,8 +238,8 @@ msgstr "``pip`` を使用ã—㟠Ansible ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" #: ../../rst/installation_guide/intro_installation.rst:120 #: ../../rst/installation_guide/intro_installation.rst:152 -#: ../../rst/installation_guide/intro_installation.rst:391 -#: ../../rst/installation_guide/intro_installation.rst:490 +#: ../../rst/installation_guide/intro_installation.rst:377 +#: ../../rst/installation_guide/intro_installation.rst:484 msgid "If you have Ansible 2.9 or older installed or Ansible 3, see :ref:`pip_upgrade`." msgstr "Ansible 2.9 以å‰ã‚‚ã—ã㯠Ansible 3 ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€ã€Œ:ref:`pip_upgrade`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" @@ -316,7 +316,7 @@ msgid "Installing Ansible on RHEL, CentOS, or Fedora" msgstr "RHELã€CentOSã€ã¾ãŸã¯ Fedora ã¸ã® Ansible ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" #: ../../rst/installation_guide/intro_installation.rst:223 -#: ../../rst/installation_guide/intro_installation.rst:608 +#: ../../rst/installation_guide/intro_installation.rst:602 msgid "On Fedora:" msgstr "Fedora ã®å ´åˆ:" @@ -329,465 +329,461 @@ msgid "On CentOS:" msgstr "CentOS ã®å ´åˆ:" #: ../../rst/installation_guide/intro_installation.rst:242 -msgid "RPMs for RHEL 7 and RHEL 8 are available from the `Ansible Engine repository <https://access.redhat.com/articles/3174981>`_." -msgstr "RHEL 7 ãŠã‚ˆã³ RHEL 8 ã® RPM ã¯ã€`Ansible Engine リãƒã‚¸ãƒˆãƒªãƒ¼ <https://access.redhat.com/articles/3174981>`_ ã‹ã‚‰å…¥æ‰‹ã§ãã¾ã™ã€‚" - -#: ../../rst/installation_guide/intro_installation.rst:244 -msgid "To enable the Ansible Engine repository for RHEL 8, run the following command:" -msgstr "RHEL 8 用㮠Ansible Engine リãƒã‚¸ãƒˆãƒªãƒ¼ã‚’有効ã«ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" - -#: ../../rst/installation_guide/intro_installation.rst:250 -msgid "To enable the Ansible Engine repository for RHEL 7, run the following command:" -msgstr "RHEL 7 用㮠Ansible Engine リãƒã‚¸ãƒˆãƒªãƒ¼ã‚’有効ã«ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" - -#: ../../rst/installation_guide/intro_installation.rst:256 msgid "RPMs for currently supported versions of RHEL and CentOS are also available from `EPEL <https://fedoraproject.org/wiki/EPEL>`_." msgstr "ç¾åœ¨ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã‚‹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® RHEL ãŠã‚ˆã³ CentOS ã®å ´åˆã¯ã€`EPEL <https://fedoraproject.org/wiki/EPEL>`_ ã‹ã‚‰ã‚‚利用ã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:260 +#: ../../rst/installation_guide/intro_installation.rst:246 msgid "Since Ansible 2.10 for RHEL is not available at this time, continue to use Ansible 2.9." msgstr "ç¾åœ¨ã€RHEL ã§ã¯ Ansible 2.10 ãŒåˆ©ç”¨ã§ããªã„ãŸã‚ã€å¼•ã続ã Ansible 2.9 を使用ã—ã¦ãã ã•ã„。" -#: ../../rst/installation_guide/intro_installation.rst:262 +#: ../../rst/installation_guide/intro_installation.rst:248 msgid "Ansible can manage older operating systems that contain Python 2.6 or higher." msgstr "Ansible ã¯ã€Python 2.6 以é™ãŒå«ã¾ã‚Œã‚‹å¤ã„オペレーティングシステムを管ç†ã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:267 +#: ../../rst/installation_guide/intro_installation.rst:253 msgid "Installing Ansible on Ubuntu" msgstr "Ubuntu ã¸ã® Ansible ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/installation_guide/intro_installation.rst:269 +#: ../../rst/installation_guide/intro_installation.rst:255 msgid "Ubuntu builds are available `in a PPA here <https://launchpad.net/~ansible/+archive/ubuntu/ansible>`_." msgstr "Ubuntu ビルド㯠`PPA <https://launchpad.net/~ansible/+archive/ubuntu/ansible>`_ ã§åˆ©ç”¨ã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:271 +#: ../../rst/installation_guide/intro_installation.rst:257 msgid "To configure the PPA on your machine and install Ansible run these commands:" msgstr "自分ã®ãƒžã‚·ãƒ³ã« PPA ã‚’è¨å®šã—㦠Ansible をインストールã™ã‚‹ã«ã¯ã€æ¬¡ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:280 +#: ../../rst/installation_guide/intro_installation.rst:266 msgid "On older Ubuntu distributions, \"software-properties-common\" is called \"python-software-properties\". You may want to use ``apt-get`` instead of ``apt`` in older versions. Also, be aware that only newer distributions (in other words, 18.04, 18.10, and so on) have a ``-u`` or ``--update`` flag, so adjust your script accordingly." msgstr "以å‰ã® Ubuntu ディストリビューションã§ã¯ã€ã€Œsoftware-properties-commonã€ã¯ã€Œpython-software-propertiesã€ã¨å‘¼ã°ã‚Œã‚‹ãŸã‚ã€éŽåŽ»ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã¯ ``apt`` ã§ã¯ãªã ``apt-get`` を使用ã™ã‚‹ã»ã†ãŒé©ã—ã¦ã„ã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚ã¾ãŸã€``-u`` フラグã¾ãŸã¯ ``--update`` フラグãŒæŒ‡å®šã§ãã‚‹ã®ã¯ã€æ–°ã—ã„ディストリビューション (18.04ã€18.10 ãªã©) ã«é™å®šã•ã‚Œã‚‹ã“ã¨ã«æ³¨æ„ã—ã€ã‚¹ã‚¯ãƒªãƒ—トを調整ã—ã¦ãã ã•ã„。" -#: ../../rst/installation_guide/intro_installation.rst:282 +#: ../../rst/installation_guide/intro_installation.rst:268 msgid "Debian/Ubuntu packages can also be built from the source checkout, run:" msgstr "Debian/Ubuntu パッケージã¯ã€ã‚½ãƒ¼ã‚¹ãƒã‚§ãƒƒã‚¯ã‚¢ã‚¦ãƒˆã‹ã‚‰æ§‹ç¯‰ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚以下を実行ã—ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:289 +#: ../../rst/installation_guide/intro_installation.rst:275 msgid "Installing Ansible on Debian" msgstr "Ansible ã® Debian ã¸ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/installation_guide/intro_installation.rst:291 +#: ../../rst/installation_guide/intro_installation.rst:277 msgid "Debian users may use the same source as the Ubuntu PPA (using the following table)." msgstr "Debian ユーザー㯠Ubuntu PPA ã¨åŒã˜ã‚½ãƒ¼ã‚¹ã‚’使用ã§ãã¾ã™ï¼ˆä»¥ä¸‹ã®è¡¨ã‚’使用）。" -#: ../../rst/installation_guide/intro_installation.rst:296 +#: ../../rst/installation_guide/intro_installation.rst:282 msgid "Debian" msgstr "Debian" -#: ../../rst/installation_guide/intro_installation.rst:298 +#: ../../rst/installation_guide/intro_installation.rst:284 msgid "Ubuntu" msgstr "Ubuntu" -#: ../../rst/installation_guide/intro_installation.rst:299 +#: ../../rst/installation_guide/intro_installation.rst:285 msgid "Debian 11 (Bullseye)" msgstr "Debian 11 (Bullseye)" -#: ../../rst/installation_guide/intro_installation.rst:300 -#: ../../rst/installation_guide/intro_installation.rst:303 -#: ../../rst/installation_guide/intro_installation.rst:306 -#: ../../rst/installation_guide/intro_installation.rst:309 +#: ../../rst/installation_guide/intro_installation.rst:286 +#: ../../rst/installation_guide/intro_installation.rst:289 +#: ../../rst/installation_guide/intro_installation.rst:292 +#: ../../rst/installation_guide/intro_installation.rst:295 msgid "->" msgstr "->" -#: ../../rst/installation_guide/intro_installation.rst:301 +#: ../../rst/installation_guide/intro_installation.rst:287 msgid "Ubuntu 20.04 (Focal)" msgstr "Ubuntu 20.04 (Focal)" -#: ../../rst/installation_guide/intro_installation.rst:302 +#: ../../rst/installation_guide/intro_installation.rst:288 msgid "Debian 10 (Buster)" msgstr "Debian 10 (Buster)" -#: ../../rst/installation_guide/intro_installation.rst:304 +#: ../../rst/installation_guide/intro_installation.rst:290 msgid "Ubuntu 18.04 (Bionic)" msgstr "Ubuntu 18.04 (Bionic)" -#: ../../rst/installation_guide/intro_installation.rst:305 +#: ../../rst/installation_guide/intro_installation.rst:291 msgid "Debian 9 (Stretch)" msgstr "Debian 9 (Stretch)" -#: ../../rst/installation_guide/intro_installation.rst:307 +#: ../../rst/installation_guide/intro_installation.rst:293 msgid "Ubuntu 16.04 (Xenial)" msgstr "Ubuntu 16.04 (Xenial)" -#: ../../rst/installation_guide/intro_installation.rst:308 +#: ../../rst/installation_guide/intro_installation.rst:294 msgid "Debian 8 (Jessie)" msgstr "Debian 8 (Jessie)" -#: ../../rst/installation_guide/intro_installation.rst:310 +#: ../../rst/installation_guide/intro_installation.rst:296 msgid "Ubuntu 14.04 (Trusty)" msgstr "Ubuntu 14.04 (Trusty)" -#: ../../rst/installation_guide/intro_installation.rst:314 +#: ../../rst/installation_guide/intro_installation.rst:300 msgid "As of Ansible 4.0.0, new releases will only be generated for Ubuntu 18.04 (Bionic) or later releases." msgstr "Ansible 4.0.0 ã®æ™‚点ã§ã€æ–°ã—ã„リリース㯠Ubuntu 18.04 (Bionic) 以é™ã®ãƒªãƒªãƒ¼ã‚¹ã«å¯¾ã—ã¦ã®ã¿ç”Ÿæˆã•ã‚Œã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:316 +#: ../../rst/installation_guide/intro_installation.rst:302 msgid "Add the following line to ``/etc/apt/sources.list`` or ``/etc/apt/sources.list.d/ansible.list``:" msgstr "以下ã®è¡Œã‚’ ``/etc/apt/sources.list`` ã¾ãŸã¯ ``/etc/apt/sources.list.d/ansible.list`` ã«è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:322 +#: ../../rst/installation_guide/intro_installation.rst:308 msgid "Example for Debian 11 (Bullseye)" msgstr "Debian 11 ã®ä¾‹ (Bullseye)" -#: ../../rst/installation_guide/intro_installation.rst:328 +#: ../../rst/installation_guide/intro_installation.rst:314 msgid "Then run these commands:" msgstr "次ã«ã€ä»¥ä¸‹ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:337 +#: ../../rst/installation_guide/intro_installation.rst:323 msgid "Installing Ansible on Gentoo with portage" msgstr "portage を使用ã—㟠Gentoo ã¸ã® Ansible ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/installation_guide/intro_installation.rst:343 +#: ../../rst/installation_guide/intro_installation.rst:329 msgid "To install the newest version, you may need to unmask the Ansible package prior to emerging:" msgstr "最新ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’インストールã™ã‚‹ã«ã¯ã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã™ã‚‹å‰ã« Ansible パッケージã®ãƒžã‚¹ã‚¯è§£é™¤ãŒå¿…è¦ã«ãªã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:350 +#: ../../rst/installation_guide/intro_installation.rst:336 msgid "Installing Ansible on FreeBSD" msgstr "FreeBSD ã¸ã® Ansible ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/installation_guide/intro_installation.rst:352 +#: ../../rst/installation_guide/intro_installation.rst:338 msgid "Though Ansible works with both Python 2 and 3 versions, FreeBSD has different packages for each Python version. So to install you can use:" msgstr "Ansible 㯠Python 2 ãŠã‚ˆã³ 3 ã®ä¸¡ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§å‹•ä½œã—ã¾ã™ãŒã€FreeBSD パッケージã¯å„ Python ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ç•°ãªã‚Šã¾ã™ã€‚ã—ãŸãŒã£ã¦ã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã«ã¯ã€ä»¥ä¸‹ã‚’使用ã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:359 +#: ../../rst/installation_guide/intro_installation.rst:345 msgid "or:" msgstr "ã¾ãŸã¯" -#: ../../rst/installation_guide/intro_installation.rst:366 +#: ../../rst/installation_guide/intro_installation.rst:352 msgid "You may also wish to install from ports, run:" msgstr "ãƒãƒ¼ãƒˆã‹ã‚‰ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚以下を実行ã—ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:372 +#: ../../rst/installation_guide/intro_installation.rst:358 msgid "You can also choose a specific version, for example ``ansible25``." msgstr "特定ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ (例: ``ansible25``) ã‚’é¸æŠžã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:374 +#: ../../rst/installation_guide/intro_installation.rst:360 msgid "Older versions of FreeBSD worked with something like this (substitute for your choice of package manager):" msgstr "以å‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® FreeBSD ã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ãªã‚‚ã®ã§å‹•ä½œã—ã¾ã™ (パッケージマãƒãƒ¼ã‚¸ãƒ£ãƒ¼ã®ä»£ã‚ã‚Šã§ã™)。" -#: ../../rst/installation_guide/intro_installation.rst:383 +#: ../../rst/installation_guide/intro_installation.rst:369 msgid "Installing Ansible on macOS" msgstr "MacOS ã¸ã® Ansible ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/installation_guide/intro_installation.rst:385 +#: ../../rst/installation_guide/intro_installation.rst:371 msgid "The preferred way to install Ansible on a Mac is with ``pip``." msgstr "Mac ã« Ansible をインストールã™ã‚‹ã«ã¯ ``pip`` を使用ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:387 +#: ../../rst/installation_guide/intro_installation.rst:373 msgid "The instructions can be found in :ref:`from_pip`. If you are running macOS version 10.12 or older, then you should upgrade to the latest ``pip`` to connect to the Python Package Index securely. It should be noted that pip must be run as a module on macOS, and the linked ``pip`` instructions will show you how to do that." msgstr "æ‰‹é †ã¯ã€Œ:ref:`from_pip`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。MacOS ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 10.12 以å‰ã‚’実行ã—ã¦ã„ã‚‹å ´åˆã«ã€Python Package Index ã«å®‰å…¨ã«æŽ¥ç¶šã™ã‚‹ã«ã¯æœ€æ–°ã® ``pip`` ã«ã‚¢ãƒƒãƒ—グレードã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚pip ã¯ã€MacOS ã§ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¨ã—ã¦å®Ÿè¡Œã™ã‚‹å¿…è¦ãŒã‚ã‚Šã€ãƒªãƒ³ã‚¯ã•ã‚Œã¦ã„ã‚‹ ``pip`` ã®æ‰‹é †ã«ãã®å®Ÿè¡Œæ–¹æ³•ãŒç¤ºã•ã‚Œã‚‹ã“ã¨ã«æ³¨æ„ã—ã¦ãã ã•ã„。" -#: ../../rst/installation_guide/intro_installation.rst:396 +#: ../../rst/installation_guide/intro_installation.rst:382 msgid "macOS by default is configured for a small number of file handles, so if you want to use 15 or more forks you'll need to raise the ulimit with ``sudo launchctl limit maxfiles unlimited``. This command can also fix any \"Too many open files\" errors." msgstr "MacOS ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã€å°‘æ•°ã®ãƒ•ã‚¡ã‚¤ãƒ«ãƒãƒ³ãƒ‰ãƒ«å‘ã‘ã«è¨å®šã•ã‚Œã¦ã„ã‚‹ãŸã‚ã€15 個以上ã®ãƒ•ã‚©ãƒ¼ã‚¯ã‚’使用ã™ã‚‹å ´åˆã¯ã€``sudo launchctl limit maxfiles unlimited`` を使用ã—㦠ulimit を増やã™å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®ã‚³ãƒžãƒ³ãƒ‰ã¯ã€ã€ŒToo many open filesã€ã‚¨ãƒ©ãƒ¼ã‚’ä¿®æ£ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:398 +#: ../../rst/installation_guide/intro_installation.rst:384 msgid "If you are installing on macOS Mavericks (10.9), you may encounter some noise from your compiler. A workaround is to do the following::" msgstr "MacOS Mavericks (10.9) ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã™ã‚‹å ´åˆã¯ã€ã‚³ãƒ³ãƒ‘イラーã‹ã‚‰ä½•ã‚‰ã‹ã®å•é¡ŒãŒç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚回é¿ç–ã¨ã—ã¦ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:406 +#: ../../rst/installation_guide/intro_installation.rst:392 msgid "Installing Ansible on Solaris" msgstr "Solaris ã¸ã® Ansible ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/installation_guide/intro_installation.rst:408 +#: ../../rst/installation_guide/intro_installation.rst:394 msgid "Ansible is available for Solaris as `SysV package from OpenCSW <https://www.opencsw.org/packages/ansible/>`_." msgstr "Solaris ã§ã¯ã€`SysV package from OpenCSW <https://www.opencsw.org/packages/ansible/>`_ ã¨ã—㦠Ansible を利用ã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:418 +#: ../../rst/installation_guide/intro_installation.rst:404 msgid "Installing Ansible on Arch Linux" msgstr "Arch Linux ã¸ã® Ansible ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/installation_guide/intro_installation.rst:420 +#: ../../rst/installation_guide/intro_installation.rst:406 msgid "Ansible is available in the Community repository::" msgstr "Ansible ã¯ã€ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ãƒ¼ãƒªãƒã‚¸ãƒˆãƒªãƒ¼ã‹ã‚‰å…¥æ‰‹ã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:424 -msgid "The AUR has a PKGBUILD for pulling directly from GitHub called `ansible-git <https://aur.archlinux.org/packages/ansible-git>`_." -msgstr "AUR ã«ã¯ã€(`ansible-git <https://aur.archlinux.org/packages/ansible-git>`_ ã¨å‘¼ã°ã‚Œã¦ã„ã‚‹) GitHub ã‹ã‚‰ç›´æŽ¥ãƒ—ルã™ã‚‹ãŸã‚ã® PKGBUILD ãŒã‚ã‚Šã¾ã™ã€‚" +#: ../../rst/installation_guide/intro_installation.rst:410 +msgid "The AUR has a PKGBUILD for pulling directly from GitHub called `ansible-core-git <https://aur.archlinux.org/packages/ansible-core-git>`_." +msgstr "AUR ã«ã¯ã€(`ansible-core-git <https://aur.archlinux.org/packages/ansible-core-git>`_ ã¨å‘¼ã°ã‚Œã¦ã„ã‚‹) GitHub ã‹ã‚‰ç›´æŽ¥ãƒ—ルã™ã‚‹ãŸã‚ã® PKGBUILD ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:426 +#: ../../rst/installation_guide/intro_installation.rst:412 msgid "Also see the `Ansible <https://wiki.archlinux.org/index.php/Ansible>`_ page on the ArchWiki." msgstr "ArchWiki ã®ã€Œ`Ansible <https://wiki.archlinux.org/index.php/Ansible>`_ã€ãƒšãƒ¼ã‚¸ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/installation_guide/intro_installation.rst:431 +#: ../../rst/installation_guide/intro_installation.rst:417 msgid "Installing Ansible on Slackware Linux" msgstr "Slackware Linux ã¸ã® Ansible ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/installation_guide/intro_installation.rst:433 +#: ../../rst/installation_guide/intro_installation.rst:419 msgid "Ansible build script is available in the `SlackBuilds.org <https://slackbuilds.org/apps/ansible/>`_ repository. Can be built and installed using `sbopkg <https://sbopkg.org/>`_." msgstr "Ansible ビルドスクリプト㯠`SlackBuilds.org <https://slackbuilds.org/apps/ansible/>`_ リãƒã‚¸ãƒˆãƒªãƒ¼ã‹ã‚‰åˆ©ç”¨ã§ãã¾ã™ã€‚`sbopkg <https://sbopkg.org/>`_ を使用ã—ã¦ãƒ“ルドãŠã‚ˆã³ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:436 +#: ../../rst/installation_guide/intro_installation.rst:422 msgid "Create queue with Ansible and all dependencies::" msgstr "Ansible ãŠã‚ˆã³ã™ã¹ã¦ã®ä¾å˜é–¢ä¿‚ã‚’å«ã‚€ã‚ューを作æˆã—ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:440 +#: ../../rst/installation_guide/intro_installation.rst:426 msgid "Build and install packages from a created queuefile (answer Q for question if sbopkg should use queue or package)::" msgstr "作æˆã—㟠queuefile ã‹ã‚‰ãƒ‘ッケージを構築ã—ã¦ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã¾ã™ (sbopkg ãŒã‚ューã¾ãŸã¯ãƒ‘ッケージを使用ã™ã‚‹å¿…è¦ãŒã‚ã‚‹å ´åˆã®å•é¡Œã¸ã®å›žç” Q)。" -#: ../../rst/installation_guide/intro_installation.rst:447 +#: ../../rst/installation_guide/intro_installation.rst:433 msgid "Installing Ansible on Clear Linux" msgstr "Clear Linux ã¸ã® Ansible ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/installation_guide/intro_installation.rst:449 +#: ../../rst/installation_guide/intro_installation.rst:435 msgid "Ansible and its dependencies are available as part of the sysadmin host management bundle::" msgstr "Ansible ãŠã‚ˆã³ãã®ä¾å˜é–¢ä¿‚ã¯ã€sysadmin ホスト管ç†ãƒãƒ³ãƒ‰ãƒ«ã®ä¸€éƒ¨ã¨ã—ã¦åˆ©ç”¨ã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:453 +#: ../../rst/installation_guide/intro_installation.rst:439 msgid "Update of the software will be managed by the swupd tool::" msgstr "ソフトウェアã®æ›´æ–°ã¯ã€swupd ツールã«ã‚ˆã‚Šç®¡ç†ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:461 +#: ../../rst/installation_guide/intro_installation.rst:449 +msgid "Installing Ansible on Windows" +msgstr "Ansible ã® Windows ã¸ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" + +#: ../../rst/installation_guide/intro_installation.rst:451 +msgid "See :ref:`windows_faq_ansible`" +msgstr "「:ref:`windows_faq_ansible`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#: ../../rst/installation_guide/intro_installation.rst:455 msgid "Installing and running the ``devel`` branch from source" msgstr "ソースã‹ã‚‰ ``devel`` ブランãƒã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãŠã‚ˆã³å®Ÿè¡Œ" -#: ../../rst/installation_guide/intro_installation.rst:463 +#: ../../rst/installation_guide/intro_installation.rst:457 msgid "In Ansible 2.10 and later, the `ansible/ansible repository <https://github.com/ansible/ansible>`_ contains the code for basic features and functions, such as copying module code to managed nodes. This code is also known as ``ansible-core``." msgstr "Ansible 2.10 以é™ã§ã¯ã€`ansible/ansible repository <https://github.com/ansible/ansible>`_ ã«ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚³ãƒ¼ãƒ‰ã‚’管ç†å¯¾è±¡ãƒŽãƒ¼ãƒ‰ã«ã‚³ãƒ”ーã™ã‚‹ãªã©ã€åŸºæœ¬çš„ãªæ©Ÿèƒ½ã‚„関数ã®ã‚³ãƒ¼ãƒ‰ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ã“ã®ã‚³ãƒ¼ãƒ‰ã¯ ``ansible-core`` ã¨ã—ã¦ã‚‚知られã¦ã„ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:465 +#: ../../rst/installation_guide/intro_installation.rst:459 msgid "New features are added to ``ansible-core`` on a branch called ``devel``. If you are testing new features, fixing bugs, or otherwise working with the development team on changes to the core code, you can install and run ``devel``." msgstr "新機能㌠``devel`` ブランãƒã® ``ansible-core`` ã«è¿½åŠ ã•ã‚Œã¾ã—ãŸã€‚新機能ã®ãƒ†ã‚¹ãƒˆã€ãƒã‚°ã®ä¿®æ£ã€ã¾ãŸã¯ã‚³ã‚¢ã‚³ãƒ¼ãƒ‰ã¸ã®å¤‰æ›´ã«å¯¾ã—ã¦é–‹ç™ºãƒãƒ¼ãƒ ã§ã®ä½œæ¥ã‚’è¡Œã†å ´åˆã¯ã€``devel`` をインストールã—ã¦å®Ÿè¡Œã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:469 +#: ../../rst/installation_guide/intro_installation.rst:463 msgid "You should only install and run the ``devel`` branch if you are modifying ``ansible-core`` or trying out features under development. This is a rapidly changing source of code and can become unstable at any point." msgstr "開発時㫠``ansible-core`` を変更ã—ã€æ©Ÿèƒ½ã‚’試ã™å ´åˆã¯ã€``devel`` ブランãƒã®ã¿ã‚’インストールã—ã€å®Ÿè¡Œã—ã¦ãã ã•ã„。ã“ã®ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã¯æ€¥é€Ÿã«å¤‰åŒ–ã™ã‚‹ãŸã‚ã€ã„ã¤ã§ã‚‚ä¸å®‰å®šã«ãªã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:473 +#: ../../rst/installation_guide/intro_installation.rst:467 msgid "If you want to use Ansible AWX as the control node, do not install or run the ``devel`` branch of Ansible. Use an OS package manager (like ``apt`` or ``yum``) or ``pip`` to install a stable version." msgstr "Ansible AWX をコントãƒãƒ¼ãƒ«ãƒŽãƒ¼ãƒ‰ã¨ã—ã¦ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Ansible ã® ``devel`` ブランãƒã‚’インストールã¾ãŸã¯å®Ÿè¡Œã—ãªã„ã§ãã ã•ã„。OS パッケージマãƒãƒ¼ã‚¸ãƒ£ãƒ¼ (``apt``ã€``yum`` ãªã©) ã¾ãŸã¯ ``pip`` を使用ã—ã¦å®‰å®šã—ãŸãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’インストールã—ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:475 +#: ../../rst/installation_guide/intro_installation.rst:469 msgid "If you are running Ansible from source, you may also wish to follow the `Ansible GitHub project <https://github.com/ansible/ansible>`_. We track issues, document bugs, and share feature ideas in this and other related repositories." msgstr "ソースã‹ã‚‰ Ansible を実行ã™ã‚‹å ´åˆã¯ã€`Ansible GitHub プãƒã‚¸ã‚§ã‚¯ãƒˆ <https://github.com/ansible/ansible>`_ ã«å¾“ã£ã¦ã€å•é¡Œã‚’追跡ã—ã€ãƒã‚°ã‚’文書化ã—ã€ã“ã®ãƒªãƒã‚¸ãƒˆãƒªãƒ¼ã¾ãŸã¯ãã®ä»–ã®ãƒªãƒã‚¸ãƒˆãƒªãƒ¼ã«é–¢ã™ã‚‹æ©Ÿèƒ½ã®ã‚¢ã‚¤ãƒ‡ã‚¢ã‚’共有ã—ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:477 +#: ../../rst/installation_guide/intro_installation.rst:471 msgid "For more information on getting involved in the Ansible project, see the :ref:`ansible_community_guide`. For more information on creating Ansible modules and Collections, see the :ref:`developer_guide`." msgstr "Ansible プãƒã‚¸ã‚§ã‚¯ãƒˆã¸ã®è²¢çŒ®ã®è©³ç´°ã¯ã€ã€Œ:ref:`ansible_community_guide`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。Ansible モジュールãŠã‚ˆã³ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ä½œæˆæ–¹æ³•ã¯ã€ã€Œ:ref:`developer_guide`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/installation_guide/intro_installation.rst:480 +#: ../../rst/installation_guide/intro_installation.rst:474 msgid "Installing ``devel`` from GitHub with ``pip``" msgstr "``pip`` を使用ã—㟠GitHub ã‹ã‚‰ã® ``devel`` ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/installation_guide/intro_installation.rst:482 +#: ../../rst/installation_guide/intro_installation.rst:476 msgid "You can install the ``devel`` branch of ``ansible-core`` directly from GitHub with ``pip``:" msgstr "``pip`` を使用ã—ã¦ã€``ansible-core`` ã® ``devel`` ブランãƒã‚’直接 GitHub ã‹ã‚‰ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:494 +#: ../../rst/installation_guide/intro_installation.rst:488 msgid "You can replace ``devel`` in the URL mentioned above, with any other branch or tag on GitHub to install older versions of Ansible (prior to ``ansible-base`` 2.10.), tagged alpha or beta versions, and release candidates. This installs all of Ansible." msgstr "上記㮠URL ã® ``devel`` ã‚’ã€ä»–ã®ãƒ–ランãƒã¾ãŸã¯ GitHub ã®ã‚¿ã‚°ã«ç½®ãæ›ãˆã¦ã€å¤ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Ansible (``ansible-base`` 2.10 以å‰)ã€ã‚¿ã‚°ä»˜ã‘ã•ã‚ŒãŸ alpha ã¾ãŸã¯ beta ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã€ãŠã‚ˆã³ãƒªãƒªãƒ¼ã‚¹å€™è£œã‚’インストールã—ã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ã™ã¹ã¦ã® Ansible ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:500 +#: ../../rst/installation_guide/intro_installation.rst:494 msgid "See :ref:`from_source` for instructions on how to run ``ansible-core`` directly from source." msgstr "ソースã‹ã‚‰ç›´æŽ¥ ``ansible-core`` を実行ã™ã‚‹æ–¹æ³•ã¯ã€ã€Œ:ref:`from_source`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/installation_guide/intro_installation.rst:504 +#: ../../rst/installation_guide/intro_installation.rst:498 msgid "Installing ``devel`` from GitHub by cloning" msgstr "クãƒãƒ¼ãƒ³ä½œæˆã«ã‚ˆã‚‹ GitHub ã‹ã‚‰ã® ``devel`` ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/installation_guide/intro_installation.rst:506 +#: ../../rst/installation_guide/intro_installation.rst:500 msgid "You can install the ``devel`` branch of ``ansible-core`` by cloning the GitHub repository:" msgstr "GitHub リãƒã‚¸ãƒˆãƒªãƒ¼ã®ã‚¯ãƒãƒ¼ãƒ³ã‚’作æˆã—ã¦ã€``ansible-core`` ã® ``devel`` ブランãƒã‚’インストールã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:513 +#: ../../rst/installation_guide/intro_installation.rst:507 msgid "The default branch is ``devel``." msgstr "デフォルトã®ãƒ–ランãƒã¯ ``devel`` ã§ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:518 +#: ../../rst/installation_guide/intro_installation.rst:512 msgid "Running the ``devel`` branch from a clone" msgstr "クãƒãƒ¼ãƒ³ã‹ã‚‰ã® ``devel`` ブランãƒã®å®Ÿè¡Œ" -#: ../../rst/installation_guide/intro_installation.rst:520 +#: ../../rst/installation_guide/intro_installation.rst:514 msgid "``ansible-core`` is easy to run from source. You do not need ``root`` permissions to use it and there is no software to actually install. No daemons or database setup are required." msgstr "``ansible-core`` ソースã‹ã‚‰ã®å®Ÿè¡Œã¯ç°¡å˜ã§ã™ã€‚``root`` パーミッションã¯å¿…è¦ã‚ã‚Šã¾ã›ã‚“。実際ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã™ã‚‹ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ã¯ã‚ã‚Šã¾ã›ã‚“。デーモンやデータベースè¨å®šã¯å¿…è¦ã‚ã‚Šã¾ã›ã‚“。" -#: ../../rst/installation_guide/intro_installation.rst:522 +#: ../../rst/installation_guide/intro_installation.rst:516 msgid "Once you have installed the ``ansible-core`` repository by cloning, setup the Ansible environment:" msgstr "クãƒãƒ¼ãƒ³ä½œæˆã«ã‚ˆã‚Š ``ansible-core`` リãƒã‚¸ãƒˆãƒªãƒ¼ã‚’インストールã—ãŸã‚‰ã€Ansible 環境をè¨å®šã—ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:524 +#: ../../rst/installation_guide/intro_installation.rst:518 msgid "Using Bash:" msgstr "Bash ã®ä½¿ç”¨:" -#: ../../rst/installation_guide/intro_installation.rst:530 +#: ../../rst/installation_guide/intro_installation.rst:524 msgid "Using Fish::" msgstr "Fish ã®ä½¿ç”¨::" -#: ../../rst/installation_guide/intro_installation.rst:534 +#: ../../rst/installation_guide/intro_installation.rst:528 msgid "If you want to suppress spurious warnings/errors, use::" msgstr "誤ã£ãŸè¦å‘Šã‚„エラーãŒè¡¨ç¤ºã•ã‚Œãªã„よã†ã«ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:538 +#: ../../rst/installation_guide/intro_installation.rst:532 msgid "If you do not have ``pip`` installed in your version of Python, install it::" msgstr "ãŠä½¿ã„ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Python ã« ``pip`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„å ´åˆã¯ã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:543 +#: ../../rst/installation_guide/intro_installation.rst:537 msgid "Ansible also uses the following Python modules that need to be installed [1]_:" msgstr "Ansible ã¯ã€ä»¥ä¸‹ã® Python モジュールも使用ã—ã€ã“ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚‚インストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ [1]_。" -#: ../../rst/installation_guide/intro_installation.rst:549 +#: ../../rst/installation_guide/intro_installation.rst:543 msgid "To update the ``devel`` branch of ``ansible-core`` on your local machine, use pull-with-rebase so any local changes are replayed." msgstr "ãƒãƒ¼ã‚«ãƒ«ãƒžã‚·ãƒ³ã§ ``ansible-core`` ã® ``devel`` ブランãƒã‚’æ›´æ–°ã™ã‚‹ã«ã¯ã€ãƒãƒ¼ã‚«ãƒ«ã®å¤‰æ›´ãŒå†ç”Ÿã•ã‚Œã‚‹ã‚ˆã†ã« pull-with-rebase を使用ã—ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:560 +#: ../../rst/installation_guide/intro_installation.rst:554 msgid "After you run the the env-setup script, you will be running from the source code. The default inventory file will be ``/etc/ansible/hosts``. You can optionally specify an inventory file (see :ref:`inventory`) other than ``/etc/ansible/hosts``:" msgstr "env-setup スクリプトã®å®Ÿè¡Œå¾Œã«ã€ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã‹ã‚‰å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚デフォルトã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ•ã‚¡ã‚¤ãƒ«ã¯ ``/etc/ansible/hosts`` ã«ãªã‚Šã¾ã™ã€‚å¿…è¦ã«å¿œã˜ã¦ã€``/etc/ansible/hosts`` 以外ã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ•ã‚¡ã‚¤ãƒ«ã‚’指定ã§ãã¾ã™ (:ref:`inventory` ã‚’å‚ç…§)。" -#: ../../rst/installation_guide/intro_installation.rst:567 +#: ../../rst/installation_guide/intro_installation.rst:561 msgid "You can read more about the inventory file at :ref:`inventory`." msgstr "インベントリーファイルã®è©³ç´°ã¯ã€:ref:`inventory`ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/installation_guide/intro_installation.rst:570 +#: ../../rst/installation_guide/intro_installation.rst:564 msgid "Confirming your installation" msgstr "インストールã®ç¢ºèª" -#: ../../rst/installation_guide/intro_installation.rst:572 +#: ../../rst/installation_guide/intro_installation.rst:566 msgid "Whatever method of installing Ansible you chose, you can test that it is installed correctly with a ping command:" msgstr "é¸æŠžã—㟠Ansible ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«æ–¹æ³•ã«é–¢ä¿‚ãªãã€ping コマンドを使用ã—ã¦æ£ã—ãインストールã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’テストã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:578 +#: ../../rst/installation_guide/intro_installation.rst:572 msgid "You can also use \"sudo make install\"." msgstr "「sudo make installã€ã‚‚使用ã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:583 +#: ../../rst/installation_guide/intro_installation.rst:577 msgid "Finding tarballs of tagged releases" msgstr "タグ付ã‘ã•ã‚ŒãŸãƒªãƒªãƒ¼ã‚¹ã® tarball ã®å ´æ‰€" -#: ../../rst/installation_guide/intro_installation.rst:585 +#: ../../rst/installation_guide/intro_installation.rst:579 msgid "If you are packaging Ansible or wanting to build a local package yourself, and you want to avoid a git checkout, you can use a tarball of a tagged release. You can download the latest stable release from PyPI's `ansible package page <https://pypi.org/project/ansible/>`_. If you need a specific older version, beta version, or release candidate, you can use the pattern ``pypi.python.org/packages/source/a/ansible/ansible-{{VERSION}}.tar.gz``. VERSION must be the full version number, for example 3.1.0 or 4.0.0b2. You can make VERSION a variable in your package managing system that you update in one place whenever you package a new version." msgstr "nsible をパッケージ化ã™ã‚‹å ´åˆã‚„ã€ãƒãƒ¼ã‚«ãƒ«ãƒ‘ッケージを自分ã§æ§‹ç¯‰ã—ã€git ã®ãƒã‚§ãƒƒã‚¯ã‚¢ã‚¦ãƒˆã‚’回é¿ã™ã‚‹å¿…è¦ãŒã‚ã‚‹å ´åˆã¯ã€ã‚¿ã‚°ä»˜ã‘ã•ã‚ŒãŸãƒªãƒªãƒ¼ã‚¹ã® tarball を使用ã§ãã¾ã™ã€‚PyPI ã® `ansible package page <https://pypi.org/project/ansible/>`_ ã‹ã‚‰æœ€æ–°ã®å®‰å®šã—ãŸãƒªãƒªãƒ¼ã‚¹ã‚’ダウンãƒãƒ¼ãƒ‰ã§ãã¾ã™ã€‚å¤ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã€beta ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã€ã¾ãŸã¯ãƒªãƒªãƒ¼ã‚¹å€™è£œãŒå¿…è¦ãªå ´åˆã¯ã€``pypi.python.org/packages/source/a/ansible/ansible-{{VERSION}}.tar.gz`` パターンを使用ã§ãã¾ã™ã€‚VERSION ã¯å®Œå…¨ãªãƒãƒ¼ã‚¸ãƒ§ãƒ³ç•ªå· (3.1.0ã€4.0.0b2 ãªã©) ã§ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚VERSION ã¯ã€æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’パッケージ化ã™ã‚‹ãŸã³ã« 1 カ所ã§æ›´æ–°ã™ã‚‹ãƒ‘ッケージ管ç†ã‚·ã‚¹ãƒ†ãƒ ã®å¤‰æ•°ã«ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:589 +#: ../../rst/installation_guide/intro_installation.rst:583 msgid "If you are creating your own Ansible package, you must also download or package ``ansible-core`` (or ``ansible-base`` for packages based on 2.10.x) from PyPI as part of your Ansible package. You must specify a particular version. Visit the PyPI project pages to download files for `ansible-core <https://pypi.org/project/ansible-core/>`_ or `ansible-base <https://pypi.org/project/ansible-base/>`_." msgstr "独自㮠Ansible パッケージを作æˆã™ã‚‹å ´åˆã¯ã€Ansible パッケージã®ä¸€éƒ¨ã¨ã—㦠PyPI ã‹ã‚‰ ``ansible-core`` (ã¾ãŸã¯ ``ansible-base`` 2.10.x ã«åŸºã¥ãパッケージã®å ´åˆ) をダウンãƒãƒ¼ãƒ‰ã¾ãŸã¯ãƒ‘ッケージ化ã™ã‚‹å¿…è¦ã‚‚ã‚ã‚Šã¾ã™ã€‚特定ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚PyPI プãƒã‚¸ã‚§ã‚¯ãƒˆãƒšãƒ¼ã‚¸ã«ã‚¢ã‚¯ã‚»ã‚¹ã—ã¦ã€`ansible-core <https://pypi.org/project/ansible-core/>`_ ã¾ãŸã¯ `ansible-base <https://pypi.org/project/ansible-base/>`_ ã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’ダウンãƒãƒ¼ãƒ‰ã—ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:591 +#: ../../rst/installation_guide/intro_installation.rst:585 msgid "These releases are also tagged in the `git repository <https://github.com/ansible/ansible/releases>`_ with the release version." msgstr "ã“れらã®ãƒªãƒªãƒ¼ã‚¹ã¯ã€`git リãƒã‚¸ãƒˆãƒªãƒ¼ <https://github.com/ansible/ansible/releases>`_ ã§ã‚‚リリースãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã‚¿ã‚°ä»˜ã‘ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:597 +#: ../../rst/installation_guide/intro_installation.rst:591 msgid "Adding Ansible command shell completion" msgstr "Ansible コマンドシェル補完ã®è¿½åŠ " -#: ../../rst/installation_guide/intro_installation.rst:599 +#: ../../rst/installation_guide/intro_installation.rst:593 msgid "As of Ansible 2.9, you can add shell completion of the Ansible command line utilities by installing an optional dependency called ``argcomplete``. ``argcomplete`` supports bash, and has limited support for zsh and tcsh." msgstr "Ansible 2.9 ã®æ™‚点ã§ã€``argcomplete`` ã¨å‘¼ã°ã‚Œã‚‹ä»»æ„ã®ä¾å˜é–¢ä¿‚をインストールã—ã¦ã€Ansible コマンドラインユーティリティーã®ã‚·ã‚§ãƒ«è£œå®Œã‚’è¿½åŠ ã§ãã¾ã™ã€‚``argcomplete`` 㯠bash をサãƒãƒ¼ãƒˆã—ã€åˆ¶é™ä»˜ã㧠zsh ãŠã‚ˆã³ tcsh ã®ã‚µãƒãƒ¼ãƒˆã‚’サãƒãƒ¼ãƒˆã—ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:601 +#: ../../rst/installation_guide/intro_installation.rst:595 msgid "You can install ``python-argcomplete`` from EPEL on Red Hat Enterprise based distributions, and or from the standard OS repositories for many other distributions." msgstr "``python-argcomplete`` ã¯ã€Red Hat Enterprise ベースã®ãƒ‡ã‚£ã‚¹ãƒˆãƒªãƒ“ューションã§ã¯ EPEL ã‹ã‚‰ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ãã€ãã®ä»–ã®å¤šãã®ãƒ‡ã‚£ã‚¹ãƒˆãƒªãƒ“ューションã§ã¯æ¨™æº– OS リãƒã‚¸ãƒˆãƒªãƒ¼ã§å…¥æ‰‹ã§ãã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:603 +#: ../../rst/installation_guide/intro_installation.rst:597 msgid "For more information about installation and configuration, see the `argcomplete documentation <https://kislyuk.github.io/argcomplete/>`_." msgstr "インストールã¨è¨å®šã®è©³ç´°ã¯ã€`argcomplete ドã‚ュメント <https://kislyuk.github.io/argcomplete/>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/installation_guide/intro_installation.rst:606 +#: ../../rst/installation_guide/intro_installation.rst:600 msgid "Installing ``argcomplete`` on RHEL, CentOS, or Fedora" msgstr "RHELã€CentOSã€ã¾ãŸã¯ Fedora ã¸ã® ``argcomplete`` ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/installation_guide/intro_installation.rst:614 +#: ../../rst/installation_guide/intro_installation.rst:608 msgid "On RHEL and CentOS:" msgstr "RHEL ãŠã‚ˆã³ CentOS ã®å ´åˆ:" -#: ../../rst/installation_guide/intro_installation.rst:623 +#: ../../rst/installation_guide/intro_installation.rst:617 msgid "Installing ``argcomplete`` with ``apt``" msgstr "``apt`` を使用ã—㟠``argcomplete`` ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/installation_guide/intro_installation.rst:631 +#: ../../rst/installation_guide/intro_installation.rst:625 msgid "Installing ``argcomplete`` with ``pip``" msgstr "``pip`` を使用ã—㟠``argcomplete`` ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/installation_guide/intro_installation.rst:638 +#: ../../rst/installation_guide/intro_installation.rst:632 msgid "Configuring ``argcomplete``" msgstr "``argcomplete`` ã®è¨å®š" -#: ../../rst/installation_guide/intro_installation.rst:640 +#: ../../rst/installation_guide/intro_installation.rst:634 msgid "There are 2 ways to configure ``argcomplete`` to allow shell completion of the Ansible command line utilities: globally or per command." msgstr "Ansible コマンドラインユーティリティーã®ã‚·ã‚§ãƒ«è£œå®Œã‚’å¯èƒ½ã«ã™ã‚‹ ``argcomplete`` ã®è¨å®šæ–¹æ³•ã¯ã€2 通りã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:643 +#: ../../rst/installation_guide/intro_installation.rst:637 msgid "Global configuration" msgstr "ã‚°ãƒãƒ¼ãƒãƒ«è¨å®š" -#: ../../rst/installation_guide/intro_installation.rst:645 +#: ../../rst/installation_guide/intro_installation.rst:639 msgid "Global completion requires bash 4.2." msgstr "ã‚°ãƒãƒ¼ãƒãƒ«è£œå®Œã«ã¯ bash 4.2 ãŒå¿…è¦ã§ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:651 +#: ../../rst/installation_guide/intro_installation.rst:645 msgid "This will write a bash completion file to a global location. Use ``--dest`` to change the location." msgstr "ã“ã‚Œã«ã‚ˆã‚Šã€bash 補完ファイルãŒã‚°ãƒãƒ¼ãƒãƒ«ãƒã‚±ãƒ¼ã‚·ãƒ§ãƒ³ã«æ›¸ãè¾¼ã¾ã‚Œã¾ã™ã€‚ãƒã‚±ãƒ¼ã‚·ãƒ§ãƒ³ã‚’変更ã™ã‚‹ã«ã¯ ``--dest`` を使用ã—ã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:654 +#: ../../rst/installation_guide/intro_installation.rst:648 msgid "Per command configuration" msgstr "コマンドã”ã¨ã®è¨å®š" -#: ../../rst/installation_guide/intro_installation.rst:656 +#: ../../rst/installation_guide/intro_installation.rst:650 msgid "If you do not have bash 4.2, you must register each script independently." msgstr "bash 4.2 ãŒãªã„å ´åˆã¯ã€å„スクリプトを個別ã«ç™»éŒ²ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:670 +#: ../../rst/installation_guide/intro_installation.rst:664 msgid "You should place the above commands into your shells profile file such as ``~/.profile`` or ``~/.bash_profile``." msgstr "上記ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’ã€``~/.profile``ã€``~/.bash_profile`` ãªã©ã®ã‚·ã‚§ãƒ«ãƒ—ãƒãƒ•ã‚¡ã‚¤ãƒ«ãƒ•ã‚¡ã‚¤ãƒ«ã«ç½®ãå¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/installation_guide/intro_installation.rst:673 +#: ../../rst/installation_guide/intro_installation.rst:667 msgid "Using ``argcomplete`` with zsh or tcsh" msgstr "zsh ã¾ãŸã¯ tcsh 㧠``argcomplete`` を使用" -#: ../../rst/installation_guide/intro_installation.rst:675 +#: ../../rst/installation_guide/intro_installation.rst:669 msgid "See the `argcomplete documentation <https://kislyuk.github.io/argcomplete/>`_." msgstr "`argcomplete ドã‚ュメント <https://kislyuk.github.io/argcomplete/>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/installation_guide/intro_installation.rst:680 +#: ../../rst/installation_guide/intro_installation.rst:674 msgid ":ref:`intro_adhoc`" msgstr ":ref:`intro_adhoc`" -#: ../../rst/installation_guide/intro_installation.rst:681 +#: ../../rst/installation_guide/intro_installation.rst:675 msgid "Examples of basic commands" msgstr "基本コマンドã®ä¾‹" -#: ../../rst/installation_guide/intro_installation.rst:682 +#: ../../rst/installation_guide/intro_installation.rst:676 msgid ":ref:`working_with_playbooks`" msgstr ":ref:`working_with_playbooks`" -#: ../../rst/installation_guide/intro_installation.rst:683 +#: ../../rst/installation_guide/intro_installation.rst:677 msgid "Learning ansible's configuration management language" msgstr "Ansible ã®è¨å®šç®¡ç†è¨€èªžã®æ¦‚è¦" -#: ../../rst/installation_guide/intro_installation.rst:684 +#: ../../rst/installation_guide/intro_installation.rst:678 msgid ":ref:`installation_faqs`" msgstr ":ref:`installation_faqs`" -#: ../../rst/installation_guide/intro_installation.rst:685 +#: ../../rst/installation_guide/intro_installation.rst:679 msgid "Ansible Installation related to FAQs" msgstr "FAQ ã«é–¢é€£ã™ã‚‹ Ansible インストール" -#: ../../rst/installation_guide/intro_installation.rst:686 +#: ../../rst/installation_guide/intro_installation.rst:680 msgid "`Mailing List <https://groups.google.com/group/ansible-project>`_" msgstr "`メーリングリスト <https://groups.google.com/group/ansible-project>`_" -#: ../../rst/installation_guide/intro_installation.rst:687 +#: ../../rst/installation_guide/intro_installation.rst:681 msgid "Questions? Help? Ideas? Stop by the list on Google Groups" msgstr "ã”質å•ã¯ã”ã–ã„ã¾ã™ã‹ã€‚サãƒãƒ¼ãƒˆãŒå¿…è¦ã§ã™ã‹ã€‚ã”æ案ã¯ã”ã–ã„ã¾ã™ã‹ã€‚Google グループã®ä¸€è¦§ã‚’ã”覧ãã ã•ã„。" -#: ../../rst/installation_guide/intro_installation.rst:688 +#: ../../rst/installation_guide/intro_installation.rst:682 msgid ":ref:`communication_irc`" msgstr ":ref:`communication_irc`" -#: ../../rst/installation_guide/intro_installation.rst:689 +#: ../../rst/installation_guide/intro_installation.rst:683 msgid "How to join Ansible chat channels" msgstr "Ansible ãƒãƒ£ãƒƒãƒˆãƒãƒ£ãƒ³ãƒãƒ«ã¸ã®å‚åŠ æ–¹æ³•" -#: ../../rst/installation_guide/intro_installation.rst:691 +#: ../../rst/installation_guide/intro_installation.rst:685 msgid "``paramiko`` was included in Ansible's ``requirements.txt`` prior to 2.8." msgstr "``paramiko`` ã¯ã€2.8 以å‰ã® Ansible ã® ``requirements.txt`` ã«åŒæ¢±ã•ã‚Œã¦ã„ã¾ã™ã€‚" @@ -866,3 +862,12 @@ msgstr "``paramiko`` ã¯ã€2.8 以å‰ã® Ansible ã® ``requirements.txt`` ã«åŒ #~ msgid "If you have issues with the \"pycrypto\" package install on macOS, then you may need to try ``CC=clang sudo -E pip install pycrypto``." #~ msgstr "MacOS ã¸ã®ã€Œpycryptoã€ãƒ‘ッケージã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã«å•é¡ŒãŒã‚ã‚‹å ´åˆã¯ã€``CC=clang sudo -E pip install pycrypto`` ã®è©¦è¡ŒãŒå¿…è¦ã«ãªã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚" +#~ msgid "RPMs for RHEL 7 and RHEL 8 are available from the `Ansible Engine repository <https://access.redhat.com/articles/3174981>`_." +#~ msgstr "RHEL 7 ãŠã‚ˆã³ RHEL 8 ã® RPM ã¯ã€`Ansible Engine リãƒã‚¸ãƒˆãƒªãƒ¼ <https://access.redhat.com/articles/3174981>`_ ã‹ã‚‰å…¥æ‰‹ã§ãã¾ã™ã€‚" + +#~ msgid "To enable the Ansible Engine repository for RHEL 8, run the following command:" +#~ msgstr "RHEL 8 用㮠Ansible Engine リãƒã‚¸ãƒˆãƒªãƒ¼ã‚’有効ã«ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" + +#~ msgid "To enable the Ansible Engine repository for RHEL 7, run the following command:" +#~ msgstr "RHEL 7 用㮠Ansible Engine リãƒã‚¸ãƒˆãƒªãƒ¼ã‚’有効ã«ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" + diff --git a/docs/docsite/rst/locales/ja/LC_MESSAGES/network.po b/docs/docsite/rst/locales/ja/LC_MESSAGES/network.po index 37650946..20263767 100644 --- a/docs/docsite/rst/locales/ja/LC_MESSAGES/network.po +++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/network.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Ansible devel\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-10-05 13:53+0200\n" +"POT-Creation-Date: 2021-11-09 14:07+0100\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" @@ -801,13 +801,14 @@ msgid "Your tests should detect resources (such as interfaces) at runtime rather msgstr "テストã¯ã€(インターフェースãªã©ã®) リソースをテストã«ãƒãƒ¼ãƒ‰ã‚³ãƒ¼ãƒ‡ã‚£ãƒ³ã‚°ã™ã‚‹ã®ã§ã¯ãªãã€ãƒ©ãƒ³ã‚¿ã‚¤ãƒ 時ã«ãƒªã‚½ãƒ¼ã‚¹ã‚’検出ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ãƒ†ã‚¹ãƒˆã¯ã•ã¾ã–ã¾ãªã‚·ã‚¹ãƒ†ãƒ ã§å®Ÿè¡Œã§ãã¾ã™ã€‚" #: ../../rst/network/dev_guide/developing_resource_modules_network.rst:631 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:203 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:262 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:298 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:327 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:358 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:405 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:611 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:205 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:264 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:300 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:329 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:360 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:409 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:615 +#: ../../rst/network/user_guide/network_working_with_command_output.rst:29 msgid "For example:" msgstr "例:" @@ -968,7 +969,7 @@ msgid "Documenting new network platforms" msgstr "æ–°ã—ã„ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ—ラットフォームã®ãƒ‰ã‚ュメント化" #: ../../rst/network/dev_guide/documenting_modules_network.rst:11 -msgid "When you create network modules for a new platform, or modify the connections provided by an existing network platform(such as ``network_cli`` and ``httpapi``), you also need to update the :ref:`settings_by_platform` table and add or modify the Platform Options file for your platform." +msgid "When you create network modules for a new platform, or modify the connections provided by an existing network platform (such as ``network_cli`` and ``httpapi``), you also need to update the :ref:`settings_by_platform` table and add or modify the Platform Options file for your platform." msgstr "æ–°ã—ã„プラットフォーム用ã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’作æˆã™ã‚‹å ´åˆã‚„ã€æ—¢å˜ã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ—ラットフォーム(``network_cli``ã€``httpapi`` ãªã©) ãŒæä¾›ã™ã‚‹æŽ¥ç¶šã‚’変更ã™ã‚‹å ´åˆã¯ã€:ref:`settings_by_platform` テーブルを更新ã—ã¦ã€ãƒ—ラットフォーム㮠Platform Options ãƒ•ã‚¡ã‚¤ãƒ«ã‚’è¿½åŠ ã¾ãŸã¯å¤‰æ›´ã™ã‚‹ã“ã¨ã‚‚å¿…è¦ã§ã™ã€‚" #: ../../rst/network/dev_guide/documenting_modules_network.rst:13 @@ -2998,7 +2999,7 @@ msgid "SSH key issues" msgstr "SSH ã‚ーã®å•é¡Œ" #: ../../rst/network/user_guide/network_debug_troubleshooting.rst -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:439 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:443 msgid "Timeout issues" msgstr "タイムアウトã®å•é¡Œ" @@ -3011,7 +3012,7 @@ msgid "May actually be masking a authentication issue" msgstr "èªè¨¼ã®å•é¡Œã‚’実際ã«ãƒžã‚¹ã‚¯ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚‹" #: ../../rst/network/user_guide/network_debug_troubleshooting.rst -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:600 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:604 msgid "Playbook issues" msgstr "Playbook ã®å•é¡Œ" @@ -3032,13 +3033,13 @@ msgid "Enabling Networking logging and how to read the logfile" msgstr "ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒã‚®ãƒ³ã‚°ã®æœ‰åŠ¹åŒ–ã¨ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã®èªã¿å–り方法" #: ../../rst/network/user_guide/network_debug_troubleshooting.rst:39 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:96 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:156 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:199 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:256 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:294 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:321 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:426 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:98 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:158 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:201 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:258 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:296 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:323 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:430 msgid "**Platforms:** Any" msgstr "**プラットフォーム:** ä»»æ„" @@ -3051,545 +3052,545 @@ msgid "Because logging is very verbose, it is disabled by default. It can be ena msgstr "ãƒã‚®ãƒ³ã‚°ã¯éžå¸¸ã«è©³ç´°ãªãŸã‚ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã¯ç„¡åŠ¹ã«ãªã£ã¦ã„ã¾ã™ã€‚ã“ã‚Œã¯ã€ansible-controller ã® :envvar:`ANSIBLE_LOG_PATH` オプションãŠã‚ˆã³ :envvar:`ANSIBLE_DEBUG` オプションã§æœ‰åŠ¹ã«ã§ãã¾ã™ã€‚ã“ã‚Œã¯ã€``ansible-playbook`` を実行ã—ã¦ã„るマシンã§ã™ã€‚" #: ../../rst/network/user_guide/network_debug_troubleshooting.rst:45 -msgid "Before running ``ansible-playbook``, run the following commands to enable logging::" +msgid "Before running ``ansible-playbook``, run the following commands to enable logging:" msgstr "``ansible-playbook`` を実行ã™ã‚‹å‰ã«ã€ä»¥ä¸‹ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¦ãƒã‚®ãƒ³ã‚°ã‚’有効ã«ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:55 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:57 msgid "After Ansible has finished running you can inspect the log file which has been created on the ansible-controller:" msgstr "Ansible ã®å®Ÿè¡ŒãŒå®Œäº†ã—ãŸã‚‰ã€ansible-controller ã§ä½œæˆã•ã‚ŒãŸãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã‚’確èªã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:73 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:75 msgid "From the log notice:" msgstr "ã“ã®ãƒã‚°é€šçŸ¥ã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:75 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:77 msgid "``p=28990`` Is the PID (Process ID) of the ``ansible-connection`` process" msgstr "``p=28990`` ``ansible-connection`` プãƒã‚»ã‚¹ã® PID (プãƒã‚»ã‚¹ ID) ã§ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:76 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:78 msgid "``u=fred`` Is the user `running` ansible, not the remote-user you are attempting to connect as" msgstr "``u=fred`` ansible ã‚’ `実行` ã—ã¦ã„るユーザーã§ã™ (接続ã—よã†ã¨ã—ã¦ã„るリモートユーザーã§ã¯ã‚ã‚Šã¾ã›ã‚“)。" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:77 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:79 msgid "``creating new control socket for host veos01:22 as user admin`` host:port as user" msgstr "``ホスト veos01:22 ã®æ–°ã—ã„コントãƒãƒ¼ãƒ«ã‚½ã‚±ãƒƒãƒˆã‚’ユーザー管ç†è€…`` ユーザーã¨ã—㦠host:port" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:78 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:80 msgid "``control socket path is`` location on disk where the persistent connection socket is created" msgstr "``control socket path is`` 永続接続ソケットãŒä½œæˆã•ã‚Œã‚‹ãƒ‡ã‚£ã‚¹ã‚¯ã®å ´æ‰€" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:79 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:81 msgid "``using connection plugin network_cli`` Informs you that persistent connection is being used" msgstr "``using connection plugin network_cli`` 永続接続ãŒä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹ã“ã¨ãŒé€šçŸ¥ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:80 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:82 msgid "``connection established to veos01 in 0:00:22.580626`` Time taken to obtain a shell on the remote device" msgstr "``connection established to veos01 in 0:00:22.580626`` リモートデãƒã‚¤ã‚¹ã§ã‚·ã‚§ãƒ«ã®å–å¾—ã«ã‹ã‹ã£ãŸæ™‚é–“" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:83 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:85 msgid "Port None ``creating new control socket for host veos01:None``" msgstr "ãƒãƒ¼ãƒˆãªã— ``ホスト veos01:22 ã®æ–°ã—ã„コントãƒãƒ¼ãƒ«ã‚½ã‚±ãƒƒãƒˆã‚’ユーザー管ç†è€…``" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:85 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:87 msgid "If the log reports the port as ``None`` this means that the default port is being used. A future Ansible release will improve this message so that the port is always logged." msgstr "ãƒã‚°ã§ãƒãƒ¼ãƒˆãŒ ``None`` ã¨ã—ã¦å ±å‘Šã•ã‚Œã‚‹å ´åˆã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã®ãƒãƒ¼ãƒˆãŒä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚今後㮠Ansible リリースã§ã¯ã€ãƒãƒ¼ãƒˆãŒå¸¸ã«ãƒã‚°ã«è¨˜éŒ²ã•ã‚Œã‚‹ã‚ˆã†ã«ã“ã®ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãŒæ”¹å–„ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:88 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:90 msgid "Because the log files are verbose, you can use grep to look for specific information. For example, once you have identified the ``pid`` from the ``creating new control socket for host`` line you can search for other connection log entries::" msgstr "ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã¯å†—é•·ã§ã‚ã‚‹ãŸã‚ã€grepを使用ã—ã¦ç‰¹å®šã®æƒ…å ±ã‚’æ¤œç´¢ã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€``creating new control socket for host`` è¡Œã‹ã‚‰ ``pid`` を特定ã—ãŸã‚‰ã€ä»–ã®æŽ¥ç¶šãƒã‚°ã‚¨ãƒ³ãƒˆãƒªãƒ¼ã‚’検索ã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:94 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:96 msgid "Enabling Networking device interaction logging" msgstr "ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ‡ãƒã‚¤ã‚¹ã®å¯¾è©±ãƒã‚®ãƒ³ã‚°ã®æœ‰åŠ¹åŒ–" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:98 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:100 msgid "Ansible includes logging of device interaction in the log file to help diagnose and troubleshoot issues regarding Ansible Networking modules. The messages are logged in the file pointed to by the ``log_path`` configuration option in the Ansible configuration file or by setting the :envvar:`ANSIBLE_LOG_PATH`." msgstr "Ansible ã«ã¯ã€Ansible ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«é–¢ã™ã‚‹å•é¡Œã®è¨ºæ–ãŠã‚ˆã³ãƒˆãƒ©ãƒ–ルシューティングã«å½¹ç«‹ã¤ã€ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«å†…ã®ãƒ‡ãƒã‚¤ã‚¹ã®å¯¾è©±ã®ãƒã‚°ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ã“ã®ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã¯ã€Ansible è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã® ``log_path`` è¨å®šã‚ªãƒ—ションã§æŒ‡å®šã•ã‚Œã¦ã„るファイルã«è¨˜éŒ²ã•ã‚Œã‚‹ã‹ã€:envvar:`ANSIBLE_LOG_PATH` ã‚’è¨å®šã™ã‚‹ã¨è¨˜éŒ²ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:103 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:105 msgid "The device interaction messages consist of command executed on the target device and the returned response. Since this log data can contain sensitive information including passwords in plain text it is disabled by default. Additionally, in order to prevent accidental leakage of data, a warning will be shown on every task with this setting enabled, specifying which host has it enabled and where the data is being logged." msgstr "デãƒã‚¤ã‚¹ã‚¤ãƒ³ã‚¿ãƒ©ã‚¯ã‚·ãƒ§ãƒ³ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã¯ã€ã‚¿ãƒ¼ã‚²ãƒƒãƒˆãƒ‡ãƒã‚¤ã‚¹ä¸Šã§å®Ÿè¡Œã•ã‚ŒãŸã‚³ãƒžãƒ³ãƒ‰ã¨è¿”ã•ã‚ŒãŸå¿œç”ã§æ§‹æˆã•ã‚Œã¾ã™ã€‚ã“ã®ãƒã‚°ãƒ‡ãƒ¼ã‚¿ã«ã¯ã€ãƒ‘スワードãªã©ã®æ©Ÿå¯†æƒ…å ±ãŒãƒ—レーンテã‚ストã®å½¢å¼ã§å«ã¾ã‚Œã‚‹å¯èƒ½æ€§ãŒã‚ã‚‹ãŸã‚ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã¯ç„¡åŠ¹ã«ãªã£ã¦ã„ã¾ã™ã€‚ã¾ãŸã€èª¤ã£ã¦ãƒ‡ãƒ¼ã‚¿ãŒæ¼æ´©ã—ãªã„よã†ã«ã€ã“ã®è¨å®šãŒæœ‰åŠ¹ã«ãªã£ã¦ã„ã‚‹ã™ã¹ã¦ã®ã‚¿ã‚¹ã‚¯ã«è¦å‘ŠãŒè¡¨ç¤ºã•ã‚Œã€æœ‰åŠ¹ã«ãªã£ã¦ã„るホストã¨ãƒ‡ãƒ¼ã‚¿ãŒè¨˜éŒ²ã•ã‚Œã‚‹å ´æ‰€ãŒæŒ‡å®šã•ã‚Œã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:108 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:110 msgid "Be sure to fully understand the security implications of enabling this option. The device interaction logging can be enabled either globally by setting in configuration file or by setting environment or enabled on per task basis by passing a special variable to the task." msgstr "ã“ã®ã‚ªãƒ—ションを有効ã«ã—ãŸå ´åˆã®ã‚»ã‚ュリティーã¸ã®å½±éŸ¿ã‚’完全ã«ç†è§£ã—ã¦ãã ã•ã„。デãƒã‚¤ã‚¹å¯¾è©±ãƒã‚®ãƒ³ã‚°ã¯ã€è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã§ã‚°ãƒãƒ¼ãƒãƒ«ã«è¨å®šã™ã‚‹ã‹ã€ç’°å¢ƒã‚’è¨å®šã—ã¦æœ‰åŠ¹ã«ã™ã‚‹ã‹ã€ã¾ãŸã¯ç‰¹æ®Šãªå¤‰æ•°ã‚’タスクã«æ¸¡ã™ã“ã¨ã§ã‚¿ã‚¹ã‚¯ã”ã¨ã«æœ‰åŠ¹ã«ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:110 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:112 msgid "Before running ``ansible-playbook`` run the following commands to enable logging:" msgstr "``ansible-playbook`` を実行ã™ã‚‹å‰ã«ã€ä»¥ä¸‹ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¦ãƒã‚®ãƒ³ã‚°ã‚’有効ã«ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:118 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:120 msgid "Enable device interaction logging for a given task" msgstr "特定ã®ã‚¿ã‚¹ã‚¯ã®ãƒ‡ãƒã‚¤ã‚¹å¯¾è©±ãƒã‚°ã‚’有効ã«ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:130 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:756 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:823 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:132 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:760 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:827 msgid "To make this a global setting, add the following to your ``ansible.cfg`` file:" msgstr "ã“ã®è¨å®šã‚’ã‚°ãƒãƒ¼ãƒãƒ«ã«ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®è¨å®šã‚’ ``ansible.cfg`` ファイルã«è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:137 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:139 msgid "or enable the environment variable `ANSIBLE_PERSISTENT_LOG_MESSAGES`:" msgstr "ã¾ãŸã¯ã€ç’°å¢ƒå¤‰æ•° `ANSIBLE_PERSISTENT_LOG_MESSAGES` を有効ã«ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:144 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:146 msgid "If the task is failing on connection initialization itself, you should enable this option globally. If an individual task is failing intermittently this option can be enabled for that task itself to find the root cause." msgstr "タスク自体ãŒæŽ¥ç¶šã®åˆæœŸåŒ–ã«å¤±æ•—ã—ã¦ã„ã‚‹å ´åˆã¯ã€ã“ã®ã‚ªãƒ—ションをグãƒãƒ¼ãƒãƒ«ã«æœ‰åŠ¹ã«ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚個々ã®ã‚¿ã‚¹ã‚¯ãŒæ–続的ã«å¤±æ•—ã™ã‚‹å ´åˆã¯ã€ãã®ã‚¿ã‚¹ã‚¯è‡ªä½“ã«å¯¾ã—ã¦ã“ã®ã‚ªãƒ—ションを有効ã«ã—ã¦ã€æ ¹æœ¬åŽŸå› を見ã¤ã‘ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:147 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:149 msgid "After Ansible has finished running you can inspect the log file which has been created on the ansible-controller" msgstr "Ansible ã®å®Ÿè¡ŒãŒå®Œäº†ã—ãŸã‚‰ã€ansible-controller ã§ä½œæˆã•ã‚ŒãŸãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã‚’確èªã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:149 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:151 msgid "Be sure to fully understand the security implications of enabling this option as it can log sensitive information in log file thus creating security vulnerability." msgstr "ã“ã®ã‚ªãƒ—ションを有効ã«ã™ã‚‹ã¨ã€ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã«æ©Ÿå¯†æƒ…å ±ãŒè¨˜éŒ²ã•ã‚Œã€ã‚»ã‚ュリティ上ã®è„†å¼±æ€§ãŒç”Ÿã˜ã‚‹å¯èƒ½æ€§ãŒã‚ã‚‹ãŸã‚ã€ã‚»ã‚ュリティー上ã®å½±éŸ¿ã‚’å分ã«ç†è§£ã—ã¦ãã ã•ã„。" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:154 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:156 msgid "Isolating an error" msgstr "エラーã®åˆ†é›¢" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:158 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:160 msgid "As with any effort to troubleshoot it's important to simplify the test case as much as possible." msgstr "トラブルシューティングã«ãŠã‘ã‚‹ã‚らゆる作æ¥ã¨åŒæ§˜ã«ã€ãƒ†ã‚¹ãƒˆã‚±ãƒ¼ã‚¹ã‚’ã§ãã‚‹ã ã‘簡略化ã™ã‚‹ã“ã¨ãŒé‡è¦ã§ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:160 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:162 msgid "For Ansible this can be done by ensuring you are only running against one remote device:" msgstr "Ansible ã®å ´åˆã¯ã€1 ã¤ã®ãƒªãƒ¢ãƒ¼ãƒˆãƒ‡ãƒã‚¤ã‚¹ã«å¯¾ã—ã¦ã®ã¿å®Ÿè¡Œã™ã‚‹ã‚ˆã†ã«ã™ã‚‹ã“ã¨ã§ã“れを行ã†ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:162 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:164 msgid "Using ``ansible-playbook --limit switch1.example.net...``" msgstr "``ansible-playbook --limit switch1.example.net...`` ã®ä½¿ç”¨" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:163 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:165 msgid "Using an ad hoc ``ansible`` command" msgstr "``ansible`` アドホックコマンドã®ä½¿ç”¨" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:165 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:167 msgid "`ad hoc` refers to running Ansible to perform some quick command using ``/usr/bin/ansible``, rather than the orchestration language, which is ``/usr/bin/ansible-playbook``. In this case we can ensure connectivity by attempting to execute a single command on the remote device::" msgstr "`ad hoc` ã¯ã€ã‚ªãƒ¼ã‚±ã‚¹ãƒˆãƒ¬ãƒ¼ã‚·ãƒ§ãƒ³è¨€èªž ``/usr/bin/ansible-playbook`` ã§ã¯ãªãã€``/usr/bin/ansible`` を使用ã—ã¦ç°¡å˜ãªã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã™ã‚‹ãŸã‚ã« Ansible を実行ã™ã‚‹ã“ã¨ã‚’指ã—ã¾ã™ã€‚ã“ã®å ´åˆã¯ã€ãƒªãƒ¢ãƒ¼ãƒˆãƒ‡ãƒã‚¤ã‚¹ã§ 1 ã¤ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã™ã‚‹ã“ã¨ã§ã€æŽ¥ç¶šã‚’確èªã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:169 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:171 msgid "In the above example, we:" msgstr "上記ã®ä¾‹ã§ã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:171 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:173 msgid "connect to ``switch1.example.net`` specified in the inventory file ``inventory``" msgstr "インベントリーファイル ``inventory`` ã«æŒ‡å®šã•ã‚ŒãŸ ``switch1.example.net`` ã«æŽ¥ç¶šã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:172 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:174 msgid "use the module ``arista.eos.eos_command``" msgstr "``arista.eos.eos_command`` モジュールã®ä½¿ç”¨" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:173 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:175 msgid "run the command ``?``" msgstr "``?`` コマンドã®å®Ÿè¡Œ" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:174 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:176 msgid "connect using the username ``admin``" msgstr "ユーザーå ``admin`` を使用ã—ã¦æŽ¥ç¶š" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:175 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:177 msgid "inform the ``ansible`` command to prompt for the SSH password by specifying ``-k``" msgstr "``-k`` を指定ã—㦠SSH パスワードをè¦æ±‚ã™ã‚‹ã‚ˆã†ã«ã€``ansible`` コマンドã«é€šçŸ¥" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:177 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:179 msgid "If you have SSH keys configured correctly, you don't need to specify the ``-k`` parameter." msgstr "SSH ã‚ーãŒæ£ã—ãè¨å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€``-k`` パラメーターを指定ã™ã‚‹å¿…è¦ã¯ã‚ã‚Šã¾ã›ã‚“。" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:179 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:181 msgid "If the connection still fails you can combine it with the enable_network_logging parameter. For example:" msgstr "ãã‚Œã§ã‚‚接続ãŒå¤±æ•—ã—ãŸå ´åˆã¯ã€ã“れを enable_network_logging パラメーターã¨çµ„ã¿åˆã‚ã›ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:190 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:192 msgid "Then review the log file and find the relevant error message in the rest of this document." msgstr "次ã«ã€ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã‚’確èªã—ã€ã“ã®ãƒ‰ã‚ュメントã®æ®‹ã‚Šã®éƒ¨åˆ†ã§ã€é–¢é€£ã™ã‚‹ã‚¨ãƒ©ãƒ¼ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã‚’見ã¤ã‘ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:197 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:199 msgid "Troubleshooting socket path issues" msgstr "ソケットパスã®å•é¡Œã®ãƒˆãƒ©ãƒ–ルシューティング" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:201 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:203 msgid "The ``Socket path does not exist or cannot be found`` and ``Unable to connect to socket`` messages indicate that the socket used to communicate with the remote network device is unavailable or does not exist." msgstr "``Socket path does not exist or cannot be found`` メッセージãŠã‚ˆã³ ``Unable to connect to socket``メッセージã¯ã€ãƒªãƒ¢ãƒ¼ãƒˆãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ‡ãƒã‚¤ã‚¹ã¨ã®é€šä¿¡ã«ä½¿ç”¨ã•ã‚Œã‚‹ã‚½ã‚±ãƒƒãƒˆãŒåˆ©ç”¨ã§ããªã„ã‹ã€å˜åœ¨ã—ãªã„ã“ã¨ã‚’示ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:216 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:241 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:378 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:218 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:243 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:380 msgid "or" msgstr "ã¾ãŸã¯" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:229 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:283 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:309 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:335 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:369 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:419 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:450 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:476 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:502 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:513 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:539 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:623 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:795 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:231 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:285 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:311 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:337 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:371 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:423 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:454 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:480 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:506 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:517 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:543 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:627 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:799 msgid "Suggestions to resolve:" msgstr "解決ã™ã‚‹ãŸã‚ã®ãƒ’ント:" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:231 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:233 msgid "Verify that you have write access to the socket path described in the error message." msgstr "エラーメッセージã«è¨˜è¼‰ã•ã‚Œã¦ã„るソケットパスã¸ã®æ›¸ãè¾¼ã¿æ¨©é™ãŒã‚ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:233 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:235 msgid "Follow the steps detailed in :ref:`enable network logging <enable_network_logging>`." msgstr "「:ref:`ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒã‚®ãƒ³ã‚°ã®æœ‰åŠ¹åŒ– <enable_network_logging>`ã€è¨˜è¼‰ã•ã‚Œã‚‹æ‰‹é †ã«å¾“ã£ã¦ãã ã•ã„。" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:235 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:237 msgid "If the identified error message from the log file is:" msgstr "ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã‹ã‚‰ç‰¹å®šã•ã‚ŒãŸã‚¨ãƒ©ãƒ¼ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãŒä»¥ä¸‹ã®å ´åˆã¯ã€" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:247 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:249 msgid "Follow the steps detailed in :ref:`timeout issues <timeout_issues>`" msgstr "「:ref:`タイムアウトã®å•é¡Œ <timeout_issues>`ã€ã«è¨˜è¼‰ã®æ‰‹é †ã«å¾“ã£ã¦ãã ã•ã„。" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:253 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:255 msgid "Category \"Unable to open shell\"" msgstr "Category \"Unable to open shell\"" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:258 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:260 msgid "The ``unable to open shell`` message means that the ``ansible-connection`` daemon has not been able to successfully talk to the remote network device. This generally means that there is an authentication issue. It is a \"catch all\" message, meaning you need to enable :ref:`logging <a_note_about_logging>` to find the underlying issues." msgstr "``unable to open shell`` メッセージã¯ã€``ansible-connection`` デーモンãŒãƒªãƒ¢ãƒ¼ãƒˆãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ‡ãƒã‚¤ã‚¹ã¨æ£å¸¸ã«é€šä¿¡ã§ããªã‹ã£ãŸã“ã¨ã‚’示ã—ã¾ã™ã€‚ã“ã‚Œã¯é€šå¸¸ã€èªè¨¼ã®å•é¡ŒãŒã‚ã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚ã“ã‚Œã¯ã€Œcatch all (å…¨ã¦å–å¾—ã™ã‚‹)ã€ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã§ã™ã€‚ã¤ã¾ã‚Šã€:ref:`logging <a_note_about_logging>` を有効ã«ã—ã¦ã€æ ¹æœ¬çš„ãªå•é¡Œã‚’検出ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:270 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:272 msgid "or:" msgstr "ã¾ãŸã¯" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:285 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:287 msgid "Follow the steps detailed in enable_network_logging_." msgstr "enable_network_logging_ ã«è¨˜è¼‰ã®æ‰‹é †ã«å¾“ã„ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:287 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:289 msgid "Once you've identified the error message from the log file, the specific solution can be found in the rest of this document." msgstr "ãƒã‚°ãƒ•ã‚¡ã‚¤ãƒ«ã‹ã‚‰ã‚¨ãƒ©ãƒ¼ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãŒç‰¹å®šã§ããŸã‚‰ã€ç‰¹å®šã®è§£æ±ºæ–¹æ³•ã¯ã€æœ¬ã‚¬ã‚¤ãƒ‰ã®ãã®ä»–ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:292 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:294 msgid "Error: \"[Errno -2] Name or service not known\"" msgstr "Error: \"[Errno -2] Name or service not known\"" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:296 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:298 msgid "Indicates that the remote host you are trying to connect to can not be reached" msgstr "接続ã—よã†ã¨ã—ã¦ã„るリモートホストã«åˆ°é”ã§ããªã„ã“ã¨ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:311 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:313 msgid "If you are using the ``provider:`` options ensure that its suboption ``host:`` is set correctly." msgstr "``provider:`` オプションを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ã‚µãƒ–オプション ``host:`` ãŒæ£ã—ãè¨å®šã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:312 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:314 msgid "If you are not using ``provider:`` nor top-level arguments ensure your inventory file is correct." msgstr "``provider:`` ã¾ãŸã¯ãƒˆãƒƒãƒ—レベルã®å¼•æ•°ã‚’使用ã—ãªã„å ´åˆã«ã¯ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ•ã‚¡ã‚¤ãƒ«ãŒæ£ã—ã„ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:319 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:321 msgid "Error: \"Authentication failed\"" msgstr "Error: \"Authentication failed\"" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:323 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:325 msgid "Occurs if the credentials (username, passwords, or ssh keys) passed to ``ansible-connection`` (via ``ansible`` or ``ansible-playbook``) can not be used to connect to the remote device." msgstr "(``ansible`` ã¾ãŸã¯ ``ansible-playbook`` を使用ã—ã¦) ``ansible-connection`` ã«æ¸¡ã•ã‚Œã‚‹èªè¨¼æƒ…å ± (ユーザーåã€ãƒ‘スワードã€ã¾ãŸã¯ ssh ã‚ー) を使用ã—ã¦ãƒªãƒ¢ãƒ¼ãƒˆãƒ‡ãƒã‚¤ã‚¹ã«æŽ¥ç¶šã§ããªã„å ´åˆã«ç™ºç”Ÿã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:337 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:339 msgid "If you are specifying credentials via ``password:`` (either directly or via ``provider:``) or the environment variable `ANSIBLE_NET_PASSWORD` it is possible that ``paramiko`` (the Python SSH library that Ansible uses) is using ssh keys, and therefore the credentials you are specifying are being ignored. To find out if this is the case, disable \"look for keys\". This can be done like this:" msgstr "(直接ã¾ãŸã¯ ``provider:`` を使用ã—ã¦) ``password:`` ã§èªè¨¼æƒ…å ±ã‚’æŒ‡å®šã™ã‚‹å ´åˆã‚„ã€ç’°å¢ƒå¤‰æ•° `ANSIBLE_NET_PASSWORD` を指定ã™ã‚‹å ´åˆã¯ã€``paramiko`` (Ansible ãŒä½¿ç”¨ã™ã‚‹ Python SSH ライブラリー) ㌠ssh ã‚ーを使用ã—ã¦ã„ã‚‹å¯èƒ½æ€§ãŒã‚ã‚‹ãŸã‚ã€æŒ‡å®šã™ã‚‹èªè¨¼æƒ…å ±ãŒç„¡åŠ¹ã«ãªã‚Šã¾ã™ã€‚ã“れを確èªã™ã‚‹ã«ã¯ã€ã€Œlook for keysã€ã‚’無効ã«ã—ã¾ã™ã€‚ã“ã‚Œã¯æ¬¡ã®ã‚ˆã†ã«è¡Œã„ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:343 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:458 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:485 -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:550 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:345 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:462 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:489 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:554 msgid "To make this a permanent change, add the following to your ``ansible.cfg`` file:" msgstr "ã“れを永続的ã«è¡Œã†ã«ã¯ã€ä»¥ä¸‹ã‚’ ``ansible.cfg`` ファイルã«è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:352 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:354 msgid "Error: \"connecting to host <hostname> returned an error\" or \"Bad address\"" msgstr "Error: \"connecting to host <hostname> returned an error\" or \"Bad address\"" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:354 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:356 msgid "This may occur if the SSH fingerprint hasn't been added to Paramiko's (the Python SSH library) know hosts file." msgstr "ã“ã‚Œã¯ã€SSH フィンガープリント㌠Paramiko ã®æ—¢çŸ¥ã®ãƒ›ã‚¹ãƒˆãƒ•ã‚¡ã‚¤ãƒ« (Python SSH ライブラリー) ã«è¿½åŠ ã•ã‚Œã¦ã„ãªã„å ´åˆã«ç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:356 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:358 msgid "When using persistent connections with Paramiko, the connection runs in a background process. If the host doesn't already have a valid SSH key, by default Ansible will prompt to add the host key. This will cause connections running in background processes to fail." msgstr "Paramiko ã§æ°¸ç¶šçš„ãªæŽ¥ç¶šã‚’使用ã™ã‚‹å ´åˆã€æŽ¥ç¶šã¯ãƒãƒƒã‚¯ã‚°ãƒ©ã‚¦ãƒ³ãƒ‰ãƒ—ãƒã‚»ã‚¹ã§å®Ÿè¡Œã—ã¾ã™ã€‚ホストãŒæœ‰åŠ¹ãª SSH ã‚ーをæŒã£ã¦ã„ãªã„å ´åˆã€Ansible ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ãƒ›ã‚¹ãƒˆã‚ãƒ¼ã‚’è¿½åŠ ã™ã‚‹ã‚ˆã†ãƒ—ãƒãƒ³ãƒ—トを出ã—ã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ãƒãƒƒã‚¯ã‚°ãƒ©ã‚¦ãƒ³ãƒ‰ãƒ—ãƒã‚»ã‚¹ã§å®Ÿè¡Œä¸ã®æŽ¥ç¶šãŒå¤±æ•—ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:371 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:373 msgid "Use ``ssh-keyscan`` to pre-populate the known_hosts. You need to ensure the keys are correct." msgstr "``ssh-keyscan`` を使用ã—㦠known_hosts を事å‰ã«è¨å®šã—ã¾ã™ã€‚ã‚ーãŒæ£ã—ã„ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:380 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:382 msgid "You can tell Ansible to automatically accept the keys" msgstr "éµã‚’自動的ã«å—ã‘入れるよã†ã« Ansible ã«è¨å®šã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:382 -msgid "Environment variable method::" -msgstr "環境変数メソッド::" +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:384 +msgid "Environment variable method:" +msgstr "環境変数メソッド:" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:387 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:391 msgid "``ansible.cfg`` method:" msgstr "``ansible.cfg`` メソッド:" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:389 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:393 msgid "ansible.cfg" msgstr "ansible.cfg" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:403 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:407 msgid "Error: \"No authentication methods available\"" msgstr "Error: \"No authentication methods available\"" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:421 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:425 msgid "No password or SSH key supplied" msgstr "パスワードã¾ãŸã¯ SSH ã‚ーãŒæŒ‡å®šã•ã‚Œã¦ã„ãªã„" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:424 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:428 msgid "Clearing Out Persistent Connections" msgstr "永続的ãªæŽ¥ç¶šã‚’解除" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:428 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:432 msgid "In Ansible 2.3, persistent connection sockets are stored in ``~/.ansible/pc`` for all network devices. When an Ansible playbook runs, the persistent socket connection is displayed when verbose output is specified." msgstr "Ansible 2.3 ã§ã¯ã€ã™ã¹ã¦ã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ‡ãƒã‚¤ã‚¹ã®æ°¸ç¶šçš„ãªæŽ¥ç¶šã‚½ã‚±ãƒƒãƒˆãŒ ``~/.ansible/pc`` ã«ä¿å˜ã•ã‚Œã¾ã™ã€‚Ansible Playbook ãŒå®Ÿè¡Œã™ã‚‹ã¨ã€è©³ç´°ãªå‡ºåŠ›ãŒæŒ‡å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã«æ°¸ç¶šçš„ãªã‚½ã‚±ãƒƒãƒˆæŽ¥ç¶šãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:430 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:434 msgid "``<switch> socket_path: /home/fred/.ansible/pc/f64ddfa760``" msgstr "``<switch> socket_path: /home/fred/.ansible/pc/f64ddfa760``" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:432 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:436 msgid "To clear out a persistent connection before it times out (the default timeout is 30 seconds of inactivity), simple delete the socket file." msgstr "タイムアウトã™ã‚‹å‰ã«æ°¸ç¶šçš„ãªæŽ¥ç¶š (デフォルトã®ã‚¿ã‚¤ãƒ アウト㌠30 秒ã®éžã‚¢ã‚¯ãƒ†ã‚£ãƒ–タイムアウト) を削除ã™ã‚‹ã«ã¯ã€ã‚½ã‚±ãƒƒãƒˆãƒ•ã‚¡ã‚¤ãƒ«ã‚’ç°¡å˜ãªå‰Šé™¤ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:442 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:446 msgid "Persistent connection idle timeout" msgstr "永続的ãªæŽ¥ç¶šã‚¢ã‚¤ãƒ‰ãƒ«ã‚¿ã‚¤ãƒ アウト" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:444 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:448 msgid "By default, ``ANSIBLE_PERSISTENT_CONNECT_TIMEOUT`` is set to 30 (seconds). You may see the following error if this value is too low:" msgstr "デフォルトã§ã¯ã€``ANSIBLE_PERSISTENT_CONNECT_TIMEOUT`` 㯠30 (秒) ã«è¨å®šã•ã‚Œã¾ã™ã€‚ã“ã®å€¤ãŒä½Žã™ãŽã‚‹ã¨ã€ä»¥ä¸‹ã®ã‚¨ãƒ©ãƒ¼ãŒè¡¨ç¤ºã•ã‚Œã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:452 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:456 msgid "Increase value of persistent connection idle timeout:" msgstr "永続的ãªæŽ¥ç¶šã‚¢ã‚¤ãƒ‰ãƒ«ã‚¿ã‚¤ãƒ アウトã®å€¤ã‚’大ããã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:466 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:470 msgid "Command timeout" msgstr "コマンドタイムアウト" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:468 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:472 msgid "By default, ``ANSIBLE_PERSISTENT_COMMAND_TIMEOUT`` is set to 30 (seconds). Prior versions of Ansible had this value set to 10 seconds by default. You may see the following error if this value is too low:" msgstr "デフォルトã§ã¯ã€``ANSIBLE_PERSISTENT_COMMAND_TIMEOUT`` 㯠30 (秒) ã«è¨å®šã•ã‚Œã¾ã™ã€‚Ansible ã®ä»¥å‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã“ã®å€¤ã‚’ 10 秒ã«è¨å®šã•ã‚Œã¦ã„ã¾ã™ã€‚ã“ã®å€¤ãŒä½Žã™ãŽã‚‹ã¨ã€ä»¥ä¸‹ã®ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:478 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:482 msgid "Option 1 (Global command timeout setting): Increase value of command timeout in configuration file or by setting environment variable." msgstr "オプション 1 (ã‚°ãƒãƒ¼ãƒãƒ«ã‚³ãƒžãƒ³ãƒ‰ã®ã‚¿ã‚¤ãƒ アウトè¨å®š): è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã€ã¾ãŸã¯ç’°å¢ƒå¤‰æ•°ã‚’è¨å®šã—ã¦ã‚³ãƒžãƒ³ãƒ‰ã‚¿ã‚¤ãƒ アウトã®å€¤ã‚’増やã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:492 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:496 msgid "Option 2 (Per task command timeout setting): Increase command timeout per task basis. All network modules support a timeout value that can be set on a per task basis. The timeout value controls the amount of time in seconds before the task will fail if the command has not returned." msgstr "オプション 2 (タスクã”ã¨ã®ã‚³ãƒžãƒ³ãƒ‰ã®ã‚¿ã‚¤ãƒ アウトè¨å®š): タスクã”ã¨ã«ã‚³ãƒžãƒ³ãƒ‰ã‚¿ã‚¤ãƒ アウトを増やã—ã¾ã™ã€‚ã™ã¹ã¦ã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€ã‚¿ã‚¹ã‚¯ã”ã¨ã«è¨å®šã§ãるタイムアウト値をサãƒãƒ¼ãƒˆã—ã¦ã„ã¾ã™ã€‚タイムアウト値ã¯ã€ã‚³ãƒžãƒ³ãƒ‰ãŒè¿”ã•ã‚Œãªã‹ã£ãŸå ´åˆã«ã‚¿ã‚¹ã‚¯ãŒå¤±æ•—ã™ã‚‹ã¾ã§ã®æ™‚間を秒å˜ä½ã§åˆ¶å¾¡ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:498 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:502 msgid "For local connection type:" msgstr "ãƒãƒ¼ã‚«ãƒ«æŽ¥ç¶šã‚¿ã‚¤ãƒ—ã®å ´åˆ:" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:523 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:527 msgid "Some operations take longer than the default 30 seconds to complete. One good example is saving the current running config on IOS devices to startup config. In this case, changing the timeout value from the default 30 seconds to 60 seconds will prevent the task from failing before the command completes successfully." msgstr "一部ã®æ“作ã¯ã€å®Œäº†ã¾ã§ã«ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã® 30 秒より長ãã‹ã‹ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€IOS デãƒã‚¤ã‚¹ä¸Šã®ç¾åœ¨ã®å®Ÿè¡Œè¨å®šã‚’スタートアップè¨å®šã«ä¿å˜ã—ã¾ã™ã€‚ã“ã®å ´åˆã¯ã€ã‚¿ã‚¤ãƒ アウト値をデフォルト㮠30 秒ã‹ã‚‰ 60 秒ã«å¤‰æ›´ã™ã‚‹ã¨ã€ã‚³ãƒžãƒ³ãƒ‰ãŒæ£å¸¸ã«å®Œäº†ã™ã‚‹å‰ã«ã‚¿ã‚¹ã‚¯ãŒå¤±æ•—ã™ã‚‹ã®ã‚’防ãã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:530 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:534 msgid "Persistent connection retry timeout" msgstr "永続的ãªæŽ¥ç¶šã®å†è©¦è¡Œã‚¿ã‚¤ãƒ アウト" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:532 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:536 msgid "By default, ``ANSIBLE_PERSISTENT_CONNECT_RETRY_TIMEOUT`` is set to 15 (seconds). You may see the following error if this value is too low:" msgstr "デフォルトã§ã¯ã€``ANSIBLE_PERSISTENT_CONNECT_RETRY_TIMEOUT`` 㯠15 (秒) ã«è¨å®šã•ã‚Œã¾ã™ã€‚ã“ã®å€¤ãŒä½Žã™ãŽã‚‹ã¨ã€ä»¥ä¸‹ã®ã‚¨ãƒ©ãƒ¼ãŒè¡¨ç¤ºã•ã‚Œã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:541 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:545 msgid "Increase the value of the persistent connection idle timeout. Note: This value should be greater than the SSH timeout value (the timeout value under the defaults section in the configuration file) and less than the value of the persistent connection idle timeout (connect_timeout)." msgstr "æŒç¶šçš„接続アイドルタイムアウトã®å€¤ã‚’増やã—ã¾ã™ã€‚注æ„: ã“ã®å€¤ã¯ã€SSH タイムアウト値 (è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã‚»ã‚¯ã‚·ãƒ§ãƒ³ã®ä¸‹ã®ã‚¿ã‚¤ãƒ アウト値) より大ããã€æ°¸ç¶šçš„接続アイドルタイムアウト値 (connect_timeout) よりå°ã•ãã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:559 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:563 msgid "Timeout issue due to platform specific login menu with ``network_cli`` connection type" msgstr "``network_cli`` 接続タイプをæŒã¤ãƒ—ラットフォーム固有ã®ãƒã‚°ã‚¤ãƒ³ãƒ¡ãƒ‹ãƒ¥ãƒ¼ã«ã‚ˆã‚‹ã‚¿ã‚¤ãƒ アウトã®å•é¡Œ" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:561 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:565 msgid "In Ansible 2.9 and later, the network_cli connection plugin configuration options are added to handle the platform specific login menu. These options can be set as group/host or tasks variables." msgstr "Ansible 2.9 以é™ã§ã¯ã€ãƒ—ラットフォーム固有ã®ãƒã‚°ã‚¤ãƒ³ãƒ¡ãƒ‹ãƒ¥ãƒ¼ã‚’処ç†ã™ã‚‹ãŸã‚ã« network_cli connection プラグインè¨å®šã‚ªãƒ—ションãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸã€‚ã“れらã®ã‚ªãƒ—ションã¯ã€ã‚°ãƒ«ãƒ¼ãƒ—/ホストã¾ãŸã¯ã‚¿ã‚¹ã‚¯å¤‰æ•°ã¨ã—ã¦è¨å®šã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:565 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:569 msgid "Example: Handle single login menu prompts with host variables" msgstr "例: ホスト変数を使用ã—㟠1 ã¤ã®ãƒã‚°ã‚¤ãƒ³ãƒ¡ãƒ‹ãƒ¥ãƒ¼ãƒ—ãƒãƒ³ãƒ—トを処ç†ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:576 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:580 msgid "Example: Handle remote host multiple login menu prompts with host variables" msgstr "例: ホスト変数を使用ã—ãŸãƒªãƒ¢ãƒ¼ãƒˆãƒ›ã‚¹ãƒˆã®è¤‡æ•°ã®ãƒã‚°ã‚¤ãƒ³ãƒ¡ãƒ‹ãƒ¥ãƒ¼ãƒ—ãƒãƒ³ãƒ—トを処ç†ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:590 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:594 msgid "To handle multiple login menu prompts:" msgstr "複数ã®ãƒã‚°ã‚¤ãƒ³ãƒ¡ãƒ‹ãƒ¥ãƒ¼ãƒ—ãƒãƒ³ãƒ—トを処ç†ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:592 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:596 msgid "The values of ``ansible_terminal_initial_prompt`` and ``ansible_terminal_initial_answer`` should be a list." msgstr "``ansible_terminal_initial_prompt`` ãŠã‚ˆã³ ``ansible_terminal_initial_answer`` ã®å€¤ã¯ä¸€è¦§å½¢å¼ã§ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:593 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:597 msgid "The prompt sequence should match the answer sequence." msgstr "プãƒãƒ³ãƒ—トシーケンスã¯ã€å¿œç”シーケンスã«ä¸€è‡´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:594 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:598 msgid "The value of ``ansible_terminal_initial_prompt_checkall`` should be set to ``True``." msgstr "``ansible_terminal_initial_prompt_checkall`` ã®å€¤ã¯ ``True`` ã«è¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:596 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:600 msgid "If all the prompts in sequence are not received from remote host at the time connection initialization it will result in a timeout." msgstr "接続ã®åˆæœŸåŒ–時ã«ã€ãƒªãƒ¢ãƒ¼ãƒˆãƒ›ã‚¹ãƒˆã‹ã‚‰ã‚·ãƒ¼ã‚±ãƒ³ã‚¹å†…ã®ã™ã¹ã¦ã®ãƒ—ãƒãƒ³ãƒ—トをå—ã‘å–らãªã„ã¨ã€ã‚¿ã‚¤ãƒ アウトãŒç”Ÿã˜ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:602 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:606 msgid "This section details issues are caused by issues with the Playbook itself." msgstr "本セクションã§ã¯ã€Playbook 自体ã®å•é¡ŒãŒåŽŸå› ã§ç™ºç”Ÿã™ã‚‹å•é¡Œã‚’詳ã—ã説明ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:605 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:609 msgid "Error: \"Unable to enter configuration mode\"" msgstr "Error: \"Unable to enter configuration mode\"" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:607 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:611 msgid "**Platforms:** Arista EOS and Cisco IOS" msgstr "**プラットフォーム:** Arista EOS ãŠã‚ˆã³ Cisco IOS" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:609 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:613 msgid "This occurs when you attempt to run a task that requires privileged mode in a user mode shell." msgstr "ã“ã‚Œã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãƒ¢ãƒ¼ãƒ‰ã‚·ã‚§ãƒ«ã§ç‰¹æ¨©ãƒ¢ãƒ¼ãƒ‰ã‚’å¿…è¦ã¨ã™ã‚‹ã‚¿ã‚¹ã‚¯ã‚’実行ã—よã†ã¨ã™ã‚‹ã¨ç™ºç”Ÿã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:625 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:629 msgid "Use ``connection: ansible.netcommon.network_cli`` and ``become: yes``" msgstr "``connection: ansible.netcommon.network_cli`` ãŠã‚ˆã³ ``become: yes`` ã®ä½¿ç”¨" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:629 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:633 msgid "Proxy Issues" msgstr "プãƒã‚シーã®å•é¡Œ" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:634 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:638 msgid "delegate_to vs ProxyCommand" msgstr "delegate_to 対 ProxyCommand" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:636 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:640 msgid "In order to use a bastion or intermediate jump host to connect to network devices over ``cli`` transport, network modules support the use of ``ProxyCommand``." msgstr "bastion ã¾ãŸã¯ä¸é–“ジャンプホストを使用ã—㦠``cli`` トランスãƒãƒ¼ãƒˆã§ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ‡ãƒã‚¤ã‚¹ã«æŽ¥ç¶šã™ã‚‹ãŸã‚ã«ã€ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ ``ProxyCommand`` ã®ä½¿ç”¨ã«å¯¾å¿œã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:639 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:643 msgid "To use ``ProxyCommand``, configure the proxy settings in the Ansible inventory file to specify the proxy host." msgstr "``ProxyCommand`` を使用ã™ã‚‹ã«ã¯ã€Ansible インベントリーファイルã§ãƒ—ãƒã‚シーè¨å®šã‚’è¨å®šã—ã¦ã€ãƒ—ãƒã‚シーホストを指定ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:652 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:656 msgid "With the configuration above, simply build and run the playbook as normal with no additional changes necessary. The network module will now connect to the network device by first connecting to the host specified in ``ansible_ssh_common_args``, which is ``bastion01`` in the above example." msgstr "上記ã®è¨å®šã§ã¯ã€è¿½åŠ ã®å¤‰æ›´ã‚’å¿…è¦ã¨ã›ãšã«ã€é€šå¸¸ã©ãŠã‚Š Playbook をビルドã—ã¦å®Ÿè¡Œã—ã¾ã™ã€‚ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€æœ€åˆã« ``ansible_ssh_common_args`` ã§æŒ‡å®šã—ãŸãƒ›ã‚¹ãƒˆ (上記ã®ä¾‹ã¯ ``bastion01``) ã«æŽ¥ç¶šã—ã¦ã€ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ‡ãƒã‚¤ã‚¹ã«æŽ¥ç¶šã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:657 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:661 msgid "You can also set the proxy target for all hosts by using environment variables." msgstr "環境変数を使用ã—ã¦ã€ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã®ãƒ—ãƒã‚シーターゲットをè¨å®šã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:664 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:668 msgid "Using bastion/jump host with netconf connection" msgstr "netconf 接続ã§ã® bastion/ジャンプホストã®ä½¿ç”¨" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:667 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:671 msgid "Enabling jump host setting" msgstr "ジャンプホストè¨å®šã®æœ‰åŠ¹åŒ–" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:673 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:677 msgid "Bastion/jump host with netconf connection can be enabled by:" msgstr "netconf 接続をæŒã¤ bastion/ジャンプホストã¯ã€ä»¥ä¸‹ã§æœ‰åŠ¹ã«ã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:671 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:675 msgid "Setting Ansible variable ``ansible_netconf_ssh_config`` either to ``True`` or custom ssh config file path" msgstr "Ansible 変数 ``ansible_netconf_ssh_config`` ã‚’ ``True`` ã¾ãŸã¯ã‚«ã‚¹ã‚¿ãƒ ã® ssh è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ãƒ‘スã«è¨å®š" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:672 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:676 msgid "Setting environment variable ``ANSIBLE_NETCONF_SSH_CONFIG`` to ``True`` or custom ssh config file path" msgstr "環境変数 ``ANSIBLE_NETCONF_SSH_CONFIG`` ã‚’ ``True`` ã¾ãŸã¯ã‚«ã‚¹ã‚¿ãƒ ã® ssh è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ãƒ‘スã«è¨å®š" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:673 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:677 msgid "Setting ``ssh_config = 1`` or ``ssh_config = <ssh-file-path>`` under ``netconf_connection`` section" msgstr "``ssh_config = 1`` セクションã®ä¸‹ã« ``ssh_config = <ssh-file-path>`` ã¾ãŸã¯ ``netconf_connection`` ã®è¨å®š" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:675 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:679 msgid "If the configuration variable is set to 1 the proxycommand and other ssh variables are read from default ssh config file (~/.ssh/config)." msgstr "è¨å®šå¤‰æ•°ãŒ 1 ã«è¨å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã€proxycommand ãŠã‚ˆã³ãã®ä»–ã® ssh 変数ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã® ssh è¨å®šãƒ•ã‚¡ã‚¤ãƒ« (~/.ssh/config) ã‹ã‚‰èªã¿è¾¼ã¾ã‚Œã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:678 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:682 msgid "If the configuration variable is set to file path the proxycommand and other ssh variables are read from the given custom ssh file path" msgstr "è¨å®šå¤‰æ•°ãŒãƒ•ã‚¡ã‚¤ãƒ«ãƒ‘スã«è¨å®šã•ã‚Œã¦ã„ã‚‹ã¨ã€proxycommand ãŠã‚ˆã³ãã®ä»–ã® ssh 変数ã¯æŒ‡å®šã®ã‚«ã‚¹ã‚¿ãƒ ssh ファイルパスã‹ã‚‰èªã¿è¾¼ã¾ã‚Œã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:682 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:686 msgid "Example ssh config file (~/.ssh/config)" msgstr "ssh è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã®ä¾‹ (~/.ssh/config)" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:709 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:713 msgid "Example Ansible inventory file" msgstr "Ansible インベントリーファイルã®ä¾‹" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:723 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:727 msgid "Using ``ProxyCommand`` with passwords via variables" msgstr "変数を介ã—ãŸãƒ‘スワードã§ã® ``ProxyCommand`` ã®ä½¿ç”¨" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:725 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:729 msgid "By design, SSH doesn't support providing passwords via environment variables. This is done to prevent secrets from leaking out, for example in ``ps`` output." msgstr "è¨è¨ˆä¸Šã€SSH ã¯ç’°å¢ƒå¤‰æ•°çµŒç”±ã§ãƒ‘スワードã®æ供をサãƒãƒ¼ãƒˆã—ã¾ã›ã‚“。ã“ã‚Œã¯ã€``ps`` ã®å‡ºåŠ›ãªã©ã€ã‚·ãƒ¼ã‚¯ãƒ¬ãƒƒãƒˆãŒãƒªãƒ¼ã‚¯ã—ãªã„よã†ã«ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:728 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:732 msgid "We recommend using SSH Keys, and if needed an ssh-agent, rather than passwords, where ever possible." msgstr "SSH éµã‚’使用ã™ã‚‹ã“ã¨ã‚’推奨ã—ã¾ã™ã€‚å¿…è¦ã«å¿œã˜ã¦ã€å¯èƒ½ãªå ´åˆã¯ã€ãƒ‘スワードã§ã¯ãªã ssh-agent を使用ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:731 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:735 msgid "Miscellaneous Issues" msgstr "ãã®ä»–ã®å•é¡Œ" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:735 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:739 msgid "Intermittent failure while using ``ansible.netcommon.network_cli`` connection type" msgstr "``ansible.netcommon.network_cli`` 接続タイプã®ä½¿ç”¨ä¸ã«æ–続的ãªå¤±æ•—" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:737 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:741 msgid "If the command prompt received in response is not matched correctly within the ``ansible.netcommon.network_cli`` connection plugin the task might fail intermittently with truncated response or with the error message ``operation requires privilege escalation``. Starting in 2.7.1 a new buffer read timer is added to ensure prompts are matched properly and a complete response is send in output. The timer default value is 0.2 seconds and can be adjusted on a per task basis or can be set globally in seconds." msgstr "å¿œç”ã§å—ã‘å–ã£ãŸã‚³ãƒžãƒ³ãƒ‰ãƒ—ãƒãƒ³ãƒ—ト㌠``ansible.netcommon.network_cli`` connection プラグイン内ã§æ£ã—ã一致ã—ãªã„ã¨ã€ã‚¿ã‚¹ã‚¯ãŒæ–続的ã«å¤±æ•—ã—ã€å¿œç”ãŒåˆ‡ã‚Šæ¨ã¦ã‚‰ã‚Œã‚‹ã‹ã€ã‚¨ãƒ©ãƒ¼ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ ``operation requires privilege escalation`` ãŒè¡¨ç¤ºã•ã‚Œã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚2.7.1 以é™ã€ãƒ—ãƒãƒ³ãƒ—トãŒæ£ã—ã一致ã—ã€å®Œå…¨ãªå¿œç”ãŒå‡ºåŠ›ã«é€ä¿¡ã•ã‚Œã‚‹ã‚ˆã†ã«ã€æ–°ã—ã„ãƒãƒƒãƒ•ã‚¡èªã¿å–りタイマーãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸã€‚タイマーã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã¯ 0.2 秒ã§ã€ã‚¿ã‚¹ã‚¯ã”ã¨ã«èª¿æ•´ã™ã‚‹ã“ã¨ã‚‚ã€ç§’å˜ä½ã§ã‚°ãƒãƒ¼ãƒãƒ«ã«è¨å®šã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:744 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:748 msgid "Example Per task timer setting" msgstr "タスクタイマーã”ã¨ã®è¨å®šä¾‹" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:763 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:767 msgid "This timer delay per command executed on remote host can be disabled by setting the value to zero." msgstr "リモートホストã§å®Ÿè¡Œã•ã‚Œã‚‹ã‚³ãƒžãƒ³ãƒ‰åˆ¥ã®ã“ã®ã‚¿ã‚¤ãƒžãƒ¼é…延ã¯ã€å€¤ã‚’ゼãƒã«è¨å®šã™ã‚‹ã¨ç„¡åŠ¹ã«ã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:767 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:771 msgid "Task failure due to mismatched error regex within command response using ``ansible.netcommon.network_cli`` connection type" msgstr "``ansible.netcommon.network_cli`` 接続タイプを使用ã—ãŸã‚³ãƒžãƒ³ãƒ‰å¿œç”内ã®ã‚¨ãƒ©ãƒ¼æ£è¦è¡¨ç¾ã®ä¸ä¸€è‡´ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã®å¤±æ•—" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:769 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:773 msgid "In Ansible 2.9 and later, the ``ansible.netcommon.network_cli`` connection plugin configuration options are added to handle the stdout and stderr regex to identify if the command execution response consist of a normal response or an error response. These options can be set group/host variables or as tasks variables." msgstr "Ansible 2.9 以é™ã§ã¯ã€``ansible.netcommon.network_cli`` connection プラグインè¨å®šã‚ªãƒ—ションãŒè¿½åŠ ã•ã‚Œã€æ¨™æº–出力ã¨æ¨™æº–エラーã®æ£è¦è¡¨ç¾ã‚’処ç†ã—ã¦ã€ã‚³ãƒžãƒ³ãƒ‰å®Ÿè¡Œå¿œç”ãŒé€šå¸¸ã®å¿œç”ã‹ã‚¨ãƒ©ãƒ¼å¿œç”ã‹ã‚’è˜åˆ¥ã—ã¾ã™ã€‚ã“れらã®ã‚ªãƒ—ションã¯ã€ã‚°ãƒ«ãƒ¼ãƒ—/ホスト変数ã¾ãŸã¯ã‚¿ã‚¹ã‚¯å¤‰æ•°ã¨ã—ã¦è¨å®šã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:774 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:778 msgid "Example: For mismatched error response" msgstr "例: ä¸ä¸€è‡´ã®ã‚¨ãƒ©ãƒ¼å¿œç”ã®å ´åˆ" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:784 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:788 msgid "Playbook run output:" msgstr "Playbook 実行ã®å‡ºåŠ›:" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:797 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:801 msgid "Modify the error regex for individual task." msgstr "個々ã®ã‚¿ã‚¹ã‚¯ã®ã‚¨ãƒ©ãƒ¼æ£è¦è¡¨ç¾ã‚’変更ã—ã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:810 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:814 msgid "The terminal plugin regex options ``ansible_terminal_stderr_re`` and ``ansible_terminal_stdout_re`` have ``pattern`` and ``flags`` as keys. The value of the ``flags`` key should be a value that is accepted by the ``re.compile`` python method." msgstr "端末プラグインã®æ£è¦è¡¨ç¾ã‚ªãƒ—ション ``ansible_terminal_stderr_re`` ãŠã‚ˆã³ ``ansible_terminal_stdout_re`` ã¯ã€``pattern`` 㨠``flags`` ã‚’ã‚ーã¨ã—ã¾ã™ã€‚``flags`` ã‚ーã®å€¤ã¯ã€``re.compile`` python メソッドã§è¨±å¯ã•ã‚Œã‚‹å€¤ã§ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:816 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:820 msgid "Intermittent failure while using ``ansible.netcommon.network_cli`` connection type due to slower network or remote target host" msgstr "低速ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã¾ãŸã¯ãƒªãƒ¢ãƒ¼ãƒˆã‚¿ãƒ¼ã‚²ãƒƒãƒˆãƒ›ã‚¹ãƒˆã«ã‚ˆã‚‹ ``ansible.netcommon.network_cli`` 接続タイプã®ä½¿ç”¨æ™‚ã®æ–続的ãªå¤±æ•—" -#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:818 +#: ../../rst/network/user_guide/network_debug_troubleshooting.rst:822 msgid "In Ansible 2.9 and later, the ``ansible.netcommon.network_cli`` connection plugin configuration option is added to control the number of attempts to connect to a remote host. The default number of attempts is three. After every retry attempt the delay between retries is increased by power of 2 in seconds until either the maximum attempts are exhausted or either the ``persistent_command_timeout`` or ``persistent_connect_timeout`` timers are triggered." msgstr "Ansible 2.9 以é™ã§ã¯ã€ãƒªãƒ¢ãƒ¼ãƒˆãƒ›ã‚¹ãƒˆã¸ã®æŽ¥ç¶šã®è©¦è¡Œå›žæ•°ã‚’制御ã™ã‚‹ãŸã‚ã«ã€``ansible.netcommon.network_cli`` connection プラグインè¨å®šã‚ªãƒ—ションãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸã€‚デフォルトã®è©¦è¡Œå›žæ•°ã¯ 3 回ã§ã™ã€‚å†è©¦è¡Œã®ãŸã³ã«ã€æœ€å¤§è©¦è¡Œå›žæ•°ãŒãªããªã‚‹ã‹ã€``persistent_command_timeout`` ã¾ãŸã¯ ``persistent_connect_timeout`` タイマーã®ã„ãšã‚Œã‹ãŒç™ºç”Ÿã™ã‚‹ã¾ã§ã€å†è©¦è¡Œé–“ã®é…延㯠2 ã®ç´¯ä¹— (秒) ãšã¤å¢—åŠ ã—ã¾ã™ã€‚" @@ -3789,67 +3790,63 @@ msgstr "``contains`` - オブジェクトã«æŒ‡å®šã•ã‚ŒãŸé …ç›®ãŒå«ã¾ã‚Œã‚‹ msgid "Conditional statements evaluate the results from the commands that are executed remotely on the device. Once the task executes the command set, the ``wait_for`` argument can be used to evaluate the results before returning control to the Ansible playbook." msgstr "æ¡ä»¶æ–‡ã¯ã€ãƒ‡ãƒã‚¤ã‚¹ä¸Šã§ãƒªãƒ¢ãƒ¼ãƒˆã«å®Ÿè¡Œã•ã‚Œã‚‹ã‚³ãƒžãƒ³ãƒ‰ã®çµæžœã‚’評価ã—ã¾ã™ã€‚タスクãŒã‚³ãƒžãƒ³ãƒ‰ã‚»ãƒƒãƒˆã‚’実行ã™ã‚‹ã¨ã€Ansible Playbook ã«åˆ¶å¾¡ã‚’戻ã™å‰ã«ã€``wait_for`` 引数を使用ã—ã¦çµæžœã‚’評価ã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_working_with_command_output.rst:29 -msgid "For example::" -msgstr "例::" - -#: ../../rst/network/user_guide/network_working_with_command_output.rst:39 +#: ../../rst/network/user_guide/network_working_with_command_output.rst:41 msgid "In the above example task, the command :code:`show interface Ethernet4 | json` is executed on the remote device and the results are evaluated. If the path :code:`(result[0].interfaces.Ethernet4.interfaceStatus)` is not equal to \"connected\", then the command is retried. This process continues until either the condition is satisfied or the number of retries has expired (by default, this is 10 retries at 1 second intervals)." msgstr "上記ã®ã‚¿ã‚¹ã‚¯ä¾‹ã§ã¯ã€ãƒªãƒ¢ãƒ¼ãƒˆãƒ‡ãƒã‚¤ã‚¹ã§ command :code:`show interface Ethernet4 | json` ãŒå®Ÿè¡Œã•ã‚Œã€çµæžœãŒè©•ä¾¡ã•ã‚Œã¾ã™ã€‚path :code:`(result[0].interfaces.Ethernet4.interfaceStatus)`ãŒã€Œconnectedã€ã«ãªã£ã¦ã„ãªã‘ã‚Œã°ã€ã‚³ãƒžãƒ³ãƒ‰ã¯å†è©¦è¡Œã•ã‚Œã¾ã™ã€‚ã“ã®å‡¦ç†ã¯ã€æ¡ä»¶ãŒæº€ãŸã•ã‚Œã‚‹ã‹ã€å†è©¦è¡Œå›žæ•°ãŒæœŸé™åˆ‡ã‚Œã«ãªã‚‹ (デフォルトã§ã¯ã€1 秒間隔㧠10 回ã®å†è©¦è¡Œ) ã¾ã§ç¶™ç¶šã•ã‚Œã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_working_with_command_output.rst:47 -msgid "The commands module can also evaluate more than one set of command results in an interface. For instance::" +#: ../../rst/network/user_guide/network_working_with_command_output.rst:49 +msgid "The commands module can also evaluate more than one set of command results in an interface. For instance:" msgstr "ã¾ãŸã€commands モジュールã¯ã€1 ã¤ã®ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ã§è¤‡æ•°ã®ã‚³ãƒžãƒ³ãƒ‰çµæžœã‚’評価ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_working_with_command_output.rst:60 +#: ../../rst/network/user_guide/network_working_with_command_output.rst:64 msgid "In the above example, two commands are executed on the remote device, and the results are evaluated. By specifying the result index value (0 or 1), the correct result output is checked against the conditional." msgstr "上記ã®ä¾‹ã§ã¯ã€2 ã¤ã®ã‚³ãƒžãƒ³ãƒ‰ãŒãƒªãƒ¢ãƒ¼ãƒˆãƒ‡ãƒã‚¤ã‚¹ã§å®Ÿè¡Œã•ã‚Œã€çµæžœãŒè©•ä¾¡ã•ã‚Œã¾ã™ã€‚çµæžœã®ã‚¤ãƒ³ãƒ‡ãƒƒã‚¯ã‚¹å€¤ (0 ã¾ãŸã¯ 1) を指定ã™ã‚‹ã“ã¨ã§ã€æ¡ä»¶ã«å¯¾ã—ã¦æ£ã—ã„çµæžœå‡ºåŠ›ãŒç¢ºèªã•ã‚Œã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_working_with_command_output.rst:65 +#: ../../rst/network/user_guide/network_working_with_command_output.rst:69 msgid "The ``wait_for`` argument must always start with result and then the command index in ``[]``, where ``0`` is the first command in the commands list, ``1`` is the second command, ``2`` is the third and so on." msgstr "``wait_for`` 引数ã¯ã€å¿…ãšçµæžœã§ã€æ¬¡ã« ``[]`` ã®ã‚³ãƒžãƒ³ãƒ‰ã‚¤ãƒ³ãƒ‡ãƒƒã‚¯ã‚¹ãŒå¿…è¦ã§ã™ã€‚``0`` ã¯ã‚³ãƒžãƒ³ãƒ‰ãƒªã‚¹ãƒˆã®æœ€åˆã®ã‚³ãƒžãƒ³ãƒ‰ã€``1`` 㯠2 番目ã®ã‚³ãƒžãƒ³ãƒ‰ã€``2`` 㯠3 番目ã®ã‚³ãƒžãƒ³ãƒ‰ãªã©ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_working_with_command_output.rst:71 +#: ../../rst/network/user_guide/network_working_with_command_output.rst:75 msgid "Handling prompts in network modules" msgstr "ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ—ãƒãƒ³ãƒ—トã®å‡¦ç†" -#: ../../rst/network/user_guide/network_working_with_command_output.rst:73 +#: ../../rst/network/user_guide/network_working_with_command_output.rst:77 msgid "Network devices may require that you answer a prompt before performing a change on the device. Individual network modules such as :ref:`cisco.ios.ios_command <ansible_collections.cisco.ios.ios_command_module>` and :ref:`cisco.nxos.nxos_command <ansible_collections.cisco.nxos.nxos_command_module>` can handle this with a ``prompt`` parameter." msgstr "ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ‡ãƒã‚¤ã‚¹ã¯ã€ãƒ‡ãƒã‚¤ã‚¹ã®å¤‰æ›´ã‚’実行ã™ã‚‹å‰ã«ãƒ—ãƒãƒ³ãƒ—トã®å›žç”ãŒå¿…è¦ã«ãªã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚:ref:`cisco.ios.ios_command <ansible_collections.cisco.ios.ios_command_module>` ãŠã‚ˆã³ :ref:`cisco.nxos.nxos_command <ansible_collections.cisco.nxos.nxos_command_module>` ãªã©ã®å€‹åˆ¥ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ ``prompt`` パラメーターã§ã“れを処ç†ã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_working_with_command_output.rst:77 +#: ../../rst/network/user_guide/network_working_with_command_output.rst:81 msgid "``prompt`` is a Python regex. If you add special characters such as ``?`` in the ``prompt`` value, the prompt won't match and you will get a timeout. To avoid this, ensure that the ``prompt`` value is a Python regex that matches the actual device prompt. Any special characters must be handled correctly in the ``prompt`` regex." msgstr "``prompt`` 㯠Python ã®æ£è¦è¡¨ç¾ã§ã™ã€‚``prompt`` 値㫠``?`` ãªã©ã®ç‰¹æ®Šæ–‡å—ã‚’è¿½åŠ ã™ã‚‹ã¨ã€ãƒ—ãƒãƒ³ãƒ—トãŒä¸€è‡´ã›ãšã€ã‚¿ã‚¤ãƒ アウトãŒç™ºç”Ÿã—ã¾ã™ã€‚ã“れを回é¿ã™ã‚‹ã«ã¯ã€``prompt`` 値ãŒå®Ÿéš›ã®ãƒ‡ãƒã‚¤ã‚¹ãƒ—ãƒãƒ³ãƒ—トã¨ä¸€è‡´ã™ã‚‹ Python æ£è¦è¡¨ç¾ã§ã‚ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚特殊文å—ã¯ã€``prompt`` æ£è¦è¡¨ç¾ã§æ£ã—ã処ç†ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_working_with_command_output.rst:79 +#: ../../rst/network/user_guide/network_working_with_command_output.rst:83 msgid "You can also use the :ref:`ansible.netcommon.cli_command <ansible_collections.ansible.netcommon.cli_command_module>` to handle multiple prompts." msgstr ":ref:`ansible.netcommon.cli_command <ansible_collections.ansible.netcommon.cli_command_module>` を使用ã—ã¦ã€è¤‡æ•°ã®ãƒ—ãƒãƒ³ãƒ—トを処ç†ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_working_with_command_output.rst:97 +#: ../../rst/network/user_guide/network_working_with_command_output.rst:101 msgid "You must list the prompt and the answers in the same order (that is, prompt[0] is answered by answer[0])." msgstr "プãƒãƒ³ãƒ—トã¨å›žç”ã‚’åŒã˜é †åºã§ä¸€è¦§è¡¨ç¤ºã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (ã¤ã¾ã‚Šã€prompt[0] ã«ã¯ answer[0] ã§å¿œç”ã—ã¾ã™)。" -#: ../../rst/network/user_guide/network_working_with_command_output.rst:99 +#: ../../rst/network/user_guide/network_working_with_command_output.rst:103 msgid "In the above example, ``check_all: True`` ensures that the task gives the matching answer to each prompt. Without that setting, a task with multiple prompts would give the first answer to every prompt." msgstr "上記ã®ä¾‹ã§ã¯ã€``check_all: True`` ã«ã‚ˆã‚Šã€ã‚¿ã‚¹ã‚¯ãŒå„プãƒãƒ³ãƒ—トã«ä¸€è‡´ã™ã‚‹å¿œç”ã‚’è¿”ã™ã‚ˆã†ã«ã—ã¾ã™ã€‚ã“ã®è¨å®šãŒãªã„ã¨ã€è¤‡æ•°ã®ãƒ—ãƒãƒ³ãƒ—トãŒã‚るタスクã§ã¯ã€ã™ã¹ã¦ã®ãƒ—ãƒãƒ³ãƒ—トã«å¯¾ã—ã¦æœ€åˆã®å¿œç”ãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_working_with_command_output.rst:101 +#: ../../rst/network/user_guide/network_working_with_command_output.rst:105 msgid "In the following example, the second answer would be ignored and ``y`` would be the answer given to both prompts. That is, this task only works because both answers are identical. Also notice again that ``prompt`` must be a Python regex, which is why the ``?`` is escaped in the first prompt." msgstr "次ã®ä¾‹ã§ã¯ã€2 番目ã®å›žç”ã¯ç„¡è¦–ã•ã‚Œã€ä¸¡æ–¹ã®ãƒ—ãƒãƒ³ãƒ—ト㫠``y`` ãŒå…¥åŠ›ã•ã‚Œã¾ã™ã€‚ã¤ã¾ã‚Šã€ã“ã®ã‚¿ã‚¹ã‚¯ãŒæ©Ÿèƒ½ã™ã‚‹ã®ã¯ã€ä¸¡æ–¹ã®ç”ãˆãŒåŒã˜ã ã‹ã‚‰ã§ã™ã€‚ã¾ãŸã€``prompt`` 㯠Python ã®æ£è¦è¡¨ç¾ã§ãªã‘ã‚Œã°ãªã‚‰ãªã„ã“ã¨ã«ã‚‚注æ„ã—ã¦ãã ã•ã„。ã“ã®ãŸã‚ã€``?`` ã¯æœ€åˆã®ãƒ—ãƒãƒ³ãƒ—トã§ã‚¨ã‚¹ã‚±ãƒ¼ãƒ—ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/network/user_guide/network_working_with_command_output.rst:119 +#: ../../rst/network/user_guide/network_working_with_command_output.rst:123 msgid "`Rebooting network devices with Ansible <https://www.ansible.com/blog/rebooting-network-devices-with-ansible>`_" msgstr "`Rebooting network devices with Ansible <https://www.ansible.com/blog/rebooting-network-devices-with-ansible>`_" -#: ../../rst/network/user_guide/network_working_with_command_output.rst:119 +#: ../../rst/network/user_guide/network_working_with_command_output.rst:123 msgid "Examples using ``wait_for``, ``wait_for_connection``, and ``prompt`` for network devices." msgstr "ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ‡ãƒã‚¤ã‚¹ç”¨ã« ``wait_for``ã€``wait_for_connection``ã€ãŠã‚ˆã³ ``prompt`` を使用ã™ã‚‹ä¾‹ã€‚" -#: ../../rst/network/user_guide/network_working_with_command_output.rst:121 +#: ../../rst/network/user_guide/network_working_with_command_output.rst:125 msgid "`Deep dive on cli_command <https://www.ansible.com/blog/deep-dive-on-cli-command-for-network-automation>`_" msgstr "`Deep dive on cli_command <https://www.ansible.com/blog/deep-dive-on-cli-command-for-network-automation>`_" -#: ../../rst/network/user_guide/network_working_with_command_output.rst:122 +#: ../../rst/network/user_guide/network_working_with_command_output.rst:126 msgid "Detailed overview of how to use the ``cli_command``." msgstr "``cli_command`` ã®ä½¿ç”¨æ–¹æ³•ã«é–¢ã™ã‚‹è©³ç´°ãªæ¦‚è¦" @@ -5738,3 +5735,6 @@ msgstr "ã“ã‚Œã«ã‚ˆã‚Šã€Ethernet2/1 ãŠã‚ˆã³ Ethernet2/10 ã¯ã€å®šç¾©ã•ã‚Œã #~ msgid "8.4(1) and later" #~ msgstr "8.4(1) 以é™" +#~ msgid "For example::" +#~ msgstr "例::" + diff --git a/docs/docsite/rst/locales/ja/LC_MESSAGES/porting_guides.po b/docs/docsite/rst/locales/ja/LC_MESSAGES/porting_guides.po index 4931333d..09efa7dd 100644 --- a/docs/docsite/rst/locales/ja/LC_MESSAGES/porting_guides.po +++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/porting_guides.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Ansible devel\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-10-05 13:53+0200\n" +"POT-Creation-Date: 2021-11-09 14:07+0100\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" @@ -37,7 +37,6 @@ msgid "This section discusses the behavioral changes between Ansible 1.x and Ans msgstr "ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€Ansible 1.x ã‹ã‚‰ Ansible 2.0 ã«ãŠã‘る動作ã®å¤‰æ›´ç‚¹ã‚’説明ã—ã¾ã™ã€‚" #: ../../rst/porting_guides/porting_guide_2.0.rst:10 -#: ../../rst/porting_guides/porting_guide_2.10.rst:16 #: ../../rst/porting_guides/porting_guide_2.3.rst:10 #: ../../rst/porting_guides/porting_guide_2.4.rst:10 #: ../../rst/porting_guides/porting_guide_2.5.rst:9 @@ -77,14 +76,12 @@ msgid "Topics" msgstr "トピック" #: ../../rst/porting_guides/porting_guide_2.0.rst:20 -#: ../../rst/porting_guides/porting_guide_2.10.rst:33 #: ../../rst/porting_guides/porting_guide_2.3.rst:20 #: ../../rst/porting_guides/porting_guide_2.5.rst:18 #: ../../rst/porting_guides/porting_guide_2.6.rst:18 #: ../../rst/porting_guides/porting_guide_2.7.rst:54 #: ../../rst/porting_guides/porting_guide_2.8.rst:19 #: ../../rst/porting_guides/porting_guide_2.9.rst:20 -#: ../../rst/porting_guides/porting_guide_4.rst:18 #: ../../rst/porting_guides/porting_guide_base_2.10.rst:26 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:21 #: ../../rst/porting_guides/porting_guide_core_2.12.rst:20 @@ -156,14 +153,12 @@ msgid "from 2.0.1 onwards, the implicit setup task from gather_facts now correct msgstr "2.0.1 以é™ã€gather_facts ã®æš—黙的ãªè¨å®šã‚¿ã‚¹ã‚¯ã¯ã€ãƒ—レイã‹ã‚‰ã™ã¹ã¦æ£ã—ã継承ã•ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸãŒã€ã“ã‚Œã«ã‚ˆã‚Šã€ãƒ—レイレベル㧠`environment` ã‚’è¨å®šã—ã€`ansible_env` ã®å˜åœ¨ã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã«å•é¡ŒãŒç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã—ãŸãŒã€ä»¥å‰ã¯ã“ã®å•é¡Œã¯ç„¡è¦–ã•ã‚Œã¦ã„ã¾ã—ãŸã€‚ã“ã‚Œã‹ã‚‰ã¯ã€ŒUndefinedã€ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" #: ../../rst/porting_guides/porting_guide_2.0.rst:107 -#: ../../rst/porting_guides/porting_guide_2.10.rst:51 #: ../../rst/porting_guides/porting_guide_2.4.rst:52 #: ../../rst/porting_guides/porting_guide_2.5.rst:101 #: ../../rst/porting_guides/porting_guide_2.6.rst:23 #: ../../rst/porting_guides/porting_guide_2.7.rst:104 #: ../../rst/porting_guides/porting_guide_2.8.rst:325 #: ../../rst/porting_guides/porting_guide_2.9.rst:43 -#: ../../rst/porting_guides/porting_guide_4.rst:30 #: ../../rst/porting_guides/porting_guide_base_2.10.rst:44 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:33 #: ../../rst/porting_guides/porting_guide_core_2.12.rst:52 @@ -392,14 +387,12 @@ msgid "callback plugins" msgstr "callback プラグイン" #: ../../rst/porting_guides/porting_guide_2.0.rst:394 -#: ../../rst/porting_guides/porting_guide_2.10.rst:97 #: ../../rst/porting_guides/porting_guide_2.3.rst:160 #: ../../rst/porting_guides/porting_guide_2.5.rst:281 #: ../../rst/porting_guides/porting_guide_2.6.rst:102 #: ../../rst/porting_guides/porting_guide_2.7.rst:241 #: ../../rst/porting_guides/porting_guide_2.8.rst:549 #: ../../rst/porting_guides/porting_guide_2.9.rst:722 -#: ../../rst/porting_guides/porting_guide_4.rst:131 #: ../../rst/porting_guides/porting_guide_base_2.10.rst:90 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:134 #: ../../rst/porting_guides/porting_guide_core_2.12.rst:109 @@ -410,2252 +403,21 @@ msgstr "カスタムスクリプトã®ç§»æ¤" msgid "Custom scripts that used the ``ansible.runner.Runner`` API in 1.x have to be ported in 2.x. Please refer to: :ref:`developing_api`" msgstr "1.x 㧠``ansible.runner.Runner`` API を使用ã—ãŸã‚«ã‚¹ã‚¿ãƒ スクリプトã¯ã€2.x ã«ç§»æ¤ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚「:ref:`developing_api`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_2.10.rst:8 +#: ../../rst/porting_guides/porting_guide_2.10.rst:7 msgid "Ansible 2.10 Porting Guide" msgstr "Ansible 2.10 移æ¤ã‚¬ã‚¤ãƒ‰" -#: ../../rst/porting_guides/porting_guide_2.10.rst:12 -msgid "In Ansible 2.10, many plugins and modules have migrated to Collections on `Ansible Galaxy <https://galaxy.ansible.com>`_. Your playbooks should continue to work without any changes. We recommend you start using the fully-qualified collection name (FQCN) in your playbooks as the explicit and authoritative indicator of which collection to use as some collections may contain duplicate module names. You can search the `index of all modules <https://docs.ansible.com/ansible/2.10/collections/index_module.html>`_ to find the collection a module has been relocated to." -msgstr "Ansible 2.10 ã§ã¯ã€å¤šãã®ãƒ—ラグインやモジュールãŒã€`Ansible Galaxy <https://galaxy.ansible.com>`_ ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«ç§»è¡Œã—ã¾ã—ãŸã€‚ãŠä½¿ã„ã® Playbook ã¯ä½•ã®å¤‰æ›´ã‚‚ãªã継続ã—ã¦ãŠä½¿ã„ã„ãŸã ã‘ã¾ã™ã€‚一部ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«åãŒé‡è¤‡ã—ã¦ã„ã‚‹å¯èƒ½æ€§ãŒã‚ã‚‹ãŸã‚ã€ã©ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’使用ã™ã‚‹ã‹ã®æ˜Žç¤ºçš„ã‹ã¤æ¨©å¨çš„ãªæŒ‡æ¨™ã¨ã—ã¦ã€Playbook ã§ã€å®Œå…¨ä¿®é£¾ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³å（FQCN）を使用ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚`ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ã‚¤ãƒ³ãƒ‡ãƒƒã‚¯ã‚¹ <https://docs.ansible.com/ansible/2.10/collections/index_module.html>`_ を検索ã™ã‚‹ã¨ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒå†é…ç½®ã•ã‚ŒãŸã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’見ã¤ã‘ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_2.10.rst:9 +#: ../../rst/porting_guides/porting_guide_3.rst:9 +#: ../../rst/porting_guides/porting_guide_4.rst:9 +msgid "Ansible Porting Guides are maintained in the ``devel`` branch only. See `the devel Ansible 4 Porting guide <https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html>`_ for up to date information." +msgstr "Ansible 移æ¤ã‚¬ã‚¤ãƒ‰ã¯ã€``devel`` ブランãƒã§ã®ã¿ç¶æŒã•ã‚Œã¾ã™ã€‚最新ã®æƒ…å ±ã¯ã€`the devel Ansible 4 Porting guide <https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_2.10.rst:14 -msgid "This section discusses the behavioral changes between Ansible 2.9 and Ansible 2.10." -msgstr "ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€Ansible 2.9 ã‹ã‚‰ Ansible 2.10 ã«ãŠã‘る動作ã®å¤‰æ›´ç‚¹ã‚’説明ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:18 -msgid "We suggest you read this page along with the `Ansible Changelog for 2.10 <https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst>`_ to understand what updates you may need to make." -msgstr "å¿…è¦ãªæ›´æ–°ã«ã¤ã„ã¦ç†è§£ã™ã‚‹ã«ã¯ã€ã“ã®ãƒšãƒ¼ã‚¸ã¨ä½µã›ã¦ã€Œ`Ansible 2.10 ã®ãƒã‚§ãƒ³ã‚¸ãƒã‚° <https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:20 -msgid "Since 2.10, Ansible consists of two parts:" -msgstr "2.10 以é™ã€Ansible ã¯ä»¥ä¸‹ã® 2 ã¤ã®éƒ¨åˆ†ã‹ã‚‰æ§‹æˆã•ã‚Œã¦ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:22 -msgid "ansible-base, which includes the command line tools with a small selection of plugins and modules, and" -msgstr "ansible-base: プラグインやモジュールãŒå°‘ãªã„コマンドラインツールãŒå«ã¾ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:23 -msgid "a `set of collections <https://github.com/ansible-community/ansible-build-data/blob/main/2.10/ansible.in>`_." -msgstr "`コレクションã®ã‚»ãƒƒãƒˆ <https://github.com/ansible-community/ansible-build-data/blob/main/2.10/ansible.in>`" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:25 -msgid "The :ref:`porting_2.10_guide_base` is included in this porting guide. The complete list of porting guides can be found at :ref:`porting guides <porting_guides>`." -msgstr ":ref:`porting_2.10_guide_base` ã¯ã€ã“ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰ã«å«ã¾ã‚Œã¾ã™ã€‚移æ¤ã‚¬ã‚¤ãƒ‰ã®ä¸€è¦§ã¯ã€Œ:ref:`移æ¤ã‚¬ã‚¤ãƒ‰ <porting_guides>`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:35 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:28 -msgid "Fixed a bug on boolean keywords that made random strings return 'False', now they should return an error if they are not a proper boolean Example: ``diff: yes-`` was returning ``False``." -msgstr "ランダムãªæ–‡å—列ãŒã€ŒFalseã€ã‚’è¿”ã™ãƒ–ール値ã®ã‚ーワードã®ãƒã‚°ã‚’ä¿®æ£ã—ã¾ã—ãŸã€‚é©åˆ‡ãªãƒ–ール値ã§ã¯ãªã„å ´åˆã¯ã‚¨ãƒ©ãƒ¼ã‚’è¿”ã™ã¯ãšã§ã™ (例: ``diff: yes-`` ㌠``False`` ã‚’è¿”ã—ã¦ã„ã‚‹å ´åˆ)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:37 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:30 -msgid "A new fact, ``ansible_processor_nproc`` reflects the number of vcpus available to processes (falls back to the number of vcpus available to the scheduler)." -msgstr "æ–°ã—ã„ファクト ``ansible_processor_nproc`` ã¯ã€ãƒ—ãƒã‚»ã‚¹ã§åˆ©ç”¨å¯èƒ½ãª vcpu ã®æ•°ã‚’åæ˜ ã—ã¦ã„ã¾ã™ (スケジューラーã§åˆ©ç”¨å¯èƒ½ãª vcpu ã®æ•°ã«æˆ»ã•ã‚Œã¾ã™)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:43 -#: ../../rst/porting_guides/porting_guide_2.7.rst:18 -#: ../../rst/porting_guides/porting_guide_2.8.rst:305 -#: ../../rst/porting_guides/porting_guide_2.9.rst:37 -#: ../../rst/porting_guides/porting_guide_4.rst:24 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:36 -#: ../../rst/porting_guides/porting_guide_core_2.11.rst:27 -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:46 -msgid "Command Line" -msgstr "コマンドライン" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:45 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:38 -msgid "The ``ansible-galaxy login`` command has been removed, as the underlying API it used for GitHub auth is being shut down. Publishing roles or collections to Galaxy via ``ansible-galaxy`` now requires that a Galaxy API token be passed to the CLI via a token file (default location ``~/.ansible/galaxy_token``) or (insecurely) via the ``--token`` argument to ``ansible-galaxy``." -msgstr "GitHub èªè¨¼ã«ä½¿ç”¨ã•ã‚Œã‚‹åŸºç¤Žã¨ãªã‚‹ API ãŒã‚·ãƒ£ãƒƒãƒˆãƒ€ã‚¦ãƒ³ã•ã‚Œã‚‹ãŸã‚ã€``ansible-galaxy login`` コマンドãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚``ansible-galaxy`` 経由㧠Galaxy ã«ãƒãƒ¼ãƒ«ã¾ãŸã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’公開ã™ã‚‹å ´åˆã¯ã€Galaxy API トークンをトークンファイル (デフォルトã®å ´æ‰€ ``~/.ansible/galaxy_token``) ã¾ãŸã¯ ``--token`` 引数ã‹ã‚‰ ``ansible-galaxy`` ã« (ã‚»ã‚ュリティーを確ä¿ã›ãšã«ã‚»ã‚ュアã«) 渡ã™ã“ã¨ãŒå¿…è¦ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:53 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:46 -msgid "Windows Server 2008 and 2008 R2 will no longer be supported or tested in the next Ansible release, see :ref:`windows_faq_server2008`." -msgstr "Windows Server 2008 ãŠã‚ˆã³ 2008 R2 ã¯ã€æ¬¡å›žã® Ansible リリースã§ã¯ã‚µãƒãƒ¼ãƒˆã•ã‚Œãšã€ãƒ†ã‚¹ãƒˆã•ã‚Œãªããªã‚Šã¾ã™ã€‚「:ref:`windows_faq_server2008`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:57 -#: ../../rst/porting_guides/porting_guide_2.3.rst:108 -#: ../../rst/porting_guides/porting_guide_2.4.rst:77 -#: ../../rst/porting_guides/porting_guide_2.5.rst:156 -#: ../../rst/porting_guides/porting_guide_2.6.rst:28 -#: ../../rst/porting_guides/porting_guide_2.7.rst:154 -#: ../../rst/porting_guides/porting_guide_2.8.rst:364 -#: ../../rst/porting_guides/porting_guide_2.9.rst:72 -#: ../../rst/porting_guides/porting_guide_4.rst:95 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:50 -#: ../../rst/porting_guides/porting_guide_core_2.11.rst:98 -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:72 -msgid "Modules" -msgstr "モジュール" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:61 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:54 -msgid "Links on this page may not point to the most recent versions of modules. We will update them when we can." -msgstr "ã“ã®ãƒšãƒ¼ã‚¸ã®ãƒªãƒ³ã‚¯ã¯ã€æœ€æ–°ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’å‚ç…§ã—ã¦ã„ãªã„å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚å¯èƒ½ãªé™ã‚Šæ›´æ–°ã—ã¦ã„ãã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:63 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:56 -msgid "Version 2.10.0 of ansible-base changed the default mode of file-based tasks to ``0o600 & ~umask`` when the user did not specify a ``mode`` parameter on file-based tasks. This was in response to a CVE report which we have reconsidered. As a result, the mode change has been reverted in 2.10.1, and mode will now default to ``0o666 & ~umask`` as in previous versions of Ansible." -msgstr "ansible-base ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.10.0 ã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒãƒ•ã‚¡ã‚¤ãƒ«ãƒ™ãƒ¼ã‚¹ã®ã‚¿ã‚¹ã‚¯ã§ ``mode`` パラメーターを指定ã—ãªã‹ã£ãŸå ´åˆã«ã€ãƒ•ã‚¡ã‚¤ãƒ«ãƒ™ãƒ¼ã‚¹ã®ã‚¿ã‚¹ã‚¯ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãƒ¢ãƒ¼ãƒ‰ã‚’ ``0o600 & ~umask`` ã«å¤‰æ›´ã—ã¾ã—ãŸã€‚ã“ã‚Œã¯ã€å†ç·¨æˆã—㟠CVE レãƒãƒ¼ãƒˆã«å¯¾ã™ã‚‹å¯¾å¿œã§ã—ãŸã€‚ãã®çµæžœã€2.10.1 ã§ã¯ãƒ¢ãƒ¼ãƒ‰ã®å¤‰æ›´ãŒå…ƒã«æˆ»ã•ã‚Œã€ä»¥å‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Ansible ã¨åŒæ§˜ã«ã€ãƒ¢ãƒ¼ãƒ‰ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãŒ ``0o666 & ~umask`` ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:64 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:57 -msgid "If you changed any tasks to specify less restrictive permissions while using 2.10.0, those changes will be unnecessary (but will do no harm) in 2.10.1." -msgstr "2.10.0 を使用ã™ã‚‹éš›ã«ã€ã‚ˆã‚Šåˆ¶é™ã®å°‘ãªã„パーミッションを指定ã™ã‚‹ã‚ˆã†ã«ã‚¿ã‚¹ã‚¯ã‚’変更ã—ãŸå ´åˆã€2.10.1 ã§ã¯ãã®å¤‰æ›´ã¯ä¸è¦ã«ãªã‚Šã¾ã™ (ãŸã ã—ã€å®³ã¯ã‚ã‚Šã¾ã›ã‚“)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:65 -#: ../../rst/porting_guides/porting_guide_2.8.rst:376 -#: ../../rst/porting_guides/porting_guide_2.9.rst:79 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:58 -msgid "To avoid the issue raised in CVE-2020-1736, specify a ``mode`` parameter in all file-based tasks that accept it." -msgstr "CVE-2020-1736 ã§ç™ºç”Ÿã™ã‚‹å•é¡Œã‚’回é¿ã™ã‚‹ã«ã¯ã€ãれをå—ã‘入れるファイルベースã®ã‚¿ã‚¹ã‚¯ã§ ``mode`` パラメーターを指定ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:67 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:60 -msgid "``dnf`` and ``yum`` - As of version 2.10.1, the ``dnf`` module (and ``yum`` action when it uses ``dnf``) now correctly validates GPG signatures of packages (CVE-2020-14365). If you see an error such as ``Failed to validate GPG signature for [package name]``, please ensure that you have imported the correct GPG key for the DNF repository and/or package you are using. One way to do this is with the ``rpm_key`` module. Although we discourage it, in some cases it may be necessary to disable the GPG check. This can be done by explicitly adding ``disable_gpg_check: yes`` in your ``dnf`` or ``yum`` task." -msgstr "``dnf`` ãŠã‚ˆã³ ``yum`` - ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.10.1 よりã€``dnf`` モジュール (ãŠã‚ˆã³ ``dnf`` を使用ã™ã‚‹å ´åˆã¯ ``yum`` アクション) ãŒãƒ‘ッケージ㮠GPG ç½²åã‚’æ£ã—ã検証ã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—㟠(CVE-2020-14365)。``Failed to validate GPG signature for [package name]`` ã®ã‚ˆã†ãªã‚¨ãƒ©ãƒ¼ãŒè¡¨ç¤ºã•ã‚ŒãŸå ´åˆã¯ã€ä½¿ç”¨ã—ã¦ã„ã‚‹ DNF リãƒã‚¸ãƒˆãƒªãƒ¼ã‚„パッケージ㮠GPG ã‚ーãŒæ£ã—ãインãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。ã“れを行ㆠ1 ã¤ã®æ–¹æ³•ã¨ã—ã¦ã€``rpm_key`` モジュールã®ä½¿ç”¨ãŒã‚ã‚Šã¾ã™ã€‚推奨ã¯ã—ã¾ã›ã‚“ãŒã€å ´åˆã«ã‚ˆã£ã¦ã¯ GPG ãƒã‚§ãƒƒã‚¯ã‚’無効ã«ã™ã‚‹å¿…è¦ãŒã‚ã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“。ã“ã‚Œã¯ã€``dnf`` タスクã¾ãŸã¯ ``yum`` タスク㫠``disable_gpg_check: yes`` を明示的ã«è¿½åŠ ã™ã‚‹ã“ã¨ã§å®Ÿç¾ã§ãã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:71 -#: ../../rst/porting_guides/porting_guide_2.3.rst:141 -#: ../../rst/porting_guides/porting_guide_2.4.rst:99 -#: ../../rst/porting_guides/porting_guide_2.5.rst:207 -#: ../../rst/porting_guides/porting_guide_2.6.rst:49 -#: ../../rst/porting_guides/porting_guide_2.7.rst:193 -#: ../../rst/porting_guides/porting_guide_2.8.rst:414 -#: ../../rst/porting_guides/porting_guide_2.9.rst:699 -#: ../../rst/porting_guides/porting_guide_4.rst:116 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:64 -#: ../../rst/porting_guides/porting_guide_core_2.11.rst:119 -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:96 -msgid "Noteworthy module changes" -msgstr "モジュール変更ã«é–¢ã™ã‚‹æ³¨ç›®ç‚¹" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:73 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:66 -msgid "Ansible modules created with ``add_file_common_args=True`` added a number of undocumented arguments which were mostly there to ease implementing certain action plugins. The undocumented arguments ``src``, ``follow``, ``force``, ``content``, ``backup``, ``remote_src``, ``regexp``, ``delimiter``, and ``directory_mode`` are now no longer added. Modules relying on these options to be added need to specify them by themselves." -msgstr "``add_file_common_args=True`` ã§ä½œæˆã•ã‚ŒãŸ Ansible モジュールã«ã‚ˆã‚Šã€ç‰¹å®šã‚¢ã‚¯ã‚·ãƒ§ãƒ³ãƒ—ラグインã®å®Ÿè£…を容易ã«ã™ã‚‹ãŸã‚ã«ã€æ–‡æ›¸åŒ–ã•ã‚Œã¦ã„ãªã„引数ãŒè¤‡æ•°è¿½åŠ ã•ã‚Œã¦ã„ã¾ã™ã€‚ドã‚ュメント化ã•ã‚Œã¦ã„ãªã„引数 ``src``ã€``follow``ã€``force``ã€``content``ã€``backup``ã€``remote_src``ã€``regexp``ã€``delimiter``ã€ãŠã‚ˆã³ ``directory_mode`` ãŒè¿½åŠ ã•ã‚Œãªããªã‚Šã¾ã—ãŸã€‚ã‚ªãƒ—ã‚·ãƒ§ãƒ³ã‚’è¿½åŠ ã™ã‚‹ãŸã‚ã€ã“れらã®ã‚ªãƒ—ションãŒè¿½åŠ ã•ã‚Œã‚‹ã“ã¨ã«ä¾å˜ã—ã¦ã„るモジュールã¯ã€è‡ªåˆ†ã§ãれらを指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:74 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:67 -msgid "Ansible no longer looks for Python modules in the current working directory (typically the ``remote_user``'s home directory) when an Ansible module is run. This is to fix becoming an unprivileged user on OpenBSD and to mitigate any attack vector if the current working directory is writable by a malicious user. Install any Python modules needed to run the Ansible modules on the managed node in a system-wide location or in another directory which is in the ``remote_user``'s ``$PYTHONPATH`` and readable by the ``become_user``." -msgstr "Ansible ã¯ã€Ansible モジュールã®å®Ÿè¡Œæ™‚ã«ã€ç¾åœ¨ã®ä½œæ¥ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ (通常㯠``remote_user`` ã®ãƒ›ãƒ¼ãƒ ディレクトリー) ã«ã‚ã‚‹ Python モジュールを検索ã—ãªããªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã«ã‚ˆã‚Šã€OpenBSD ã§æ¨©é™ã®ãªã„ユーザーã«ãªã‚Š (become)ã€æ‚ªæ„ã®ã‚るユーザーãŒç¾åœ¨ã®ä½œæ¥ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã‚’書ãè¾¼ã¿å¯èƒ½ãªå ´åˆã«æ”»æ’ƒãƒ™ã‚¯ãƒˆãƒ«ã‚’軽減ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚Ansible モジュールをã€ã‚·ã‚¹ãƒ†ãƒ 全体ã®ç®¡ç†ãƒŽãƒ¼ãƒ‰ã¾ãŸã¯ ``remote_user`` ã® ``$PYTHONPATH`` ã«ã‚ã‚Šã€``become_user`` ãŒèªã¿å–ã‚Šå¯èƒ½ãªåˆ¥ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ã€Ansible モジュールを実行ã™ã‚‹ã®ã«å¿…è¦ãª Python モジュールをインストールã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:78 -#: ../../rst/porting_guides/porting_guide_2.3.rst:155 -#: ../../rst/porting_guides/porting_guide_2.4.rst:107 -#: ../../rst/porting_guides/porting_guide_2.5.rst:237 -#: ../../rst/porting_guides/porting_guide_2.6.rst:83 -#: ../../rst/porting_guides/porting_guide_2.7.rst:231 -#: ../../rst/porting_guides/porting_guide_2.8.rst:511 -#: ../../rst/porting_guides/porting_guide_2.9.rst:713 -#: ../../rst/porting_guides/porting_guide_4.rst:124 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:71 -#: ../../rst/porting_guides/porting_guide_core_2.11.rst:127 -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:102 -msgid "Plugins" -msgstr "プラグイン" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:81 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:74 -msgid "Lookup plugin names case-sensitivity" -msgstr "大文å—å°æ–‡å—を区別ã—ã¦ãƒ—ラグインåã®æ¤œç´¢" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:83 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:76 -msgid "Prior to Ansible ``2.10`` lookup plugin names passed in as an argument to the ``lookup()`` function were treated as case-insensitive as opposed to lookups invoked via ``with_<lookup_name>``. ``2.10`` brings consistency to ``lookup()`` and ``with_`` to be both case-sensitive." -msgstr "Ansible ``2.10`` ã® lookup プラグインå㌠``lookup()`` 関数ã«å¼•æ•°ã¨ã—ã¦æ¸¡ã•ã‚Œã‚‹å‰ã«ã€``with_<lookup_name>`` を介ã—ã¦å‘¼ã³å‡ºã•ã‚Œã‚‹ãƒ«ãƒƒã‚¯ã‚¢ãƒƒãƒ—ã¨ã¯ç•°ãªã‚Šã€å¤§æ–‡å—ã¨å°æ–‡å—を区別ã—ãªã„ã‚‚ã®ã¨ã—ã¦å‡¦ç†ã•ã‚Œã¾ã™ã€‚``2.10`` ã§ã¯ã€``lookup()`` 㨠``with_`` ã®ä¸¡æ–¹ã§å¤§æ–‡å—å°æ–‡å—を区別ã™ã‚‹ã‚ˆã†ã«æ•´åˆæ€§ãŒå–られã¦ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:86 -#: ../../rst/porting_guides/porting_guide_2.6.rst:94 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:79 -msgid "Noteworthy plugin changes" -msgstr "注目ã™ã¹ãプラグインã®å¤‰æ›´ç‚¹" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:88 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:81 -msgid "Cache plugins in collections can be used to cache data from inventory plugins. Previously, cache plugins in collections could only be used for fact caching." -msgstr "コレクション㮠cache プラグインを使用ã™ã‚‹ã¨ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ—ラグインã‹ã‚‰ãƒ‡ãƒ¼ã‚¿ã‚’ã‚ャッシュã§ãã¾ã™ã€‚以å‰ã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® cache プラグインã¯ãƒ•ã‚¡ã‚¯ãƒˆã‚ャッシュã«ã—ã‹ä½¿ç”¨ã§ãã¾ã›ã‚“ã§ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:89 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:82 -msgid "Some undocumented arguments from ``FILE_COMMON_ARGUMENTS`` have been removed; plugins using these, in particular action plugins, need to be adjusted. The undocumented arguments which were removed are ``src``, ``follow``, ``force``, ``content``, ``backup``, ``remote_src``, ``regexp``, ``delimiter``, and ``directory_mode``." -msgstr "``FILE_COMMON_ARGUMENTS`` ã‹ã‚‰ã€æ–‡æ›¸åŒ–ã•ã‚Œã¦ã„ãªã„引数ãŒã„ãã¤ã‹å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れらã®ç‰¹å®šã®ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ãƒ—ラグインを使用ã™ã‚‹ãƒ—ラグインã¯ã€èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚削除ã•ã‚ŒãŸãƒ‰ã‚ュメントãªã—ã®å¼•æ•°ã¯ã€``src``ã€``follow``ã€``force``ã€``content``ã€``backup``ã€``remote_src``ã€``regexp``ã€``delimiter``ã€ãŠã‚ˆã³ ``directory_mode`` ã§ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:92 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:85 -msgid "Action plugins which execute modules should use fully-qualified module names" -msgstr "モジュールを実行ã™ã‚‹ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ãƒ—ラグインã¯å®Œå…¨ä¿®é£¾ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«åã®ä½¿ç”¨ãŒå¿…è¦" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:94 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:87 -msgid "Action plugins that call modules should pass explicit, fully-qualified module names to ``_execute_module()`` whenever possible (eg, ``ansible.builtin.file`` rather than ``file``). This ensures that the task's collection search order is not consulted to resolve the module. Otherwise, a module from a collection earlier in the search path could be used when not intended." -msgstr "モジュールを呼ã³å‡ºã™ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ãƒ—ラグインã¯ã€å¯èƒ½ãªé™ã‚Šæ˜Žç¤ºçš„ãªå®Œå…¨ä¿®é£¾ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«åã‚’ ``_execute_module()`` ã«æ¸¡ã™å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``file``ã§ã¯ãªã ``ansible.builtin.file``)。ã“ã‚Œã«ã‚ˆã‚Šã€ã‚¿ã‚¹ã‚¯ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³æ¤œç´¢é †åºãŒãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’解決ã™ã‚‹ã‚ˆã†ã«å‚ç…§ã•ã‚Œãªããªã‚Šã¾ã™ã€‚ãã†ã—ãªã„ã¨ã€æ„図ã—ã¦ã„ãªã„ã¨ãã«æ¤œç´¢ãƒ‘スã®å‰ã®æ–¹ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒä½¿ç”¨ã•ã‚Œã¦ã—ã¾ã†å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:99 -#: ../../rst/porting_guides/porting_guide_2.9.rst:45 -#: ../../rst/porting_guides/porting_guide_2.9.rst:724 -#: ../../rst/porting_guides/porting_guide_4.rst:106 -#: ../../rst/porting_guides/porting_guide_4.rst:112 -#: ../../rst/porting_guides/porting_guide_4.rst:133 -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:92 -#: ../../rst/porting_guides/porting_guide_core_2.11.rst:109 -#: ../../rst/porting_guides/porting_guide_core_2.11.rst:115 -#: ../../rst/porting_guides/porting_guide_core_2.11.rst:136 -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:86 -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:92 -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:98 -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:111 -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:117 -msgid "No notable changes" -msgstr "主ãªå¤‰æ›´ã¯ã‚ã‚Šã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:102 -msgid "Porting Guide for v2.10.7" -msgstr "v2.10.7 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:105 -#: ../../rst/porting_guides/porting_guide_2.10.rst:191 -#: ../../rst/porting_guides/porting_guide_2.10.rst:264 -#: ../../rst/porting_guides/porting_guide_2.10.rst:376 -#: ../../rst/porting_guides/porting_guide_2.10.rst:469 -#: ../../rst/porting_guides/porting_guide_3.rst:103 -#: ../../rst/porting_guides/porting_guide_3.rst:205 -#: ../../rst/porting_guides/porting_guide_4.rst:36 -#: ../../rst/porting_guides/porting_guide_4.rst:426 -#: ../../rst/porting_guides/porting_guide_core_2.11.rst:39 -msgid "Breaking Changes" -msgstr "互æ›æ€§ã‚’失ã‚ã›ã‚‹å¤‰æ›´ç‚¹" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:108 -#: ../../rst/porting_guides/porting_guide_2.10.rst:150 -#: ../../rst/porting_guides/porting_guide_2.10.rst:202 -#: ../../rst/porting_guides/porting_guide_2.10.rst:275 -#: ../../rst/porting_guides/porting_guide_2.10.rst:360 -#: ../../rst/porting_guides/porting_guide_2.10.rst:518 -#: ../../rst/porting_guides/porting_guide_2.10.rst:651 -#: ../../rst/porting_guides/porting_guide_2.10.rst:809 -#: ../../rst/porting_guides/porting_guide_2.10.rst:924 -#: ../../rst/porting_guides/porting_guide_3.rst:174 -#: ../../rst/porting_guides/porting_guide_3.rst:225 -#: ../../rst/porting_guides/porting_guide_3.rst:329 -#: ../../rst/porting_guides/porting_guide_3.rst:467 -#: ../../rst/porting_guides/porting_guide_3.rst:608 -#: ../../rst/porting_guides/porting_guide_4.rst:299 -#: ../../rst/porting_guides/porting_guide_4.rst:376 -#: ../../rst/porting_guides/porting_guide_4.rst:448 -#: ../../rst/porting_guides/porting_guide_4.rst:597 -#: ../../rst/porting_guides/porting_guide_4.rst:748 -msgid "community.general" -msgstr "community.general" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:110 -#: ../../rst/porting_guides/porting_guide_3.rst:269 -#: ../../rst/porting_guides/porting_guide_4.rst:459 -msgid "utm_proxy_auth_profile - the ``frontend_cookie_secret`` return value now contains a placeholder string instead of the module's ``frontend_cookie_secret`` parameter (https://github.com/ansible-collections/community.general/pull/1736)." -msgstr "utm_proxy_auth_profile - ``frontend_cookie_secret`` ã®æˆ»ã‚Šå€¤ã«ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã® ``frontend_cookie_secret`` パラメーターã§ã¯ãªãプレースホルダーã®æ–‡å—列ãŒå«ã¾ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/1736)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:113 -#: ../../rst/porting_guides/porting_guide_2.10.rst:147 -#: ../../rst/porting_guides/porting_guide_2.10.rst:199 -#: ../../rst/porting_guides/porting_guide_2.10.rst:272 -#: ../../rst/porting_guides/porting_guide_2.10.rst:384 -#: ../../rst/porting_guides/porting_guide_2.10.rst:425 -#: ../../rst/porting_guides/porting_guide_2.10.rst:613 -#: ../../rst/porting_guides/porting_guide_3.rst:34 -#: ../../rst/porting_guides/porting_guide_3.rst:68 -#: ../../rst/porting_guides/porting_guide_3.rst:131 -#: ../../rst/porting_guides/porting_guide_3.rst:321 -#: ../../rst/porting_guides/porting_guide_4.rst:139 -#: ../../rst/porting_guides/porting_guide_4.rst:164 -#: ../../rst/porting_guides/porting_guide_4.rst:238 -#: ../../rst/porting_guides/porting_guide_4.rst:266 -#: ../../rst/porting_guides/porting_guide_4.rst:322 -#: ../../rst/porting_guides/porting_guide_4.rst:479 -msgid "Major Changes" -msgstr "主ãªå¤‰æ›´ç‚¹" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:115 -msgid "Restricting the version of the community.okd collection to 1.0.0. The previously included version, 1.0.1, had a dependency on kubernetes.core and thus required the installation of an additional collection that was not included in Ansible 2.10. Version 1.0.0 is essentially identical to 1.0.1, except that it uses community.kubernetes, wihch is included in Ansible 2.10." -msgstr "community.okd コレクションã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’ 1.0.0 ã«åˆ¶é™ã—ã¾ã—ãŸã€‚ã“ã‚Œã¾ã§å«ã¾ã‚Œã¦ã„ãŸãƒãƒ¼ã‚¸ãƒ§ãƒ³ 1.0.1 ã¯ã€kubernetes.core ã«ä¾å˜ã—ã¦ã„ãŸãŸã‚ã€Ansible 2.10 ã«å«ã¾ã‚Œã¦ã„ãªã„è¿½åŠ ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã—ãŸã€‚ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 1.0.0 ã¯ã€Ansible 2.10 ã«å«ã¾ã‚Œã¦ã„ã‚‹ community.kubernetes を使用ã—ã¦ã„る以外ã¯ã€1.0.1 ã¨åŸºæœ¬çš„ã«åŒã˜ã§ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:118 -#: ../../rst/porting_guides/porting_guide_2.10.rst:392 -#: ../../rst/porting_guides/porting_guide_2.10.rst:739 -#: ../../rst/porting_guides/porting_guide_3.rst:415 -#: ../../rst/porting_guides/porting_guide_4.rst:172 -msgid "ovirt.ovirt" -msgstr "ovirt.ovirt" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:120 -#: ../../rst/porting_guides/porting_guide_3.rst:424 -msgid "ovirt_system_option_info - Add new module (https://github.com/oVirt/ovirt-ansible-collection/pull/206)." -msgstr "ovirt_system_option_info - æ–°ã—ã„ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/206)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:123 -#: ../../rst/porting_guides/porting_guide_3.rst:430 -#: ../../rst/porting_guides/porting_guide_4.rst:469 -#: ../../rst/porting_guides/porting_guide_4.rst:569 -msgid "servicenow.servicenow" -msgstr "servicenow.servicenow" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:125 -#: ../../rst/porting_guides/porting_guide_3.rst:432 -msgid "add new tests (find with no result, search many)" -msgstr "æ–°è¦ãƒ†ã‚¹ãƒˆã®è¿½åŠ (çµæžœãŒãªã„検索ã€å¤šæ•°ã®æ¤œç´¢)" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:126 -#: ../../rst/porting_guides/porting_guide_3.rst:433 -msgid "add related tests" -msgstr "関連テストã®è¿½åŠ " - -#: ../../rst/porting_guides/porting_guide_2.10.rst:127 -#: ../../rst/porting_guides/porting_guide_3.rst:434 -msgid "add support for ServiceNOW table api display_value exclude_reference_link and suppress_pagination_header" -msgstr "ServiceNOW テーブル api display_value exclude_reference_link ãŠã‚ˆã³ suppress_pagination_header ã®ã‚µãƒãƒ¼ãƒˆã‚’è¿½åŠ " - -#: ../../rst/porting_guides/porting_guide_2.10.rst:128 -#: ../../rst/porting_guides/porting_guide_3.rst:435 -msgid "use new API for pysnow >=0.6.0" -msgstr "0.6.0 以é™ã® pysnow ã§æ–°ã—ã„ API ã®ä½¿ç”¨" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:131 -#: ../../rst/porting_guides/porting_guide_2.10.rst:238 -#: ../../rst/porting_guides/porting_guide_2.10.rst:357 -#: ../../rst/porting_guides/porting_guide_2.10.rst:414 -#: ../../rst/porting_guides/porting_guide_2.10.rst:434 -#: ../../rst/porting_guides/porting_guide_2.10.rst:851 -#: ../../rst/porting_guides/porting_guide_3.rst:52 -#: ../../rst/porting_guides/porting_guide_3.rst:76 -#: ../../rst/porting_guides/porting_guide_3.rst:111 -#: ../../rst/porting_guides/porting_guide_3.rst:155 -#: ../../rst/porting_guides/porting_guide_3.rst:587 -#: ../../rst/porting_guides/porting_guide_4.rst:153 -#: ../../rst/porting_guides/porting_guide_4.rst:177 -#: ../../rst/porting_guides/porting_guide_4.rst:207 -#: ../../rst/porting_guides/porting_guide_4.rst:246 -#: ../../rst/porting_guides/porting_guide_4.rst:287 -#: ../../rst/porting_guides/porting_guide_4.rst:363 -#: ../../rst/porting_guides/porting_guide_4.rst:709 -msgid "Deprecated Features" -msgstr "éžæŽ¨å¥¨ã®æ©Ÿèƒ½" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:134 -#: ../../rst/porting_guides/porting_guide_2.10.rst:417 -#: ../../rst/porting_guides/porting_guide_2.10.rst:437 -#: ../../rst/porting_guides/porting_guide_3.rst:590 -#: ../../rst/porting_guides/porting_guide_4.rst:215 -#: ../../rst/porting_guides/porting_guide_4.rst:527 -#: ../../rst/porting_guides/porting_guide_4.rst:724 -msgid "cisco.nxos" -msgstr "cisco.nxos" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:136 -#: ../../rst/porting_guides/porting_guide_3.rst:592 -msgid "Deprecated `nxos_bgp` and `nxos_bgp_neighbor` modules in favor of `nxos_bgp_global` resource module." -msgstr "`nxos_bgp` モジュールãŠã‚ˆã³ `nxos_bgp_neighbor` モジュールãŒéžæŽ¨å¥¨ã¨ãªã‚Šã€`nxos_bgp_global` リソースモジュールãŒä½¿ç”¨ã•ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:139 -#: ../../rst/porting_guides/porting_guide_2.10.rst:537 -#: ../../rst/porting_guides/porting_guide_2.10.rst:827 -#: ../../rst/porting_guides/porting_guide_2.10.rst:944 -#: ../../rst/porting_guides/porting_guide_3.rst:79 -#: ../../rst/porting_guides/porting_guide_3.rst:634 -#: ../../rst/porting_guides/porting_guide_4.rst:269 -#: ../../rst/porting_guides/porting_guide_4.rst:767 -msgid "community.vmware" -msgstr "community.vmware" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:141 -#: ../../rst/porting_guides/porting_guide_3.rst:636 -msgid "vmware_host_firewall_manager - the creation of new rule with no ``allowed_ip`` entry in the ``allowed_hosts`` dictionary won't be allowed after 2.0.0 release." -msgstr "vmware_host_firewall_manager - ``allowed_hosts`` ディクショナリー㫠``allowed_ip`` エントリーãŒãªã„æ–°è¦ãƒ«ãƒ¼ãƒ«ã®ä½œæˆã¯ã€2.0.0 リリース後ã¯è¨±å¯ã•ã‚Œãªããªã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:144 -msgid "Porting Guide for v2.10.6" -msgstr "v2.10.6 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:152 -msgid "For community.general 2.0.0, the kubevirt modules will be moved to the `community.kubevirt <https://galaxy.ansible.com/community/kubevirt>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." -msgstr "community.general 2.0.0 ã®å ´åˆã€kubevirt モジュール㯠`community.kubevirt <https://galaxy.ansible.com/community/kubevirt>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:155 -msgid "If you use Ansible 2.9 and explicitly use kubevirt modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.kubevirt.`` instead of ``community.general.``, for example replace ``community.general.kubevirt_vm`` in a task by ``community.kubevirt.kubevirt_vm``." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ã® kubevirt モジュールを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€``community.general.`` ã§ã¯ãªã ``community.kubevirt.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã« Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’調整ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``community.kubevirt.kubevirt_vm`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.general.kubevirt_vm`` ã‚’ç½®ãæ›ãˆã¾ã™)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:158 -msgid "If you use ansible-base and installed ``community.general`` manually and rely on the kubevirt modules, you have to make sure to install the ``community.kubevirt`` collection as well. If you are using FQCNs, for example ``community.general.kubevirt_vm`` instead of ``kubevirt_vm``, it will continue working, but we still recommend to adjust the FQCNs as well." -msgstr "ansible-base を使用ã—㦠``community.general`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€kubevirt モジュールã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.kubevirt`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãŸã¨ãˆã° ``kubevirt_vm`` ã®ä»£ã‚ã‚Šã« ``community.general.kubevirt_vm`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:162 -#: ../../rst/porting_guides/porting_guide_2.10.rst:304 -#: ../../rst/porting_guides/porting_guide_2.10.rst:368 -#: ../../rst/porting_guides/porting_guide_2.10.rst:532 -#: ../../rst/porting_guides/porting_guide_2.10.rst:822 -#: ../../rst/porting_guides/porting_guide_3.rst:282 -#: ../../rst/porting_guides/porting_guide_3.rst:551 -#: ../../rst/porting_guides/porting_guide_3.rst:629 -#: ../../rst/porting_guides/porting_guide_4.rst:687 -msgid "community.network" -msgstr "community.network" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:164 -msgid "For community.network 2.0.0, the Cisco NSO modules will be moved to the `cisco.nso <https://galaxy.ansible.com/cisco/nso>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." -msgstr "community.network 2.0.0 ã§ã¯ã€Cisco NSO モジュール㯠`cisco.nso <https://galaxy.ansible.com/cisco/nso>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã—ãªãã¦ã‚‚よã„よã†ã«ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæŒ¿å…¥ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:167 -msgid "If you use Ansible 2.9 and explicitly use Cisco NSO modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``cisco.nso.`` instead of ``community.network.``, for example replace ``community.network.nso_config`` in a task by ``cisco.nso.nso_config``." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ Cisco NSO モジュールを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.network.`` ã§ã¯ãªã ``cisco.nso.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``cisco.nso.nso_config`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.network.nso_config`` ã‚’ç½®ãæ›ãˆã¾ã™)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:170 -msgid "If you use ansible-base and installed ``community.network`` manually and rely on the Cisco NSO modules, you have to make sure to install the ``cisco.nso`` collection as well. If you are using FQCNs, for example ``community.network.nso_config`` instead of ``nso_config``, it will continue working, but we still recommend to adjust the FQCNs as well." -msgstr "ansible-base を使用ã—㦠``community.network`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€Cisco NSO モジュールã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``cisco.nso`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ãŸã¨ãˆã° ``nso_config`` ã®ä»£ã‚ã‚Šã« ``community.network.nso_config`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:172 -msgid "For community.network 2.0.0, the FortiOS modules will be moved to the `community.fortios <https://galaxy.ansible.com/ansible-collections/community.fortios>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." -msgstr "community.network 2.0.0 ã§ã¯ã€FortiOS モジュール㯠`community.fortios <https://galaxy.ansible.com/ansible-collections/community.fortios>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã—ãªãã¦ã‚‚よã„よã†ã«ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæŒ¿å…¥ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:175 -msgid "If you use Ansible 2.9 and explicitly use FortiOS modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.fortios.`` instead of ``community.network.``, for example replace ``community.network.fmgr_device`` in a task by ``community.fortios.fmgr_device``." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ FortiOS モジュールを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.network.`` ã§ã¯ãªã ``community.fortios.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``community.fortios.fmgr_device`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.network.fmgr_device`` ã‚’ç½®ãæ›ãˆã¾ã™)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:178 -msgid "If you use ansible-base and installed ``community.network`` manually and rely on the FortiOS modules, you have to make sure to install the ``community.fortios`` collection as well. If you are using FQCNs, for example ``community.network.fmgr_device`` instead of ``fmgr_device``, it will continue working, but we still recommend to adjust the FQCNs as well." -msgstr "ansible-base を使用ã—㦠``community.network`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€FortiOS モジュールã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.fortios`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ãŸã¨ãˆã° ``fmgr_device`` ã®ä»£ã‚ã‚Šã« ``community.network.fmgr_device`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:182 -#: ../../rst/porting_guides/porting_guide_2.10.rst:387 -#: ../../rst/porting_guides/porting_guide_2.10.rst:409 -#: ../../rst/porting_guides/porting_guide_2.10.rst:728 -#: ../../rst/porting_guides/porting_guide_2.10.rst:841 -#: ../../rst/porting_guides/porting_guide_2.10.rst:958 -#: ../../rst/porting_guides/porting_guide_3.rst:84 -#: ../../rst/porting_guides/porting_guide_3.rst:148 -#: ../../rst/porting_guides/porting_guide_3.rst:373 -#: ../../rst/porting_guides/porting_guide_3.rst:582 -#: ../../rst/porting_guides/porting_guide_4.rst:693 -#: ../../rst/porting_guides/porting_guide_4.rst:772 -msgid "f5networks.f5_modules" -msgstr "f5networks.f5_modules" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:184 -#: ../../rst/porting_guides/porting_guide_3.rst:376 -msgid "Added async_timeout parameter to bigip_ucs_fetch module to allow customization of module wait for async interface" -msgstr "bigip_ucs_fetch モジュール㫠async_timeout ãƒ‘ãƒ©ãƒ¡ãƒ¼ã‚¿ãƒ¼ã‚’è¿½åŠ ã—ã¦ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒ async インターフェースを待機ã§ãるよã†ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:185 -#: ../../rst/porting_guides/porting_guide_3.rst:377 -msgid "Changed bigip_ucs_fetch module to use asynchronous interface when generating UCS files" -msgstr "UCS ファイルã®ç”Ÿæˆæ™‚ã«éžåŒæœŸã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ã‚’使用ã™ã‚‹ã‚ˆã†ã« bigip_ucs_fetch モジュールã®å¤‰æ›´" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:188 -msgid "Porting Guide for v2.10.5" -msgstr "v2.10.5 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:194 -#: ../../rst/porting_guides/porting_guide_2.10.rst:251 -#: ../../rst/porting_guides/porting_guide_3.rst:272 -#: ../../rst/porting_guides/porting_guide_3.rst:619 -#: ../../rst/porting_guides/porting_guide_4.rst:249 -#: ../../rst/porting_guides/porting_guide_4.rst:305 -msgid "community.hashi_vault" -msgstr "community.hashi_vault" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:196 -#: ../../rst/porting_guides/porting_guide_3.rst:274 -msgid "hashi_vault - the ``VAULT_ADDR`` environment variable is now checked last for the ``url`` parameter. For details on which use cases are impacted, see (https://github.com/ansible-collections/community.hashi_vault/issues/8)." -msgstr "hashi_vault - ``VAULT_ADDR`` 環境変数ãŒã€æœ€å¾Œã« ``url`` パラメーターã«ã¤ã„ã¦ãƒã‚§ãƒƒã‚¯ã•ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚影響をå—ã‘るユースケースã®è©³ç´°ã¯ã€https://github.com/ansible-collections/community.hashi_vault/issues/8 ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:204 -msgid "For community.general 2.0.0, the Google modules will be moved to the `community.google <https://galaxy.ansible.com/community/google>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." -msgstr "community.general 2.0.0 ã®å ´åˆã€Google モジュール㯠`community.google <https://galaxy.ansible.com/community/google>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:207 -msgid "If you use Ansible 2.9 and explicitly use Google modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.google.`` instead of ``community.general.``, for example replace ``community.general.gcpubsub`` in a task by ``community.google.gcpubsub``." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ Google モジュールを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.general.`` ã§ã¯ãªã ``community.google.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``community.google.gcpubsub`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.general.gcpubsub`` ã‚’ç½®ãæ›ãˆã¾ã™)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:210 -msgid "If you use ansible-base and installed ``community.general`` manually and rely on the Google modules, you have to make sure to install the ``community.google`` collection as well. If you are using FQCNs, for example ``community.general.gcpubsub`` instead of ``gcpubsub``, it will continue working, but we still recommend to adjust the FQCNs as well." -msgstr "ansible-base を使用ã—㦠``community.general`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€Google モジュールã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.google`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ãŸã¨ãˆã° ``gcpubsub`` ã®ä»£ã‚ã‚Šã« ``community.general.gcpubsub`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:212 -msgid "For community.general 2.0.0, the OC connection plugin will be moved to the `community.okd <https://galaxy.ansible.com/community/okd>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." -msgstr "community.general 2.0.0 ã®å ´åˆã€OC 接続プラグイン㯠`community.okd <https://galaxy.ansible.com/community/okd>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:215 -msgid "If you use Ansible 2.9 and explicitly use OC connection plugin from this collection, you will need to adjust your playbooks and roles to use FQCNs ``community.okd.oc`` instead of ``community.general.oc``." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ OC 接続プラグインを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.general.oc`` ã§ã¯ãªã FQCN ã® ``community.okd.oc`` を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:217 -msgid "If you use ansible-base and installed ``community.general`` manually and rely on the OC connection plugin, you have to make sure to install the ``community.okd`` collection as well. If you are using FQCNs, in other words ``community.general.oc`` instead of ``oc``, it will continue working, but we still recommend to adjust this FQCN as well." -msgstr "ansible-base を使用ã—ã€æ‰‹å‹•ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—㟠``community.general`` を使用ã—ã€OC 接続プラグインã«ä¾å˜ã™ã‚‹å ´åˆã¯ã€``community.okd`` コレクションもインストールã—ã¦ãã ã•ã„。FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ã¤ã¾ã‚Šã€``oc`` ã®ä»£ã‚ã‚Šã« ``community.general.oc`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ã‚’推奨ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:219 -msgid "For community.general 2.0.0, the hashi_vault lookup plugin will be moved to the `community.hashi_vault <https://galaxy.ansible.com/community/hashi_vault>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." -msgstr "community.general 2.0.0 ã®å ´åˆã€hashi_vault lookup プラグイン㯠`community.hashi_vault <https://galaxy.ansible.com/community/hashi_vault>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:222 -msgid "If you use Ansible 2.9 and explicitly use hashi_vault lookup plugin from this collection, you will need to adjust your playbooks and roles to use FQCNs ``community.hashi_vault.hashi_vault`` instead of ``community.general.hashi_vault``." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® hashi_vault lookup プラグインを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€``community.general.hashi_vault`` ã§ã¯ãªã FQCN ``community.hashi_vault.hashi_vault`` を使用ã™ã‚‹ã‚ˆã†ã« Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’調整ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:224 -msgid "If you use ansible-base and installed ``community.general`` manually and rely on the hashi_vault lookup plugin, you have to make sure to install the ``community.hashi_vault`` collection as well. If you are using FQCNs, in other words ``community.general.hashi_vault`` instead of ``hashi_vault``, it will continue working, but we still recommend to adjust this FQCN as well." -msgstr "ansible-base を使用ã—ã€æ‰‹å‹•ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—㟠``community.general`` を手動ã§ã—ã€hashi_vault lookup プラグインã«ä¾å˜ã™ã‚‹å ´åˆã¯ã€``community.hashi_vault`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ã¤ã¾ã‚Šã€``hashi_vault`` ã§ã¯ãªã ``community.general.hashi_vault`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ã‚’推奨ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:228 -#: ../../rst/porting_guides/porting_guide_2.10.rst:559 -#: ../../rst/porting_guides/porting_guide_3.rst:405 -#: ../../rst/porting_guides/porting_guide_4.rst:350 -msgid "netbox.netbox" -msgstr "netbox.netbox" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:230 -#: ../../rst/porting_guides/porting_guide_3.rst:407 -msgid "nb_inventory - Add ``dns_name`` option that adds ``dns_name`` to the host when ``True`` and device has a primary IP address. (#394)" -msgstr "nb_inventory - ``True`` ãŠã‚ˆã³ãƒ‡ãƒã‚¤ã‚¹ã«ãƒ—ライマリー IP アドレスãŒã‚ã‚‹å ´åˆã« ``dns_name`` をホストã«è¿½åŠ ã™ã‚‹ ``dns_name`` ã‚ªãƒ—ã‚·ãƒ§ãƒ³ã‚’è¿½åŠ ã—ã¾ã™ã€‚(#394)" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:231 -#: ../../rst/porting_guides/porting_guide_3.rst:408 -msgid "nb_inventory - Add ``status`` as a ``group_by`` option. (398)" -msgstr "nb_inventory - ``group_by`` オプションã¨ã—㦠``status`` ã‚’è¿½åŠ ã—ã¾ã™ã€‚(398)" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:232 -#: ../../rst/porting_guides/porting_guide_3.rst:409 -msgid "nb_inventory - Move around ``extracted_primary_ip`` to allow for ``config_context`` or ``custom_field`` to overwite. (#377)" -msgstr "nb_inventory - ``config_context`` ã¾ãŸã¯ ``custom_field`` ã®ä¸Šæ›¸ãを許å¯ã™ã‚‹ ``extracted_primary_ip`` を移動ã—ã¾ã™ã€‚(#377)" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:233 -#: ../../rst/porting_guides/porting_guide_3.rst:410 -msgid "nb_inventory - Services are now a list of integers due to NetBox 2.10 changes. (#396)" -msgstr "nb_inventory - サービスã¯ã€NetBox 2.10 ã®å¤‰æ›´ã«ã‚ˆã‚Šæ•´æ•°ã®ä¸€è¦§ã«ãªã‚Šã¾ã—ãŸã€‚(#396)" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:234 -#: ../../rst/porting_guides/porting_guide_3.rst:411 -msgid "nb_lookup - Allow ID to be passed in and use ``.get`` instead of ``.filter``. (#376)" -msgstr "nb_lookup - ID を渡ã™ã“ã¨ãŒã§ãã€``.filter`` ã®ä»£ã‚ã‚Šã« ``.get`` を使用ã§ãã¾ã™ã€‚(#376)" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:235 -#: ../../rst/porting_guides/porting_guide_3.rst:412 -msgid "nb_lookup - Allow ``api_endpoint`` and ``token`` to be found via env. (#391)" -msgstr "nb_lookup - ``api_endpoint`` ãŠã‚ˆã³ ``token`` ã‚’ env 経由ã§æ¤œç´¢ã™ã‚‹ã“ã¨ã‚’許å¯ã—ã¾ã™ã€‚(#391)" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:241 -#: ../../rst/porting_guides/porting_guide_2.10.rst:892 -#: ../../rst/porting_guides/porting_guide_3.rst:55 -#: ../../rst/porting_guides/porting_guide_3.rst:163 -#: ../../rst/porting_guides/porting_guide_3.rst:598 -#: ../../rst/porting_guides/porting_guide_4.rst:735 -msgid "community.aws" -msgstr "community.aws" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:243 -#: ../../rst/porting_guides/porting_guide_3.rst:600 -msgid "ec2_vpc_igw_info - After 2022-06-22 the ``convert_tags`` parameter default value will change from ``False`` to ``True`` to match the collection standard behavior (https://github.com/ansible-collections/community.aws/pull/318)." -msgstr "ec2_vpc_igw_info - 2022-06-22 以é™ã€``convert_tags`` パラメーターã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ãŒ ``False`` ã‹ã‚‰ ``True`` ã«å¤‰æ›´ã—ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®æ¨™æº–動作ã¨ä¸€è‡´ã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã™ (https://github.com/ansible-collections/community.aws/pull/318)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:246 -#: ../../rst/porting_guides/porting_guide_2.10.rst:331 -#: ../../rst/porting_guides/porting_guide_3.rst:60 -#: ../../rst/porting_guides/porting_guide_3.rst:106 -#: ../../rst/porting_guides/porting_guide_3.rst:441 -#: ../../rst/porting_guides/porting_guide_3.rst:603 -#: ../../rst/porting_guides/porting_guide_4.rst:220 -#: ../../rst/porting_guides/porting_guide_4.rst:371 -#: ../../rst/porting_guides/porting_guide_4.rst:443 -msgid "community.docker" -msgstr "community.docker" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:248 -#: ../../rst/porting_guides/porting_guide_3.rst:605 -msgid "docker_container - currently ``published_ports`` can contain port mappings next to the special value ``all``, in which case the port mappings are ignored. This behavior is deprecated for community.docker 2.0.0, at which point it will either be forbidden, or this behavior will be properly implemented similar to how the Docker CLI tool handles this (https://github.com/ansible-collections/community.docker/issues/8, https://github.com/ansible-collections/community.docker/pull/60)." -msgstr "docker_container - ç¾åœ¨ã€``published_ports`` ã«ã¯ã€ç‰¹åˆ¥ãªå€¤ ``all`` ã®æ¨ªã«ãƒãƒ¼ãƒˆãƒžãƒƒãƒ”ングをå«ã‚ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã®å‹•ä½œã¯ã€community.docker 2.0.0 ã§ã¯éžæŽ¨å¥¨ã§ã™ã€‚ãã®æ™‚点ã§ã€ç¦æ¢ã•ã‚Œã‚‹ã‹ã€Docker CLI ツールãŒã©ã®ã‚ˆã†ã«ã“れを処ç†ã™ã‚‹ã‹ã¨åŒã˜ã‚ˆã†ã«ã€ã“ã®å‹•ä½œãŒé©åˆ‡ã«å®Ÿè£…ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.docker/issues/8ã€https://github.com/ansible-collections/community.docker/pull/60)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:253 -#: ../../rst/porting_guides/porting_guide_3.rst:621 -msgid "hashi_vault - ``VAULT_ADDR`` environment variable for option ``url`` will have its precedence lowered in 1.0.0; use ``ANSIBLE_HASHI_VAULT_ADDR`` to intentionally override a config value (https://github.com/ansible-collections/community.hashi_vault/issues/8)." -msgstr "hashi_vault - オプション ``url`` ã® ``VAULT_ADDR`` 環境変数ã®å„ªå…ˆåº¦ã¯ 1.0.0 ã§ä½Žããªã‚Šã¾ã™ã€‚è¨å®šå€¤ã‚’æ„図的ã«ä¸Šæ›¸ãã™ã‚‹ã«ã¯ ``ANSIBLE_HASHI_VAULT_ADDR`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.hashi_vault/issues/8)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:254 -#: ../../rst/porting_guides/porting_guide_3.rst:622 -msgid "hashi_vault - ``VAULT_AUTH_METHOD`` environment variable for option ``auth_method`` will be removed in 2.0.0, use ``ANSIBLE_HASHI_VAULT_AUTH_METHOD`` instead (https://github.com/ansible-collections/community.hashi_vault/issues/17)." -msgstr "hashi_vault - オプション ``auth_method`` ã® ``VAULT_AUTH_METHOD`` 環境変数㯠2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ``ANSIBLE_HASHI_VAULT_AUTH_METHOD`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.hashi_vault/issues/17)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:255 -#: ../../rst/porting_guides/porting_guide_3.rst:623 -msgid "hashi_vault - ``VAULT_ROLE_ID`` environment variable for option ``role_id`` will be removed in 2.0.0, use ``ANSIBLE_HASHI_VAULT_ROLE_ID`` instead (https://github.com/ansible-collections/community.hashi_vault/issues/20)." -msgstr "hashi_vault - オプション ``role_id`` ã® ``VAULT_ROLE_ID`` 環境変数㯠2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ``ANSIBLE_HASHI_VAULT_ROLE_ID`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.hashi_vault/issues/20)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:256 -#: ../../rst/porting_guides/porting_guide_3.rst:624 -msgid "hashi_vault - ``VAULT_SECRET_ID`` environment variable for option ``secret_id`` will be removed in 2.0.0, use ``ANSIBLE_HASHI_VAULT_SECRET_ID`` instead (https://github.com/ansible-collections/community.hashi_vault/issues/20)." -msgstr "hashi_vault - オプション ``secret_id`` ã® ``VAULT_SECRET_ID`` 環境変数㯠2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ``ANSIBLE_HASHI_VAULT_SECRET_ID`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.hashi_vault/issues/20)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:257 -#: ../../rst/porting_guides/porting_guide_3.rst:625 -msgid "hashi_vault - ``VAULT_TOKEN_FILE`` environment variable for option ``token_file`` will be removed in 2.0.0, use ``ANSIBLE_HASHI_VAULT_TOKEN_FILE`` instead (https://github.com/ansible-collections/community.hashi_vault/issues/15)." -msgstr "hashi_vault - オプション ``token_file`` ã® ``VAULT_TOKEN_FILE`` 環境変数㯠2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ``ANSIBLE_HASHI_VAULT_TOKEN_FILE`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.hashi_vault/issues/15)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:258 -#: ../../rst/porting_guides/porting_guide_3.rst:626 -msgid "hashi_vault - ``VAULT_TOKEN_PATH`` environment variable for option ``token_path`` will be removed in 2.0.0, use ``ANSIBLE_HASHI_VAULT_TOKEN_PATH`` instead (https://github.com/ansible-collections/community.hashi_vault/issues/15)." -msgstr "hashi_vault - オプション ``token_path`` ã® ``VAULT_TOKEN_PATH`` 環境変数㯠2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ``ANSIBLE_HASHI_VAULT_TOKEN_PATH`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.hashi_vault/issues/15)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:261 -msgid "Porting Guide for v2.10.4" -msgstr "v2.10.4 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:267 -#: ../../rst/porting_guides/porting_guide_3.rst:277 -msgid "community.hrobot" -msgstr "community.hrobot" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:269 -#: ../../rst/porting_guides/porting_guide_3.rst:279 -msgid "firewall - now requires the `ipaddress <https://pypi.org/project/ipaddress/>`_ library (https://github.com/ansible-collections/community.hrobot/pull/2)." -msgstr "firewall - `ipaddress <https://pypi.org/project/ipaddress/>`_ ライブラリーãŒå¿…è¦ã«ãªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.hrobot/pull/2)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:277 -msgid "For community.general 2.0.0, the Hetzner Robot modules will be moved to the `community.hrobot <https://galaxy.ansible.com/community/hrobot>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." -msgstr "community.general 2.0.0 ã®å ´åˆã€Heatzner Robot モジュール㌠`community.hrobot <https://galaxy.ansible.com/community/hrobot>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã—ãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:280 -msgid "If you use Ansible 2.9 and explicitly use Hetzner Robot modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.hrobot.`` instead of ``community.general.hetzner_``, for example replace ``community.general.hetzner_firewall_info`` in a task by ``community.hrobot.firewall_info``." -msgstr "Ansible 2.9 を使用ã—ã¦ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ Hetzner Robot モジュールを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€``community.general.hetzner_`` ã§ã¯ãªã ``community.hrobot.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã« Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’調整ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``community.hrobot.firewall_info`` ã§ã€ã‚¿ã‚¹ã‚¯å†…ã® ``community.general.hetzner_firewall_info`` ã‚’ç½®ãæ›ãˆã¾ã™)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:283 -msgid "If you use ansible-base and installed ``community.general`` manually and rely on the Hetzner Robot modules, you have to make sure to install the ``community.hrobot`` collection as well. If you are using FQCNs, i.e. ``community.general.hetzner_failover_ip`` instead of ``hetzner_failover_ip``, it will continue working, but we still recommend to adjust the FQCNs as well." -msgstr "ansible-base を使用ã—㦠``community.general`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€Hetzner Robot モジュールã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.hrobot`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ãŸã¨ãˆã° ``hetzner_failover_ip`` ã®ä»£ã‚ã‚Šã« ``community.general.hetzner_failover_ip`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:285 -msgid "For community.general 2.0.0, the ``docker`` modules and plugins will be moved to the `community.docker <https://galaxy.ansible.com/community/docker>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." -msgstr "community.general 2.0.0 ã®å ´åˆã€``docker`` モジュールãŠã‚ˆã³ãƒ—ラグイン㯠`community.docker <https://galaxy.ansible.com/community/docker>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:288 -msgid "If you use Ansible 2.9 and explicitly use ``docker`` content from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.docker.`` instead of ``community.general.``, for example replace ``community.general.docker_container`` in a task by ``community.docker.docker_container``." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ ``docker`` コンテンツを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.general.`` ã§ã¯ãªã ``community.docker.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``community.docker.docker_container`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.general.docker_container`` ã‚’ç½®ãæ›ãˆã¾ã™)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:291 -msgid "If you use ansible-base and installed ``community.general`` manually and rely on the ``docker`` content, you have to make sure to install the ``community.docker`` collection as well. If you are using FQCNs, i.e. ``community.general.docker_container`` instead of ``docker_container``, it will continue working, but we still recommend to adjust the FQCNs as well." -msgstr "ansible-base を使用ã—㦠``community.general`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€``docker`` コンテンツã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.docker`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ã¤ã¾ã‚Š ``docker_container`` ã®ä»£ã‚ã‚Šã« ``community.general.docker_container`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:293 -msgid "For community.general 2.0.0, the ``postgresql`` modules and plugins will be moved to the `community.postgresql <https://galaxy.ansible.com/community/postgresql>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." -msgstr "community.general 2.0.0 ã®å ´åˆã€``postgresql`` モジュールãŠã‚ˆã³ãƒ—ラグイン㯠`community.postgresql <https://galaxy.ansible.com/community/postgresql>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:296 -msgid "If you use Ansible 2.9 and explicitly use ``postgresql`` content from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.postgresql.`` instead of ``community.general.``, for example replace ``community.general.postgresql_info`` in a task by ``community.postgresql.postgresql_info``." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ ``postgresql`` コンテンツを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.general.`` ã§ã¯ãªã ``community.postgresql.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``community.postgresql.postgresql_info`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.general.postgresql_info`` ã‚’ç½®ãæ›ãˆã¾ã™)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:299 -msgid "If you use ansible-base and installed ``community.general`` manually and rely on the ``postgresql`` content, you have to make sure to install the ``community.postgresql`` collection as well. If you are using FQCNs, i.e. ``community.general.postgresql_info`` instead of ``postgresql_info``, it will continue working, but we still recommend to adjust the FQCNs as well." -msgstr "ansible-base を使用ã—㦠``community.general`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€``postgresql`` コンテンツã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.postgresql`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ã¤ã¾ã‚Š ``postgresql_info`` ã®ä»£ã‚ã‚Šã« ``community.general.postgresql_info`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:301 -#: ../../rst/porting_guides/porting_guide_3.rst:340 -msgid "The community.general collection no longer depends on the ansible.posix collection (https://github.com/ansible-collections/community.general/pull/1157)." -msgstr "community.general コレクション㯠ansible.posix コレクションã«ä¾å˜ã—ãªããªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/1157)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:306 -msgid "For community.network 2.0.0, the ``routeros`` modules and plugins will be moved to the `community.routeros <https://galaxy.ansible.com/community/routeros>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." -msgstr "community.network 2.0.0 ã®å ´åˆã€``routeros`` モジュールãŠã‚ˆã³ãƒ—ラグイン㯠`community.routeros <https://galaxy.ansible.com/community/routeros>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:309 -msgid "If you use Ansible 2.9 and explicitly use ``routeros`` content from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.routeros.`` instead of ``community.network.routeros_``, for example replace ``community.network.routeros_api`` in a task by ``community.routeros.api``." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ ``routeros`` コンテンツを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.network.routeros_`` ã§ã¯ãªã ``community.routeros.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``community.routeros.api`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.network.routeros_api`` ã‚’ç½®ãæ›ãˆã¾ã™)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:312 -msgid "If you use ansible-base and installed ``community.network`` manually and rely on the ``routeros`` content, you have to make sure to install the ``community.routeros`` collection as well. If you are using FQCNs, i.e. ``community.network.routeros_command`` instead of ``routeros_command``, it will continue working, but we still recommend to adjust the FQCNs as well." -msgstr "ansible-base を使用ã—㦠``community.network`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€``routeros`` コンテンツã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.routeros`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ã¤ã¾ã‚Š ``routeros_command`` ã®ä»£ã‚ã‚Šã« ``community.network.routeros_command`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:314 -msgid "In community.network 2.0.0, the ``fortimanager`` httpapi plugin will be removed and replaced by a redirect to the corresponding plugin in the fortios.fortimanager collection. For Ansible 2.10 and ansible-base 2.10 users, this means that it will continue to work assuming that collection is installed. For Ansible 2.9 users, this means that they have to adjust the FQCN from ``community.network.fortimanager`` to ``fortios.fortimanager.fortimanager`` (https://github.com/ansible-collections/community.network/pull/151)." -msgstr "community.network 2.0.0 ã§ã¯ã€``fortimanager`` httpapi プラグインãŒå‰Šé™¤ã•ã‚Œã€fortios.fortimanager コレクションã«ã‚る対応ã™ã‚‹ãƒ—ラグインã¸ã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚Ansible 2.10 ãŠã‚ˆã³ ansible-base 2.10 ユーザーã®å ´åˆã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã¨ä»®å®šã—ã¦å‹•ä½œã¯ç¶™ç¶šã—ã¾ã™ã€‚Ansible 2.9 ユーザーã¯ã€FQCN ã‚’ ``community.network.fortimanager`` ã‹ã‚‰ ``fortios.fortimanager.fortimanager`` ã¸èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚(https://github.com/ansible-collections/community.network/pull/151)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:317 -#: ../../rst/porting_guides/porting_guide_3.rst:349 -msgid "community.okd" -msgstr "community.okd" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:319 -#: ../../rst/porting_guides/porting_guide_3.rst:351 -msgid "Add custom k8s module, integrate better Molecule tests (https://github.com/ansible-collections/community.okd/pull/7)." -msgstr "カスタムk8s ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’è¿½åŠ ã—ã€å„ªã‚ŒãŸ Molecule テストを統åˆã—ã¾ã™ (https://github.com/ansible-collections/community.okd/pull/7)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:320 -#: ../../rst/porting_guides/porting_guide_3.rst:352 -msgid "Add downstream build scripts to build redhat.openshift (https://github.com/ansible-collections/community.okd/pull/20)." -msgstr "redhat.openshift を構築ã™ã‚‹ãŸã‚ã®ãƒ€ã‚¦ãƒ³ã‚¹ãƒˆãƒªãƒ¼ãƒ ãƒ“ãƒ«ãƒ‰ã‚¹ã‚¯ãƒªãƒ—ãƒˆã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/ansible-collections/community.okd/pull/20)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:321 -#: ../../rst/porting_guides/porting_guide_3.rst:353 -msgid "Add openshift connection plugin, update inventory plugin to use it (https://github.com/ansible-collections/community.okd/pull/18)." -msgstr "openshift æŽ¥ç¶šãƒ—ãƒ©ã‚°ã‚¤ãƒ³ã‚’è¿½åŠ ã—ã€ä½¿ç”¨ã™ã‚‹ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ—ラグインを更新ã—ã¾ã™ (https://github.com/ansible-collections/community.okd/pull/18)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:322 -#: ../../rst/porting_guides/porting_guide_3.rst:354 -msgid "Add openshift_process module for template rendering and optional application of rendered resources (https://github.com/ansible-collections/community.okd/pull/44)." -msgstr "テンプレートをレンダリングã—ã€ãƒ¬ãƒ³ãƒ€ãƒªãƒ³ã‚°ã•ã‚ŒãŸãƒªã‚½ãƒ¼ã‚¹ã®ä»»æ„ã®ã‚¢ãƒ—リケーション用㫠openshift_process ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/ansible-collections/community.okd/pull/44)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:323 -#: ../../rst/porting_guides/porting_guide_3.rst:355 -msgid "Add openshift_route module for creating routes from services (https://github.com/ansible-collections/community.okd/pull/40)." -msgstr "サービスã‹ã‚‰ãƒ«ãƒ¼ãƒˆã‚’作æˆã™ã‚‹ openshift_route ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/ansible-collections/community.okd/pull/40)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:324 -#: ../../rst/porting_guides/porting_guide_3.rst:356 -msgid "Initial content migration from community.kubernetes (https://github.com/ansible-collections/community.okd/pull/3)." -msgstr "community.kubernetes ã‹ã‚‰ã®æœ€åˆã®ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã®ç§»è¡Œ (https://github.com/ansible-collections/community.okd/pull/3)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:325 -#: ../../rst/porting_guides/porting_guide_3.rst:357 -msgid "openshift_auth - new module (migrated from k8s_auth in community.kubernetes) (https://github.com/ansible-collections/community.okd/pull/33)." -msgstr "openshift_auth - æ–°ã—ã„モジュール (community.kubernetes ã® k8s_auth ã‹ã‚‰ã®ç§»è¡Œ) (https://github.com/ansible-collections/community.okd/pull/33)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:328 -#: ../../rst/porting_guides/porting_guide_2.10.rst:406 -#: ../../rst/porting_guides/porting_guide_2.10.rst:786 -#: ../../rst/porting_guides/porting_guide_3.rst:145 -#: ../../rst/porting_guides/porting_guide_3.rst:438 -#: ../../rst/porting_guides/porting_guide_4.rst:355 -#: ../../rst/porting_guides/porting_guide_4.rst:583 -msgid "Removed Features" -msgstr "削除ã•ã‚ŒãŸæ©Ÿèƒ½" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:333 -#: ../../rst/porting_guides/porting_guide_3.rst:443 -msgid "docker_container - no longer returns ``ansible_facts`` (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_container - ``ansible_facts`` ãŒè¿”ã•ã‚Œãªããªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:334 -#: ../../rst/porting_guides/porting_guide_3.rst:444 -msgid "docker_container - the default of ``networks_cli_compatible`` changed to ``true`` (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_container - ``networks_cli_compatible`` ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãŒ ``true`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:335 -#: ../../rst/porting_guides/porting_guide_3.rst:445 -msgid "docker_container - the unused option ``trust_image_content`` has been removed (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_container - 未使用ã®ã‚ªãƒ—ション ``trust_image_content`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:336 -#: ../../rst/porting_guides/porting_guide_3.rst:446 -msgid "docker_image - ``state=build`` has been removed. Use ``present`` instead (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_image - ``state=build`` ã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``present`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:337 -#: ../../rst/porting_guides/porting_guide_3.rst:447 -msgid "docker_image - the ``container_limits``, ``dockerfile``, ``http_timeout``, ``nocache``, ``rm``, ``path``, ``buildargs``, ``pull`` have been removed. Use the corresponding suboptions of ``build`` instead (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_image - ``container_limits``ã€``dockerfile``ã€``http_timeout``ã€``nocache``ã€``rm``ã€``path``ã€``buildargs``ã€``pull`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ 代ã‚ã‚Šã« ``build`` ã®è©²å½“ã™ã‚‹ã‚µãƒ–オプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:338 -#: ../../rst/porting_guides/porting_guide_3.rst:448 -msgid "docker_image - the ``force`` option has been removed. Use the more specific ``force_*`` options instead (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_image - ``force`` オプションã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã«ã€ã‚ˆã‚Šå…·ä½“的㪠``force_*`` オプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:339 -#: ../../rst/porting_guides/porting_guide_3.rst:449 -msgid "docker_image - the ``source`` option is now mandatory (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_image - ``source`` オプションãŒå¿…é ˆã«ãªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:340 -#: ../../rst/porting_guides/porting_guide_3.rst:450 -msgid "docker_image - the ``use_tls`` option has been removed. Use ``tls`` and ``validate_certs`` instead (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_image - ``use_tls`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``tls`` ãŠã‚ˆã³ ``validate_certs`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:341 -#: ../../rst/porting_guides/porting_guide_3.rst:451 -msgid "docker_image - the default of the ``build.pull`` option changed to ``false`` (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_image - ``build.pull`` オプションã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãŒ ``false`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:342 -#: ../../rst/porting_guides/porting_guide_3.rst:452 -msgid "docker_image_facts - this alias is on longer availabe, use ``docker_image_info`` instead (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_image - ã“ã®ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã¯åˆ©ç”¨ã§ããªããªã‚Šã¾ã™ã€‚代ã‚ã‚Šã« ``docker_image_info`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:343 -#: ../../rst/porting_guides/porting_guide_3.rst:453 -msgid "docker_network - no longer returns ``ansible_facts`` (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_network - ``ansible_facts`` ãŒè¿”ã•ã‚Œãªããªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:344 -#: ../../rst/porting_guides/porting_guide_3.rst:454 -msgid "docker_network - the ``ipam_options`` option has been removed. Use ``ipam_config`` instead (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_network - ``ipam_options`` オプションã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``ipam_config`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:345 -#: ../../rst/porting_guides/porting_guide_3.rst:455 -msgid "docker_service - no longer returns ``ansible_facts`` (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_service - ``ansible_facts`` ãŒè¿”ã•ã‚Œãªããªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:346 -#: ../../rst/porting_guides/porting_guide_3.rst:456 -msgid "docker_swarm - ``state=inspect`` has been removed. Use ``docker_swarm_info`` instead (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_swarm - ``state=inspect`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``docker_swarm_info`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:347 -#: ../../rst/porting_guides/porting_guide_3.rst:457 -msgid "docker_swarm_service - the ``constraints`` option has been removed. Use ``placement.constraints`` instead (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_swarm_service - ``constraints`` オプションã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``placement.constraints`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:348 -#: ../../rst/porting_guides/porting_guide_3.rst:458 -msgid "docker_swarm_service - the ``limit_cpu`` and ``limit_memory`` options has been removed. Use the corresponding suboptions in ``limits`` instead (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_swarm_service - ``limit_cpu`` オプションãŠã‚ˆã³ ``limit_memory`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``limits`` ã§å¯¾å¿œã™ã‚‹ã‚µãƒ–オプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:349 -#: ../../rst/porting_guides/porting_guide_3.rst:459 -msgid "docker_swarm_service - the ``log_driver`` and ``log_driver_options`` options has been removed. Use the corresponding suboptions in ``logging`` instead (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_swarm_service - ``log_driver`` オプションãŠã‚ˆã³ ``log_driver_options`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``logging`` ã§å¯¾å¿œã™ã‚‹ã‚µãƒ–オプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:350 -#: ../../rst/porting_guides/porting_guide_3.rst:460 -msgid "docker_swarm_service - the ``reserve_cpu`` and ``reserve_memory`` options has been removed. Use the corresponding suboptions in ``reservations`` instead (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_swarm_service - ``reserve_cpu`` オプションãŠã‚ˆã³ ``reserve_memory`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``reservations`` ã§å¯¾å¿œã™ã‚‹ã‚µãƒ–オプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:351 -#: ../../rst/porting_guides/porting_guide_3.rst:461 -msgid "docker_swarm_service - the ``restart_policy``, ``restart_policy_attempts``, ``restart_policy_delay`` and ``restart_policy_window`` options has been removed. Use the corresponding suboptions in ``restart_config`` instead (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_swarm_service - ``restart_policy`` オプションã€``restart_policy_attempts`` オプションã€``restart_policy_delay`` オプションã€ãŠã‚ˆã³ ``restart_policy_window`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``restart_config`` ã§å¯¾å¿œã™ã‚‹ã‚µãƒ–オプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:352 -#: ../../rst/porting_guides/porting_guide_3.rst:462 -msgid "docker_swarm_service - the ``update_delay``, ``update_parallelism``, ``update_failure_action``, ``update_monitor``, ``update_max_failure_ratio`` and ``update_order`` options has been removed. Use the corresponding suboptions in ``update_config`` instead (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_swarm_service - ``update_delay`` オプションã€``update_parallelism`` オプションã€``update_failure_action`` オプションã€``update_monitor``ã€``update_max_failure_ratio`` オプションã€ãŠã‚ˆã³ ``update_order`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``update_config`` ã§å¯¾å¿œã™ã‚‹ã‚µãƒ–オプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:353 -#: ../../rst/porting_guides/porting_guide_3.rst:463 -msgid "docker_volume - no longer returns ``ansible_facts`` (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_volume - ``ansible_facts`` ãŒè¿”ã•ã‚Œãªããªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:354 -#: ../../rst/porting_guides/porting_guide_3.rst:464 -msgid "docker_volume - the ``force`` option has been removed. Use ``recreate`` instead (https://github.com/ansible-collections/community.docker/pull/1)." -msgstr "docker_volume - ``force`` オプションã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``recreate`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:362 -#: ../../rst/porting_guides/porting_guide_3.rst:612 -msgid "django_manage - the parameter ``liveserver`` relates to a no longer maintained third-party module for django. It is now deprecated, and will be remove in community.general 3.0.0 (https://github.com/ansible-collections/community.general/pull/1154)." -msgstr "django_manage - パラメーター ``liveserver`` ã¯ã€django ã®ç¶æŒã•ã‚Œã¦ã„るサードパーティーモジュールã«é–¢é€£ã—ãªããªã‚Šã¾ã—ãŸã€‚ç¾åœ¨ã¯éžæŽ¨å¥¨ã«ãªã‚Šã€community.general 3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/1154)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:363 -#: ../../rst/porting_guides/porting_guide_3.rst:613 -msgid "proxmox - the default of the new ``proxmox_default_behavior`` option will change from ``compatibility`` to ``no_defaults`` in community.general 4.0.0. Set the option to an explicit value to avoid a deprecation warning (https://github.com/ansible-collections/community.general/pull/850)." -msgstr "proxmox - æ–°ã—ã„ ``proxmox_default_behavior`` オプションã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãŒ community.general 4.0.0 㧠``compatibility`` ã‹ã‚‰ ``no_defaults`` ã«å¤‰æ›´ã—ã¾ã™ã€‚éžæŽ¨å¥¨ã®è¦å‘Šã‚’防ããŸã‚ã«ã€ã‚ªãƒ—ションを明示的ãªå€¤ã«è¨å®šã—ã¾ã™ (https://github.com/ansible-collections/community.general/pull/850))。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:364 -#: ../../rst/porting_guides/porting_guide_3.rst:614 -msgid "proxmox_kvm - the default of the new ``proxmox_default_behavior`` option will change from ``compatibility`` to ``no_defaults`` in community.general 4.0.0. Set the option to an explicit value to avoid a deprecation warning (https://github.com/ansible-collections/community.general/pull/850)." -msgstr "proxmox_kvm - æ–°ã—ã„ ``proxmox_default_behavior`` オプションã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãŒ community.general 4.0.0 㧠``compatibility`` ã‹ã‚‰ ``no_defaults`` ã«å¤‰æ›´ã•ã‚Œã¾ã™ã€‚éžæŽ¨å¥¨ã®è¦å‘Šã‚’防ããŸã‚ã«ã€ã‚ªãƒ—ションを明示的ãªå€¤ã«è¨å®šã—ã¾ã™ (https://github.com/ansible-collections/community.general/pull/850)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:365 -#: ../../rst/porting_guides/porting_guide_3.rst:615 -msgid "syspatch - deprecate the redundant ``apply`` argument (https://github.com/ansible-collections/community.general/pull/360)." -msgstr "syspatch - 冗長㪠``apply`` 引数をéžæŽ¨å¥¨ã«ã—ã¾ã™ (https://github.com/ansible-collections/community.general/pull/360)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:370 -#: ../../rst/porting_guides/porting_guide_3.rst:631 -msgid "Deprecate connection=local support for network platforms using persistent framework (https://github.com/ansible-collections/community.network/pull/120)." -msgstr "永続的ãªãƒ•ãƒ¬ãƒ¼ãƒ ワークを使用ã—ãŸãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ—ラットフォーム㮠connection=local サãƒãƒ¼ãƒˆã‚’éžæŽ¨å¥¨ã«ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.network/pull/120)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:373 -msgid "Porting Guide for v2.10.2" -msgstr "v2.10.2 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:379 -#: ../../rst/porting_guides/porting_guide_2.10.rst:616 -#: ../../rst/porting_guides/porting_guide_2.10.rst:789 -#: ../../rst/porting_guides/porting_guide_2.10.rst:856 -#: ../../rst/porting_guides/porting_guide_3.rst:37 -#: ../../rst/porting_guides/porting_guide_3.rst:208 -msgid "Ansible-base" -msgstr "Ansible-base" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:381 -#: ../../rst/porting_guides/porting_guide_3.rst:210 -#: ../../rst/porting_guides/porting_guide_4.rst:435 -msgid "ansible-galaxy login command has been removed (see https://github.com/ansible/ansible/issues/71560)" -msgstr "ansible-galaxy login コマンドãŒå‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible/ansible/issues/71560) ã‚’å‚ç…§)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:389 -#: ../../rst/porting_guides/porting_guide_3.rst:375 -msgid "Add phone home Teem integration into all modules, functionality can be disabled by setting up F5_TEEM environment variable or no_f5_teem provider parameter" -msgstr "ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã« phone home Teem çµ±åˆã‚’è¿½åŠ ã—ã¾ã™ã€‚F5_TEEM 環境変数ã¾ãŸã¯ no_f5_teem プãƒãƒã‚¤ãƒ€ãƒ¼ãƒ‘ラメーターをè¨å®šã—ã¦æ©Ÿèƒ½ã‚’無効ã«ã§ãã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:394 -#: ../../rst/porting_guides/porting_guide_3.rst:417 -msgid "cluster_upgrade - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/94)." -msgstr "cluster_upgrade - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/94)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:395 -#: ../../rst/porting_guides/porting_guide_3.rst:418 -msgid "disaster_recovery - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/134)." -msgstr "disaster_recovery - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/134)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:396 -#: ../../rst/porting_guides/porting_guide_3.rst:419 -msgid "engine_setup - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/69)." -msgstr "engine_setup - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/69)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:397 -#: ../../rst/porting_guides/porting_guide_3.rst:420 -msgid "hosted_engine_setup - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/106)." -msgstr "hosted_engine_setup - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/106)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:398 -#: ../../rst/porting_guides/porting_guide_3.rst:421 -msgid "image_template - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/95)." -msgstr "image_template - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/95)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:399 -#: ../../rst/porting_guides/porting_guide_3.rst:422 -msgid "infra - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/92)." -msgstr "infra - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/92)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:400 -#: ../../rst/porting_guides/porting_guide_3.rst:423 -msgid "manageiq - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/97)." -msgstr "manageiq - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/97)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:401 -#: ../../rst/porting_guides/porting_guide_3.rst:425 -msgid "repositories - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/96)." -msgstr "repositories - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/96)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:402 -#: ../../rst/porting_guides/porting_guide_3.rst:426 -msgid "shutdown_env - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/112)." -msgstr "shutdown_env - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/112)" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:403 -#: ../../rst/porting_guides/porting_guide_3.rst:427 -msgid "vm_infra - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/93)." -msgstr "vm_infra - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/93)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:411 -#: ../../rst/porting_guides/porting_guide_3.rst:584 -msgid "Removed arp_state parameter from the bigip_virtual_address module" -msgstr "bigip_virtual_address モジュールã‹ã‚‰ arp_state パラメーターを削除ã—ã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:419 -#: ../../rst/porting_guides/porting_guide_3.rst:593 -msgid "Deprecated `nxos_interface_ospf` in favor of `nxos_ospf_interfaces` Resource Module." -msgstr "`nxos_interface_ospf` ã‚’éžæŽ¨å¥¨ã«ã—ã€`nxos_ospf_interfaces` Resource Module ãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:422 -msgid "Porting Guide for v2.10.1" -msgstr "v2.10.1 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:428 -#: ../../rst/porting_guides/porting_guide_2.10.rst:664 -#: ../../rst/porting_guides/porting_guide_3.rst:343 -msgid "community.kubernetes" -msgstr "community.kubernetes" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:430 -#: ../../rst/porting_guides/porting_guide_3.rst:345 -msgid "k8s - Add support for template parameter (https://github.com/ansible-collections/community.kubernetes/pull/230)." -msgstr "k8s - テンプレートパラメーターã®ã‚µãƒãƒ¼ãƒˆã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/ansible-collections/community.kubernetes/pull/230)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:431 -#: ../../rst/porting_guides/porting_guide_3.rst:346 -msgid "k8s_* - Add support for vaulted kubeconfig and src (https://github.com/ansible-collections/community.kubernetes/pull/193)." -msgstr "k8s_* - Vault 済㿠kubeconfig ãŠã‚ˆã³ src ã®ã‚µãƒãƒ¼ãƒˆã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/ansible-collections/community.kubernetes/pull/193)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:439 -#: ../../rst/porting_guides/porting_guide_3.rst:594 -msgid "Deprecated `nxos_smu` in favor of `nxos_rpm` module." -msgstr "`nxos_smu` ã‚’éžæŽ¨å¥¨ã«ã—ã€`nxos_rpm` モジュールãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:440 -#: ../../rst/porting_guides/porting_guide_3.rst:595 -msgid "The `nxos_ospf_vrf` module is deprecated by `nxos_ospfv2` and `nxos_ospfv3` Resource Modules." -msgstr "`nxos_ospf_vrf` モジュールã¯ã€`nxos_ospfv2` ãŠã‚ˆã³ `nxos_ospfv3` Resource Module ã«ã‚ˆã£ã¦éžæŽ¨å¥¨ã¨ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:443 -msgid "Porting Guide for v2.10.0" -msgstr "v2.10.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:446 -#: ../../rst/porting_guides/porting_guide_3.rst:23 -#: ../../rst/porting_guides/porting_guide_3.rst:92 -#: ../../rst/porting_guides/porting_guide_3.rst:122 -#: ../../rst/porting_guides/porting_guide_3.rst:195 -#: ../../rst/porting_guides/porting_guide_4.rst:199 -#: ../../rst/porting_guides/porting_guide_4.rst:257 -#: ../../rst/porting_guides/porting_guide_4.rst:313 -#: ../../rst/porting_guides/porting_guide_4.rst:405 -msgid "Known Issues" -msgstr "既知ã®å•é¡Œ" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:448 -msgid "Due to a limitation in pip, you cannot ``pip install --upgrade`` from ansible-2.9 or earlier to ansible-2.10 or higher. Instead, you must explicitly use ``pip uninstall ansible`` before pip installing the new version. If you attempt to upgrade Ansible with pip without first uninstalling, the installer warns you to uninstall first." -msgstr "pip ã®åˆ¶é™ã«ã‚ˆã‚Šã€ansible-2.9 以å‰ã‹ã‚‰ ansible-2.10 以é™ã«ã¯ ``pip install --upgrade`` ã‚’è¡Œã†ã“ã¨ãŒã§ãã¾ã›ã‚“。代ã‚ã‚Šã«ã€pip ã§æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’インストールã™ã‚‹å‰ã« ``pip uninstall ansible`` を明示的ã«ä½¿ç”¨ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚最åˆã«ã‚¢ãƒ³ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã›ãšã« pip 㧠Ansible をアップグレードã™ã‚‹å ´åˆã¯ã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ©ãƒ¼ãŒæœ€åˆã«ã‚¢ãƒ³ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã‚’è¦å‘Šã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:449 -#, python-format -msgid "The individual collections that make up the ansible-2.10.0 package can be viewed independently. However, they are not currently listed by ansible-galaxy. To view these collections with ansible-galaxy, explicitly specify where ansible has installed the collections -- ``COLLECTION_INSTALL=$(python -c 'import ansible, os.path ; print(\"%s/../ansible_collections\" % os.path.dirname(ansible.__file__))') ansible-galaxy collection list -p \"$COLLECTION_INSTALL\"``." -msgstr "ansible-2.10.0 パッケージを構æˆã™ã‚‹å€‹ã€…ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã¯å€‹åˆ¥ã«è¡¨ç¤ºã§ãã¾ã™ãŒã€ç¾åœ¨ ansible-galaxy ã«ã‚ˆã‚Šä¸€è¦§è¡¨ç¤ºã•ã‚Œã¦ã„ã¾ã›ã‚“。ansible-galaxy ã§ã“れらã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’表示ã™ã‚‹ã«ã¯ã€ansible ãŒã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´æ‰€ã‚’明示的ã«æŒ‡å®šã—ã¾ã™ã€‚``COLLECTION_INSTALL=$(python -c 'import ansible, os.path ; print(\"%s/../ansible_collections\" % os.path.dirname(ansible.__file__))') ansible-galaxy collection list -p \"$COLLECTION_INSTALL\"``" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:450 -msgid "These fortios modules are not automatically redirected from their 2.9.x names to the new 2.10.x names within collections. You must modify your playbooks to use fully qualified collection names for them. You can use the documentation (https://docs.ansible.com/ansible/2.10/collections/fortinet/fortios/) for the ``fortinet.fortios`` collection to determine what the fully qualified collection names are." -msgstr "ã“れら㮠fortios モジュールã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³å†…㧠2.9.x ã®åå‰ã‹ã‚‰æ–°ã—ã„ 2.10.x ã®åå‰ã«è‡ªå‹•çš„ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã•ã‚Œã¾ã›ã‚“。ã“れらã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«å®Œå…¨ä¿®é£¾ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³åを使用ã™ã‚‹ã‚ˆã†ã« Playbook を変更ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚完全修飾コレクションåã«ã¤ã„ã¦ã¯ã€``fortinet.fortios`` コレクションã®ãƒ‰ã‚ュメント (https://docs.ansible.com/ansible/2.10/collections/fortinet/fortios/)) ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:452 -msgid "fortios_address" -msgstr "fortios_address" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:453 -msgid "fortios_config" -msgstr "fortios_config" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:454 -msgid "fortios_firewall_DoS_policy" -msgstr "fortios_firewall_DoS_policy" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:455 -msgid "fortios_firewall_DoS_policy6" -msgstr "fortios_firewall_DoS_policy6" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:456 -msgid "fortios_ipv4_policy" -msgstr "fortios_ipv4_policy" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:457 -msgid "fortios_switch_controller_802_1X_settings" -msgstr "fortios_switch_controller_802_1X_settings" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:458 -msgid "fortios_switch_controller_security_policy_802_1X" -msgstr "fortios_switch_controller_security_policy_802_1X" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:459 -msgid "fortios_system_firmware_upgrade" -msgstr "fortios_system_firmware_upgrade" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:460 -msgid "fortios_system_nd_proxy" -msgstr "fortios_system_nd_proxy" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:461 -msgid "fortios_webfilter" -msgstr "fortios_webfilter" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:464 -#: ../../rst/porting_guides/porting_guide_2.10.rst:658 -#: ../../rst/porting_guides/porting_guide_3.rst:134 -#: ../../rst/porting_guides/porting_guide_4.rst:156 -#: ../../rst/porting_guides/porting_guide_4.rst:533 -msgid "community.grafana" -msgstr "community.grafana" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:466 -msgid "grafana_datasource doesn't set password correctly (#113)" -msgstr "grafana_datasource ã§ãƒ‘スワードãŒæ£ã—ãè¨å®šã•ã‚Œãªã„ (#113)" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:471 -msgid "cisco.nxos.nxos_igmp_interface - no longer supports the deprecated ``oif_prefix`` and ``oif_source`` options. These have been superceeded by ``oif_ps``." -msgstr "cisco.nxos.nxos_igmp_interface - éžæŽ¨å¥¨ã® ``oif_prefix`` オプションãŠã‚ˆã³ ``oif_source`` オプションをサãƒãƒ¼ãƒˆã—ãªããªã‚Šã¾ã—ãŸã€‚ã“れら㯠``oif_ps`` ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:472 -msgid "community.grafana.grafana_dashboard - the parameter ``message`` is renamed to ``commit_message`` since ``message`` is used by Ansible Core engine internally." -msgstr "community.grafana.grafana_dashboard - ``message`` ã¯å†…部的㫠Ansible Core Engine ã§ä½¿ç”¨ã•ã‚Œã‚‹ãŸã‚ã€ãƒ‘ラメーター ``message`` ã®åå‰ãŒ ``commit_message`` ã«å¤‰æ›´ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:473 -msgid "purestorage.flashblade.purefb_fs - no longer supports the deprecated ``nfs`` option. This has been superceeded by ``nfsv3``." -msgstr "purestorage.flashblade.purefb_fs - éžæŽ¨å¥¨ã® ``nfs`` オプションã«å¯¾å¿œã—ãªããªã‚Šã¾ã—ãŸã€‚ã“れ㯠``nfsv3`` ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:476 -#: ../../rst/porting_guides/porting_guide_2.10.rst:627 -#: ../../rst/porting_guides/porting_guide_2.10.rst:863 -msgid "amazon.aws" -msgstr "amazon.aws" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:478 -msgid "aws_s3 - can now delete versioned buckets even when they are not empty - set mode to delete to delete a versioned bucket and everything in it." -msgstr "aws_s3 - ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚¢ãƒƒãƒ—ã•ã‚ŒãŸãƒã‚±ãƒƒãƒˆãŒç©ºã§ãªãã¦ã‚‚削除ã§ãるよã†ã«ãªã‚Šã¾ã—ãŸã€‚モードを delete ã«è¨å®šã™ã‚‹ã¨ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚¢ãƒƒãƒ—ã•ã‚ŒãŸãƒã‚±ãƒƒãƒˆã¨ãã®ä¸ã®ã‚‚ã®ãŒã™ã¹ã¦å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:481 -#: ../../rst/porting_guides/porting_guide_2.10.rst:799 -#: ../../rst/porting_guides/porting_guide_2.10.rst:882 -#: ../../rst/porting_guides/porting_guide_4.rst:292 -#: ../../rst/porting_guides/porting_guide_4.rst:358 -#: ../../rst/porting_guides/porting_guide_4.rst:366 -msgid "ansible.windows" -msgstr "ansible.windows" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:483 -msgid "setup - Make sure ``ansible_date_time.epoch`` is seconds since EPOCH in UTC to mirror the POSIX facts. The ``ansible_date_time.epoch_local`` contains seconds since EPOCH in the local timezone for backwards compatibility" -msgstr "setup - POSIX ファクトをåæ˜ ã•ã›ã‚‹ãŸã‚ã«ã€``ansible_date_time.epoch`` ㌠UTC ã® EPOCH 以é™ã®ç§’æ•°ã§ã‚ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚後方互æ›ã®ãŸã‚ã«ã€``ansible_date_time.epoch_local`` ã«ã¯ã€ãƒãƒ¼ã‚«ãƒ«ã‚¿ã‚¤ãƒ ゾーン㮠EPOCH 以é™ã®ç§’æ•°ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:484 -msgid "setup - Will now add the IPv6 scope on link local addresses for ``ansible_ip_addresses``" -msgstr "setup - ``ansible_ip_addresses`` ã®ãƒªãƒ³ã‚¯ãƒãƒ¼ã‚«ãƒ«ã‚¢ãƒ‰ãƒ¬ã‚¹ã« IPv6 ã‚¹ã‚³ãƒ¼ãƒ—ã‚’è¿½åŠ ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:485 -msgid "setup - ``ansible_processor`` will now return the index before the other values to match the POSIX fact behaviour" -msgstr "setup - ``ansible_processor`` ãŒã€POSIX ファクトã®å‹•ä½œã«ä¸€è‡´ã™ã‚‹ãŸã‚ã«ä»–ã®å€¤ã®å‰ã«ã‚¤ãƒ³ãƒ‡ãƒƒã‚¯ã‚¹ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:486 -msgid "win_find - No longer filters by size on directories, this feature had a lot of bugs, slowed down the module, and not a supported scenario with the ``find`` module." -msgstr "win_find - ディレクトリーã«ãŠã„ã¦ã‚µã‚¤ã‚ºã§ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ãŒè¨å®šã•ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã€ã“ã®æ©Ÿèƒ½ã¯ãƒã‚°ãŒå¤šããªã‚Šã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®é€Ÿåº¦ãŒä½Žä¸‹ã—ã€``find`` モジュールã§ã®å¯¾å¿œã‚·ãƒŠãƒªã‚ªã¯ã‚ã‚Šã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:489 -msgid "win_find - module has been refactored to better match the behaviour of the ``find`` module. Here is what has changed:" -msgstr "win_find - モジュールã¯ã€``find`` モジュールã®å‹•ä½œã«åˆã‚ã›ã¦ãƒªãƒ•ã‚¡ã‚¯ã‚¿ãƒªãƒ³ã‚°ã•ã‚Œã¾ã—ãŸã€‚ã“ã‚ŒãŒå¤‰æ›´ã«ãªã‚Šã¾ã—ãŸ:" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:488 -msgid "When the directory specified by ``paths`` does not exist or is a file, it will no longer fail and will just warn the user" -msgstr "``paths`` ã§æŒ‡å®šã•ã‚ŒãŸãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ãŒå˜åœ¨ã—ãªã„ã‹ã€ãƒ•ã‚¡ã‚¤ãƒ«ã§ã‚ã‚‹ã¨ã€å¤±æ•—ã—ãªããªã‚Šã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«è¦å‘ŠãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:489 -msgid "Junction points are no longer reported as ``islnk``, use ``isjunction`` to properly report these files. This behaviour matches the win_stat module" -msgstr "ジャンクションãƒã‚¤ãƒ³ãƒˆã¯ ``islnk`` ã¨ã—ã¦å ±å‘Šã•ã‚Œãªããªã‚Šã¾ã—ãŸã€‚ã“れらã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’æ£ã—ãå ±å‘Šã™ã‚‹ã«ã¯ ``isjunction`` を使用ã—ã¦ãã ã•ã„。ã“ã®å‹•ä½œã¯ win_stat モジュールã¨ä¸€è‡´ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:490 -msgid "Directories no longer return a ``size``, this matches the ``stat`` and ``find`` behaviour and has been removed due to the difficulties in correctly reporting the size of a directory" -msgstr "ディレクトリー㌠``size`` ã‚’è¿”ã•ãªããªã‚Šã¾ã—ãŸã€‚ã“れ㯠``stat`` ãŠã‚ˆã³ ``find`` ã®å‹•ä½œã¨ä¸€è‡´ã—ã€ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã®ã‚µã‚¤ã‚ºã‚’æ£ã—ãå ±å‘Šã™ã‚‹ã“ã¨ãŒå›°é›£ã§ã‚ã‚‹ãŸã‚ã€å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:491 -msgid "win_user - Change idempotency checks for ``description`` to be case sensitive" -msgstr "win_user - 大文å—ã¨å°æ–‡å—を区別ã™ã‚‹ãŸã‚ã« ``description`` ã®å†ªç‰æ€§ãƒã‚§ãƒƒã‚¯ã‚’変更ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:492 -msgid "win_user - Change idempotency checks for ``fullname`` to be case sensitive" -msgstr "win_user - 大文å—ã¨å°æ–‡å—を区別ã™ã‚‹ãŸã‚ã« ``fullname`` ã®å†ªç‰æ€§ãƒã‚§ãƒƒã‚¯ã‚’変更ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:495 -#: ../../rst/porting_guides/porting_guide_2.10.rst:642 -msgid "cisco.meraki" -msgstr "cisco.meraki" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:497 -msgid "meraki_device - Changed tags from string to list" -msgstr "meraki_device - æ–‡å—列ã‹ã‚‰ãƒªã‚¹ãƒˆã«ã‚¿ã‚°ã‚’変更ã—ã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:498 -msgid "meraki_device - Removed serial_lldp_cdp parameter" -msgstr "meraki_device - serial_lldp_cdp パラメーターを削除ã—ã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:499 -msgid "meraki_device - Removed serial_uplink parameter" -msgstr "meraki_device - serial_uplink パラメーターを削除ã—ã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:500 -msgid "meraki_intrusion_prevention - Rename whitedlisted_rules to allowed_rules" -msgstr "meraki_intrusion_prevention - whitedlisted_rules ã®åå‰ã‚’ allowed_rules ã«å¤‰æ›´ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:501 -msgid "meraki_mx_l3_firewall - Rule responses are now in a `rules` list" -msgstr "meraki_mx_l3_firewall - ルール応ç”㌠`rules` リストã«è¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:502 -msgid "meraki_mx_l7_firewall - Rename blacklisted_countries to blocked_countries" -msgstr "meraki_mx_l7_firewall - blocked_countries ã®åå‰ã‚’ blacklisted_countries ã«å¤‰æ›´ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:503 -msgid "meraki_mx_l7_firewall - Rename whitelisted_countries to allowed_countries" -msgstr "meraki_mx_l7_firewall - whitelisted_countries ã®åå‰ã‚’ allowed_countries ã«å¤‰æ›´ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:504 -msgid "meraki_network - Local and remote status page settings cannot be set during network creation" -msgstr "meraki_network - ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã®ä½œæˆæ™‚ã«ãƒãƒ¼ã‚«ãƒ«ãŠã‚ˆã³ãƒªãƒ¢ãƒ¼ãƒˆã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ãƒšãƒ¼ã‚¸è¨å®šã‚’è¨å®šã§ãã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:505 -msgid "meraki_network - `disableRemoteStatusPage` response is now `remote_status_page_enabled`" -msgstr "meraki_network - `disableRemoteStatusPage` ã®å¿œç”㌠`remote_status_page_enabled` ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:506 -msgid "meraki_network - `disable_my_meraki_com` response is now `local_status_page_enabled`" -msgstr "meraki_network - `disable_my_meraki_com` ã®å¿œç”㌠`local_status_page_enabled` ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:507 -msgid "meraki_network - `disable_my_meraki` has been deprecated" -msgstr "meraki_network - `disable_my_meraki` ãŒéžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:508 -msgid "meraki_network - `enable_my_meraki` is now called `local_status_page_enabled`" -msgstr "meraki_network - `enable_my_meraki` ㌠`local_status_page_enabled` ã¨å‘¼ã°ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:509 -msgid "meraki_network - `enable_remote_status_page` is now called `remote_status_page_enabled`" -msgstr "meraki_network - `enable_remote_status_page` ㌠`remote_status_page_enabled` ã¨å‘¼ã°ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:510 -msgid "meraki_network - `enabled` response for VLAN status is now `vlans_enabled`" -msgstr "meraki_network - VLAN ステータスã«å¯¾ã™ã‚‹ `enabled` å¿œç”㌠`vlans_enabled` ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:511 -msgid "meraki_network - `tags` and `type` now return a list" -msgstr "meraki_network - `tags` ãŠã‚ˆã³ `type` ãŒä¸€è¦§ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:512 -msgid "meraki_snmp - peer_ips is now a list" -msgstr "meraki_snmp - peer_ips ãŒãƒªã‚¹ãƒˆã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:513 -msgid "meraki_switchport - `access_policy_number` is now an int and not a string" -msgstr "meraki_switchport - `access_policy_number` ã¯æ–‡å—列型ã§ã¯ãªã int åž‹ã«ãªã‚Šã¾ã—ãŸ" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:514 -msgid "meraki_switchport - `tags` is now a list and not a string" -msgstr "meraki_switchport - `tags` ãŒæ–‡å—列型ã§ã¯ãªãリスト型ã«ãªã‚Šã¾ã—ãŸ" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:515 -msgid "meraki_webhook - Querying test status now uses state of query." -msgstr "meraki_webhook - テストステータスã®ã‚¯ã‚¨ãƒªãƒ¼ã¯ã‚¯ã‚¨ãƒªãƒ¼çŠ¶æ…‹ã‚’使用ã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:520 -msgid "The environment variable for the auth context for the oc.py connection plugin has been corrected (K8S_CONTEXT). It was using an initial lowercase k by mistake. (https://github.com/ansible-collections/community.general/pull/377)." -msgstr "oc.py 接続プラグインã®èªè¨¼ã‚³ãƒ³ãƒ†ã‚ストã®ç’°å¢ƒå¤‰æ•° (K8S_CONTEXT) ãŒä¿®æ£ã•ã‚Œã¾ã—ãŸã€‚ã“ã‚Œã¯ã€æœ€åˆã®å°æ–‡å—ã® k ã‚’é–“é•ã£ã¦ä½¿ç”¨ã—ã¦ã„ã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/377)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:521 -msgid "bigpanda - the parameter ``message`` was renamed to ``deployment_message`` since ``message`` is used by Ansible Core engine internally." -msgstr "bigpanda - ``message`` 㯠Ansible Core Engine ã§å†…部的ã«ä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹ãŸã‚ã€ãƒ‘ラメーター ``message`` 㯠``deployment_message`` ã«å¤‰æ›´ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:522 -msgid "cisco_spark - the module option ``message`` was renamed to ``msg``, as ``message`` is used internally in Ansible Core engine (https://github.com/ansible/ansible/issues/39295)" -msgstr "cisco_spark - Ansible Core エンジン㧠``message`` ãŒå†…部ã§ä½¿ç”¨ã•ã‚Œã‚‹ãŸã‚ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚ªãƒ—ション ``message`` ã®åå‰ãŒ ``msg`` ã«å¤‰æ›´ã•ã‚Œã¾ã—㟠(https://github.com/ansible/ansible/issues/39295)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:523 -msgid "datadog - the parameter ``message`` was renamed to ``notification_message`` since ``message`` is used by Ansible Core engine internally." -msgstr "datadog - ``message`` 㯠Ansible Core Engine ã§å†…部的ã«ä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹ãŸã‚ã€ãƒ‘ラメーターã®åå‰ ``message`` 㯠``notification_message`` ã«å¤‰æ›´ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:524 -msgid "docker_container - no longer passes information on non-anonymous volumes or binds as ``Volumes`` to the Docker daemon. This increases compatibility with the ``docker`` CLI program. Note that if you specify ``volumes: strict`` in ``comparisons``, this could cause existing containers created with docker_container from Ansible 2.9 or earlier to restart." -msgstr "docker_container - 匿åã§ãªã„ボリュームã®æƒ…å ±ã‚„ ``Volumes`` ã¨ã—ã¦ã®ãƒã‚¤ãƒ³ãƒ‰ã‚’ Docker デーモンã«æ¸¡ã•ãªããªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã«ã‚ˆã‚Šã€``docker`` CLI プãƒã‚°ãƒ©ãƒ ã¨ã®äº’æ›æ€§ãŒé«˜ã¾ã‚Šã¾ã—ãŸã€‚ãªãŠã€``comparisons`` ã«``volumes: strict`` を指定ã™ã‚‹ã¨ã€Ansible 2.9 以å‰ã® docker_container ã§ä½œæˆã•ã‚ŒãŸæ—¢å˜ã®ã‚³ãƒ³ãƒ†ãƒŠãƒ¼ãŒå†èµ·å‹•ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:525 -msgid "docker_container - support for port ranges was adjusted to be more compatible to the ``docker`` command line utility: a one-port container range combined with a multiple-port host range will no longer result in only the first host port be used, but the whole range being passed to Docker so that a free port in that range will be used." -msgstr "docker_container - ãƒãƒ¼ãƒˆç¯„囲ã®ã‚µãƒãƒ¼ãƒˆã¯ã€``docker`` コマンドラインユーティリティーã¨ã®äº’æ›æ€§ã‚’高ã‚ã‚‹ãŸã‚ã«èª¿æ•´ã•ã‚Œã¾ã—ãŸã€‚1 ãƒãƒ¼ãƒˆã®ã‚³ãƒ³ãƒ†ãƒŠãƒ¼ç¯„囲ã¨è¤‡æ•°ãƒãƒ¼ãƒˆã®ãƒ›ã‚¹ãƒˆç¯„囲を組ã¿åˆã‚ã›ãŸå ´åˆã¯ã€æœ€åˆã®ãƒ›ã‚¹ãƒˆãƒãƒ¼ãƒˆã®ã¿ãŒä½¿ç”¨ã•ã‚Œã‚‹ã“ã¨ã¯ãªããªã‚Šã€ç¯„囲全体㌠Docker ã«æ¸¡ã•ã‚Œã€ãã®ç¯„囲内ã®ç©ºããƒãƒ¼ãƒˆãŒä½¿ç”¨ã•ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:526 -msgid "hashi_vault lookup - now returns the latest version when using the KV v2 secrets engine. Previously, it returned all versions of the secret which required additional steps to extract and filter the desired version." -msgstr "hashi_vault lookup - KV v2 シークレットエンジンを使用ã™ã‚‹éš›ã«ã€æœ€æ–°ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã¾ã§ã¯ã€ã™ã¹ã¦ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ã‚·ãƒ¼ã‚¯ãƒ¬ãƒƒãƒˆãŒè¿”ã•ã‚Œã¦ã„ãŸãŸã‚ã€ç›®çš„ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’抽出ã—ã¦ãƒ•ã‚£ãƒ«ã‚¿ãƒªãƒ³ã‚°ã™ã‚‹ãŸã‚ã®è¿½åŠ æ‰‹é †ãŒå¿…è¦ã§ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:527 -#: ../../rst/porting_guides/porting_guide_3.rst:264 -msgid "log_plays callback - add missing information to the logs generated by the callback plugin. This changes the log message format (https://github.com/ansible-collections/community.general/pull/442)." -msgstr "log_plays callback - callback プラグインã§ç”Ÿæˆã•ã‚ŒãŸãƒã‚°ã«ä¸è¶³ã—ã¦ã„ã‚‹æƒ…å ±ã‚’è¿½åŠ ã—ã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ãƒã‚°ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã®å½¢å¼ãŒå¤‰æ›´ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/442)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:528 -#: ../../rst/porting_guides/porting_guide_3.rst:266 -msgid "pkgng - passing ``name: *`` with ``state: absent`` will no longer remove every installed package from the system. It is now a noop. (https://github.com/ansible-collections/community.general/pull/569)." -msgstr "pkgng - ``name: *`` ã« ``state: absent`` を渡ã™ã¨ã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«æ¸ˆã¿ãƒ‘ッケージãŒã™ã¹ã¦ã‚·ã‚¹ãƒ†ãƒ ã‹ã‚‰å‰Šé™¤ã•ã‚Œãªããªã‚Šã€noop ã«ãªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/569)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:529 -#: ../../rst/porting_guides/porting_guide_3.rst:267 -msgid "pkgng - passing ``name: *`` with ``state: latest`` or ``state: present`` will no longer install every package from the configured package repositories. Instead, ``name: *, state: latest`` will upgrade all already-installed packages, and ``name: *, state: present`` is a noop. (https://github.com/ansible-collections/community.general/pull/569)." -msgstr "pkgng - ``name: *`` ã« ``state: latest`` ã¾ãŸã¯``state: present`` を渡ã™ã¨ã€è¨å®šã•ã‚ŒãŸãƒ‘ッケージリãƒã‚¸ãƒˆãƒªãƒ¼ã‹ã‚‰ã™ã¹ã¦ã®ãƒ‘ッケージをインストールã—ãªããªã‚Šã¾ã™ã€‚代ã‚ã‚Šã«ã€``name: *, state: latest`` ã¯æ—¢ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„るパッケージをã™ã¹ã¦ã‚¢ãƒƒãƒ—グレードã—ã€``name: *, state: present`` 㯠noop ã§ã™ (https://github.com/ansible-collections/community.general/pull/569)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:534 -msgid "routeros_facts - allow multiple addresses and neighbors per interface. This makes ``ansible_net_neighbors`` a list instead of a dict (https://github.com/ansible-collections/community.network/pull/6)." -msgstr "routeros_facts - インターフェースã”ã¨ã«è¤‡æ•°ã®ã‚¢ãƒ‰ãƒ¬ã‚¹ã¨è¿‘接アドレスを許å¯ã—ã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€``ansible_net_neighbors`` ㌠dict ã§ã¯ãªã list ã«ãªã‚Šã¾ã™ (https://github.com/ansible-collections/community.network/pull/6)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:539 -msgid "vmware_datastore_maintenancemode - now returns ``datastore_status`` instead of Ansible internal key ``results``." -msgstr "vmware_datastore_maintenancemode - Ansible 内部ã‚ー ``results`` ã®ä»£ã‚ã‚Šã« ``datastore_status`` ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:540 -msgid "vmware_guest_custom_attributes - does not require VM name which was a required parameter for releases prior to Ansible 2.10." -msgstr "vmware_guest_custom_attributes - Ansible 2.10 よりå‰ã®ãƒªãƒªãƒ¼ã‚¹ã§å¿…é ˆã ã£ãŸãƒ‘ラメーターã§ã‚る仮想マシンåã¯å¿…è¦ã‚ã‚Šã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:541 -msgid "vmware_guest_find - the ``datacenter`` option has been removed." -msgstr "vmware_guest_find - ``datacenter`` オプションã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:542 -msgid "vmware_host_kernel_manager - now returns ``host_kernel_status`` instead of Ansible internal key ``results``." -msgstr "vmware_host_kernel_manager - Ansible 内部ã‚ー ``results`` ã®ä»£ã‚ã‚Šã« ``host_kernel_status`` ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:543 -msgid "vmware_host_ntp - now returns ``host_ntp_status`` instead of Ansible internal key ``results``." -msgstr "vmware_host_ntp - Ansible 内部ã‚ー ``results`` ã®ä»£ã‚ã‚Šã« ``host_ntp_status`` ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:544 -msgid "vmware_host_service_manager - now returns ``host_service_status`` instead of Ansible internal key ``results``." -msgstr "vmware_host_service_manager - Ansible 内部ã‚ー ``results`` ã®ä»£ã‚ã‚Šã« ``host_service_status`` ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:545 -msgid "vmware_tag - now returns ``tag_status`` instead of Ansible internal key ``results``." -msgstr "vmware_tag - Ansible 内部ã‚ー ``results`` ã®ä»£ã‚ã‚Šã« ``tag_status`` ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:546 -msgid "vmware_vmkernel - the options ``ip_address`` and ``subnet_mask`` have been removed; use the suboptions ``ip_address`` and ``subnet_mask`` of the ``network`` option instead." -msgstr "vmware_vmkernel - ``ip_address`` オプションãŠã‚ˆã³ ``subnet_mask`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``network`` オプションã®ã‚µãƒ–オプション ``ip_address`` ãŠã‚ˆã³ ``subnet_mask`` を使用ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:549 -#: ../../rst/porting_guides/porting_guide_2.10.rst:835 -msgid "community.windows" -msgstr "community.windows" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:551 -msgid "win_pester - no longer runs all ``*.ps1`` file in the directory specified due to it executing potentially unknown scripts. It will follow the default behaviour of only running tests for files that are like ``*.tests.ps1`` which is built into Pester itself." -msgstr "win_pester - 未知ã®ã‚¹ã‚¯ãƒªãƒ—トを実行ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚‹ãŸã‚ã€æŒ‡å®šã—ãŸãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼å†…ã®ã™ã¹ã¦ã® ``*.ps1`` ファイルを実行ã—ãªããªã‚Šã¾ã—ãŸã€‚Pester 自体ã«çµ„ã¿è¾¼ã¾ã‚Œã¦ã„ã‚‹ ``*.tests.ps1`` ã®ã‚ˆã†ãªãƒ•ã‚¡ã‚¤ãƒ«ã«å¯¾ã—ã¦ã®ã¿ãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã¨ã„ã†ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã®å‹•ä½œã«å¾“ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:554 -#: ../../rst/porting_guides/porting_guide_2.10.rst:953 -msgid "community.zabbix" -msgstr "community.zabbix" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:556 -msgid "zabbix_javagateway - options ``javagateway_pidfile``, ``javagateway_listenip``, ``javagateway_listenport`` and ``javagateway_startpollers`` renamed to ``zabbix_javagateway_xyz`` (see `UPGRADE.md <https://github.com/ansible-collections/community.zabbix/blob/main/docs/UPGRADE.md>`_)." -msgstr "zabbix_javagateway - ``javagateway_pidfile`` オプションã€``javagateway_listenip`` オプションã€``javagateway_listenport``ã€ãŠã‚ˆã³ ``javagateway_startpollers`` オプションã®åå‰ãŒ ``zabbix_javagateway_xyz`` ã«å¤‰æ›´ã•ã‚Œã¦ã„ã¾ã™ (`UPGRADE.md <https://github.com/ansible-collections/community.zabbix/blob/main/docs/UPGRADE.md>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:561 -msgid "Change ``ip-addresses`` key in netbox inventory plugin to ``ip_addresses`` (https://github.com/netbox-community/ansible_modules/issues/139)" -msgstr "netbox インベントリープラグイン㮠``ip-addresses`` ã‚ーを ``ip_addresses`` ã«å¤‰æ›´ã—ã¾ã™ (https://github.com/netbox-community/ansible_modules/issues/139)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:562 -msgid "Changed ``group`` to ``tenant_group`` in ``netbox_tenant.py`` (https://github.com/netbox-community/ansible_modules/issues/9)" -msgstr "``netbox_tenant.py`` ã® ``group`` ã‚’ ``tenant_group`` ã¸å¤‰æ›´ã—ã¾ã—㟠(https://github.com/netbox-community/ansible_modules/issues/9)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:563 -msgid "Changed ``role`` to ``prefix_role`` in ``netbox_prefix.py`` (https://github.com/netbox-community/ansible_modules/issues/9)" -msgstr "``netbox_prefix.py`` ã® ``role`` ã‚’ ``prefix_role`` ã¸å¤‰æ›´ã—ã¾ã—㟠(https://github.com/netbox-community/ansible_modules/issues/9)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:564 -msgid "Module failures when required fields arent provided (https://github.com/netbox-community/ansible_modules/issues/24)" -msgstr "å¿…é ˆãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ãŒæä¾›ã•ã‚Œã¦ã„ãªã„å ´åˆã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®å¤±æ•— (https://github.com/netbox-community/ansible_modules/issues/24)" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:565 -msgid "Renamed ``netbox_interface`` to ``netbox_device_interface`` (https://github.com/netbox-community/ansible_modules/issues/9)" -msgstr "``netbox_interface`` ã®åå‰ãŒ ``netbox_device_interface`` ã«å¤‰æ›´ (https://github.com/netbox-community/ansible_modules/issues/9)" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:566 -msgid "This version has a few breaking changes due to new namespace and collection name. I felt it necessary to change the name of the lookup plugin and inventory plugin just not to have a non descriptive namespace call to use them. Below is an example: ``netbox.netbox.netbox`` would be used for both inventory plugin and lookup plugin, but in different contexts so no collision will arise, but confusion will. I renamed the lookup plugin to ``nb_lookup`` so it will be used with the FQCN ``netbox.netbox.nb_lookup``. The inventory plugin will now be called within an inventory file by ``netbox.netbox.nb_inventory``" -msgstr "ã“ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«ã¯ã€æ–°ã—ã„åå‰ç©ºé–“ã¨ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³åã®ãŸã‚ã«ã„ãã¤ã‹ã®é‡å¤§ãªå¤‰æ›´ãŒã‚ã‚Šã¾ã™ã€‚lookup プラグイン㨠inventory プラグインã®åå‰ã‚’変更ã—ã¦ã€ãれを使用ã™ã‚‹ãŸã‚ã®éžè¨˜è¿°çš„ãªåå‰ç©ºé–“呼ã³å‡ºã—ã‚’è¡Œã‚ãªã„よã†ã«ã™ã‚‹å¿…è¦ãŒã‚ã‚‹ã¨æ„Ÿã˜ã¾ã—ãŸã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚inventory プラグイン㨠lookup プラグインã®ä¸¡æ–¹ã« ``netbox.netbox.netbox`` ãŒä½¿ç”¨ã•ã‚Œã¾ã™ãŒã€ã‚³ãƒ³ãƒ†ã‚ストãŒç•°ãªã‚‹ãŸã‚ã€è¡çªã¯ç™ºç”Ÿã—ã¾ã›ã‚“ãŒã€æ··ä¹±ãŒç™ºç”Ÿã—ã¾ã™ã€‚lookup プラグインã®åå‰ã‚’ ``nb_lookup`` ã«å¤‰æ›´ã—ã¾ã—ãŸã€‚ãã®ãŸã‚ã€FQCN ``netbox.netbox.nb_lookup`` ã§ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚インベントリープラグインã¯ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ•ã‚¡ã‚¤ãƒ«å†…㧠``netbox.netbox.nb_inventory`` ã«ã‚ˆã‚Šå‘¼ã³å‡ºã•ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:570 -msgid "To pass in integers via Ansible Jinja filters for a key in ``data`` that requires querying an endpoint is now done by making it a dictionary with an ``id`` key. The previous behavior was to just pass in an integer and it was converted when normalizing the data, but some people may have names that are all integers and those were being converted erroneously so we made the decision to change the method to convert to an integer for the NetBox API." -msgstr "エンドãƒã‚¤ãƒ³ãƒˆã¸ã®å•ã„åˆã‚ã›ãŒå¿…è¦ãª ``data`` ã®ã‚ーã«å¯¾ã—ã¦ã€Ansible Jinja ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã§æ•´æ•°ã‚’渡ã™ãŸã‚ã«ã¯ã€``id`` ã‚ーをæŒã¤ãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼ã«ã™ã‚‹ã“ã¨ã§è¡Œã†ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã¾ã§ã®å‹•ä½œã§ã¯ã€æ•´æ•°ã‚’渡ã™ã ã‘ã§ãƒ‡ãƒ¼ã‚¿ã®æ£è¦åŒ–時ã«å¤‰æ›ã•ã‚Œã¦ã„ã¾ã—ãŸãŒã€äººã«ã‚ˆã£ã¦ã¯åå‰ãŒã™ã¹ã¦æ•´æ•°ã§ã‚ã‚‹å ´åˆãŒã‚ã‚Šã€ãれらãŒèª¤ã£ã¦å¤‰æ›ã•ã‚Œã¦ã„ãŸãŸã‚ã€NetBox API ã§ã¯æ•´æ•°ã«å¤‰æ›ã™ã‚‹æ–¹æ³•ã«å¤‰æ›´ã™ã‚‹ã“ã¨ã«ã—ã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:593 -msgid "``pynetbox`` changed to using ``requests.Session()`` to manage the HTTP session which broke passing in ``ssl_verify`` when building the NetBox API client. This PR makes ``pynetbox 5.0.4+`` the new required version of `pynetbox` for the Ansible modules and lookup plugin. (https://github.com/netbox-community/ansible_modules/pull/269)" -msgstr "``pynetbox`` ã¯ã€NetBox API クライアントを構築ã™ã‚‹éš›ã« ``ssl_verify`` を渡ã™ã“ã¨ãŒã§ããªããªã£ãŸãŸã‚ã€HTTP セッションã®ç®¡ç†ã« ``requests.Session()`` を使用ã™ã‚‹ã‚ˆã†ã«å¤‰æ›´ã—ã¾ã—ãŸã€‚ã“ã® PR ã«ã‚ˆã‚Šã€``pynetbox 5.0.4+`` ã¯ã€Ansible モジュール㨠lookup プラグインã«å¿…è¦ãª `pynetbox` ã®æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¨ãªã‚Šã¾ã—㟠(https://github.com/netbox-community/ansible_modules/pull/269)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:599 -#: ../../rst/porting_guides/porting_guide_4.rst:474 -msgid "theforeman.foreman" -msgstr "theforeman.foreman" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:601 -msgid "All modules were renamed to drop the ``foreman_`` and ``katello_`` prefixes. Additionally to the prefix removal, the following modules were further ranamed:" -msgstr "ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®åå‰ãŒ ``foreman_`` 接é 辞ãŠã‚ˆã³ ``katello_`` 接é 辞を削除ã™ã‚‹ã‚ˆã†ã«å¤‰æ›´ã•ã‚Œã¾ã—ãŸã€‚接é 辞ã®å‰Šé™¤ä»¥å¤–ã«ã€ä»¥ä¸‹ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®åå‰ãŒã•ã‚‰ã«ç„¡è¦–ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:604 -msgid "katello_upload to content_upload" -msgstr "katello_upload ã‹ã‚‰ content_upload ã¸" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:605 -msgid "katello_sync to repository_sync" -msgstr "katello_sync ã‹ã‚‰ repository_sync ã¸" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:606 -msgid "katello_manifest to subscription_manifest" -msgstr "katello_manifest ã‹ã‚‰ subscription_manifest ã¸" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:607 -msgid "foreman_search_facts to resource_info" -msgstr "foreman_search_facts ã‹ã‚‰ resource_info ã¸" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:608 -msgid "foreman_ptable to partition_table" -msgstr "foreman_ptable ã‹ã‚‰ partition_table ã¸" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:609 -msgid "foreman_model to hardware_model" -msgstr "foreman_model ã‹ã‚‰ hardware_model ã¸" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:610 -msgid "foreman_environment to puppet_environment" -msgstr "foreman_environment ã‹ã‚‰ puppet_environment ã¸" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:618 -msgid "Both ansible-doc and ansible-console's help command will error for modules and plugins whose return documentation cannot be parsed as YAML. All modules and plugins passing ``ansible-test sanity --test yamllint`` will not be affected by this." -msgstr "ansible-doc 㨠ansible-console ã® help コマンドã®ä¸¡æ–¹ãŒã€ãƒªã‚¿ãƒ¼ãƒ³ãƒ‰ã‚ュメント㌠YAML ã¨ã—ã¦è§£æžã§ããªã„モジュールã¨ãƒ—ラグインã«å¯¾ã—ã¦ã‚¨ãƒ©ãƒ¼ã‚’出ã—ã¾ã™ã€‚``ansible-test sanity --test yamllint`` を通éŽã™ã‚‹ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¨ãƒ—ラグインã¯ã€ã“ã®å½±éŸ¿ã‚’å—ã‘ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:619 -msgid "Collections may declare a list of supported/tested Ansible versions for the collection. A warning is issued if a collection does not support the Ansible version that loads it (can also be configured as silent or a fatal error). Collections that do not declare supported Ansible versions do not issue a warning/error." -msgstr "コレクションã¯ã€ãã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã§ã‚µãƒãƒ¼ãƒˆ/テストã•ã‚Œã¦ã„ã‚‹ Ansible ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒªã‚¹ãƒˆã‚’宣言ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚コレクションãŒã€ãれをèªã¿è¾¼ã‚€ Ansible ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’サãƒãƒ¼ãƒˆã—ã¦ã„ãªã„å ´åˆã¯ã€è¦å‘ŠãŒç™ºè¡Œã•ã‚Œã¾ã™ (サイレントã¾ãŸã¯è‡´å‘½çš„ãªã‚¨ãƒ©ãƒ¼ã¨ã—ã¦è¨å®šã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™)。サãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã‚‹ Ansible ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’宣言ã—ã¦ã„ãªã„コレクションã¯ã€è¦å‘Š/エラーを発行ã—ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:620 -msgid "Plugin routing allows collections to declare deprecation, redirection targets, and removals for all plugin types." -msgstr "プラグインルーティングã«ã‚ˆã‚Šã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã¯ã™ã¹ã¦ã®ãƒ—ラグインタイプã®éžæŽ¨å¥¨ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚¿ãƒ¼ã‚²ãƒƒãƒˆã€ãŠã‚ˆã³å‰Šé™¤ã‚’宣言ã§ãã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:621 -msgid "Plugins that import module_utils and other ansible namespaces that have moved to collections should continue to work unmodified." -msgstr "コレクションã«ç§»å‹•ã—㟠module_utils ãŠã‚ˆã³ãã®ä»–ã® Ansible åå‰ç©ºé–“をインãƒãƒ¼ãƒˆã™ã‚‹ãƒ—ラグインã¯ã€å¤‰æ›´ã›ãšã«å‹•ä½œã—続ã‘ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:622 -msgid "Routing data built into Ansible 2.10 ensures that 2.9 content should work unmodified on 2.10. Formerly included modules and plugins that were moved to collections are still accessible by their original unqualified names, so long as their destination collections are installed." -msgstr "Ansible 2.10 ã«çµ„ã¿è¾¼ã¾ã‚ŒãŸãƒ«ãƒ¼ãƒ†ã‚£ãƒ³ã‚°ãƒ‡ãƒ¼ã‚¿ã«ã‚ˆã‚Šã€2.9 ã®ã‚³ãƒ³ãƒ†ãƒ³ãƒ„㌠2.10 ã§å¤‰æ›´ãªã動作ã™ã‚‹ã“ã¨ãŒä¿è¨¼ã•ã‚Œã¾ã™ã€‚コレクションã«ç§»å‹•ã—ãŸä»¥å‰ã«åŒæ¢±ã•ã‚Œã¦ã„るモジュールやプラグインã¯ã€ç§»å‹•å…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹é™ã‚Šã€å…ƒã®æœªä¿®é£¾åã§ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:623 -msgid "When deprecations are done in code, they to specify a ``collection_name`` so that deprecation warnings can mention which collection - or ansible-base - is deprecating a feature. This affects all ``Display.deprecated()`` or ``AnsibleModule.deprecate()`` or ``Ansible.Basic.Deprecate()`` calls, and ``removed_in_version``/``removed_at_date`` or ``deprecated_aliases`` in module argument specs." -msgstr "コードã§éžæŽ¨å¥¨ã¨ãªã£ãŸå ´åˆã¯ã€éžæŽ¨å¥¨ã®è¦å‘Šã§ã©ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (ã¾ãŸã¯ ansible-base) ãŒæ©Ÿèƒ½ã‚’éžæŽ¨å¥¨ã¨ã—ã¦ã„ã‚‹ã‹ã‚’言åŠã§ãるよã†ã«ã€``collection_name`` を指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€ã™ã¹ã¦ã® ``Display.deprecated()``ã€``AnsibleModule.deprecate()``ã€ã¾ãŸã¯``Ansible.Basic.Deprecate()`` ã®å‘¼ã³å‡ºã—ã€ãŠã‚ˆã³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«å¼•æ•°ä»•æ§˜ã® ``removed_in_version``/``removed_at_date`` ã¾ãŸã¯ ``deprecated_aliases`` ã«å½±éŸ¿ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:624 -msgid "ansible-test now uses a different ``default`` test container for Ansible Collections" -msgstr "ansible-test ãŒã€Ansible Collections ã«ç•°ãªã‚‹ ``default`` テストコンテナーを使用ã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:629 -msgid "ec2 module_utils - The ``AWSRetry`` decorator no longer catches ``NotFound`` exceptions by default. ``NotFound`` exceptions need to be explicitly added using ``catch_extra_error_codes``. Some AWS modules may see an increase in transient failures due to AWS''s eventual consistency model." -msgstr "ec2 module_utils - ``AWSRetry`` デコレーターã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ ``NotFound`` ã®ä¾‹å¤–ã‚’ã‚ャッãƒã—ãªããªã‚Šã¾ã—ãŸã€‚``NotFound`` ã®ä¾‹å¤–ã¯ã€``catch_extra_error_codes`` を使用ã—ã¦æ˜Žç¤ºçš„ã«è¿½åŠ ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚一部㮠AWS モジュールã§ã¯ã€AWS ã®æœ€çµ‚çš„ãªä¸€è²«æ€§ãƒ¢ãƒ‡ãƒ«ã«ã‚ˆã‚Šã€ä¸€æ™‚çš„ãªéšœå®³ãŒå¢—åŠ ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:632 -#: ../../rst/porting_guides/porting_guide_2.10.rst:794 -#: ../../rst/porting_guides/porting_guide_4.rst:180 -#: ../../rst/porting_guides/porting_guide_4.rst:438 -#: ../../rst/porting_guides/porting_guide_4.rst:498 -#: ../../rst/porting_guides/porting_guide_4.rst:719 -msgid "ansible.netcommon" -msgstr "ansible.netcommon" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:634 -msgid "Add libssh connection plugin and refactor network_cli (https://github.com/ansible-collections/ansible.netcommon/pull/30)" -msgstr "libssh æŽ¥ç¶šãƒ—ãƒ©ã‚°ã‚¤ãƒ³ã‚’è¿½åŠ ã—ã€refactor network_cli をリファクタリングã—ã¾ã™ (https://github.com/ansible-collections/ansible.netcommon/pull/30)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:637 -msgid "ansible.posix" -msgstr "ansible.posix" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:639 -msgid "Bootstrap Collection (https://github.com/ansible-collections/ansible.posix/pull/1)." -msgstr "ブートストラップコレクション (https://github.com/ansible-collections/ansible.posix/pull/1)" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:644 -msgid "Rewrite requests method for version 1.0 API and improved readability" -msgstr "ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 1.0 ã® API ã«åˆã‚ã›ã¦ requests メソッドを書ãæ›ãˆã€èªã¿ã‚„ã™ã•ã‚’å‘上ã•ã›ã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:645 -msgid "meraki_mr_rf_profile - Configure wireless RF profiles." -msgstr "meraki_mr_rf_profile - ワイヤレス RF プãƒãƒ•ã‚¡ã‚¤ãƒ«ã‚’è¨å®šã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:646 -msgid "meraki_mr_settings - Configure network settings for wireless." -msgstr "meraki_mr_settings - ワイヤレスã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯è¨å®šã‚’構æˆã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:647 -msgid "meraki_ms_l3_interface - New module" -msgstr "meraki_ms_l3_interface - æ–°ã—ã„モジュール" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:648 -msgid "meraki_ms_ospf - Configure OSPF." -msgstr "meraki_ms_ospf - OSPF ã‚’è¨å®šã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:653 -msgid "docker_container - the ``network_mode`` option will be set by default to the name of the first network in ``networks`` if at least one network is given and ``networks_cli_compatible`` is ``true`` (will be default from community.general 2.0.0 on). Set to an explicit value to avoid deprecation warnings if you specify networks and set ``networks_cli_compatible`` to ``true``. The current default (not specifying it) is equivalent to the value ``default``." -msgstr "docker_container -``network_mode`` オプションã¯ã€å°‘ãªãã¨ã‚‚ 1 ã¤ã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãŒæŒ‡å®šã•ã‚Œã€``networks_cli_compatible`` ãŒ``true`` ã§ã‚ã‚‹å ´åˆã¯ã€``networks`` ã®æœ€åˆã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã®åå‰ãŒãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§è¨å®šã•ã‚Œã¾ã™ (community.general 2.0.0 以é™ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã«ãªã‚Šã¾ã™)。ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚’指定ã—㦠``networks_cli_compatible`` ã‚’ ``true`` ã«è¨å®šã—ãŸå ´åˆã®éžæŽ¨å¥¨è¦å‘Šã‚’回é¿ã™ã‚‹ãŸã‚ã«ã€æ˜Žç¤ºçš„ãªå€¤ã«è¨å®šã—ã¾ã™ã€‚ç¾åœ¨ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆ (指定ãªã—) ã¯ã€``default`` ã®å€¤ã¨åŒç‰ã§ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:654 -msgid "docker_container - the module has a new option, ``container_default_behavior``, whose default value will change from ``compatibility`` to ``no_defaults``. Set to an explicit value to avoid deprecation warnings." -msgstr "docker_container - モジュールã«ã¯æ–°ã—ã„オプション ``container_default_behavior`` ãŒã‚ã‚Šã€ãã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã¯ ``compatibility`` ã‹ã‚‰ ``no_defaults`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ã€‚éžæŽ¨å¥¨ã®è¦å‘Šã‚’回é¿ã™ã‚‹ãŸã‚ã«æ˜Žç¤ºçš„ãªå€¤ã‚’è¨å®šã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:655 -msgid "gitlab_user - no longer requires ``name``, ``email`` and ``password`` arguments when ``state=absent``." -msgstr "gitlab_user - ``state=absent`` ã®å ´åˆã« ``name`` 引数ã€``email`` 引数ã€ãŠã‚ˆã³ ``password`` 引数ãŒå¿…è¦ãªããªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:660 -msgid "Add changelog management for ansible 2.10 (#112)" -msgstr "Ansible 2.10 ã® changelog 管ç†ã‚’è¿½åŠ (#112)" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:661 -msgid "grafana_datasource ; adding additional_json_data param" -msgstr "grafana_datasource - additional_json_data パラメーターã®è¿½åŠ " - -#: ../../rst/porting_guides/porting_guide_2.10.rst:666 -msgid "Add changelog and fragments and document changelog process (https://github.com/ansible-collections/community.kubernetes/pull/131)." -msgstr "変更ãƒã‚°ãŠã‚ˆã³ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã‚’è¿½åŠ ã—ã€å¤‰æ›´ãƒã‚°ãƒ—ãƒã‚»ã‚¹ã‚’文書化ã—ã¾ã™ (https://github.com/ansible-collections/community.kubernetes/pull/131)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:667 -msgid "helm - New module for managing Helm charts (https://github.com/ansible-collections/community.kubernetes/pull/61)." -msgstr "helm - Helm ãƒãƒ£ãƒ¼ãƒˆç®¡ç†ç”¨ã®æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/community.kubernetes/pull/61)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:668 -msgid "helm_info - New module for retrieving Helm chart information (https://github.com/ansible-collections/community.kubernetes/pull/61)." -msgstr "helm_info - Helm ãƒãƒ£ãƒ¼ãƒˆæƒ…å ±ã‚’å–å¾—ã™ã‚‹æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/community.kubernetes/pull/61)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:669 -msgid "helm_plugin - new module to manage Helm plugins (https://github.com/ansible-collections/community.kubernetes/pull/154)." -msgstr "helm_plugin - Helm プラグインを管ç†ã™ã‚‹æ–°ã—ã„モジュール (https://github.com/ansible-collections/community.kubernetes/pull/154)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:670 -msgid "helm_plugin_info - new modules to gather information about Helm plugins (https://github.com/ansible-collections/community.kubernetes/pull/154)." -msgstr "helm_plugin_info - Helm プラグインã«é–¢ã™ã‚‹æƒ…å ±ã‚’åŽé›†ã™ã‚‹æ–°ã—ã„モジュール (https://github.com/ansible-collections/community.kubernetes/pull/154)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:671 -msgid "helm_repository - New module for managing Helm repositories (https://github.com/ansible-collections/community.kubernetes/pull/61)." -msgstr "helm_repository - Helm リãƒã‚¸ãƒˆãƒªãƒ¼ã‚’管ç†ã™ã‚‹ãŸã‚ã®æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/community.kubernetes/pull/61)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:672 -#: ../../rst/porting_guides/porting_guide_3.rst:389 -msgid "k8s - Inventory source migrated from Ansible 2.9 to Kubernetes collection." -msgstr "k8s - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚½ãƒ¼ã‚¹ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:673 -#: ../../rst/porting_guides/porting_guide_3.rst:390 -msgid "k8s - Lookup plugin migrated from Ansible 2.9 to Kubernetes collection." -msgstr "k8s - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸãƒ—ラグイン。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:674 -#: ../../rst/porting_guides/porting_guide_3.rst:391 -msgid "k8s - Module migrated from Ansible 2.9 to Kubernetes collection." -msgstr "k8s - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:675 -#: ../../rst/porting_guides/porting_guide_3.rst:393 -msgid "k8s_auth - Module migrated from Ansible 2.9 to Kubernetes collection." -msgstr "k8s_auth - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:676 -#: ../../rst/porting_guides/porting_guide_3.rst:394 -msgid "k8s_config_resource_name - Filter plugin migrated from Ansible 2.9 to Kubernetes collection." -msgstr "k8s_config_resource_name - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸãƒ—ラグインã«ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã‚’è¨å®šã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:677 -msgid "k8s_exec - New module for executing commands on pods via Kubernetes API (https://github.com/ansible-collections/community.kubernetes/pull/14)." -msgstr "k8s_exec - Kubernetes API を使用ã—㦠Pod ã§ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã™ã‚‹æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/community.kubernetes/pull/14)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:678 -msgid "k8s_exec - Return rc for the command executed (https://github.com/ansible-collections/community.kubernetes/pull/158)." -msgstr "k8s_exec - 実行ã—ãŸã‚³ãƒžãƒ³ãƒ‰ã® rc ã‚’è¿”ã—ã¾ã™ (https://github.com/ansible-collections/community.kubernetes/pull/158)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:679 -#: ../../rst/porting_guides/porting_guide_3.rst:397 -msgid "k8s_info - Module migrated from Ansible 2.9 to Kubernetes collection." -msgstr "k8s_info - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:680 -msgid "k8s_log - New module for retrieving pod logs (https://github.com/ansible-collections/community.kubernetes/pull/16)." -msgstr "k8s_log - Pod ãƒã‚°ã‚’å–å¾—ã™ã‚‹æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/community.kubernetes/pull/16)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:681 -#: ../../rst/porting_guides/porting_guide_3.rst:399 -msgid "k8s_scale - Module migrated from Ansible 2.9 to Kubernetes collection." -msgstr "k8s_scale - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:682 -#: ../../rst/porting_guides/porting_guide_3.rst:400 -msgid "k8s_service - Module migrated from Ansible 2.9 to Kubernetes collection." -msgstr "k8s_service - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:683 -#: ../../rst/porting_guides/porting_guide_3.rst:401 -msgid "kubectl - Connection plugin migrated from Ansible 2.9 to Kubernetes collection." -msgstr "kubectl - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸæŽ¥ç¶šãƒ—ラグイン。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:684 -#: ../../rst/porting_guides/porting_guide_3.rst:402 -msgid "openshift - Inventory source migrated from Ansible 2.9 to Kubernetes collection." -msgstr "openshift - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚½ãƒ¼ã‚¹ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:687 -msgid "community.libvirt" -msgstr "community.libvirt" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:689 -msgid "added generic libvirt inventory plugin" -msgstr "汎用 libvirt インベントリープラグインã®è¿½åŠ " - -#: ../../rst/porting_guides/porting_guide_2.10.rst:690 -msgid "removed libvirt_lxc inventory script" -msgstr "libvirt_lxc インベントリースクリプトを削除" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:693 -#: ../../rst/porting_guides/porting_guide_3.rst:309 -#: ../../rst/porting_guides/porting_guide_3.rst:367 -msgid "dellemc.os10" -msgstr "dellemc.os10" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:695 -msgid "New role os10_aaa - Facilitates the configuration of Authentication Authorization and Accounting (AAA), TACACS and RADIUS server." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_aaa - èªè¨¼æ‰¿èªãŠã‚ˆã³ã‚¢ã‚«ã‚¦ãƒ³ãƒˆ (AAA)ã€TACACS サーãƒãƒ¼ãŠã‚ˆã³ RADIUS サーãƒãƒ¼ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:696 -msgid "New role os10_acl - Facilitates the configuration of Access Control lists." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_acl - アクセス制御リストã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:697 -msgid "New role os10_bfd - Facilitates the configuration of BFD global attributes." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_bfd - BFD ã‚°ãƒãƒ¼ãƒãƒ«å±žæ€§ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:698 -msgid "New role os10_bgp - Facilitates the configuration of border gateway protocol (BGP) attributes." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_bgp - 境界線ゲートウェイプãƒãƒˆã‚³ãƒ« (BGP) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:699 -msgid "New role os10_copy_config - This role pushes the backup running configuration into a OS10 device." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_copy_config - ã“ã®ãƒãƒ¼ãƒ«ã¯ã€ãƒãƒƒã‚¯ã‚¢ãƒƒãƒ—ã®å®Ÿè¡Œè¨å®šã‚’ OS10 デãƒã‚¤ã‚¹ã«ãƒ—ッシュã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:700 -msgid "New role os10_dns - Facilitates the configuration of domain name service (DNS)." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_dns - ドメインãƒãƒ¼ãƒ サービス (DNS) ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:701 -msgid "New role os10_ecmp - Facilitates the configuration of equal cost multi-path (ECMP) for IPv4." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_ecmp - IPv4 用ã®åŒç‰ã®ã‚³ã‚¹ãƒˆãƒžãƒ«ãƒãƒ‘ス (ECMP) ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:702 -msgid "New role os10_fabric_summary Facilitates to get show system information of all the OS10 switches in the fabric." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_fabric_summary - ファブリック内ã®ã™ã¹ã¦ã® OS10 スイッãƒã®ã‚·ã‚¹ãƒ†ãƒ æƒ…å ±ã‚’è¡¨ç¤ºã™ã‚‹ã®ã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:703 -msgid "New role os10_flow_monitor Facilitates the configuration of ACL flow-based monitoring attributes." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_flow_monitor - ACL フãƒãƒ¼ãƒ™ãƒ¼ã‚¹ã®ç›£è¦–属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:704 -msgid "New role os10_image_upgrade Facilitates installation of OS10 software images." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_image_upgrade - OS10 ソフトウェアイメージã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:705 -msgid "New role os10_interface Facilitates the configuration of interface attributes." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_interface - インターフェース属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:706 -msgid "New role os10_lag Facilitates the configuration of link aggregation group (LAG) attributes." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_lag - リンクアグリゲーショングループ (LAG) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:707 -msgid "New role os10_lldp Facilitates the configuration of link layer discovery protocol (LLDP) attributes at global and interface level." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_lldp - ã‚°ãƒãƒ¼ãƒãƒ«ãŠã‚ˆã³ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ãƒ¬ãƒ™ãƒ«ã§ã®ãƒªãƒ³ã‚¯ãƒ¬ã‚¤ãƒ¤ãƒ¼æ¤œå‡ºãƒ—ãƒãƒˆã‚³ãƒ« (LLDP) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:708 -msgid "New role os10_logging Facilitates the configuration of global logging attributes and logging servers." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_logging - ã‚°ãƒãƒ¼ãƒãƒ«ãƒã‚®ãƒ³ã‚°å±žæ€§ãŠã‚ˆã³ãƒã‚®ãƒ³ã‚°ã‚µãƒ¼ãƒãƒ¼ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:709 -msgid "New role os10_network_validation Facilitates validation of wiring connection, BGP neighbors, MTU between neighbors and VLT pair." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_network_validation - é…線接続ã€BGP 近接ã€è¿‘接間 MTUã€VLT ペアã®æ¤œè¨¼ã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:710 -msgid "New role os10_ntp Facilitates the configuration of network time protocol (NTP) attributes." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_ntp - ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚¿ã‚¤ãƒ プãƒãƒˆã‚³ãƒ« (NTP) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:711 -msgid "New role os10_prefix_list Facilitates the configuration of IP prefix-list." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_prefix_list - IP プレフィックスリストã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:712 -msgid "New role os10_qos Facilitates the configuration of quality of service attributes including policy-map and class-map." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_qos - policy-map ãŠã‚ˆã³ class-map ã‚’å«ã‚€ QoS (Quality of Service) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:713 -msgid "New role os10_raguard Facilitates the configuration of IPv6 RA Guard attributes." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_raguard - IPv6 RA Guard 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:714 -msgid "New role os10_route_map Facilitates the configuration of route-map attributes." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_route_map - route-map 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:715 -msgid "New role os10_snmp Facilitates the configuration of global SNMP attributes." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_snmp - ã‚°ãƒãƒ¼ãƒãƒ« SNMP 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:716 -msgid "New role os10_system Facilitates the configuration of hostname and hashing algorithm." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_system - ホストåã¨ãƒãƒƒã‚·ãƒ¥ã‚¢ãƒ«ã‚´ãƒªã‚ºãƒ ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:717 -msgid "New role os10_template The role takes the raw string input from the CLI of OS10 device, and returns a structured text in the form of a Python dictionary." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_template - ã“ã®ãƒãƒ¼ãƒ«ã¯ã€OS10 デãƒã‚¤ã‚¹ã® CLI ã‹ã‚‰ raw æ–‡å—列入力をå–å¾—ã—ã€Python ディクショナリーã®å½¢å¼ã§æ§‹é€ 化ã•ã‚ŒãŸãƒ†ã‚ストを返ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:718 -msgid "New role os10_uplink Facilitates the configuration of uplink attributes like uplink-state group." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_uplink - uplink-state グループã®ã‚ˆã†ãªã‚¢ãƒƒãƒ—リンク属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:719 -msgid "New role os10_users Facilitates the configuration of global system user attributes." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_users - ã‚°ãƒãƒ¼ãƒãƒ«ã‚·ã‚¹ãƒ†ãƒ ユーザー属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:720 -msgid "New role os10_vlan Facilitates the configuration of virtual LAN (VLAN) attributes." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_vlan - 仮想 LAN (VLAN) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:721 -msgid "New role os10_vlt Facilitates the configuration of virtual link trunking (VLT)." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_vlt - 仮想リンクトランク (VLT) ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:722 -msgid "New role os10_vrf Facilitates the configuration of virtual routing and forwarding (VRF)." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_vrf - VRF (Virtual Routing and Forwarding) ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:723 -msgid "New role os10_vrrp Facilitates the configuration of virtual router redundancy protocol (VRRP) attributes." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_vrrp - 仮想ルーター冗長性プãƒãƒˆã‚³ãƒ« (VRRP) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:724 -msgid "New role os10_vxlan Facilitates the configuration of virtual extensible LAN (VXLAN) attributes." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_vxlan - 仮想拡張å¯èƒ½ LAN (VXLAN) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:725 -msgid "New role os10_xstp Facilitates the configuration of xSTP attributes." -msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_xstp - xSTP 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:730 -msgid "Broke apart bigip_device_auth_radius to implement radius server configuration in bigip_device_auth_server module. Refer to module documentation for usage details" -msgstr "bigip_device_auth_radius を分割ã—ã€radius サーãƒã®è¨å®šã‚’ bigip_device_auth_server モジュールã«å®Ÿè£…ã—ã¾ã—ãŸã€‚使用方法ã®è©³ç´°ã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ‰ã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:731 -msgid "Remove redundant parameters in f5_provider to fix disparity between documentation and module parameters" -msgstr "f5_provider ã§å†—é•·ãªãƒ‘ラメーターを削除ã—ã¦ã€ãƒ‰ã‚ュメントã¨ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ‘ラメーターã®ä¸ä¸€è‡´ã‚’ä¿®æ£ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:734 -#: ../../rst/porting_guides/porting_guide_4.rst:148 -msgid "gluster.gluster" -msgstr "gluster.gluster" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:736 -msgid "geo_rep - Added the independent module of geo rep with other gluster modules (https://github.com/gluster/gluster-ansible-collection/pull/2)." -msgstr "geo_rep - ä»–ã® gluster モジュールã¨ã€geo rep ã®ç‹¬ç«‹ã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒè¿½åŠ ã•ã‚Œã¾ã—㟠(https://github.com/gluster/gluster-ansible-collection/pull/2)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:741 -msgid "ovirt_disk - Add backup (https://github.com/oVirt/ovirt-ansible-collection/pull/57)." -msgstr "ovirt_disk - ãƒãƒƒã‚¯ã‚¢ãƒƒãƒ—è¿½åŠ ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/57)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:742 -msgid "ovirt_disk - Support direct upload/download (https://github.com/oVirt/ovirt-ansible-collection/pull/35)." -msgstr "ovirt_disk - 直接アップãƒãƒ¼ãƒ‰/ダウンãƒãƒ¼ãƒ‰ã‚’サãƒãƒ¼ãƒˆã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/35)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:743 -msgid "ovirt_host - Add ssh_port (https://github.com/oVirt/ovirt-ansible-collection/pull/60)." -msgstr "ovirt_host - ssh_port ã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/60)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:744 -msgid "ovirt_vm_os_info - Creation of module (https://github.com/oVirt/ovirt-ansible-collection/pull/26)." -msgstr "ovirt_vm_os_info - モジュールを作æˆã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/26)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:747 -msgid "purestorage.flasharray" -msgstr "purestorage.flasharray" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:749 -msgid "purefa_console - manage Console Lock setting for the FlashArray" -msgstr "purefa_console - FlashArray ã®ã‚³ãƒ³ã‚½ãƒ¼ãƒ«ãƒãƒƒã‚¯è¨å®šã‚’管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:750 -msgid "purefa_endpoint - manage VMware protocol-endpoints on the FlashArray" -msgstr "purefa_endpoint - FlashArray 㧠VMware プãƒãƒˆã‚³ãƒ«ã‚¨ãƒ³ãƒ‰ãƒã‚¤ãƒ³ãƒˆã‚’管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:751 -msgid "purefa_eula - sign, or resign, FlashArray EULA" -msgstr "purefa_eula - sign ã¾ãŸã¯ resignã€FlashArray EULA" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:752 -msgid "purefa_inventory - get hardware inventory information from a FlashArray" -msgstr "purefa_inventory - FlashArray ã‹ã‚‰ãƒãƒ¼ãƒ‰ã‚¦ã‚§ã‚¢ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼æƒ…å ±ã‚’å–å¾—ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:753 -msgid "purefa_network - manage the physical and virtual network settings on the FlashArray" -msgstr "purefa_network - FlashArray ã§ç‰©ç†ãŠã‚ˆã³ä»®æƒ³ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã®è¨å®šã‚’管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:754 -msgid "purefa_pgsched - manage protection group snapshot and replication schedules on the FlashArray" -msgstr "purefa_pgsched - FlashArray ã§ä¿è·ã‚°ãƒ«ãƒ¼ãƒ—ã®ã‚¹ãƒŠãƒƒãƒ—ショットãŠã‚ˆã³ãƒ¬ãƒ—リケーションスケジュールを管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:755 -msgid "purefa_pod - manage ActiveCluster pods in FlashArrays" -msgstr "purefa_pod - FlashArray 㧠ActiveCluster Pod を管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:756 -msgid "purefa_pod_replica - manage ActiveDR pod replica links in FlashArrays" -msgstr "purefa_pod_replica - FlashArray 㧠ActiveDR Pod レプリカリンクを管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:757 -msgid "purefa_proxy - manage the phonehome HTTPS proxy setting for the FlashArray" -msgstr "purefa_proxy - FlashArray ã® phonehome HTTPS プãƒã‚シーè¨å®šã‚’管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:758 -msgid "purefa_smis - manage SMI-S settings on the FlashArray" -msgstr "purefa_smis - FlashArray 㧠SMI-S è¨å®šã‚’管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:759 -msgid "purefa_subnet - manage network subnets on the FlashArray" -msgstr "purefa_subnet - FlashArray ã§ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚µãƒ–ãƒãƒƒãƒˆã‚’管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:760 -msgid "purefa_timeout - manage the GUI idle timeout on the FlashArray" -msgstr "purefa_timeout - FlashArray 㧠GUI ã®ã‚¢ã‚¤ãƒ‰ãƒ«ã‚¿ã‚¤ãƒ アウトを管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:761 -msgid "purefa_vlan - manage VLAN interfaces on the FlashArray" -msgstr "purefa_vlan - FlashArray 㧠VLAN インターフェースを管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:762 -msgid "purefa_vnc - manage VNC for installed applications on the FlashArray" -msgstr "purefa_vnc - FlashArray ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚ŒãŸã‚¢ãƒ—リケーション㮠VNC を管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:763 -msgid "purefa_volume_tags - manage volume tags on the FlashArray" -msgstr "purefa_volume_tags - FlashArray ã§ãƒœãƒªãƒ¥ãƒ¼ãƒ タグを管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:766 -msgid "purestorage.flashblade" -msgstr "purestorage.flashblade" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:768 -msgid "purefb_alert - manage alert email settings on a FlashBlade" -msgstr "purefb_alert - FlashBlade ã§ã‚¢ãƒ©ãƒ¼ãƒˆã®ãƒ¡ãƒ¼ãƒ«è¨å®šã‚’管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:769 -msgid "purefb_bladename - manage FlashBlade name" -msgstr "purefb_bladename - FlashBlade åを管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:770 -msgid "purefb_bucket_replica - manage bucket replica links on a FlashBlade" -msgstr "purefb_bucket_replica - FlashBlade ã§ãƒã‚±ãƒƒãƒˆãƒ¬ãƒ—リカリンクを管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:771 -msgid "purefb_connect - manage connections between FlashBlades" -msgstr "purefb_connect - FlashBlades é–“ã®æŽ¥ç¶šã‚’管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:772 -msgid "purefb_dns - manage DNS settings on a FlashBlade" -msgstr "purefb_dns - FlashBlade 㧠DNS è¨å®šã‚’管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:773 -msgid "purefb_fs_replica - manage filesystem replica links on a FlashBlade" -msgstr "purefb_fs_replica - FlashBlade ã§ãƒ•ã‚¡ã‚¤ãƒ«ã‚·ã‚¹ãƒ†ãƒ レプリカリンクを管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:774 -msgid "purefb_inventory - get information about the hardware inventory of a FlashBlade" -msgstr "purefb_inventory - FlashBlade ã®ãƒãƒ¼ãƒ‰ã‚¦ã‚§ã‚¢ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã«é–¢ã™ã‚‹æƒ…å ±ã‚’å–å¾—ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:775 -msgid "purefb_ntp - manage the NTP settings for a FlashBlade" -msgstr "purefb_ntp - FlashBlade ã® NTP è¨å®šã‚’管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:776 -msgid "purefb_phonehome - manage the phone home settings for a FlashBlade" -msgstr "purefb_phonehome - FlashBlade ã®é›»è©±ãƒ›ãƒ¼ãƒ ディレクトリーè¨å®šã‚’管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:777 -msgid "purefb_policy - manage the filesystem snapshot policies for a FlashBlade" -msgstr "purefb_policy - FlashBlade ã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚·ã‚¹ãƒ†ãƒ スナップショットãƒãƒªã‚·ãƒ¼ã‚’管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:778 -msgid "purefb_proxy - manage the phone home HTTP proxy settings for a FlashBlade" -msgstr "purefb_proxy - FlashBlade ã®é›»è©±ãƒ›ãƒ¼ãƒ HTTP プãƒã‚シーè¨å®šã‚’管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:779 -msgid "purefb_remote_cred - manage the Object Store Remote Credentials on a FlashBlade" -msgstr "purefb_remote_cred - FlashBlade ã§ã‚ªãƒ–ジェクトストアã®ãƒªãƒ¢ãƒ¼ãƒˆèªè¨¼æƒ…å ±ã‚’ç®¡ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:780 -msgid "purefb_snmp_agent - modify the FlashBlade SNMP Agent" -msgstr "purefb_snmp_agent - FlashBlade SNMP エージェントを変更ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:781 -msgid "purefb_snmp_mgr - manage SNMP Managers on a FlashBlade" -msgstr "purefb_snmp_mgr - FlashBlade 㧠SNMP Manager を管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:782 -msgid "purefb_target - manage remote S3-capable targets for a FlashBlade" -msgstr "purefb_target - FlashBlade ã®ãƒªãƒ¢ãƒ¼ãƒˆ S3 対応ターゲットを管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:783 -msgid "purefb_user - manage local ``pureuser`` account password on a FlashBlade" -msgstr "purefb_user - FlashBlade ã§ãƒãƒ¼ã‚«ãƒ«ã® ``pureuser`` アカウントã®ãƒ‘スワードを管ç†ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:791 -msgid "core - remove support for ``check_invalid_arguments`` in ``AnsibleModule``, ``AzureModule`` and ``UTMModule``." -msgstr "core - ``AnsibleModule``ã€``AzureModule``ã€ãŠã‚ˆã³ ``UTMModule`` ã® ``check_invalid_arguments`` ã®ã‚µãƒãƒ¼ãƒˆã‚’削除ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:796 -msgid "module_utils.network.common.utils.ComplexDict has been removed" -msgstr "module_utils.network.common.utils.ComplexDict ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:801 -msgid "win_stat - removed the deprecated ``get_md55`` option and ``md5`` return value." -msgstr "win_stat - éžæŽ¨å¥¨ã® ``get_md55`` オプション㨠``md5`` ã®æˆ»ã‚Šå€¤ã‚’削除ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:804 -#: ../../rst/porting_guides/porting_guide_2.10.rst:919 -#: ../../rst/porting_guides/porting_guide_3.rst:114 -#: ../../rst/porting_guides/porting_guide_3.rst:169 -#: ../../rst/porting_guides/porting_guide_4.rst:742 -msgid "community.crypto" -msgstr "community.crypto" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:806 -msgid "The ``letsencrypt`` module has been removed. Use ``acme_certificate`` instead." -msgstr "``letsencrypt`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``acme_certificate`` を使用ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:811 -#: ../../rst/porting_guides/porting_guide_3.rst:538 -msgid "conjur_variable lookup - has been moved to the ``cyberark.conjur`` collection. A redirection is active, which will be removed in version 2.0.0 (https://github.com/ansible-collections/community.general/pull/570)." -msgstr "conjur_variable ルックアップ - ``cyberark.conjur`` コレクションã«ç§»å‹•ã—ã¾ã—ãŸã€‚リダイレクトã¯ã‚¢ã‚¯ãƒ†ã‚£ãƒ–ã§ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/570)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:812 -msgid "core - remove support for ``check_invalid_arguments`` in ``UTMModule``." -msgstr "core - ``UTMModule`` ã® ``check_invalid_arguments`` ã®ã‚µãƒãƒ¼ãƒˆã‚’削除ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:813 -#: ../../rst/porting_guides/porting_guide_3.rst:539 -msgid "digital_ocean_* - all DigitalOcean modules have been moved to the ``community.digitalocean`` collection. A redirection is active, which will be removed in version 2.0.0 (https://github.com/ansible-collections/community.general/pull/622)." -msgstr "digital_ocean_* - ã™ã¹ã¦ã® DigitalOcean モジュール㌠``community.digitalocean`` コレクションã«ç§»å‹•ã—ã¾ã—ãŸã€‚リダイレクトã¯ã‚¢ã‚¯ãƒ†ã‚£ãƒ–ã§ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/622)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:814 -#: ../../rst/porting_guides/porting_guide_3.rst:540 -msgid "infini_* - all infinidat modules have been moved to the ``infinidat.infinibox`` collection. A redirection is active, which will be removed in version 2.0.0 (https://github.com/ansible-collections/community.general/pull/607)." -msgstr "infini_* - ã™ã¹ã¦ã® infinidat モジュール㌠``infinidat.infinibox`` コレクションã«ç§»å‹•ã•ã‚Œã¾ã—ãŸã€‚リダイレクトã¯ã‚¢ã‚¯ãƒ†ã‚£ãƒ–ã§ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/607)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:815 -#: ../../rst/porting_guides/porting_guide_3.rst:542 -msgid "logicmonitor - the module has been removed in 1.0.0 since it is unmaintained and the API used by the module has been turned off in 2017 (https://github.com/ansible-collections/community.general/issues/539, https://github.com/ansible-collections/community.general/pull/541)." -msgstr "logicmonitor - ã“ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹å¯¾è±¡å¤–ã§ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒä½¿ç”¨ã™ã‚‹ API ㌠2017 å¹´ã«å‰Šé™¤ã•ã‚ŒãŸãŸã‚ã€1.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.general/issues/539ã€https://github.com/ansible-collections/community.general/pull/541)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:816 -#: ../../rst/porting_guides/porting_guide_3.rst:543 -msgid "logicmonitor_facts - the module has been removed in 1.0.0 since it is unmaintained and the API used by the module has been turned off in 2017 (https://github.com/ansible-collections/community.general/issues/539, https://github.com/ansible-collections/community.general/pull/541)." -msgstr "logicmonitor_facts - ã“ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹å¯¾è±¡å¤–ã§ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒä½¿ç”¨ã™ã‚‹ API ㌠2017 å¹´ã«å‰Šé™¤ã•ã‚ŒãŸãŸã‚ã€1.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.general/issues/539ã€https://github.com/ansible-collections/community.general/pull/541)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:817 -#: ../../rst/porting_guides/porting_guide_3.rst:545 -msgid "mysql_* - all MySQL modules have been moved to the ``community.mysql`` collection. A redirection is active, which will be removed in version 2.0.0 (https://github.com/ansible-collections/community.general/pull/633)." -msgstr "mysql_* - ã™ã¹ã¦ã® MySQL モジュール㌠``community.mysql`` コレクションã«ç§»å‹•ã—ã¾ã—ãŸã€‚リダイレクトã¯ã‚¢ã‚¯ãƒ†ã‚£ãƒ–ã§ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/633)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:818 -msgid "pacman - Removed deprecated ``recurse`` option, use ``extra_args=--recursive`` instead" -msgstr "pacman - éžæŽ¨å¥¨ã® ``recurse`` オプションを削除ã—ã¾ã—ãŸã€‚代ã‚ã‚Šã« ``extra_args=--recursive`` を使用ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:819 -#: ../../rst/porting_guides/porting_guide_3.rst:546 -msgid "proxysql_* - all ProxySQL modules have been moved to the ``community.proxysql`` collection. A redirection is active, which will be removed in version 2.0.0 (https://github.com/ansible-collections/community.general/pull/624)." -msgstr "proxysql_* - ã™ã¹ã¦ã® ProxySQL モジュール㌠``community.proxysql`` コレクションã«ç§»å‹•ã•ã‚Œã¾ã—ãŸã€‚リダイレクトã¯ã‚¢ã‚¯ãƒ†ã‚£ãƒ–ã§ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/624)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:824 -#: ../../rst/porting_guides/porting_guide_3.rst:579 -msgid "onyx - all onyx modules and plugins have been moved to the mellanox.onyx collection. Redirects have been added that will be removed in community.network 2.0.0 (https://github.com/ansible-collections/community.network/pull/83)." -msgstr "onyx - ã™ã¹ã¦ã® onyx モジュールã¨ãƒ—ラグインã¯ã€mellanox.onyx コレクションã«ç§»å‹•ã—ã¾ã—ãŸã€‚community.network 2.0.0 ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒè¿½åŠ ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.network/pull/83)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:829 -msgid "vmware_guest_find - Removed deprecated ``datacenter`` option" -msgstr "vmware_guest_find - éžæŽ¨å¥¨ã® ``datacenter`` オプションを削除ã—ã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:830 -msgid "vmware_portgroup - removed 'inbound_policy', and 'rolling_order' deprecated options." -msgstr "vmware_portgroup - 「inbound_policyã€ãŠã‚ˆã³ã€Œrolling_orderã€ã®éžæŽ¨å¥¨ã‚ªãƒ—ションを削除ã—ã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:831 -msgid "vmware_vmkernel - Removed deprecated ``ip_address`` option; use sub-option ip_address in the network option instead" -msgstr "vms_vmkernel - éžæŽ¨å¥¨ã® ``ip_address`` オプション。代ã‚ã‚Šã« network オプションã«ã‚µãƒ–オプション ip_address を使用ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:832 -msgid "vmware_vmkernel - Removed deprecated ``subnet_mask`` option; use sub-option subnet_mask in the network option instead" -msgstr "vmware_vmkernel - éžæŽ¨å¥¨ã® ``subnet_mask`` オプションを削除ã—ã¾ã—ãŸã€‚代ã‚ã‚Šã« network オプションã«ã‚µãƒ–オプション subnet_mask を使用ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:837 -msgid "win_disk_image - removed the deprecated return value ``mount_path`` in favor of ``mount_paths``." -msgstr "win_disk_image - éžæŽ¨å¥¨ã®æˆ»ã‚Šå€¤ ``mount_path`` ãŒå‰Šé™¤ã•ã‚Œã€``mount_paths`` ãŒå¤‰æ›´ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:838 -msgid "win_psexec - removed the deprecated ``extra_opts`` option." -msgstr "win_psexec - éžæŽ¨å¥¨ã® ``extra_opts`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:843 -msgid "Remove _bigip_iapplx_package alias" -msgstr "_bigip_iapplx_package エイリアスã®å‰Šé™¤" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:844 -msgid "Remove _bigip_security_address_list alias" -msgstr "_bigip_security_address_list エイリアスã®å‰Šé™¤" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:845 -msgid "Remove _bigip_security_port_list alias" -msgstr "_bigip_security_port_list エイリアスã®å‰Šé™¤" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:846 -msgid "Remove _bigip_traffic_group alias" -msgstr "_bigip_traffic_group エイリアスã®å‰Šé™¤" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:847 -msgid "Remove bigip_appsvcs_extension module" -msgstr "bigip_appsvcs_extension モジュールã®å‰Šé™¤" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:848 -msgid "Remove bigip_asm_policy module" -msgstr "bigip_asm_policy モジュールã®å‰Šé™¤" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:853 -msgid "The vyos.vyos.vyos_static_route module has been deprecated and will be removed in a later release; use vyos.vyos.vyos_static_routes instead." -msgstr "vyos.vyos.vyos_static_route モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚代ã‚ã‚Šã«ã€vyos.vyos.vyos_static_routes を使用ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:858 -msgid "Using the DefaultCallback without the correspodning doc_fragment or copying the documentation." -msgstr "対応ã™ã‚‹ doc_fragment を使用ã›ãšã« DefaultCallback を使用ã€ã¾ãŸã¯ãƒ‰ã‚ュメントã®ã‚³ãƒ”ー" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:859 -msgid "hash_behaviour - Deprecate ``hash_behaviour`` for future removal." -msgstr "hash_behaviour - 今後削除ã•ã‚Œã‚‹ ``hash_behaviour`` ã‚’éžæŽ¨å¥¨ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:860 -msgid "script inventory plugin - The 'cache' option is deprecated and will be removed in 2.12. Its use has been removed from the plugin since it has never had any effect." -msgstr "スクリプトインベントリープラグイン - 「cacheã€ã‚ªãƒ—ションã¯éžæŽ¨å¥¨ã«ãªã‚Šã€2.12 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚何も効果ãŒãªã„ãŸã‚ã€ãã®ä½¿ç”¨ã¯ãƒ—ラグインã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:865 -msgid "All AWS Modules - ``aws_access_key``, ``aws_secret_key`` and ``security_token`` will be made mutually exclusive with ``profile`` after 2022-06-01." -msgstr "ã™ã¹ã¦ã® AWS モジュール - ``aws_access_key``ã€``aws_secret_key``ã€ãŠã‚ˆã³ ``security_token`` 㯠2022-06-01 以é™ã« ``profile`` ã¨ç›¸äº’ã«æŽ’ä»–çš„ã«ãªã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:866 -#: ../../rst/porting_guides/porting_guide_2.10.rst:894 -msgid "cloudformation - The ``template_format`` option had no effect since Ansible 2.3 and will be removed after 2022-06-01" -msgstr "cloudformation - ``template_format`` オプション㯠Ansible 2.3 以é™ã«ã¯å½±éŸ¿ã—ã¾ã›ã‚“ãŒã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:867 -msgid "cloudformation - the ``template_format`` option has been deprecated and will be removed in a later release. It has been ignored by the module since Ansible 2.3." -msgstr "cloudformation - ``template_format`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚ã“れ㯠Ansible 2.3 以é™ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚ˆã£ã¦ç„¡è¦–ã•ã‚Œã¦ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:868 -msgid "data_pipeline - The ``version`` option had no effect and will be removed in after 2022-06-01" -msgstr "data_pipeline - ``version`` オプションã¯å½±éŸ¿ã‚’å—ã‘ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:869 -msgid "ec2 - in a later release, the ``group`` and ``group_id`` options will become mutually exclusive. Currently ``group_id`` is ignored if you pass both." -msgstr "ec2 - 今後ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€``group`` オプション㨠``group_id`` オプションãŒç›¸äº’ã«æŽ’ä»–çš„ã«ãªã‚Šã¾ã™ã€‚ç¾æ™‚点ã§ã¯ã€ä¸¡æ–¹ã‚’渡ã™ã¨ ``group_id`` ã¯ç„¡è¦–ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:870 -msgid "ec2_ami - The ``no_device`` alias ``NoDevice`` has been deprecated and will be removed after 2022-06-01" -msgstr "ec2_ami - ``no_device`` エイリアス ``NoDevice`` ã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:871 -msgid "ec2_ami - The ``virtual_name`` alias ``VirtualName`` has been deprecated and will be removed after 2022-06-01" -msgstr "ec2_ami - ``virtual_name`` エイリアス ``VirtualName`` ã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:872 -#: ../../rst/porting_guides/porting_guide_2.10.rst:897 -msgid "ec2_eip - The ``wait_timeout`` option had no effect and will be removed after 2022-06-01" -msgstr "ec2_eip - ``wait_timeout`` オプションã¯å½±éŸ¿ã‚’å—ã‘ã¦ãŠã‚‰ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:873 -#: ../../rst/porting_guides/porting_guide_2.10.rst:899 -msgid "ec2_key - The ``wait_timeout`` option had no effect and will be removed after 2022-06-01" -msgstr "ec2_key - ``wait_timeout`` オプションã¯å½±éŸ¿ã‚’å—ã‘ã¦ãŠã‚‰ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:874 -#: ../../rst/porting_guides/porting_guide_2.10.rst:900 -msgid "ec2_key - The ``wait`` option had no effect and will be removed after 2022-06-01" -msgstr "ec2_key - ``wait`` オプションã¯å½±éŸ¿ã‚’å—ã‘ã¦ãŠã‚‰ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:875 -msgid "ec2_key - the ``wait_timeout`` option has been deprecated and will be removed in a later release. It has had no effect since Ansible 2.5." -msgstr "ec2_key - ``wait_timeout`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚Ansible 2.5 以é™ã«ã¯å¤‰æ›´ã¯ã‚ã‚Šã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:876 -msgid "ec2_key - the ``wait`` option has been deprecated and will be removed in a later release. It has had no effect since Ansible 2.5." -msgstr "ec2_key - ``wait`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚Ansible 2.5 以é™ã«ã¯å¤‰æ›´ã¯ã‚ã‚Šã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:877 -#: ../../rst/porting_guides/porting_guide_2.10.rst:901 -msgid "ec2_lc - The ``associate_public_ip_address`` option had no effect and will be removed after 2022-06-01" -msgstr "ec2_lc - ``associate_public_ip_address`` オプションã¯å½±éŸ¿ã‚’å—ã‘ã¦ãŠã‚‰ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:878 -msgid "ec2_tag - deprecate the ``list`` option in favor of ec2_tag_info" -msgstr "ec2_tag - ``list`` オプションãŒéžæŽ¨å¥¨ã«ãªã‚Šã€ec2_tag_info ãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:879 -msgid "ec2_tag - support for ``list`` as a state has been deprecated and will be removed in a later release. The ``ec2_tag_info`` can be used to fetch the tags on an EC2 resource." -msgstr "ec2_tag - 状態ã¨ã—ã¦ã® ``list`` ã®ã‚µãƒãƒ¼ãƒˆã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚``ec2_tag_info`` を使用ã™ã‚‹ã¨ã€EC2 リソースã§ã‚¿ã‚°ã‚’å–å¾—ã§ãã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:884 -msgid "win_domain_computer - Deprecated the undocumented ``log_path`` option. This option will be removed in a major release after ``2022-07-01``." -msgstr "win_domain_ computers - ドã‚ュメント化ã•ã‚Œã¦ã„ãªã„ ``log_path`` オプションãŒéžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚ã“ã®ã‚ªãƒ—ション㯠``2022-07-01`` 後ã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:885 -msgid "win_domain_controller - the ``log_path`` option has been deprecated and will be removed in a later release. This was undocumented and only related to debugging information for module development." -msgstr "win_domain_controller - ``log_path`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯æ–‡æ›¸åŒ–ã•ã‚Œã¦ãŠã‚‰ãšã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«é–‹ç™ºã®ãƒ‡ãƒãƒƒã‚°æƒ…å ±ã«ã®ã¿é–¢é€£ã—ã¦ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:886 -msgid "win_package - the ``ensure`` alias for the ``state`` option has been deprecated and will be removed in a later release. Please use ``state`` instead of ``ensure``." -msgstr "win_package - ``state`` オプション㮠``ensure`` エイリアスã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚``ensure`` ã®ä»£ã‚ã‚Šã« ``state`` を使用ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:887 -msgid "win_package - the ``productid`` alias for the ``product_id`` option has been deprecated and will be removed in a later release. Please use ``product_id`` instead of ``productid``." -msgstr "win_package - ``product_id`` オプション㮠``productid`` エイリアスã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚``productid`` ã®ä»£ã‚ã‚Šã« ``product_id`` を使用ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:888 -msgid "win_package - the ``username`` and ``password`` options has been deprecated and will be removed in a later release. The same functionality can be done by using ``become: yes`` and ``become_flags: logon_type=new_credentials logon_flags=netcredentials_only`` on the task." -msgstr "win_package - ``username`` オプションãŠã‚ˆã³ ``password`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚åŒæ§˜ã«ã€ã‚¿ã‚¹ã‚¯ã® ``become: yes`` ãŠã‚ˆã³ ``become_flags: logon_type=new_credentials logon_flags=netcredentials_only`` を使用ã—ã¦å®Ÿè¡Œã§ãã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:889 -msgid "win_regedit - Deprecated using forward slashes as a path separator, use backslashes to avoid ambiguity between a forward slash in the key name or a forward slash as a path separator. This feature will be removed in a major release after ``2021-07-01``." -msgstr "win_regedit - スラッシュをパス区切り文å—ã¨ã—ã¦ä½¿ç”¨ã—ã€ãƒãƒƒã‚¯ã‚¹ãƒ©ãƒƒã‚·ãƒ¥ã‚’使用ã—ã¦ã€ã‚ーåã®ã‚¹ãƒ©ãƒƒã‚·ãƒ¥ã¨ãƒ‘ス区切りã®ã‚¹ãƒ©ãƒƒã‚·ãƒ¥ã®æ›–昧ã•ã‚’回é¿ã—ã¾ã™ã€‚ã“ã®æ©Ÿèƒ½ã¯ã€``2021-07-01`` ã®å¾Œã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:895 -msgid "data_pipeline - The ``version`` option had no effect and will be removed after 2022-06-01" -msgstr "data_pipeline - ``version`` オプションã¯å½±éŸ¿ã‚’å—ã‘ã¦ãŠã‚‰ãšã€2022-06-01 以é™å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:896 -msgid "data_pipeline - the ``version`` option has been deprecated and will be removed in a later release. It has always been ignored by the module." -msgstr "data_pipeline - ``version`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚常ã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚ˆã£ã¦ç„¡è¦–ã•ã‚Œã¦ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:898 -msgid "ec2_eip - the ``wait_timeout`` option has been deprecated and will be removed in a later release. It has had no effect since Ansible 2.3." -msgstr "ec2_eip - ``wait_timeout`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚Ansible 2.3 以é™ã¯å¤‰æ›´ã•ã‚Œã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:902 -msgid "ec2_lc - the ``associate_public_ip_address`` option has been deprecated and will be removed after a later release. It has always been ignored by the module." -msgstr "ec2_lc - ``associate_public_ip_address`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚常ã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚ˆã£ã¦ç„¡è¦–ã•ã‚Œã¦ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:903 -msgid "elb_network_lb - The current default value of the ``state`` option has been deprecated and will change from absent to present after 2022-06-01" -msgstr "elb_network_lb - ``state`` オプションã®ç¾åœ¨ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€2022-06-01 以é™ã« absent ã‹ã‚‰ present ã«å¤‰æ›´ã™ã‚‹äºˆå®šã§ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:904 -msgid "elb_network_lb - in a later release, the default behaviour for the ``state`` option will change from ``absent`` to ``present``. To maintain the existing behavior explicitly set state to ``absent``." -msgstr "elb_network_lb - 今後ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€``state`` オプションã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå‹•ä½œãŒ ``absent`` ã‹ã‚‰ ``present`` ã«å¤‰æ›´ãªã‚Šã¾ã™ã€‚æ—¢å˜ã®å‹•ä½œã‚’ç¶æŒã™ã‚‹ã«ã¯ã€çŠ¶æ…‹ã‚’明示的㫠``absent`` ã«è¨å®šã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:905 -msgid "iam_managed_policy - The ``fail_on_delete`` option had no effect and will be removed after 2022-06-01" -msgstr "iam_managed_policy - ``fail_on_delete`` オプションã¯å½±éŸ¿ã‚’å—ã‘ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:906 -msgid "iam_managed_policy - the ``fail_on_delete`` option has been deprecated and will be removed after a later release. It has always been ignored by the module." -msgstr "iam_managed_policy - ``fail_on_delete`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚常ã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚ˆã£ã¦ç„¡è¦–ã•ã‚Œã¦ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:907 -msgid "iam_policy - The ``policy_document`` will be removed after 2022-06-01. To maintain the existing behavior use the ``policy_json`` option and read the file with the ``lookup`` plugin." -msgstr "iam_policy - ``policy_document`` 㯠2022-06-01 以é™å‰Šé™¤ã•ã‚Œã¾ã™ã€‚æ—¢å˜ã®å‹•ä½œã‚’ç¶æŒã™ã‚‹ã«ã¯ã€``policy_json`` オプションを使用ã—㦠``lookup`` プラグインã§ãƒ•ã‚¡ã‚¤ãƒ«ã‚’èªã¿å–ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:908 -msgid "iam_policy - The default value of ``skip_duplicates`` will change after 2022-06-01 from ``true`` to ``false``." -msgstr "iam_policy -``skip_duplicates`` ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã¯ã€2022-06-01 以é™ã€``true`` ã‹ã‚‰``false`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:909 -msgid "iam_policy - in a later release, the default value for the ``skip_duplicates`` option will change from ``true`` to ``false``. To maintain the existing behavior explicitly set it to ``true``." -msgstr "iam_policy - 今後ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€``skip_duplicates`` オプションã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ãŒ ``true`` ã‹ã‚‰``false`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ã€‚æ—¢å˜ã®å‹•ä½œã‚’ç¶æŒã™ã‚‹ã«ã¯ã€æ˜Žç¤ºçš„ã« ``true`` ã«è¨å®šã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:910 -msgid "iam_policy - the ``policy_document`` option has been deprecated and will be removed after a later release. To maintain the existing behavior use the ``policy_json`` option and read the file with the ``lookup`` plugin." -msgstr "iam_policy - ``policy_document`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€å¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚æ—¢å˜ã®å‹•ä½œã‚’ç¶æŒã™ã‚‹ã«ã¯ã€``policy_json`` オプションを使用ã—ã€``lookup`` プラグインã§ãƒ•ã‚¡ã‚¤ãƒ«ã‚’èªã¿è¾¼ã‚“ã§ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:911 -msgid "iam_role - The default value of the purge_policies has been deprecated and will change from true to false after 2022-06-01" -msgstr "iam_role - purge_policies ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€2022-06-01 以é™ã¯ true ã‹ã‚‰ false ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:912 -msgid "iam_role - in a later release, the ``purge_policies`` option (also know as ``purge_policy``) default value will change from ``true`` to ``false``" -msgstr "iam_role - 今後ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€``purge_policies`` オプション (``purge_policy`` ã¨ã‚‚呼ã°ã‚Œã‚‹) ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ãŒ ``true`` ã‹ã‚‰ ``false`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:913 -msgid "s3_lifecycle - The ``requester_pays`` option had no effect and will be removed after 2022-06-01" -msgstr "s3_lifecycle - ``requester_pays`` オプションã¯å½±éŸ¿ã‚’å—ã‘ã¦ãŠã‚‰ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:914 -msgid "s3_lifecycle - the ``requester_pays`` option has been deprecated and will be removed after a later release. It has always been ignored by the module." -msgstr "s3_lifecycle - ``requester_pays`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚モジュールã§ã¯å¸¸ã«ç„¡è¦–ã•ã‚Œã¦ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:915 -msgid "s3_sync - The ``retries`` option had no effect and will be removed after 2022-06-01" -msgstr "s3_sync - ``retries`` オプションã¯å½±éŸ¿ã‚’å—ã‘ã¦ãŠã‚‰ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:916 -msgid "s3_sync - the ``retries`` option has been deprecated and will be removed after 2022-06-01. It has always been ignored by the module." -msgstr "s3_sync - ``retries`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€2022-06-01 以é™ã¯å‰Šé™¤ã•ã‚Œã¾ã™ã€‚モジュールã§ã¯å¸¸ã«ç„¡è¦–ã•ã‚Œã¦ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:921 -msgid "openssl_csr - all values for the ``version`` option except ``1`` are deprecated. The value 1 denotes the current only standardized CSR version." -msgstr "openssl_csr - ``version`` オプション㮠``1`` 以外ã®å€¤ã¯éžæŽ¨å¥¨ã§ã™ã€‚値 1 ã¯ã€ç¾åœ¨å”¯ä¸€æ¨™æº–化ã•ã‚Œã¦ã„ã‚‹ CSR ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’示ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:926 -#: ../../rst/porting_guides/porting_guide_3.rst:611 -msgid "The ldap_attr module has been deprecated and will be removed in a later release; use ldap_attrs instead." -msgstr "ldap_attr モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ldap_attrs を使用ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:927 -msgid "airbrake_deployment - Add deprecation notice for ``token`` parameter and v2 api deploys. This feature will be removed in community.general 3.0.0." -msgstr "airbrake_deployment - ``token`` パラメーター㨠v2 api ã®ãƒ‡ãƒ—ãƒã‚¤ã«é–¢ã™ã‚‹éžæŽ¨å¥¨ã®å‘ŠçŸ¥ã‚’è¿½åŠ ã—ã¾ã™ã€‚ã“ã®æ©Ÿèƒ½ã¯ community.general 3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:928 -msgid "clc_aa_policy - The ``wait`` option had no effect and will be removed in community.general 3.0.0." -msgstr "clc_aa_policy - ``wait`` オプションã¯å½±éŸ¿ã‚’å—ã‘ãšã€community.general 3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:929 -msgid "clc_aa_policy - the ``wait`` parameter will be removed. It has always been ignored by the module." -msgstr "clc_aa_policy - ``wait`` パラメーターã¯å‰Šé™¤ã•ã‚Œã¾ã™ã€‚常ã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚ˆã‚Šç„¡è¦–ã•ã‚Œã¦ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:930 -msgid "docker_container - the ``trust_image_content`` option is now deprecated and will be removed in community.general 3.0.0. It has never been used by the module." -msgstr "docker_container - ``trust_image_content`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€community.general 3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚モジュールã§ä½¿ç”¨ã•ã‚Œã‚‹ã“ã¨ã¯ã‚ã‚Šã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:931 -msgid "docker_container - the ``trust_image_content`` option will be removed. It has always been ignored by the module." -msgstr "docker_container - ``trust_image_content`` オプションã¯å‰Šé™¤ã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¾ã§ã‚‚モジュールã¯ã“ã®ã‚ªãƒ—ションを無視ã—ã¦ã„ã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:932 -msgid "docker_container - the default of ``container_default_behavior`` will change from ``compatibility`` to ``no_defaults`` in community.general 3.0.0. Set the option to an explicit value to avoid a deprecation warning." -msgstr "docker_container - ``container_default_behavior`` ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ãŒ community.general 3.0.0 㧠``compatibility`` ã‹ã‚‰ ``no_defaults`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ã€‚éžæŽ¨å¥¨ã®è¦å‘Šã‚’防ããŸã‚ã«ã€ã‚ªãƒ—ションを明示的ã«è¨å®šã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:933 -msgid "docker_container - the default value for ``network_mode`` will change in community.general 3.0.0, provided at least one network is specified and ``networks_cli_compatible`` is ``true``. See porting guide, module documentation or deprecation warning for more details." -msgstr "docker_container - community.general 3.0.0 ã§ã¯ã€å°‘ãªãã¨ã‚‚ 1 ã¤ã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãŒæŒ‡å®šã•ã‚Œã€``networks_cli_compatible`` ㌠``true`` ã§ã‚ã‚‹å ´åˆã¯ã€``network_mode`` ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ãŒå¤‰æ›´ã—ã¾ã™ã€‚詳細ã¯ç§»æ¤ã‚¬ã‚¤ãƒ‰ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ‰ã‚ュメントã€ã¾ãŸã¯éžæŽ¨å¥¨ã®è¦å‘Šã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:934 -msgid "docker_stack - Return values ``out`` and ``err`` have been deprecated and will be removed in community.general 3.0.0. Use ``stdout`` and ``stderr`` instead." -msgstr "docker_stack - 戻り値㮠``out`` ã¨``err`` ã¯éžæŽ¨å¥¨ã§ã‚ã‚Šã€community.general 3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ``stdout`` ã¨``stderr`` を使用ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:935 -msgid "docker_stack - the return values ``err`` and ``out`` have been deprecated. Use ``stdout`` and ``stderr`` from now on instead." -msgstr "docker_stack - ``err`` ã¨``out`` ã®æˆ»ã‚Šå€¤ã¯éžæŽ¨å¥¨ã¨ãªã‚Šã¾ã—ãŸã€‚今後㯠``stdout`` 㨠``stderr`` を使用ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:936 -msgid "helm - Put ``helm`` module to deprecated. New implementation is available in community.kubernetes collection." -msgstr "helm - ``helm`` モジュールをéžæŽ¨å¥¨ã«ã—ã¾ã—ãŸã€‚æ–°ã—ã„実装㯠community.kubernetes コレクションã§å…¬é–‹ã•ã‚Œã¦ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:937 -msgid "redfish_config - Deprecate ``bios_attribute_name`` and ``bios_attribute_value`` in favor of new `bios_attributes`` option." -msgstr "redfish_config - ``bios_attribute_name`` 㨠``bios_attribute_value`` ã‚’éžæŽ¨å¥¨ã¨ã—ã€æ–°ã—ã„ `bios_attributes`` オプションを採用ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:938 -msgid "redfish_config - the ``bios_attribute_name`` and ``bios_attribute_value`` options will be removed. To maintain the existing behavior use the ``bios_attributes`` option instead." -msgstr "redfish_config - ``bios_attribute_name`` オプションãŠã‚ˆã³ ``bios_attribute_value`` オプションを削除ã—ã¾ã™ã€‚æ—¢å˜ã®å‹•ä½œã‚’ç¶æŒã™ã‚‹ã«ã¯ã€ä»£ã‚ã‚Šã« ``bios_attributes`` オプションを使用ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:939 -msgid "redfish_config and redfish_command - the behavior to select the first System, Manager, or Chassis resource to modify when multiple are present will be removed. Use the new ``resource_id`` option to specify target resource to modify." -msgstr "redfish_config ãŠã‚ˆã³ redfish_command - 複数ã®ãƒªã‚½ãƒ¼ã‚¹ãŒå˜åœ¨ã™ã‚‹å ´åˆã«ä¿®æ£ã™ã‚‹æœ€åˆã® System リソースã€Manager リソースã€ã¾ãŸã¯ Chassis リソースをé¸æŠžã™ã‚‹å‹•ä½œãŒå‰Šé™¤ã•ã‚Œã¾ã™ã€‚æ–°ã—ã„ ``resource_id`` オプションを使用ã—ã¦ã€å¤‰æ›´ã™ã‚‹å¯¾è±¡ã®ãƒªã‚½ãƒ¼ã‚¹ã‚’指定ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:940 -msgid "redfish_config, redfish_command - Behavior to modify the first System, Mananger, or Chassis resource when multiple are present is deprecated. Use the new ``resource_id`` option to specify target resource to modify." -msgstr "redfish_configã€redfish_command - 複数ã®ãƒªã‚½ãƒ¼ã‚¹ãŒå˜åœ¨ã™ã‚‹å ´åˆã€æœ€åˆã® Systemã€Manangerã€ã¾ãŸã¯ Chassis リソースを修æ£ã™ã‚‹å‹•ä½œã¯éžæŽ¨å¥¨ã§ã™ã€‚æ–°ã—ã„ ``resource_id`` オプションを使用ã—ã¦ã€å¤‰æ›´ã™ã‚‹å¯¾è±¡ã®ãƒªã‚½ãƒ¼ã‚¹ã‚’指定ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:941 -#: ../../rst/porting_guides/porting_guide_3.rst:616 -msgid "xbps - the ``force`` option never had any effect. It is now deprecated, and will be removed in 3.0.0 (https://github.com/ansible-collections/community.general/pull/568)." -msgstr "xbps - ``force`` オプションã«ã¯ä½•ã‚‚効果ãŒã‚ã‚Šã¾ã›ã‚“。ç¾åœ¨éžæŽ¨å¥¨ã«ãªã‚Šã€3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/568)。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:946 -msgid "The vmware_dns_config module has been deprecated and will be removed in a later release; use vmware_host_dns instead." -msgstr "vmware_dns_config モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚代ã‚ã‚Šã« vmware_host_dns を使用ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:947 -msgid "vca - vca_fw, vca_nat, vca_app are deprecated since these modules rely on deprecated part of Pyvcloud library." -msgstr "vca - vca_fw モジュールã€vca_nat モジュールã€vca_app モジュールã¯ã€Pyvcloud ライブラリーã®éžæŽ¨å¥¨ã®éƒ¨åˆ†ã«ä¾å˜ã—ã¦ã„ã‚‹ãŸã‚éžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:948 -msgid "vmware_dns_config - Deprecate in favor of new module vmware_host_dns." -msgstr "vmc_dns_config - éžæŽ¨å¥¨ã«ãªã‚Šã€æ–°ã—ã„モジュール vmware_host_dns ãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:949 -msgid "vmware_guest - deprecate specifying CDROM configuration as a dict, instead use a list." -msgstr "vmware_guest - CDROM è¨å®šã‚’ dict ã¨ã—ã¦æŒ‡å®šã™ã‚‹ã“ã¨ã‚’éžæŽ¨å¥¨ã¨ã—ã€ä»£ã‚ã‚Šã«ãƒªã‚¹ãƒˆã‚’使用ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:950 -msgid "vmware_tag_info - in a later release, the module will not return ``tag_facts`` since it does not return multiple tags with the same name and different category id. To maintain the existing behavior use ``tag_info`` which is a list of tag metadata." -msgstr "vmware_tag_info - 今後ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€åŒã˜åå‰ã§ç•°ãªã‚‹ã‚«ãƒ†ã‚´ãƒªãƒ¼ ID ã‚’æŒã¤è¤‡æ•°ã®ã‚¿ã‚°ã‚’è¿”ã•ãªã„ãŸã‚ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ ``tag_facts`` ã‚’è¿”ã—ã¾ã›ã‚“。既å˜ã®å‹•ä½œã‚’ç¶æŒã™ã‚‹ã«ã¯ã€ã‚¿ã‚°ã®ãƒ¡ã‚¿ãƒ‡ãƒ¼ã‚¿ã®ãƒªã‚¹ãƒˆã§ã‚ã‚‹ ``tag_info`` を使用ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:955 -msgid "zabbix_proxy (module) - deprecates ``interface`` sub-options ``type`` and ``main`` when proxy type is set to passive via ``status=passive``. Make sure these suboptions are removed from your playbook as they were never supported by Zabbix in the first place." -msgstr "zabbix_proxy (モジュール) - ``status=passive`` ã§ãƒ—ãƒã‚シー㌠passive ã«è¨å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€``interface`` ã®ã‚µãƒ–オプション ``type`` 㨠``main`` ã‚’éžæŽ¨å¥¨ã¨ã—ã¾ã™ã€‚ã“れらã®ã‚µãƒ–オプションã¯ãã‚‚ãã‚‚ Zabbix ã§ã¯ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ãªã„ãŸã‚ã€å¿…ãš Playbook ã‹ã‚‰å‰Šé™¤ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:960 -msgid "Deprecated bigip_appsvcs_extension module" -msgstr "éžæŽ¨å¥¨ã® bigip_appsvcs_extension モジュール" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:961 -msgid "Deprecated bigip_device_facts module name" -msgstr "éžæŽ¨å¥¨ã® bigip_device_facts モジュールå" - -#: ../../rst/porting_guides/porting_guide_2.10.rst:962 -msgid "Deprecated bigiq_device_facts module name" -msgstr "éžæŽ¨å¥¨ã® bigiq_device_facts モジュールå" +#: ../../rst/porting_guides/porting_guide_2.10.rst:13 +#: ../../rst/porting_guides/porting_guide_3.rst:13 +#: ../../rst/porting_guides/porting_guide_4.rst:13 +msgid "This link takes you to a different version of the Ansible documentation. Use the version selection on the left or your browser back button to return to this version of the documentation." +msgstr "ã“ã®ãƒªãƒ³ã‚¯ã¯ã€Ansible ã®ãƒ‰ã‚ュメントã®åˆ¥ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«ç§»å‹•ã—ã¾ã™ã€‚å·¦å´ã¾ãŸã¯ãƒ–ラウザーã®æˆ»ã‚‹ãƒœã‚¿ãƒ³ã‚’使用ã—ã¦ã€ã“ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒ‰ã‚ュメントã«æˆ»ã‚Šã¾ã™ã€‚" #: ../../rst/porting_guides/porting_guide_2.3.rst:6 msgid "Ansible 2.3 Porting Guide" @@ -2725,6 +487,19 @@ msgstr "ã“ã“ã§ã¯ã€æ›´æ–°æ™‚ã«éé‡ã™ã‚‹ã‚ã£ãŸã«ç™ºç”Ÿã—ãªã„ケー msgid "Made ``any_errors_fatal`` inheritable from play to task and all other objects in between." msgstr "``any_errors_fatal`` をプレイã‹ã‚‰ã‚¿ã‚¹ã‚¯ãŠã‚ˆã³ä»–ã®ã‚ªãƒ–ジェクトã¸ç¶™æ‰¿ã§ãるよã†ã«ã—ã¾ã—ãŸã€‚" +#: ../../rst/porting_guides/porting_guide_2.3.rst:108 +#: ../../rst/porting_guides/porting_guide_2.4.rst:77 +#: ../../rst/porting_guides/porting_guide_2.5.rst:156 +#: ../../rst/porting_guides/porting_guide_2.6.rst:28 +#: ../../rst/porting_guides/porting_guide_2.7.rst:154 +#: ../../rst/porting_guides/porting_guide_2.8.rst:364 +#: ../../rst/porting_guides/porting_guide_2.9.rst:72 +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:50 +#: ../../rst/porting_guides/porting_guide_core_2.11.rst:98 +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:72 +msgid "Modules" +msgstr "モジュール" + #: ../../rst/porting_guides/porting_guide_2.3.rst:110 #: ../../rst/porting_guides/porting_guide_2.3.rst:115 #: ../../rst/porting_guides/porting_guide_2.3.rst:157 @@ -2740,7 +515,6 @@ msgstr "ã“ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«ã¯å¤§ããªå¤‰æ›´ãŒã‚ã‚Šã¾ã›ã‚“。" #: ../../rst/porting_guides/porting_guide_2.7.rst:168 #: ../../rst/porting_guides/porting_guide_2.8.rst:382 #: ../../rst/porting_guides/porting_guide_2.9.rst:122 -#: ../../rst/porting_guides/porting_guide_4.rst:102 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:105 #: ../../rst/porting_guides/porting_guide_core_2.12.rst:82 msgid "Modules removed" @@ -2754,7 +528,6 @@ msgstr "削除ã•ã‚ŒãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«" #: ../../rst/porting_guides/porting_guide_2.7.rst:174 #: ../../rst/porting_guides/porting_guide_2.8.rst:393 #: ../../rst/porting_guides/porting_guide_2.9.rst:139 -#: ../../rst/porting_guides/porting_guide_4.rst:110 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:113 #: ../../rst/porting_guides/porting_guide_core_2.12.rst:90 msgid "Deprecation notices" @@ -2804,6 +577,19 @@ msgstr "nxos_mtu ã¯ã€ä»£ã‚ã‚Šã« :ref:`nxos_system <nxos_system_module>` ã‚’ä msgid "These modules may no longer have documentation in the current release. Please see the `Ansible 2.3 module documentation <https://docs.ansible.com/ansible/2.3/list_of_all_modules.html>`_ if you need to know how they worked for porting your playbooks." msgstr "ã“れらã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã¯ç¾åœ¨ã®ãƒªãƒªãƒ¼ã‚¹ã®ãƒ‰ã‚ュメントãŒå«ã¾ã‚Œã¦ã„ãªã„å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚Playbook ã®ç§»æ¤æ–¹æ³•ã‚’把æ¡ã™ã‚‹å¿…è¦ãŒã‚ã‚‹å ´åˆã¯ã€`Ansible 2.3 モジュールドã‚ュメント <https://docs.ansible.com/ansible/2.3/list_of_all_modules.html>`_ を確èªã—ã¦ãã ã•ã„。" +#: ../../rst/porting_guides/porting_guide_2.3.rst:141 +#: ../../rst/porting_guides/porting_guide_2.4.rst:99 +#: ../../rst/porting_guides/porting_guide_2.5.rst:207 +#: ../../rst/porting_guides/porting_guide_2.6.rst:49 +#: ../../rst/porting_guides/porting_guide_2.7.rst:193 +#: ../../rst/porting_guides/porting_guide_2.8.rst:414 +#: ../../rst/porting_guides/porting_guide_2.9.rst:699 +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:64 +#: ../../rst/porting_guides/porting_guide_core_2.11.rst:119 +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:96 +msgid "Noteworthy module changes" +msgstr "モジュール変更ã«é–¢ã™ã‚‹æ³¨ç›®ç‚¹" + #: ../../rst/porting_guides/porting_guide_2.3.rst:144 msgid "AWS lambda" msgstr "AWS ラムダ" @@ -2820,6 +606,19 @@ msgstr "マウント" msgid "Mount: Some fixes so bind mounts are not mounted each time the playbook runs." msgstr "マウント: Playbook ã®å®Ÿè¡Œæ™‚ã«ãƒã‚¤ãƒ³ãƒ‰ãƒžã‚¦ãƒ³ãƒˆãŒãƒžã‚¦ãƒ³ãƒˆã•ã‚Œãªã„よã†ã«ã™ã‚‹ä¿®æ£ã‚‚ã‚ã‚Šã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_2.3.rst:155 +#: ../../rst/porting_guides/porting_guide_2.4.rst:107 +#: ../../rst/porting_guides/porting_guide_2.5.rst:237 +#: ../../rst/porting_guides/porting_guide_2.6.rst:83 +#: ../../rst/porting_guides/porting_guide_2.7.rst:231 +#: ../../rst/porting_guides/porting_guide_2.8.rst:511 +#: ../../rst/porting_guides/porting_guide_2.9.rst:713 +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:71 +#: ../../rst/porting_guides/porting_guide_core_2.11.rst:127 +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:102 +msgid "Plugins" +msgstr "プラグイン" + #: ../../rst/porting_guides/porting_guide_2.3.rst:165 #: ../../rst/porting_guides/porting_guide_2.4.rst:199 #: ../../rst/porting_guides/porting_guide_2.6.rst:107 @@ -3005,7 +804,6 @@ msgstr ":ref:`win_shell <win_shell_module>` モジュールãŠã‚ˆã³ :ref:`win_c #: ../../rst/porting_guides/porting_guide_2.7.rst:170 #: ../../rst/porting_guides/porting_guide_2.8.rst:384 #: ../../rst/porting_guides/porting_guide_2.9.rst:124 -#: ../../rst/porting_guides/porting_guide_4.rst:104 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:107 #: ../../rst/porting_guides/porting_guide_core_2.12.rst:84 msgid "The following modules no longer exist:" @@ -3772,6 +1570,11 @@ msgstr "Openstack モジュール㧠``shade`` ライブラリーãŒä½¿ç”¨ã•ã‚Œ msgid "``openshift`` use ``k8s`` instead." msgstr "``openshift`` ã¯ã€ä»£ã‚ã‚Šã« ``k8s`` を使用ã—ã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_2.6.rst:94 +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:79 +msgid "Noteworthy plugin changes" +msgstr "注目ã™ã¹ãプラグインã®å¤‰æ›´ç‚¹" + #: ../../rst/porting_guides/porting_guide_2.6.rst:96 msgid "The ``k8s`` lookup plugin now supports all Kubernetes resources including those from Custom Resource Definitions and aggregated API servers. This includes all OpenShift resources." msgstr "``k8s`` lookup モジュールã¯ã€Custom Resource Definitions や集約ã•ã‚ŒãŸ API サーãƒãƒ¼ã‹ã‚‰ã®ã‚‚ã®ã‚’å«ã‚€ã™ã¹ã¦ã® Kubernetes リソースをサãƒãƒ¼ãƒˆã—ã¾ã™ã€‚ã“ã‚Œã«ã¯ã€ã™ã¹ã¦ã® OpenShift リソースもå«ã¾ã‚Œã¾ã™ã€‚" @@ -3804,6 +1607,15 @@ msgstr "ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€Ansible 2.6 ã‹ã‚‰ Ansible 2.7 ã«ãŠã‘ã‚ msgid "We suggest you read this page along with `Ansible Changelog for 2.7 <https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst>`_ to understand what updates you may need to make." msgstr "å¿…è¦ãªæ›´æ–°ã«ã¤ã„ã¦ç†è§£ã™ã‚‹ã«ã¯ã€ã“ã®ãƒšãƒ¼ã‚¸ã¨ä½µã›ã¦ã€Œ`Ansible Changelog for 2.7 <https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" +#: ../../rst/porting_guides/porting_guide_2.7.rst:18 +#: ../../rst/porting_guides/porting_guide_2.8.rst:305 +#: ../../rst/porting_guides/porting_guide_2.9.rst:37 +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:36 +#: ../../rst/porting_guides/porting_guide_core_2.11.rst:27 +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:46 +msgid "Command Line" +msgstr "コマンドライン" + #: ../../rst/porting_guides/porting_guide_2.7.rst:20 msgid "If you specify ``--tags`` or ``--skip-tags`` multiple times on the command line, Ansible will merge the specified tags together. In previous versions of Ansible, you could set ``merge_multiple_cli_tags`` to ``False`` if you wanted to keep only the last-specified ``--tags``. This config option existed for backwards compatibility. The overwriting behavior was deprecated in 2.3 and the default behavior was changed in 2.4. Ansible-2.7 removes the config option; multiple ``--tags`` are now always merged." msgstr "コマンドライン㧠``--tags`` ã‚„ ``--skip-tags`` を複数回指定ã—ãŸå ´åˆã€Ansible ã¯æŒ‡å®šã•ã‚ŒãŸã‚¿ã‚°ã‚’ã¾ã¨ã‚ã¦ãƒžãƒ¼ã‚¸ã—ã¾ã™ã€‚Ansible ã®ä»¥å‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã¯ã€æœ€å¾Œã«æŒ‡å®šã—㟠``--tags`` ã ã‘を残ã—ãŸã„å ´åˆã¯ã€``merge_multiple_cli_tags`` ã‚’ ``False`` ã«è¨å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã—ãŸã€‚ã“ã®è¨å®šã‚ªãƒ—ションã¯å¾Œæ–¹äº’æ›æ€§ã®ãŸã‚ã«å˜åœ¨ã—ã¦ã„ã¾ã—ãŸã€‚上書ãã®å‹•ä½œã¯ 2.3 ã§éžæŽ¨å¥¨ã¨ãªã‚Šã€2.4 ã§ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã®å‹•ä½œãŒå¤‰æ›´ã•ã‚Œã¾ã—ãŸã€‚Ansible-2.7 ã§ã¯ã€ã“ã®è¨å®šã‚ªãƒ—ションãŒå‰Šé™¤ã•ã‚Œã€è¤‡æ•°ã® ``--tags`` ãŒå¸¸ã«ãƒžãƒ¼ã‚¸ã•ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" @@ -4381,6 +2193,12 @@ msgstr "Ansible ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.8.14 ã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒãƒ•ã‚¡ã‚¤ãƒ«ãƒ™ãƒ msgid "If you changed any tasks to specify less restrictive permissions while using 2.8.14, those changes will be unnecessary (but will do no harm) in 2.8.15." msgstr "2.8.14 を使用ã™ã‚‹éš›ã«ã€ã‚ˆã‚Šåˆ¶é™ã®å°‘ãªã„パーミッションを指定ã™ã‚‹ã‚ˆã†ã«ã‚¿ã‚¹ã‚¯ã‚’変更ã—ãŸå ´åˆã€2.8.15 ã§ã¯ãã®å¤‰æ›´ã¯ä¸è¦ã«ãªã‚Šã¾ã™ (ãŸã ã—ã€å®³ã¯ã‚ã‚Šã¾ã›ã‚“)。" +#: ../../rst/porting_guides/porting_guide_2.8.rst:376 +#: ../../rst/porting_guides/porting_guide_2.9.rst:79 +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:58 +msgid "To avoid the issue raised in CVE-2020-1736, specify a ``mode`` parameter in all file-based tasks that accept it." +msgstr "CVE-2020-1736 ã§ç™ºç”Ÿã™ã‚‹å•é¡Œã‚’回é¿ã™ã‚‹ã«ã¯ã€ãれをå—ã‘入れるファイルベースã®ã‚¿ã‚¹ã‚¯ã§ ``mode`` パラメーターを指定ã—ã¾ã™ã€‚" + #: ../../rst/porting_guides/porting_guide_2.8.rst:378 msgid "``dnf`` and ``yum`` - As of version 2.8.15, the ``dnf`` module (and ``yum`` action when it uses ``dnf``) now correctly validates GPG signatures of packages (CVE-2020-14365). If you see an error such as ``Failed to validate GPG signature for [package name]``, please ensure that you have imported the correct GPG key for the DNF repository and/or package you are using. One way to do this is with the ``rpm_key`` module. Although we discourage it, in some cases it may be necessary to disable the GPG check. This can be done by explicitly adding ``disable_gpg_check: yes`` in your ``dnf`` or ``yum`` task." msgstr "``dnf`` ãŠã‚ˆã³ ``yum`` - ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.8.15 よりã€``dnf`` モジュール (ãŠã‚ˆã³ ``dnf`` を使用ã™ã‚‹å ´åˆã¯ ``yum`` アクション) ãŒãƒ‘ッケージ㮠GPG ç½²åã‚’æ£ã—ã検証ã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—㟠(CVE-2020-14365)。``Failed to validate GPG signature for [package name]`` ã®ã‚ˆã†ãªã‚¨ãƒ©ãƒ¼ãŒè¡¨ç¤ºã•ã‚ŒãŸå ´åˆã¯ã€ä½¿ç”¨ã—ã¦ã„ã‚‹ DNF リãƒã‚¸ãƒˆãƒªãƒ¼ã‚„パッケージ㮠GPG ã‚ーãŒæ£ã—ãインãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。ã“れを行ㆠ1 ã¤ã®æ–¹æ³•ã¨ã—ã¦ã€``rpm_key`` モジュールã®ä½¿ç”¨ãŒã‚ã‚Šã¾ã™ã€‚推奨ã¯ã—ã¾ã›ã‚“ãŒã€å ´åˆã«ã‚ˆã£ã¦ã¯ GPG ãƒã‚§ãƒƒã‚¯ã‚’無効ã«ã™ã‚‹å¿…è¦ãŒã‚ã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“。ã“ã‚Œã¯ã€``dnf`` タスクã¾ãŸã¯ ``yum`` タスク㫠``disable_gpg_check: yes`` を明示的ã«è¿½åŠ ã™ã‚‹ã“ã¨ã§å®Ÿç¾ã§ãã¾ã™ã€‚" @@ -4697,6 +2515,20 @@ msgstr "以å‰ã®å‹•ä½œã‚’許å¯ã™ã‚‹ã«ã¯ã€ã€Œ:ref:`migrating_to_loop`ã€ã§ msgid "The location of the Galaxy token file has changed from ``~/.ansible_galaxy`` to ``~/.ansible/galaxy_token``. You can configure both path and file name with the :ref:`galaxy_token_path` config." msgstr "Galaxy トークンファイルã®å ´æ‰€ãŒ ``~/.ansible_galaxy`` ã‹ã‚‰ ``~/.ansible/galaxy_token`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã—ãŸã€‚:ref:`galaxy_token_path` è¨å®šã§ã€ãƒ‘スã¨ãƒ•ã‚¡ã‚¤ãƒ«åã®ä¸¡æ–¹ã‚’è¨å®šã§ãã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_2.9.rst:45 +#: ../../rst/porting_guides/porting_guide_2.9.rst:724 +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:92 +#: ../../rst/porting_guides/porting_guide_core_2.11.rst:109 +#: ../../rst/porting_guides/porting_guide_core_2.11.rst:115 +#: ../../rst/porting_guides/porting_guide_core_2.11.rst:136 +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:86 +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:92 +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:98 +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:111 +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:117 +msgid "No notable changes" +msgstr "主ãªå¤‰æ›´ã¯ã‚ã‚Šã¾ã›ã‚“。" + #: ../../rst/porting_guides/porting_guide_2.9.rst:49 msgid "Collection loader changes" msgstr "コレクションãƒãƒ¼ãƒ€ãƒ¼ã®å¤‰æ›´" @@ -6145,2203 +3977,3054 @@ msgstr "``username``ã€``host``ã€``password`` ãªã©ã®æœ€ä¸Šä½ãƒ¬ãƒ™ãƒ«ã®æŽ¥ msgid "Change your playbooks to the connection types ``network_cli`` and ``netconf`` using standard Ansible connection properties, and setting those properties in inventory by group. As you update your playbooks and inventory files, you can easily make the change to ``become`` for privilege escalation (on platforms that support it). For more information, see the :ref:`using become with network modules<become_network>` guide and the :ref:`platform documentation<platform_options>`." msgstr "Playbook ã‚’ã€Ansible ã®æ¨™æº–çš„ãªæŽ¥ç¶šãƒ—ãƒãƒ‘ティーを使用ã—ã¦æŽ¥ç¶šã‚¿ã‚¤ãƒ— ``network_cli`` ãŠã‚ˆã³``netconf`` ã«å¤‰æ›´ã—ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã§ã“れらã®ãƒ—ãƒãƒ‘ティーをグループã”ã¨ã«è¨å®šã—ã¾ã™ã€‚Playbook ã¨ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ•ã‚¡ã‚¤ãƒ«ã‚’æ›´æ–°ã™ã‚‹éš›ã«ã€ç‰¹æ¨©æ˜‡æ ¼ã®ãŸã‚ã« ``become`` ã¸ã®å¤‰æ›´ã‚’ç°¡å˜ã«è¡Œã†ã“ã¨ãŒã§ãã¾ã™ (サãƒãƒ¼ãƒˆã—ã¦ã„るプラットフォームã®å ´åˆ)。詳細ã«ã¤ã„ã¦ã¯ã€ã€Œ:ref:`ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã§ become ã®ä½¿ç”¨<become_network>`ã€ã‚¬ã‚¤ãƒ‰ãŠã‚ˆã³ :ref:`プラットフォームã®ãƒ‰ã‚ュメント<platform_options>` ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_3.rst:8 +#: ../../rst/porting_guides/porting_guide_3.rst:7 msgid "Ansible 3 Porting Guide" msgstr "Ansible 3 移æ¤ã‚¬ã‚¤ãƒ‰" -#: ../../rst/porting_guides/porting_guide_3.rst:15 -msgid "Ansible 3 is based on Ansible-Base 2.10, which is the same major release as Ansible 2.10. Therefore, there is no section on ansible-base in this porting guide. If you are upgrading from Ansible 2.9, please first consult the Ansible 2.10 porting guide before continuing with the Ansible 3 porting guide." -msgstr "Ansible 3 ã¯ã€Ansible 2.10 ã¨åŒã˜ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã§ã‚ã‚‹ Ansible-Base 2.10 をベースã«ã—ã¦ã„ã¾ã™ã€‚ãã®ãŸã‚ã€ã“ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰ã«ã¯ã€ansible-base ã«é–¢ã™ã‚‹ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã¯ã‚ã‚Šã¾ã›ã‚“。Ansible 2.9 ã‹ã‚‰ã‚¢ãƒƒãƒ—グレードã™ã‚‹å ´åˆã¯ã€ã¾ãš Ansible 2.10 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰ã‚’å‚ç…§ã—ã¦ã‹ã‚‰ã€Ansible 3 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰ã«é€²ã‚“ã§ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_3.rst:17 -msgid "We suggest you read this page along with the `Ansible 3 Changelog <https://github.com/ansible-community/ansible-build-data/blob/main/3/CHANGELOG-v3.rst>`_ to understand what updates you may need to make." -msgstr "å¿…è¦ãªæ›´æ–°ã«ã¤ã„ã¦ç†è§£ã™ã‚‹ã«ã¯ã€ã“ã®ãƒšãƒ¼ã‚¸ã¨ä½µã›ã¦ã€Œ`Ansible 3 Changelog <https://github.com/ansible-community/ansible-build-data/blob/main/3/CHANGELOG-v3.rst>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_3.rst:20 -msgid "Porting Guide for v3.4.0" -msgstr "v3.4.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_3.rst:26 -#: ../../rst/porting_guides/porting_guide_3.rst:95 -#: ../../rst/porting_guides/porting_guide_3.rst:125 -#: ../../rst/porting_guides/porting_guide_3.rst:198 -#: ../../rst/porting_guides/porting_guide_3.rst:360 -#: ../../rst/porting_guides/porting_guide_3.rst:639 -#: ../../rst/porting_guides/porting_guide_4.rst:202 -#: ../../rst/porting_guides/porting_guide_4.rst:260 -#: ../../rst/porting_guides/porting_guide_4.rst:274 -#: ../../rst/porting_guides/porting_guide_4.rst:316 -#: ../../rst/porting_guides/porting_guide_4.rst:335 -#: ../../rst/porting_guides/porting_guide_4.rst:413 -msgid "dellemc.openmanage" -msgstr "dellemc.openmanage" - -#: ../../rst/porting_guides/porting_guide_3.rst:28 -#: ../../rst/porting_guides/porting_guide_3.rst:97 -#: ../../rst/porting_guides/porting_guide_4.rst:204 -#: ../../rst/porting_guides/porting_guide_4.rst:262 -#: ../../rst/porting_guides/porting_guide_4.rst:318 -#: ../../rst/porting_guides/porting_guide_4.rst:415 -msgid "idrac_user - Issue(192043) 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." -msgstr "idrac_user - Issue(192043)モジュール㯠``unable to perform the import or export operation because there are pending attribute changes or a configuration job is in progress`` メッセージã§ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚ジョブãŒå®Œäº†ã™ã‚‹ã¾ã§å¾…æ©Ÿã—ã€ã‚¿ã‚¹ã‚¯ã‚’å†åº¦å®Ÿè¡Œã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:29 -#: ../../rst/porting_guides/porting_guide_3.rst:98 -#: ../../rst/porting_guides/porting_guide_4.rst:416 -msgid "ome_configuration_compliance_info - Issue(195592) Module may error out with the message ``unable to process the request because an error occurred``. If the issue persists, report it to the system administrator." -msgstr "ome_configuration_compliance_info - Issue(195592) モジュール㯠``unable to process the request because an error occurred`` メッセージã§ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚å•é¡ŒãŒè§£æ±ºã—ãªã„å ´åˆã¯ã€ã‚·ã‚¹ãƒ†ãƒ 管ç†è€…ã«å ±å‘Šã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_3.rst:30 -#: ../../rst/porting_guides/porting_guide_3.rst:99 -#: ../../rst/porting_guides/porting_guide_3.rst:127 -#: ../../rst/porting_guides/porting_guide_4.rst:417 -msgid "ome_smart_fabric - Issue(185322) Only three design types are supported by OpenManage Enterprise Modular but the module successfully creates a fabric when the design type is not supported." -msgstr "ome_smart_fabric - Issue(185322)㯠OpenManage Enterprise Modular ã§ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã‚‹ 3 ã¤ã®è¨è¨ˆã‚¿ã‚¤ãƒ—ã®ã¿ã§ã™ãŒã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯è¨è¨ˆã‚¿ã‚¤ãƒ—ãŒã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ãªã„ã¨ã€ãƒ•ã‚¡ãƒ–リックãŒæ£å¸¸ã«ä½œæˆã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:31 -#: ../../rst/porting_guides/porting_guide_3.rst:100 -#: ../../rst/porting_guides/porting_guide_3.rst:128 -#: ../../rst/porting_guides/porting_guide_4.rst:263 -#: ../../rst/porting_guides/porting_guide_4.rst:319 -#: ../../rst/porting_guides/porting_guide_4.rst:418 -msgid "ome_smart_fabric_uplink - Issue(186024) ome_smart_fabric_uplink module does not allow the creation of multiple uplinks of the same name even though this is supported by OpenManage Enterprise Modular. If an uplink is created using the same name as an existing uplink, the existing uplink is modified." -msgstr "ome_smart_fabric_uplink - Issue(186024)ome_smart_fabric_uplink モジュールã§ã¯ã€OpenManage Enterprise Modular ã§ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã¦ã‚‚ã€åŒã˜åå‰ã®è¤‡æ•°ã®ã‚¢ãƒƒãƒ—リンクã®ä½œæˆã¯ã§ãã¾ã›ã‚“。アップリンクãŒæ—¢å˜ã®ã‚¢ãƒƒãƒ—リンクã¨åŒã˜åå‰ã‚’使用ã—ã¦ä½œæˆã•ã‚Œã‚‹ã¨ã€æ—¢å˜ã®ã‚¢ãƒƒãƒ—ãŒå¤‰æ›´ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:39 -#: ../../rst/porting_guides/porting_guide_4.rst:495 -msgid "ansible-test - Tests run with the ``centos6`` and ``default`` test containers now use a PyPI proxy container to access PyPI when Python 2.6 is used. This allows tests running under Python 2.6 to continue functioning even though PyPI is discontinuing support for non-SNI capable clients." -msgstr "ansible-test - ``centos6`` ãŠã‚ˆã³ ``default`` テストコンテナーã§å®Ÿè¡Œã•ã‚Œã‚‹ãƒ†ã‚¹ãƒˆã§ã¯ã€Python 2.6 ã®ä½¿ç”¨æ™‚ã« PyPI プãƒã‚シーコンテナーを使用ã—㦠PyPI ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãるよã†ã«ãªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã«ã‚ˆã‚Šã€Python 2.6 ã§å®Ÿè¡Œã•ã‚Œã‚‹ãƒ†ã‚¹ãƒˆã¯ã€PyPI 以外ã®ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã®ã‚µãƒãƒ¼ãƒˆãŒã‚ã‚‹å ´åˆã§ã‚‚引ã続ã機能ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:42 -#: ../../rst/porting_guides/porting_guide_4.rst:330 -msgid "community.postgresql" -msgstr "community.postgresql" - -#: ../../rst/porting_guides/porting_guide_3.rst:44 -#: ../../rst/porting_guides/porting_guide_4.rst:332 -msgid "postgresql_query - the default value of the ``as_single_query`` option will be changed to ``yes`` in community.postgresql 2.0.0 (https://github.com/ansible-collections/community.postgresql/issues/85)." -msgstr "postgresql_query - ``as_single_query`` オプションã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ãŒ community.postgresql 2.0.0 㧠``yes`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ (https://github.com/ansible-collections/community.postgresql/issues/85)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:47 -#: ../../rst/porting_guides/porting_guide_4.rst:564 -msgid "netapp.ontap" -msgstr "netapp.ontap" - -#: ../../rst/porting_guides/porting_guide_3.rst:49 -#: ../../rst/porting_guides/porting_guide_4.rst:566 -msgid "na_ontap_autosupport - Added REST support to the module." -msgstr "na_ontap_autosupport - モジュール㫠REST サãƒãƒ¼ãƒˆã‚’è¿½åŠ ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:57 -#: ../../rst/porting_guides/porting_guide_4.rst:739 -msgid "ec2_vpc_endpoint_info - the ``query`` option has been deprecated and will be removed after 2022-12-01 (https://github.com/ansible-collections/community.aws/pull/346). The ec2_vpc_endpoint_info now defaults to listing information about endpoints. The ability to search for information about available services has been moved to the dedicated module ``ec2_vpc_endpoint_service_info``." -msgstr "ec2_vpc_endpoint_info - ``query`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€2022-12-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.aws/pull/346）。ec2_vpc_endpoint_info ã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã‚¨ãƒ³ãƒ‰ãƒã‚¤ãƒ³ãƒˆã«é–¢ã™ã‚‹æƒ…å ±ã‚’ä¸€è¦§è¡¨ç¤ºã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚利用å¯èƒ½ãªã‚µãƒ¼ãƒ“スã«é–¢ã™ã‚‹æƒ…å ±ã®æ¤œç´¢æ©Ÿèƒ½ãŒã€å°‚用ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``ec2_vpc_endpoint_service_info`` ã«ç§»å‹•ã—ã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:62 -#: ../../rst/porting_guides/porting_guide_4.rst:373 -msgid "docker_* modules and plugins, except ``docker_swarm`` connection plugin and ``docker_compose`` and ``docker_stack*` modules - the current default ``localhost`` for ``tls_hostname`` is deprecated. In community.docker 2.0.0 it will be computed from ``docker_host`` instead (https://github.com/ansible-collections/community.docker/pull/134)." -msgstr "docker_* モジュールãŠã‚ˆã³ãƒ—ラグイン（``docker_swarm`` 接続プラグインã€``docker_compose`` モジュールã€ãŠã‚ˆã³ '`docker_stack*` モジュールを除ã）ã¯éžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚``tls_hostname`` ã®ç¾åœ¨ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆ ``localhost`` ã¯éžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚community.docker 2.0.0 ã§ã¯ã€ä»£ã‚ã‚Šã« ``docker_host`` ã‹ã‚‰è¨ˆç®—ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.docker/pull/134）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:65 -msgid "Porting Guide for v3.3.0" -msgstr "v3.3.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_3.rst:71 -#: ../../rst/porting_guides/porting_guide_3.rst:139 -#: ../../rst/porting_guides/porting_guide_4.rst:538 -msgid "community.mysql" -msgstr "community.mysql" - -#: ../../rst/porting_guides/porting_guide_3.rst:73 -#: ../../rst/porting_guides/porting_guide_4.rst:547 -msgid "mysql_user - the ``REQUIRESSL`` is an alias for the ``ssl`` key in the ``tls_requires`` option in ``community.mysql`` 2.0.0 and support will be dropped altogether in ``community.mysql`` 3.0.0 (https://github.com/ansible-collections/community.mysql/issues/121)." -msgstr "``REQUIRESSL`` ã¯ã€``community.mysql`` 2.0.0 ã® ``tls_requires`` オプションã«ã‚ã‚‹ ``ssl`` ã‚ーã®ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã§ã™ã€‚サãƒãƒ¼ãƒˆã¯ ``community.mysql`` 3.0.0 ã§ã™ã¹ã¦å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.mysql/issues/121）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:81 -#: ../../rst/porting_guides/porting_guide_4.rst:769 -msgid "vmware_vmkernel_ip_config - deprecate in favor of vmware_vmkernel (https://github.com/ansible-collections/community.vmware/pull/667)." -msgstr "vmware_vmkernel_ip_config - vmware_vmkernel ãŒæŽ¡ç”¨ã•ã‚Œã‚‹ï¼ˆéžæŽ¨å¥¨ï¼‰ï¼ˆhttps://github.com/ansible-collections/community.kubernetes/pull/16）" - -#: ../../rst/porting_guides/porting_guide_3.rst:86 -#: ../../rst/porting_guides/porting_guide_4.rst:774 -msgid "Support for Python versions earlier than 3.5 is being deprecated" -msgstr "3.5 よりもå‰ã® Python ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ã‚µãƒãƒ¼ãƒˆãŒéžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:89 -msgid "Porting Guide for v3.2.0" -msgstr "v3.2.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_3.rst:108 -#: ../../rst/porting_guides/porting_guide_4.rst:445 -msgid "docker_swarm - if ``join_token`` is specified, a returned join token with the same value will be replaced by ``VALUE_SPECIFIED_IN_NO_LOG_PARAMETER``. Make sure that you do not blindly use the join tokens from the return value of this module when the module is invoked with ``join_token`` specified! This breaking change appears in a minor release since it is necessary to fix a security issue (https://github.com/ansible-collections/community.docker/pull/103)." -msgstr "docker_swarm - ``join_token`` ãŒæŒ‡å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã€è¿”ã•ã‚Œã‚‹çµåˆãƒˆãƒ¼ã‚¯ãƒ³ãŒ ``VALUE_SPECIFIED_IN_NO_LOG_PARAMETER`` ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒ ``join_token`` ã§å‘¼ã³å‡ºã•ã‚Œã‚‹ã¨ã€ã“ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®æˆ»ã‚Šå€¤ã‹ã‚‰çµåˆãƒˆãƒ¼ã‚¯ãƒ³ã‚’使用ã—ãªã„よã†ã«ã—ã¾ã™ã€‚ã“ã®é‡å¤§ãªå¤‰æ›´ã¯ã€ã‚»ã‚ュリティーã®å•é¡Œã‚’ä¿®æ£ã™ã‚‹ãŸã‚ã«å¿…è¦ãªãŸã‚ã€ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ã«å¤‰æ›´ã«ãªã‚Šã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.docker/pull/103）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:116 -#: ../../rst/porting_guides/porting_guide_4.rst:744 -msgid "acme module_utils - the ``acme`` module_utils (``ansible_collections.community.crypto.plugins.module_utils.acme``) is deprecated and will be removed in community.crypto 2.0.0. Use the new Python modules in the ``acme`` package instead (``ansible_collections.community.crypto.plugins.module_utils.acme.xxx``) (https://github.com/ansible-collections/community.crypto/pull/184)." -msgstr "acme module_utils - ``acme`` module_utils（``ansible_collections.community.crypto.plugins.module_utils.acme``）ã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€community.crypto 2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ``acme`` パッケージã§æ–°ã—ã„ Python モジュールを使用ã—ã¦ãã ã•ã„（``ansible_collections.community.crypto.plugins.module_utils.acme.xxx``)（https://github.com/ansible-collections/community.crypto/pull/184）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:119 -msgid "Porting Guide for v3.1.0" -msgstr "v3.1.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_3.rst:136 -#: ../../rst/porting_guides/porting_guide_4.rst:535 -msgid "introduce \"skip_version_check\" parameter in grafana_teams and grafana_folder modules (#147)" -msgstr "grafana_teams モジュールãŠã‚ˆã³ grafana_folder モジュールã«ã€Œskip_version_checkã€ãƒ‘ラメーターãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸ(#147)" - -#: ../../rst/porting_guides/porting_guide_3.rst:141 -#: ../../rst/porting_guides/porting_guide_4.rst:542 -msgid "mysql_replication - the mode options values ``getslave``, ``startslave``, ``stopslave``, ``resetslave``, ``resetslaveall` and the master_use_gtid option ``slave_pos`` are deprecated (see the alternative values) and will be removed in ``community.mysql`` 3.0.0 (https://github.com/ansible-collections/community.mysql/pull/97)." -msgstr "mysql_replication - モードオプションã®å€¤ ``getslave``ã€``startslave``ã€``stopslave``ã€``resetslave``ã€`resetslaveall`ã€ãŠã‚ˆã³ master_use_gtid オプション ``slave_pos`` ã¯éžæŽ¨å¥¨ã¨ãªã‚Šï¼ˆåˆ¥ã®å€¤ã‚’å‚照）ã€``community.mysql`` 3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆåˆ¥ã®å€¤ã‚’å‚照）（https://github.com/ansible-collections/community.mysql/pull/97)）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:142 -#: ../../rst/porting_guides/porting_guide_4.rst:544 -msgid "mysql_replication - the word ``SLAVE`` in messages returned by the module will be changed to ``REPLICA`` in ``community.mysql`` 2.0.0 (https://github.com/ansible-collections/community.mysql/issues/98)." -msgstr "mysql_replication - モジュールã«ã‚ˆã£ã¦è¿”ã•ã‚ŒãŸãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã® ``SLAVE`` ã¨ã„ã†å˜èªžã¯ ``community.mysql`` 2.0.0 ã§ã¯ ``REPLICA`` ã«å¤‰æ›´ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.mysql/issues/98）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:150 -#: ../../rst/porting_guides/porting_guide_4.rst:695 -msgid "Removed TMOS v11 support for bigip_gtm_pool and bigip_gtm_wide_ip modules" -msgstr "bigip_gtm_pool ãŠã‚ˆã³ bigip_gtm_wide_ip モジュール㮠TMOS v11 サãƒãƒ¼ãƒˆã‚’削除" - -#: ../../rst/porting_guides/porting_guide_3.rst:151 -#: ../../rst/porting_guides/porting_guide_4.rst:696 -msgid "Removed quorum and monitor_type parameters in bigip_node module. See porting guides section at https://clouddocs.f5.com/products/orchestration/ansible/devel/usage/porting-guides.html" -msgstr "bigip_node モジュール㧠quorum ãŠã‚ˆã³ monitor_type パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚移æ¤ã‚¬ã‚¤ãƒ‰ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ï¼ˆhttps://clouddocs.f5.com/products/orchestration/ansible/devel/usage/porting-guides.html）をå‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_3.rst:152 -#: ../../rst/porting_guides/porting_guide_4.rst:697 -msgid "Removed syslog_settings and pool_settings parameters in bigip_log_destination moduke. See porting guides section at https://clouddocs.f5.com/products/orchestration/ansible/devel/usage/porting-guides.html" -msgstr "bigip_log_destination モジュール㧠syslog_settings パラメーターãŠã‚ˆã³ pool_settings パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚移æ¤ã‚¬ã‚¤ãƒ‰ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ï¼ˆhttps://clouddocs.f5.com/products/orchestration/ansible/devel/usage/porting-guides.html）をå‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_3.rst:158 -#: ../../rst/porting_guides/porting_guide_3.rst:220 -#: ../../rst/porting_guides/porting_guide_4.rst:325 -#: ../../rst/porting_guides/porting_guide_4.rst:730 -msgid "cloudscale_ch.cloud" -msgstr "cloudscale_ch.cloud" - -#: ../../rst/porting_guides/porting_guide_3.rst:160 -#: ../../rst/porting_guides/porting_guide_4.rst:732 -msgid "The aliases ``server_uuids`` and ``server_uuid`` of the servers parameter in the volume module will be removed in version 3.0.0." -msgstr "ボリュームモジュール㮠server パラメーターã®ã‚¨ã‚¤ãƒªã‚¢ã‚¹ ``server_uuids`` ãŠã‚ˆã³ ``server_uuid`` ã¯ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:165 -#: ../../rst/porting_guides/porting_guide_4.rst:737 -msgid "ec2_eip - formally deprecate the ``instance_id`` alias for ``device_id`` (https://github.com/ansible-collections/community.aws/pull/349)." -msgstr "ec2_eip - ``device_id`` ã® ``instance_id`` エイリアスをæ£å¼ã«éžæŽ¨å¥¨åŒ–（https://github.com/ansible-collections/community.aws/pull/349）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:166 -#: ../../rst/porting_guides/porting_guide_4.rst:738 -msgid "ec2_vpc_endpoint - deprecate the policy_file option and recommend using policy with a lookup (https://github.com/ansible-collections/community.aws/pull/366)." -msgstr "ec2_vpc_endpoint - policy_file オプションをéžæŽ¨å¥¨ã«ã—ã€ãƒ«ãƒƒã‚¯ã‚¢ãƒƒãƒ—ã§ã®ãƒãƒªã‚·ãƒ¼ã®ä½¿ç”¨ã‚’推奨ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.aws/pull/366）" - -#: ../../rst/porting_guides/porting_guide_3.rst:171 -#: ../../rst/porting_guides/porting_guide_4.rst:745 -msgid "acme_account_info - when ``retrieve_orders=url_list``, ``orders`` will no longer be returned in community.crypto 2.0.0. Use ``order_uris`` instead (https://github.com/ansible-collections/community.crypto/pull/178)." -msgstr "acme_account_info - ``retrieve_orders=url_list`` ã®å ´åˆã€``orders`` 㯠community.crypto 2.0.0 ã§è¿”ã•ã‚Œãªããªã‚Šã¾ã™ã€‚代ã‚ã‚Šã« ``order_uris`` を使用ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.crypto/pull/178）" - -#: ../../rst/porting_guides/porting_guide_3.rst:176 -#: ../../rst/porting_guides/porting_guide_4.rst:750 -msgid "apt_rpm - deprecated invalid parameter alias ``update-cache``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." -msgstr "apt_rpm - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-cache`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:177 -#: ../../rst/porting_guides/porting_guide_4.rst:751 -msgid "composer - deprecated invalid parameter aliases ``working-dir``, ``global-command``, ``prefer-source``, ``prefer-dist``, ``no-dev``, ``no-scripts``, ``no-plugins``, ``optimize-autoloader``, ``classmap-authoritative``, ``apcu-autoloader``, ``ignore-platform-reqs``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." -msgstr "composer - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``working-dir``ã€``global-command``ã€``prefer-source``ã€``prefer-dist``ã€``no-dev``ã€``no-scripts``ã€``no-plugins``ã€``optimize-autoloader``ã€``classmap-authoritative``ã€``apcu-autoloader``ã€``ignore-platform-reqs`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927。" - -#: ../../rst/porting_guides/porting_guide_3.rst:178 -#: ../../rst/porting_guides/porting_guide_4.rst:753 -msgid "github_deploy_key - deprecated invalid parameter alias ``2fa_token``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." -msgstr "github_deploy_key - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``2fa_token`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）" - -#: ../../rst/porting_guides/porting_guide_3.rst:179 -#: ../../rst/porting_guides/porting_guide_4.rst:754 -msgid "grove - the option ``message`` will be removed in community.general 4.0.0. Use the new option ``message_content`` instead (https://github.com/ansible-collections/community.general/pull/1929)." -msgstr "grove - オプション ``message`` 㯠community.general 4.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã«ã€æ–°ã—ã„オプション ``message_content`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1929）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:180 -#: ../../rst/porting_guides/porting_guide_4.rst:755 -msgid "homebrew - deprecated invalid parameter alias ``update-brew``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." -msgstr "homebrew - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-brew`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）" - -#: ../../rst/porting_guides/porting_guide_3.rst:181 -#: ../../rst/porting_guides/porting_guide_4.rst:756 -msgid "homebrew_cask - deprecated invalid parameter alias ``update-brew``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." -msgstr "homebrew_cask - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-brew`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:182 -#: ../../rst/porting_guides/porting_guide_4.rst:757 -msgid "opkg - deprecated invalid parameter alias ``update-cache``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." -msgstr "opkg - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-cache`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:183 -#: ../../rst/porting_guides/porting_guide_4.rst:758 -msgid "pacman - deprecated invalid parameter alias ``update-cache``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." -msgstr "pacman - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-cache`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:184 -#: ../../rst/porting_guides/porting_guide_4.rst:759 -msgid "puppet - deprecated undocumented parameter ``show_diff``, will be removed in 7.0.0. (https://github.com/ansible-collections/community.general/pull/1927)." -msgstr "puppet - ドã‚ュメント化ã•ã‚Œã¦ã„ãªã„éžæŽ¨å¥¨ã®ãƒ‘ラメーター ``show_diff`` ㌠7.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:185 -#: ../../rst/porting_guides/porting_guide_4.rst:760 -msgid "runit - unused parameter ``dist`` marked for deprecation (https://github.com/ansible-collections/community.general/pull/1830)." -msgstr "runit - 未使用ã®ãƒ‘ラメーター ``dist`` ã¯éžæŽ¨å¥¨ã¨ç¤ºã•ã‚Œã¦ã„ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1830）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:186 -#: ../../rst/porting_guides/porting_guide_4.rst:761 -msgid "slackpkg - deprecated invalid parameter alias ``update-cache``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." -msgstr "slackpkg - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-cache`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:187 -#: ../../rst/porting_guides/porting_guide_4.rst:762 -msgid "urmpi - deprecated invalid parameter aliases ``update-cache`` and ``no-recommends``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." -msgstr "urmpi - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-cache`` ãŠã‚ˆã³ ``no-recommends`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:188 -#: ../../rst/porting_guides/porting_guide_4.rst:763 -msgid "xbps - deprecated invalid parameter alias ``update-cache``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." -msgstr "xbps - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-cache`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:189 -#: ../../rst/porting_guides/porting_guide_4.rst:764 -msgid "xfconf - returning output as facts is deprecated, this will be removed in community.general 4.0.0. Please register the task output in a variable and use it instead. You can already switch to the new behavior now by using the new ``disable_facts`` option (https://github.com/ansible-collections/community.general/pull/1747)." -msgstr "xfconf - 出力をファクトã¨ã—ã¦è¿”ã™ã®ã¯éžæŽ¨å¥¨ã§ã™ã€‚ã“れ㯠community.general 4.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚タスクã®å‡ºåŠ›ã‚’変数ã«ç™»éŒ²ã—ã¦ä»£ã‚ã‚Šã«ä½¿ç”¨ã—ã¦ãã ã•ã„。新ã—ã„``disable_facts`` オプション使用ã™ã‚‹ã¨æ–°ã—ã„挙動ã«åˆ‡ã‚Šæ›¿ãˆã‚‹ã“ã¨ãŒã§ãã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1747。" - -#: ../../rst/porting_guides/porting_guide_3.rst:192 -msgid "Porting Guide for v3.0.0" -msgstr "v3.0.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_3.rst:200 -msgid "Issue 1(186024): ome_smart_fabric_uplink module does not allow the creation of multiple uplinks of the same name even though this is supported by OpenManage Enterprise Modular. If an uplink is created using the same name as an existing uplink, the existing uplink is modified." -msgstr "Issue 1(186024): ome_smart_fabric_uplink モジュールã§ã¯ã€OpenManage Enterprise Modular ã§ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã¦ã‚‚ã€åŒã˜åå‰ã®è¤‡æ•°ã®ã‚¢ãƒƒãƒ—リンクã®ä½œæˆã¯ã§ãã¾ã›ã‚“。アップリンクãŒæ—¢å˜ã®ã‚¢ãƒƒãƒ—リンクã¨åŒã˜åå‰ã‚’使用ã—ã¦ä½œæˆã•ã‚Œã‚‹ã¨ã€æ—¢å˜ã®ã‚¢ãƒƒãƒ—ãŒå¤‰æ›´ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:201 -msgid "Issue 2(187956): If an invalid job_id is provided, idrac_lifecycle_controller_job_status_info returns an error message. This error message does not contain information about the exact issue with the invalid job_id." -msgstr "Issue 2(187956): 無効ãªjob_idãŒæä¾›ã•ã‚ŒãŸå ´åˆã€idrac_lifecycle_controller_job_status_infoã¯ã‚¨ãƒ©ãƒ¼ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã‚’è¿”ã—ã¾ã™ã€‚ã“ã®ã‚¨ãƒ©ãƒ¼ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã«ã¯ã€ç„¡åŠ¹ãªjob_idã«é–¢ã™ã‚‹æ£ç¢ºãªå•é¡Œã«ã¤ã„ã¦ã®æƒ…å ±ãŒå«ã¾ã‚Œã¦ã„ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_3.rst:202 -msgid "Issue 3(188267): While updating the iDRAC firmware, the idrac_firmware module completes execution before the firmware update job is completed. An incorrect message is displayed in the task output as 'DRAC WSMAN endpoint returned HTTP code '400' Reason 'Bad Request''. This issue may occur if the target iDRAC firmware version is less than 3.30.30.30" -msgstr "Issue 3(188267): iDRACファームウェアã®æ›´æ–°ä¸ã«ã€idrac_firmwareモジュールã¯ã€ãƒ•ã‚¡ãƒ¼ãƒ ウェア更新ジョブãŒå®Œäº†ã™ã‚‹å‰ã«å®Ÿè¡Œã‚’完了ã—ã¾ã™ã€‚タスク出力ã«èª¤ã£ãŸãƒ¡ãƒƒã‚»ãƒ¼ã‚¸'DRAC WSMAN endpoint returned HTTP code '400' Reason 'Bad Request''ãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚ã“ã®å•é¡Œã¯ã€ã‚¿ãƒ¼ã‚²ãƒƒãƒˆiDRACファームウェアãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒ3.30.30.30未満ã®å ´åˆã«ç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™" - -#: ../../rst/porting_guides/porting_guide_3.rst:213 -msgid "ansible.utils" -msgstr "ansible.utils" - -#: ../../rst/porting_guides/porting_guide_3.rst:215 -msgid "If added custom sub plugins in your collection move from old location `plugins/<sub-plugin-name>` to the new location `plugins/sub_plugins/<sub-plugin-name>` and update the imports as required" -msgstr "コレクションã«ã‚«ã‚¹ã‚¿ãƒ ã‚µãƒ–ãƒ—ãƒ©ã‚°ã‚¤ãƒ³ã‚’è¿½åŠ ã—ãŸå ´åˆã€ä»¥å‰ã®å ´æ‰€ `plugins/<sub-plugin-name>` ã‹ã‚‰æ–°ã—ã„å ´æ‰€ `plugins/sub_plugins/<sub-plugin-name>` ã«ç§»å‹•ã—ã€å¿…è¦ã«å¿œã˜ã¦ã‚¤ãƒ³ãƒãƒ¼ãƒˆã‚’æ›´æ–°ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:216 -msgid "Move sub plugins cli_parsers, fact_diff and validate to `plugins/sub_plugins` folder" -msgstr "サブプラグイン cli_parsersã€fact_diffã€ãŠã‚ˆã³ validate ã‚’ `plugins/sub_plugins` ディレクトリーã«ç§»å‹•ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:217 -msgid "The `cli_parsers` sub plugins folder name is changed to `cli_parse` to have consistent naming convention, that is all the cli_parse subplugins will now be in `plugins/sub_plugins/cli_parse` folder" -msgstr "`cli_parsers` サブプラグインã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼åãŒã€ä¸€è²«æ€§ã®ã‚る命åè¦å‰‡ã‚’æŒã¤ã‚ˆã†ã« `cli_parse` ã«å¤‰æ›´ã«ãªã‚Šã€cli_parse サブプラグインã¯ã™ã¹ã¦ `plugins/sub_plugins/cli_parse` ディレクトリーã«ç½®ã‹ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:222 -msgid "floating_ip - ``name`` is required for assigning a new floating IP." -msgstr "floating_ip - æ–°ã—ã„ Floating IP アドレスã®å‰²ã‚Šå½“ã¦ã«ã¯ ``name`` ãŒå¿…è¦ã§ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:227 -msgid "If you use Ansible 2.9 and the Google cloud plugins or modules from this collection, community.general 2.0.0 results in errors when trying to use the Google cloud content by FQCN, like ``community.general.gce_img``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.google.gce_img`` for the previous example) and to make sure that you have ``community.google`` installed." -msgstr "Ansible 2.9 ã¨ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® Google Cloud プラグインã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 2.0.0 ã§ã¯ã€``community.general.gce_img`` ã®ã‚ˆã†ã« FQCN 㧠Google Cloud コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (å‰ã®ä¾‹ã§ã¯ ``community.google.gce_img``) を使用ã™ã‚‹ãŸã‚ã« Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã—ã€``community.google`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã‹ã©ã†ã‹ã‚’確èªã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:230 -msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install the ``community.google`` or ``google.cloud`` collections if you are using any of the Google cloud plugins or modules. While ansible-base 2.10 or newer can use the redirects that community.general 2.0.0 adds, the collection they point to (such as community.google) must be installed for them to work." -msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ãŸå ´åˆã€Google cloud プラグインã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.google`` コレクションã¾ãŸã¯ ``google.cloud`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.google ãªã©) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_3.rst:232 -msgid "If you use Ansible 2.9 and the Kubevirt plugins or modules from this collection, community.general 2.0.0 results in errors when trying to use the Kubevirt content by FQCN, like ``community.general.kubevirt_vm``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.kubevirt.kubevirt_vm`` for the previous example) and to make sure that you have ``community.kubevirt`` installed." -msgstr "Ansible 2.9 ã¨ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® Kubevirt プラグインã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 2.0.0 ã§ã¯ã€``community.general.kubevirt_vm`` ã®ã‚ˆã†ãª FQCN ã«ã‚ˆã‚‹ Kubevirt コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN を使用ã™ã‚‹ãŸã‚ã« Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (å‰è¿°ã®ä¾‹ã§ã¯ ``community.kubevirt.kubevirt_vm``)。ã¾ãŸã€``community.kubevirt`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_3.rst:235 -msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install the ``community.kubevirt`` collection if you are using any of the Kubevirt plugins or modules. While ansible-base 2.10 or newer can use the redirects that community.general 2.0.0 adds, the collection they point to (such as community.google) must be installed for them to work." -msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€Kubevirt プラグインã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.kubevirt`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.google ãªã©) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_3.rst:237 -msgid "If you use Ansible 2.9 and the ``docker`` plugins or modules from this collections, community.general 2.0.0 results in errors when trying to use the docker content by FQCN, like ``community.general.docker_container``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.docker.docker_container`` for the previous example) and to make sure that you have ``community.docker`` installed." -msgstr "Ansible 2.9 ã¨ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``docker`` プラグインやモジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 2.0.0 ã§ã¯ã€``community.general.docker_container`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ docker コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (å‰ã®ä¾‹ã§ã¯ ``community.docker.docker_container``) を使用ã—ã€``community.docker`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:240 -msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install ``community.docker`` if you are using any of the ``docker`` plugins or modules. While ansible-base 2.10 or newer can use the redirects that community.general 2.0.0 adds, the collection they point to (community.docker) must be installed for them to work." -msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ãŸå ´åˆã€``docker`` プラグインã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.docker`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.docker) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_3.rst:242 -msgid "If you use Ansible 2.9 and the ``hashi_vault`` lookup plugin from this collections, community.general 2.0.0 results in errors when trying to use the Hashi Vault content by FQCN, like ``community.general.hashi_vault``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your inventories, variable files, playbooks and roles manually to use the new FQCN (``community.hashi_vault.hashi_vault``) and to make sure that you have ``community.hashi_vault`` installed." -msgstr "Ansible 2.9 ã¨ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``hashi_vault`` lookup プラグインやモジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 2.0.0 ã§ã¯ã€``community.general.hashi_vault`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ Hashi Vault コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (``community.hashi_vault.hashi_vault``) を使用ã—ã€``community.hashi_vault`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã€å¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«ã€Playbookã€ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:245 -msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install ``community.hashi_vault`` if you are using the ``hashi_vault`` plugin. While ansible-base 2.10 or newer can use the redirects that community.general 2.0.0 adds, the collection they point to (community.hashi_vault) must be installed for them to work." -msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€``hashi_vault`` プラグインを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.hashi_vault`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.hashi_vault) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_3.rst:247 -msgid "If you use Ansible 2.9 and the ``hetzner`` modules from this collections, community.general 2.0.0 results in errors when trying to use the hetzner content by FQCN, like ``community.general.hetzner_firewall``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.hrobot.firewall`` for the previous example) and to make sure that you have ``community.hrobot`` installed." -msgstr "Ansible 2.9 ã¨ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``hetzner`` プラグインやモジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 2.0.0 ã§ã¯ã€``community.general.hetzner_firewall`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ hetzner コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (å‰ã®ä¾‹ã§ã¯ ``community.hrobot.firewall``) を使用ã—ã€``community.hrobot`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:250 -msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install ``community.hrobot`` if you are using any of the ``hetzner`` modules. While ansible-base 2.10 or newer can use the redirects that community.general 2.0.0 adds, the collection they point to (community.hrobot) must be installed for them to work." -msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ãŸå ´åˆã€``hetzner`` モジュールを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.hrobot`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.hrobot) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_3.rst:252 -msgid "If you use Ansible 2.9 and the ``oc`` connection plugin from this collections, community.general 2.0.0 results in errors when trying to use the oc content by FQCN, like ``community.general.oc``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your inventories, variable files, playbooks and roles manually to use the new FQCN (``community.okd.oc``) and to make sure that you have ``community.okd`` installed." -msgstr "Ansible 2.9 ã¨ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``oc`` connection プラグインやモジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 2.0.0 ã§ã¯ã€``community.general.oc`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ oc コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (``community.okd.oc``) を使用ã—ã€``community.okd`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã€å¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:255 -msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install ``community.okd`` if you are using the ``oc`` plugin. While ansible-base 2.10 or newer can use the redirects that community.general 2.0.0 adds, the collection they point to (community.okd) must be installed for them to work." -msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€``oc`` プラグインを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.okd`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.okd) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_3.rst:257 -msgid "If you use Ansible 2.9 and the ``postgresql`` modules from this collections, community.general 2.0.0 results in errors when trying to use the postgresql content by FQCN, like ``community.general.postgresql_info``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.postgresql.postgresql_info`` for the previous example) and to make sure that you have ``community.postgresql`` installed." -msgstr "Ansible 2.9 ã¨ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``postgresql`` プラグインやモジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 2.0.0 ã§ã¯ã€``community.general.postgresql_info`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ postgresql コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (å‰ã®ä¾‹ã§ã¯ ``community.postgresql.postgresql_info``) を使用ã—ã€``community.postgresql`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:260 -msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install ``community.postgresql`` if you are using any of the ``postgresql`` modules. While ansible-base 2.10 or newer can use the redirects that community.general 2.0.0 adds, the collection they point to (community.postgresql) must be installed for them to work." -msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€``postgresql`` モジュールを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.postgresql`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.postgresql) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_3.rst:262 -#: ../../rst/porting_guides/porting_guide_3.rst:493 -msgid "The Google cloud inventory script ``gce.py`` has been migrated to the ``community.google`` collection. Install the ``community.google`` collection in order to continue using it." -msgstr "Google クラウドインベントリースクリプト ``gce.py`` ã‚’ ``community.google`` コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚使用を継続ã™ã‚‹ã«ã¯ã€``community.google`` コレクションをインストールã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_3.rst:263 -msgid "archive - remove path folder itself when ``remove`` parameter is true (https://github.com/ansible-collections/community.general/issues/1041)." -msgstr "archive - ``remove`` パラメーター㌠true ã®å ´åˆã«ãƒ‘スフォルダー自体を削除ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/issues/1041）。" - -#: ../../rst/porting_guides/porting_guide_3.rst:265 -msgid "passwordstore lookup plugin - now parsing a password store entry as YAML if possible, skipping the first line (which by convention only contains the password and nothing else). If it cannot be parsed as YAML, the old ``key: value`` parser will be used to process the entry. Can break backwards compatibility if YAML formatted code was parsed in a non-YAML interpreted way, e.g. ``foo: [bar, baz]`` will become a list with two elements in the new version, but a string ``'[bar, baz]'`` in the old (https://github.com/ansible-collections/community.general/issues/1673)." -msgstr "passwordstore lookup プラグイン - パスワードストアã®ã‚¨ãƒ³ãƒˆãƒªãƒ¼ã‚’å¯èƒ½ãªé™ã‚Š YAML ã¨ã—ã¦è§£æžã™ã‚‹ã‚ˆã†ã«ãªã‚Šã€æœ€åˆã®è¡Œ (慣例ã§ã¯ãƒ‘スワードã®ã¿ã‚’å«ã¿ã€ä»–ã«ã¯ä½•ã‚‚ãªã„) をスã‚ップã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚YAML ã¨ã—ã¦è§£æžã§ããªã„å ´åˆã¯ã€å¤ã„ ``key: value`` パーサーãŒã‚¨ãƒ³ãƒˆãƒªãƒ¼ã®å‡¦ç†ã«ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚YAML å½¢å¼ã®ã‚³ãƒ¼ãƒ‰ãŒ YAML ã§ã¯ãªã„解釈方法ã§è§£æžã•ã‚ŒãŸå ´åˆã¯ã€ä¸‹ä½äº’æ›æ€§ã‚’失ã†å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€``foo: [bar, baz]`` ã¯æ–°ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã¯ 2 ã¤ã®è¦ç´ ã‚’æŒã¤ãƒªã‚¹ãƒˆã«ãªã‚Šã¾ã™ãŒã€æ—§ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã¯æ–‡å—列 ``'[bar, baz]'`` ã«ãªã‚Šã¾ã™ (https://github.com/ansible-collections/community.general/issues/1673)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:268 -msgid "proxmox_kvm - recognize ``force=yes`` in conjunction with ``state=absent`` to forcibly remove a running VM (https://github.com/ansible-collections/community.general/pull/849)." -msgstr "proxmox_kvm - ``force=yes`` ã‚’ ``state=absent`` ã¨ä½µç”¨ã—ã¦ã€å®Ÿè¡Œä¸ã®ä»®æƒ³ãƒžã‚·ãƒ³ã‚’強制的ã«å‰Šé™¤ã—ã¾ã™ (https://github.com/ansible-collections/community.general/pull/849)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:284 -msgid "If you use Ansible 2.9 and the FortiOS modules from this collection, community.network 2.0.0 results in errors when trying to use the FortiOS content by FQCN, like ``community.network.fmgr_device``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.fortios.fmgr_device`` for the previous example) and to make sure that you have ``community.fortios`` installed." -msgstr "ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® Ansible 2.9 㨠FortiOS モジュールを使用ã™ã‚‹å ´åˆã¯ã€community.network 2.0.0 を使用ã™ã‚‹ã¨ã€FQCN 㧠``community.network.fmgr_device`` ã®ã‚ˆã†ãª FortiOS コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã€ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã—ã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN を使用ã—ã€``community.fortios`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã®ã‚’確èªã™ã‚‹ã«ã¯ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (å‰ã®ä¾‹ã® ``community.fortios.fmgr_device``)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:287 -msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.network manually, you need to make sure to also install ``community.fortios`` if you are using any of the FortiOS modules. While ansible-base 2.10 or newer can use the redirects that community.network 2.0.0 adds, the collection they point to (community.fortios) must be installed for them to work." -msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.network をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ãŸå ´åˆã€FortiOS モジュールを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.fortios`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.network 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.fortios) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_3.rst:289 -msgid "If you use Ansible 2.9 and the ``cp_publish`` module from this collection, community.network 2.0.0 results in errors when trying to use the module by FQCN, i.e. ``community.network.cp_publish``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``check_point.mgmt.cp_mgmt_publish``) and to make sure that you have ``check_point.mgmt`` installed. If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.network manually, you need to make sure to also install ``check_point.mgmt`` if you are using the ``cp_publish`` module. While ansible-base 2.10 or newer can use the redirects that community.network 2.0.0 adds, the collection they point to (check_point.mgmt) must be installed for them to work." -msgstr "Ansible 2.9 ã¨ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``cp_publish`` モジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.network 2.0.0 ã§ã¯ã€FQCN ã§ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã—ã¾ã™ (``community.network.cp_publish``)。Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (``check_point.mgmt.cp_mgmt_publish``) を使用ã—ã€``check_point.mgmt`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€community.network を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ« (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€``cp_publish`` モジュールを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``check_point.mgmt`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ community.network 2.0.0 ãŒè¿½åŠ ã™ã‚‹ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (check_point.mgmt) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_3.rst:291 -msgid "If you use Ansible 2.9 and the ``fortimanager`` httpapi plugin from this collection, community.network 2.0.0 results in errors when trying to use it by FQCN (``community.network.fortimanager``). Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCN ``fortinet.fortimanager.fortimanager`` and to make sure that you have ``fortinet.fortimanager`` installed." -msgstr "Ansible 2.9 ã¨ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``fortimanager`` httpapi プラグインを使用ã—ã¦ã„ã‚‹å ´åˆã€community.network 2.0.0 ã§ã¯ã€FQCN (``community.network.fortimanager``) ã§ä½¿ç”¨ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN ``fortinet.fortimanager.fortimanager`` を使用ã—ã€``fortinet.fortimanager`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:294 -msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.network manually, you need to make sure to also install ``fortinet.fortimanager`` if you are using the ``fortimanager`` httpapi plugin. While ansible-base 2.10 or newer can use the redirect that community.network 2.0.0 adds, the collection they point to (fortinet.fortimanager) must be installed for it to work." -msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.network をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€``fortimanager`` httpapi プラグインを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``fortinet.fortimanager`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.network 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (fortinet.fortimanager) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_3.rst:296 -msgid "If you use Ansible 2.9 and the ``nso`` modules from this collection, community.network 2.0.0 results in errors when trying to use the nso content by FQCN, like ``community.network.nso_config``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``cisco.nso.nso_config`` for the previous example) and to make sure that you have ``cisco.nso`` installed." -msgstr "Ansible 2.9 ã¨ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``nso`` モジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.network 2.0.0 ã§ã¯ã€``community.network.nso_config`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ nso コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (å‰ã®ä¾‹ã§ã¯``cisco.nso.nso_config``) を使用ã—ã€``cisco.nso`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ã«ã¯ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:299 -msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.network manually, you need to make sure to also install ``cisco.nso`` if you are using any of the ``nso`` modules. While ansible-base 2.10 or newer can use the redirects that community.network 2.0.0 adds, the collection they point to (cisco.nso) must be installed for them to work." -msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.network をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€``nso`` モジュールを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``cisco.nso`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.network 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (cisco.nso) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_3.rst:301 -msgid "If you use Ansible 2.9 and the ``routeros`` plugins or modules from this collections, community.network 2.0.0 results in errors when trying to use the routeros content by FQCN, like ``community.network.routeros_command``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.routeros.command`` for the previous example) and to make sure that you have ``community.routeros`` installed." -msgstr "Ansible 2.9 ã¨ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``routeros`` プラグインやモジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.network 2.0.0 ã§ã¯ã€``community.network.routeros_command`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ routeros コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (å‰ã®ä¾‹ã§ã¯ ``community.routeros.command``) を使用ã—ã€``community.routeros`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:304 -msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.network manually, you need to make sure to also install ``community.routeros`` if you are using any of the ``routeros`` plugins or modules. While ansible-base 2.10 or newer can use the redirects that community.network 2.0.0 adds, the collection they point to (community.routeros) must be installed for them to work." -msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.network をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€``routeros`` プラグインã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.routeros`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.network 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.routeros) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_3.rst:306 -msgid "cnos_static_route - move ipaddress import from ansible.netcommon to builtin or package before ipaddress is removed from ansible.netcommon. You need to make sure to have the ipaddress package installed if you are using this module on Python 2.7 (https://github.com/ansible-collections/community.network/pull/129)." -msgstr "cnos_static_route - ansible.netcommon ã‹ã‚‰ ipaddress ãŒå‰Šé™¤ã•ã‚Œã‚‹å‰ã«ã€ansible.netcommon ã‹ã‚‰ ipaddress ã®ã‚¤ãƒ³ãƒãƒ¼ãƒˆã‚’ビルドインã¾ãŸã¯ãƒ‘ッケージã«ç§»å‹•ã—ã¾ã™ã€‚ã“ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’ Python 2.7 ã§ä½¿ã†å ´åˆã¯ã€ipaddress パッケージãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (https://github.com/ansible-collections/community.network/pull/129)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:311 -msgid "os10_bgp - Changed \"subnet\" key as list format instead of dictionary format under \"listen\" key to support multiple neighbor prefix for listen command" -msgstr "os10_bgp - listen コマンドã®è¤‡æ•°ã® neighbor 接é 辞をサãƒãƒ¼ãƒˆã™ã‚‹ãŸã‚ã«ã€ã€Œlistenã€ã‚ーã®ã€Œsubnetã€ã‚ーをã€ãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼å½¢å¼ã‹ã‚‰ãƒªã‚¹ãƒˆå½¢å¼ã«å¤‰æ›´ã—ã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:312 -msgid "os10_bgp - Changed \"vrf\" key as list format instead of dictionary format to supprot multiple VRF in router BGP and changed the \"vrf\" key name to \"vrfs\"" -msgstr "os10_bgp - ルーター BGP ã§è¤‡æ•°ã® VRF をサãƒãƒ¼ãƒˆã™ã‚‹ãŸã‚ã«ã€ã€Œvrfã€ã‚ーをディクショナリー形å¼ã§ã¯ãªãリスト形å¼ã«å¤‰æ›´ã—ã€ã€Œvrfã€ã‚ーã®åå‰ã‚’「vrfsã€ã«å¤‰æ›´ã—ã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:315 -msgid "ngine_io.cloudstack" -msgstr "ngine_io.cloudstack" - -#: ../../rst/porting_guides/porting_guide_3.rst:317 -msgid "Authentication option using INI files e.g. ``cloudstack.ini`` has been removed. The only supported option to authenticate is by using the module params with fallback to the ENV variables." -msgstr "INI ファイル (例: ``cloudstack.ini``) を使用ã—ãŸèªè¨¼ã‚ªãƒ—ションã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ç¾åœ¨ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã‚‹èªè¨¼æ–¹æ³•ã¯ã€ENV 変数ã«ãƒ•ã‚©ãƒ¼ãƒ«ãƒãƒƒã‚¯ã—ã¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ‘ラメーターを使用ã™ã‚‹æ–¹æ³•ã®ã¿ã§ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:318 -msgid "default zone deprecation - The `zone` param default value, across multiple modules, has been deprecated due to unreliable API (https://github.com/ngine-io/ansible-collection-cloudstack/pull/62)." -msgstr "デフォルトゾーンãŒéžæŽ¨å¥¨ã«ãªã‚‹ - API ã®ä¿¡é ¼æ€§ãŒä½Žã„ãŸã‚ã€è¤‡æ•°ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«é–“㧠`zone` パラメーターã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ãŒéžæŽ¨å¥¨ã«ãªã‚Šã¾ã—㟠(https://github.com/ngine-io/ansible-collection-cloudstack/pull/62)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:324 -msgid "cisco.aci" -msgstr "cisco.aci" - -#: ../../rst/porting_guides/porting_guide_3.rst:326 -msgid "Change certificate_name to name in aci_aaa_user_certificate module for query operation" -msgstr "クエリーæ“作㮠certificate_name ã®åå‰ã‚’ aci_aaa_user_certificate モジュールã®åå‰ã«å¤‰æ›´ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:331 -msgid "For community.general 3.0.0, the ``ome_device_info``, ``idrac_firmware`` and ``idrac_server_config_profile`` modules will be moved to the `dellemc.openmanage <https://galaxy.ansible.com/dellemc/openmanage>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." -msgstr "community.general 3.0.0 ã®å ´åˆã€``ome_device_info`` モジュールã€``idrac_firmware`` モジュールã€ãŠã‚ˆã³ ``idrac_server_config_profile`` モジュール㯠`dellemc.openmanage <https://galaxy.ansible.com/dellemc/openmanage>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:334 -msgid "If you use Ansible 2.9 and explicitly use the DellEMC modules mentioned above from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``dellemc.openmanage.`` instead of ``community.general.``, for example replace ``community.general.ome_device_info`` in a task by ``dellemc.openmanage.ome_device_info``." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ä¸Šè¨˜ã® DellEMC モジュールを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.general.`` ã§ã¯ãªã ``dellemc.openmanage.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``dellemc.openmanage.ome_device_info`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.general.ome_device_info`` ã‚’ç½®ãæ›ãˆã¾ã™)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:337 -msgid "If you use ansible-base and installed ``community.general`` manually and rely on the DellEMC modules mentioned above, you have to make sure to install the ``dellemc.openmanage`` collection as well. If you are using FQCNs, for example ``community.general.ome_device_info`` instead of ``ome_device_info``, it will continue working, but we still recommend to adjust the FQCNs as well." -msgstr "ansible-base を使用ã—㦠``community.general`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€ä¸Šè¨˜ã® DellEMC モジュールã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``dellemc.openmanage`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ãŸã¨ãˆã° ``ome_device_info`` ã®ä»£ã‚ã‚Šã« ``community.general.ome_device_info`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:339 -msgid "The community.general collection no longer depends on the ansible.netcommon collection (https://github.com/ansible-collections/community.general/pull/1561)." -msgstr "community.general コレクションã¯ã€ansible.netcommon コレクションã«ä¾å˜ã—ãªããªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/1561)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:362 -msgid "Removed the existing deprecated modules." -msgstr "æ—¢å˜ã®éžæŽ¨å¥¨ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’削除。" - -#: ../../rst/porting_guides/porting_guide_3.rst:363 -msgid "Standardization of ten iDRAC ansible modules based on ansible guidelines." -msgstr "Ansible ガイドラインã«åŸºã¥ã 10 個㮠iDRAC Ansible モジュールã®æ¨™æº–化。" - -#: ../../rst/porting_guides/porting_guide_3.rst:364 -msgid "Support for OpenManage Enterprise Modular." -msgstr "OpenManage Enterprise Modular ã®ã‚µãƒãƒ¼ãƒˆã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:369 -msgid "os10_bgp - Enhanced router bgp keyword support for non-default vrf which are supported for default vrf and additional keyword to support both default and non-default vrf" -msgstr "os10_bgp - デフォルト vrf ã«å¯¾å¿œã—ã¦ã„ã‚‹éžãƒ‡ãƒ•ã‚©ãƒ«ãƒˆ vrf 用ã®ãƒ«ãƒ¼ã‚¿ãƒ¼ bgp ã‚ーワードã®ã‚µãƒãƒ¼ãƒˆã‚’強化ã—ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãŠã‚ˆã³éžãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã® vrf ã®ä¸¡æ–¹ã«å¯¾å¿œã™ã‚‹ãŸã‚ã®è¿½åŠ ã‚ãƒ¼ãƒ¯ãƒ¼ãƒ‰ã‚’è¿½åŠ ã—ã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:370 -msgid "os10_snmp role - Added support for snmp V3 features in community, group, host, engineID" -msgstr "os10_snmp role - コミュニティーã€ã‚°ãƒ«ãƒ¼ãƒ—ã€ãƒ›ã‚¹ãƒˆã€engineID ã«ãŠã‘ã‚‹ snmp V3 機能ã®ã‚µãƒãƒ¼ãƒˆã‚’è¿½åŠ ã—ã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:380 -msgid "kubernetes.core" -msgstr "kubernetes.core" - -#: ../../rst/porting_guides/porting_guide_3.rst:382 -msgid "Add changelog and fragments and document changelog process (https://github.com/ansible-collections/kubernetes.core/pull/131)." -msgstr "変更ãƒã‚°ãŠã‚ˆã³ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã‚’è¿½åŠ ã—ã€å¤‰æ›´ãƒã‚°ãƒ—ãƒã‚»ã‚¹ã‚’文書化ã—ã¾ã™ (https://github.com/ansible-collections/kubernetes.core/pull/131)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:383 -msgid "helm - New module for managing Helm charts (https://github.com/ansible-collections/kubernetes.core/pull/61)." -msgstr "helm - Helm ãƒãƒ£ãƒ¼ãƒˆç®¡ç†ç”¨ã®æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/kubernetes.core/pull/61)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:384 -msgid "helm_info - New module for retrieving Helm chart information (https://github.com/ansible-collections/kubernetes.core/pull/61)." -msgstr "helm_info - Helm ãƒãƒ£ãƒ¼ãƒˆæƒ…å ±ã‚’å–å¾—ã™ã‚‹æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/kubernetes.core/pull/61)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:385 -msgid "helm_plugin - new module to manage Helm plugins (https://github.com/ansible-collections/kubernetes.core/pull/154)." -msgstr "helm_plugin - Helm プラグインを管ç†ã™ã‚‹æ–°ã—ã„モジュール (https://github.com/ansible-collections/kubernetes.core/pull/154)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:386 -msgid "helm_plugin_info - new modules to gather information about Helm plugins (https://github.com/ansible-collections/kubernetes.core/pull/154)." -msgstr "helm_plugin_info - Helm プラグインã«é–¢ã™ã‚‹æƒ…å ±ã‚’åŽé›†ã™ã‚‹æ–°ã—ã„モジュール (https://github.com/ansible-collections/kubernetes.core/pull/154)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:387 -msgid "helm_repository - New module for managing Helm repositories (https://github.com/ansible-collections/kubernetes.core/pull/61)." -msgstr "helm_repository - Helm リãƒã‚¸ãƒˆãƒªãƒ¼ã‚’管ç†ã™ã‚‹ãŸã‚ã®æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/kubernetes.core/pull/61)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:388 -msgid "k8s - Add support for template parameter (https://github.com/ansible-collections/kubernetes.core/pull/230)." -msgstr "k8s - テンプレートパラメーターã®ã‚µãƒãƒ¼ãƒˆã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/ansible-collections/kubernetes.core/pull/230)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:392 -msgid "k8s_* - Add support for vaulted kubeconfig and src (https://github.com/ansible-collections/kubernetes.core/pull/193)." -msgstr "k8s_* - Vault 済㿠kubeconfig ãŠã‚ˆã³ src ã®ã‚µãƒãƒ¼ãƒˆã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/ansible-collections/kubernetes.core/pull/193)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:395 -msgid "k8s_exec - New module for executing commands on pods via Kubernetes API (https://github.com/ansible-collections/kubernetes.core/pull/14)." -msgstr "k8s_exec - Kubernetes API を使用ã—㦠Pod ã§ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã™ã‚‹æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/kubernetes.core/pull/14)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:396 -msgid "k8s_exec - Return rc for the command executed (https://github.com/ansible-collections/kubernetes.core/pull/158)." -msgstr "k8s_exec - 実行ã—ãŸã‚³ãƒžãƒ³ãƒ‰ã® rc ã‚’è¿”ã—ã¾ã™ (https://github.com/ansible-collections/kubernetes.core/pull/158)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:398 -msgid "k8s_log - New module for retrieving pod logs (https://github.com/ansible-collections/kubernetes.core/pull/16)." -msgstr "k8s_log - Pod ãƒã‚°ã‚’å–å¾—ã™ã‚‹æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/kubernetes.core/pull/16)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:469 -msgid "All Google cloud modules and plugins have now been migrated away from this collection. They can be found in either the `community.google <https://galaxy.ansible.com/community/google>`_ or `google.cloud <https://galaxy.ansible.com/google/cloud>`_ collections. If you use ansible-base 2.10 or newer, redirections have been provided." -msgstr "Google クラウドモジュールãŠã‚ˆã³ãƒ—ラグインã¯ã™ã¹ã¦ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ç§»è¡Œã•ã‚Œã¾ã—ãŸã€‚ã“れら㯠`community.google <https://galaxy.ansible.com/community/google>`_ コレクションã¾ãŸã¯ `google.cloud <https://galaxy.ansible.com/google/cloud>`_ コレクションã«ã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¦ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:473 -msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.gce_img`` → ``community.google.gce_img``) and make sure to install the community.google or google.cloud collections as appropriate." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN を調整 (``community.general.gce_img`` →``community.google.gce_img``) ã—ã€å¿…è¦ã«å¿œã˜ã¦ community.google コレクションã¾ãŸã¯ google.cloud collections コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_3.rst:474 -msgid "All Kubevirt modules and plugins have now been migrated from community.general to the `community.kubevirt <https://galaxy.ansible.com/community/kubevirt>`_ Ansible collection. If you use ansible-base 2.10 or newer, redirections have been provided." -msgstr "ã™ã¹ã¦ã® Kubevirt モジュールãŠã‚ˆã³ãƒ—ラグインã¯ã€community.general ã‹ã‚‰ `community.kubevirt <https://galaxy.ansible.com/community/kubevirt>`_ Ansibleコレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:477 -msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.kubevirt_vm`` → ``community.kubevirt.kubevirt_vm``) and make sure to install the community.kubevirt collection." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.general.kubevirt_vm`` →``community.kubevirt.kubevirt_vm``) を調整ã—ã€community.kubevirt コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_3.rst:478 -msgid "All ``docker`` modules and plugins have been removed from this collection. They have been migrated to the `community.docker <https://galaxy.ansible.com/community/docker>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided." -msgstr "ã™ã¹ã¦ã® ``docker`` モジュールã¨ãƒ—ラグインãŒã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れら㯠`community.docker <https://galaxy.ansible.com/community/docker>`_ コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:482 -msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.docker_container`` → ``community.docker.docker_container``) and make sure to install the community.docker collection." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.general.docker_container`` →``community.docker.docker_container``) を調整ã—ã€community.docker コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_3.rst:483 -msgid "All ``hetzner`` modules have been removed from this collection. They have been migrated to the `community.hrobot <https://galaxy.ansible.com/community/hrobot>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided." -msgstr "ã™ã¹ã¦ã® ``hetzner`` モジュールãŒã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れら㯠`community.hrobot <https://galaxy.ansible.com/community/hrobot>`_ コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:487 -msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.hetzner_firewall`` → ``community.hrobot.firewall``) and make sure to install the community.hrobot collection." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.general.hetzner_firewall`` →``community.hrobot.firewall``) を調整ã—ã€community.hrobot コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_3.rst:488 -msgid "All ``postgresql`` modules have been removed from this collection. They have been migrated to the `community.postgresql <https://galaxy.ansible.com/community/postgresql>`_ collection." -msgstr "ã™ã¹ã¦ã® ``postgresql`` モジュールã¯ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れら㯠`community.postgresql <https://galaxy.ansible.com/community/postgresql>`_ コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:491 -msgid "If you use ansible-base 2.10 or newer, redirections have been provided. If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.postgresql_info`` → ``community.postgresql.postgresql_info``) and make sure to install the community.postgresql collection." -msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¦ã„ã¾ã™ã€‚Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.general.postgresql_info`` →``community.postgresql.postgresql_info``) を調整ã—ã€å¿…è¦ã«å¿œã˜ã¦ community.postgresql コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_3.rst:494 -msgid "The ``hashi_vault`` lookup plugin has been removed from this collection. It has been migrated to the `community.hashi_vault <https://galaxy.ansible.com/community/hashi_vault>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided." -msgstr "``hashi_vault`` lookup プラグインã¯ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れ㯠`community.hashi_vault <https://galaxy.ansible.com/community/hashi_vault>`_ コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¦ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:498 -msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.hashi_vault`` → ``community.hashi_vault.hashi_vault``) and make sure to install the community.hashi_vault collection." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.general.hashi_vault`` →``community.hashi_vault.hashi_vault``) を調整ã—ã€community.hashi_vault コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_3.rst:499 -msgid "The ``oc`` connection plugin has been removed from this collection. It has been migrated to the `community.okd <https://galaxy.ansible.com/community/okd>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided." -msgstr "``oc`` connection プラグインã¯ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れ㯠`community.okd <https://galaxy.ansible.com/community/okd>`_ コレクションã«ç§»è¡Œã•ã‚Œã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_3.rst:503 -msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.oc`` → ``community.okd.oc``) and make sure to install the community.okd collection." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.general.oc`` →``community.okd.oc``) を調整ã—ã€community.okd コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_3.rst:504 -msgid "The deprecated ``actionable`` callback plugin has been removed. Use the ``ansible.builtin.default`` callback plugin with ``display_skipped_hosts = no`` and ``display_ok_hosts = no`` options instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``actionable`` コールãƒãƒƒã‚¯ãƒ—ラグインãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã«ã€``ansible.builtin.default`` コールãƒãƒƒã‚¯ãƒ—ラグインを ``display_skipped_hosts = no`` オプションãŠã‚ˆã³ ``display_ok_hosts = no`` オプションã¨ä¸€ç·’ã«ä½¿ç”¨ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:505 -msgid "The deprecated ``foreman`` module has been removed. Use the modules from the theforeman.foreman collection instead (https://github.com/ansible-collections/community.general/pull/1347) (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``foreman`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« theforeman.foreman コレクションã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347) (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:506 -msgid "The deprecated ``full_skip`` callback plugin has been removed. Use the ``ansible.builtin.default`` callback plugin with ``display_skipped_hosts = no`` option instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``full_skip`` コールãƒãƒƒã‚¯ãƒ—ラグインãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã«ã€``ansible.builtin.default`` コールãƒãƒƒã‚¯ãƒ—ラグインを ``display_skipped_hosts = no`` オプションã¨ä¸€ç·’ã«ä½¿ç”¨ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:507 -msgid "The deprecated ``gcdns_record`` module has been removed. Use ``google.cloud.gcp_dns_resource_record_set`` instead (https://github.com/ansible-collections/community.general/pull/1370)." -msgstr "éžæŽ¨å¥¨ã® ``gcdns_record`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_dns_resource_record_set`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:508 -msgid "The deprecated ``gcdns_zone`` module has been removed. Use ``google.cloud.gcp_dns_managed_zone`` instead (https://github.com/ansible-collections/community.general/pull/1370)." -msgstr "éžæŽ¨å¥¨ã® ``gcdns_zone`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_dns_managed_zone`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:509 -msgid "The deprecated ``gce`` module has been removed. Use ``google.cloud.gcp_compute_instance`` instead (https://github.com/ansible-collections/community.general/pull/1370)." -msgstr "éžæŽ¨å¥¨ã® ``gce`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_compute_instance`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:510 -msgid "The deprecated ``gcp_backend_service`` module has been removed. Use ``google.cloud.gcp_compute_backend_service`` instead (https://github.com/ansible-collections/community.general/pull/1370)." -msgstr "éžæŽ¨å¥¨ã® ``gcp_backend_service`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_compute_backend_service`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:511 -msgid "The deprecated ``gcp_forwarding_rule`` module has been removed. Use ``google.cloud.gcp_compute_forwarding_rule`` or ``google.cloud.gcp_compute_global_forwarding_rule`` instead (https://github.com/ansible-collections/community.general/pull/1370)." -msgstr "éžæŽ¨å¥¨ã® ``gcp_forwarding_rule`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_compute_forwarding_rule`` ã¾ãŸã¯ ``google.cloud.gcp_compute_global_forwarding_rule`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:512 -msgid "The deprecated ``gcp_healthcheck`` module has been removed. Use ``google.cloud.gcp_compute_health_check``, ``google.cloud.gcp_compute_http_health_check`` or ``google.cloud.gcp_compute_https_health_check`` instead (https://github.com/ansible-collections/community.general/pull/1370)." -msgstr "éžæŽ¨å¥¨ã® ``gcp_healthcheck`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_compute_health_check``ã€``google.cloud.gcp_compute_http_health_check``ã€ã¾ãŸã¯ ``google.cloud.gcp_compute_https_health_check`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:513 -msgid "The deprecated ``gcp_target_proxy`` module has been removed. Use ``google.cloud.gcp_compute_target_http_proxy`` instead (https://github.com/ansible-collections/community.general/pull/1370)." -msgstr "éžæŽ¨å¥¨ã® ``gcp_target_proxy`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_compute_target_http_proxy`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:514 -msgid "The deprecated ``gcp_url_map`` module has been removed. Use ``google.cloud.gcp_compute_url_map`` instead (https://github.com/ansible-collections/community.general/pull/1370)." -msgstr "éžæŽ¨å¥¨ã® ``gcp_url_map`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_compute_url_map`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:515 -msgid "The deprecated ``gcspanner`` module has been removed. Use ``google.cloud.gcp_spanner_database`` and/or ``google.cloud.gcp_spanner_instance`` instead (https://github.com/ansible-collections/community.general/pull/1370)." -msgstr "éžæŽ¨å¥¨ã® ``gcspanner`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_spanner_database`` ã‚„ ``google.cloud.gcp_spanner_instance`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:516 -msgid "The deprecated ``github_hooks`` module has been removed. Use ``community.general.github_webhook`` and ``community.general.github_webhook_info`` instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``github_hooks`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``community.general.github_webhook`` ãŠã‚ˆã³ ``community.general.github_webhook_info`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:517 -msgid "The deprecated ``katello`` module has been removed. Use the modules from the theforeman.foreman collection instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``katello`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« theforeman.foreman コレクションã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:518 -msgid "The deprecated ``na_cdot_aggregate`` module has been removed. Use netapp.ontap.na_ontap_aggregate instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``na_cdot_aggregate`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_aggregate を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:519 -msgid "The deprecated ``na_cdot_license`` module has been removed. Use netapp.ontap.na_ontap_license instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``na_cdot_license`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_license を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:520 -msgid "The deprecated ``na_cdot_lun`` module has been removed. Use netapp.ontap.na_ontap_lun instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``na_cdot_lun`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_lun を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:521 -msgid "The deprecated ``na_cdot_qtree`` module has been removed. Use netapp.ontap.na_ontap_qtree instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``na_cdot_qtree`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_qtree を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:522 -msgid "The deprecated ``na_cdot_svm`` module has been removed. Use netapp.ontap.na_ontap_svm instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``na_cdot_svm`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_svm を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:523 -msgid "The deprecated ``na_cdot_user_role`` module has been removed. Use netapp.ontap.na_ontap_user_role instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``na_cdot_user_role`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_user_role を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:524 -msgid "The deprecated ``na_cdot_user`` module has been removed. Use netapp.ontap.na_ontap_user instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``na_cdot_user`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_user を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:525 -msgid "The deprecated ``na_cdot_volume`` module has been removed. Use netapp.ontap.na_ontap_volume instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``na_cdot_volume`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_volume を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:526 -msgid "The deprecated ``sf_account_manager`` module has been removed. Use netapp.elementsw.na_elementsw_account instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``sf_account_manager`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.elementsw.na_elementsw_account を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:527 -msgid "The deprecated ``sf_check_connections`` module has been removed. Use netapp.elementsw.na_elementsw_check_connections instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``sf_check_connections`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.elementsw.na_elementsw_check_connections を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:528 -msgid "The deprecated ``sf_snapshot_schedule_manager`` module has been removed. Use netapp.elementsw.na_elementsw_snapshot_schedule instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``sf_snapshot_schedule_manager`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.elementsw.na_elementsw_snapshot_schedule を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:529 -msgid "The deprecated ``sf_volume_access_group_manager`` module has been removed. Use netapp.elementsw.na_elementsw_access_group instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``sf_volume_access_group_manager`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.elementsw.na_elementsw_access_group を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:530 -msgid "The deprecated ``sf_volume_manager`` module has been removed. Use netapp.elementsw.na_elementsw_volume instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``sf_volume_manager`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.elementsw.na_elementsw_volume を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:531 -msgid "The deprecated ``stderr`` callback plugin has been removed. Use the ``ansible.builtin.default`` callback plugin with ``display_failed_stderr = yes`` option instead (https://github.com/ansible-collections/community.general/pull/1347)." -msgstr "éžæŽ¨å¥¨ã® ``stderr`` コールãƒãƒƒã‚¯ãƒ—ラグインãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã«ã€``ansible.builtin.default`` コールãƒãƒƒã‚¯ãƒ—ラグインを ``display_failed_stderr = yes`` オプションã¨ä¸€ç·’ã«ä½¿ç”¨ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:532 -msgid "The redirect of the ``conjur_variable`` lookup plugin to ``cyberark.conjur.conjur_variable`` collection was removed (https://github.com/ansible-collections/community.general/pull/1346)." -msgstr "``conjur_variable`` ルックアッププラグイン㮠``cyberark.conjur.conjur_variable`` コレクションã¸ã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒå‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/1346)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:533 -msgid "The redirect of the ``firewalld`` module and the ``firewalld`` module_utils to the ``ansible.posix`` collection was removed (https://github.com/ansible-collections/community.general/pull/1346)." -msgstr "``firewalld`` モジュールãŠã‚ˆã³ ``firewalld`` module_utils ã® ``ansible.posix`` コレクションã¸ã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒå‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/1346)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:534 -msgid "The redirect to the ``community.digitalocean`` collection was removed for: the ``digital_ocean`` doc fragment, the ``digital_ocean`` module_utils, and the following modules: ``digital_ocean``, ``digital_ocean_account_facts``, ``digital_ocean_account_info``, ``digital_ocean_block_storage``, ``digital_ocean_certificate``, ``digital_ocean_certificate_facts``, ``digital_ocean_certificate_info``, ``digital_ocean_domain``, ``digital_ocean_domain_facts``, ``digital_ocean_domain_info``, ``digital_ocean_droplet``, ``digital_ocean_firewall_facts``, ``digital_ocean_firewall_info``, ``digital_ocean_floating_ip``, ``digital_ocean_floating_ip_facts``, ``digital_ocean_floating_ip_info``, ``digital_ocean_image_facts``, ``digital_ocean_image_info``, ``digital_ocean_load_balancer_facts``, ``digital_ocean_load_balancer_info``, ``digital_ocean_region_facts``, ``digital_ocean_region_info``, ``digital_ocean_size_facts``, ``digital_ocean_size_info``, ``digital_ocean_snapshot_facts``, ``digital_ocean_snapshot_info``, ``digital_ocean_sshkey``, ``digital_ocean_sshkey_facts``, ``digital_ocean_sshkey_info``, ``digital_ocean_tag``, ``digital_ocean_tag_facts``, ``digital_ocean_tag_info``, ``digital_ocean_volume_facts``, ``digital_ocean_volume_info`` (https://github.com/ansible-collections/community.general/pull/1346)." -msgstr "``community.digitalocean`` コレクションã¸ã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒå‰Šé™¤ã•ã‚ŒãŸã®ã¯ã€``digital_ocean`` ドã‚ュメントã®ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã€``digital_ocean`` module_utilsã€ãŠã‚ˆã³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``digital_ocean``ã€``digital_ocean_account_facts``ã€``digital_ocean_account_info``ã€``digital_ocean_block_storage``ã€``digital_ocean_certificate``ã€``digital_ocean_certificate_facts``ã€``digital_ocean_certificate_info``ã€``digital_ocean_domain``ã€``digital_ocean_domain_facts``ã€``digital_ocean_domain_info``ã€``digital_ocean_droplet``ã€``digital_ocean_firewall_facts``ã€``digital_ocean_firewall_info``ã€``digital_ocean_floating_ip``ã€``digital_ocean_floating_ip_facts``ã€``digital_ocean_floating_ip_info``ã€``digital_ocean_image_facts``ã€``digital_ocean_image_info``ã€``digital_ocean_load_balancer_facts``ã€``digital_ocean_load_balancer_info``ã€``digital_ocean_region_facts``ã€``digital_ocean_region_info``ã€``digital_ocean_size_facts``ã€``digital_ocean_size_info``ã€``digital_ocean_snapshot_facts``ã€``digital_ocean_snapshot_info``ã€``digital_ocean_sshkey``ã€``digital_ocean_sshkey_facts``ã€``digital_ocean_sshkey_info``ã€``digital_ocean_tag``ã€``digital_ocean_tag_facts``ã€``digital_ocean_tag_info``ã€``digital_ocean_volume_facts``ã€``digital_ocean_volume_info`` ã§ã™ (https://github.com/ansible-collections/community.general/pull/1346)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:535 -msgid "The redirect to the ``community.mysql`` collection was removed for: the ``mysql`` doc fragment, the ``mysql`` module_utils, and the following modules: ``mysql_db``, ``mysql_info``, ``mysql_query``, ``mysql_replication``, ``mysql_user``, ``mysql_variables`` (https://github.com/ansible-collections/community.general/pull/1346)." -msgstr "``community.mysql`` コレクションã¸ã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒå‰Šé™¤ã•ã‚ŒãŸã®ã¯ã€``mysql`` ドã‚ュメントã®ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã€``mysql`` module_utilsã€ãŠã‚ˆã³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``mysql_db``ã€``mysql_info``ã€``mysql_query``ã€``mysql_replication``ã€``mysql_user``ã€``mysql_variables`` ã§ã™ (https://github.com/ansible-collections/community.general/pull/1346)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:536 -msgid "The redirect to the ``community.proxysql`` collection was removed for: the ``proxysql`` doc fragment, and the following modules: ``proxysql_backend_servers``, ``proxysql_global_variables``, ``proxysql_manage_config``, ``proxysql_mysql_users``, ``proxysql_query_rules``, ``proxysql_replication_hostgroups``, ``proxysql_scheduler`` (https://github.com/ansible-collections/community.general/pull/1346)." -msgstr "``proxysql`` doc フラグメントã¨ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``proxysql_backend_servers``ã€``proxysql_global_variables``ã€``proxysql_manage_config``ã€``proxysql_mysql_users``ã€``proxysql_query_rules``ã€``proxysql_replication_hostgroups``ã€ãŠã‚ˆã³ ``proxysql_scheduler`` ã§ã€``community.proxysql`` コレクションã¸ã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒå‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/1346)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:537 -msgid "The redirect to the ``infinidat.infinibox`` collection was removed for: the ``infinibox`` doc fragment, the ``infinibox`` module_utils, and the following modules: ``infini_export``, ``infini_export_client``, ``infini_fs``, ``infini_host``, ``infini_pool``, ``infini_vol`` (https://github.com/ansible-collections/community.general/pull/1346)." -msgstr "``infinidat.infinibox`` コレクションã¸ã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒå‰Šé™¤ã•ã‚ŒãŸã®ã¯ã€``infinibox`` ドã‚ュメントã®ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã€``infinibox`` module_utilsã€ãŠã‚ˆã³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``infini_export``ã€``infini_export_client``ã€``infini_fs``ã€``infini_host``ã€``infini_pool``ã€``infini_vol`` ã§ã™ (https://github.com/ansible-collections/community.general/pull/1346)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:541 -msgid "iptables_state - the ``ANSIBLE_ASYNC_DIR`` environment is no longer supported, use the ``async_dir`` shell option instead (https://github.com/ansible-collections/community.general/pull/1371)." -msgstr "iptables_state - ``ANSIBLE_ASYNC_DIR`` 環境ã¯ã‚µãƒãƒ¼ãƒˆå¯¾è±¡å¤–ã«ãªã£ãŸãŸã‚ã€ä»£ã‚ã‚Šã« ``async_dir`` シェルオプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1371)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:544 -msgid "memcached cache plugin - do not import ``CacheModule``s directly. Use ``ansible.plugins.loader.cache_loader`` instead (https://github.com/ansible-collections/community.general/pull/1371)." -msgstr "memcached cache プラグイン - ``CacheModule`` を直接インãƒãƒ¼ãƒˆã—ã¾ã›ã‚“。代ã‚ã‚Šã« ``ansible.plugins.loader.cache_loader`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.general/pull/1371)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:547 -msgid "redis cache plugin - do not import ``CacheModule``s directly. Use ``ansible.plugins.loader.cache_loader`` instead (https://github.com/ansible-collections/community.general/pull/1371)." -msgstr "redis cache プラグイン - ``CacheModule`` を直接インãƒãƒ¼ãƒˆã—ã¾ã›ã‚“。代ã‚ã‚Šã« ``ansible.plugins.loader.cache_loader`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1371)。" - -#: ../../rst/porting_guides/porting_guide_3.rst:548 -msgid "xml - when ``content=attribute``, the ``attribute`` option is ignored (https://github.com/ansible-collections/community.general/pull/1371)." -msgstr "XML - ``content=attribute`` ã®å ´åˆã€``attribute`` オプションãŒç„¡è¦–ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/1371)。" +#: ../../rst/porting_guides/porting_guide_4.rst:7 +msgid "Ansible 4 Porting Guide" +msgstr "Ansible 4 移æ¤ã‚¬ã‚¤ãƒ‰" -#: ../../rst/porting_guides/porting_guide_3.rst:553 -msgid "All FortiOS modules and plugins have been removed from this collection. They have been migrated to the `community.fortios <https://galaxy.ansible.com/community/fortios>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided." -msgstr "ã™ã¹ã¦ã® FortiOS モジュールã¨ãƒ—ラグインãŒã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れら㯠`community.fortios <https://galaxy.ansible.com/community/fortios>`_ コレクションã«ç§»è¡Œã•ã‚Œã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:6 +msgid "Ansible-base 2.10 Porting Guide" +msgstr "Ansible-base 2.10 移æ¤ã‚¬ã‚¤ãƒ‰" -#: ../../rst/porting_guides/porting_guide_3.rst:557 -msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.network.fmgr_device`` → ``community.fortios.fmgr_device``) and make sure to install the `community.fortios` collection." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.network.fmgr_device`` →``community.fortios.fmgr_device``) を調整ã—ã€`community.fortios` コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:10 +msgid "In preparation for the release of 2.10, many plugins and modules have migrated to Collections on `Ansible Galaxy <https://galaxy.ansible.com>`_. For the current development status of Collections and FAQ see `Ansible Collections Community Guide <https://github.com/ansible-collections/overview/blob/main/README.rst>`_. We expect the 2.10 Porting Guide to change frequently up to the 2.10 release. Follow the conversations about collections on our various :ref:`communication` channels for the latest information on the status of the ``devel`` branch." +msgstr "2.10 ã®ãƒªãƒªãƒ¼ã‚¹æº–å‚™ã®ãŸã‚ã«ã€å¤šãã®ãƒ—ラグインãŠã‚ˆã³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒ `Ansible Galaxy <https://galaxy.ansible.com>`_ ã® Collection ã«ç§»è¡Œã—ã¦ã„ã¾ã™ã€‚Collection ãŠã‚ˆã³ FAQ ã®ç¾åœ¨ã®é–‹ç™ºã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã¯ã€ã€Œ`Ansible Collections コミュニティーガイド <https://github.com/ansible-collections/overview/blob/main/README.rst>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。2.10 ã®ã€Œç§»æ¤ã‚¬ã‚¤ãƒ‰ã€ã¯ã€2.10 ã®ãƒªãƒªãƒ¼ã‚¹ã«åˆã‚ã›ã¦é »ç¹ã«å¤‰æ›´ã™ã‚‹ã“ã¨ã‚’想定ã—ã¦ã„ã¾ã™ã€‚``devel`` ブランãƒã®ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã«é–¢ã™ã‚‹æœ€æ–°æƒ…å ±ã¯ã€ã•ã¾ã–ã¾ãª :ref:`communication` ãƒãƒ£ãƒ³ãƒãƒ«ã«ã‚るコレクションã«é–¢ã™ã‚‹è°è«–を確èªã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_3.rst:558 -msgid "All ``nso`` modules have been removed from this collection. They have been migrated to the `cisco.nso <https://galaxy.ansible.com/cisco/nso>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided." -msgstr "ã™ã¹ã¦ã® ``nso`` モジュールãŒã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れら㯠`cisco.nso <https://galaxy.ansible.com/cisco/nso>`_ コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:12 +msgid "This section discusses the behavioral changes between Ansible 2.9 and Ansible-base 2.10." +msgstr "ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€Ansible 2.9 㨠Ansible-base 2.10 ã§ã®å‹•ä½œã®å¤‰æ›´ç‚¹ã‚’説明ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_3.rst:562 -msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.network.nso_config`` → ``cisco.nso.nso_config``) and make sure to install the `cisco.nso` collection." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.network.nso_config`` →``cisco.nso.nso_config``) を調整ã—ã€`cisco.nso` コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:14 +msgid "It is intended to assist in updating your playbooks, plugins and other parts of your Ansible infrastructure so they will work with this version of Ansible-base." +msgstr "本ガイドã¯ã€ã“ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Ansible-base ã§å‹•ä½œã™ã‚‹ã‚ˆã†ã«ã€Playbookã€ãƒ—ラグインã€ãã®ä»–ã® Ansible インフラストラクãƒãƒ£ãƒ¼ã‚’æ›´æ–°ã™ã‚‹éš›ã«ã”利用ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_3.rst:563 -msgid "All ``routeros`` modules and plugins have been removed from this collection. They have been migrated to the `community.routeros <https://galaxy.ansible.com/community/routeros>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided." -msgstr "ã™ã¹ã¦ã® ``routeros`` モジュールã¨ãƒ—ラグインãŒã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れら㯠`community.routeros <https://galaxy.ansible.com/community/routeros>`_ コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:16 +msgid "We suggest you read this page along with the `Ansible-base Changelog for 2.10 <https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst>`_ to understand what updates you may need to make." +msgstr "å¿…è¦ãªæ›´æ–°ã«ã¤ã„ã¦ç†è§£ã™ã‚‹ã«ã¯ã€ã“ã®ãƒšãƒ¼ã‚¸ã¨ä½µã›ã¦ã€Œ`Ansible-base Changelog for 2.10 <https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_3.rst:567 -msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.network.routeros_command`` → ``community.routeros.command``) and make sure to install the community.routeros collection." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN を調整 (``community.network.routeros_command`` →``community.routeros.command``) ã—ã€community.routeros コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:18 +msgid "Ansible-base is mainly of interest for developers and users who only want to use a small, controlled subset of the available collections. Regular users should install ansible." +msgstr "Ansible-base ã¯ã€ä¸»ã«ã€åˆ©ç”¨å¯èƒ½ãªã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ã†ã¡ã€åˆ¶å¾¡ã•ã‚ŒãŸå°ã•ãªã‚µãƒ–セットã®ã¿ã‚’使用ã—ãŸã„開発者やユーザーã®èˆˆå‘³ã‚’引ã製å“ã§ã™ã€‚一般ユーザー㯠Ansible をインストールã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_3.rst:568 -msgid "The ``cp_publish`` module has been removed from this collection. It was a duplicate of ``check_point.mgmt.cp_mgmt_publish`` in the `check_point.mgmt <https://galaxy.ansible.com/check_point/mgmt>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided. If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.network.cp_publish`` → ``check_point.mgmt.cp_mgmt_publish``) and make sure to install the check_point.mgmt collection." -msgstr "``cp_publish`` モジュールã¯ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れ㯠`check_point.mgmt <https://galaxy.ansible.com/check_point/mgmt>`_ コレクション㮠``check_point.mgmt.cp_mgmt_publish`` ã¨é‡è¤‡ã—ã¦ã„ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.network.cp_publish`` →``check_point.mgmt.cp_mgmt_publish``) を調整ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã¾ãŸã€check_point.mgmt コレクションをインストールã—ã¦ãã ã•ã„。" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:20 +#: ../../rst/porting_guides/porting_guide_core_2.11.rst:16 +msgid "The complete list of porting guides can be found at :ref:`porting guides <porting_guides>`." +msgstr "移æ¤ã‚¬ã‚¤ãƒ‰ã®å®Œå…¨ãªãƒªã‚¹ãƒˆã¯ã€ã€Œ:ref:`移æ¤ã‚¬ã‚¤ãƒ‰ <porting_guides>`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_3.rst:570 -msgid "The ``fortimanager`` httpapi plugin has been removed from this collection. It was a duplicate of the one in the `fortinet.fortimanager <https://galaxy.ansible.com/fortinet/fortimanager>`_ collection. If you use ansible-base 2.10 or newer, a redirection has been provided." -msgstr "``fortimanager`` httpapi プラグインã¯ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れ㯠`fortinet.fortimanager <https://galaxy.ansible.com/fortinet/fortimanager>`_ コレクションã«ã‚ã‚‹ã‚‚ã®ã¨é‡è¤‡ã—ã¦ã„ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’ãŠä½¿ã„ã®æ–¹ã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒç”¨æ„ã•ã‚Œã¦ã„ã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:23 +#: ../../rst/porting_guides/porting_guide_core_2.11.rst:18 +msgid "Contents" +msgstr "内容" -#: ../../rst/porting_guides/porting_guide_3.rst:574 -msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.network.fortimanager`` → ``fortinet.fortimanager.fortimanager``) and make sure to install the `fortinet.fortimanager` collection." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.network.fortimanager`` →``fortinet.fortimanager.fortimanager``) を調整ã—ã€`fortinet.fortimanager` コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:28 +msgid "Fixed a bug on boolean keywords that made random strings return 'False', now they should return an error if they are not a proper boolean Example: ``diff: yes-`` was returning ``False``." +msgstr "ランダムãªæ–‡å—列ãŒã€ŒFalseã€ã‚’è¿”ã™ãƒ–ール値ã®ã‚ーワードã®ãƒã‚°ã‚’ä¿®æ£ã—ã¾ã—ãŸã€‚é©åˆ‡ãªãƒ–ール値ã§ã¯ãªã„å ´åˆã¯ã‚¨ãƒ©ãƒ¼ã‚’è¿”ã™ã¯ãšã§ã™ (例: ``diff: yes-`` ㌠``False`` ã‚’è¿”ã—ã¦ã„ã‚‹å ´åˆ)。" -#: ../../rst/porting_guides/porting_guide_3.rst:575 -msgid "The dependency on the ``check_point.mgmt`` collection has been removed. If you depend on that installing ``community.network`` also installs ``check_point.mgmt``, you have to make sure to install ``check_point.mgmt`` explicitly." -msgstr "``check_point.mgmt`` コレクションã®ä¾å˜é–¢ä¿‚ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚``community.network`` ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã«ã‚ˆã£ã¦ ``check_point.mgmt`` もインストールã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€å¿…ãš ``check_point.mgmt`` を明示的ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:30 +msgid "A new fact, ``ansible_processor_nproc`` reflects the number of vcpus available to processes (falls back to the number of vcpus available to the scheduler)." +msgstr "æ–°ã—ã„ファクト ``ansible_processor_nproc`` ã¯ã€ãƒ—ãƒã‚»ã‚¹ã§åˆ©ç”¨å¯èƒ½ãª vcpu ã®æ•°ã‚’åæ˜ ã—ã¦ã„ã¾ã™ (スケジューラーã§åˆ©ç”¨å¯èƒ½ãª vcpu ã®æ•°ã«æˆ»ã•ã‚Œã¾ã™)。" -#: ../../rst/porting_guides/porting_guide_3.rst:576 -msgid "The deprecated Pluribus Networks modules ``pn_cluster``, ``pn_ospf``, ``pn_ospfarea``, ``pn_show``, ``pn_trunk``, ``pn_vlag``, ``pn_vlan``, ``pn_vrouter``, ``pn_vrouterbgp``, ``pn_vrouterif``, ``pn_vrouterlbif`` have been removed (https://github.com/ansible-collections/community.network/pull/176)." -msgstr "éžæŽ¨å¥¨ã® Pluribus Networks モジュール ``pn_cluster``ã€``pn_ospf``ã€``pn_ospfarea``ã€``pn_show``ã€``pn_trunk``ã€``pn_vlag`` ``pn_vlan``ã€``pn_vrouter``ã€``pn_vrouterbgp``ã€``pn_vrouterif``ã€ãŠã‚ˆã³ ``pn_vrouterlbif`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.network/pull/176)。" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:38 +msgid "The ``ansible-galaxy login`` command has been removed, as the underlying API it used for GitHub auth is being shut down. Publishing roles or collections to Galaxy via ``ansible-galaxy`` now requires that a Galaxy API token be passed to the CLI via a token file (default location ``~/.ansible/galaxy_token``) or (insecurely) via the ``--token`` argument to ``ansible-galaxy``." +msgstr "GitHub èªè¨¼ã«ä½¿ç”¨ã•ã‚Œã‚‹åŸºç¤Žã¨ãªã‚‹ API ãŒã‚·ãƒ£ãƒƒãƒˆãƒ€ã‚¦ãƒ³ã•ã‚Œã‚‹ãŸã‚ã€``ansible-galaxy login`` コマンドãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚``ansible-galaxy`` 経由㧠Galaxy ã«ãƒãƒ¼ãƒ«ã¾ãŸã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’公開ã™ã‚‹å ´åˆã¯ã€Galaxy API トークンをトークンファイル (デフォルトã®å ´æ‰€ ``~/.ansible/galaxy_token``) ã¾ãŸã¯ ``--token`` 引数ã‹ã‚‰ ``ansible-galaxy`` ã« (ã‚»ã‚ュリティーを確ä¿ã›ãšã«ã‚»ã‚ュアã«) 渡ã™ã“ã¨ãŒå¿…è¦ã«ãªã‚Šã¾ã—ãŸã€‚" -#: ../../rst/porting_guides/porting_guide_3.rst:577 -msgid "The deprecated modules ``panos_admin``, ``panos_admpwd``, ``panos_cert_gen_ssh``, ``panos_check``, ``panos_commit``, ``panos_dag``, ``panos_dag_tags``, ``panos_import``, ``panos_interface``, ``panos_lic``, ``panos_loadcfg``, ``panos_match_rule``, ``panos_mgtconfig``, ``panos_nat_rule``, ``panos_object``, ``panos_op``, ``panos_pg``, ``panos_query_rules``, ``panos_restart``, ``panos_sag``, ``panos_security_rule``, ``panos_set`` have been removed. Use modules from the `paloaltonetworks.panos collection <https://galaxy.ansible.com/paloaltonetworks/panos>`_ instead (https://github.com/ansible-collections/community.network/pull/176)." -msgstr "éžæŽ¨å¥¨ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``panos_admin``ã€``panos_admpwd``ã€``panos_cert_gen_ssh``ã€``panos_check``ã€``panos_commit``ã€``panos_dag``ã€``panos_dag_tags`` ``panos_import``ã€``panos_interface``ã€``panos_lic``ã€``panos_loadcfg``ã€``panos_match_rule``ã€``panos_mgtconfig``ã€``panos_nat_rule``ã€``panos_object``ã€``panos_op``ã€``panos_pg``ã€``panos_query_rules``ã€``panos_restart``ã€``panos_sag``ã€``panos_security_rule``ã€ãŠã‚ˆã³ ``panos_set`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« `paloaltonetworks.panos collection <https://galaxy.ansible.com/paloaltonetworks/panos>`_ ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¾ã™ (https://github.com/ansible-collections/community.network/pull/176)。" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:46 +msgid "Windows Server 2008 and 2008 R2 will no longer be supported or tested in the next Ansible release, see :ref:`windows_faq_server2008`." +msgstr "Windows Server 2008 ãŠã‚ˆã³ 2008 R2 ã¯ã€æ¬¡å›žã® Ansible リリースã§ã¯ã‚µãƒãƒ¼ãƒˆã•ã‚Œãšã€ãƒ†ã‚¹ãƒˆã•ã‚Œãªããªã‚Šã¾ã™ã€‚「:ref:`windows_faq_server2008`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_3.rst:578 -msgid "The redirect to the ``mellanox.onyx`` collection was removed for: the ``onyx`` cliconf plugin, terminal plugin, module_utils, action plugin, doc fragment, and the following modules: ``onyx_aaa``, ``onyx_bfd``, ``onyx_bgp``, ``onyx_buffer_pool``, ``onyx_command``, ``onyx_config``, ``onyx_facts``, ``onyx_igmp``, ``onyx_igmp_interface``, ``onyx_igmp_vlan``, ``onyx_interface``, ``onyx_l2_interface``, ``onyx_l3_interface``, ``onyx_linkagg``, ``onyx_lldp``, ``onyx_lldp_interface``, ``onyx_magp``, ``onyx_mlag_ipl``, ``onyx_mlag_vip``, ``onyx_ntp``, ``onyx_ntp_servers_peers``, ``onyx_ospf``, ``onyx_pfc_interface``, ``onyx_protocol``, ``onyx_ptp_global``, ``onyx_ptp_interface``, ``onyx_qos``, ``onyx_snmp``, ``onyx_snmp_hosts``, ``onyx_snmp_users``, ``onyx_syslog_files``, ``onyx_syslog_remote``, ``onyx_traffic_class``, ``onyx_username``, ``onyx_vlan``, ``onyx_vxlan``, ``onyx_wjh`` (https://github.com/ansible-collections/community.network/pull/175)." -msgstr "``mellanox.onyx`` コレクションã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã¯ã€``onyx`` cliconf プラグインã€ã‚¿ãƒ¼ãƒŸãƒŠãƒ«ãƒ—ラグインã€module_utilsã€action プラグインã€doc フラグメントã€ãŠã‚ˆã³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``onyx_aaa``ã€``onyx_bfd``ã€``onyx_bgp``ã€``onyx_buffer_pool``ã€``onyx_command``ã€``onyx_config``ã€``onyx_facts``ã€``onyx_igmp``ã€``onyx_igmp_interface``ã€``onyx_igmp_vlan``ã€``onyx_interface``ã€``onyx_l2_interface``ã€``onyx_l3_interface``ã€``onyx_linkagg``ã€``onyx_lldp``ã€``onyx_lldp_interface``ã€``onyx_magp``ã€``onyx_mlag_ipl``ã€``onyx_mlag_vip``ã€``onyx_ntp``ã€``onyx_ntp_servers_peers``ã€``onyx_ospf``ã€``onyx_pfc_interface``ã€``onyx_protocol``ã€``onyx_ptp_global``ã€``onyx_ptp_interface``ã€``onyx_qos``ã€``onyx_snmp``ã€``onyx_snmp_hosts``ã€``onyx_snmp_users``ã€``onyx_syslog_files``ã€``onyx_syslog_remote``ã€``onyx_traffic_class``ã€``onyx_username``ã€``onyx_vlan``ã€``onyx_vxlan``ã€ãŠã‚ˆã³ ``onyx_wjh`` ã«å¯¾ã—ã¦å‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.network/pull/175)。" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:54 +msgid "Links on this page may not point to the most recent versions of modules. We will update them when we can." +msgstr "ã“ã®ãƒšãƒ¼ã‚¸ã®ãƒªãƒ³ã‚¯ã¯ã€æœ€æ–°ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’å‚ç…§ã—ã¦ã„ãªã„å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚å¯èƒ½ãªé™ã‚Šæ›´æ–°ã—ã¦ã„ãã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_3.rst:610 -msgid "The ``gluster_heal_info``, ``gluster_peer`` and ``gluster_volume`` modules have migrated to the `gluster.gluster <https://galaxy.ansible.com/gluster/gluster>`_ collection. Ansible-base 2.10.1 adjusted the routing target to point to the modules in that collection, so we will remove these modules in community.general 3.0.0. If you use Ansible 2.9, or use FQCNs ``community.general.gluster_*`` in your playbooks and/or roles, please update them to use the modules from ``gluster.gluster`` instead." -msgstr "``gluster_heal_info`` モジュールã€``gluster_peer`` モジュールã€ãŠã‚ˆã³ ``gluster_volume`` モジュール㯠`gluster.gluster <https://galaxy.ansible.com/gluster/gluster>`_ コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚Ansible-base 2.10.1 ã§ã¯ã€ãƒ«ãƒ¼ãƒ†ã‚£ãƒ³ã‚°ã‚¿ãƒ¼ã‚²ãƒƒãƒˆãŒã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’å‚ç…§ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã•ã‚ŒãŸãŸã‚ã€community.general 3.0.0 ã§ã“れらã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’削除ã™ã‚‹äºˆå®šã§ã™ã€‚Ansible 2.9 を使用ã—ã¦ã„ã‚‹å ´åˆã‚„ã€Playbook ã‚„ãƒãƒ¼ãƒ«ã§ FQCN ã® ``community.general.gluster_*`` を使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ä»£ã‚ã‚Šã«ã“れらをアップデートã—㦠``gluster.gluster`` ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:56 +msgid "Version 2.10.0 of ansible-base changed the default mode of file-based tasks to ``0o600 & ~umask`` when the user did not specify a ``mode`` parameter on file-based tasks. This was in response to a CVE report which we have reconsidered. As a result, the mode change has been reverted in 2.10.1, and mode will now default to ``0o666 & ~umask`` as in previous versions of Ansible." +msgstr "ansible-base ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.10.0 ã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒãƒ•ã‚¡ã‚¤ãƒ«ãƒ™ãƒ¼ã‚¹ã®ã‚¿ã‚¹ã‚¯ã§ ``mode`` パラメーターを指定ã—ãªã‹ã£ãŸå ´åˆã«ã€ãƒ•ã‚¡ã‚¤ãƒ«ãƒ™ãƒ¼ã‚¹ã®ã‚¿ã‚¹ã‚¯ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãƒ¢ãƒ¼ãƒ‰ã‚’ ``0o600 & ~umask`` ã«å¤‰æ›´ã—ã¾ã—ãŸã€‚ã“ã‚Œã¯ã€å†ç·¨æˆã—㟠CVE レãƒãƒ¼ãƒˆã«å¯¾ã™ã‚‹å¯¾å¿œã§ã—ãŸã€‚ãã®çµæžœã€2.10.1 ã§ã¯ãƒ¢ãƒ¼ãƒ‰ã®å¤‰æ›´ãŒå…ƒã«æˆ»ã•ã‚Œã€ä»¥å‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Ansible ã¨åŒæ§˜ã«ã€ãƒ¢ãƒ¼ãƒ‰ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãŒ ``0o666 & ~umask`` ã«ãªã‚Šã¾ã—ãŸã€‚" -#: ../../rst/porting_guides/porting_guide_3.rst:641 -msgid "The ``dellemc_get_firmware_inventory`` module is deprecated and replaced with ``idrac_firmware_info``." -msgstr "``dellemc_get_firmware_inventory`` モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€``idrac_firmware_info`` ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:57 +msgid "If you changed any tasks to specify less restrictive permissions while using 2.10.0, those changes will be unnecessary (but will do no harm) in 2.10.1." +msgstr "2.10.0 を使用ã™ã‚‹éš›ã«ã€ã‚ˆã‚Šåˆ¶é™ã®å°‘ãªã„パーミッションを指定ã™ã‚‹ã‚ˆã†ã«ã‚¿ã‚¹ã‚¯ã‚’変更ã—ãŸå ´åˆã€2.10.1 ã§ã¯ãã®å¤‰æ›´ã¯ä¸è¦ã«ãªã‚Šã¾ã™ (ãŸã ã—ã€å®³ã¯ã‚ã‚Šã¾ã›ã‚“)。" -#: ../../rst/porting_guides/porting_guide_3.rst:642 -msgid "The ``dellemc_get_system_inventory`` module is deprecated and replaced with ``idrac_system_info``." -msgstr "``dellemc_get_system_inventory`` モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€``idrac_system_info`` ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:60 +msgid "``dnf`` and ``yum`` - As of version 2.10.1, the ``dnf`` module (and ``yum`` action when it uses ``dnf``) now correctly validates GPG signatures of packages (CVE-2020-14365). If you see an error such as ``Failed to validate GPG signature for [package name]``, please ensure that you have imported the correct GPG key for the DNF repository and/or package you are using. One way to do this is with the ``rpm_key`` module. Although we discourage it, in some cases it may be necessary to disable the GPG check. This can be done by explicitly adding ``disable_gpg_check: yes`` in your ``dnf`` or ``yum`` task." +msgstr "``dnf`` ãŠã‚ˆã³ ``yum`` - ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.10.1 よりã€``dnf`` モジュール (ãŠã‚ˆã³ ``dnf`` を使用ã™ã‚‹å ´åˆã¯ ``yum`` アクション) ãŒãƒ‘ッケージ㮠GPG ç½²åã‚’æ£ã—ã検証ã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—㟠(CVE-2020-14365)。``Failed to validate GPG signature for [package name]`` ã®ã‚ˆã†ãªã‚¨ãƒ©ãƒ¼ãŒè¡¨ç¤ºã•ã‚ŒãŸå ´åˆã¯ã€ä½¿ç”¨ã—ã¦ã„ã‚‹ DNF リãƒã‚¸ãƒˆãƒªãƒ¼ã‚„パッケージ㮠GPG ã‚ーãŒæ£ã—ãインãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。ã“れを行ㆠ1 ã¤ã®æ–¹æ³•ã¨ã—ã¦ã€``rpm_key`` モジュールã®ä½¿ç”¨ãŒã‚ã‚Šã¾ã™ã€‚推奨ã¯ã—ã¾ã›ã‚“ãŒã€å ´åˆã«ã‚ˆã£ã¦ã¯ GPG ãƒã‚§ãƒƒã‚¯ã‚’無効ã«ã™ã‚‹å¿…è¦ãŒã‚ã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“。ã“ã‚Œã¯ã€``dnf`` タスクã¾ãŸã¯ ``yum`` タスク㫠``disable_gpg_check: yes`` を明示的ã«è¿½åŠ ã™ã‚‹ã“ã¨ã§å®Ÿç¾ã§ãã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_3.rst:643 -msgid "The dellemc_change_power_state module is deprecated and replaced with the redfish_powerstate module." -msgstr "dellemc_change_power_state モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€redfish_powerstate モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:66 +msgid "Ansible modules created with ``add_file_common_args=True`` added a number of undocumented arguments which were mostly there to ease implementing certain action plugins. The undocumented arguments ``src``, ``follow``, ``force``, ``content``, ``backup``, ``remote_src``, ``regexp``, ``delimiter``, and ``directory_mode`` are now no longer added. Modules relying on these options to be added need to specify them by themselves." +msgstr "``add_file_common_args=True`` ã§ä½œæˆã•ã‚ŒãŸ Ansible モジュールã«ã‚ˆã‚Šã€ç‰¹å®šã‚¢ã‚¯ã‚·ãƒ§ãƒ³ãƒ—ラグインã®å®Ÿè£…を容易ã«ã™ã‚‹ãŸã‚ã«ã€æ–‡æ›¸åŒ–ã•ã‚Œã¦ã„ãªã„引数ãŒè¤‡æ•°è¿½åŠ ã•ã‚Œã¦ã„ã¾ã™ã€‚ドã‚ュメント化ã•ã‚Œã¦ã„ãªã„引数 ``src``ã€``follow``ã€``force``ã€``content``ã€``backup``ã€``remote_src``ã€``regexp``ã€``delimiter``ã€ãŠã‚ˆã³ ``directory_mode`` ãŒè¿½åŠ ã•ã‚Œãªããªã‚Šã¾ã—ãŸã€‚ã‚ªãƒ—ã‚·ãƒ§ãƒ³ã‚’è¿½åŠ ã™ã‚‹ãŸã‚ã€ã“れらã®ã‚ªãƒ—ションãŒè¿½åŠ ã•ã‚Œã‚‹ã“ã¨ã«ä¾å˜ã—ã¦ã„るモジュールã¯ã€è‡ªåˆ†ã§ãれらを指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_3.rst:644 -msgid "The dellemc_configure_bios module is deprecated and replaced with the idrac_bios module." -msgstr "dellemc_configure_bios モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_bios モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:67 +msgid "Ansible no longer looks for Python modules in the current working directory (typically the ``remote_user``'s home directory) when an Ansible module is run. This is to fix becoming an unprivileged user on OpenBSD and to mitigate any attack vector if the current working directory is writable by a malicious user. Install any Python modules needed to run the Ansible modules on the managed node in a system-wide location or in another directory which is in the ``remote_user``'s ``$PYTHONPATH`` and readable by the ``become_user``." +msgstr "Ansible ã¯ã€Ansible モジュールã®å®Ÿè¡Œæ™‚ã«ã€ç¾åœ¨ã®ä½œæ¥ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ (通常㯠``remote_user`` ã®ãƒ›ãƒ¼ãƒ ディレクトリー) ã«ã‚ã‚‹ Python モジュールを検索ã—ãªããªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã«ã‚ˆã‚Šã€OpenBSD ã§æ¨©é™ã®ãªã„ユーザーã«ãªã‚Š (become)ã€æ‚ªæ„ã®ã‚るユーザーãŒç¾åœ¨ã®ä½œæ¥ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã‚’書ãè¾¼ã¿å¯èƒ½ãªå ´åˆã«æ”»æ’ƒãƒ™ã‚¯ãƒˆãƒ«ã‚’軽減ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚Ansible モジュールをã€ã‚·ã‚¹ãƒ†ãƒ 全体ã®ç®¡ç†ãƒŽãƒ¼ãƒ‰ã¾ãŸã¯ ``remote_user`` ã® ``$PYTHONPATH`` ã«ã‚ã‚Šã€``become_user`` ãŒèªã¿å–ã‚Šå¯èƒ½ãªåˆ¥ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ã€Ansible モジュールを実行ã™ã‚‹ã®ã«å¿…è¦ãª Python モジュールをインストールã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_3.rst:645 -msgid "The dellemc_configure_idrac_network module is deprecated and replaced with the idrac_network module." -msgstr "dellemc_configure_idrac_network モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_network モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:74 +msgid "Lookup plugin names case-sensitivity" +msgstr "大文å—å°æ–‡å—を区別ã—ã¦ãƒ—ラグインåã®æ¤œç´¢" -#: ../../rst/porting_guides/porting_guide_3.rst:646 -msgid "The dellemc_configure_idrac_timezone module is deprecated and replaced with the idrac_timezone_ntp module." -msgstr "dellemc_configure_idrac_timezone モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_timezone_ntp モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:76 +msgid "Prior to Ansible ``2.10`` lookup plugin names passed in as an argument to the ``lookup()`` function were treated as case-insensitive as opposed to lookups invoked via ``with_<lookup_name>``. ``2.10`` brings consistency to ``lookup()`` and ``with_`` to be both case-sensitive." +msgstr "Ansible ``2.10`` ã® lookup プラグインå㌠``lookup()`` 関数ã«å¼•æ•°ã¨ã—ã¦æ¸¡ã•ã‚Œã‚‹å‰ã«ã€``with_<lookup_name>`` を介ã—ã¦å‘¼ã³å‡ºã•ã‚Œã‚‹ãƒ«ãƒƒã‚¯ã‚¢ãƒƒãƒ—ã¨ã¯ç•°ãªã‚Šã€å¤§æ–‡å—ã¨å°æ–‡å—を区別ã—ãªã„ã‚‚ã®ã¨ã—ã¦å‡¦ç†ã•ã‚Œã¾ã™ã€‚``2.10`` ã§ã¯ã€``lookup()`` 㨠``with_`` ã®ä¸¡æ–¹ã§å¤§æ–‡å—å°æ–‡å—を区別ã™ã‚‹ã‚ˆã†ã«æ•´åˆæ€§ãŒå–られã¦ã„ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_3.rst:647 -msgid "The dellemc_configure_idrac_users module is deprecated and replaced with the idrac_user module." -msgstr "dellemc_configure_idrac_users モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_user モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:81 +msgid "Cache plugins in collections can be used to cache data from inventory plugins. Previously, cache plugins in collections could only be used for fact caching." +msgstr "コレクション㮠cache プラグインを使用ã™ã‚‹ã¨ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ—ラグインã‹ã‚‰ãƒ‡ãƒ¼ã‚¿ã‚’ã‚ャッシュã§ãã¾ã™ã€‚以å‰ã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® cache プラグインã¯ãƒ•ã‚¡ã‚¯ãƒˆã‚ャッシュã«ã—ã‹ä½¿ç”¨ã§ãã¾ã›ã‚“ã§ã—ãŸã€‚" -#: ../../rst/porting_guides/porting_guide_3.rst:648 -msgid "The dellemc_delete_lc_job and dellemc_delete_lc_job_queue modules are deprecated and replaced with the idrac_lifecycle_controller_jobs module." -msgstr "dellemc_delete_lc_job モジュールãŠã‚ˆã³ dellemc_delete_lc_job_queue モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_lifecycle_controller_jobs モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:82 +msgid "Some undocumented arguments from ``FILE_COMMON_ARGUMENTS`` have been removed; plugins using these, in particular action plugins, need to be adjusted. The undocumented arguments which were removed are ``src``, ``follow``, ``force``, ``content``, ``backup``, ``remote_src``, ``regexp``, ``delimiter``, and ``directory_mode``." +msgstr "``FILE_COMMON_ARGUMENTS`` ã‹ã‚‰ã€æ–‡æ›¸åŒ–ã•ã‚Œã¦ã„ãªã„引数ãŒã„ãã¤ã‹å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れらã®ç‰¹å®šã®ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ãƒ—ラグインを使用ã™ã‚‹ãƒ—ラグインã¯ã€èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚削除ã•ã‚ŒãŸãƒ‰ã‚ュメントãªã—ã®å¼•æ•°ã¯ã€``src``ã€``follow``ã€``force``ã€``content``ã€``backup``ã€``remote_src``ã€``regexp``ã€``delimiter``ã€ãŠã‚ˆã³ ``directory_mode`` ã§ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_3.rst:649 -msgid "The dellemc_export_lc_logs module is deprecated and replaced with the idrac_lifecycle_controller_logs module." -msgstr "dellemc_export_lc_logs モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_lifecycle_controller_logs モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:85 +msgid "Action plugins which execute modules should use fully-qualified module names" +msgstr "モジュールを実行ã™ã‚‹ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ãƒ—ラグインã¯å®Œå…¨ä¿®é£¾ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«åã®ä½¿ç”¨ãŒå¿…è¦" -#: ../../rst/porting_guides/porting_guide_3.rst:650 -msgid "The dellemc_get_lc_job_status module is deprecated and replaced with the idrac_lifecycle_controller_job_status_info module." -msgstr "dellemc_get_lc_job_status モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_lifecycle_controller_job_status_info モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" +#: ../../rst/porting_guides/porting_guide_base_2.10.rst:87 +msgid "Action plugins that call modules should pass explicit, fully-qualified module names to ``_execute_module()`` whenever possible (eg, ``ansible.builtin.file`` rather than ``file``). This ensures that the task's collection search order is not consulted to resolve the module. Otherwise, a module from a collection earlier in the search path could be used when not intended." +msgstr "モジュールを呼ã³å‡ºã™ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ãƒ—ラグインã¯ã€å¯èƒ½ãªé™ã‚Šæ˜Žç¤ºçš„ãªå®Œå…¨ä¿®é£¾ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«åã‚’ ``_execute_module()`` ã«æ¸¡ã™å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``file``ã§ã¯ãªã ``ansible.builtin.file``)。ã“ã‚Œã«ã‚ˆã‚Šã€ã‚¿ã‚¹ã‚¯ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³æ¤œç´¢é †åºãŒãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’解決ã™ã‚‹ã‚ˆã†ã«å‚ç…§ã•ã‚Œãªããªã‚Šã¾ã™ã€‚ãã†ã—ãªã„ã¨ã€æ„図ã—ã¦ã„ãªã„ã¨ãã«æ¤œç´¢ãƒ‘スã®å‰ã®æ–¹ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒä½¿ç”¨ã•ã‚Œã¦ã—ã¾ã†å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_3.rst:651 -msgid "The dellemc_get_lcstatus module is deprecated and replaced with the idrac_lifecycle_controller_status_info module." -msgstr "dellemc_get_lcstatus モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_lifecycle_controller_status_info モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" +#: ../../rst/porting_guides/porting_guide_core_2.11.rst:6 +msgid "Ansible-core 2.11 Porting Guide" +msgstr "Ansible-core 2.11 移æ¤ã‚¬ã‚¤ãƒ‰" -#: ../../rst/porting_guides/porting_guide_3.rst:652 -msgid "The dellemc_idrac_reset module is deprecated and replaced with the idrac_reset module." -msgstr "dellemc_idrac_reset モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_reset モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" +#: ../../rst/porting_guides/porting_guide_core_2.11.rst:8 +msgid "This section discusses the behavioral changes between ``ansible-base`` 2.10 and ``ansible-core`` 2.11." +msgstr "ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€``ansible-base`` 2.10 ã‹ã‚‰ ``ansible-core`` 2.11 ã«ãŠã‘る動作ã®å¤‰æ›´ç‚¹ã‚’説明ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_3.rst:653 -msgid "The dellemc_setup_idrac_syslog module is deprecated and replaced with the idrac_syslog module." -msgstr "dellemc_setup_idrac_syslog モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_syslog モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" +#: ../../rst/porting_guides/porting_guide_core_2.11.rst:10 +msgid "It is intended to assist in updating your playbooks, plugins and other parts of your Ansible infrastructure so they work with this version of ``ansible-core``." +msgstr "本ガイドã¯ã€ã“ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® ``ansible-core`` ã§å‹•ä½œã™ã‚‹ã‚ˆã†ã«ã€Playbookã€ãƒ—ラグインã€ãã®ä»–ã® Ansible インフラストラクãƒãƒ£ãƒ¼ã‚’æ›´æ–°ã™ã‚‹éš›ã«ã”利用ã«ãªã‚Œã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:8 -msgid "Ansible 4 Porting Guide" -msgstr "Ansible 4 移æ¤ã‚¬ã‚¤ãƒ‰" +#: ../../rst/porting_guides/porting_guide_core_2.11.rst:12 +msgid "We suggest you read this page along with the `ansible-core Changelog for 2.11 <https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst>`_ to understand what updates you may need to make." +msgstr "å¿…è¦ãªæ›´æ–°ã«ã¤ã„ã¦ç†è§£ã™ã‚‹ã«ã¯ã€ã“ã®ãƒšãƒ¼ã‚¸ã¨ä½µã›ã¦ã€Œ`ansible-core Changelog for 2.11 <https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_4.rst:15 -msgid "We suggest you read this page along with the `Ansible 4 Changelog <https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst>`_ to understand what updates you may need to make." -msgstr "å¿…è¦ãªæ›´æ–°ã«ã¤ã„ã¦ç†è§£ã™ã‚‹ã«ã¯ã€ã“ã®ãƒšãƒ¼ã‚¸ã¨ä½µã›ã¦ã€Œ`Ansible 4 Changelog <https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" +#: ../../rst/porting_guides/porting_guide_core_2.11.rst:14 +msgid "``ansible-core`` is mainly of interest for developers and users who only want to use a small, controlled subset of the available collections. Regular users should install Ansible." +msgstr "``ansible-core`` ã¯ã€ä¸»ã«ã€åˆ©ç”¨å¯èƒ½ãªã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ã†ã¡ã€åˆ¶å¾¡ã•ã‚ŒãŸå°ã•ãªã‚µãƒ–セットã®ã¿ã‚’使用ã—ãŸã„開発者やユーザーã®èˆˆå‘³ã‚’引ã製å“ã§ã™ã€‚一般ユーザー㯠Ansible をインストールã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_4.rst:20 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:23 msgid "The ``jinja2_native`` setting now does not affect the template module which implicitly returns strings. For the template lookup there is a new argument ``jinja2_native`` (off by default) to control that functionality. The rest of the Jinja2 expressions still operate based on the ``jinja2_native`` setting." msgstr "``jinja2_native`` è¨å®šã¯ã€æš—黙的ã«æ–‡å—列を返ã™ãƒ†ãƒ³ãƒ—レートモジュールã«ã¯å½±éŸ¿ã‚’åŠã¼ã—ã¾ã›ã‚“。テンプレートã®æ¤œç´¢ã§ã¯ã€ãã®æ©Ÿèƒ½ã‚’制御ã™ã‚‹æ–°ã—ã„引数 ``jinja2_native`` (デフォルトã§ã¯ off) ãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸã€‚残り㮠Jinja2 å¼ã¯ã€``jinja2_native`` è¨å®šã«åŸºã¥ã„ã¦å‹•ä½œã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:26 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:29 msgid "The ``ansible-galaxy login`` command has been removed, as the underlying API it used for GitHub auth has been shut down. Publishing roles or collections to Galaxy with ``ansible-galaxy`` now requires that a Galaxy API token be passed to the CLI using a token file (default location ``~/.ansible/galaxy_token``) or (insecurely) with the ``--token`` argument to ``ansible-galaxy``." msgstr "GitHub èªè¨¼ã«ä½¿ç”¨ã•ã‚Œã‚‹åŸºç¤Žã¨ãªã‚‹ API ãŒã‚·ãƒ£ãƒƒãƒˆãƒ€ã‚¦ãƒ³ã•ã‚Œã‚‹ãŸã‚ã€``ansible-galaxy login`` コマンドãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚``ansible-galaxy`` 経由㧠Galaxy ã«ãƒãƒ¼ãƒ«ã¾ãŸã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’公開ã™ã‚‹å ´åˆã¯ã€Galaxy API トークンをトークンファイル (デフォルトã®å ´æ‰€ ``~/.ansible/galaxy_token``) ã¾ãŸã¯ ``--token`` 引数ã‹ã‚‰ ``ansible-galaxy`` ã« (ã‚»ã‚ュリティーを確ä¿ã›ãšã«) 渡ã™ã“ã¨ãŒå¿…è¦ã«ãªã‚Šã¾ã—ãŸã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:32 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:35 msgid "The constant ``ansible.module_utils.basic._CHECK_ARGUMENT_TYPES_DISPATCHER`` is deprecated. Use :const:`ansible.module_utils.common.parameters.DEFAULT_TYPE_VALIDATORS` instead." msgstr "定数 ``ansible.module_utils.basic._CHECK_ARGUMENT_TYPES_DISPATCHER`` ã¯å»ƒæ¢ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« :const:`ansible.module_utils.common.parameters.DEFAULT_TYPE_VALIDATORS` を使用ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_4.rst:39 +#: ../../rst/porting_guides/porting_guide_core_2.11.rst:39 +msgid "Breaking Changes" +msgstr "互æ›æ€§ã‚’失ã‚ã›ã‚‹å¤‰æ›´ç‚¹" + #: ../../rst/porting_guides/porting_guide_core_2.11.rst:42 msgid "Changes to ``AnsibleModule``" msgstr "``AnsibleModule`` ã®å¤‰æ›´ç‚¹" -#: ../../rst/porting_guides/porting_guide_4.rst:41 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:44 msgid "With the move to :class:`ArgumentSpecValidator <ansible.module_utils.common.arg_spec.ArgumentSpecValidator>` for performing argument spec validation, the following private methods in :class:`AnsibleModule <ansible.module_utils.basic.AnsibleModule>` have been removed:" msgstr "引数仕様ã®æ¤œè¨¼ã‚’実行ã™ã‚‹ãŸã‚ã« :class:`ArgumentSpecValidator <ansible.module_utils.common.arg_spec.ArgumentSpecValidator>` ã«ç§»è¡Œã—ãŸã“ã¨ã§ã€:class:`AnsibleModule <ansible.module_utils.basic.AnsibleModule>` ã«ã‚る以下ã®ãƒ—ライベートメソッドãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:43 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:46 msgid "``_check_argument_types()``" msgstr "``_check_argument_types()``" -#: ../../rst/porting_guides/porting_guide_4.rst:44 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:47 msgid "``_check_argument_values()``" msgstr "``_check_argument_values()``" -#: ../../rst/porting_guides/porting_guide_4.rst:45 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:48 msgid "``_check_arguments()``" msgstr "``_check_arguments()``" -#: ../../rst/porting_guides/porting_guide_4.rst:46 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:49 msgid "``_check_mutually_exclusive()`` --> :func:`ansible.module_utils.common.validation.check_mutually_exclusive`" msgstr "``_check_mutually_exclusive()`` --> :func:`ansible.module_utils.common.validation.check_mutually_exclusive`" -#: ../../rst/porting_guides/porting_guide_4.rst:47 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:50 msgid "``_check_required_arguments()`` --> :func:`ansible.module_utils.common.validation.check_required_arguments`" msgstr "``_check_required_arguments()`` --> :func:`ansible.module_utils.common.validation.check_required_arguments`" -#: ../../rst/porting_guides/porting_guide_4.rst:48 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:51 msgid "``_check_required_by()`` --> :func:`ansible.module_utils.common.validation.check_required_by`" msgstr "``_check_required_by()`` --> :func:`ansible.module_utils.common.validation.check_required_by`" -#: ../../rst/porting_guides/porting_guide_4.rst:49 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:52 msgid "``_check_required_if()`` --> :func:`ansible.module_utils.common.validation.check_required_if`" msgstr "``_check_required_if()`` --> :func:`ansible.module_utils.common.validation.check_required_if`" -#: ../../rst/porting_guides/porting_guide_4.rst:50 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:53 msgid "``_check_required_one_of()`` --> :func:`ansible.module_utils.common.validation.check_required_one_of`" msgstr "``_check_required_one_of()`` --> :func:`ansible.module_utils.common.validation.check_required_one_of`" -#: ../../rst/porting_guides/porting_guide_4.rst:51 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:54 msgid "``_check_required_together()`` --> :func:`ansible.module_utils.common.validation.check_required_together`" msgstr "``_check_required_together()`` --> :func:`ansible.module_utils.common.validation.check_required_together`" -#: ../../rst/porting_guides/porting_guide_4.rst:52 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:55 msgid "``_check_type_bits()`` --> :func:`ansible.module_utils.common.validation.check_type_bits`" msgstr "``_check_type_bits()`` --> :func:`ansible.module_utils.common.validation.check_type_bits`" -#: ../../rst/porting_guides/porting_guide_4.rst:53 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:56 msgid "``_check_type_bool()`` --> :func:`ansible.module_utils.common.validation.check_type_bool`" msgstr "``_check_type_bool()`` --> :func:`ansible.module_utils.common.validation.check_type_bool`" -#: ../../rst/porting_guides/porting_guide_4.rst:54 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:57 msgid "``_check_type_bytes()`` --> :func:`ansible.module_utils.common.validation.check_type_bytes`" msgstr "``_check_type_bytes()`` --> :func:`ansible.module_utils.common.validation.check_type_bytes`" -#: ../../rst/porting_guides/porting_guide_4.rst:55 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:58 msgid "``_check_type_dict()`` --> :func:`ansible.module_utils.common.validation.check_type_dict`" msgstr "``_check_type_dict()`` --> :func:`ansible.module_utils.common.validation.check_type_dict`" -#: ../../rst/porting_guides/porting_guide_4.rst:56 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:59 msgid "``_check_type_float()`` --> :func:`ansible.module_utils.common.validation.check_type_float`" msgstr "``_check_type_float()`` --> :func:`ansible.module_utils.common.validation.check_type_float`" -#: ../../rst/porting_guides/porting_guide_4.rst:57 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:60 msgid "``_check_type_int()`` --> :func:`ansible.module_utils.common.validation.check_type_int`" msgstr "``_check_type_int()`` --> :func:`ansible.module_utils.common.validation.check_type_int`" -#: ../../rst/porting_guides/porting_guide_4.rst:58 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:61 msgid "``_check_type_jsonarg()`` --> :func:`ansible.module_utils.common.validation.check_type_jsonarg`" msgstr "``_check_type_jsonarg()`` --> :func:`ansible.module_utils.common.validation.check_type_jsonarg`" -#: ../../rst/porting_guides/porting_guide_4.rst:59 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:62 msgid "``_check_type_list()`` --> :func:`ansible.module_utils.common.validation.check_type_list`" msgstr "``_check_type_list()`` --> :func:`ansible.module_utils.common.validation.check_type_list`" -#: ../../rst/porting_guides/porting_guide_4.rst:60 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:63 msgid "``_check_type_path()`` --> :func:`ansible.module_utils.common.validation.check_type_path`" msgstr "``_check_type_path()`` --> :func:`ansible.module_utils.common.validation.check_type_path`" -#: ../../rst/porting_guides/porting_guide_4.rst:61 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:64 msgid "``_check_type_raw()`` --> :func:`ansible.module_utils.common.validation.check_type_raw`" msgstr "``_check_type_raw()`` --> :func:`ansible.module_utils.common.validation.check_type_raw`" -#: ../../rst/porting_guides/porting_guide_4.rst:62 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:65 msgid "``_check_type_str()`` --> :func:`ansible.module_utils.common.validation.check_type_str`" msgstr "``_check_type_str()`` --> :func:`ansible.module_utils.common.validation.check_type_str`" -#: ../../rst/porting_guides/porting_guide_4.rst:63 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:66 msgid "``_count_terms()`` --> :func:`ansible.module_utils.common.validation.count_terms`" msgstr "``_count_terms()`` --> :func:`ansible.module_utils.common.validation.count_terms`" -#: ../../rst/porting_guides/porting_guide_4.rst:64 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:67 msgid "``_get_wanted_type()``" msgstr "``_get_wanted_type()``" -#: ../../rst/porting_guides/porting_guide_4.rst:65 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:68 msgid "``_handle_aliases()``" msgstr "``_handle_aliases()``" -#: ../../rst/porting_guides/porting_guide_4.rst:66 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:69 msgid "``_handle_no_log_values()``" msgstr "``_handle_no_log_values()``" -#: ../../rst/porting_guides/porting_guide_4.rst:67 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:70 msgid "``_handle_options()``" msgstr "``_handle_options()``" -#: ../../rst/porting_guides/porting_guide_4.rst:68 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:71 msgid "``_set_defaults()``" msgstr "``_set_defaults()``" -#: ../../rst/porting_guides/porting_guide_4.rst:69 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:72 msgid "``_set_fallbacks()``" msgstr "``_set_fallbacks()``" -#: ../../rst/porting_guides/porting_guide_4.rst:71 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:74 msgid "Modules or plugins using these private methods should use the public functions in :mod:`ansible.module_utils.common.validation` or :meth:`ArgumentSpecValidator.validate() <ansible.module_utils.common.arg_spec.ArgumentSpecValidator.validate>` if no public function was listed above." msgstr "ã“れらã®ãƒ—ライベートメソッドを使用ã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¾ãŸã¯ãƒ—ラグインã¯ã€:mod:`ansible.module_utils.common.validation` ã®å…¬é–‹é–¢æ•° (公開関数ãŒä¸Šè¨˜ã®ä¸€è¦§ã«è¨˜è¼‰ã•ã‚Œã¦ã„ãªã„å ´åˆã¯ :meth:`ArgumentSpecValidator.validate() <ansible.module_utils.common.arg_spec.ArgumentSpecValidator.validate>`) を使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:75 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:78 msgid "Changes to :mod:`ansible.module_utils.common.parameters`" msgstr ":mod:`ansible.module_utils.common.parameters` ã®å¤‰æ›´ç‚¹" -#: ../../rst/porting_guides/porting_guide_4.rst:77 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:80 msgid "The following functions in :mod:`ansible.module_utils.common.parameters` are now private and should not be used directly. Use :meth:`ArgumentSpecValidator.validate() <ansible.module_utils.common.arg_spec.ArgumentSpecValidator.validate>` instead." msgstr ":mod:`ansible.module_utils.common.parameters` ã®ä»¥ä¸‹ã®æ©Ÿèƒ½ã¯ãƒ—ライベートã§ã‚ã‚‹ãŸã‚ã€ç›´æŽ¥ä½¿ç”¨ã—ãªã„ã§ãã ã•ã„。代ã‚ã‚Šã« :meth:`ArgumentSpecValidator.validate() <ansible.module_utils.common.arg_spec.ArgumentSpecValidator.validate>` を使用ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_4.rst:79 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:82 msgid "``list_no_log_values``" msgstr "``list_no_log_values``" -#: ../../rst/porting_guides/porting_guide_4.rst:80 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:83 msgid "``list_deprecations``" msgstr "``list_deprecations``" -#: ../../rst/porting_guides/porting_guide_4.rst:81 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:84 msgid "``handle_aliases``" msgstr "``handle_aliases``" -#: ../../rst/porting_guides/porting_guide_4.rst:85 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:88 msgid "Other" msgstr "ãã®ä»–" -#: ../../rst/porting_guides/porting_guide_4.rst:87 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:90 msgid "**Upgrading**: If upgrading from ``ansible < 2.10`` or from ``ansible-base`` and using pip, you must ``pip uninstall ansible`` or ``pip uninstall ansible-base`` before installing ``ansible-core`` to avoid conflicts." msgstr "**アップグレード**: ``ansible < 2.10`` ã¾ãŸã¯ ``ansible-base`` ã‹ã‚‰ã‚¢ãƒƒãƒ—グレードã—㦠pip を使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``ansible-core`` をインストールã™ã‚‹å‰ã«ã€``pip uninstall ansible`` ã¾ãŸã¯ ``pip uninstall ansible-base`` を指定ã—ã¦ç«¶åˆã‚’回é¿ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:88 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:91 msgid "Python 3.8 on the controller node is a soft requirement for this release. ``ansible-core`` 2.11 still works with the same versions of Python that ``ansible-base`` 2.10 worked with, however 2.11 emits a warning when running on a controller node with a Python version less than 3.8. This warning can be disabled by setting ``ANSIBLE_CONTROLLER_PYTHON_WARNING=False`` in your environment. ``ansible-core`` 2.12 will require Python 3.8 or greater." msgstr "コントãƒãƒ¼ãƒ©ãƒ¼ãƒŽãƒ¼ãƒ‰ã® Python 3.8 ã¯ã€æœ¬ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã‚½ãƒ•ãƒˆè¦ä»¶ã§ã™ã€‚``ansible-core`` 2.11 ã¯ã€``ansible-base`` 2.10 ãŒå‹•ä½œã—ãŸã®ã¨åŒã˜ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Python ã§å¼•ã続ã機能ã—ã¾ã™ãŒã€2.11 ã§ã¯ã€Python ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒ 3.8 未満ã®ã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©ãƒ¼ãƒŽãƒ¼ãƒ‰ã§å®Ÿè¡Œã™ã‚‹ã¨è¦å‘ŠãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚ã“ã®è¦å‘Šã¯ã€ãŠä½¿ã„ã®ç’°å¢ƒã« ``ANSIBLE_CONTROLLER_PYTHON_WARNING=False`` ã‚’è¨å®šã—ã¦ç„¡åŠ¹ã«ã§ãã¾ã™ã€‚``ansible-core`` 2.12 ã®å ´åˆã¯ Python 3.8 以é™ãŒå¿…è¦ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:89 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:92 msgid "The configuration system now validates the ``choices`` field, so any settings that violate it and were ignored in 2.10 cause an error in 2.11. For example, ``ANSIBLE_COLLECTIONS_ON_ANSIBLE_VERSION_MISMATCH=0`` now causes an error (valid choices are ``ignore``, ``warn`` or ``error``)." msgstr "è¨å®šã‚·ã‚¹ãƒ†ãƒ 㯠``choices`` フィールドを検証ã—ã€ã“れをé•åã—ã€2.10 ã§ç„¡è¦–ã•ã‚Œã¦ã„ãŸã™ã¹ã¦ã®è¨å®šãŒ 2.11 ã§ã‚¨ãƒ©ãƒ¼ã¨ãªã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚ãŸã¨ãˆã°ã€``ANSIBLE_COLLECTIONS_ON_ANSIBLE_VERSION_MISMATCH=0`` ã§ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—㟠(有効ãªé¸æŠžè‚¢ã¯ ``ignore``ã€``warn``ã€``error``ã§ã™)。" -#: ../../rst/porting_guides/porting_guide_4.rst:90 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:93 msgid "The ``ansible-galaxy`` command now uses ``resolvelib`` for resolving dependencies. In most cases this should not make a user-facing difference beyond being more performant, but we note it here for posterity and completeness." msgstr "``ansible-galaxy`` コマンドã§ã¯ã€ä¾å˜é–¢ä¿‚ã®è§£æ±ºã« ``resolvelib`` ãŒä½¿ç”¨ã•ã‚Œã¾ã™ã€‚ã»ã¨ã‚“ã©ã®å ´åˆã€ãƒ‘フォーマンスãŒå‘上ã™ã‚‹ã ã‘ã§ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«ã¨ã£ã¦ã¯ä½•ã®å¤‰åŒ–ã‚‚ã‚ã‚Šã¾ã›ã‚“ãŒã€è¨˜éŒ²ã®ãŸã‚ã«ã“ã“ã«è¨˜ã—ã¦ãŠãã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:91 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:94 msgid "If you import Python ``module_utils`` into any modules you maintain, you may now mark the import as optional during the module payload build by wrapping the ``import`` statement in a ``try`` or ``if`` block. This allows modules to use ``module_utils`` that may not be present in all versions of Ansible or a collection, and to perform arbitrary recovery or fallback actions during module runtime." msgstr "Python ``module_utils`` ã‚’ã€ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚¤ãƒ³ãƒãƒ¼ãƒˆã™ã‚‹å ´åˆã¯ã€``try`` ブãƒãƒƒã‚¯ã¾ãŸã¯ ``if`` ブãƒãƒƒã‚¯ã® ``import`` ステートメントをラップã—ã¦ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒšã‚¤ãƒãƒ¼ãƒ‰ã®æ§‹ç¯‰æ™‚ã«ã‚¤ãƒ³ãƒãƒ¼ãƒˆã‚’オプションã¨ãƒžãƒ¼ã‚¯ã§ãるよã†ã«ãªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã™ã¹ã¦ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Ansible ã¾ãŸã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«å˜åœ¨ã—ãªã„ ``module_utils`` を使用ã—ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ©ãƒ³ã‚¿ã‚¤ãƒ 時ã®ä»»æ„ã®ãƒªã‚«ãƒãƒªãƒ¼ã¾ãŸã¯ãƒ•ã‚©ãƒ¼ãƒ«ãƒãƒƒã‚¯ã®ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ã‚’実行ã§ãã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:97 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:100 msgid "The ``apt_key`` module has explicitly defined ``file`` as mutually exclusive with ``data``, ``keyserver`` and ``url``. They cannot be used together anymore." msgstr "``apt_key`` モジュールã¯ã€``data``ã€``keyserver``ã€ãŠã‚ˆã³ ``url`` ã¨ç›¸äº’ã«æŽ’ä»–çš„ãªã‚‚ã®ã¨ã—ã¦ã€``file`` を明示的ã«å®šç¾©ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:98 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:101 msgid "The ``meta`` module now supports tags for user-defined tasks. Set the task's tags to 'always' to maintain the previous behavior. Internal ``meta`` tasks continue to always run." msgstr "``meta`` モジュールã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼å®šç¾©ã®ã‚¿ã‚¹ã‚¯ã®ã‚¿ã‚°ã‚’サãƒãƒ¼ãƒˆã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚以å‰ã®å‹•ä½œã‚’ç¶æŒã™ã‚‹ãŸã‚ã«ã€ã‚¿ã‚¹ã‚¯ã®ã‚¿ã‚°ã‚’「alwaysã€ã«è¨å®šã—ã¾ã™ã€‚内部㮠``meta`` タスクã¯å¸¸ã«å®Ÿè¡Œã‚’継続ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:118 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:121 msgid "facts - On NetBSD, ``ansible_virtualization_type`` now tries to report a more accurate result than ``xen`` when virtualized and not running on Xen." msgstr "ファクト - NetBSD ã«ãŠã„ã¦ã€Xen 上ã§ä»®æƒ³åŒ–ã•ã‚Œã¦ã„ã¦å®Ÿè¡Œã—ã¦ã„ãªã„å ´åˆã€``ansible_virtualization_type`` ã¯ã€``xen`` よりもæ£ç¢ºãªçµæžœã‚’å ±å‘Šã—よã†ã¨ã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:119 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:122 msgid "facts - Virtualization facts now include ``virtualization_tech_guest`` and ``virtualization_tech_host`` keys. These are lists of virtualization technologies that a guest is a part of, or that a host provides, respectively. As an example, if you set up a host to provide both KVM and VirtualBox, both values are included in ``virtualization_tech_host``. Similarly, a podman container running on a VM powered by KVM has a ``virtualization_tech_guest`` of ``[\"kvm\", \"podman\", \"container\"]``." msgstr "ファクト: 仮想化ファクト㫠``virtualization_tech_guest`` ã‚ーãŠã‚ˆã³ ``virtualization_tech_host`` ã‚ーãŒå«ã¾ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚以下ã¯ã€ã‚²ã‚¹ãƒˆãŒã€ã¾ãŸã¯ãƒ›ã‚¹ãƒˆãŒæä¾›ã™ã‚‹ä»®æƒ³åŒ–テクノãƒã‚¸ãƒ¼ã®ä¸€è¦§ã§ã™ã€‚ãŸã¨ãˆã°ã€KVM 㨠VirtualBox ã®ä¸¡æ–¹ã‚’æä¾›ã™ã‚‹ãƒ›ã‚¹ãƒˆã‚’è¨å®šã™ã‚‹å ´åˆã¯ã€ä¸¡æ–¹ã®å€¤ãŒ ``virtualization_tech_host`` ã«çµ„ã¿è¾¼ã¾ã‚Œã¾ã™ã€‚åŒæ§˜ã«ã€KVM ãŒå¯¾å¿œã™ã‚‹ä»®æƒ³ãƒžã‚·ãƒ³ã§å®Ÿè¡Œã—ã¦ã„ã‚‹ podman コンテナーã«ã¯ã€ ``[\"kvm\", \"podman\", \"container\"]`` ã® ``virtualization_tech_guest`` ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:120 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:123 msgid "The parameter ``filter`` type is changed from ``string`` to ``list`` in the :ref:`setup <setup_module>` module in order to use more than one filter. Previous behavior (using a ``string``) still remains and works as a single filter." msgstr "複数ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã‚’使用ã™ã‚‹ãŸã‚ã«ã€ãƒ‘ラメーター ``filter`` タイプ㯠:ref:`setup <setup_module>` モジュール㮠``string`` ã‹ã‚‰ ``list`` ã«å¤‰æ›´ã•ã‚Œã¦ã„ã¾ã™ã€‚以å‰ã®å‹•ä½œã¯ (``string`` を使用) ã¯ãã®ã¾ã¾ã§ã€å˜ä¸€ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã¨ã—ã¦æ©Ÿèƒ½ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:126 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:129 msgid "inventory plugins - ``CachePluginAdjudicator.flush()`` now calls the underlying cache plugin's ``flush()`` instead of only deleting keys that it knows about. Inventory plugins should use ``delete()`` to remove any specific keys. As a user, this means that when an inventory plugin calls its ``clear_cache()`` method, facts could also be flushed from the cache. To work around this, users can configure inventory plugins to use a cache backend that is independent of the facts cache." msgstr "インベントリープラグイン - ``CachePluginAdjudicator.flush()`` ã¯ã€èªè˜ã—ã¦ã„ã‚‹éµã‚’削除ã™ã‚‹ã®ã§ã¯ãªãã€åŸºç¤Žã¨ãªã‚‹ã‚ャッシュプラグイン㮠``flush()`` を呼ã³å‡ºã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚インベントリープラグインã¯ã€``delete()`` を使用ã—ã¦ç‰¹å®šã‚ーを削除ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ユーザーã¨ã—ã¦ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ—ラグイン㌠``clear_cache()`` メソッドを呼ã³å‡ºã™ã¨ã€ãƒ•ã‚¡ã‚¯ãƒˆã‚’ã‚ャッシュã‹ã‚‰ãƒ•ãƒ©ãƒƒã‚·ãƒ¥ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚ã“れを回é¿ã™ã‚‹ã«ã¯ã€ãƒ•ã‚¡ã‚¯ãƒˆã‚ャッシュã‹ã‚‰ç‹¬ç«‹ã—ãŸã‚ャッシュãƒãƒƒã‚¯ã‚¨ãƒ³ãƒ‰ã‚’使用ã™ã‚‹ã‚ˆã†ã«ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ—ラグインをè¨å®šã§ãã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:127 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:130 msgid "callback plugins - ``meta`` task execution is now sent to ``v2_playbook_on_task_start`` like any other task. By default, only explicit meta tasks are sent there. Callback plugins can opt-in to receiving internal, implicitly created tasks to act on those as well, as noted in the plugin development documentation." msgstr "callback プラグイン - ``meta`` タスクã®å®Ÿè¡Œã¯ã€ä»–ã®ã‚¿ã‚¹ã‚¯ã¨åŒæ§˜ã« ``v2_playbook_on_task_start`` ã«é€ã‚‰ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚デフォルトã§ã¯ã€æ˜Žç¤ºçš„ãªãƒ¡ã‚¿ã‚¿ã‚¹ã‚¯ã®ã¿ãŒé€ä¿¡ã•ã‚Œã¾ã™ã€‚コールãƒãƒƒã‚¯ãƒ—ラグインã¯ã€ãƒ—ラグイン開発ã®ãƒ‰ã‚ュメントã«ã‚るよã†ã«ã€å†…部ã§æš—黙的ã«ä½œæˆã•ã‚ŒãŸã‚¿ã‚¹ã‚¯ã‚’å—ã‘å–ã£ã¦ã€ãれらã«ã‚‚対処ã™ã‚‹ã“ã¨ã‚’é¸æŠžã§ãã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:128 #: ../../rst/porting_guides/porting_guide_core_2.11.rst:131 msgid "The ``choices`` are now validated, so plugins that were using incorrect or incomplete choices issue an error in 2.11 if the value provided does not match. This has a simple fix: update the entries in ``choices`` to match reality." msgstr "``choices`` ãŒæ¤œè¨¼ã•ã‚Œã‚‹ã‚ˆã†ã«ãªã£ãŸãŸã‚ã€èª¤ã£ãŸé¸æŠžã€ã¾ãŸã¯ä¸å®Œå…¨ãªé¸æŠžã‚’使用ã—ã¦ã„ãŸãƒ—ラグインãŒã€2.11 ã§ã¯æä¾›ã•ã‚ŒãŸå€¤ãŒä¸€è‡´ã—ãªã„å ´åˆã«ã‚¨ãƒ©ãƒ¼ã«ãªã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã¯ç°¡å˜ã«ä¿®æ£ã§ãã¾ã™ã€‚実際ã®è¨å®šã«åˆã‚ã›ã¦ ``choices`` ã®ã‚¨ãƒ³ãƒˆãƒªãƒ¼ã‚’æ›´æ–°ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_4.rst:136 -msgid "Porting Guide for v4.6.0" -msgstr "v4.6.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_4.rst:142 -msgid "containers.podman" -msgstr "containers.podman" - -#: ../../rst/porting_guides/porting_guide_4.rst:144 -msgid "Add systemd generation for pods" -msgstr "Pod ã® systemd 生æˆã‚’è¿½åŠ " - -#: ../../rst/porting_guides/porting_guide_4.rst:145 -msgid "Generate systemd service files for containers" -msgstr "コンテナー㮠systemd サービスファイルã®ç”Ÿæˆ" - -#: ../../rst/porting_guides/porting_guide_4.rst:150 -msgid "enable client.ssl,server.ssl before starting the gluster volume (https://github.com/gluster/gluster-ansible-collection/pull/19)" -msgstr "gluster ボリュームを起動ã™ã‚‹å‰ã« client.ssl,server.ssl を有効ã«ã—ã¾ã™ï¼ˆhttps://github.com/gluster/gluster-ansible-collection/pull/19）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:158 -msgid "grafana_dashboard lookup - Providing a mangled version of the API key is no longer preferred." -msgstr "grafana_dashboard lookup - API ã‚ー㮠mangled ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®æä¾›ã¯æŽ¨å¥¨ã•ã‚Œãªããªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:161 -msgid "Porting Guide for v4.5.0" -msgstr "v4.5.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_4.rst:167 -msgid "hetzner.hcloud" -msgstr "hetzner.hcloud" - -#: ../../rst/porting_guides/porting_guide_4.rst:169 -msgid "Introduction of placement groups" -msgstr "é…置グループã®æ¦‚è¦" - -#: ../../rst/porting_guides/porting_guide_4.rst:174 -msgid "remove_stale_lun - Add role for removing stale LUN (https://bugzilla.redhat.com/1966873)." -msgstr "remove_stale_lun - å¤ã„ LUN を削除ã™ã‚‹ãƒãƒ¼ãƒ«ã‚’è¿½åŠ ã—ã¾ã™ï¼ˆhttps://bugzilla.redhat.com/1966873）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:182 -msgid "network_cli - The paramiko_ssh setting ``look_for_keys`` was set automatically based on the values of the ``password`` and ``private_key_file`` options passed to network_cli. This option can now be set explicitly, and the automatic setting of ``look_for_keys`` will be removed after 2024-01-01 (https://github.com/ansible-collections/ansible.netcommon/pull/271)." -msgstr "network_cli - paramiko_ssh è¨å®š ``look_for_keys`` ã¯ã€network_cli ã«æ¸¡ã•ã‚Œã‚‹ ``password`` オプションãŠã‚ˆã³ ``private_key_file`` オプションã®å€¤ã«åŸºã¥ã„ã¦è‡ªå‹•çš„ã«è¨å®šã•ã‚Œã¾ã™ã€‚ã“ã®ã‚ªãƒ—ションã¯æ˜Žç¤ºçš„ã«è¨å®šã§ãã€``look_for_keys`` ã®è‡ªå‹•è¨å®šã¯ 2024-01-01 以é™å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/ansible.netcommon/pull/271）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:185 -#: ../../rst/porting_guides/porting_guide_4.rst:514 -msgid "cisco.ios" -msgstr "cisco.ios" - -#: ../../rst/porting_guides/porting_guide_4.rst:187 -msgid "Deprecated ios_bgp in favor of ios_bgp_global and ios_bgp_address_family." -msgstr "ios_bgp_global ãŒéžæŽ¨å¥¨ã¨ãªã‚Šã€ios_bgp 㯠ios_bgp_global ãŠã‚ˆã³ ios_bgp_address_family ãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:188 -msgid "Remove testing with provider for ansible-test integration jobs. This helps prepare us to move to network-ee integration tests." -msgstr "ansible-test çµ±åˆã‚¸ãƒ§ãƒ–ã®ãƒ—ãƒãƒã‚¤ãƒ€ãƒ¼ã§ãƒ†ã‚¹ãƒˆã‚’削除ã—ã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€network-eeçµ±åˆãƒ†ã‚¹ãƒˆã«ç§»è¡Œã™ã‚‹ã®ã«ä¾¿åˆ©ã§ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:191 -#: ../../rst/porting_guides/porting_guide_4.rst:225 -#: ../../rst/porting_guides/porting_guide_4.rst:558 -msgid "junipernetworks.junos" -msgstr "junipernetworks.junos" - -#: ../../rst/porting_guides/porting_guide_4.rst:193 -msgid "Deprecated router_id from ospfv3 resource module." -msgstr "ospfv3 リソースモジュール㮠router_id ãŒéžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:196 -msgid "Porting Guide for v4.4.0" -msgstr "v4.4.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_4.rst:210 -#: ../../rst/porting_guides/porting_guide_4.rst:520 -msgid "cisco.iosxr" -msgstr "cisco.iosxr" - -#: ../../rst/porting_guides/porting_guide_4.rst:212 -msgid "The iosxr_logging module has been deprecated in favor of the new iosxr_logging_global resource module and will be removed in a release after '2023-08-01'." -msgstr "iosxr_logging モジュールãŒéžæŽ¨å¥¨ã¨ãªã‚Šã€'2023-08-01' ã®å¾Œã«ãƒªãƒªãƒ¼ã‚¹ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚æ–°ã—ã„ iosxr_logging_global リソースモジュールãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:217 -msgid "The nxos_logging module has been deprecated in favor of the new nxos_logging_global resource module and will be removed in a release after '2023-08-01'." -msgstr "nxos_logging モジュールãŒéžæŽ¨å¥¨ã¨ãªã‚Šã€'2023-08-01' ã®å¾Œã«ãƒªãƒªãƒ¼ã‚¹ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚æ–°ã—ã„ nxos_logging_global リソースモジュールãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:222 -msgid "docker_container - the new ``command_handling``'s default value, ``compatibility``, is deprecated and will change to ``correct`` in community.docker 3.0.0. A deprecation warning is emitted by the module in cases where the behavior will change. Please note that ansible-core will output a deprecation warning only once, so if it is shown for an earlier task, there could be more tasks with this warning where it is not shown (https://github.com/ansible-collections/community.docker/pull/186)." -msgstr "docker_container - æ–°ã—ã„ ``command_handling``ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ ``compatibility`` ã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€community.docker 3.0.0 㧠``correct`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ã€‚éžæŽ¨å¥¨ã®è¦å‘Šã¯ã€å‹•ä½œãŒå¤‰ã‚ã‚‹å ´åˆã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚ˆã£ã¦å‡ºåŠ›ã•ã‚Œã¾ã™ã€‚ansible-core ã¯éžæŽ¨å¥¨ã®è¦å‘Šã‚’一度ã ã‘出力ã™ã‚‹ãŸã‚ã€ä»¥å‰ã®ã‚¿ã‚¹ã‚¯ã§ã¯è¡¨ç¤ºã•ã‚Œãªã„å ´åˆã€è¡¨ç¤ºã•ã‚Œã¦ã„ãªã„å ´æ‰€ã§ã“ã®è¦å‘Šã§ã‚ˆã‚Šè¡¨ç¤ºã•ã‚Œã‚‹ã‚¿ã‚¹ã‚¯ãŒå¢—ãˆã‚‹å¯èƒ½æ€§ãŒã‚ã‚‹ã“ã¨ã«æ³¨æ„ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.docker/pull/186）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:227 -msgid "The junos_logging module has been deprecated in favor of the new junos_logging_global resource module and will be removed in a release after '2023-08-01'." -msgstr "junos_logging モジュールãŒéžæŽ¨å¥¨ã¨ãªã‚Šã€'2023-08-01' ã®å¾Œã«ãƒªãƒªãƒ¼ã‚¹ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚æ–°ã—ã„ junos_logging_global リソースモジュールãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:230 -#: ../../rst/porting_guides/porting_guide_4.rst:576 -msgid "vyos.vyos" -msgstr "vyos.vyos" - -#: ../../rst/porting_guides/porting_guide_4.rst:232 -msgid "The vyos_logging module has been deprecated in favor of the new vyos_logging_global resource module and will be removed in a release after \"2023-08-01\"." -msgstr "vyos_logging モジュールãŒéžæŽ¨å¥¨ã¨ãªã‚Šã€'2023-08-01' ã®å¾Œã«ãƒªãƒªãƒ¼ã‚¹ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚æ–°ã—ã„ vyos_logging_global リソースモジュールãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:235 -msgid "Porting Guide for v4.3.0" -msgstr "v4.3.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_4.rst:241 -msgid "netapp.cloudmanager" -msgstr "netapp.cloudmanager" - -#: ../../rst/porting_guides/porting_guide_4.rst:243 -msgid "Adding stage environment to all modules in cloudmanager" -msgstr "cloudmanager ã®ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¸ã®ã‚¹ãƒ†ãƒ¼ã‚¸ç’°å¢ƒã®è¿½åŠ " - -#: ../../rst/porting_guides/porting_guide_4.rst:251 -msgid "hashi_vault collection - support for Python 3.5 will be dropped in version ``2.0.0`` of ``community.hashi_vault`` (https://github.com/ansible-collections/community.hashi_vault/issues/81)." -msgstr "hashi_vault コレクション - Python3.5ã®ã‚µãƒãƒ¼ãƒˆãŒãƒãƒ¼ã‚¸ãƒ§ãƒ³``2.0.0``ã®``community.hashi_vault``ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.hashi_vault/issues/81）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:254 -msgid "Porting Guide for v4.2.0" -msgstr "v4.2.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_4.rst:271 -msgid "vmware_object_custom_attributes_info - added a new module to gather custom attributes of an object (https://github.com/ansible-collections/community.vmware/pull/851)." -msgstr "vmware_object_custom_attributes_info - オブジェクトã®ã‚«ã‚¹ã‚¿ãƒ 属性をåŽé›†ã™ã‚‹æ–°ã—ã„モジュールãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.vmware/pull/851）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:276 -msgid "idrac_server_config_profile - Added support for exporting and importing Server Configuration Profile through HTTP/HTTPS share." -msgstr "idrac_server_config_profile - HTTP/HTTPS 共有ã§ã®ã‚µãƒ¼ãƒãƒ¼è¨å®šãƒ—ãƒãƒ•ã‚¡ã‚¤ãƒ«ã®ã‚¨ã‚¯ã‚¹ãƒãƒ¼ãƒˆãŠã‚ˆã³ã‚¤ãƒ³ãƒãƒ¼ãƒˆã®ã‚µãƒãƒ¼ãƒˆãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:277 -msgid "ome_device_group - Added support for adding devices to a group using the IP addresses of the devices and group ID." -msgstr "ome_device_group - デãƒã‚¤ã‚¹ãŠã‚ˆã³ã‚°ãƒ«ãƒ¼ãƒ— ID ã® IP アドレスを使用ã—ã¦ã€ãƒ‡ãƒã‚¤ã‚¹ã‚’グループã«è¿½åŠ ã™ã‚‹ãŸã‚ã®ã‚µãƒãƒ¼ãƒˆãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:280 -#: ../../rst/porting_guides/porting_guide_4.rst:341 -#: ../../rst/porting_guides/porting_guide_4.rst:421 -#: ../../rst/porting_guides/porting_guide_4.rst:462 -#: ../../rst/porting_guides/porting_guide_4.rst:550 -#: ../../rst/porting_guides/porting_guide_4.rst:700 -msgid "fortinet.fortios" -msgstr "fortinet.fortios" - -#: ../../rst/porting_guides/porting_guide_4.rst:282 -msgid "New module fortios_monitor_fact." -msgstr "æ–°ã—ã„モジュール fortios_monitor_fact。" - -#: ../../rst/porting_guides/porting_guide_4.rst:283 -msgid "Support Fortios 7.0." -msgstr "Fortios 7.0 をサãƒãƒ¼ãƒˆã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:284 -msgid "Support Log APIs." -msgstr "ãƒã‚° API をサãƒãƒ¼ãƒˆã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:289 -msgid "The community.kubernetes collection is being renamed to kubernetes.core. In Ansible 5, community.kubernetes will be replaced by an empty collection which has deprecated redirects for all the current content to kubernetes.core. If you are using FQCNs starting with ``community.kubernetes.``, please update them to ``kubernetes.core.`` now. Note that kubernetes.core has been included in Ansible since Ansible 3.0.0 (https://github.com/ansible-community/community-topics/issues/22)." -msgstr "community.kubernetes コレクション㯠kubernetes.core ã«å¤‰æ›´ã•ã‚Œã¾ã—ãŸã€‚Ansible 5 ã§ã¯ã€community.kubernetes ã¯ã€ç¾åœ¨ã®ã™ã¹ã¦ã®ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã‚’ kubernetes.core ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã™ã‚‹ç©ºã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.kubernetes.`` ã§å§‹ã¾ã‚‹ FQCN ã‚’ ``kubernetes.core.`` ã«æ›´æ–°ã—ã¦ãã ã•ã„。Ansible 3.0.0 以é™ã€kubernetes.core 㯠Ansible ã«çµ„ã¿è¾¼ã¾ã‚Œã¦ã„る点ã«æ³¨æ„ã—ã¦ãã ã•ã„（https://github.com/ansible-community/community-topics/issues/22）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:294 -msgid "win_updates - Deprecated the ``filtered_reason`` return value for each filtered up in favour of ``filtered_reasons``. This has been done to show all the reasons why an update was filtered and not just the first reason." -msgstr "win_updates - フィルター処ç†ã•ã‚ŒãŸãã‚Œãžã‚Œã®``filtered_reason``戻り値ãŒéžæŽ¨å¥¨ã«ãªã‚Šã€``filtered_reasons``ãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚ã“ã‚Œã¯ã€æœ€åˆã®ç†ç”±ã ã‘ã§ãªãã€æ›´æ–°ãŒãƒ•ã‚£ãƒ«ã‚¿ãƒªãƒ³ã‚°ã•ã‚ŒãŸã™ã¹ã¦ã®ç†ç”±ã‚’示ã™ãŸã‚ã«è¡Œã‚ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:295 -msgid "win_updates - Deprecated the ``use_scheduled_task`` option as it is no longer used." -msgstr "win_updates - 使用ã•ã‚Œãªããªã£ãŸ ``use_scheduled_task`` オプションãŒéžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:296 -msgid "win_updates - Deprecated the ``whitelist`` and ``blacklist`` options in favour of ``accept_list`` and ``reject_list`` respectively to conform to the new standards used in Ansible for these types of options." -msgstr "win_updates - ``whitelist`` オプションãŠã‚ˆã³ ``blacklist`` オプションãŒéžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚オプションã®ç¨®é¡žã«ã¤ã„㦠Ansible ã§ä½¿ç”¨ã•ã‚Œã‚‹æ–°ã—ã„標準ã«æº–æ‹ ã™ã‚‹ãŸã‚ã«ãã‚Œãžã‚Œ ``accept_list`` 㨠``reject_list`` ãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:301 -msgid "ali_instance_info - marked removal version of deprecated parameters ``availability_zone`` and ``instance_names`` (https://github.com/ansible-collections/community.general/issues/2429)." -msgstr "ali_instance_info - éžæŽ¨å¥¨ã®ãƒ‘ラメーター``availability_zone``ã¨``instance_names``ã®å‰Šé™¤ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒç¤ºã•ã‚Œã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.general/issues/2429）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:302 -msgid "serverless - deprecating parameter ``functions`` because it was not used in the code (https://github.com/ansible-collections/community.general/pull/2845)." -msgstr "serverless - コードã§ä½¿ç”¨ã•ã‚Œã¦ã„ãªã„ãŸã‚パラメーター ``functions`` ã‚’éžæŽ¨å¥¨åŒ–（https://github.com/ansible-collections/community.general/pull/2845）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:307 -msgid "hashi_vault collection - support for Python 2 will be dropped in version ``2.0.0`` of ``community.hashi_vault`` (https://github.com/ansible-collections/community.hashi_vault/issues/81)." -msgstr "hashi_vault コレクション - Python 2 ã®ã‚µãƒãƒ¼ãƒˆãŒãƒãƒ¼ã‚¸ãƒ§ãƒ³``2.0.0``ã®``community.hashi_vault``ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.hashi_vault/issues/81).）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:310 -msgid "Porting Guide for v4.1.0" -msgstr "v4.1.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" - -#: ../../rst/porting_guides/porting_guide_4.rst:327 -msgid "Add custom_image module" -msgstr "custom_image モジュールã®è¿½åŠ " - -#: ../../rst/porting_guides/porting_guide_4.rst:337 -msgid "ome_firmware_baseline - Module supports check mode, and allows the modification and deletion of firmware baselines." -msgstr "ome_firmware_baseline - モジュールã¯ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã‚’サãƒãƒ¼ãƒˆã—ã€ãƒ•ã‚¡ãƒ¼ãƒ ウェアベースラインã®å¤‰æ›´ã‚„削除をå¯èƒ½ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:338 -msgid "ome_firmware_catalog - Module supports check mode, and allows the modification and deletion of firmware catalogs." -msgstr "ome_firmware_catalog - モジュールã¯ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã‚’サãƒãƒ¼ãƒˆã—ã€ãƒ•ã‚¡ãƒ¼ãƒ ウェアカタãƒã‚°ã®å¤‰æ›´ã‚„削除をå¯èƒ½ã«ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:343 -msgid "Improve ``fortios_configuration_fact`` to use multiple selectors concurrently." -msgstr "複数ã®ã‚»ãƒ¬ã‚¯ã‚¿ãƒ¼ã‚’åŒæ™‚ã«ä½¿ç”¨ã™ã‚‹ã‚ˆã†ã« ``fortios_configuration_fact`` を改善ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:344 -msgid "Support ``check_mode`` in all cofigurationAPI-based modules." -msgstr "ã™ã¹ã¦ã® cofigurationAPI ベースã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã® ``check_mode`` をサãƒãƒ¼ãƒˆã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:345 -msgid "Support filtering for fact gathering modules ``fortios_configuration_fact`` and ``fortios_monitor_fact``." -msgstr "ファクトåŽé›†ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``fortios_configuration_fact`` ãŠã‚ˆã³ ``fortios_monitor_fact`` ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒªãƒ³ã‚°ã‚’サãƒãƒ¼ãƒˆã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:346 -msgid "Support moving policy in ``firewall_central_snat_map``." -msgstr "``firewall_central_snat_map`` ã§ã®ç§»è¡Œãƒãƒªã‚·ãƒ¼ã®ã‚µãƒãƒ¼ãƒˆ" - -#: ../../rst/porting_guides/porting_guide_4.rst:347 -msgid "Unify schemas for monitor API." -msgstr "モニター API ã®ã‚¹ã‚ーマã®çµ±ä¸€" - -#: ../../rst/porting_guides/porting_guide_4.rst:352 -msgid "packages is now a required Python package and gets installed via Ansible 2.10+." -msgstr "パッケージãŒå¿…è¦ãª Python パッケージã«ãªã‚Šã€Ansible 2.10 以é™ã‹ã‚‰ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:360 -msgid "win_reboot - Removed ``shutdown_timeout`` and ``shutdown_timeout_sec`` which has not done anything since Ansible 2.5." -msgstr "win_reboot - ``shutdown_timeout`` ãŠã‚ˆã³ ``shutdown_timeout_sec`` を削除ã—ã¾ã—ãŸãŒã€Ansible 2.5 以é™ã¯å®Ÿè¡Œã•ã‚Œã¦ã„ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_4.rst:368 -msgid "win_reboot - Unreachable hosts can be ignored with ``ignore_errors: True``, this ability will be removed in a future version. Use ``ignore_unreachable: True`` to ignore unreachable hosts instead. - https://github.com/ansible-collections/ansible.windows/issues/62" -msgstr "win_reboot - ``ignore_errors: True`` ã§åˆ°é”ã§ããªã„ホストを無視ã§ãã¾ã™ã€‚ã“ã®æ©Ÿèƒ½ã¯ä»Šå¾Œã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚代ã‚ã‚Šã« ``ignore_unreachable: True`` を使用ã—ã¦ã€åˆ°é”ä¸èƒ½ãªãƒ›ã‚¹ãƒˆã‚’無視ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/ansible.windows/issues/62）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:378 -msgid "All inventory and vault scripts will be removed from community.general in version 4.0.0. If you are referencing them, please update your references to the new `contrib-scripts GitHub repository <https://github.com/ansible-community/contrib-scripts>`_ so your workflow will not break once community.general 4.0.0 is released (https://github.com/ansible-collections/community.general/pull/2697)." -msgstr "インベントリーãŠã‚ˆã³ vault スクリプトã¯ã™ã¹ã¦ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 4.0.0 ã® community.general ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚ãれらをå‚ç…§ã™ã‚‹å ´åˆã¯ã€æ–°ã—ã„ `contrib-scripts GitHub repository <https://github.com/ansible-community/contrib-scripts>`_ ã¸ã®å‚照を更新ã—ã¦ãã ã•ã„。ã“ã‚Œã«ã‚ˆã‚Šã€community.general 4.0.0 ãŒãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã¦ã‚‚ワークフãƒãƒ¼ãŒç ´æã™ã‚‹ã“ã¨ã¯ã‚ã‚Šã¾ã›ã‚“（https://github.com/ansible-collections/community.general/pull/2697）" - -#: ../../rst/porting_guides/porting_guide_4.rst:379 -msgid "The nios, nios_next_ip, nios_next_network lookup plugins, the nios documentation fragment, and the nios_host_record, nios_ptr_record, nios_mx_record, nios_fixed_address, nios_zone, nios_member, nios_a_record, nios_aaaa_record, nios_network, nios_dns_view, nios_txt_record, nios_naptr_record, nios_srv_record, nios_cname_record, nios_nsgroup, and nios_network_view module have been deprecated and will be removed from community.general 5.0.0. Please install the `infoblox.nios_modules <https://galaxy.ansible.com/infoblox/nios_modules>`_ collection instead and use its plugins and modules (https://github.com/ansible-collections/community.general/pull/2458)." -msgstr "niosã€nios_next_ipã€nios_next_networkルックアッププラグインã€niosドã‚ュメントフラグメントã€ãŠã‚ˆã³nios_host_recordã€nios_ptr_recordã€nios_mx_recordã€nios_fixed_addressã€nios_zoneã€nios_memberã€nios_a_recordã€nios_aaaa_recordã€nios_networkã€nios_dns_viewã€nios_txt_recordã€nios_naptr_recordã€nios_srv_recordã€nios_cname_recordã€nios_nsgroupã€ãŠã‚ˆã³ nios_network_view モジュールã¯éžæŽ¨å¥¨ã«ãªã‚Šã€community.general 5.0.0ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« `infoblox.nios_modules <https://galaxy.ansible.com/infoblox/nios_modules>`_ をインストールã—ã€ãã®ãƒ—ラグインã¨ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/2458）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:380 -msgid "The vendored copy of ``ipaddress`` will be removed in community.general 4.0.0. Please switch to ``ipaddress`` from the Python 3 standard library, or `from pypi <https://pypi.org/project/ipaddress/>`_, if your code relies on the vendored version of ``ipaddress`` (https://github.com/ansible-collections/community.general/pull/2459)." -msgstr "``ipaddress`` ã®ãƒ™ãƒ³ãƒ€ãƒ¼ã‚³ãƒ”ーã¯ã€community.general 4.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚Python 3 標準ライブラリーã‹ã‚‰ ``ipaddress`` ã«åˆ‡ã‚Šæ›¿ãˆã‚‹ã‹ã€ã‚³ãƒ¼ãƒ‰ãŒãƒ™ãƒ³ãƒ€ãƒ¼ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® ``ipaddress`` ã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ `from pypi <https://pypi.org/project/ipaddress/>`_ ã«åˆ‡ã‚Šæ›¿ãˆã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/2459。" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:6 +msgid "Ansible-core 2.12 Porting Guide" +msgstr "Ansible-core 2.12 移æ¤ã‚¬ã‚¤ãƒ‰" -#: ../../rst/porting_guides/porting_guide_4.rst:381 -msgid "linode - parameter ``backupsenabled`` is deprecated and will be removed in community.general 5.0.0 (https://github.com/ansible-collections/community.general/pull/2410)." -msgstr "linode - パラメーター``backupsenabled``ã¯éžæŽ¨å¥¨ã«ãªã‚Šã€community.general 5.0.0ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/2410）。" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:8 +msgid "This section discusses the behavioral changes between ``ansible-core`` 2.11 and ``ansible-core`` 2.12." +msgstr "ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€``ansible-core`` 2.11 ã‹ã‚‰ ``ansible-core`` 2.12 ã«ãŠã‘る動作ã®å¤‰æ›´ç‚¹ã‚’説明ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:382 -msgid "lxd inventory plugin - the plugin will require ``ipaddress`` installed when used with Python 2 from community.general 4.0.0 on. ``ipaddress`` is part of the Python 3 standard library, but can be installed for Python 2 from pypi (https://github.com/ansible-collections/community.general/pull/2459)." -msgstr "lxd inventory プラグイン - プラグイン㯠community.general 4.0.0 ã® Python 2 ã§ä½¿ç”¨ã™ã‚‹éš›ã« ``ipaddress`` をインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚``ipaddress`` 㯠Python 3 標準ライブラリーã®ä¸€éƒ¨ã§ã™ãŒã€pypi ã‹ã‚‰ Python 2 用ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ãã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/2459）。" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:12 +msgid "We suggest you read this page along with `ansible-core Changelog for 2.12 <https://github.com/ansible/ansible/blob/devel/changelogs/CHANGELOG-v2.12.rst>`_ to understand what updates you may need to make." +msgstr "å¿…è¦ãªæ›´æ–°ã«ã¤ã„ã¦ç†è§£ã™ã‚‹ã«ã¯ã€ã“ã®ãƒšãƒ¼ã‚¸ã¨ä½µã›ã¦ã€Œ`ansible-core Changelog for 2.12 <https://github.com/ansible/ansible/blob/devel/changelogs/CHANGELOG-v2.12.rst>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_4.rst:383 -msgid "scaleway_security_group_rule - the module will require ``ipaddress`` installed when used with Python 2 from community.general 4.0.0 on. ``ipaddress`` is part of the Python 3 standard library, but can be installed for Python 2 from pypi (https://github.com/ansible-collections/community.general/pull/2459)." -msgstr "scaleway_security_group_rule - モジュールã¯ã€community.general 4.0.0 ã® Python 2 ã§ä½¿ç”¨ã™ã‚‹éš›ã« ``ipaddress`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚``ipaddress`` 㯠Python 3 標準ライブラリーã®ä¸€éƒ¨ã§ã™ãŒã€pypi ã‹ã‚‰ Python 2 用ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ãã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/2459）。" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:22 +msgid "When calling tasks and setting ``async``, setting ``ANSIBLE_ASYNC_DIR`` under ``environment:`` is no longer valid. Instead, use the shell configuration variable ``async_dir``, for example by setting ``ansible_async_dir``:" +msgstr "タスクを呼ã³å‡ºã—㦠``async`` ã‚’è¨å®šã™ã‚‹å ´åˆã¯ã€``environment:`` 㧠``ANSIBLE_ASYNC_DIR`` ã®è¨å®šã¯æœ‰åŠ¹ã§ã¯ãªããªã‚Šã¾ã—ãŸã€‚代ã‚ã‚Šã«ã€``ansible_async_dir`` ã‚’è¨å®šã—ã¦ã‚·ã‚§ãƒ«è¨å®šå¤‰æ•° ``async_dir`` を使用ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:386 -msgid "inspur.sm" -msgstr "inspur.sm" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:38 +msgid "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``." +msgstr "``INTERPRETER_PYTHON_FALLBACK`` ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã¯ ``auto`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã—ãŸãŒã€``INTERPRETER_PYTHON_FALLBACK`` ã® Python インタープリターã®ãƒªã‚¹ãƒˆãŒã€Python 2 よりも Python 3 を優先ã™ã‚‹ã‚ˆã†ã«å¤‰æ›´ã•ã‚Œã¾ã—ãŸã€‚ã“れらã®å¤‰æ›´ã®çµ„ã¿åˆã‚ã›ã«ã‚ˆã‚Šã€æ–°ã—ã„デフォルト動作ã§ã¯ã€ãƒªãƒ¢ãƒ¼ãƒˆãƒ›ã‚¹ãƒˆã® Python 2 よりも Python 3 ãŒæš—黙的ã«å„ªå…ˆã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¾ã§ã€ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ—リター検出㧠Python 3 ãŒä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹ã¨ã„ã†éžæŽ¨å¥¨ã®è¦å‘Šã¯ã€Python 3 を使用ã—ã¾ã™ãŒã€ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ—リターã®æ¤œå‡ºãŒ ``/usr/bin/python`` ã«è¨å®šã•ã‚Œã¦ã„る状態ã§ã—ãŸã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:388 -msgid "add_ad_group - This feature will be removed in inspur.sm.add_ad_group 3.0.0. replaced with inspur.sm.ad_group." -msgstr "add_ad_group - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.add_ad_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.ad_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã‚‹äºˆå®šã§ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:40 +msgid "``INTERPRETER_PYTHON_FALLBACK`` can be changed from the default list of interpreters by setting the ``ansible_interpreter_python_fallback`` variable." +msgstr "``INTERPRETER_PYTHON_FALLBACK`` ã¯ã€``ansible_interpreter_python_fallback`` 変数をè¨å®šã—ã¦ã€ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ—リターã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãƒªã‚¹ãƒˆã‹ã‚‰å¤‰æ›´ã§ãã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:389 -msgid "add_ldap_group - This feature will be removed in inspur.sm.add_ldap_group 3.0.0. replaced with inspur.sm.ldap_group." -msgstr "add_ldap_group - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.add_ldap_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.ldap_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:42 +msgid "See :ref:`interpreter discovery documentation <interpreter_discovery>` for more details." +msgstr "詳細ã¯ã€:ref:`interpreter discovery documentation <interpreter_discovery>` ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_4.rst:390 -msgid "add_user - This feature will be removed in inspur.sm.add_user 3.0.0. replaced with inspur.sm.user." -msgstr "add_user - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.add_user 3.0.0. ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.user ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:48 +msgid "Python 3.8 on the controller node is a hard requirement for this release. The command line scripts will not function with a lower Python version." +msgstr "コントãƒãƒ¼ãƒ©ãƒ¼ãƒŽãƒ¼ãƒ‰ã® Python 3.8 ã¯ã€æœ¬ãƒªãƒªãƒ¼ã‚¹ã§ã¯ãƒãƒ¼ãƒ‰è¦ä»¶ã§ã™ã€‚コマンドラインスクリプトã¯ã€ã‚ˆã‚Šä½Žã„ Python ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã¯æ©Ÿèƒ½ã—ã¾ã›ã‚“。" -#: ../../rst/porting_guides/porting_guide_4.rst:391 -msgid "add_user_group - This feature will be removed in inspur.sm.add_user_group 3.0.0. replaced with inspur.sm.user_group." -msgstr "add_user_group - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.add_user_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.user_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:49 +msgid "``ansible-vault`` no longer supports ``PyCrypto`` and requires ``cryptography``." +msgstr "``ansible-vault`` 㯠``PyCrypto`` ã«å¯¾å¿œã—ãªããªã‚Šã€``cryptography`` ãŒå¿…è¦ãªããªã‚Šã¾ã—ãŸã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:392 -msgid "del_ad_group - This feature will be removed in inspur.sm.del_ad_group 3.0.0. replaced with inspur.sm.ad_group." -msgstr "del_ad_group - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.del_ad_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.ad_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:54 +msgid "Python 2.6 on the target node is deprecated in this release. ``ansible-core`` 2.13 will remove support for Python 2.6." +msgstr "ターゲットノード上㮠Python 2.6 ã¯æœ¬ãƒªãƒªãƒ¼ã‚¹ã§éžæŽ¨å¥¨ã¨ãªã‚Šã¾ã—ãŸã€‚``ansible-core`` 2.13 ã§ã¯ã€Python 2.6 ã®ã‚µãƒãƒ¼ãƒˆãŒå‰Šé™¤ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:393 -msgid "del_ldap_group - This feature will be removed in inspur.sm.del_ldap_group 3.0.0. replaced with inspur.sm.ldap_group." -msgstr "del_ldap_group - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.del_ldap_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.ldap_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:55 +msgid "Bare variables in conditionals: ``when`` conditionals no longer automatically parse string booleans such as ``\"true\"`` and ``\"false\"`` into actual booleans. Any variable containing a non-empty string is considered true. This was previously configurable with the ``CONDITIONAL_BARE_VARS`` configuration option (and the ``ANSIBLE_CONDITIONAL_BARE_VARS`` environment variable). This setting no longer has any effect. Users can work around the issue by using the ``|bool`` filter:" +msgstr "æ¡ä»¶ã®ãƒ™ã‚¢ãƒ¡ã‚¿ãƒ«å¤‰æ•°: ``when`` æ¡ä»¶ã¯ã€``\"true\"`` ã‚„ ``\"false\"`` ãªã©ã®æ–‡å—列ブール値を実際ã®ãƒ–ール値ã«è‡ªå‹•çš„ã«è§£æžã—ãªããªã‚Šã¾ã—ãŸã€‚空ã§ãªã„æ–‡å—列をå«ã‚€å¤‰æ•°ã¯ true ã¨è¦‹ãªã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ä»¥å‰ã¯ ``CONDITIONAL_BARE_VARS`` è¨å®šã‚ªãƒ—ション（ãŠã‚ˆã³ ``ANSIBLE_CONDITIONAL_BARE_VARS`` 環境変数）ã§è¨å®šå¯èƒ½ã§ã—ãŸã€‚ã“ã®è¨å®šã¯å½±éŸ¿ã¯ã‚ã‚Šã¾ã›ã‚“。``|bool`` フィルターを使用ã™ã‚‹ã“ã¨ã§å•é¡Œã‚’回é¿ã§ãã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:394 -msgid "del_user - This feature will be removed in inspur.sm.del_user 3.0.0. replaced with inspur.sm.user." -msgstr "del_user - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.del_user 3.0.0. ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.user ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:69 +msgid "The ``_remote_checksum()`` method in ``ActionBase`` is deprecated. Any action plugin using this method should use ``_execute_remote_stat()`` instead." +msgstr "``ActionBase`` ã® ``_remote_checksum()`` メソッドã¯éžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚ã“ã®ãƒ¡ã‚½ãƒƒãƒ‰ã‚’使用ã™ã‚‹ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ãƒ—ラグインã¯ã€ä»£ã‚ã‚Šã« ``_execute_remote_stat()`` を使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:395 -msgid "del_user_group - This feature will be removed in inspur.sm.del_user_group 3.0.0. replaced with inspur.sm.user_group." -msgstr "del_user_group - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.del_user_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.user_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:74 +msgid "``cron`` now requires ``name`` to be specified in all cases." +msgstr "``cron`` ã¯ã€ã™ã¹ã¦ã®ã‚±ãƒ¼ã‚¹ã§ ``name`` を指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:396 -msgid "edit_ad_group - This feature will be removed in inspur.sm.edit_ad_group 3.0.0. replaced with inspur.sm.ad_group." -msgstr "edit_ad_group - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.edit_ad_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.ad_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã‚‹äºˆå®šã§ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:75 +msgid "``cron`` no longer allows a ``reboot`` parameter. Use ``special_time: reboot`` instead." +msgstr "``cron`` ã¯ã€``reboot`` パラメーターãŒè¨±å¯ã•ã‚Œãªããªã‚Šã¾ã—ãŸã€‚代ã‚ã‚Šã« ``special_time: reboot`` を使用ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_4.rst:397 -msgid "edit_ldap_group - This feature will be removed in inspur.sm.edit_ldap_group 3.0.0. replaced with inspur.sm.ldap_group." -msgstr "edit_ldap_group - ã“ã®æ©Ÿèƒ½ã¯ã€inspur.sm.edit_ldap_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.ldap_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã‚‹äºˆå®šã§ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:76 +msgid "``hostname`` - On FreeBSD, the ``before`` result will no longer be ``\"temporarystub\"`` if permanent hostname file does not exist. It will instead be ``\"\"`` (empty string) for consistency with other systems." +msgstr "``hostname`` - FreeBSD ã§ã¯ã€æ°¸ç¶šçš„ãªãƒ›ã‚¹ãƒˆåファイルãŒå˜åœ¨ã—ãªã„å ´åˆã€``before`` ã®çµæžœã¯ ``\"temporarystub\"`` ã«ãªã‚‰ãªããªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã¯ã€ä»–ã®ã‚·ã‚¹ãƒ†ãƒ ã¨ã®æ•´åˆæ€§ã‚’ä¿ã¤ãŸã‚ã« ``\"\"`` （空ã®æ–‡å—列）ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:398 -msgid "edit_user - This feature will be removed in inspur.sm.edit_user 3.0.0. replaced with inspur.sm.user." -msgstr "edit_user - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.edit_user 3.0.0. ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.user ã«ç½®ãæ›ãˆã‚‰ã‚Œã‚‹äºˆå®šã§ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:77 +msgid "``hostname`` - On OpenRC and Solaris based systems, the ``before`` result will no longer be ``\"UNKNOWN\"`` if the permanent hostname file does not exist. It will instead be ``\"\"`` (empty string) for consistency with other systems." +msgstr "``hostname`` - OpenRC ãŠã‚ˆã³ Solaris ベースã®ã‚·ã‚¹ãƒ†ãƒ ã§ã¯ã€æ°¸ç¶šçš„ãªãƒ›ã‚¹ãƒˆåファイルãŒå˜åœ¨ã—ãªã„å ´åˆã€``before`` ã®çµæžœã¯ ``\"UNKNOWN\"`` ã«ãªã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€ä»–ã®ã‚·ã‚¹ãƒ†ãƒ ã¨ã®æ•´åˆæ€§ã‚’ä¿ã¤ãŸã‚ã« ``\"\"``（空ã®æ–‡å—列）ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:399 -msgid "edit_user_group - This feature will be removed in inspur.sm.edit_user_group 3.0.0. replaced with inspur.sm.user_group." -msgstr "edit_user_group: ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.edit_user_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.user_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã‚‹äºˆå®šã§ã™ã€‚" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:78 +msgid "``pip`` now uses the ``pip`` Python module installed for the Ansible module's Python interpreter, if available, unless ``executable`` or ``virtualenv`` were specified." +msgstr "``pip`` ã¯ã€``executable`` ã¾ãŸã¯ ``virtualenv`` ãŒæŒ‡å®šã•ã‚Œã¦ã„ãªã„é™ã‚Šã€Ansible モジュール㮠Python インタープリターã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚ŒãŸ ``pip`` Python モジュールを使用ã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:402 -msgid "Porting Guide for v4.0.0" -msgstr "v4.0.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:104 +msgid "``unique`` filter with Jinja2 < 2.10 is case-sensitive and now raise coherently an error if ``case_sensitive=False`` instead of when ``case_sensitive=True``." +msgstr "2.10 よりå‰ã® Jinja2 を使用ã™ã‚‹ ``unique`` フィルターã¯ã€å¤§æ–‡å—ã¨å°æ–‡å—ãŒåŒºåˆ¥ã•ã‚Œã€``case_sensitive=True`` ã§ã¯ãªã ``case_sensitive=False`` ã®å ´åˆã«ä¸€è²«ã—ã¦ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã—ã¦ã„ã¾ã—ãŸã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:408 -#: ../../rst/porting_guides/porting_guide_4.rst:429 -#: ../../rst/porting_guides/porting_guide_4.rst:482 -#: ../../rst/porting_guides/porting_guide_4.rst:586 -#: ../../rst/porting_guides/porting_guide_4.rst:712 -msgid "Ansible-core" -msgstr "Ansible-core" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:105 +msgid "Set theory filters (``intersect``, ``difference``, ``symmetric_difference`` and ``union``) are now case-sensitive. Explicitly use ``case_sensitive=False`` to keep previous behavior. Note: with Jinja2 < 2.10, the filters were already case-sensitive by default." +msgstr "ç†è«–フィルター（``intersect``ã€``difference``ã€``symmetric_difference``ã€ãŠã‚ˆã³ ``union``）ã®è¨å®šã¯ã€å¤§æ–‡å—ã¨å°æ–‡å—ãŒåŒºåˆ¥ã•ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚明示的㪠``case_sensitive=False`` を使用ã—ã¦ä»¥å‰ã®å‹•ä½œã‚’ç¶æŒã—ã¾ã™ã€‚2.10 よりå‰ã® Jinja2 ã§ã€ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã¯ã™ã§ã«å¤§æ–‡å—ã¨å°æ–‡å—を区別ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:410 -msgid "ansible-test - The ``pylint`` sanity test no longer correctly detects \"bad\" variable names for non-constants. See https://github.com/PyCQA/pylint/issues/3701 for additional details." -msgstr "ansible-test - ``pylint`` å¥å…¨æ€§ãƒ†ã‚¹ãƒˆã¯ã€éžåˆ¶ç´„ã®ãŸã‚\"bad\" 変数åã‚’æ£ã—ã検出ã—ãªããªã‚Šã¾ã—ãŸã€‚詳細ã¯ã€https://github.com/PyCQA/pylint/issues/3701 ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" +#: ../../rst/porting_guides/porting_guide_core_2.12.rst:106 +msgid "``password_hash``` now uses ``passlib`` defaults when an option is unspecified, e.g. ``bcrypt_sha256`` now default to the \"2b\" format and if the \"2a\" format is required it must be specified." +msgstr "``password_hash``` now uses ``passlib`` defaults when an option is unspecified, e.g. ``bcrypt_sha256`` ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã€Œ2bã€ãƒ•ã‚©ãƒ¼ãƒžãƒƒãƒˆã«ãªã‚Šã€ã€Œ2aã€ãƒ•ã‚©ãƒ¼ãƒžãƒƒãƒˆãŒå¿…è¦ãªå ´åˆã¯æŒ‡å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:423 -msgid "Modules for monitor API are not versioned yet." -msgstr "モニター API 用ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã¾ã ãƒãƒ¼ã‚¸ãƒ§ãƒ³åŒ–ã•ã‚Œã¦ã„ã¾ã›ã‚“。" +#: ../../rst/porting_guides/porting_guides.rst:5 +msgid "Ansible Porting Guides" +msgstr "Ansible 移æ¤ã‚¬ã‚¤ãƒ‰" -#: ../../rst/porting_guides/porting_guide_4.rst:431 -msgid "Made SCM collections be reinstalled regardless of ``--force`` being present." -msgstr "作æˆã•ã‚ŒãŸ SCM コレクションã¯ã€``--force`` ãŒå˜åœ¨ã™ã‚‹ã‹ã©ã†ã‹ã«é–¢ã‚らãšå†ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¾ã™ã€‚" +#: ../../rst/porting_guides/porting_guides.rst:7 +msgid "Ansible Porting Guides are maintained in the ``devel`` branch only. See `the devel Ansible Porting guides <https://docs.ansible.com/ansible/devel/porting_guides/porting_guides.html>`_ for up to date information." +msgstr "Ansible 移æ¤ã‚¬ã‚¤ãƒ‰ã¯ã€``devel`` ブランãƒã§ã®ã¿ç¶æŒã•ã‚Œã¾ã™ã€‚最新ã®æƒ…å ±ã¯ã€`the devel Ansible Porting guides <https://docs.ansible.com/ansible/devel/porting_guides/porting_guides.html>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_4.rst:432 -msgid "NetBSD virtualization facts (specifically ``ansible_virtualization_type``) now returns a more accurate value by checking the value of the ``machdep.hypervisor`` ``sysctl`` key. This change is breaking because in some cases previously, we would erroneously report ``xen`` even when the target is not running on Xen. This prevents that behavior in most cases. (https://github.com/ansible/ansible/issues/69352)" -msgstr "NetBSD 仮想化ファクト（具体的ã«ã¯ ``ansible_virtualization_type``）ã¯ã€``machdep.hypervisor`` ``sysctl`` ã‚ーã®å€¤ã‚’ãƒã‚§ãƒƒã‚¯ã™ã‚‹ã“ã¨ã§ã€ã‚ˆã‚Šæ£ç¢ºãªå€¤ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚以å‰ã¯ã€ã‚¿ãƒ¼ã‚²ãƒƒãƒˆãŒ Xen ã§å®Ÿè¡Œã—ã¦ã„ãªã„å ´åˆã§ã‚‚ ``xen``を誤ã£ã¦å ±å‘Šã—ã¦ã„ãŸãŸã‚ã€ã“ã®å¤‰æ›´ã¯é‡è¦ã§ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ã»ã¨ã‚“ã©ã®å ´åˆã€ãã®å‹•ä½œãŒé˜»æ¢ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible/ansible/issues/69352）。" +#~ msgid "We suggest you read this page along with the `ansible-core Changelog for 2.11 <https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst>`_ to understand what updates you may need to make." +#~ msgstr "" -#: ../../rst/porting_guides/porting_guide_4.rst:433 -msgid "Replaced the in-tree dependency resolver with an external implementation that pip >= 20.3 uses now by default — ``resolvelib``. (https://github.com/ansible/ansible/issues/71784)" -msgstr "ツリー内ã®ä¾å˜é–¢ä¿‚リゾルãƒãƒ¼ãŒã€pip> = 20.3ãŒãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ä½¿ç”¨ã™ã‚‹å¤–部実装``resolvelib``ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸï¼ˆhttps://github.com/ansible/ansible/issues/71784。" +#~ msgid "The configuration system now validates the ``choices`` field, so any settings that currently violate it and are currently ignored will now cause an error. For example, `ANSIBLE_COLLECTIONS_ON_ANSIBLE_VERSION_MISMATCH=0` will now cause an error (valid chioces are 'ignore', 'warn' or 'error'." +#~ msgstr "" -#: ../../rst/porting_guides/porting_guide_4.rst:434 -msgid "The ``meta`` module now supports tags for user-defined tasks. Internal ``meta`` tasks continue to always run. (https://github.com/ansible/ansible/issues/64558)" -msgstr "``meta`` モジュールã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼å®šç¾©ã®ã‚¿ã‚¹ã‚¯ã®ã‚¿ã‚°ã‚’サãƒãƒ¼ãƒˆã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚内部 ``meta`` タスクã¯å¸¸ã«å®Ÿè¡Œã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible/ansible/issues/64558）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:440 -msgid "Removed vendored ipaddress package from collection. If you use ansible_collections.ansible.netcommon.plugins.module_utils.compat.ipaddress in your collection, you will need to change this to import ipaddress instead. If your content using ipaddress supports Python 2.7, you will additionally need to make sure that the user has the ipaddress package installed. Please refer to https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_best_practices.html#importing-and-using-shared-code to see how to safely import external packages that may be missing from the user's system A backport of ipaddress for Python 2.7 is available at https://pypi.org/project/ipaddress/" -msgstr "コレクションã‹ã‚‰ãƒ™ãƒ³ãƒ€ãƒ¼åŒ–ã•ã‚ŒãŸ ipaddress パッケージãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚コレクションã®ansible_collections.ansible.netcommon.plugins.module_utils.compat.ipaddress を使用ã™ã‚‹å ´åˆã¯ã€ä»£ã‚ã‚Šã« ipaddress をインãƒãƒ¼ãƒˆã™ã‚‹ãŸã‚ã«ã“れを変更ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ipaddress を使用ã™ã‚‹ã‚³ãƒ³ãƒ†ãƒ³ãƒ„㌠Python 2.7 ã«å¯¾å¿œã—ã¦ã„ã‚‹å ´åˆã¯ã€ã•ã‚‰ã«ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒ ipaddress パッケージãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ユーザーã®ã‚·ã‚¹ãƒ†ãƒ A ã«æ¬ è½ã—ã¦ã„ã‚‹å¯èƒ½æ€§ã®ã‚る外部パッケージを安全ã«ã‚¤ãƒ³ãƒãƒ¼ãƒˆã™ã‚‹æ–¹æ³•ã«ã¤ã„ã¦ã¯ã€https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_best_practices.html#importing-and-using-shared-codeã‚’å‚ç…§ã—ã¦ãã ã•ã„。Python 2.7用ã®ipaddressã®ãƒãƒƒã‚¯ãƒãƒ¼ãƒˆã¯ã€https://pypi.org/project/ipaddress/ã§åˆ©ç”¨ã§ãã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:450 -msgid "If you use Ansible 2.9 and these plugins or modules from this collection, community.general 3.0.0 results in errors when trying to use the DellEMC content by FQCN, like ``community.general.idrac_firmware``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``dellemc.openmanage.idrac_firmware`` for the previous example) and to make sure that you have ``dellemc.openmanage`` installed." -msgstr "Ansible 2.9 ã¨ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒ—ラグインやモジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 3.0.0 ã§ã¯ã€``community.general.idrac_firmware`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ DellEMC コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (å‰ã®ä¾‹ã§ã¯ ``dellemc.openmanage.idrac_firmware``) を使用ã—ã€``dellemc.openmanage`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:453 -msgid "If you use ansible-base 2.10 or newer and did not install Ansible 4.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install the ``dellemc.openmanage`` collection if you are using any of these plugins or modules. While ansible-base 2.10 or newer can use the redirects that community.general 3.0.0 adds, the collection they point to (such as dellemc.openmanage) must be installed for them to work." -msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 4.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€ã“ã®ãƒ—ラグインã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``dellemc.openmanage`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 3.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (dellemc.openmanage ãªã©) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" - -#: ../../rst/porting_guides/porting_guide_4.rst:455 -msgid "gitlab_deploy_key - if for an already existing key title a different public key was given as parameter nothing happened, now this changed so that the public key is updated to the new value (https://github.com/ansible-collections/community.general/pull/1661)." -msgstr "gitlab_deploy_key - æ—¢å˜ã®éµã‚¿ã‚¤ãƒˆãƒ«ã«å¯¾ã—ã¦ã€ãƒ‘ラメーターã¨ã—ã¦åˆ¥ã®å…¬é–‹éµãŒä½•ã‚‚èµ·ã“らãªã‹ã£ãŸå ´åˆã€ã“ã‚ŒãŒå¤‰æ›´ã•ã‚Œã€å…¬é–‹éµãŒæ–°ã—ã„値ã«æ›´æ–°ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1661）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:456 -msgid "java_keystore - instead of failing, now overwrites keystore if the alias (name) is changed. This was originally the intended behavior, but did not work due to a logic error. Make sure that your playbooks and roles do not depend on the old behavior of failing instead of overwriting (https://github.com/ansible-collections/community.general/issues/1671)." -msgstr "java_keystore - 失敗ã™ã‚‹ä»£ã‚ã‚Šã«ã€ã‚¨ã‚¤ãƒªã‚¢ã‚¹ï¼ˆåå‰ï¼‰ãŒå¤‰æ›´ã—ãŸå ´åˆã«ã‚ーストアを上書ãã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã¯å…ƒã€…æ„図ã•ã‚ŒãŸå‹•ä½œã§ã—ãŸãŒã€è«–ç†ã‚¨ãƒ©ãƒ¼ã®ãŸã‚ã«æ©Ÿèƒ½ã—ã¾ã›ã‚“ã§ã—ãŸã€‚Playbook ã¨ãƒãƒ¼ãƒ«ãŒã€ä¸Šæ›¸ãã™ã‚‹ä»£ã‚ã‚Šã«å¤±æ•—ã™ã‚‹ã¨ã„ã†å¤ã„動作ã«ä¾å˜ã—ã¦ã„ãªã„ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/issues/1671）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:457 -msgid "java_keystore - instead of failing, now overwrites keystore if the passphrase is changed. Make sure that your playbooks and roles do not depend on the old behavior of failing instead of overwriting (https://github.com/ansible-collections/community.general/issues/1671)." -msgstr "java_keystore - 失敗ã™ã‚‹ä»£ã‚ã‚Šã«ã€ãƒ‘スフレーズãŒå¤‰æ›´ã—ãŸå ´åˆã«ã‚ーストアを上書ãã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚Playbook ã¨ãƒãƒ¼ãƒ«ãŒã€ä¸Šæ›¸ãã™ã‚‹ä»£ã‚ã‚Šã«å¤±æ•—ã™ã‚‹ã¨ã„ã†å¤ã„動作ã«ä¾å˜ã—ã¦ã„ãªã„ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/issues/1671）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:458 -msgid "one_image - use pyone instead of python-oca (https://github.com/ansible-collections/community.general/pull/2032)." -msgstr "one_image - python-oca ã®ä»£ã‚ã‚Šã« pyone を使用ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/2032）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:464 -msgid "Generic FortiOS Module - FOS module to issue generic request with Ansible." -msgstr "汎用 FortiOS モジュール - Ansible ã§æ±Žç”¨è¦æ±‚を発行ã™ã‚‹ãŸã‚ã® FOS モジュール。" - -#: ../../rst/porting_guides/porting_guide_4.rst:465 -msgid "Support for FOS Monitor API - several modules are new for monitor API." -msgstr "FOS Monitor API ã®ã‚µãƒãƒ¼ãƒˆ - 複数ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒãƒ¢ãƒ‹ã‚¿ãƒ¼ API 用ã«æ–°ãŸã«è¿½åŠ ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:466 -msgid "Unified Collection - The fortios collection itself will be adapting any FOS platforms." -msgstr "çµ±åˆã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ - fortios コレクション自体ãŒã€FOS プラットフォームã«é©å¿œã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:471 -msgid "auth field now required for anything other than Basic authentication" -msgstr "Basic èªè¨¼ä»¥å¤–ã®ã™ã¹ã¦ã®ãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ã«èªè¨¼ãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ãŒå¿…è¦ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:476 -msgid "All role variables are now prefixed with ``foreman_`` to avoid clashes with similarly named variables from roles outside this collection." -msgstr "ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³å¤–ã®ãƒãƒ¼ãƒ«ã‹ã‚‰ã®åŒæ§˜ã®åå‰ã®å¤‰æ•°ã¨ã®è¡çªã‚’回é¿ã™ã‚‹ãŸã‚ã€ã™ã¹ã¦ã®ãƒãƒ¼ãƒ«å¤‰æ•°ã«ã¯ ``foreman_`` ã®ãƒ—レフィックスãŒä»˜ã‘られã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:484 -msgid "A collection can be reinstalled with new version requirements without using the ``--force`` flag. The collection's dependencies will also be updated if necessary with the new requirements. Use ``--upgrade`` to force transitive dependency updates." -msgstr "コレクションã¯ã€``--force`` フラグを使用ã›ãšã«ã€æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®è¦ä»¶ã§å†ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ãã¾ã™ã€‚ã¾ãŸã€æ–°ã—ã„è¦ä»¶ã§å¿…è¦ãªå ´åˆã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ä¾å˜é–¢ä¿‚ã‚‚æ›´æ–°ã•ã‚Œã¾ã™ã€‚``--upgrade`` を使用ã—ã¦ã€æŽ¨ç§»çš„ãªä¾å˜é–¢ä¿‚ã®æ›´æ–°ã‚’強制ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:485 -msgid "AnsibleModule - use ``ArgumentSpecValidator`` class for validating argument spec and remove private methods related to argument spec validation. Any modules using private methods should now use the ``ArgumentSpecValidator`` class or the appropriate validation function." -msgstr "AnsibleModule - 引数仕様を検証ã™ã‚‹ãŸã‚ã« ``ArgumentSpecValidator`` クラスを使用ã—ã€å¼•æ•°ä»•æ§˜ã®æ¤œè¨¼ã«é–¢é€£ã™ã‚‹ãƒ—ライベートメソッドを削除ã—ã¾ã™ã€‚プライベートメソッドを使用ã™ã‚‹ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€``ArgumentSpecValidator`` クラスã¾ãŸã¯é©åˆ‡ãªæ¤œè¨¼æ©Ÿèƒ½ã‚’使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:486 -msgid "Declared ``resolvelib >= 0.5.3, < 0.6.0`` a direct dependency of ansible-core. Refs: - https://github.com/sarugaku/resolvelib - https://pypi.org/p/resolvelib - https://pradyunsg.me/blog/2020/03/27/pip-resolver-testing" -msgstr "ansible-core ã®ç›´æŽ¥ã®ä¾å˜é–¢ä¿‚``resolvelib >= 0.5.3, < 0.6.0`` ãŒå®£è¨€ã•ã‚Œã¾ã™ã€‚https://github.com/sarugaku/resolvelibã€https://pypi.org/p/resolvelibã€https://pradyunsg.me/blog/2020/03/27/pip-resolver-testing ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_4.rst:491 -msgid "It became possible to install Ansible Collections from local folders and namespaces folder similar to SCM structure with multiple collections." -msgstr "複数ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’æŒã¤ SCM æ§‹é€ ã¨åŒæ§˜ã«ã€ãƒãƒ¼ã‚«ãƒ«ãƒ•ã‚©ãƒ«ãƒ€ãƒ¼ãŠã‚ˆã³ namespace フォルダーã‹ã‚‰ Ansible Collections をインストールã§ãるよã†ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:492 -msgid "It became possible to upgrade Ansible collections from Galaxy servers using the ``--upgrade`` option with ``ansible-galaxy collection install``." -msgstr "``ansible-galaxy collection install`` 㧠``--upgrade`` オプションを使用ã—ã¦ã€Galaxy サーãƒãƒ¼ã‹ã‚‰ Ansible コレクションをアップグレードã§ãるよã†ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:493 -msgid "Support for role argument specification validation at role execution time. When a role contains an argument spec, an implicit validation task is inserted at the start of role execution." -msgstr "ãƒãƒ¼ãƒ«å®Ÿè¡Œæ™‚ã«ãƒãƒ¼ãƒ«å¼•æ•°ã®ä»•æ§˜æ¤œè¨¼ã®ã‚µãƒãƒ¼ãƒˆã€‚ãƒãƒ¼ãƒ«ã«å¼•æ•°ã®ä»•æ§˜ãŒå«ã¾ã‚Œã‚‹å ´åˆã¯ã€æš—黙的ãªæ¤œè¨¼ã‚¿ã‚¹ã‚¯ãŒãƒãƒ¼ãƒ«å®Ÿè¡Œã®é–‹å§‹æ™‚ã«æŒ¿å…¥ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:494 -msgid "add ``ArgumentSpecValidator`` class for validating parameters against an argument spec outside of ``AnsibleModule`` (https://github.com/ansible/ansible/pull/73335)" -msgstr "``AnsibleModule`` (https://github.com/ansible/ansible/pull/73335) ã«å«ã¾ã‚Œãªã„引数仕様ã«å¯¾ã—ã¦ãƒ‘ラメーターを検証ã™ã‚‹ ``ArgumentSpecValidator`` ã‚¯ãƒ©ã‚¹ã‚’è¿½åŠ ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:500 -msgid "Remove deprecated connection arguments from netconf_config" -msgstr "netconf_config ã‹ã‚‰éžæŽ¨å¥¨ã®æŽ¥ç¶šå¼•æ•°ã‚’削除" - -#: ../../rst/porting_guides/porting_guide_4.rst:503 -msgid "arista.eos" -msgstr "arista.eos" - -#: ../../rst/porting_guides/porting_guide_4.rst:505 -msgid "Requires ansible.netcommon v2.0.0+ to support `ansible_network_single_user_mode` and `ansible_network_import_modules` - Please refer to ansible.netcommon `changelog <https://github.com/ansible-collections/ansible.netcommon/blob/main/changelogs/CHANGELOG.rst#ansible-netcommon-collection-release-notes>`_ for more details." -msgstr "`ansible_network_single_user_mode` ãŠã‚ˆã³ `ansible_network_import_modules` をサãƒãƒ¼ãƒˆã™ã‚‹ã«ã¯ã€ansible.netcommon v2.0.0 以é™ãŒå¿…è¦ã§ã™ã€‚詳細ã¯ã€ansible.netcommon ã® `changelog <https://github.com/ansible-collections/ansible.netcommon/blob/main/changelogs/CHANGELOG.rst#ansible-netcommon-collection-release-notes>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_4.rst:508 -msgid "cisco.asa" -msgstr "cisco.asa" - -#: ../../rst/porting_guides/porting_guide_4.rst:510 -msgid "Please refer to ansible.netcommon `changelog <https://github.com/ansible-collections/ansible.netcommon/blob/main/changelogs/CHANGELOG.rst#ansible-netcommon-collection-release-notes>` for more details." -msgstr "詳細ã¯ã€ansible.netcommon ã® `changelog <https://github.com/ansible-collections/ansible.netcommon/blob/main/changelogs/CHANGELOG.rst#ansible-netcommon-collection-release-notes>` ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_4.rst:511 -#: ../../rst/porting_guides/porting_guide_4.rst:517 -#: ../../rst/porting_guides/porting_guide_4.rst:523 -#: ../../rst/porting_guides/porting_guide_4.rst:530 -#: ../../rst/porting_guides/porting_guide_4.rst:561 -msgid "Requires ansible.netcommon v2.0.0+ to support `ansible_network_single_user_mode` and `ansible_network_import_modules`." -msgstr "`ansible_network_single_user_mode` ãŠã‚ˆã³ `ansible_network_import_modules` をサãƒãƒ¼ãƒˆã™ã‚‹ã«ã¯ã€ansible.netcommon v2.0.0 以é™ãŒå¿…è¦ã§ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:516 -#: ../../rst/porting_guides/porting_guide_4.rst:522 -#: ../../rst/porting_guides/porting_guide_4.rst:529 -#: ../../rst/porting_guides/porting_guide_4.rst:560 -#: ../../rst/porting_guides/porting_guide_4.rst:578 -msgid "Please refer to ansible.netcommon `changelog <https://github.com/ansible-collections/ansible.netcommon/blob/main/changelogs/CHANGELOG.rst#ansible-netcommon-collection-release-notes>`_ for more details." -msgstr "詳細ã¯ã€ansible.netcommon `changelog <https://github.com/ansible-collections/ansible.netcommon/blob/main/changelogs/CHANGELOG.rst#ansible-netcommon-collection-release-notes>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_4.rst:524 -#: ../../rst/porting_guides/porting_guide_4.rst:580 -msgid "ipaddress is no longer in ansible.netcommon. For Python versions without ipaddress (< 3.0), the ipaddress package is now required." -msgstr "ipaddress 㯠ansible.netcommon ã§ã¯ãªããªã‚Šã¾ã—ãŸã€‚ipaddress (< 3.0) ã®ãªã„ Python ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã¯ã€ipaddress パッケージãŒå¿…è¦ã«ãªã‚Šã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:540 -msgid "mysql_replication - add deprecation warning that the ``Is_Slave`` and ``Is_Master`` return values will be replaced with ``Is_Primary`` and ``Is_Replica`` in ``community.mysql`` 3.0.0 (https://github.com/ansible-collections/community.mysql/pull/147)." -msgstr "mysql_replication - ``Is_Slave`` ãŠã‚ˆã³ ``Is_Master`` ã®æˆ»ã‚Šå€¤ãŒ ``community.mysql`` 3.0.0 ã® ``Is_Primary`` ãŠã‚ˆã³ ``Is_Replica`` ã«ç½®ãæ›ãˆã‚‰ã‚ŒãŸã“ã¨ã‚’示ã™éžæŽ¨å¥¨ã®è¦å‘Šã‚’è¿½åŠ ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.mysql/pull/147）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:541 -msgid "mysql_replication - the choices of the ``state`` option containing ``master`` will be finally replaced with the alternative ``primary`` choices in ``community.mysql`` 3.0.0, add deprecation warnings (https://github.com/ansible-collections/community.mysql/pull/150)." -msgstr "mysql_replication - ``master`` ãŒå«ã¾ã‚Œã‚‹ ``state`` オプションã®é¸æŠžãŒã€æœ€çµ‚çš„ã« ``community.mysql`` 3.0.0 ã®ä»£æ›¿ ``primary`` ã®é¸æŠžè‚¢ã«ç½®ãæ›ãˆã‚‰ã‚Œã€éžæŽ¨å¥¨ã®è¦å‘Šã‚’è¿½åŠ ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.mysql/pull/150）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:543 -msgid "mysql_replication - the return value ``Is_Slave`` and ``Is_Master`` will be replaced with ``Is_Replica`` and ``Is_Primary`` in ``community.mysql`` 3.0.0 (https://github.com/ansible-collections/community.mysql/issues/145)." -msgstr "mysql_replication - 戻り値 ``Is_Slave`` ãŠã‚ˆã³ ``Is_Master`` ã¯ã€``community.mysql`` 3.0.0 㧠``Is_Replica`` ãŠã‚ˆã³ ``Is_Primary`` ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.mysql/issues/145）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:545 -msgid "mysql_replication - the word ``master`` in messages returned by the module will be replaced with ``primary`` in ``community.mysql`` 3.0.0 (https://github.com/ansible-collections/community.mysql/issues/145)." -msgstr "mysql_replication - モジュールã«ã‚ˆã£ã¦è¿”ã•ã‚ŒãŸãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã®å˜èªž ``master`` ã¯ã€``community.mysql`` 3.0.0 㧠``primary`` ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.mysql/issues/145）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:546 -msgid "mysql_replication - the word ``slave`` in messages returned by the module replaced with ``replica`` (https://github.com/ansible-collections/community.mysql/issues/98)." -msgstr "mysql_replication - ``replica`` ã«ç½®ãæ›ãˆã‚‰ã‚ŒãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚ˆã£ã¦è¿”ã•ã‚ŒãŸãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã®å˜èªž ``slave`` ã§ã™ï¼ˆhttps://github.com/ansible-collections/community.mysql/issues/98）。" - -#: ../../rst/porting_guides/porting_guide_4.rst:552 -msgid "New module fortios_configuration_fact" -msgstr "æ–°ã—ã„モジュール fortios_configuration_fact" - -#: ../../rst/porting_guides/porting_guide_4.rst:553 -msgid "New module fortios_json_generic" -msgstr "æ–°ã—ã„モジュール fortios_json_generic" - -#: ../../rst/porting_guides/porting_guide_4.rst:554 -msgid "New module fortios_monitor" -msgstr "æ–°ã—ã„モジュール fortios_monitor" - -#: ../../rst/porting_guides/porting_guide_4.rst:555 -msgid "New module fortios_monitor_fact" -msgstr "æ–°ã—ã„モジュール fortios_monitor_fact" - -#: ../../rst/porting_guides/porting_guide_4.rst:571 -msgid "refactored client to inherit from AnsibleModule" -msgstr "AnsibleModule ã‹ã‚‰ç¶™æ‰¿ã™ã‚‹ãƒªãƒ•ã‚¡ã‚¯ã‚¿ãƒ¼ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆ" - -#: ../../rst/porting_guides/porting_guide_4.rst:572 -msgid "supports OpenID Connect authentication protocol" -msgstr "OpenID Connect ã«ã‚ˆã‚‹èªè¨¼ãƒ—ãƒãƒˆã‚³ãƒ«ã®ã‚µãƒãƒ¼ãƒˆ" - -#: ../../rst/porting_guides/porting_guide_4.rst:573 -msgid "supports bearer tokens for authentication" -msgstr "èªè¨¼ç”¨ã®ãƒ™ã‚¢ãƒ©ãƒ¼ãƒˆãƒ¼ã‚¯ãƒ³ã®ã‚µãƒãƒ¼ãƒˆ" - -#: ../../rst/porting_guides/porting_guide_4.rst:579 -msgid "Requires ansible.netcommon v2.0.0+ to support `ansible_network_single_user_mode` and `ansible_network_import_modules`" -msgstr "`ansible_network_single_user_mode` をサãƒãƒ¼ãƒˆã™ã‚‹ã«ã¯ã€ansible.netcommon v2.0.0 以é™ãŠã‚ˆã³ `ansible_network_import_modules` ãŒå¿…è¦ã§ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:588 -msgid "Removed `SharedPluginLoaderObj` class from ansible.plugins.strategy. It was deprecated in favor of using the standard plugin loader." -msgstr "標準ã®ãƒ—ラグインãƒãƒ¼ãƒ€ãƒ¼ã®ä½¿ç”¨ãŒæŽ¡ç”¨ã•ã‚ŒãŸãŸã‚ã€ansible.plugins.strategy ã‹ã‚‰ `SharedPluginLoaderObj` クラスãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:589 -msgid "Removed `_get_item()` alias from callback plugin base class which had been deprecated in favor of `_get_item_label()`." -msgstr "éžæŽ¨å¥¨ã«ãªã£ã¦ã„㟠`_get_item()` エイリアスをコールãƒãƒƒã‚¯ãƒ—ラグインベースクラスã‹ã‚‰å‰Šé™¤ã•ã‚Œã€`_get_item_label()` ãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:590 -msgid "The \"user\" parameter was previously deprecated and is now removed in favor of \"scope\"" -msgstr "「userã€ãƒ‘ラメーターã¯éžæŽ¨å¥¨ã¨ãªã£ã¦ãŠã‚Šã€å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚「scopeã€ãŒæŽ¡ç”¨ã•ã‚Œã¦ã„ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:591 -msgid "The deprecated ``ansible.constants.BECOME_METHODS`` has been removed." -msgstr "éžæŽ¨å¥¨ã® ``ansible.constants.BECOME_METHODS`` ã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:592 -msgid "The deprecated ``ansible.constants.get_config()`` has been removed." -msgstr "éžæŽ¨å¥¨ã® ``ansible.constants.get_config()`` ã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:593 -msgid "The deprecated ``ansible.constants.mk_boolean()`` has been removed." -msgstr "éžæŽ¨å¥¨ã® ``ansible.constants.mk_boolean()`` ã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:594 -msgid "`with_*` loops are no longer optimized for modules whose `name` parameters can take lists (mostly package managers). Use `name` instead of looping over individual names with `with_items` and friends." -msgstr "`with_*` ループã¯ã€`name` パラメーターãŒãƒªã‚¹ãƒˆï¼ˆã»ã¨ã‚“ã©ã®å ´åˆã¯ãƒ‘ッケージマãƒãƒ¼ã‚¸ãƒ£ãƒ¼ï¼‰ã‚’å–ã‚‹ã“ã¨ãŒã§ãるモジュールå‘ã‘ã«æœ€é©åŒ–ã•ã‚Œãªããªã‚Šã¾ã—ãŸã€‚`with_items` ãŠã‚ˆã³ãƒ•ãƒ¬ãƒ³ã‚ºã‚’使用ã—ã¦å€‹åˆ¥åã«ãƒ«ãƒ¼ãƒ—ã™ã‚‹ä»£ã‚ã‚Šã«ã€`name` を使用ã—ã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:599 -msgid "The ``ome_device_info``, ``idrac_firmware`` and ``idrac_server_config_profile`` modules have now been migrated from community.general to the `dellemc.openmanage <https://galaxy.ansible.com/dellemc/openmanage>`_ Ansible collection. If you use ansible-base 2.10 or newer, redirections have been provided." -msgstr "``ome_device_info``ã€``idrac_firmware``ã€ãŠã‚ˆã³ ``idrac_server_config_profile`` モジュールã¯ã€community.general ã‹ã‚‰ `dellemc.openmanage <https://galaxy.ansible.com/dellemc/openmanage>`_ Ansibleコレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/porting_guides/porting_guide_4.rst:602 -msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.idrac_firmware`` → ``dellemc.openmanage.idrac_firmware``) and make sure to install the dellemc.openmanage collection." -msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.general.idrac_firmware`` →``dellemc.openmanage.idrac_firmware``) を調整ã—ã€dellemc.openmanage コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" - -#: ../../rst/porting_guides/porting_guide_4.rst:603 -msgid "The deprecated ali_instance_facts module has been removed. Use ali_instance_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ali_instance_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ali_instance_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "Due to a scheduling conflict, the latest version of Ansible 2.10 (2.10.7) has a few collections which are newer than Ansible 3.0.0. Ansible 3.1.0 will contain updated versions of those collections." +#~ msgstr "スケジュールã®éƒ½åˆä¸Šã€Ansible 2.10 ã®æœ€æ–°ç‰ˆ (2.10.7) ã«ã¯ã€Ansible 3.0.0 よりも新ã—ã„コレクションãŒã„ãã¤ã‹ã‚ã‚Šã¾ã™ã€‚Ansible 3.1.0 ã«ã¯ã€ã“れらã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ã‚¢ãƒƒãƒ—デート版ãŒå«ã¾ã‚Œã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:604 -msgid "The deprecated gluster_heal_info module has been removed. Use gluster.gluster.gluster_heal_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® gluster_heal_info モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« gluster.gluster.gluster_heal_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "Python 3.8 on the controller node is a soft requirement for this release. ``ansible-core`` 2.11 will continue to work with the same versions of Python that ``ansible-base`` 2.10 worked with, however it will emit a warning when running on a controller node with a Python version less than 3.8. This warning can be disabled by setting ``ANSIBLE_CONTROLLER_PYTHON_WARNING=False`` in your environment. ``ansible-core`` 2.12 will require Python 3.8 or greater." +#~ msgstr "コントãƒãƒ¼ãƒ©ãƒ¼ãƒŽãƒ¼ãƒ‰ã® Python 3.8 ã¯ã€æœ¬ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã‚½ãƒ•ãƒˆè¦ä»¶ã§ã™ã€‚``ansible-core`` 2.11 ã¯ã€``ansible-base`` 2.10 ãŒå‹•ä½œã—ãŸã®ã¨åŒã˜ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Python ã§å¼•ã続ã機能ã—ã¾ã™ãŒã€Python ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒ 3.8 未満ã®ã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©ãƒ¼ãƒŽãƒ¼ãƒ‰ã§å®Ÿè¡Œã™ã‚‹ã¨è¦å‘ŠãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚ã“ã®è¦å‘Šã¯ã€ãŠä½¿ã„ã®ç’°å¢ƒã« ``ANSIBLE_CONTROLLER_PYTHON_WARNING=False`` ã‚’è¨å®šã—ã¦ç„¡åŠ¹ã«ã§ãã¾ã™ã€‚``ansible-core`` 2.12 ã®å ´åˆã¯ Python 3.8 以é™ãŒå¿…è¦ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:605 -msgid "The deprecated gluster_peer module has been removed. Use gluster.gluster.gluster_peer instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® gluster_peer モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« gluster.gluster.gluster_peer を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "The configuration system now validates the ``choices`` field, so any settings that currently violate it and are currently ignored will now cause an error. For example, `ANSIBLE_COLLECTIONS_ON_ANSIBLE_VERSION_MISMATCH=0` will now cause an error (valid choices are 'ignore', 'warn' or 'error')." +#~ msgstr "è¨å®šã‚·ã‚¹ãƒ†ãƒ 㯠``choices`` フィールドを検証ã™ã‚‹ãŸã‚ã€ç¾åœ¨ãã‚Œã«é•åã—ã¦ã„ã‚‹è¨å®šãŒã‚ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ãŒç”Ÿã˜ã¾ã™ã€‚ãŸã¨ãˆã°ã€`ANSIBLE_COLLECTIONS_ON_ANSIBLE_VERSION_MISMATCH=0` ã‚’é¸æŠžã™ã‚‹ã¨ã€ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã—ã¾ã™ (有効ãªé¸æŠžè‚¢ã¯ã€Œignoreã€ã€ã€Œwarnã€ã€ã¾ãŸã¯ã€Œerrorã€ã§ã™)。" -#: ../../rst/porting_guides/porting_guide_4.rst:606 -msgid "The deprecated gluster_volume module has been removed. Use gluster.gluster.gluster_volume instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® gluster_volume モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« gluster.gluster.gluster_volume を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）" +#~ msgid "In Ansible 2.10, many plugins and modules have migrated to Collections on `Ansible Galaxy <https://galaxy.ansible.com>`_. Your playbooks should continue to work without any changes. We recommend you start using the fully-qualified collection name (FQCN) in your playbooks as the explicit and authoritative indicator of which collection to use as some collections may contain duplicate module names. You can search the `index of all modules <https://docs.ansible.com/ansible/2.10/collections/index_module.html>`_ to find the collection a module has been relocated to." +#~ msgstr "Ansible 2.10 ã§ã¯ã€å¤šãã®ãƒ—ラグインやモジュールãŒã€`Ansible Galaxy <https://galaxy.ansible.com>`_ ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«ç§»è¡Œã—ã¾ã—ãŸã€‚ãŠä½¿ã„ã® Playbook ã¯ä½•ã®å¤‰æ›´ã‚‚ãªã継続ã—ã¦ãŠä½¿ã„ã„ãŸã ã‘ã¾ã™ã€‚一部ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«åãŒé‡è¤‡ã—ã¦ã„ã‚‹å¯èƒ½æ€§ãŒã‚ã‚‹ãŸã‚ã€ã©ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’使用ã™ã‚‹ã‹ã®æ˜Žç¤ºçš„ã‹ã¤æ¨©å¨çš„ãªæŒ‡æ¨™ã¨ã—ã¦ã€Playbook ã§ã€å®Œå…¨ä¿®é£¾ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³å（FQCN）を使用ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚`ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ã‚¤ãƒ³ãƒ‡ãƒƒã‚¯ã‚¹ <https://docs.ansible.com/ansible/2.10/collections/index_module.html>`_ を検索ã™ã‚‹ã¨ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒå†é…ç½®ã•ã‚ŒãŸã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’見ã¤ã‘ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:607 -msgid "The deprecated helm module has been removed. Use community.kubernetes.helm instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® helm モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« community.kubernetes.helm を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "This section discusses the behavioral changes between Ansible 2.9 and Ansible 2.10." +#~ msgstr "ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€Ansible 2.9 ã‹ã‚‰ Ansible 2.10 ã«ãŠã‘る動作ã®å¤‰æ›´ç‚¹ã‚’説明ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:608 -msgid "The deprecated hpilo_facts module has been removed. Use hpilo_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® hpilo_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« hpilo_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "We suggest you read this page along with the `Ansible Changelog for 2.10 <https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst>`_ to understand what updates you may need to make." +#~ msgstr "å¿…è¦ãªæ›´æ–°ã«ã¤ã„ã¦ç†è§£ã™ã‚‹ã«ã¯ã€ã“ã®ãƒšãƒ¼ã‚¸ã¨ä½µã›ã¦ã€Œ`Ansible 2.10 ã®ãƒã‚§ãƒ³ã‚¸ãƒã‚° <https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_4.rst:609 -msgid "The deprecated idrac_redfish_facts module has been removed. Use idrac_redfish_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® idrac_redfish_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« idrac_redfish_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "Since 2.10, Ansible consists of two parts:" +#~ msgstr "2.10 以é™ã€Ansible ã¯ä»¥ä¸‹ã® 2 ã¤ã®éƒ¨åˆ†ã‹ã‚‰æ§‹æˆã•ã‚Œã¦ã„ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:610 -msgid "The deprecated jenkins_job_facts module has been removed. Use jenkins_job_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® jenkins_job_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« jenkins_job_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "ansible-base, which includes the command line tools with a small selection of plugins and modules, and" +#~ msgstr "ansible-base: プラグインやモジュールãŒå°‘ãªã„コマンドラインツールãŒå«ã¾ã‚Œã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:611 -msgid "The deprecated ldap_attr module has been removed. Use ldap_attrs instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ldap_attr モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ldap_attrs を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "a `set of collections <https://github.com/ansible-community/ansible-build-data/blob/main/2.10/ansible.in>`_." +#~ msgstr "`コレクションã®ã‚»ãƒƒãƒˆ <https://github.com/ansible-community/ansible-build-data/blob/main/2.10/ansible.in>`" -#: ../../rst/porting_guides/porting_guide_4.rst:612 -msgid "The deprecated memset_memstore_facts module has been removed. Use memset_memstore_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® memset_memstore_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« memset_memstore_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "The :ref:`porting_2.10_guide_base` is included in this porting guide. The complete list of porting guides can be found at :ref:`porting guides <porting_guides>`." +#~ msgstr ":ref:`porting_2.10_guide_base` ã¯ã€ã“ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰ã«å«ã¾ã‚Œã¾ã™ã€‚移æ¤ã‚¬ã‚¤ãƒ‰ã®ä¸€è¦§ã¯ã€Œ:ref:`移æ¤ã‚¬ã‚¤ãƒ‰ <porting_guides>`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_4.rst:613 -msgid "The deprecated memset_server_facts module has been removed. Use memset_server_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® memset_server_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« memset_server_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "Porting Guide for v2.10.7" +#~ msgstr "v2.10.7 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" -#: ../../rst/porting_guides/porting_guide_4.rst:614 -msgid "The deprecated na_ontap_gather_facts module has been removed. Use netapp.ontap.na_ontap_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® na_ontap_gather_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_volume を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1924)。" +#~ msgid "community.general" +#~ msgstr "community.general" -#: ../../rst/porting_guides/porting_guide_4.rst:615 -msgid "The deprecated nginx_status_facts module has been removed. Use nginx_status_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® nginx_status_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« nginx_status_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "utm_proxy_auth_profile - the ``frontend_cookie_secret`` return value now contains a placeholder string instead of the module's ``frontend_cookie_secret`` parameter (https://github.com/ansible-collections/community.general/pull/1736)." +#~ msgstr "utm_proxy_auth_profile - ``frontend_cookie_secret`` ã®æˆ»ã‚Šå€¤ã«ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã® ``frontend_cookie_secret`` パラメーターã§ã¯ãªãプレースホルダーã®æ–‡å—列ãŒå«ã¾ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/1736)。" -#: ../../rst/porting_guides/porting_guide_4.rst:616 -msgid "The deprecated one_image_facts module has been removed. Use one_image_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® one_image_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« one_image_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "Major Changes" +#~ msgstr "主ãªå¤‰æ›´ç‚¹" -#: ../../rst/porting_guides/porting_guide_4.rst:617 -msgid "The deprecated onepassword_facts module has been removed. Use onepassword_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® onepassword_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« onepassword_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "Restricting the version of the community.okd collection to 1.0.0. The previously included version, 1.0.1, had a dependency on kubernetes.core and thus required the installation of an additional collection that was not included in Ansible 2.10. Version 1.0.0 is essentially identical to 1.0.1, except that it uses community.kubernetes, wihch is included in Ansible 2.10." +#~ msgstr "community.okd コレクションã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’ 1.0.0 ã«åˆ¶é™ã—ã¾ã—ãŸã€‚ã“ã‚Œã¾ã§å«ã¾ã‚Œã¦ã„ãŸãƒãƒ¼ã‚¸ãƒ§ãƒ³ 1.0.1 ã¯ã€kubernetes.core ã«ä¾å˜ã—ã¦ã„ãŸãŸã‚ã€Ansible 2.10 ã«å«ã¾ã‚Œã¦ã„ãªã„è¿½åŠ ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã—ãŸã€‚ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 1.0.0 ã¯ã€Ansible 2.10 ã«å«ã¾ã‚Œã¦ã„ã‚‹ community.kubernetes を使用ã—ã¦ã„る以外ã¯ã€1.0.1 ã¨åŸºæœ¬çš„ã«åŒã˜ã§ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:618 -msgid "The deprecated oneview_datacenter_facts module has been removed. Use oneview_datacenter_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® oneview_datacenter_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_datacenter_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "ovirt.ovirt" +#~ msgstr "ovirt.ovirt" -#: ../../rst/porting_guides/porting_guide_4.rst:619 -msgid "The deprecated oneview_enclosure_facts module has been removed. Use oneview_enclosure_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® oneview_enclosure_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_enclosure_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "ovirt_system_option_info - Add new module (https://github.com/oVirt/ovirt-ansible-collection/pull/206)." +#~ msgstr "ovirt_system_option_info - æ–°ã—ã„ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/206)。" -#: ../../rst/porting_guides/porting_guide_4.rst:620 -msgid "The deprecated oneview_ethernet_network_facts module has been removed. Use oneview_ethernet_network_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® oneview_ethernet_network_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_ethernet_network_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "servicenow.servicenow" +#~ msgstr "servicenow.servicenow" -#: ../../rst/porting_guides/porting_guide_4.rst:621 -msgid "The deprecated oneview_fc_network_facts module has been removed. Use oneview_fc_network_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® oneview_fc_network_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_fc_network_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "add new tests (find with no result, search many)" +#~ msgstr "æ–°è¦ãƒ†ã‚¹ãƒˆã®è¿½åŠ (çµæžœãŒãªã„検索ã€å¤šæ•°ã®æ¤œç´¢)" -#: ../../rst/porting_guides/porting_guide_4.rst:622 -msgid "The deprecated oneview_fcoe_network_facts module has been removed. Use oneview_fcoe_network_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® oneview_fcoe_network_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_fcoe_network_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "add related tests" +#~ msgstr "関連テストã®è¿½åŠ " -#: ../../rst/porting_guides/porting_guide_4.rst:623 -msgid "The deprecated oneview_logical_interconnect_group_facts module has been removed. Use oneview_logical_interconnect_group_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® oneview_logical_interconnect_group_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_logical_interconnect_group_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "add support for ServiceNOW table api display_value exclude_reference_link and suppress_pagination_header" +#~ msgstr "ServiceNOW テーブル api display_value exclude_reference_link ãŠã‚ˆã³ suppress_pagination_header ã®ã‚µãƒãƒ¼ãƒˆã‚’è¿½åŠ " -#: ../../rst/porting_guides/porting_guide_4.rst:624 -msgid "The deprecated oneview_network_set_facts module has been removed. Use oneview_network_set_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® oneview_network_set_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_network_set_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924).）。" +#~ msgid "use new API for pysnow >=0.6.0" +#~ msgstr "0.6.0 以é™ã® pysnow ã§æ–°ã—ã„ API ã®ä½¿ç”¨" -#: ../../rst/porting_guides/porting_guide_4.rst:625 -msgid "The deprecated oneview_san_manager_facts module has been removed. Use oneview_san_manager_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® oneview_san_manager_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_san_manager_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "Deprecated Features" +#~ msgstr "éžæŽ¨å¥¨ã®æ©Ÿèƒ½" -#: ../../rst/porting_guides/porting_guide_4.rst:626 -msgid "The deprecated online_server_facts module has been removed. Use online_server_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® online_server_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« online_server_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "cisco.nxos" +#~ msgstr "cisco.nxos" -#: ../../rst/porting_guides/porting_guide_4.rst:627 -msgid "The deprecated online_user_facts module has been removed. Use online_user_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® online_user_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« online_user_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "Deprecated `nxos_bgp` and `nxos_bgp_neighbor` modules in favor of `nxos_bgp_global` resource module." +#~ msgstr "`nxos_bgp` モジュールãŠã‚ˆã³ `nxos_bgp_neighbor` モジュールãŒéžæŽ¨å¥¨ã¨ãªã‚Šã€`nxos_bgp_global` リソースモジュールãŒä½¿ç”¨ã•ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:628 -msgid "The deprecated ovirt module has been removed. Use ovirt.ovirt.ovirt_vm instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_vm を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "community.vmware" +#~ msgstr "community.vmware" -#: ../../rst/porting_guides/porting_guide_4.rst:629 -msgid "The deprecated ovirt_affinity_label_facts module has been removed. Use ovirt.ovirt.ovirt_affinity_label_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_affinity_label_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_affinity_label_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "vmware_host_firewall_manager - the creation of new rule with no ``allowed_ip`` entry in the ``allowed_hosts`` dictionary won't be allowed after 2.0.0 release." +#~ msgstr "vmware_host_firewall_manager - ``allowed_hosts`` ディクショナリー㫠``allowed_ip`` エントリーãŒãªã„æ–°è¦ãƒ«ãƒ¼ãƒ«ã®ä½œæˆã¯ã€2.0.0 リリース後ã¯è¨±å¯ã•ã‚Œãªããªã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:630 -msgid "The deprecated ovirt_api_facts module has been removed. Use ovirt.ovirt.ovirt_api_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_api_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_api_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "Porting Guide for v2.10.6" +#~ msgstr "v2.10.6 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" -#: ../../rst/porting_guides/porting_guide_4.rst:631 -msgid "The deprecated ovirt_cluster_facts module has been removed. Use ovirt.ovirt.ovirt_cluster_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_cluster_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_cluster_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "For community.general 2.0.0, the kubevirt modules will be moved to the `community.kubevirt <https://galaxy.ansible.com/community/kubevirt>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." +#~ msgstr "community.general 2.0.0 ã®å ´åˆã€kubevirt モジュール㯠`community.kubevirt <https://galaxy.ansible.com/community/kubevirt>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:632 -msgid "The deprecated ovirt_datacenter_facts module has been removed. Use ovirt.ovirt.ovirt_datacenter_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_datacenter_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_datacenter_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "If you use Ansible 2.9 and explicitly use kubevirt modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.kubevirt.`` instead of ``community.general.``, for example replace ``community.general.kubevirt_vm`` in a task by ``community.kubevirt.kubevirt_vm``." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ã® kubevirt モジュールを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€``community.general.`` ã§ã¯ãªã ``community.kubevirt.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã« Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’調整ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``community.kubevirt.kubevirt_vm`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.general.kubevirt_vm`` ã‚’ç½®ãæ›ãˆã¾ã™)。" -#: ../../rst/porting_guides/porting_guide_4.rst:633 -msgid "The deprecated ovirt_disk_facts module has been removed. Use ovirt.ovirt.ovirt_disk_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_disk_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_disk_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "If you use ansible-base and installed ``community.general`` manually and rely on the kubevirt modules, you have to make sure to install the ``community.kubevirt`` collection as well. If you are using FQCNs, for example ``community.general.kubevirt_vm`` instead of ``kubevirt_vm``, it will continue working, but we still recommend to adjust the FQCNs as well." +#~ msgstr "ansible-base を使用ã—㦠``community.general`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€kubevirt モジュールã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.kubevirt`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãŸã¨ãˆã° ``kubevirt_vm`` ã®ä»£ã‚ã‚Šã« ``community.general.kubevirt_vm`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:634 -msgid "The deprecated ovirt_event_facts module has been removed. Use ovirt.ovirt.ovirt_event_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_event_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_event_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "community.network" +#~ msgstr "community.network" -#: ../../rst/porting_guides/porting_guide_4.rst:635 -msgid "The deprecated ovirt_external_provider_facts module has been removed. Use ovirt.ovirt.ovirt_external_provider_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_external_provider_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_external_provider_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "For community.network 2.0.0, the Cisco NSO modules will be moved to the `cisco.nso <https://galaxy.ansible.com/cisco/nso>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." +#~ msgstr "community.network 2.0.0 ã§ã¯ã€Cisco NSO モジュール㯠`cisco.nso <https://galaxy.ansible.com/cisco/nso>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã—ãªãã¦ã‚‚よã„よã†ã«ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæŒ¿å…¥ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:636 -msgid "The deprecated ovirt_group_facts module has been removed. Use ovirt.ovirt.ovirt_group_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_group_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_group_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "If you use Ansible 2.9 and explicitly use Cisco NSO modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``cisco.nso.`` instead of ``community.network.``, for example replace ``community.network.nso_config`` in a task by ``cisco.nso.nso_config``." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ Cisco NSO モジュールを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.network.`` ã§ã¯ãªã ``cisco.nso.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``cisco.nso.nso_config`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.network.nso_config`` ã‚’ç½®ãæ›ãˆã¾ã™)。" -#: ../../rst/porting_guides/porting_guide_4.rst:637 -msgid "The deprecated ovirt_host_facts module has been removed. Use ovirt.ovirt.ovirt_host_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_host_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_host_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "If you use ansible-base and installed ``community.network`` manually and rely on the Cisco NSO modules, you have to make sure to install the ``cisco.nso`` collection as well. If you are using FQCNs, for example ``community.network.nso_config`` instead of ``nso_config``, it will continue working, but we still recommend to adjust the FQCNs as well." +#~ msgstr "ansible-base を使用ã—㦠``community.network`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€Cisco NSO モジュールã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``cisco.nso`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ãŸã¨ãˆã° ``nso_config`` ã®ä»£ã‚ã‚Šã« ``community.network.nso_config`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:638 -msgid "The deprecated ovirt_host_storage_facts module has been removed. Use ovirt.ovirt.ovirt_host_storage_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_host_storage_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_host_storage_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "For community.network 2.0.0, the FortiOS modules will be moved to the `community.fortios <https://galaxy.ansible.com/ansible-collections/community.fortios>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." +#~ msgstr "community.network 2.0.0 ã§ã¯ã€FortiOS モジュール㯠`community.fortios <https://galaxy.ansible.com/ansible-collections/community.fortios>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã—ãªãã¦ã‚‚よã„よã†ã«ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæŒ¿å…¥ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:639 -msgid "The deprecated ovirt_network_facts module has been removed. Use ovirt.ovirt.ovirt_network_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_network_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_network_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "If you use Ansible 2.9 and explicitly use FortiOS modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.fortios.`` instead of ``community.network.``, for example replace ``community.network.fmgr_device`` in a task by ``community.fortios.fmgr_device``." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ FortiOS モジュールを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.network.`` ã§ã¯ãªã ``community.fortios.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``community.fortios.fmgr_device`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.network.fmgr_device`` ã‚’ç½®ãæ›ãˆã¾ã™)。" -#: ../../rst/porting_guides/porting_guide_4.rst:640 -msgid "The deprecated ovirt_nic_facts module has been removed. Use ovirt.ovirt.ovirt_nic_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_nic_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_nic_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "If you use ansible-base and installed ``community.network`` manually and rely on the FortiOS modules, you have to make sure to install the ``community.fortios`` collection as well. If you are using FQCNs, for example ``community.network.fmgr_device`` instead of ``fmgr_device``, it will continue working, but we still recommend to adjust the FQCNs as well." +#~ msgstr "ansible-base を使用ã—㦠``community.network`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€FortiOS モジュールã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.fortios`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ãŸã¨ãˆã° ``fmgr_device`` ã®ä»£ã‚ã‚Šã« ``community.network.fmgr_device`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:641 -msgid "The deprecated ovirt_permission_facts module has been removed. Use ovirt.ovirt.ovirt_permission_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_permission_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_permission_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "f5networks.f5_modules" +#~ msgstr "f5networks.f5_modules" -#: ../../rst/porting_guides/porting_guide_4.rst:642 -msgid "The deprecated ovirt_quota_facts module has been removed. Use ovirt.ovirt.ovirt_quota_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_quota_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_quota_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "Added async_timeout parameter to bigip_ucs_fetch module to allow customization of module wait for async interface" +#~ msgstr "bigip_ucs_fetch モジュール㫠async_timeout ãƒ‘ãƒ©ãƒ¡ãƒ¼ã‚¿ãƒ¼ã‚’è¿½åŠ ã—ã¦ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒ async インターフェースを待機ã§ãるよã†ã«ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:643 -msgid "The deprecated ovirt_scheduling_policy_facts module has been removed. Use ovirt.ovirt.ovirt_scheduling_policy_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_scheduling_policy_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_scheduling_policy_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "Changed bigip_ucs_fetch module to use asynchronous interface when generating UCS files" +#~ msgstr "UCS ファイルã®ç”Ÿæˆæ™‚ã«éžåŒæœŸã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ã‚’使用ã™ã‚‹ã‚ˆã†ã« bigip_ucs_fetch モジュールã®å¤‰æ›´" -#: ../../rst/porting_guides/porting_guide_4.rst:644 -msgid "The deprecated ovirt_snapshot_facts module has been removed. Use ovirt.ovirt.ovirt_snapshot_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_snapshot_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_snapshot_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "Porting Guide for v2.10.5" +#~ msgstr "v2.10.5 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" -#: ../../rst/porting_guides/porting_guide_4.rst:645 -msgid "The deprecated ovirt_storage_domain_facts module has been removed. Use ovirt.ovirt.ovirt_storage_domain_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_storage_domain_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_storage_domain_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "community.hashi_vault" +#~ msgstr "community.hashi_vault" -#: ../../rst/porting_guides/porting_guide_4.rst:646 -msgid "The deprecated ovirt_storage_template_facts module has been removed. Use ovirt.ovirt.ovirt_storage_template_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_storage_template_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_storage_template_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "hashi_vault - the ``VAULT_ADDR`` environment variable is now checked last for the ``url`` parameter. For details on which use cases are impacted, see (https://github.com/ansible-collections/community.hashi_vault/issues/8)." +#~ msgstr "hashi_vault - ``VAULT_ADDR`` 環境変数ãŒã€æœ€å¾Œã« ``url`` パラメーターã«ã¤ã„ã¦ãƒã‚§ãƒƒã‚¯ã•ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚影響をå—ã‘るユースケースã®è©³ç´°ã¯ã€https://github.com/ansible-collections/community.hashi_vault/issues/8 ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/porting_guides/porting_guide_4.rst:647 -msgid "The deprecated ovirt_storage_vm_facts module has been removed. Use ovirt.ovirt.ovirt_storage_vm_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_storage_vm_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_storage_vm_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "For community.general 2.0.0, the Google modules will be moved to the `community.google <https://galaxy.ansible.com/community/google>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." +#~ msgstr "community.general 2.0.0 ã®å ´åˆã€Google モジュール㯠`community.google <https://galaxy.ansible.com/community/google>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:648 -msgid "The deprecated ovirt_tag_facts module has been removed. Use ovirt.ovirt.ovirt_tag_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_tag_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_tag_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "If you use Ansible 2.9 and explicitly use Google modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.google.`` instead of ``community.general.``, for example replace ``community.general.gcpubsub`` in a task by ``community.google.gcpubsub``." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ Google モジュールを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.general.`` ã§ã¯ãªã ``community.google.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``community.google.gcpubsub`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.general.gcpubsub`` ã‚’ç½®ãæ›ãˆã¾ã™)。" -#: ../../rst/porting_guides/porting_guide_4.rst:649 -msgid "The deprecated ovirt_template_facts module has been removed. Use ovirt.ovirt.ovirt_template_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_template_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_template_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "If you use ansible-base and installed ``community.general`` manually and rely on the Google modules, you have to make sure to install the ``community.google`` collection as well. If you are using FQCNs, for example ``community.general.gcpubsub`` instead of ``gcpubsub``, it will continue working, but we still recommend to adjust the FQCNs as well." +#~ msgstr "ansible-base を使用ã—㦠``community.general`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€Google モジュールã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.google`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ãŸã¨ãˆã° ``gcpubsub`` ã®ä»£ã‚ã‚Šã« ``community.general.gcpubsub`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:650 -msgid "The deprecated ovirt_user_facts module has been removed. Use ovirt.ovirt.ovirt_user_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_user_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_user_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "For community.general 2.0.0, the OC connection plugin will be moved to the `community.okd <https://galaxy.ansible.com/community/okd>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." +#~ msgstr "community.general 2.0.0 ã®å ´åˆã€OC 接続プラグイン㯠`community.okd <https://galaxy.ansible.com/community/okd>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:651 -msgid "The deprecated ovirt_vm_facts module has been removed. Use ovirt.ovirt.ovirt_vm_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_vm_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_vm_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "If you use Ansible 2.9 and explicitly use OC connection plugin from this collection, you will need to adjust your playbooks and roles to use FQCNs ``community.okd.oc`` instead of ``community.general.oc``." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ OC 接続プラグインを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.general.oc`` ã§ã¯ãªã FQCN ã® ``community.okd.oc`` を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:652 -msgid "The deprecated ovirt_vmpool_facts module has been removed. Use ovirt.ovirt.ovirt_vmpool_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® ovirt_vmpool_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_vmpool_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "If you use ansible-base and installed ``community.general`` manually and rely on the OC connection plugin, you have to make sure to install the ``community.okd`` collection as well. If you are using FQCNs, in other words ``community.general.oc`` instead of ``oc``, it will continue working, but we still recommend to adjust this FQCN as well." +#~ msgstr "ansible-base を使用ã—ã€æ‰‹å‹•ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—㟠``community.general`` を使用ã—ã€OC 接続プラグインã«ä¾å˜ã™ã‚‹å ´åˆã¯ã€``community.okd`` コレクションもインストールã—ã¦ãã ã•ã„。FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ã¤ã¾ã‚Šã€``oc`` ã®ä»£ã‚ã‚Šã« ``community.general.oc`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ã‚’推奨ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:653 -msgid "The deprecated purefa_facts module has been removed. Use purestorage.flasharray.purefa_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® purefa_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« purestorage.flasharray.purefa_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "For community.general 2.0.0, the hashi_vault lookup plugin will be moved to the `community.hashi_vault <https://galaxy.ansible.com/community/hashi_vault>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." +#~ msgstr "community.general 2.0.0 ã®å ´åˆã€hashi_vault lookup プラグイン㯠`community.hashi_vault <https://galaxy.ansible.com/community/hashi_vault>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:654 -msgid "The deprecated purefb_facts module has been removed. Use purestorage.flasharray.purefb_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® purefb_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« purestorage.flasharray.purefb_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "If you use Ansible 2.9 and explicitly use hashi_vault lookup plugin from this collection, you will need to adjust your playbooks and roles to use FQCNs ``community.hashi_vault.hashi_vault`` instead of ``community.general.hashi_vault``." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® hashi_vault lookup プラグインを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€``community.general.hashi_vault`` ã§ã¯ãªã FQCN ``community.hashi_vault.hashi_vault`` を使用ã™ã‚‹ã‚ˆã†ã« Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’調整ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:655 -msgid "The deprecated python_requirements_facts module has been removed. Use python_requirements_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® python_requirements_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« python_requirements_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "If you use ansible-base and installed ``community.general`` manually and rely on the hashi_vault lookup plugin, you have to make sure to install the ``community.hashi_vault`` collection as well. If you are using FQCNs, in other words ``community.general.hashi_vault`` instead of ``hashi_vault``, it will continue working, but we still recommend to adjust this FQCN as well." +#~ msgstr "ansible-base を使用ã—ã€æ‰‹å‹•ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—㟠``community.general`` を手動ã§ã—ã€hashi_vault lookup プラグインã«ä¾å˜ã™ã‚‹å ´åˆã¯ã€``community.hashi_vault`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ã¤ã¾ã‚Šã€``hashi_vault`` ã§ã¯ãªã ``community.general.hashi_vault`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ã‚’推奨ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:656 -msgid "The deprecated redfish_facts module has been removed. Use redfish_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® redfish_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« redfish_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "netbox.netbox" +#~ msgstr "netbox.netbox" -#: ../../rst/porting_guides/porting_guide_4.rst:657 -msgid "The deprecated scaleway_image_facts module has been removed. Use scaleway_image_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® scaleway_image_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« scaleway_image_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "nb_inventory - Add ``dns_name`` option that adds ``dns_name`` to the host when ``True`` and device has a primary IP address. (#394)" +#~ msgstr "nb_inventory - ``True`` ãŠã‚ˆã³ãƒ‡ãƒã‚¤ã‚¹ã«ãƒ—ライマリー IP アドレスãŒã‚ã‚‹å ´åˆã« ``dns_name`` をホストã«è¿½åŠ ã™ã‚‹ ``dns_name`` ã‚ªãƒ—ã‚·ãƒ§ãƒ³ã‚’è¿½åŠ ã—ã¾ã™ã€‚(#394)" -#: ../../rst/porting_guides/porting_guide_4.rst:658 -msgid "The deprecated scaleway_ip_facts module has been removed. Use scaleway_ip_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® scaleway_ip_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« scaleway_ip_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "nb_inventory - Add ``status`` as a ``group_by`` option. (398)" +#~ msgstr "nb_inventory - ``group_by`` オプションã¨ã—㦠``status`` ã‚’è¿½åŠ ã—ã¾ã™ã€‚(398)" -#: ../../rst/porting_guides/porting_guide_4.rst:659 -msgid "The deprecated scaleway_organization_facts module has been removed. Use scaleway_organization_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® scaleway_organization_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« scaleway_organization_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "nb_inventory - Move around ``extracted_primary_ip`` to allow for ``config_context`` or ``custom_field`` to overwite. (#377)" +#~ msgstr "nb_inventory - ``config_context`` ã¾ãŸã¯ ``custom_field`` ã®ä¸Šæ›¸ãを許å¯ã™ã‚‹ ``extracted_primary_ip`` を移動ã—ã¾ã™ã€‚(#377)" -#: ../../rst/porting_guides/porting_guide_4.rst:660 -msgid "The deprecated scaleway_security_group_facts module has been removed. Use scaleway_security_group_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® scaleway_security_group_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« scaleway_security_group_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "nb_inventory - Services are now a list of integers due to NetBox 2.10 changes. (#396)" +#~ msgstr "nb_inventory - サービスã¯ã€NetBox 2.10 ã®å¤‰æ›´ã«ã‚ˆã‚Šæ•´æ•°ã®ä¸€è¦§ã«ãªã‚Šã¾ã—ãŸã€‚(#396)" -#: ../../rst/porting_guides/porting_guide_4.rst:661 -msgid "The deprecated scaleway_server_facts module has been removed. Use scaleway_server_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® scaleway_server_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« scaleway_server_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "nb_lookup - Allow ID to be passed in and use ``.get`` instead of ``.filter``. (#376)" +#~ msgstr "nb_lookup - ID を渡ã™ã“ã¨ãŒã§ãã€``.filter`` ã®ä»£ã‚ã‚Šã« ``.get`` を使用ã§ãã¾ã™ã€‚(#376)" -#: ../../rst/porting_guides/porting_guide_4.rst:662 -msgid "The deprecated scaleway_snapshot_facts module has been removed. Use scaleway_snapshot_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® scaleway_snapshot_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« scaleway_snapshot_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "nb_lookup - Allow ``api_endpoint`` and ``token`` to be found via env. (#391)" +#~ msgstr "nb_lookup - ``api_endpoint`` ãŠã‚ˆã³ ``token`` ã‚’ env 経由ã§æ¤œç´¢ã™ã‚‹ã“ã¨ã‚’許å¯ã—ã¾ã™ã€‚(#391)" -#: ../../rst/porting_guides/porting_guide_4.rst:663 -msgid "The deprecated scaleway_volume_facts module has been removed. Use scaleway_volume_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® scaleway_volume_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« scaleway_volume_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "community.aws" +#~ msgstr "community.aws" -#: ../../rst/porting_guides/porting_guide_4.rst:664 -msgid "The deprecated smartos_image_facts module has been removed. Use smartos_image_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® smartos_image_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« smartos_image_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "ec2_vpc_igw_info - After 2022-06-22 the ``convert_tags`` parameter default value will change from ``False`` to ``True`` to match the collection standard behavior (https://github.com/ansible-collections/community.aws/pull/318)." +#~ msgstr "ec2_vpc_igw_info - 2022-06-22 以é™ã€``convert_tags`` パラメーターã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ãŒ ``False`` ã‹ã‚‰ ``True`` ã«å¤‰æ›´ã—ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®æ¨™æº–動作ã¨ä¸€è‡´ã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã™ (https://github.com/ansible-collections/community.aws/pull/318)。" -#: ../../rst/porting_guides/porting_guide_4.rst:665 -msgid "The deprecated vertica_facts module has been removed. Use vertica_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® vertica_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« vertica_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "community.docker" +#~ msgstr "community.docker" -#: ../../rst/porting_guides/porting_guide_4.rst:666 -msgid "The deprecated xenserver_guest_facts module has been removed. Use xenserver_guest_info instead (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "éžæŽ¨å¥¨ã® xenserver_guest_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« xenserver_guest_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "docker_container - currently ``published_ports`` can contain port mappings next to the special value ``all``, in which case the port mappings are ignored. This behavior is deprecated for community.docker 2.0.0, at which point it will either be forbidden, or this behavior will be properly implemented similar to how the Docker CLI tool handles this (https://github.com/ansible-collections/community.docker/issues/8, https://github.com/ansible-collections/community.docker/pull/60)." +#~ msgstr "docker_container - ç¾åœ¨ã€``published_ports`` ã«ã¯ã€ç‰¹åˆ¥ãªå€¤ ``all`` ã®æ¨ªã«ãƒãƒ¼ãƒˆãƒžãƒƒãƒ”ングをå«ã‚ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã®å‹•ä½œã¯ã€community.docker 2.0.0 ã§ã¯éžæŽ¨å¥¨ã§ã™ã€‚ãã®æ™‚点ã§ã€ç¦æ¢ã•ã‚Œã‚‹ã‹ã€Docker CLI ツールãŒã©ã®ã‚ˆã†ã«ã“れを処ç†ã™ã‚‹ã‹ã¨åŒã˜ã‚ˆã†ã«ã€ã“ã®å‹•ä½œãŒé©åˆ‡ã«å®Ÿè£…ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.docker/issues/8ã€https://github.com/ansible-collections/community.docker/pull/60)。" -#: ../../rst/porting_guides/porting_guide_4.rst:667 -msgid "The ovirt_facts docs fragment has been removed (https://github.com/ansible-collections/community.general/pull/1924)." -msgstr "ovirt_facts ドã‚ュメントã®ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.general/pull/1924）。" +#~ msgid "hashi_vault - ``VAULT_ADDR`` environment variable for option ``url`` will have its precedence lowered in 1.0.0; use ``ANSIBLE_HASHI_VAULT_ADDR`` to intentionally override a config value (https://github.com/ansible-collections/community.hashi_vault/issues/8)." +#~ msgstr "hashi_vault - オプション ``url`` ã® ``VAULT_ADDR`` 環境変数ã®å„ªå…ˆåº¦ã¯ 1.0.0 ã§ä½Žããªã‚Šã¾ã™ã€‚è¨å®šå€¤ã‚’æ„図的ã«ä¸Šæ›¸ãã™ã‚‹ã«ã¯ ``ANSIBLE_HASHI_VAULT_ADDR`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.hashi_vault/issues/8)。" -#: ../../rst/porting_guides/porting_guide_4.rst:668 -msgid "airbrake_deployment - removed deprecated ``token`` parameter. Use ``project_id`` and ``project_key`` instead (https://github.com/ansible-collections/community.general/pull/1926)." -msgstr "airbrake_deployment - éžæŽ¨å¥¨ã® ``token`` パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``project_id`` ãŠã‚ˆã³ ``project_key`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" +#~ msgid "hashi_vault - ``VAULT_AUTH_METHOD`` environment variable for option ``auth_method`` will be removed in 2.0.0, use ``ANSIBLE_HASHI_VAULT_AUTH_METHOD`` instead (https://github.com/ansible-collections/community.hashi_vault/issues/17)." +#~ msgstr "hashi_vault - オプション ``auth_method`` ã® ``VAULT_AUTH_METHOD`` 環境変数㯠2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ``ANSIBLE_HASHI_VAULT_AUTH_METHOD`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.hashi_vault/issues/17)。" -#: ../../rst/porting_guides/porting_guide_4.rst:669 -msgid "bigpanda - the alias ``message`` has been removed. Use ``deployment_message`` instead (https://github.com/ansible-collections/community.general/pull/1926)." -msgstr "bigpanda - エイリアス ``message`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``deployment_message`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" +#~ msgid "hashi_vault - ``VAULT_ROLE_ID`` environment variable for option ``role_id`` will be removed in 2.0.0, use ``ANSIBLE_HASHI_VAULT_ROLE_ID`` instead (https://github.com/ansible-collections/community.hashi_vault/issues/20)." +#~ msgstr "hashi_vault - オプション ``role_id`` ã® ``VAULT_ROLE_ID`` 環境変数㯠2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ``ANSIBLE_HASHI_VAULT_ROLE_ID`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.hashi_vault/issues/20)。" -#: ../../rst/porting_guides/porting_guide_4.rst:670 -msgid "cisco_spark, cisco_webex - the alias ``message`` has been removed. Use ``msg`` instead (https://github.com/ansible-collections/community.general/pull/1926)." -msgstr "cisco_spark, cisco_webex - エイリアス ``message`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``msg`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" +#~ msgid "hashi_vault - ``VAULT_SECRET_ID`` environment variable for option ``secret_id`` will be removed in 2.0.0, use ``ANSIBLE_HASHI_VAULT_SECRET_ID`` instead (https://github.com/ansible-collections/community.hashi_vault/issues/20)." +#~ msgstr "hashi_vault - オプション ``secret_id`` ã® ``VAULT_SECRET_ID`` 環境変数㯠2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ``ANSIBLE_HASHI_VAULT_SECRET_ID`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.hashi_vault/issues/20)。" -#: ../../rst/porting_guides/porting_guide_4.rst:671 -msgid "clc_aa_policy - the ``wait`` parameter has been removed. It did not have any effect (https://github.com/ansible-collections/community.general/pull/1926)." -msgstr "clc_aa_policy - ``wait`` パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚影響ã¯ã‚ã‚Šã¾ã›ã‚“（https://github.com/ansible-collections/community.general/pull/1926）。" +#~ msgid "hashi_vault - ``VAULT_TOKEN_FILE`` environment variable for option ``token_file`` will be removed in 2.0.0, use ``ANSIBLE_HASHI_VAULT_TOKEN_FILE`` instead (https://github.com/ansible-collections/community.hashi_vault/issues/15)." +#~ msgstr "hashi_vault - オプション ``token_file`` ã® ``VAULT_TOKEN_FILE`` 環境変数㯠2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ``ANSIBLE_HASHI_VAULT_TOKEN_FILE`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.hashi_vault/issues/15)。" -#: ../../rst/porting_guides/porting_guide_4.rst:672 -msgid "datadog_monitor - the alias ``message`` has been removed. Use ``notification_message`` instead (https://github.com/ansible-collections/community.general/pull/1926)." -msgstr "datadog_monitor - エイリアス ``message`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``notification_message`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" +#~ msgid "hashi_vault - ``VAULT_TOKEN_PATH`` environment variable for option ``token_path`` will be removed in 2.0.0, use ``ANSIBLE_HASHI_VAULT_TOKEN_PATH`` instead (https://github.com/ansible-collections/community.hashi_vault/issues/15)." +#~ msgstr "hashi_vault - オプション ``token_path`` ã® ``VAULT_TOKEN_PATH`` 環境変数㯠2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ``ANSIBLE_HASHI_VAULT_TOKEN_PATH`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.hashi_vault/issues/15)。" -#: ../../rst/porting_guides/porting_guide_4.rst:673 -msgid "django_manage - the parameter ``liveserver`` has been removed (https://github.com/ansible-collections/community.general/pull/1926)." -msgstr "django_manage - パラメーター ``liveserver`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.general/pull/1926）。" +#~ msgid "Porting Guide for v2.10.4" +#~ msgstr "v2.10.4 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" -#: ../../rst/porting_guides/porting_guide_4.rst:674 -msgid "idrac_redfish_config - the parameters ``manager_attribute_name`` and ``manager_attribute_value`` have been removed. Use ``manager_attributes`` instead (https://github.com/ansible-collections/community.general/pull/1926)." -msgstr "idrac_redfish_config - ``manager_attribute_name`` パラメーターãŠã‚ˆã³ ``manager_attribute_value`` パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``manager_attributes`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" +#~ msgid "community.hrobot" +#~ msgstr "community.hrobot" -#: ../../rst/porting_guides/porting_guide_4.rst:675 -msgid "iso_extract - the alias ``thirsty`` has been removed. Use ``force`` instead (https://github.com/ansible-collections/community.general/pull/1926)." -msgstr "iso_extract - エイリアス ``thirsty`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``force`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" +#~ msgid "firewall - now requires the `ipaddress <https://pypi.org/project/ipaddress/>`_ library (https://github.com/ansible-collections/community.hrobot/pull/2)." +#~ msgstr "firewall - `ipaddress <https://pypi.org/project/ipaddress/>`_ ライブラリーãŒå¿…è¦ã«ãªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.hrobot/pull/2)。" -#: ../../rst/porting_guides/porting_guide_4.rst:676 -msgid "ldap_entry - the ``params`` parameter is now completely removed. Using it already triggered an error since community.general 0.1.2 (https://github.com/ansible-collections/community.general/pull/2257)." -msgstr "ldap_entry - ``params`` パラメーターã¯å®Œå…¨ã«å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚community.general 0.1.2 以é™ã€ã“れを使用ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ãŒãƒˆãƒªã‚¬ãƒ¼ã•ã‚Œã¦ã„ã¾ã™ã€‚https://github.com/ansible-collections/community.general/pull/2257）" +#~ msgid "For community.general 2.0.0, the Hetzner Robot modules will be moved to the `community.hrobot <https://galaxy.ansible.com/community/hrobot>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." +#~ msgstr "community.general 2.0.0 ã®å ´åˆã€Heatzner Robot モジュール㌠`community.hrobot <https://galaxy.ansible.com/community/hrobot>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã—ãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:677 -msgid "pulp_repo - the ``feed_client_cert`` parameter no longer defaults to the value of the ``client_cert`` parameter (https://github.com/ansible-collections/community.general/pull/1926)." -msgstr "pulp_repo - ``feed_client_cert`` パラメーターã«ã‚ˆã‚Šã€``client_cert`` パラメーターã®å€¤ã«ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆè¨å®šã•ã‚Œãªããªã‚Šã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.general/pull/1926）。" +#~ msgid "If you use Ansible 2.9 and explicitly use Hetzner Robot modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.hrobot.`` instead of ``community.general.hetzner_``, for example replace ``community.general.hetzner_firewall_info`` in a task by ``community.hrobot.firewall_info``." +#~ msgstr "Ansible 2.9 を使用ã—ã¦ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ Hetzner Robot モジュールを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€``community.general.hetzner_`` ã§ã¯ãªã ``community.hrobot.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã« Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’調整ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``community.hrobot.firewall_info`` ã§ã€ã‚¿ã‚¹ã‚¯å†…ã® ``community.general.hetzner_firewall_info`` ã‚’ç½®ãæ›ãˆã¾ã™)。" -#: ../../rst/porting_guides/porting_guide_4.rst:678 -msgid "pulp_repo - the ``feed_client_key`` parameter no longer defaults to the value of the ``client_key`` parameter (https://github.com/ansible-collections/community.general/pull/1926)." -msgstr "pulp_repo - ``feed_client_key`` パラメーターã«ã‚ˆã‚Šã€``client_key`` パラメーターã®å€¤ã«ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆè¨å®šã•ã‚Œãªããªã‚Šã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.general/pull/1926）。" +#~ msgid "If you use ansible-base and installed ``community.general`` manually and rely on the Hetzner Robot modules, you have to make sure to install the ``community.hrobot`` collection as well. If you are using FQCNs, i.e. ``community.general.hetzner_failover_ip`` instead of ``hetzner_failover_ip``, it will continue working, but we still recommend to adjust the FQCNs as well." +#~ msgstr "ansible-base を使用ã—㦠``community.general`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€Hetzner Robot モジュールã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.hrobot`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ãŸã¨ãˆã° ``hetzner_failover_ip`` ã®ä»£ã‚ã‚Šã« ``community.general.hetzner_failover_ip`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:679 -msgid "pulp_repo - the alias ``ca_cert`` has been removed. Use ``feed_ca_cert`` instead (https://github.com/ansible-collections/community.general/pull/1926)." -msgstr "pulp_repo - ``ca_cert`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``feed_ca_cert`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" +#~ msgid "For community.general 2.0.0, the ``docker`` modules and plugins will be moved to the `community.docker <https://galaxy.ansible.com/community/docker>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." +#~ msgstr "community.general 2.0.0 ã®å ´åˆã€``docker`` モジュールãŠã‚ˆã³ãƒ—ラグイン㯠`community.docker <https://galaxy.ansible.com/community/docker>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:680 -msgid "rax - unused parameter ``service`` removed (https://github.com/ansible-collections/community.general/pull/2020)." -msgstr "rax - 未使用ã®ãƒ‘ラメーター ``service`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.general/pull/2020）。" +#~ msgid "If you use Ansible 2.9 and explicitly use ``docker`` content from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.docker.`` instead of ``community.general.``, for example replace ``community.general.docker_container`` in a task by ``community.docker.docker_container``." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ ``docker`` コンテンツを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.general.`` ã§ã¯ãªã ``community.docker.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``community.docker.docker_container`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.general.docker_container`` ã‚’ç½®ãæ›ãˆã¾ã™)。" -#: ../../rst/porting_guides/porting_guide_4.rst:681 -msgid "redfish modules - issuing a data modification command without specifying the ID of the target System, Chassis or Manager resource when there is more than one is no longer allowed. Use the ``resource_id`` option to specify the target ID (https://github.com/ansible-collections/community.general/pull/1926)." -msgstr "redfish モジュール - 複数ã®ãƒªã‚½ãƒ¼ã‚¹ãŒè¨±å¯ã•ã‚Œãªããªã£ãŸã¨ãã«ã€ã‚¿ãƒ¼ã‚²ãƒƒãƒˆã‚·ã‚¹ãƒ†ãƒ ã€ã‚·ãƒ£ãƒ¼ã‚·ã€ã¾ãŸã¯ãƒžãƒãƒ¼ã‚¸ãƒ£ãƒ¼ã®ãƒªã‚½ãƒ¼ã‚¹ã® ID を指定ã›ãšã«ãƒ‡ãƒ¼ã‚¿å¤‰æ›´ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã™ã‚‹ã“ã¨ã¯ã§ããªããªã‚Šã¾ã—ãŸã€‚``resource_id`` オプションを使用ã—ã¦ã‚¿ãƒ¼ã‚²ãƒƒãƒˆIDを指定ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1926）。" +#~ msgid "If you use ansible-base and installed ``community.general`` manually and rely on the ``docker`` content, you have to make sure to install the ``community.docker`` collection as well. If you are using FQCNs, i.e. ``community.general.docker_container`` instead of ``docker_container``, it will continue working, but we still recommend to adjust the FQCNs as well." +#~ msgstr "ansible-base を使用ã—㦠``community.general`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€``docker`` コンテンツã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.docker`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ã¤ã¾ã‚Š ``docker_container`` ã®ä»£ã‚ã‚Šã« ``community.general.docker_container`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:682 -msgid "redfish_config - the parameters ``bios_attribute_name`` and ``bios_attribute_value`` have been removed. Use ``bios_attributes`` instead (https://github.com/ansible-collections/community.general/pull/1926)." -msgstr "redfish_config - ``bios_attribute_name`` パラメーターãŠã‚ˆã³ ``bios_attribute_value`` パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``bios_attributes`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" +#~ msgid "For community.general 2.0.0, the ``postgresql`` modules and plugins will be moved to the `community.postgresql <https://galaxy.ansible.com/community/postgresql>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." +#~ msgstr "community.general 2.0.0 ã®å ´åˆã€``postgresql`` モジュールãŠã‚ˆã³ãƒ—ラグイン㯠`community.postgresql <https://galaxy.ansible.com/community/postgresql>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:683 -msgid "syspatch - the ``apply`` parameter has been removed. This is the default mode, so simply removing it will not change the behavior (https://github.com/ansible-collections/community.general/pull/1926)." -msgstr "syspatch - ``apply`` パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“ã‚Œã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãƒ¢ãƒ¼ãƒ‰ã§ã‚ã‚‹ãŸã‚ã€å‰Šé™¤ã—ã¦ã‚‚動作ã¯å¤‰æ›´ã•ã‚Œã¾ã›ã‚“（https://github.com/ansible-collections/community.general/pull/1926）。" +#~ msgid "If you use Ansible 2.9 and explicitly use ``postgresql`` content from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.postgresql.`` instead of ``community.general.``, for example replace ``community.general.postgresql_info`` in a task by ``community.postgresql.postgresql_info``." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ ``postgresql`` コンテンツを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.general.`` ã§ã¯ãªã ``community.postgresql.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``community.postgresql.postgresql_info`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.general.postgresql_info`` ã‚’ç½®ãæ›ãˆã¾ã™)。" -#: ../../rst/porting_guides/porting_guide_4.rst:684 -msgid "xbps - the ``force`` parameter has been removed. It did not have any effect (https://github.com/ansible-collections/community.general/pull/1926)." -msgstr "xbps - ``force`` パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚影響ã¯ã‚ã‚Šã¾ã›ã‚“（https://github.com/ansible-collections/community.general/pull/1926）。" +#~ msgid "If you use ansible-base and installed ``community.general`` manually and rely on the ``postgresql`` content, you have to make sure to install the ``community.postgresql`` collection as well. If you are using FQCNs, i.e. ``community.general.postgresql_info`` instead of ``postgresql_info``, it will continue working, but we still recommend to adjust the FQCNs as well." +#~ msgstr "ansible-base を使用ã—㦠``community.general`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€``postgresql`` コンテンツã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.postgresql`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ã¤ã¾ã‚Š ``postgresql_info`` ã®ä»£ã‚ã‚Šã« ``community.general.postgresql_info`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:689 -msgid "The deprecated ``community.network.ce_sflow`` parameters: ``rate_limit``, ``rate_limit_slot``, and ``forward_enp_slot`` have been removed (https://github.com/ansible-collections/community.network/pull/255)." -msgstr "éžæŽ¨å¥¨ã® ``community.network.ce_sflow`` パラメーター（``rate_limit``ã€``rate_limit_slot``ã€ãŠã‚ˆã³ ``forward_enp_slot`` ）ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.network/pull/255）。" +#~ msgid "The community.general collection no longer depends on the ansible.posix collection (https://github.com/ansible-collections/community.general/pull/1157)." +#~ msgstr "community.general コレクション㯠ansible.posix コレクションã«ä¾å˜ã—ãªããªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/1157)。" -#: ../../rst/porting_guides/porting_guide_4.rst:690 -msgid "The deprecated ``community.network.sros`` netconf plugin has been removed. Use ``nokia.sros.md`` instead (https://github.com/ansible-collections/community.network/pull/255)." -msgstr "éžæŽ¨å¥¨ã® ``community.network.sros`` netconf プラグインãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``nokia.sros.md`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.network/pull/255）。" +#~ msgid "For community.network 2.0.0, the ``routeros`` modules and plugins will be moved to the `community.routeros <https://galaxy.ansible.com/community/routeros>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." +#~ msgstr "community.network 2.0.0 ã®å ´åˆã€``routeros`` モジュールãŠã‚ˆã³ãƒ—ラグイン㯠`community.routeros <https://galaxy.ansible.com/community/routeros>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:702 -msgid "Removed module fortios_facts" -msgstr "fortios_facts モジュールを削除" +#~ msgid "If you use Ansible 2.9 and explicitly use ``routeros`` content from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.routeros.`` instead of ``community.network.routeros_``, for example replace ``community.network.routeros_api`` in a task by ``community.routeros.api``." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ ``routeros`` コンテンツを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.network.routeros_`` ã§ã¯ãªã ``community.routeros.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``community.routeros.api`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.network.routeros_api`` ã‚’ç½®ãæ›ãˆã¾ã™)。" -#: ../../rst/porting_guides/porting_guide_4.rst:703 -msgid "Removed module fortios_registration_forticare" -msgstr "fortios_registration_forticare モジュールを削除" +#~ msgid "If you use ansible-base and installed ``community.network`` manually and rely on the ``routeros`` content, you have to make sure to install the ``community.routeros`` collection as well. If you are using FQCNs, i.e. ``community.network.routeros_command`` instead of ``routeros_command``, it will continue working, but we still recommend to adjust the FQCNs as well." +#~ msgstr "ansible-base を使用ã—㦠``community.network`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€``routeros`` コンテンツã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.routeros`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ã¤ã¾ã‚Š ``routeros_command`` ã®ä»£ã‚ã‚Šã« ``community.network.routeros_command`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_4.rst:704 -msgid "Removed module fortios_registration_vdom" -msgstr "fortios_registration_vdom モジュールを削除" +#~ msgid "In community.network 2.0.0, the ``fortimanager`` httpapi plugin will be removed and replaced by a redirect to the corresponding plugin in the fortios.fortimanager collection. For Ansible 2.10 and ansible-base 2.10 users, this means that it will continue to work assuming that collection is installed. For Ansible 2.9 users, this means that they have to adjust the FQCN from ``community.network.fortimanager`` to ``fortios.fortimanager.fortimanager`` (https://github.com/ansible-collections/community.network/pull/151)." +#~ msgstr "community.network 2.0.0 ã§ã¯ã€``fortimanager`` httpapi プラグインãŒå‰Šé™¤ã•ã‚Œã€fortios.fortimanager コレクションã«ã‚る対応ã™ã‚‹ãƒ—ラグインã¸ã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚Ansible 2.10 ãŠã‚ˆã³ ansible-base 2.10 ユーザーã®å ´åˆã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã¨ä»®å®šã—ã¦å‹•ä½œã¯ç¶™ç¶šã—ã¾ã™ã€‚Ansible 2.9 ユーザーã¯ã€FQCN ã‚’ ``community.network.fortimanager`` ã‹ã‚‰ ``fortios.fortimanager.fortimanager`` ã¸èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚(https://github.com/ansible-collections/community.network/pull/151)。" -#: ../../rst/porting_guides/porting_guide_4.rst:705 -msgid "Removed module fortios_system_config_backup_restore" -msgstr "fortios_system_config_backup_restore モジュールを削除" +#~ msgid "community.okd" +#~ msgstr "community.okd" -#: ../../rst/porting_guides/porting_guide_4.rst:706 -msgid "Removed module fortios_system_vmlicense" -msgstr "fortios_system_vmlicense モジュールを削除" +#~ msgid "Add custom k8s module, integrate better Molecule tests (https://github.com/ansible-collections/community.okd/pull/7)." +#~ msgstr "カスタムk8s ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’è¿½åŠ ã—ã€å„ªã‚ŒãŸ Molecule テストを統åˆã—ã¾ã™ (https://github.com/ansible-collections/community.okd/pull/7)。" -#: ../../rst/porting_guides/porting_guide_4.rst:714 -msgid "Starting in 2.14, shell and command modules will no longer have the option to warn and suggest modules in lieu of commands. The ``warn`` parameter to these modules is now deprecated and defaults to ``False``. Similarly, the ``COMMAND_WARNINGS`` configuration option is also deprecated and defaults to ``False``. These will be removed and their presence will become an error in 2.14." -msgstr "2.14 以é™ã€ã‚·ã‚§ãƒ«ãŠã‚ˆã³ã‚³ãƒžãƒ³ãƒ‰ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã§ã¯ã€ã‚³ãƒžãƒ³ãƒ‰ã®ä»£ã‚ã‚Šã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®è¦å‘ŠãŠã‚ˆã³æ案ã®ã‚ªãƒ—ションãŒãªããªã‚Šã¾ã—ãŸã€‚ã“れらã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã® ``warn`` パラメーターã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ ``False`` ã«ãªã‚Šã¾ã—ãŸã€‚åŒæ§˜ã«ã€``COMMAND_WARNINGS`` è¨å®šã‚ªãƒ—ションもéžæŽ¨å¥¨ã§ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã¯ ``False`` ã«è¨å®šã•ã‚Œã¾ã™ã€‚ã“れらã¯å‰Šé™¤ã•ã‚Œã€2.14 ã§ã¯ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚" +#~ msgid "Add downstream build scripts to build redhat.openshift (https://github.com/ansible-collections/community.okd/pull/20)." +#~ msgstr "redhat.openshift を構築ã™ã‚‹ãŸã‚ã®ãƒ€ã‚¦ãƒ³ã‚¹ãƒˆãƒªãƒ¼ãƒ ãƒ“ãƒ«ãƒ‰ã‚¹ã‚¯ãƒªãƒ—ãƒˆã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/ansible-collections/community.okd/pull/20)。" -#: ../../rst/porting_guides/porting_guide_4.rst:715 -msgid "apt_key - the parameter ``key`` does not have any effect, has been deprecated and will be removed in ansible-core version 2.14 (https://github.com/ansible/ansible/pull/70319)." -msgstr "apt_key - パラメーター ``key`` ã«ã¯å½±éŸ¿ãŒãªãã€éžæŽ¨å¥¨ã«ãªã‚Šã€ansible-core ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.14 ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ï¼ˆhttps://github.com/ansible/ansible/pull/70319）。" +#~ msgid "Add openshift connection plugin, update inventory plugin to use it (https://github.com/ansible-collections/community.okd/pull/18)." +#~ msgstr "openshift æŽ¥ç¶šãƒ—ãƒ©ã‚°ã‚¤ãƒ³ã‚’è¿½åŠ ã—ã€ä½¿ç”¨ã™ã‚‹ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ—ラグインを更新ã—ã¾ã™ (https://github.com/ansible-collections/community.okd/pull/18)。" -#: ../../rst/porting_guides/porting_guide_4.rst:716 -msgid "psrp - Set the minimum version of ``pypsrp`` to ``0.4.0``." -msgstr "psrp - ``pypsrp`` ã®æœ€å°ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’ ``0.4.0`` ã«è¨å®šã—ã¾ã™ã€‚" +#~ msgid "Add openshift_process module for template rendering and optional application of rendered resources (https://github.com/ansible-collections/community.okd/pull/44)." +#~ msgstr "テンプレートをレンダリングã—ã€ãƒ¬ãƒ³ãƒ€ãƒªãƒ³ã‚°ã•ã‚ŒãŸãƒªã‚½ãƒ¼ã‚¹ã®ä»»æ„ã®ã‚¢ãƒ—リケーション用㫠openshift_process ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/ansible-collections/community.okd/pull/44)。" -#: ../../rst/porting_guides/porting_guide_4.rst:721 -msgid "Deprecate cli_parse module and textfsm, ttp, xml, json parser plugins as they are moved to ansible.utils collection (https://github.com/ansible-collections/ansible.netcommon/pull/182 https://github.com/ansible-collections/ansible.utils/pull/28)" -msgstr "cli_parse モジュール㨠textfsmã€ttpã€xmlã€json パーサープラグイン㌠ansible.utils コレクションã«ç§»å‹•ã—ãŸãŸã‚ã€éžæŽ¨å¥¨ã«ãªã‚Šã¾ã™ï¼ˆhttps://github.com/ansible-collections/ansible.netcommon/pull/182 https://github.com/ansible-collections/ansible.utils/pull/28）。" +#~ msgid "Add openshift_route module for creating routes from services (https://github.com/ansible-collections/community.okd/pull/40)." +#~ msgstr "サービスã‹ã‚‰ãƒ«ãƒ¼ãƒˆã‚’作æˆã™ã‚‹ openshift_route ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/ansible-collections/community.okd/pull/40)。" -#: ../../rst/porting_guides/porting_guide_4.rst:726 -msgid "Deprecated nxos_bgp_af in favour of nxos_bgp_address_family resource module." -msgstr "nxos_bgp_af ãŒéžæŽ¨å¥¨ã«ãªã‚Šã€nxos_bgp_address_familyリソースモジュールãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" +#~ msgid "Initial content migration from community.kubernetes (https://github.com/ansible-collections/community.okd/pull/3)." +#~ msgstr "community.kubernetes ã‹ã‚‰ã®æœ€åˆã®ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã®ç§»è¡Œ (https://github.com/ansible-collections/community.okd/pull/3)。" -#: ../../rst/porting_guides/porting_guide_4.rst:727 -msgid "Deprecated nxos_bgp_neighbor_af in favour of nxos_bgp_neighbor_address_family resource module." -msgstr "nxos_bgp_neighbor_af ã‚’éžæŽ¨å¥¨ã«ã—ã€nxos_bgp_neighbor_address_family リソースモジュールãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" +#~ msgid "openshift_auth - new module (migrated from k8s_auth in community.kubernetes) (https://github.com/ansible-collections/community.okd/pull/33)." +#~ msgstr "openshift_auth - æ–°ã—ã„モジュール (community.kubernetes ã® k8s_auth ã‹ã‚‰ã®ç§»è¡Œ) (https://github.com/ansible-collections/community.okd/pull/33)。" -#: ../../rst/porting_guides/porting_guide_4.rst:752 -msgid "cpanm - parameter ``system_lib`` deprecated in favor of using ``become`` (https://github.com/ansible-collections/community.general/pull/2218)." -msgstr "cpanm - パラメーター ``system_lib`` ãŒéžæŽ¨å¥¨ã«ãªã‚Šã€https://github.com/ansible-collections/community.general/pull/360) ã®ä½¿ç”¨ãŒæŽ¡ç”¨ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/2218）。" +#~ msgid "Removed Features" +#~ msgstr "削除ã•ã‚ŒãŸæ©Ÿèƒ½" -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:6 -msgid "Ansible-base 2.10 Porting Guide" -msgstr "Ansible-base 2.10 移æ¤ã‚¬ã‚¤ãƒ‰" +#~ msgid "docker_container - no longer returns ``ansible_facts`` (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_container - ``ansible_facts`` ãŒè¿”ã•ã‚Œãªããªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:10 -msgid "In preparation for the release of 2.10, many plugins and modules have migrated to Collections on `Ansible Galaxy <https://galaxy.ansible.com>`_. For the current development status of Collections and FAQ see `Ansible Collections Community Guide <https://github.com/ansible-collections/overview/blob/main/README.rst>`_. We expect the 2.10 Porting Guide to change frequently up to the 2.10 release. Follow the conversations about collections on our various :ref:`communication` channels for the latest information on the status of the ``devel`` branch." -msgstr "2.10 ã®ãƒªãƒªãƒ¼ã‚¹æº–å‚™ã®ãŸã‚ã«ã€å¤šãã®ãƒ—ラグインãŠã‚ˆã³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒ `Ansible Galaxy <https://galaxy.ansible.com>`_ ã® Collection ã«ç§»è¡Œã—ã¦ã„ã¾ã™ã€‚Collection ãŠã‚ˆã³ FAQ ã®ç¾åœ¨ã®é–‹ç™ºã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã¯ã€ã€Œ`Ansible Collections コミュニティーガイド <https://github.com/ansible-collections/overview/blob/main/README.rst>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。2.10 ã®ã€Œç§»æ¤ã‚¬ã‚¤ãƒ‰ã€ã¯ã€2.10 ã®ãƒªãƒªãƒ¼ã‚¹ã«åˆã‚ã›ã¦é »ç¹ã«å¤‰æ›´ã™ã‚‹ã“ã¨ã‚’想定ã—ã¦ã„ã¾ã™ã€‚``devel`` ブランãƒã®ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã«é–¢ã™ã‚‹æœ€æ–°æƒ…å ±ã¯ã€ã•ã¾ã–ã¾ãª :ref:`communication` ãƒãƒ£ãƒ³ãƒãƒ«ã«ã‚るコレクションã«é–¢ã™ã‚‹è°è«–を確èªã—ã¦ãã ã•ã„。" +#~ msgid "docker_container - the default of ``networks_cli_compatible`` changed to ``true`` (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_container - ``networks_cli_compatible`` ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãŒ ``true`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:12 -msgid "This section discusses the behavioral changes between Ansible 2.9 and Ansible-base 2.10." -msgstr "ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€Ansible 2.9 㨠Ansible-base 2.10 ã§ã®å‹•ä½œã®å¤‰æ›´ç‚¹ã‚’説明ã—ã¾ã™ã€‚" +#~ msgid "docker_container - the unused option ``trust_image_content`` has been removed (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_container - 未使用ã®ã‚ªãƒ—ション ``trust_image_content`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:14 -msgid "It is intended to assist in updating your playbooks, plugins and other parts of your Ansible infrastructure so they will work with this version of Ansible-base." -msgstr "本ガイドã¯ã€ã“ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Ansible-base ã§å‹•ä½œã™ã‚‹ã‚ˆã†ã«ã€Playbookã€ãƒ—ラグインã€ãã®ä»–ã® Ansible インフラストラクãƒãƒ£ãƒ¼ã‚’æ›´æ–°ã™ã‚‹éš›ã«ã”利用ã«ãªã‚Šã¾ã™ã€‚" +#~ msgid "docker_image - ``state=build`` has been removed. Use ``present`` instead (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_image - ``state=build`` ã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``present`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:16 -msgid "We suggest you read this page along with the `Ansible-base Changelog for 2.10 <https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst>`_ to understand what updates you may need to make." -msgstr "å¿…è¦ãªæ›´æ–°ã«ã¤ã„ã¦ç†è§£ã™ã‚‹ã«ã¯ã€ã“ã®ãƒšãƒ¼ã‚¸ã¨ä½µã›ã¦ã€Œ`Ansible-base Changelog for 2.10 <https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" +#~ msgid "docker_image - the ``container_limits``, ``dockerfile``, ``http_timeout``, ``nocache``, ``rm``, ``path``, ``buildargs``, ``pull`` have been removed. Use the corresponding suboptions of ``build`` instead (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_image - ``container_limits``ã€``dockerfile``ã€``http_timeout``ã€``nocache``ã€``rm``ã€``path``ã€``buildargs``ã€``pull`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ 代ã‚ã‚Šã« ``build`` ã®è©²å½“ã™ã‚‹ã‚µãƒ–オプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:18 -msgid "Ansible-base is mainly of interest for developers and users who only want to use a small, controlled subset of the available collections. Regular users should install ansible." -msgstr "Ansible-base ã¯ã€ä¸»ã«ã€åˆ©ç”¨å¯èƒ½ãªã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ã†ã¡ã€åˆ¶å¾¡ã•ã‚ŒãŸå°ã•ãªã‚µãƒ–セットã®ã¿ã‚’使用ã—ãŸã„開発者やユーザーã®èˆˆå‘³ã‚’引ã製å“ã§ã™ã€‚一般ユーザー㯠Ansible をインストールã—ã¦ãã ã•ã„。" +#~ msgid "docker_image - the ``force`` option has been removed. Use the more specific ``force_*`` options instead (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_image - ``force`` オプションã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã«ã€ã‚ˆã‚Šå…·ä½“的㪠``force_*`` オプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:20 -#: ../../rst/porting_guides/porting_guide_core_2.11.rst:16 -msgid "The complete list of porting guides can be found at :ref:`porting guides <porting_guides>`." -msgstr "移æ¤ã‚¬ã‚¤ãƒ‰ã®å®Œå…¨ãªãƒªã‚¹ãƒˆã¯ã€ã€Œ:ref:`移æ¤ã‚¬ã‚¤ãƒ‰ <porting_guides>`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" +#~ msgid "docker_image - the ``source`` option is now mandatory (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_image - ``source`` オプションãŒå¿…é ˆã«ãªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_base_2.10.rst:23 -#: ../../rst/porting_guides/porting_guide_core_2.11.rst:18 -msgid "Contents" -msgstr "内容" +#~ msgid "docker_image - the ``use_tls`` option has been removed. Use ``tls`` and ``validate_certs`` instead (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_image - ``use_tls`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``tls`` ãŠã‚ˆã³ ``validate_certs`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_core_2.11.rst:6 -msgid "Ansible-core 2.11 Porting Guide" -msgstr "Ansible-core 2.11 移æ¤ã‚¬ã‚¤ãƒ‰" +#~ msgid "docker_image - the default of the ``build.pull`` option changed to ``false`` (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_image - ``build.pull`` オプションã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãŒ ``false`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_core_2.11.rst:8 -msgid "This section discusses the behavioral changes between ``ansible-base`` 2.10 and ``ansible-core`` 2.11." -msgstr "ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€``ansible-base`` 2.10 ã‹ã‚‰ ``ansible-core`` 2.11 ã«ãŠã‘る動作ã®å¤‰æ›´ç‚¹ã‚’説明ã—ã¾ã™ã€‚" +#~ msgid "docker_image_facts - this alias is on longer availabe, use ``docker_image_info`` instead (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_image - ã“ã®ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã¯åˆ©ç”¨ã§ããªããªã‚Šã¾ã™ã€‚代ã‚ã‚Šã« ``docker_image_info`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_core_2.11.rst:10 -msgid "It is intended to assist in updating your playbooks, plugins and other parts of your Ansible infrastructure so they work with this version of ``ansible-core``." -msgstr "本ガイドã¯ã€ã“ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® ``ansible-core`` ã§å‹•ä½œã™ã‚‹ã‚ˆã†ã«ã€Playbookã€ãƒ—ラグインã€ãã®ä»–ã® Ansible インフラストラクãƒãƒ£ãƒ¼ã‚’æ›´æ–°ã™ã‚‹éš›ã«ã”利用ã«ãªã‚Œã¾ã™ã€‚" +#~ msgid "docker_network - no longer returns ``ansible_facts`` (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_network - ``ansible_facts`` ãŒè¿”ã•ã‚Œãªããªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_core_2.11.rst:12 -msgid "We suggest you read this page along with the `ansible-core Changelog for 2.11 <https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst>`_ to understand what updates you may need to make." -msgstr "å¿…è¦ãªæ›´æ–°ã«ã¤ã„ã¦ç†è§£ã™ã‚‹ã«ã¯ã€ã“ã®ãƒšãƒ¼ã‚¸ã¨ä½µã›ã¦ã€Œ`ansible-core Changelog for 2.11 <https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" +#~ msgid "docker_network - the ``ipam_options`` option has been removed. Use ``ipam_config`` instead (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_network - ``ipam_options`` オプションã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``ipam_config`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_core_2.11.rst:14 -msgid "``ansible-core`` is mainly of interest for developers and users who only want to use a small, controlled subset of the available collections. Regular users should install Ansible." -msgstr "``ansible-core`` ã¯ã€ä¸»ã«ã€åˆ©ç”¨å¯èƒ½ãªã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ã†ã¡ã€åˆ¶å¾¡ã•ã‚ŒãŸå°ã•ãªã‚µãƒ–セットã®ã¿ã‚’使用ã—ãŸã„開発者やユーザーã®èˆˆå‘³ã‚’引ã製å“ã§ã™ã€‚一般ユーザー㯠Ansible をインストールã—ã¦ãã ã•ã„。" +#~ msgid "docker_service - no longer returns ``ansible_facts`` (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_service - ``ansible_facts`` ãŒè¿”ã•ã‚Œãªããªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:6 -msgid "Ansible-core 2.12 Porting Guide" -msgstr "Ansible-core 2.12 移æ¤ã‚¬ã‚¤ãƒ‰" +#~ msgid "docker_swarm - ``state=inspect`` has been removed. Use ``docker_swarm_info`` instead (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_swarm - ``state=inspect`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``docker_swarm_info`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:8 -msgid "This section discusses the behavioral changes between ``ansible-core`` 2.11 and ``ansible-core`` 2.12." -msgstr "ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€``ansible-core`` 2.11 ã‹ã‚‰ ``ansible-core`` 2.12 ã«ãŠã‘る動作ã®å¤‰æ›´ç‚¹ã‚’説明ã—ã¾ã™ã€‚" +#~ msgid "docker_swarm_service - the ``constraints`` option has been removed. Use ``placement.constraints`` instead (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_swarm_service - ``constraints`` オプションã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``placement.constraints`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:12 -msgid "We suggest you read this page along with `ansible-core Changelog for 2.12 <https://github.com/ansible/ansible/blob/devel/changelogs/CHANGELOG-v2.12.rst>`_ to understand what updates you may need to make." -msgstr "å¿…è¦ãªæ›´æ–°ã«ã¤ã„ã¦ç†è§£ã™ã‚‹ã«ã¯ã€ã“ã®ãƒšãƒ¼ã‚¸ã¨ä½µã›ã¦ã€Œ`ansible-core Changelog for 2.12 <https://github.com/ansible/ansible/blob/devel/changelogs/CHANGELOG-v2.12.rst>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" +#~ msgid "docker_swarm_service - the ``limit_cpu`` and ``limit_memory`` options has been removed. Use the corresponding suboptions in ``limits`` instead (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_swarm_service - ``limit_cpu`` オプションãŠã‚ˆã³ ``limit_memory`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``limits`` ã§å¯¾å¿œã™ã‚‹ã‚µãƒ–オプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:22 -msgid "When calling tasks and setting ``async``, setting ``ANSIBLE_ASYNC_DIR`` under ``environment:`` is no longer valid. Instead, use the shell configuration variable ``async_dir``, for example by setting ``ansible_async_dir``:" -msgstr "タスクを呼ã³å‡ºã—㦠``async`` ã‚’è¨å®šã™ã‚‹å ´åˆã¯ã€``environment:`` 㧠``ANSIBLE_ASYNC_DIR`` ã®è¨å®šã¯æœ‰åŠ¹ã§ã¯ãªããªã‚Šã¾ã—ãŸã€‚代ã‚ã‚Šã«ã€``ansible_async_dir`` ã‚’è¨å®šã—ã¦ã‚·ã‚§ãƒ«è¨å®šå¤‰æ•° ``async_dir`` を使用ã—ã¾ã™ã€‚" +#~ msgid "docker_swarm_service - the ``log_driver`` and ``log_driver_options`` options has been removed. Use the corresponding suboptions in ``logging`` instead (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_swarm_service - ``log_driver`` オプションãŠã‚ˆã³ ``log_driver_options`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``logging`` ã§å¯¾å¿œã™ã‚‹ã‚µãƒ–オプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:38 -msgid "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``." -msgstr "``INTERPRETER_PYTHON_FALLBACK`` ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã¯ ``auto`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã—ãŸãŒã€``INTERPRETER_PYTHON_FALLBACK`` ã® Python インタープリターã®ãƒªã‚¹ãƒˆãŒã€Python 2 よりも Python 3 を優先ã™ã‚‹ã‚ˆã†ã«å¤‰æ›´ã•ã‚Œã¾ã—ãŸã€‚ã“れらã®å¤‰æ›´ã®çµ„ã¿åˆã‚ã›ã«ã‚ˆã‚Šã€æ–°ã—ã„デフォルト動作ã§ã¯ã€ãƒªãƒ¢ãƒ¼ãƒˆãƒ›ã‚¹ãƒˆã® Python 2 よりも Python 3 ãŒæš—黙的ã«å„ªå…ˆã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¾ã§ã€ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ—リター検出㧠Python 3 ãŒä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹ã¨ã„ã†éžæŽ¨å¥¨ã®è¦å‘Šã¯ã€Python 3 を使用ã—ã¾ã™ãŒã€ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ—リターã®æ¤œå‡ºãŒ ``/usr/bin/python`` ã«è¨å®šã•ã‚Œã¦ã„る状態ã§ã—ãŸã€‚" +#~ msgid "docker_swarm_service - the ``reserve_cpu`` and ``reserve_memory`` options has been removed. Use the corresponding suboptions in ``reservations`` instead (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_swarm_service - ``reserve_cpu`` オプションãŠã‚ˆã³ ``reserve_memory`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``reservations`` ã§å¯¾å¿œã™ã‚‹ã‚µãƒ–オプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:40 -msgid "``INTERPRETER_PYTHON_FALLBACK`` can be changed from the default list of interpreters by setting the ``ansible_interpreter_python_fallback`` variable." -msgstr "``INTERPRETER_PYTHON_FALLBACK`` ã¯ã€``ansible_interpreter_python_fallback`` 変数をè¨å®šã—ã¦ã€ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ—リターã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãƒªã‚¹ãƒˆã‹ã‚‰å¤‰æ›´ã§ãã¾ã™ã€‚" +#~ msgid "docker_swarm_service - the ``restart_policy``, ``restart_policy_attempts``, ``restart_policy_delay`` and ``restart_policy_window`` options has been removed. Use the corresponding suboptions in ``restart_config`` instead (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_swarm_service - ``restart_policy`` オプションã€``restart_policy_attempts`` オプションã€``restart_policy_delay`` オプションã€ãŠã‚ˆã³ ``restart_policy_window`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``restart_config`` ã§å¯¾å¿œã™ã‚‹ã‚µãƒ–オプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:42 -msgid "See :ref:`interpreter discovery documentation <interpreter_discovery>` for more details." -msgstr "詳細ã¯ã€:ref:`interpreter discovery documentation <interpreter_discovery>` ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" +#~ msgid "docker_swarm_service - the ``update_delay``, ``update_parallelism``, ``update_failure_action``, ``update_monitor``, ``update_max_failure_ratio`` and ``update_order`` options has been removed. Use the corresponding suboptions in ``update_config`` instead (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_swarm_service - ``update_delay`` オプションã€``update_parallelism`` オプションã€``update_failure_action`` オプションã€``update_monitor``ã€``update_max_failure_ratio`` オプションã€ãŠã‚ˆã³ ``update_order`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``update_config`` ã§å¯¾å¿œã™ã‚‹ã‚µãƒ–オプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:48 -msgid "Python 3.8 on the controller node is a hard requirement for this release. The command line scripts will not function with a lower Python version." -msgstr "コントãƒãƒ¼ãƒ©ãƒ¼ãƒŽãƒ¼ãƒ‰ã® Python 3.8 ã¯ã€æœ¬ãƒªãƒªãƒ¼ã‚¹ã§ã¯ãƒãƒ¼ãƒ‰è¦ä»¶ã§ã™ã€‚コマンドラインスクリプトã¯ã€ã‚ˆã‚Šä½Žã„ Python ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã¯æ©Ÿèƒ½ã—ã¾ã›ã‚“。" +#~ msgid "docker_volume - no longer returns ``ansible_facts`` (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_volume - ``ansible_facts`` ãŒè¿”ã•ã‚Œãªããªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:49 -msgid "``ansible-vault`` no longer supports ``PyCrypto`` and requires ``cryptography``." -msgstr "``ansible-vault`` 㯠``PyCrypto`` ã«å¯¾å¿œã—ãªããªã‚Šã€``cryptography`` ãŒå¿…è¦ãªããªã‚Šã¾ã—ãŸã€‚" +#~ msgid "docker_volume - the ``force`` option has been removed. Use ``recreate`` instead (https://github.com/ansible-collections/community.docker/pull/1)." +#~ msgstr "docker_volume - ``force`` オプションã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``recreate`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.docker/pull/1)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:54 -msgid "Python 2.6 on the target node is deprecated in this release. ``ansible-core`` 2.13 will remove support for Python 2.6." -msgstr "ターゲットノード上㮠Python 2.6 ã¯æœ¬ãƒªãƒªãƒ¼ã‚¹ã§éžæŽ¨å¥¨ã¨ãªã‚Šã¾ã—ãŸã€‚``ansible-core`` 2.13 ã§ã¯ã€Python 2.6 ã®ã‚µãƒãƒ¼ãƒˆãŒå‰Šé™¤ã•ã‚Œã¾ã™ã€‚" +#~ msgid "django_manage - the parameter ``liveserver`` relates to a no longer maintained third-party module for django. It is now deprecated, and will be remove in community.general 3.0.0 (https://github.com/ansible-collections/community.general/pull/1154)." +#~ msgstr "django_manage - パラメーター ``liveserver`` ã¯ã€django ã®ç¶æŒã•ã‚Œã¦ã„るサードパーティーモジュールã«é–¢é€£ã—ãªããªã‚Šã¾ã—ãŸã€‚ç¾åœ¨ã¯éžæŽ¨å¥¨ã«ãªã‚Šã€community.general 3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/1154)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:55 -msgid "Bare variables in conditionals: ``when`` conditionals no longer automatically parse string booleans such as ``\"true\"`` and ``\"false\"`` into actual booleans. Any variable containing a non-empty string is considered true. This was previously configurable with the ``CONDITIONAL_BARE_VARS`` configuration option (and the ``ANSIBLE_CONDITIONAL_BARE_VARS`` environment variable). This setting no longer has any effect. Users can work around the issue by using the ``|bool`` filter:" -msgstr "æ¡ä»¶ã®ãƒ™ã‚¢ãƒ¡ã‚¿ãƒ«å¤‰æ•°: ``when`` æ¡ä»¶ã¯ã€``\"true\"`` ã‚„ ``\"false\"`` ãªã©ã®æ–‡å—列ブール値を実際ã®ãƒ–ール値ã«è‡ªå‹•çš„ã«è§£æžã—ãªããªã‚Šã¾ã—ãŸã€‚空ã§ãªã„æ–‡å—列をå«ã‚€å¤‰æ•°ã¯ true ã¨è¦‹ãªã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ä»¥å‰ã¯ ``CONDITIONAL_BARE_VARS`` è¨å®šã‚ªãƒ—ション（ãŠã‚ˆã³ ``ANSIBLE_CONDITIONAL_BARE_VARS`` 環境変数）ã§è¨å®šå¯èƒ½ã§ã—ãŸã€‚ã“ã®è¨å®šã¯å½±éŸ¿ã¯ã‚ã‚Šã¾ã›ã‚“。``|bool`` フィルターを使用ã™ã‚‹ã“ã¨ã§å•é¡Œã‚’回é¿ã§ãã¾ã™ã€‚" +#~ msgid "proxmox - the default of the new ``proxmox_default_behavior`` option will change from ``compatibility`` to ``no_defaults`` in community.general 4.0.0. Set the option to an explicit value to avoid a deprecation warning (https://github.com/ansible-collections/community.general/pull/850)." +#~ msgstr "proxmox - æ–°ã—ã„ ``proxmox_default_behavior`` オプションã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãŒ community.general 4.0.0 㧠``compatibility`` ã‹ã‚‰ ``no_defaults`` ã«å¤‰æ›´ã—ã¾ã™ã€‚éžæŽ¨å¥¨ã®è¦å‘Šã‚’防ããŸã‚ã«ã€ã‚ªãƒ—ションを明示的ãªå€¤ã«è¨å®šã—ã¾ã™ (https://github.com/ansible-collections/community.general/pull/850))。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:69 -msgid "The ``_remote_checksum()`` method in ``ActionBase`` is deprecated. Any action plugin using this method should use ``_execute_remote_stat()`` instead." -msgstr "``ActionBase`` ã® ``_remote_checksum()`` メソッドã¯éžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚ã“ã®ãƒ¡ã‚½ãƒƒãƒ‰ã‚’使用ã™ã‚‹ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ãƒ—ラグインã¯ã€ä»£ã‚ã‚Šã« ``_execute_remote_stat()`` を使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" +#~ msgid "proxmox_kvm - the default of the new ``proxmox_default_behavior`` option will change from ``compatibility`` to ``no_defaults`` in community.general 4.0.0. Set the option to an explicit value to avoid a deprecation warning (https://github.com/ansible-collections/community.general/pull/850)." +#~ msgstr "proxmox_kvm - æ–°ã—ã„ ``proxmox_default_behavior`` オプションã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãŒ community.general 4.0.0 㧠``compatibility`` ã‹ã‚‰ ``no_defaults`` ã«å¤‰æ›´ã•ã‚Œã¾ã™ã€‚éžæŽ¨å¥¨ã®è¦å‘Šã‚’防ããŸã‚ã«ã€ã‚ªãƒ—ションを明示的ãªå€¤ã«è¨å®šã—ã¾ã™ (https://github.com/ansible-collections/community.general/pull/850)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:74 -msgid "``cron`` now requires ``name`` to be specified in all cases." -msgstr "``cron`` ã¯ã€ã™ã¹ã¦ã®ã‚±ãƒ¼ã‚¹ã§ ``name`` を指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" +#~ msgid "syspatch - deprecate the redundant ``apply`` argument (https://github.com/ansible-collections/community.general/pull/360)." +#~ msgstr "syspatch - 冗長㪠``apply`` 引数をéžæŽ¨å¥¨ã«ã—ã¾ã™ (https://github.com/ansible-collections/community.general/pull/360)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:75 -msgid "``cron`` no longer allows a ``reboot`` parameter. Use ``special_time: reboot`` instead." -msgstr "``cron`` ã¯ã€``reboot`` パラメーターãŒè¨±å¯ã•ã‚Œãªããªã‚Šã¾ã—ãŸã€‚代ã‚ã‚Šã« ``special_time: reboot`` を使用ã—ã¦ãã ã•ã„。" +#~ msgid "Deprecate connection=local support for network platforms using persistent framework (https://github.com/ansible-collections/community.network/pull/120)." +#~ msgstr "永続的ãªãƒ•ãƒ¬ãƒ¼ãƒ ワークを使用ã—ãŸãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ—ラットフォーム㮠connection=local サãƒãƒ¼ãƒˆã‚’éžæŽ¨å¥¨ã«ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.network/pull/120)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:76 -msgid "``hostname`` - On FreeBSD, the ``before`` result will no longer be ``\"temporarystub\"`` if permanent hostname file does not exist. It will instead be ``\"\"`` (empty string) for consistency with other systems." -msgstr "``hostname`` - FreeBSD ã§ã¯ã€æ°¸ç¶šçš„ãªãƒ›ã‚¹ãƒˆåファイルãŒå˜åœ¨ã—ãªã„å ´åˆã€``before`` ã®çµæžœã¯ ``\"temporarystub\"`` ã«ãªã‚‰ãªããªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã¯ã€ä»–ã®ã‚·ã‚¹ãƒ†ãƒ ã¨ã®æ•´åˆæ€§ã‚’ä¿ã¤ãŸã‚ã« ``\"\"`` （空ã®æ–‡å—列）ã«ãªã‚Šã¾ã™ã€‚" +#~ msgid "Porting Guide for v2.10.2" +#~ msgstr "v2.10.2 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:77 -msgid "``hostname`` - On OpenRC and Solaris based systems, the ``before`` result will no longer be ``\"UNKNOWN\"`` if the permanent hostname file does not exist. It will instead be ``\"\"`` (empty string) for consistency with other systems." -msgstr "``hostname`` - OpenRC ãŠã‚ˆã³ Solaris ベースã®ã‚·ã‚¹ãƒ†ãƒ ã§ã¯ã€æ°¸ç¶šçš„ãªãƒ›ã‚¹ãƒˆåファイルãŒå˜åœ¨ã—ãªã„å ´åˆã€``before`` ã®çµæžœã¯ ``\"UNKNOWN\"`` ã«ãªã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€ä»–ã®ã‚·ã‚¹ãƒ†ãƒ ã¨ã®æ•´åˆæ€§ã‚’ä¿ã¤ãŸã‚ã« ``\"\"``（空ã®æ–‡å—列）ã«ãªã‚Šã¾ã™ã€‚" +#~ msgid "Ansible-base" +#~ msgstr "Ansible-base" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:78 -msgid "``pip`` now uses the ``pip`` Python module installed for the Ansible module's Python interpreter, if available, unless ``executable`` or ``virtualenv`` were specified." -msgstr "``pip`` ã¯ã€``executable`` ã¾ãŸã¯ ``virtualenv`` ãŒæŒ‡å®šã•ã‚Œã¦ã„ãªã„é™ã‚Šã€Ansible モジュール㮠Python インタープリターã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚ŒãŸ ``pip`` Python モジュールを使用ã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" +#~ msgid "ansible-galaxy login command has been removed (see https://github.com/ansible/ansible/issues/71560)" +#~ msgstr "ansible-galaxy login コマンドãŒå‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible/ansible/issues/71560) ã‚’å‚ç…§)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:104 -msgid "``unique`` filter with Jinja2 < 2.10 is case-sensitive and now raise coherently an error if ``case_sensitive=False`` instead of when ``case_sensitive=True``." -msgstr "2.10 よりå‰ã® Jinja2 を使用ã™ã‚‹ ``unique`` フィルターã¯ã€å¤§æ–‡å—ã¨å°æ–‡å—ãŒåŒºåˆ¥ã•ã‚Œã€``case_sensitive=True`` ã§ã¯ãªã ``case_sensitive=False`` ã®å ´åˆã«ä¸€è²«ã—ã¦ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã—ã¦ã„ã¾ã—ãŸã€‚" +#~ msgid "Add phone home Teem integration into all modules, functionality can be disabled by setting up F5_TEEM environment variable or no_f5_teem provider parameter" +#~ msgstr "ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã« phone home Teem çµ±åˆã‚’è¿½åŠ ã—ã¾ã™ã€‚F5_TEEM 環境変数ã¾ãŸã¯ no_f5_teem プãƒãƒã‚¤ãƒ€ãƒ¼ãƒ‘ラメーターをè¨å®šã—ã¦æ©Ÿèƒ½ã‚’無効ã«ã§ãã¾ã™ã€‚" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:105 -msgid "Set theory filters (``intersect``, ``difference``, ``symmetric_difference`` and ``union``) are now case-sensitive. Explicitly use ``case_sensitive=False`` to keep previous behavior. Note: with Jinja2 < 2.10, the filters were already case-sensitive by default." -msgstr "ç†è«–フィルター（``intersect``ã€``difference``ã€``symmetric_difference``ã€ãŠã‚ˆã³ ``union``）ã®è¨å®šã¯ã€å¤§æ–‡å—ã¨å°æ–‡å—ãŒåŒºåˆ¥ã•ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚明示的㪠``case_sensitive=False`` を使用ã—ã¦ä»¥å‰ã®å‹•ä½œã‚’ç¶æŒã—ã¾ã™ã€‚2.10 よりå‰ã® Jinja2 ã§ã€ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã¯ã™ã§ã«å¤§æ–‡å—ã¨å°æ–‡å—を区別ã—ã¦ã„ã¾ã™ã€‚" +#~ msgid "cluster_upgrade - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/94)." +#~ msgstr "cluster_upgrade - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/94)。" -#: ../../rst/porting_guides/porting_guide_core_2.12.rst:106 -msgid "``password_hash``` now uses ``passlib`` defaults when an option is unspecified, e.g. ``bcrypt_sha256`` now default to the \"2b\" format and if the \"2a\" format is required it must be specified." -msgstr "``password_hash``` now uses ``passlib`` defaults when an option is unspecified, e.g. ``bcrypt_sha256`` ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã€Œ2bã€ãƒ•ã‚©ãƒ¼ãƒžãƒƒãƒˆã«ãªã‚Šã€ã€Œ2aã€ãƒ•ã‚©ãƒ¼ãƒžãƒƒãƒˆãŒå¿…è¦ãªå ´åˆã¯æŒ‡å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" +#~ msgid "disaster_recovery - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/134)." +#~ msgstr "disaster_recovery - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/134)。" -#: ../../rst/porting_guides/porting_guides.rst:5 -msgid "Ansible Porting Guides" -msgstr "Ansible 移æ¤ã‚¬ã‚¤ãƒ‰" +#~ msgid "engine_setup - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/69)." +#~ msgstr "engine_setup - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/69)。" -#: ../../rst/porting_guides/porting_guides.rst:7 -msgid "This section lists porting guides that can help you in updating playbooks, plugins and other parts of your Ansible infrastructure from one version of Ansible to the next." -msgstr "本セクションã§ã¯ã€Ansible ã®ã‚ã‚‹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‹ã‚‰æ¬¡ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«ã€Ansible インフラストラクãƒãƒ£ãƒ¼ã® Playbookã€ãƒ—ラグインãªã©ã‚’æ›´æ–°ã™ã‚‹ã®ã«å½¹ã«ç«‹ã¤ç§»æ¤ã‚¬ã‚¤ãƒ‰ã‚’紹介ã—ã¾ã™ã€‚" +#~ msgid "hosted_engine_setup - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/106)." +#~ msgstr "hosted_engine_setup - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/106)。" -#~ msgid "We suggest you read this page along with the `ansible-core Changelog for 2.11 <https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst>`_ to understand what updates you may need to make." -#~ msgstr "" +#~ msgid "image_template - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/95)." +#~ msgstr "image_template - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/95)。" -#~ msgid "The configuration system now validates the ``choices`` field, so any settings that currently violate it and are currently ignored will now cause an error. For example, `ANSIBLE_COLLECTIONS_ON_ANSIBLE_VERSION_MISMATCH=0` will now cause an error (valid chioces are 'ignore', 'warn' or 'error'." -#~ msgstr "" +#~ msgid "infra - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/92)." +#~ msgstr "infra - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/92)。" -#~ msgid "Due to a scheduling conflict, the latest version of Ansible 2.10 (2.10.7) has a few collections which are newer than Ansible 3.0.0. Ansible 3.1.0 will contain updated versions of those collections." -#~ msgstr "スケジュールã®éƒ½åˆä¸Šã€Ansible 2.10 ã®æœ€æ–°ç‰ˆ (2.10.7) ã«ã¯ã€Ansible 3.0.0 よりも新ã—ã„コレクションãŒã„ãã¤ã‹ã‚ã‚Šã¾ã™ã€‚Ansible 3.1.0 ã«ã¯ã€ã“れらã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ã‚¢ãƒƒãƒ—デート版ãŒå«ã¾ã‚Œã¾ã™ã€‚" +#~ msgid "manageiq - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/97)." +#~ msgstr "manageiq - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/97)。" -#~ msgid "Python 3.8 on the controller node is a soft requirement for this release. ``ansible-core`` 2.11 will continue to work with the same versions of Python that ``ansible-base`` 2.10 worked with, however it will emit a warning when running on a controller node with a Python version less than 3.8. This warning can be disabled by setting ``ANSIBLE_CONTROLLER_PYTHON_WARNING=False`` in your environment. ``ansible-core`` 2.12 will require Python 3.8 or greater." -#~ msgstr "コントãƒãƒ¼ãƒ©ãƒ¼ãƒŽãƒ¼ãƒ‰ã® Python 3.8 ã¯ã€æœ¬ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã‚½ãƒ•ãƒˆè¦ä»¶ã§ã™ã€‚``ansible-core`` 2.11 ã¯ã€``ansible-base`` 2.10 ãŒå‹•ä½œã—ãŸã®ã¨åŒã˜ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Python ã§å¼•ã続ã機能ã—ã¾ã™ãŒã€Python ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒ 3.8 未満ã®ã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©ãƒ¼ãƒŽãƒ¼ãƒ‰ã§å®Ÿè¡Œã™ã‚‹ã¨è¦å‘ŠãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚ã“ã®è¦å‘Šã¯ã€ãŠä½¿ã„ã®ç’°å¢ƒã« ``ANSIBLE_CONTROLLER_PYTHON_WARNING=False`` ã‚’è¨å®šã—ã¦ç„¡åŠ¹ã«ã§ãã¾ã™ã€‚``ansible-core`` 2.12 ã®å ´åˆã¯ Python 3.8 以é™ãŒå¿…è¦ã«ãªã‚Šã¾ã™ã€‚" +#~ msgid "repositories - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/96)." +#~ msgstr "repositories - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/96)。" -#~ msgid "The configuration system now validates the ``choices`` field, so any settings that currently violate it and are currently ignored will now cause an error. For example, `ANSIBLE_COLLECTIONS_ON_ANSIBLE_VERSION_MISMATCH=0` will now cause an error (valid choices are 'ignore', 'warn' or 'error')." -#~ msgstr "è¨å®šã‚·ã‚¹ãƒ†ãƒ 㯠``choices`` フィールドを検証ã™ã‚‹ãŸã‚ã€ç¾åœ¨ãã‚Œã«é•åã—ã¦ã„ã‚‹è¨å®šãŒã‚ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ãŒç”Ÿã˜ã¾ã™ã€‚ãŸã¨ãˆã°ã€`ANSIBLE_COLLECTIONS_ON_ANSIBLE_VERSION_MISMATCH=0` ã‚’é¸æŠžã™ã‚‹ã¨ã€ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã—ã¾ã™ (有効ãªé¸æŠžè‚¢ã¯ã€Œignoreã€ã€ã€Œwarnã€ã€ã¾ãŸã¯ã€Œerrorã€ã§ã™)。" +#~ msgid "shutdown_env - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/112)." +#~ msgstr "shutdown_env - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/112)" + +#~ msgid "vm_infra - Migrate role (https://github.com/oVirt/ovirt-ansible-collection/pull/93)." +#~ msgstr "vm_infra - ãƒãƒ¼ãƒ«ã‚’移行ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/93)。" + +#~ msgid "Removed arp_state parameter from the bigip_virtual_address module" +#~ msgstr "bigip_virtual_address モジュールã‹ã‚‰ arp_state パラメーターを削除ã—ã¾ã—ãŸã€‚" + +#~ msgid "Deprecated `nxos_interface_ospf` in favor of `nxos_ospf_interfaces` Resource Module." +#~ msgstr "`nxos_interface_ospf` ã‚’éžæŽ¨å¥¨ã«ã—ã€`nxos_ospf_interfaces` Resource Module ãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "Porting Guide for v2.10.1" +#~ msgstr "v2.10.1 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" + +#~ msgid "community.kubernetes" +#~ msgstr "community.kubernetes" + +#~ msgid "k8s - Add support for template parameter (https://github.com/ansible-collections/community.kubernetes/pull/230)." +#~ msgstr "k8s - テンプレートパラメーターã®ã‚µãƒãƒ¼ãƒˆã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/ansible-collections/community.kubernetes/pull/230)。" + +#~ msgid "k8s_* - Add support for vaulted kubeconfig and src (https://github.com/ansible-collections/community.kubernetes/pull/193)." +#~ msgstr "k8s_* - Vault 済㿠kubeconfig ãŠã‚ˆã³ src ã®ã‚µãƒãƒ¼ãƒˆã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/ansible-collections/community.kubernetes/pull/193)。" + +#~ msgid "Deprecated `nxos_smu` in favor of `nxos_rpm` module." +#~ msgstr "`nxos_smu` ã‚’éžæŽ¨å¥¨ã«ã—ã€`nxos_rpm` モジュールãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The `nxos_ospf_vrf` module is deprecated by `nxos_ospfv2` and `nxos_ospfv3` Resource Modules." +#~ msgstr "`nxos_ospf_vrf` モジュールã¯ã€`nxos_ospfv2` ãŠã‚ˆã³ `nxos_ospfv3` Resource Module ã«ã‚ˆã£ã¦éžæŽ¨å¥¨ã¨ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "Porting Guide for v2.10.0" +#~ msgstr "v2.10.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" + +#~ msgid "Known Issues" +#~ msgstr "既知ã®å•é¡Œ" + +#~ msgid "Due to a limitation in pip, you cannot ``pip install --upgrade`` from ansible-2.9 or earlier to ansible-2.10 or higher. Instead, you must explicitly use ``pip uninstall ansible`` before pip installing the new version. If you attempt to upgrade Ansible with pip without first uninstalling, the installer warns you to uninstall first." +#~ msgstr "pip ã®åˆ¶é™ã«ã‚ˆã‚Šã€ansible-2.9 以å‰ã‹ã‚‰ ansible-2.10 以é™ã«ã¯ ``pip install --upgrade`` ã‚’è¡Œã†ã“ã¨ãŒã§ãã¾ã›ã‚“。代ã‚ã‚Šã«ã€pip ã§æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’インストールã™ã‚‹å‰ã« ``pip uninstall ansible`` を明示的ã«ä½¿ç”¨ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚最åˆã«ã‚¢ãƒ³ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã›ãšã« pip 㧠Ansible をアップグレードã™ã‚‹å ´åˆã¯ã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ©ãƒ¼ãŒæœ€åˆã«ã‚¢ãƒ³ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã‚’è¦å‘Šã—ã¾ã™ã€‚" + +#~ msgid "The individual collections that make up the ansible-2.10.0 package can be viewed independently. However, they are not currently listed by ansible-galaxy. To view these collections with ansible-galaxy, explicitly specify where ansible has installed the collections -- ``COLLECTION_INSTALL=$(python -c 'import ansible, os.path ; print(\"%s/../ansible_collections\" % os.path.dirname(ansible.__file__))') ansible-galaxy collection list -p \"$COLLECTION_INSTALL\"``." +#~ msgstr "ansible-2.10.0 パッケージを構æˆã™ã‚‹å€‹ã€…ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã¯å€‹åˆ¥ã«è¡¨ç¤ºã§ãã¾ã™ãŒã€ç¾åœ¨ ansible-galaxy ã«ã‚ˆã‚Šä¸€è¦§è¡¨ç¤ºã•ã‚Œã¦ã„ã¾ã›ã‚“。ansible-galaxy ã§ã“れらã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’表示ã™ã‚‹ã«ã¯ã€ansible ãŒã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´æ‰€ã‚’明示的ã«æŒ‡å®šã—ã¾ã™ã€‚``COLLECTION_INSTALL=$(python -c 'import ansible, os.path ; print(\"%s/../ansible_collections\" % os.path.dirname(ansible.__file__))') ansible-galaxy collection list -p \"$COLLECTION_INSTALL\"``" + +#~ msgid "These fortios modules are not automatically redirected from their 2.9.x names to the new 2.10.x names within collections. You must modify your playbooks to use fully qualified collection names for them. You can use the documentation (https://docs.ansible.com/ansible/2.10/collections/fortinet/fortios/) for the ``fortinet.fortios`` collection to determine what the fully qualified collection names are." +#~ msgstr "ã“れら㮠fortios モジュールã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³å†…㧠2.9.x ã®åå‰ã‹ã‚‰æ–°ã—ã„ 2.10.x ã®åå‰ã«è‡ªå‹•çš„ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã•ã‚Œã¾ã›ã‚“。ã“れらã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«å®Œå…¨ä¿®é£¾ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³åを使用ã™ã‚‹ã‚ˆã†ã« Playbook を変更ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚完全修飾コレクションåã«ã¤ã„ã¦ã¯ã€``fortinet.fortios`` コレクションã®ãƒ‰ã‚ュメント (https://docs.ansible.com/ansible/2.10/collections/fortinet/fortios/)) ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "fortios_address" +#~ msgstr "fortios_address" + +#~ msgid "fortios_config" +#~ msgstr "fortios_config" + +#~ msgid "fortios_firewall_DoS_policy" +#~ msgstr "fortios_firewall_DoS_policy" + +#~ msgid "fortios_firewall_DoS_policy6" +#~ msgstr "fortios_firewall_DoS_policy6" + +#~ msgid "fortios_ipv4_policy" +#~ msgstr "fortios_ipv4_policy" + +#~ msgid "fortios_switch_controller_802_1X_settings" +#~ msgstr "fortios_switch_controller_802_1X_settings" + +#~ msgid "fortios_switch_controller_security_policy_802_1X" +#~ msgstr "fortios_switch_controller_security_policy_802_1X" + +#~ msgid "fortios_system_firmware_upgrade" +#~ msgstr "fortios_system_firmware_upgrade" + +#~ msgid "fortios_system_nd_proxy" +#~ msgstr "fortios_system_nd_proxy" + +#~ msgid "fortios_webfilter" +#~ msgstr "fortios_webfilter" + +#~ msgid "community.grafana" +#~ msgstr "community.grafana" + +#~ msgid "grafana_datasource doesn't set password correctly (#113)" +#~ msgstr "grafana_datasource ã§ãƒ‘スワードãŒæ£ã—ãè¨å®šã•ã‚Œãªã„ (#113)" + +#~ msgid "cisco.nxos.nxos_igmp_interface - no longer supports the deprecated ``oif_prefix`` and ``oif_source`` options. These have been superceeded by ``oif_ps``." +#~ msgstr "cisco.nxos.nxos_igmp_interface - éžæŽ¨å¥¨ã® ``oif_prefix`` オプションãŠã‚ˆã³ ``oif_source`` オプションをサãƒãƒ¼ãƒˆã—ãªããªã‚Šã¾ã—ãŸã€‚ã“れら㯠``oif_ps`` ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "community.grafana.grafana_dashboard - the parameter ``message`` is renamed to ``commit_message`` since ``message`` is used by Ansible Core engine internally." +#~ msgstr "community.grafana.grafana_dashboard - ``message`` ã¯å†…部的㫠Ansible Core Engine ã§ä½¿ç”¨ã•ã‚Œã‚‹ãŸã‚ã€ãƒ‘ラメーター ``message`` ã®åå‰ãŒ ``commit_message`` ã«å¤‰æ›´ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "purestorage.flashblade.purefb_fs - no longer supports the deprecated ``nfs`` option. This has been superceeded by ``nfsv3``." +#~ msgstr "purestorage.flashblade.purefb_fs - éžæŽ¨å¥¨ã® ``nfs`` オプションã«å¯¾å¿œã—ãªããªã‚Šã¾ã—ãŸã€‚ã“れ㯠``nfsv3`` ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "amazon.aws" +#~ msgstr "amazon.aws" + +#~ msgid "aws_s3 - can now delete versioned buckets even when they are not empty - set mode to delete to delete a versioned bucket and everything in it." +#~ msgstr "aws_s3 - ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚¢ãƒƒãƒ—ã•ã‚ŒãŸãƒã‚±ãƒƒãƒˆãŒç©ºã§ãªãã¦ã‚‚削除ã§ãるよã†ã«ãªã‚Šã¾ã—ãŸã€‚モードを delete ã«è¨å®šã™ã‚‹ã¨ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚¢ãƒƒãƒ—ã•ã‚ŒãŸãƒã‚±ãƒƒãƒˆã¨ãã®ä¸ã®ã‚‚ã®ãŒã™ã¹ã¦å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "ansible.windows" +#~ msgstr "ansible.windows" + +#~ msgid "setup - Make sure ``ansible_date_time.epoch`` is seconds since EPOCH in UTC to mirror the POSIX facts. The ``ansible_date_time.epoch_local`` contains seconds since EPOCH in the local timezone for backwards compatibility" +#~ msgstr "setup - POSIX ファクトをåæ˜ ã•ã›ã‚‹ãŸã‚ã«ã€``ansible_date_time.epoch`` ㌠UTC ã® EPOCH 以é™ã®ç§’æ•°ã§ã‚ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚後方互æ›ã®ãŸã‚ã«ã€``ansible_date_time.epoch_local`` ã«ã¯ã€ãƒãƒ¼ã‚«ãƒ«ã‚¿ã‚¤ãƒ ゾーン㮠EPOCH 以é™ã®ç§’æ•°ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚" + +#~ msgid "setup - Will now add the IPv6 scope on link local addresses for ``ansible_ip_addresses``" +#~ msgstr "setup - ``ansible_ip_addresses`` ã®ãƒªãƒ³ã‚¯ãƒãƒ¼ã‚«ãƒ«ã‚¢ãƒ‰ãƒ¬ã‚¹ã« IPv6 ã‚¹ã‚³ãƒ¼ãƒ—ã‚’è¿½åŠ ã—ã¾ã™ã€‚" + +#~ msgid "setup - ``ansible_processor`` will now return the index before the other values to match the POSIX fact behaviour" +#~ msgstr "setup - ``ansible_processor`` ãŒã€POSIX ファクトã®å‹•ä½œã«ä¸€è‡´ã™ã‚‹ãŸã‚ã«ä»–ã®å€¤ã®å‰ã«ã‚¤ãƒ³ãƒ‡ãƒƒã‚¯ã‚¹ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "win_find - No longer filters by size on directories, this feature had a lot of bugs, slowed down the module, and not a supported scenario with the ``find`` module." +#~ msgstr "win_find - ディレクトリーã«ãŠã„ã¦ã‚µã‚¤ã‚ºã§ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ãŒè¨å®šã•ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã€ã“ã®æ©Ÿèƒ½ã¯ãƒã‚°ãŒå¤šããªã‚Šã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®é€Ÿåº¦ãŒä½Žä¸‹ã—ã€``find`` モジュールã§ã®å¯¾å¿œã‚·ãƒŠãƒªã‚ªã¯ã‚ã‚Šã¾ã›ã‚“。" + +#~ msgid "win_find - module has been refactored to better match the behaviour of the ``find`` module. Here is what has changed:" +#~ msgstr "win_find - モジュールã¯ã€``find`` モジュールã®å‹•ä½œã«åˆã‚ã›ã¦ãƒªãƒ•ã‚¡ã‚¯ã‚¿ãƒªãƒ³ã‚°ã•ã‚Œã¾ã—ãŸã€‚ã“ã‚ŒãŒå¤‰æ›´ã«ãªã‚Šã¾ã—ãŸ:" + +#~ msgid "When the directory specified by ``paths`` does not exist or is a file, it will no longer fail and will just warn the user" +#~ msgstr "``paths`` ã§æŒ‡å®šã•ã‚ŒãŸãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ãŒå˜åœ¨ã—ãªã„ã‹ã€ãƒ•ã‚¡ã‚¤ãƒ«ã§ã‚ã‚‹ã¨ã€å¤±æ•—ã—ãªããªã‚Šã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«è¦å‘ŠãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" + +#~ msgid "Junction points are no longer reported as ``islnk``, use ``isjunction`` to properly report these files. This behaviour matches the win_stat module" +#~ msgstr "ジャンクションãƒã‚¤ãƒ³ãƒˆã¯ ``islnk`` ã¨ã—ã¦å ±å‘Šã•ã‚Œãªããªã‚Šã¾ã—ãŸã€‚ã“れらã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’æ£ã—ãå ±å‘Šã™ã‚‹ã«ã¯ ``isjunction`` を使用ã—ã¦ãã ã•ã„。ã“ã®å‹•ä½œã¯ win_stat モジュールã¨ä¸€è‡´ã—ã¾ã™ã€‚" + +#~ msgid "Directories no longer return a ``size``, this matches the ``stat`` and ``find`` behaviour and has been removed due to the difficulties in correctly reporting the size of a directory" +#~ msgstr "ディレクトリー㌠``size`` ã‚’è¿”ã•ãªããªã‚Šã¾ã—ãŸã€‚ã“れ㯠``stat`` ãŠã‚ˆã³ ``find`` ã®å‹•ä½œã¨ä¸€è‡´ã—ã€ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã®ã‚µã‚¤ã‚ºã‚’æ£ã—ãå ±å‘Šã™ã‚‹ã“ã¨ãŒå›°é›£ã§ã‚ã‚‹ãŸã‚ã€å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "win_user - Change idempotency checks for ``description`` to be case sensitive" +#~ msgstr "win_user - 大文å—ã¨å°æ–‡å—を区別ã™ã‚‹ãŸã‚ã« ``description`` ã®å†ªç‰æ€§ãƒã‚§ãƒƒã‚¯ã‚’変更ã—ã¾ã™ã€‚" + +#~ msgid "win_user - Change idempotency checks for ``fullname`` to be case sensitive" +#~ msgstr "win_user - 大文å—ã¨å°æ–‡å—を区別ã™ã‚‹ãŸã‚ã« ``fullname`` ã®å†ªç‰æ€§ãƒã‚§ãƒƒã‚¯ã‚’変更ã—ã¾ã™ã€‚" + +#~ msgid "cisco.meraki" +#~ msgstr "cisco.meraki" + +#~ msgid "meraki_device - Changed tags from string to list" +#~ msgstr "meraki_device - æ–‡å—列ã‹ã‚‰ãƒªã‚¹ãƒˆã«ã‚¿ã‚°ã‚’変更ã—ã¾ã—ãŸã€‚" + +#~ msgid "meraki_device - Removed serial_lldp_cdp parameter" +#~ msgstr "meraki_device - serial_lldp_cdp パラメーターを削除ã—ã¾ã—ãŸã€‚" + +#~ msgid "meraki_device - Removed serial_uplink parameter" +#~ msgstr "meraki_device - serial_uplink パラメーターを削除ã—ã¾ã—ãŸã€‚" + +#~ msgid "meraki_intrusion_prevention - Rename whitedlisted_rules to allowed_rules" +#~ msgstr "meraki_intrusion_prevention - whitedlisted_rules ã®åå‰ã‚’ allowed_rules ã«å¤‰æ›´ã—ã¾ã™ã€‚" + +#~ msgid "meraki_mx_l3_firewall - Rule responses are now in a `rules` list" +#~ msgstr "meraki_mx_l3_firewall - ルール応ç”㌠`rules` リストã«è¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" + +#~ msgid "meraki_mx_l7_firewall - Rename blacklisted_countries to blocked_countries" +#~ msgstr "meraki_mx_l7_firewall - blocked_countries ã®åå‰ã‚’ blacklisted_countries ã«å¤‰æ›´ã—ã¾ã™ã€‚" + +#~ msgid "meraki_mx_l7_firewall - Rename whitelisted_countries to allowed_countries" +#~ msgstr "meraki_mx_l7_firewall - whitelisted_countries ã®åå‰ã‚’ allowed_countries ã«å¤‰æ›´ã—ã¾ã™ã€‚" + +#~ msgid "meraki_network - Local and remote status page settings cannot be set during network creation" +#~ msgstr "meraki_network - ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã®ä½œæˆæ™‚ã«ãƒãƒ¼ã‚«ãƒ«ãŠã‚ˆã³ãƒªãƒ¢ãƒ¼ãƒˆã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ãƒšãƒ¼ã‚¸è¨å®šã‚’è¨å®šã§ãã¾ã›ã‚“。" + +#~ msgid "meraki_network - `disableRemoteStatusPage` response is now `remote_status_page_enabled`" +#~ msgstr "meraki_network - `disableRemoteStatusPage` ã®å¿œç”㌠`remote_status_page_enabled` ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "meraki_network - `disable_my_meraki_com` response is now `local_status_page_enabled`" +#~ msgstr "meraki_network - `disable_my_meraki_com` ã®å¿œç”㌠`local_status_page_enabled` ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "meraki_network - `disable_my_meraki` has been deprecated" +#~ msgstr "meraki_network - `disable_my_meraki` ãŒéžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "meraki_network - `enable_my_meraki` is now called `local_status_page_enabled`" +#~ msgstr "meraki_network - `enable_my_meraki` ㌠`local_status_page_enabled` ã¨å‘¼ã°ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "meraki_network - `enable_remote_status_page` is now called `remote_status_page_enabled`" +#~ msgstr "meraki_network - `enable_remote_status_page` ㌠`remote_status_page_enabled` ã¨å‘¼ã°ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "meraki_network - `enabled` response for VLAN status is now `vlans_enabled`" +#~ msgstr "meraki_network - VLAN ステータスã«å¯¾ã™ã‚‹ `enabled` å¿œç”㌠`vlans_enabled` ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "meraki_network - `tags` and `type` now return a list" +#~ msgstr "meraki_network - `tags` ãŠã‚ˆã³ `type` ãŒä¸€è¦§ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "meraki_snmp - peer_ips is now a list" +#~ msgstr "meraki_snmp - peer_ips ãŒãƒªã‚¹ãƒˆã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "meraki_switchport - `access_policy_number` is now an int and not a string" +#~ msgstr "meraki_switchport - `access_policy_number` ã¯æ–‡å—列型ã§ã¯ãªã int åž‹ã«ãªã‚Šã¾ã—ãŸ" + +#~ msgid "meraki_switchport - `tags` is now a list and not a string" +#~ msgstr "meraki_switchport - `tags` ãŒæ–‡å—列型ã§ã¯ãªãリスト型ã«ãªã‚Šã¾ã—ãŸ" + +#~ msgid "meraki_webhook - Querying test status now uses state of query." +#~ msgstr "meraki_webhook - テストステータスã®ã‚¯ã‚¨ãƒªãƒ¼ã¯ã‚¯ã‚¨ãƒªãƒ¼çŠ¶æ…‹ã‚’使用ã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "The environment variable for the auth context for the oc.py connection plugin has been corrected (K8S_CONTEXT). It was using an initial lowercase k by mistake. (https://github.com/ansible-collections/community.general/pull/377)." +#~ msgstr "oc.py 接続プラグインã®èªè¨¼ã‚³ãƒ³ãƒ†ã‚ストã®ç’°å¢ƒå¤‰æ•° (K8S_CONTEXT) ãŒä¿®æ£ã•ã‚Œã¾ã—ãŸã€‚ã“ã‚Œã¯ã€æœ€åˆã®å°æ–‡å—ã® k ã‚’é–“é•ã£ã¦ä½¿ç”¨ã—ã¦ã„ã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/377)。" + +#~ msgid "bigpanda - the parameter ``message`` was renamed to ``deployment_message`` since ``message`` is used by Ansible Core engine internally." +#~ msgstr "bigpanda - ``message`` 㯠Ansible Core Engine ã§å†…部的ã«ä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹ãŸã‚ã€ãƒ‘ラメーター ``message`` 㯠``deployment_message`` ã«å¤‰æ›´ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "cisco_spark - the module option ``message`` was renamed to ``msg``, as ``message`` is used internally in Ansible Core engine (https://github.com/ansible/ansible/issues/39295)" +#~ msgstr "cisco_spark - Ansible Core エンジン㧠``message`` ãŒå†…部ã§ä½¿ç”¨ã•ã‚Œã‚‹ãŸã‚ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚ªãƒ—ション ``message`` ã®åå‰ãŒ ``msg`` ã«å¤‰æ›´ã•ã‚Œã¾ã—㟠(https://github.com/ansible/ansible/issues/39295)。" + +#~ msgid "datadog - the parameter ``message`` was renamed to ``notification_message`` since ``message`` is used by Ansible Core engine internally." +#~ msgstr "datadog - ``message`` 㯠Ansible Core Engine ã§å†…部的ã«ä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹ãŸã‚ã€ãƒ‘ラメーターã®åå‰ ``message`` 㯠``notification_message`` ã«å¤‰æ›´ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "docker_container - no longer passes information on non-anonymous volumes or binds as ``Volumes`` to the Docker daemon. This increases compatibility with the ``docker`` CLI program. Note that if you specify ``volumes: strict`` in ``comparisons``, this could cause existing containers created with docker_container from Ansible 2.9 or earlier to restart." +#~ msgstr "docker_container - 匿åã§ãªã„ボリュームã®æƒ…å ±ã‚„ ``Volumes`` ã¨ã—ã¦ã®ãƒã‚¤ãƒ³ãƒ‰ã‚’ Docker デーモンã«æ¸¡ã•ãªããªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã«ã‚ˆã‚Šã€``docker`` CLI プãƒã‚°ãƒ©ãƒ ã¨ã®äº’æ›æ€§ãŒé«˜ã¾ã‚Šã¾ã—ãŸã€‚ãªãŠã€``comparisons`` ã«``volumes: strict`` を指定ã™ã‚‹ã¨ã€Ansible 2.9 以å‰ã® docker_container ã§ä½œæˆã•ã‚ŒãŸæ—¢å˜ã®ã‚³ãƒ³ãƒ†ãƒŠãƒ¼ãŒå†èµ·å‹•ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "docker_container - support for port ranges was adjusted to be more compatible to the ``docker`` command line utility: a one-port container range combined with a multiple-port host range will no longer result in only the first host port be used, but the whole range being passed to Docker so that a free port in that range will be used." +#~ msgstr "docker_container - ãƒãƒ¼ãƒˆç¯„囲ã®ã‚µãƒãƒ¼ãƒˆã¯ã€``docker`` コマンドラインユーティリティーã¨ã®äº’æ›æ€§ã‚’高ã‚ã‚‹ãŸã‚ã«èª¿æ•´ã•ã‚Œã¾ã—ãŸã€‚1 ãƒãƒ¼ãƒˆã®ã‚³ãƒ³ãƒ†ãƒŠãƒ¼ç¯„囲ã¨è¤‡æ•°ãƒãƒ¼ãƒˆã®ãƒ›ã‚¹ãƒˆç¯„囲を組ã¿åˆã‚ã›ãŸå ´åˆã¯ã€æœ€åˆã®ãƒ›ã‚¹ãƒˆãƒãƒ¼ãƒˆã®ã¿ãŒä½¿ç”¨ã•ã‚Œã‚‹ã“ã¨ã¯ãªããªã‚Šã€ç¯„囲全体㌠Docker ã«æ¸¡ã•ã‚Œã€ãã®ç¯„囲内ã®ç©ºããƒãƒ¼ãƒˆãŒä½¿ç”¨ã•ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "hashi_vault lookup - now returns the latest version when using the KV v2 secrets engine. Previously, it returned all versions of the secret which required additional steps to extract and filter the desired version." +#~ msgstr "hashi_vault lookup - KV v2 シークレットエンジンを使用ã™ã‚‹éš›ã«ã€æœ€æ–°ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã¾ã§ã¯ã€ã™ã¹ã¦ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ã‚·ãƒ¼ã‚¯ãƒ¬ãƒƒãƒˆãŒè¿”ã•ã‚Œã¦ã„ãŸãŸã‚ã€ç›®çš„ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’抽出ã—ã¦ãƒ•ã‚£ãƒ«ã‚¿ãƒªãƒ³ã‚°ã™ã‚‹ãŸã‚ã®è¿½åŠ æ‰‹é †ãŒå¿…è¦ã§ã—ãŸã€‚" + +#~ msgid "log_plays callback - add missing information to the logs generated by the callback plugin. This changes the log message format (https://github.com/ansible-collections/community.general/pull/442)." +#~ msgstr "log_plays callback - callback プラグインã§ç”Ÿæˆã•ã‚ŒãŸãƒã‚°ã«ä¸è¶³ã—ã¦ã„ã‚‹æƒ…å ±ã‚’è¿½åŠ ã—ã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ãƒã‚°ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã®å½¢å¼ãŒå¤‰æ›´ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/442)。" + +#~ msgid "pkgng - passing ``name: *`` with ``state: absent`` will no longer remove every installed package from the system. It is now a noop. (https://github.com/ansible-collections/community.general/pull/569)." +#~ msgstr "pkgng - ``name: *`` ã« ``state: absent`` を渡ã™ã¨ã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«æ¸ˆã¿ãƒ‘ッケージãŒã™ã¹ã¦ã‚·ã‚¹ãƒ†ãƒ ã‹ã‚‰å‰Šé™¤ã•ã‚Œãªããªã‚Šã€noop ã«ãªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/569)。" + +#~ msgid "pkgng - passing ``name: *`` with ``state: latest`` or ``state: present`` will no longer install every package from the configured package repositories. Instead, ``name: *, state: latest`` will upgrade all already-installed packages, and ``name: *, state: present`` is a noop. (https://github.com/ansible-collections/community.general/pull/569)." +#~ msgstr "pkgng - ``name: *`` ã« ``state: latest`` ã¾ãŸã¯``state: present`` を渡ã™ã¨ã€è¨å®šã•ã‚ŒãŸãƒ‘ッケージリãƒã‚¸ãƒˆãƒªãƒ¼ã‹ã‚‰ã™ã¹ã¦ã®ãƒ‘ッケージをインストールã—ãªããªã‚Šã¾ã™ã€‚代ã‚ã‚Šã«ã€``name: *, state: latest`` ã¯æ—¢ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„るパッケージをã™ã¹ã¦ã‚¢ãƒƒãƒ—グレードã—ã€``name: *, state: present`` 㯠noop ã§ã™ (https://github.com/ansible-collections/community.general/pull/569)。" + +#~ msgid "routeros_facts - allow multiple addresses and neighbors per interface. This makes ``ansible_net_neighbors`` a list instead of a dict (https://github.com/ansible-collections/community.network/pull/6)." +#~ msgstr "routeros_facts - インターフェースã”ã¨ã«è¤‡æ•°ã®ã‚¢ãƒ‰ãƒ¬ã‚¹ã¨è¿‘接アドレスを許å¯ã—ã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€``ansible_net_neighbors`` ㌠dict ã§ã¯ãªã list ã«ãªã‚Šã¾ã™ (https://github.com/ansible-collections/community.network/pull/6)。" + +#~ msgid "vmware_datastore_maintenancemode - now returns ``datastore_status`` instead of Ansible internal key ``results``." +#~ msgstr "vmware_datastore_maintenancemode - Ansible 内部ã‚ー ``results`` ã®ä»£ã‚ã‚Šã« ``datastore_status`` ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "vmware_guest_custom_attributes - does not require VM name which was a required parameter for releases prior to Ansible 2.10." +#~ msgstr "vmware_guest_custom_attributes - Ansible 2.10 よりå‰ã®ãƒªãƒªãƒ¼ã‚¹ã§å¿…é ˆã ã£ãŸãƒ‘ラメーターã§ã‚る仮想マシンåã¯å¿…è¦ã‚ã‚Šã¾ã›ã‚“。" + +#~ msgid "vmware_guest_find - the ``datacenter`` option has been removed." +#~ msgstr "vmware_guest_find - ``datacenter`` オプションã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "vmware_host_kernel_manager - now returns ``host_kernel_status`` instead of Ansible internal key ``results``." +#~ msgstr "vmware_host_kernel_manager - Ansible 内部ã‚ー ``results`` ã®ä»£ã‚ã‚Šã« ``host_kernel_status`` ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "vmware_host_ntp - now returns ``host_ntp_status`` instead of Ansible internal key ``results``." +#~ msgstr "vmware_host_ntp - Ansible 内部ã‚ー ``results`` ã®ä»£ã‚ã‚Šã« ``host_ntp_status`` ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "vmware_host_service_manager - now returns ``host_service_status`` instead of Ansible internal key ``results``." +#~ msgstr "vmware_host_service_manager - Ansible 内部ã‚ー ``results`` ã®ä»£ã‚ã‚Šã« ``host_service_status`` ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "vmware_tag - now returns ``tag_status`` instead of Ansible internal key ``results``." +#~ msgstr "vmware_tag - Ansible 内部ã‚ー ``results`` ã®ä»£ã‚ã‚Šã« ``tag_status`` ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "vmware_vmkernel - the options ``ip_address`` and ``subnet_mask`` have been removed; use the suboptions ``ip_address`` and ``subnet_mask`` of the ``network`` option instead." +#~ msgstr "vmware_vmkernel - ``ip_address`` オプションãŠã‚ˆã³ ``subnet_mask`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``network`` オプションã®ã‚µãƒ–オプション ``ip_address`` ãŠã‚ˆã³ ``subnet_mask`` を使用ã—ã¦ãã ã•ã„。" + +#~ msgid "community.windows" +#~ msgstr "community.windows" + +#~ msgid "win_pester - no longer runs all ``*.ps1`` file in the directory specified due to it executing potentially unknown scripts. It will follow the default behaviour of only running tests for files that are like ``*.tests.ps1`` which is built into Pester itself." +#~ msgstr "win_pester - 未知ã®ã‚¹ã‚¯ãƒªãƒ—トを実行ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚‹ãŸã‚ã€æŒ‡å®šã—ãŸãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼å†…ã®ã™ã¹ã¦ã® ``*.ps1`` ファイルを実行ã—ãªããªã‚Šã¾ã—ãŸã€‚Pester 自体ã«çµ„ã¿è¾¼ã¾ã‚Œã¦ã„ã‚‹ ``*.tests.ps1`` ã®ã‚ˆã†ãªãƒ•ã‚¡ã‚¤ãƒ«ã«å¯¾ã—ã¦ã®ã¿ãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ã¨ã„ã†ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã®å‹•ä½œã«å¾“ã„ã¾ã™ã€‚" + +#~ msgid "community.zabbix" +#~ msgstr "community.zabbix" + +#~ msgid "zabbix_javagateway - options ``javagateway_pidfile``, ``javagateway_listenip``, ``javagateway_listenport`` and ``javagateway_startpollers`` renamed to ``zabbix_javagateway_xyz`` (see `UPGRADE.md <https://github.com/ansible-collections/community.zabbix/blob/main/docs/UPGRADE.md>`_)." +#~ msgstr "zabbix_javagateway - ``javagateway_pidfile`` オプションã€``javagateway_listenip`` オプションã€``javagateway_listenport``ã€ãŠã‚ˆã³ ``javagateway_startpollers`` オプションã®åå‰ãŒ ``zabbix_javagateway_xyz`` ã«å¤‰æ›´ã•ã‚Œã¦ã„ã¾ã™ (`UPGRADE.md <https://github.com/ansible-collections/community.zabbix/blob/main/docs/UPGRADE.md>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„)。" + +#~ msgid "Change ``ip-addresses`` key in netbox inventory plugin to ``ip_addresses`` (https://github.com/netbox-community/ansible_modules/issues/139)" +#~ msgstr "netbox インベントリープラグイン㮠``ip-addresses`` ã‚ーを ``ip_addresses`` ã«å¤‰æ›´ã—ã¾ã™ (https://github.com/netbox-community/ansible_modules/issues/139)。" + +#~ msgid "Changed ``group`` to ``tenant_group`` in ``netbox_tenant.py`` (https://github.com/netbox-community/ansible_modules/issues/9)" +#~ msgstr "``netbox_tenant.py`` ã® ``group`` ã‚’ ``tenant_group`` ã¸å¤‰æ›´ã—ã¾ã—㟠(https://github.com/netbox-community/ansible_modules/issues/9)。" + +#~ msgid "Changed ``role`` to ``prefix_role`` in ``netbox_prefix.py`` (https://github.com/netbox-community/ansible_modules/issues/9)" +#~ msgstr "``netbox_prefix.py`` ã® ``role`` ã‚’ ``prefix_role`` ã¸å¤‰æ›´ã—ã¾ã—㟠(https://github.com/netbox-community/ansible_modules/issues/9)。" + +#~ msgid "Module failures when required fields arent provided (https://github.com/netbox-community/ansible_modules/issues/24)" +#~ msgstr "å¿…é ˆãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ãŒæä¾›ã•ã‚Œã¦ã„ãªã„å ´åˆã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®å¤±æ•— (https://github.com/netbox-community/ansible_modules/issues/24)" + +#~ msgid "Renamed ``netbox_interface`` to ``netbox_device_interface`` (https://github.com/netbox-community/ansible_modules/issues/9)" +#~ msgstr "``netbox_interface`` ã®åå‰ãŒ ``netbox_device_interface`` ã«å¤‰æ›´ (https://github.com/netbox-community/ansible_modules/issues/9)" + +#~ msgid "This version has a few breaking changes due to new namespace and collection name. I felt it necessary to change the name of the lookup plugin and inventory plugin just not to have a non descriptive namespace call to use them. Below is an example: ``netbox.netbox.netbox`` would be used for both inventory plugin and lookup plugin, but in different contexts so no collision will arise, but confusion will. I renamed the lookup plugin to ``nb_lookup`` so it will be used with the FQCN ``netbox.netbox.nb_lookup``. The inventory plugin will now be called within an inventory file by ``netbox.netbox.nb_inventory``" +#~ msgstr "ã“ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«ã¯ã€æ–°ã—ã„åå‰ç©ºé–“ã¨ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³åã®ãŸã‚ã«ã„ãã¤ã‹ã®é‡å¤§ãªå¤‰æ›´ãŒã‚ã‚Šã¾ã™ã€‚lookup プラグイン㨠inventory プラグインã®åå‰ã‚’変更ã—ã¦ã€ãれを使用ã™ã‚‹ãŸã‚ã®éžè¨˜è¿°çš„ãªåå‰ç©ºé–“呼ã³å‡ºã—ã‚’è¡Œã‚ãªã„よã†ã«ã™ã‚‹å¿…è¦ãŒã‚ã‚‹ã¨æ„Ÿã˜ã¾ã—ãŸã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚inventory プラグイン㨠lookup プラグインã®ä¸¡æ–¹ã« ``netbox.netbox.netbox`` ãŒä½¿ç”¨ã•ã‚Œã¾ã™ãŒã€ã‚³ãƒ³ãƒ†ã‚ストãŒç•°ãªã‚‹ãŸã‚ã€è¡çªã¯ç™ºç”Ÿã—ã¾ã›ã‚“ãŒã€æ··ä¹±ãŒç™ºç”Ÿã—ã¾ã™ã€‚lookup プラグインã®åå‰ã‚’ ``nb_lookup`` ã«å¤‰æ›´ã—ã¾ã—ãŸã€‚ãã®ãŸã‚ã€FQCN ``netbox.netbox.nb_lookup`` ã§ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚インベントリープラグインã¯ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ•ã‚¡ã‚¤ãƒ«å†…㧠``netbox.netbox.nb_inventory`` ã«ã‚ˆã‚Šå‘¼ã³å‡ºã•ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" + +#~ msgid "To pass in integers via Ansible Jinja filters for a key in ``data`` that requires querying an endpoint is now done by making it a dictionary with an ``id`` key. The previous behavior was to just pass in an integer and it was converted when normalizing the data, but some people may have names that are all integers and those were being converted erroneously so we made the decision to change the method to convert to an integer for the NetBox API." +#~ msgstr "エンドãƒã‚¤ãƒ³ãƒˆã¸ã®å•ã„åˆã‚ã›ãŒå¿…è¦ãª ``data`` ã®ã‚ーã«å¯¾ã—ã¦ã€Ansible Jinja ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã§æ•´æ•°ã‚’渡ã™ãŸã‚ã«ã¯ã€``id`` ã‚ーをæŒã¤ãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼ã«ã™ã‚‹ã“ã¨ã§è¡Œã†ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã¾ã§ã®å‹•ä½œã§ã¯ã€æ•´æ•°ã‚’渡ã™ã ã‘ã§ãƒ‡ãƒ¼ã‚¿ã®æ£è¦åŒ–時ã«å¤‰æ›ã•ã‚Œã¦ã„ã¾ã—ãŸãŒã€äººã«ã‚ˆã£ã¦ã¯åå‰ãŒã™ã¹ã¦æ•´æ•°ã§ã‚ã‚‹å ´åˆãŒã‚ã‚Šã€ãれらãŒèª¤ã£ã¦å¤‰æ›ã•ã‚Œã¦ã„ãŸãŸã‚ã€NetBox API ã§ã¯æ•´æ•°ã«å¤‰æ›ã™ã‚‹æ–¹æ³•ã«å¤‰æ›´ã™ã‚‹ã“ã¨ã«ã—ã¾ã—ãŸã€‚" + +#~ msgid "``pynetbox`` changed to using ``requests.Session()`` to manage the HTTP session which broke passing in ``ssl_verify`` when building the NetBox API client. This PR makes ``pynetbox 5.0.4+`` the new required version of `pynetbox` for the Ansible modules and lookup plugin. (https://github.com/netbox-community/ansible_modules/pull/269)" +#~ msgstr "``pynetbox`` ã¯ã€NetBox API クライアントを構築ã™ã‚‹éš›ã« ``ssl_verify`` を渡ã™ã“ã¨ãŒã§ããªããªã£ãŸãŸã‚ã€HTTP セッションã®ç®¡ç†ã« ``requests.Session()`` を使用ã™ã‚‹ã‚ˆã†ã«å¤‰æ›´ã—ã¾ã—ãŸã€‚ã“ã® PR ã«ã‚ˆã‚Šã€``pynetbox 5.0.4+`` ã¯ã€Ansible モジュール㨠lookup プラグインã«å¿…è¦ãª `pynetbox` ã®æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¨ãªã‚Šã¾ã—㟠(https://github.com/netbox-community/ansible_modules/pull/269)。" + +#~ msgid "theforeman.foreman" +#~ msgstr "theforeman.foreman" + +#~ msgid "All modules were renamed to drop the ``foreman_`` and ``katello_`` prefixes. Additionally to the prefix removal, the following modules were further ranamed:" +#~ msgstr "ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®åå‰ãŒ ``foreman_`` 接é 辞ãŠã‚ˆã³ ``katello_`` 接é 辞を削除ã™ã‚‹ã‚ˆã†ã«å¤‰æ›´ã•ã‚Œã¾ã—ãŸã€‚接é 辞ã®å‰Šé™¤ä»¥å¤–ã«ã€ä»¥ä¸‹ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®åå‰ãŒã•ã‚‰ã«ç„¡è¦–ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "katello_upload to content_upload" +#~ msgstr "katello_upload ã‹ã‚‰ content_upload ã¸" + +#~ msgid "katello_sync to repository_sync" +#~ msgstr "katello_sync ã‹ã‚‰ repository_sync ã¸" + +#~ msgid "katello_manifest to subscription_manifest" +#~ msgstr "katello_manifest ã‹ã‚‰ subscription_manifest ã¸" + +#~ msgid "foreman_search_facts to resource_info" +#~ msgstr "foreman_search_facts ã‹ã‚‰ resource_info ã¸" + +#~ msgid "foreman_ptable to partition_table" +#~ msgstr "foreman_ptable ã‹ã‚‰ partition_table ã¸" + +#~ msgid "foreman_model to hardware_model" +#~ msgstr "foreman_model ã‹ã‚‰ hardware_model ã¸" + +#~ msgid "foreman_environment to puppet_environment" +#~ msgstr "foreman_environment ã‹ã‚‰ puppet_environment ã¸" + +#~ msgid "Both ansible-doc and ansible-console's help command will error for modules and plugins whose return documentation cannot be parsed as YAML. All modules and plugins passing ``ansible-test sanity --test yamllint`` will not be affected by this." +#~ msgstr "ansible-doc 㨠ansible-console ã® help コマンドã®ä¸¡æ–¹ãŒã€ãƒªã‚¿ãƒ¼ãƒ³ãƒ‰ã‚ュメント㌠YAML ã¨ã—ã¦è§£æžã§ããªã„モジュールã¨ãƒ—ラグインã«å¯¾ã—ã¦ã‚¨ãƒ©ãƒ¼ã‚’出ã—ã¾ã™ã€‚``ansible-test sanity --test yamllint`` を通éŽã™ã‚‹ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¨ãƒ—ラグインã¯ã€ã“ã®å½±éŸ¿ã‚’å—ã‘ã¾ã›ã‚“。" + +#~ msgid "Collections may declare a list of supported/tested Ansible versions for the collection. A warning is issued if a collection does not support the Ansible version that loads it (can also be configured as silent or a fatal error). Collections that do not declare supported Ansible versions do not issue a warning/error." +#~ msgstr "コレクションã¯ã€ãã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã§ã‚µãƒãƒ¼ãƒˆ/テストã•ã‚Œã¦ã„ã‚‹ Ansible ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒªã‚¹ãƒˆã‚’宣言ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚コレクションãŒã€ãれをèªã¿è¾¼ã‚€ Ansible ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’サãƒãƒ¼ãƒˆã—ã¦ã„ãªã„å ´åˆã¯ã€è¦å‘ŠãŒç™ºè¡Œã•ã‚Œã¾ã™ (サイレントã¾ãŸã¯è‡´å‘½çš„ãªã‚¨ãƒ©ãƒ¼ã¨ã—ã¦è¨å®šã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™)。サãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã‚‹ Ansible ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’宣言ã—ã¦ã„ãªã„コレクションã¯ã€è¦å‘Š/エラーを発行ã—ã¾ã›ã‚“。" + +#~ msgid "Plugin routing allows collections to declare deprecation, redirection targets, and removals for all plugin types." +#~ msgstr "プラグインルーティングã«ã‚ˆã‚Šã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã¯ã™ã¹ã¦ã®ãƒ—ラグインタイプã®éžæŽ¨å¥¨ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚¿ãƒ¼ã‚²ãƒƒãƒˆã€ãŠã‚ˆã³å‰Šé™¤ã‚’宣言ã§ãã¾ã™ã€‚" + +#~ msgid "Plugins that import module_utils and other ansible namespaces that have moved to collections should continue to work unmodified." +#~ msgstr "コレクションã«ç§»å‹•ã—㟠module_utils ãŠã‚ˆã³ãã®ä»–ã® Ansible åå‰ç©ºé–“をインãƒãƒ¼ãƒˆã™ã‚‹ãƒ—ラグインã¯ã€å¤‰æ›´ã›ãšã«å‹•ä½œã—続ã‘ã¾ã™ã€‚" + +#~ msgid "Routing data built into Ansible 2.10 ensures that 2.9 content should work unmodified on 2.10. Formerly included modules and plugins that were moved to collections are still accessible by their original unqualified names, so long as their destination collections are installed." +#~ msgstr "Ansible 2.10 ã«çµ„ã¿è¾¼ã¾ã‚ŒãŸãƒ«ãƒ¼ãƒ†ã‚£ãƒ³ã‚°ãƒ‡ãƒ¼ã‚¿ã«ã‚ˆã‚Šã€2.9 ã®ã‚³ãƒ³ãƒ†ãƒ³ãƒ„㌠2.10 ã§å¤‰æ›´ãªã動作ã™ã‚‹ã“ã¨ãŒä¿è¨¼ã•ã‚Œã¾ã™ã€‚コレクションã«ç§»å‹•ã—ãŸä»¥å‰ã«åŒæ¢±ã•ã‚Œã¦ã„るモジュールやプラグインã¯ã€ç§»å‹•å…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹é™ã‚Šã€å…ƒã®æœªä¿®é£¾åã§ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã™ã€‚" + +#~ msgid "When deprecations are done in code, they to specify a ``collection_name`` so that deprecation warnings can mention which collection - or ansible-base - is deprecating a feature. This affects all ``Display.deprecated()`` or ``AnsibleModule.deprecate()`` or ``Ansible.Basic.Deprecate()`` calls, and ``removed_in_version``/``removed_at_date`` or ``deprecated_aliases`` in module argument specs." +#~ msgstr "コードã§éžæŽ¨å¥¨ã¨ãªã£ãŸå ´åˆã¯ã€éžæŽ¨å¥¨ã®è¦å‘Šã§ã©ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (ã¾ãŸã¯ ansible-base) ãŒæ©Ÿèƒ½ã‚’éžæŽ¨å¥¨ã¨ã—ã¦ã„ã‚‹ã‹ã‚’言åŠã§ãるよã†ã«ã€``collection_name`` を指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€ã™ã¹ã¦ã® ``Display.deprecated()``ã€``AnsibleModule.deprecate()``ã€ã¾ãŸã¯``Ansible.Basic.Deprecate()`` ã®å‘¼ã³å‡ºã—ã€ãŠã‚ˆã³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«å¼•æ•°ä»•æ§˜ã® ``removed_in_version``/``removed_at_date`` ã¾ãŸã¯ ``deprecated_aliases`` ã«å½±éŸ¿ã—ã¾ã™ã€‚" + +#~ msgid "ansible-test now uses a different ``default`` test container for Ansible Collections" +#~ msgstr "ansible-test ãŒã€Ansible Collections ã«ç•°ãªã‚‹ ``default`` テストコンテナーを使用ã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "ec2 module_utils - The ``AWSRetry`` decorator no longer catches ``NotFound`` exceptions by default. ``NotFound`` exceptions need to be explicitly added using ``catch_extra_error_codes``. Some AWS modules may see an increase in transient failures due to AWS''s eventual consistency model." +#~ msgstr "ec2 module_utils - ``AWSRetry`` デコレーターã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ ``NotFound`` ã®ä¾‹å¤–ã‚’ã‚ャッãƒã—ãªããªã‚Šã¾ã—ãŸã€‚``NotFound`` ã®ä¾‹å¤–ã¯ã€``catch_extra_error_codes`` を使用ã—ã¦æ˜Žç¤ºçš„ã«è¿½åŠ ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚一部㮠AWS モジュールã§ã¯ã€AWS ã®æœ€çµ‚çš„ãªä¸€è²«æ€§ãƒ¢ãƒ‡ãƒ«ã«ã‚ˆã‚Šã€ä¸€æ™‚çš„ãªéšœå®³ãŒå¢—åŠ ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "ansible.netcommon" +#~ msgstr "ansible.netcommon" + +#~ msgid "Add libssh connection plugin and refactor network_cli (https://github.com/ansible-collections/ansible.netcommon/pull/30)" +#~ msgstr "libssh æŽ¥ç¶šãƒ—ãƒ©ã‚°ã‚¤ãƒ³ã‚’è¿½åŠ ã—ã€refactor network_cli をリファクタリングã—ã¾ã™ (https://github.com/ansible-collections/ansible.netcommon/pull/30)。" + +#~ msgid "ansible.posix" +#~ msgstr "ansible.posix" + +#~ msgid "Bootstrap Collection (https://github.com/ansible-collections/ansible.posix/pull/1)." +#~ msgstr "ブートストラップコレクション (https://github.com/ansible-collections/ansible.posix/pull/1)" + +#~ msgid "Rewrite requests method for version 1.0 API and improved readability" +#~ msgstr "ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 1.0 ã® API ã«åˆã‚ã›ã¦ requests メソッドを書ãæ›ãˆã€èªã¿ã‚„ã™ã•ã‚’å‘上ã•ã›ã¾ã—ãŸã€‚" + +#~ msgid "meraki_mr_rf_profile - Configure wireless RF profiles." +#~ msgstr "meraki_mr_rf_profile - ワイヤレス RF プãƒãƒ•ã‚¡ã‚¤ãƒ«ã‚’è¨å®šã—ã¾ã™ã€‚" + +#~ msgid "meraki_mr_settings - Configure network settings for wireless." +#~ msgstr "meraki_mr_settings - ワイヤレスã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯è¨å®šã‚’構æˆã—ã¾ã™ã€‚" + +#~ msgid "meraki_ms_l3_interface - New module" +#~ msgstr "meraki_ms_l3_interface - æ–°ã—ã„モジュール" + +#~ msgid "meraki_ms_ospf - Configure OSPF." +#~ msgstr "meraki_ms_ospf - OSPF ã‚’è¨å®šã—ã¾ã™ã€‚" + +#~ msgid "docker_container - the ``network_mode`` option will be set by default to the name of the first network in ``networks`` if at least one network is given and ``networks_cli_compatible`` is ``true`` (will be default from community.general 2.0.0 on). Set to an explicit value to avoid deprecation warnings if you specify networks and set ``networks_cli_compatible`` to ``true``. The current default (not specifying it) is equivalent to the value ``default``." +#~ msgstr "docker_container -``network_mode`` オプションã¯ã€å°‘ãªãã¨ã‚‚ 1 ã¤ã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãŒæŒ‡å®šã•ã‚Œã€``networks_cli_compatible`` ãŒ``true`` ã§ã‚ã‚‹å ´åˆã¯ã€``networks`` ã®æœ€åˆã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã®åå‰ãŒãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§è¨å®šã•ã‚Œã¾ã™ (community.general 2.0.0 以é™ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã«ãªã‚Šã¾ã™)。ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚’指定ã—㦠``networks_cli_compatible`` ã‚’ ``true`` ã«è¨å®šã—ãŸå ´åˆã®éžæŽ¨å¥¨è¦å‘Šã‚’回é¿ã™ã‚‹ãŸã‚ã«ã€æ˜Žç¤ºçš„ãªå€¤ã«è¨å®šã—ã¾ã™ã€‚ç¾åœ¨ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆ (指定ãªã—) ã¯ã€``default`` ã®å€¤ã¨åŒç‰ã§ã™ã€‚" + +#~ msgid "docker_container - the module has a new option, ``container_default_behavior``, whose default value will change from ``compatibility`` to ``no_defaults``. Set to an explicit value to avoid deprecation warnings." +#~ msgstr "docker_container - モジュールã«ã¯æ–°ã—ã„オプション ``container_default_behavior`` ãŒã‚ã‚Šã€ãã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã¯ ``compatibility`` ã‹ã‚‰ ``no_defaults`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ã€‚éžæŽ¨å¥¨ã®è¦å‘Šã‚’回é¿ã™ã‚‹ãŸã‚ã«æ˜Žç¤ºçš„ãªå€¤ã‚’è¨å®šã—ã¾ã™ã€‚" + +#~ msgid "gitlab_user - no longer requires ``name``, ``email`` and ``password`` arguments when ``state=absent``." +#~ msgstr "gitlab_user - ``state=absent`` ã®å ´åˆã« ``name`` 引数ã€``email`` 引数ã€ãŠã‚ˆã³ ``password`` 引数ãŒå¿…è¦ãªããªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "Add changelog management for ansible 2.10 (#112)" +#~ msgstr "Ansible 2.10 ã® changelog 管ç†ã‚’è¿½åŠ (#112)" + +#~ msgid "grafana_datasource ; adding additional_json_data param" +#~ msgstr "grafana_datasource - additional_json_data パラメーターã®è¿½åŠ " + +#~ msgid "Add changelog and fragments and document changelog process (https://github.com/ansible-collections/community.kubernetes/pull/131)." +#~ msgstr "変更ãƒã‚°ãŠã‚ˆã³ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã‚’è¿½åŠ ã—ã€å¤‰æ›´ãƒã‚°ãƒ—ãƒã‚»ã‚¹ã‚’文書化ã—ã¾ã™ (https://github.com/ansible-collections/community.kubernetes/pull/131)。" + +#~ msgid "helm - New module for managing Helm charts (https://github.com/ansible-collections/community.kubernetes/pull/61)." +#~ msgstr "helm - Helm ãƒãƒ£ãƒ¼ãƒˆç®¡ç†ç”¨ã®æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/community.kubernetes/pull/61)。" + +#~ msgid "helm_info - New module for retrieving Helm chart information (https://github.com/ansible-collections/community.kubernetes/pull/61)." +#~ msgstr "helm_info - Helm ãƒãƒ£ãƒ¼ãƒˆæƒ…å ±ã‚’å–å¾—ã™ã‚‹æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/community.kubernetes/pull/61)。" + +#~ msgid "helm_plugin - new module to manage Helm plugins (https://github.com/ansible-collections/community.kubernetes/pull/154)." +#~ msgstr "helm_plugin - Helm プラグインを管ç†ã™ã‚‹æ–°ã—ã„モジュール (https://github.com/ansible-collections/community.kubernetes/pull/154)。" + +#~ msgid "helm_plugin_info - new modules to gather information about Helm plugins (https://github.com/ansible-collections/community.kubernetes/pull/154)." +#~ msgstr "helm_plugin_info - Helm プラグインã«é–¢ã™ã‚‹æƒ…å ±ã‚’åŽé›†ã™ã‚‹æ–°ã—ã„モジュール (https://github.com/ansible-collections/community.kubernetes/pull/154)。" + +#~ msgid "helm_repository - New module for managing Helm repositories (https://github.com/ansible-collections/community.kubernetes/pull/61)." +#~ msgstr "helm_repository - Helm リãƒã‚¸ãƒˆãƒªãƒ¼ã‚’管ç†ã™ã‚‹ãŸã‚ã®æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/community.kubernetes/pull/61)。" + +#~ msgid "k8s - Inventory source migrated from Ansible 2.9 to Kubernetes collection." +#~ msgstr "k8s - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚½ãƒ¼ã‚¹ã€‚" + +#~ msgid "k8s - Lookup plugin migrated from Ansible 2.9 to Kubernetes collection." +#~ msgstr "k8s - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸãƒ—ラグイン。" + +#~ msgid "k8s - Module migrated from Ansible 2.9 to Kubernetes collection." +#~ msgstr "k8s - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€‚" + +#~ msgid "k8s_auth - Module migrated from Ansible 2.9 to Kubernetes collection." +#~ msgstr "k8s_auth - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€‚" + +#~ msgid "k8s_config_resource_name - Filter plugin migrated from Ansible 2.9 to Kubernetes collection." +#~ msgstr "k8s_config_resource_name - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸãƒ—ラグインã«ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã‚’è¨å®šã—ã¾ã™ã€‚" + +#~ msgid "k8s_exec - New module for executing commands on pods via Kubernetes API (https://github.com/ansible-collections/community.kubernetes/pull/14)." +#~ msgstr "k8s_exec - Kubernetes API を使用ã—㦠Pod ã§ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã™ã‚‹æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/community.kubernetes/pull/14)。" + +#~ msgid "k8s_exec - Return rc for the command executed (https://github.com/ansible-collections/community.kubernetes/pull/158)." +#~ msgstr "k8s_exec - 実行ã—ãŸã‚³ãƒžãƒ³ãƒ‰ã® rc ã‚’è¿”ã—ã¾ã™ (https://github.com/ansible-collections/community.kubernetes/pull/158)。" + +#~ msgid "k8s_info - Module migrated from Ansible 2.9 to Kubernetes collection." +#~ msgstr "k8s_info - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€‚" + +#~ msgid "k8s_log - New module for retrieving pod logs (https://github.com/ansible-collections/community.kubernetes/pull/16)." +#~ msgstr "k8s_log - Pod ãƒã‚°ã‚’å–å¾—ã™ã‚‹æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/community.kubernetes/pull/16)。" + +#~ msgid "k8s_scale - Module migrated from Ansible 2.9 to Kubernetes collection." +#~ msgstr "k8s_scale - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€‚" + +#~ msgid "k8s_service - Module migrated from Ansible 2.9 to Kubernetes collection." +#~ msgstr "k8s_service - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€‚" + +#~ msgid "kubectl - Connection plugin migrated from Ansible 2.9 to Kubernetes collection." +#~ msgstr "kubectl - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸæŽ¥ç¶šãƒ—ラグイン。" + +#~ msgid "openshift - Inventory source migrated from Ansible 2.9 to Kubernetes collection." +#~ msgstr "openshift - Ansible 2.9 ã‹ã‚‰ Kubernetes コレクションã«ç§»è¡Œã—ãŸã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚½ãƒ¼ã‚¹ã€‚" + +#~ msgid "community.libvirt" +#~ msgstr "community.libvirt" + +#~ msgid "added generic libvirt inventory plugin" +#~ msgstr "汎用 libvirt インベントリープラグインã®è¿½åŠ " + +#~ msgid "removed libvirt_lxc inventory script" +#~ msgstr "libvirt_lxc インベントリースクリプトを削除" + +#~ msgid "dellemc.os10" +#~ msgstr "dellemc.os10" + +#~ msgid "New role os10_aaa - Facilitates the configuration of Authentication Authorization and Accounting (AAA), TACACS and RADIUS server." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_aaa - èªè¨¼æ‰¿èªãŠã‚ˆã³ã‚¢ã‚«ã‚¦ãƒ³ãƒˆ (AAA)ã€TACACS サーãƒãƒ¼ãŠã‚ˆã³ RADIUS サーãƒãƒ¼ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_acl - Facilitates the configuration of Access Control lists." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_acl - アクセス制御リストã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_bfd - Facilitates the configuration of BFD global attributes." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_bfd - BFD ã‚°ãƒãƒ¼ãƒãƒ«å±žæ€§ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_bgp - Facilitates the configuration of border gateway protocol (BGP) attributes." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_bgp - 境界線ゲートウェイプãƒãƒˆã‚³ãƒ« (BGP) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_copy_config - This role pushes the backup running configuration into a OS10 device." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_copy_config - ã“ã®ãƒãƒ¼ãƒ«ã¯ã€ãƒãƒƒã‚¯ã‚¢ãƒƒãƒ—ã®å®Ÿè¡Œè¨å®šã‚’ OS10 デãƒã‚¤ã‚¹ã«ãƒ—ッシュã—ã¾ã™ã€‚" + +#~ msgid "New role os10_dns - Facilitates the configuration of domain name service (DNS)." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_dns - ドメインãƒãƒ¼ãƒ サービス (DNS) ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_ecmp - Facilitates the configuration of equal cost multi-path (ECMP) for IPv4." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_ecmp - IPv4 用ã®åŒç‰ã®ã‚³ã‚¹ãƒˆãƒžãƒ«ãƒãƒ‘ス (ECMP) ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_fabric_summary Facilitates to get show system information of all the OS10 switches in the fabric." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_fabric_summary - ファブリック内ã®ã™ã¹ã¦ã® OS10 スイッãƒã®ã‚·ã‚¹ãƒ†ãƒ æƒ…å ±ã‚’è¡¨ç¤ºã™ã‚‹ã®ã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_flow_monitor Facilitates the configuration of ACL flow-based monitoring attributes." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_flow_monitor - ACL フãƒãƒ¼ãƒ™ãƒ¼ã‚¹ã®ç›£è¦–属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_image_upgrade Facilitates installation of OS10 software images." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_image_upgrade - OS10 ソフトウェアイメージã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_interface Facilitates the configuration of interface attributes." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_interface - インターフェース属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_lag Facilitates the configuration of link aggregation group (LAG) attributes." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_lag - リンクアグリゲーショングループ (LAG) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_lldp Facilitates the configuration of link layer discovery protocol (LLDP) attributes at global and interface level." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_lldp - ã‚°ãƒãƒ¼ãƒãƒ«ãŠã‚ˆã³ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ãƒ¬ãƒ™ãƒ«ã§ã®ãƒªãƒ³ã‚¯ãƒ¬ã‚¤ãƒ¤ãƒ¼æ¤œå‡ºãƒ—ãƒãƒˆã‚³ãƒ« (LLDP) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_logging Facilitates the configuration of global logging attributes and logging servers." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_logging - ã‚°ãƒãƒ¼ãƒãƒ«ãƒã‚®ãƒ³ã‚°å±žæ€§ãŠã‚ˆã³ãƒã‚®ãƒ³ã‚°ã‚µãƒ¼ãƒãƒ¼ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_network_validation Facilitates validation of wiring connection, BGP neighbors, MTU between neighbors and VLT pair." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_network_validation - é…線接続ã€BGP 近接ã€è¿‘接間 MTUã€VLT ペアã®æ¤œè¨¼ã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_ntp Facilitates the configuration of network time protocol (NTP) attributes." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_ntp - ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚¿ã‚¤ãƒ プãƒãƒˆã‚³ãƒ« (NTP) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_prefix_list Facilitates the configuration of IP prefix-list." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_prefix_list - IP プレフィックスリストã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_qos Facilitates the configuration of quality of service attributes including policy-map and class-map." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_qos - policy-map ãŠã‚ˆã³ class-map ã‚’å«ã‚€ QoS (Quality of Service) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_raguard Facilitates the configuration of IPv6 RA Guard attributes." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_raguard - IPv6 RA Guard 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_route_map Facilitates the configuration of route-map attributes." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_route_map - route-map 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_snmp Facilitates the configuration of global SNMP attributes." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_snmp - ã‚°ãƒãƒ¼ãƒãƒ« SNMP 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_system Facilitates the configuration of hostname and hashing algorithm." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_system - ホストåã¨ãƒãƒƒã‚·ãƒ¥ã‚¢ãƒ«ã‚´ãƒªã‚ºãƒ ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_template The role takes the raw string input from the CLI of OS10 device, and returns a structured text in the form of a Python dictionary." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_template - ã“ã®ãƒãƒ¼ãƒ«ã¯ã€OS10 デãƒã‚¤ã‚¹ã® CLI ã‹ã‚‰ raw æ–‡å—列入力をå–å¾—ã—ã€Python ディクショナリーã®å½¢å¼ã§æ§‹é€ 化ã•ã‚ŒãŸãƒ†ã‚ストを返ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_uplink Facilitates the configuration of uplink attributes like uplink-state group." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_uplink - uplink-state グループã®ã‚ˆã†ãªã‚¢ãƒƒãƒ—リンク属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_users Facilitates the configuration of global system user attributes." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_users - ã‚°ãƒãƒ¼ãƒãƒ«ã‚·ã‚¹ãƒ†ãƒ ユーザー属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_vlan Facilitates the configuration of virtual LAN (VLAN) attributes." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_vlan - 仮想 LAN (VLAN) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_vlt Facilitates the configuration of virtual link trunking (VLT)." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_vlt - 仮想リンクトランク (VLT) ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_vrf Facilitates the configuration of virtual routing and forwarding (VRF)." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_vrf - VRF (Virtual Routing and Forwarding) ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_vrrp Facilitates the configuration of virtual router redundancy protocol (VRRP) attributes." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_vrrp - 仮想ルーター冗長性プãƒãƒˆã‚³ãƒ« (VRRP) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_vxlan Facilitates the configuration of virtual extensible LAN (VXLAN) attributes." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_vxlan - 仮想拡張å¯èƒ½ LAN (VXLAN) 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "New role os10_xstp Facilitates the configuration of xSTP attributes." +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ãƒ« os10_xstp - xSTP 属性ã®è¨å®šã‚’容易ã«ã—ã¾ã™ã€‚" + +#~ msgid "Broke apart bigip_device_auth_radius to implement radius server configuration in bigip_device_auth_server module. Refer to module documentation for usage details" +#~ msgstr "bigip_device_auth_radius を分割ã—ã€radius サーãƒã®è¨å®šã‚’ bigip_device_auth_server モジュールã«å®Ÿè£…ã—ã¾ã—ãŸã€‚使用方法ã®è©³ç´°ã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ‰ã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "Remove redundant parameters in f5_provider to fix disparity between documentation and module parameters" +#~ msgstr "f5_provider ã§å†—é•·ãªãƒ‘ラメーターを削除ã—ã¦ã€ãƒ‰ã‚ュメントã¨ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ‘ラメーターã®ä¸ä¸€è‡´ã‚’ä¿®æ£ã—ã¾ã™ã€‚" + +#~ msgid "gluster.gluster" +#~ msgstr "gluster.gluster" + +#~ msgid "geo_rep - Added the independent module of geo rep with other gluster modules (https://github.com/gluster/gluster-ansible-collection/pull/2)." +#~ msgstr "geo_rep - ä»–ã® gluster モジュールã¨ã€geo rep ã®ç‹¬ç«‹ã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒè¿½åŠ ã•ã‚Œã¾ã—㟠(https://github.com/gluster/gluster-ansible-collection/pull/2)。" + +#~ msgid "ovirt_disk - Add backup (https://github.com/oVirt/ovirt-ansible-collection/pull/57)." +#~ msgstr "ovirt_disk - ãƒãƒƒã‚¯ã‚¢ãƒƒãƒ—è¿½åŠ ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/57)。" + +#~ msgid "ovirt_disk - Support direct upload/download (https://github.com/oVirt/ovirt-ansible-collection/pull/35)." +#~ msgstr "ovirt_disk - 直接アップãƒãƒ¼ãƒ‰/ダウンãƒãƒ¼ãƒ‰ã‚’サãƒãƒ¼ãƒˆã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/35)。" + +#~ msgid "ovirt_host - Add ssh_port (https://github.com/oVirt/ovirt-ansible-collection/pull/60)." +#~ msgstr "ovirt_host - ssh_port ã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/60)。" + +#~ msgid "ovirt_vm_os_info - Creation of module (https://github.com/oVirt/ovirt-ansible-collection/pull/26)." +#~ msgstr "ovirt_vm_os_info - モジュールを作æˆã—ã¾ã™ (https://github.com/oVirt/ovirt-ansible-collection/pull/26)。" + +#~ msgid "purestorage.flasharray" +#~ msgstr "purestorage.flasharray" + +#~ msgid "purefa_console - manage Console Lock setting for the FlashArray" +#~ msgstr "purefa_console - FlashArray ã®ã‚³ãƒ³ã‚½ãƒ¼ãƒ«ãƒãƒƒã‚¯è¨å®šã‚’管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefa_endpoint - manage VMware protocol-endpoints on the FlashArray" +#~ msgstr "purefa_endpoint - FlashArray 㧠VMware プãƒãƒˆã‚³ãƒ«ã‚¨ãƒ³ãƒ‰ãƒã‚¤ãƒ³ãƒˆã‚’管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefa_eula - sign, or resign, FlashArray EULA" +#~ msgstr "purefa_eula - sign ã¾ãŸã¯ resignã€FlashArray EULA" + +#~ msgid "purefa_inventory - get hardware inventory information from a FlashArray" +#~ msgstr "purefa_inventory - FlashArray ã‹ã‚‰ãƒãƒ¼ãƒ‰ã‚¦ã‚§ã‚¢ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼æƒ…å ±ã‚’å–å¾—ã—ã¾ã™ã€‚" + +#~ msgid "purefa_network - manage the physical and virtual network settings on the FlashArray" +#~ msgstr "purefa_network - FlashArray ã§ç‰©ç†ãŠã‚ˆã³ä»®æƒ³ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã®è¨å®šã‚’管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefa_pgsched - manage protection group snapshot and replication schedules on the FlashArray" +#~ msgstr "purefa_pgsched - FlashArray ã§ä¿è·ã‚°ãƒ«ãƒ¼ãƒ—ã®ã‚¹ãƒŠãƒƒãƒ—ショットãŠã‚ˆã³ãƒ¬ãƒ—リケーションスケジュールを管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefa_pod - manage ActiveCluster pods in FlashArrays" +#~ msgstr "purefa_pod - FlashArray 㧠ActiveCluster Pod を管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefa_pod_replica - manage ActiveDR pod replica links in FlashArrays" +#~ msgstr "purefa_pod_replica - FlashArray 㧠ActiveDR Pod レプリカリンクを管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefa_proxy - manage the phonehome HTTPS proxy setting for the FlashArray" +#~ msgstr "purefa_proxy - FlashArray ã® phonehome HTTPS プãƒã‚シーè¨å®šã‚’管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefa_smis - manage SMI-S settings on the FlashArray" +#~ msgstr "purefa_smis - FlashArray 㧠SMI-S è¨å®šã‚’管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefa_subnet - manage network subnets on the FlashArray" +#~ msgstr "purefa_subnet - FlashArray ã§ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚µãƒ–ãƒãƒƒãƒˆã‚’管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefa_timeout - manage the GUI idle timeout on the FlashArray" +#~ msgstr "purefa_timeout - FlashArray 㧠GUI ã®ã‚¢ã‚¤ãƒ‰ãƒ«ã‚¿ã‚¤ãƒ アウトを管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefa_vlan - manage VLAN interfaces on the FlashArray" +#~ msgstr "purefa_vlan - FlashArray 㧠VLAN インターフェースを管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefa_vnc - manage VNC for installed applications on the FlashArray" +#~ msgstr "purefa_vnc - FlashArray ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚ŒãŸã‚¢ãƒ—リケーション㮠VNC を管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefa_volume_tags - manage volume tags on the FlashArray" +#~ msgstr "purefa_volume_tags - FlashArray ã§ãƒœãƒªãƒ¥ãƒ¼ãƒ タグを管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purestorage.flashblade" +#~ msgstr "purestorage.flashblade" + +#~ msgid "purefb_alert - manage alert email settings on a FlashBlade" +#~ msgstr "purefb_alert - FlashBlade ã§ã‚¢ãƒ©ãƒ¼ãƒˆã®ãƒ¡ãƒ¼ãƒ«è¨å®šã‚’管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefb_bladename - manage FlashBlade name" +#~ msgstr "purefb_bladename - FlashBlade åを管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefb_bucket_replica - manage bucket replica links on a FlashBlade" +#~ msgstr "purefb_bucket_replica - FlashBlade ã§ãƒã‚±ãƒƒãƒˆãƒ¬ãƒ—リカリンクを管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefb_connect - manage connections between FlashBlades" +#~ msgstr "purefb_connect - FlashBlades é–“ã®æŽ¥ç¶šã‚’管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefb_dns - manage DNS settings on a FlashBlade" +#~ msgstr "purefb_dns - FlashBlade 㧠DNS è¨å®šã‚’管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefb_fs_replica - manage filesystem replica links on a FlashBlade" +#~ msgstr "purefb_fs_replica - FlashBlade ã§ãƒ•ã‚¡ã‚¤ãƒ«ã‚·ã‚¹ãƒ†ãƒ レプリカリンクを管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefb_inventory - get information about the hardware inventory of a FlashBlade" +#~ msgstr "purefb_inventory - FlashBlade ã®ãƒãƒ¼ãƒ‰ã‚¦ã‚§ã‚¢ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã«é–¢ã™ã‚‹æƒ…å ±ã‚’å–å¾—ã—ã¾ã™ã€‚" + +#~ msgid "purefb_ntp - manage the NTP settings for a FlashBlade" +#~ msgstr "purefb_ntp - FlashBlade ã® NTP è¨å®šã‚’管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefb_phonehome - manage the phone home settings for a FlashBlade" +#~ msgstr "purefb_phonehome - FlashBlade ã®é›»è©±ãƒ›ãƒ¼ãƒ ディレクトリーè¨å®šã‚’管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefb_policy - manage the filesystem snapshot policies for a FlashBlade" +#~ msgstr "purefb_policy - FlashBlade ã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚·ã‚¹ãƒ†ãƒ スナップショットãƒãƒªã‚·ãƒ¼ã‚’管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefb_proxy - manage the phone home HTTP proxy settings for a FlashBlade" +#~ msgstr "purefb_proxy - FlashBlade ã®é›»è©±ãƒ›ãƒ¼ãƒ HTTP プãƒã‚シーè¨å®šã‚’管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefb_remote_cred - manage the Object Store Remote Credentials on a FlashBlade" +#~ msgstr "purefb_remote_cred - FlashBlade ã§ã‚ªãƒ–ジェクトストアã®ãƒªãƒ¢ãƒ¼ãƒˆèªè¨¼æƒ…å ±ã‚’ç®¡ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefb_snmp_agent - modify the FlashBlade SNMP Agent" +#~ msgstr "purefb_snmp_agent - FlashBlade SNMP エージェントを変更ã—ã¾ã™ã€‚" + +#~ msgid "purefb_snmp_mgr - manage SNMP Managers on a FlashBlade" +#~ msgstr "purefb_snmp_mgr - FlashBlade 㧠SNMP Manager を管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefb_target - manage remote S3-capable targets for a FlashBlade" +#~ msgstr "purefb_target - FlashBlade ã®ãƒªãƒ¢ãƒ¼ãƒˆ S3 対応ターゲットを管ç†ã—ã¾ã™ã€‚" + +#~ msgid "purefb_user - manage local ``pureuser`` account password on a FlashBlade" +#~ msgstr "purefb_user - FlashBlade ã§ãƒãƒ¼ã‚«ãƒ«ã® ``pureuser`` アカウントã®ãƒ‘スワードを管ç†ã—ã¾ã™ã€‚" + +#~ msgid "core - remove support for ``check_invalid_arguments`` in ``AnsibleModule``, ``AzureModule`` and ``UTMModule``." +#~ msgstr "core - ``AnsibleModule``ã€``AzureModule``ã€ãŠã‚ˆã³ ``UTMModule`` ã® ``check_invalid_arguments`` ã®ã‚µãƒãƒ¼ãƒˆã‚’削除ã—ã¾ã™ã€‚" + +#~ msgid "module_utils.network.common.utils.ComplexDict has been removed" +#~ msgstr "module_utils.network.common.utils.ComplexDict ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "win_stat - removed the deprecated ``get_md55`` option and ``md5`` return value." +#~ msgstr "win_stat - éžæŽ¨å¥¨ã® ``get_md55`` オプション㨠``md5`` ã®æˆ»ã‚Šå€¤ã‚’削除ã—ã¾ã™ã€‚" + +#~ msgid "community.crypto" +#~ msgstr "community.crypto" + +#~ msgid "The ``letsencrypt`` module has been removed. Use ``acme_certificate`` instead." +#~ msgstr "``letsencrypt`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``acme_certificate`` を使用ã—ã¦ãã ã•ã„。" + +#~ msgid "conjur_variable lookup - has been moved to the ``cyberark.conjur`` collection. A redirection is active, which will be removed in version 2.0.0 (https://github.com/ansible-collections/community.general/pull/570)." +#~ msgstr "conjur_variable ルックアップ - ``cyberark.conjur`` コレクションã«ç§»å‹•ã—ã¾ã—ãŸã€‚リダイレクトã¯ã‚¢ã‚¯ãƒ†ã‚£ãƒ–ã§ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/570)。" + +#~ msgid "core - remove support for ``check_invalid_arguments`` in ``UTMModule``." +#~ msgstr "core - ``UTMModule`` ã® ``check_invalid_arguments`` ã®ã‚µãƒãƒ¼ãƒˆã‚’削除ã—ã¾ã™ã€‚" + +#~ msgid "digital_ocean_* - all DigitalOcean modules have been moved to the ``community.digitalocean`` collection. A redirection is active, which will be removed in version 2.0.0 (https://github.com/ansible-collections/community.general/pull/622)." +#~ msgstr "digital_ocean_* - ã™ã¹ã¦ã® DigitalOcean モジュール㌠``community.digitalocean`` コレクションã«ç§»å‹•ã—ã¾ã—ãŸã€‚リダイレクトã¯ã‚¢ã‚¯ãƒ†ã‚£ãƒ–ã§ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/622)。" + +#~ msgid "infini_* - all infinidat modules have been moved to the ``infinidat.infinibox`` collection. A redirection is active, which will be removed in version 2.0.0 (https://github.com/ansible-collections/community.general/pull/607)." +#~ msgstr "infini_* - ã™ã¹ã¦ã® infinidat モジュール㌠``infinidat.infinibox`` コレクションã«ç§»å‹•ã•ã‚Œã¾ã—ãŸã€‚リダイレクトã¯ã‚¢ã‚¯ãƒ†ã‚£ãƒ–ã§ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/607)。" + +#~ msgid "logicmonitor - the module has been removed in 1.0.0 since it is unmaintained and the API used by the module has been turned off in 2017 (https://github.com/ansible-collections/community.general/issues/539, https://github.com/ansible-collections/community.general/pull/541)." +#~ msgstr "logicmonitor - ã“ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹å¯¾è±¡å¤–ã§ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒä½¿ç”¨ã™ã‚‹ API ㌠2017 å¹´ã«å‰Šé™¤ã•ã‚ŒãŸãŸã‚ã€1.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.general/issues/539ã€https://github.com/ansible-collections/community.general/pull/541)。" + +#~ msgid "logicmonitor_facts - the module has been removed in 1.0.0 since it is unmaintained and the API used by the module has been turned off in 2017 (https://github.com/ansible-collections/community.general/issues/539, https://github.com/ansible-collections/community.general/pull/541)." +#~ msgstr "logicmonitor_facts - ã“ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹å¯¾è±¡å¤–ã§ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒä½¿ç”¨ã™ã‚‹ API ㌠2017 å¹´ã«å‰Šé™¤ã•ã‚ŒãŸãŸã‚ã€1.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.general/issues/539ã€https://github.com/ansible-collections/community.general/pull/541)。" + +#~ msgid "mysql_* - all MySQL modules have been moved to the ``community.mysql`` collection. A redirection is active, which will be removed in version 2.0.0 (https://github.com/ansible-collections/community.general/pull/633)." +#~ msgstr "mysql_* - ã™ã¹ã¦ã® MySQL モジュール㌠``community.mysql`` コレクションã«ç§»å‹•ã—ã¾ã—ãŸã€‚リダイレクトã¯ã‚¢ã‚¯ãƒ†ã‚£ãƒ–ã§ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/633)。" + +#~ msgid "pacman - Removed deprecated ``recurse`` option, use ``extra_args=--recursive`` instead" +#~ msgstr "pacman - éžæŽ¨å¥¨ã® ``recurse`` オプションを削除ã—ã¾ã—ãŸã€‚代ã‚ã‚Šã« ``extra_args=--recursive`` を使用ã—ã¾ã™ã€‚" + +#~ msgid "proxysql_* - all ProxySQL modules have been moved to the ``community.proxysql`` collection. A redirection is active, which will be removed in version 2.0.0 (https://github.com/ansible-collections/community.general/pull/624)." +#~ msgstr "proxysql_* - ã™ã¹ã¦ã® ProxySQL モジュール㌠``community.proxysql`` コレクションã«ç§»å‹•ã•ã‚Œã¾ã—ãŸã€‚リダイレクトã¯ã‚¢ã‚¯ãƒ†ã‚£ãƒ–ã§ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/624)。" + +#~ msgid "onyx - all onyx modules and plugins have been moved to the mellanox.onyx collection. Redirects have been added that will be removed in community.network 2.0.0 (https://github.com/ansible-collections/community.network/pull/83)." +#~ msgstr "onyx - ã™ã¹ã¦ã® onyx モジュールã¨ãƒ—ラグインã¯ã€mellanox.onyx コレクションã«ç§»å‹•ã—ã¾ã—ãŸã€‚community.network 2.0.0 ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒè¿½åŠ ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.network/pull/83)。" + +#~ msgid "vmware_guest_find - Removed deprecated ``datacenter`` option" +#~ msgstr "vmware_guest_find - éžæŽ¨å¥¨ã® ``datacenter`` オプションを削除ã—ã¾ã—ãŸã€‚" + +#~ msgid "vmware_portgroup - removed 'inbound_policy', and 'rolling_order' deprecated options." +#~ msgstr "vmware_portgroup - 「inbound_policyã€ãŠã‚ˆã³ã€Œrolling_orderã€ã®éžæŽ¨å¥¨ã‚ªãƒ—ションを削除ã—ã¾ã—ãŸã€‚" + +#~ msgid "vmware_vmkernel - Removed deprecated ``ip_address`` option; use sub-option ip_address in the network option instead" +#~ msgstr "vms_vmkernel - éžæŽ¨å¥¨ã® ``ip_address`` オプション。代ã‚ã‚Šã« network オプションã«ã‚µãƒ–オプション ip_address を使用ã—ã¦ãã ã•ã„。" + +#~ msgid "vmware_vmkernel - Removed deprecated ``subnet_mask`` option; use sub-option subnet_mask in the network option instead" +#~ msgstr "vmware_vmkernel - éžæŽ¨å¥¨ã® ``subnet_mask`` オプションを削除ã—ã¾ã—ãŸã€‚代ã‚ã‚Šã« network オプションã«ã‚µãƒ–オプション subnet_mask を使用ã—ã¦ãã ã•ã„。" + +#~ msgid "win_disk_image - removed the deprecated return value ``mount_path`` in favor of ``mount_paths``." +#~ msgstr "win_disk_image - éžæŽ¨å¥¨ã®æˆ»ã‚Šå€¤ ``mount_path`` ãŒå‰Šé™¤ã•ã‚Œã€``mount_paths`` ãŒå¤‰æ›´ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "win_psexec - removed the deprecated ``extra_opts`` option." +#~ msgstr "win_psexec - éžæŽ¨å¥¨ã® ``extra_opts`` オプションãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "Remove _bigip_iapplx_package alias" +#~ msgstr "_bigip_iapplx_package エイリアスã®å‰Šé™¤" + +#~ msgid "Remove _bigip_security_address_list alias" +#~ msgstr "_bigip_security_address_list エイリアスã®å‰Šé™¤" + +#~ msgid "Remove _bigip_security_port_list alias" +#~ msgstr "_bigip_security_port_list エイリアスã®å‰Šé™¤" + +#~ msgid "Remove _bigip_traffic_group alias" +#~ msgstr "_bigip_traffic_group エイリアスã®å‰Šé™¤" + +#~ msgid "Remove bigip_appsvcs_extension module" +#~ msgstr "bigip_appsvcs_extension モジュールã®å‰Šé™¤" + +#~ msgid "Remove bigip_asm_policy module" +#~ msgstr "bigip_asm_policy モジュールã®å‰Šé™¤" + +#~ msgid "The vyos.vyos.vyos_static_route module has been deprecated and will be removed in a later release; use vyos.vyos.vyos_static_routes instead." +#~ msgstr "vyos.vyos.vyos_static_route モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚代ã‚ã‚Šã«ã€vyos.vyos.vyos_static_routes を使用ã—ã¾ã™ã€‚" + +#~ msgid "Using the DefaultCallback without the correspodning doc_fragment or copying the documentation." +#~ msgstr "対応ã™ã‚‹ doc_fragment を使用ã›ãšã« DefaultCallback を使用ã€ã¾ãŸã¯ãƒ‰ã‚ュメントã®ã‚³ãƒ”ー" + +#~ msgid "hash_behaviour - Deprecate ``hash_behaviour`` for future removal." +#~ msgstr "hash_behaviour - 今後削除ã•ã‚Œã‚‹ ``hash_behaviour`` ã‚’éžæŽ¨å¥¨ã«ã—ã¾ã™ã€‚" + +#~ msgid "script inventory plugin - The 'cache' option is deprecated and will be removed in 2.12. Its use has been removed from the plugin since it has never had any effect." +#~ msgstr "スクリプトインベントリープラグイン - 「cacheã€ã‚ªãƒ—ションã¯éžæŽ¨å¥¨ã«ãªã‚Šã€2.12 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚何も効果ãŒãªã„ãŸã‚ã€ãã®ä½¿ç”¨ã¯ãƒ—ラグインã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "All AWS Modules - ``aws_access_key``, ``aws_secret_key`` and ``security_token`` will be made mutually exclusive with ``profile`` after 2022-06-01." +#~ msgstr "ã™ã¹ã¦ã® AWS モジュール - ``aws_access_key``ã€``aws_secret_key``ã€ãŠã‚ˆã³ ``security_token`` 㯠2022-06-01 以é™ã« ``profile`` ã¨ç›¸äº’ã«æŽ’ä»–çš„ã«ãªã‚Šã¾ã™ã€‚" + +#~ msgid "cloudformation - The ``template_format`` option had no effect since Ansible 2.3 and will be removed after 2022-06-01" +#~ msgstr "cloudformation - ``template_format`` オプション㯠Ansible 2.3 以é™ã«ã¯å½±éŸ¿ã—ã¾ã›ã‚“ãŒã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "cloudformation - the ``template_format`` option has been deprecated and will be removed in a later release. It has been ignored by the module since Ansible 2.3." +#~ msgstr "cloudformation - ``template_format`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚ã“れ㯠Ansible 2.3 以é™ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚ˆã£ã¦ç„¡è¦–ã•ã‚Œã¦ã„ã¾ã™ã€‚" + +#~ msgid "data_pipeline - The ``version`` option had no effect and will be removed in after 2022-06-01" +#~ msgstr "data_pipeline - ``version`` オプションã¯å½±éŸ¿ã‚’å—ã‘ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "ec2 - in a later release, the ``group`` and ``group_id`` options will become mutually exclusive. Currently ``group_id`` is ignored if you pass both." +#~ msgstr "ec2 - 今後ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€``group`` オプション㨠``group_id`` オプションãŒç›¸äº’ã«æŽ’ä»–çš„ã«ãªã‚Šã¾ã™ã€‚ç¾æ™‚点ã§ã¯ã€ä¸¡æ–¹ã‚’渡ã™ã¨ ``group_id`` ã¯ç„¡è¦–ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "ec2_ami - The ``no_device`` alias ``NoDevice`` has been deprecated and will be removed after 2022-06-01" +#~ msgstr "ec2_ami - ``no_device`` エイリアス ``NoDevice`` ã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "ec2_ami - The ``virtual_name`` alias ``VirtualName`` has been deprecated and will be removed after 2022-06-01" +#~ msgstr "ec2_ami - ``virtual_name`` エイリアス ``VirtualName`` ã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "ec2_eip - The ``wait_timeout`` option had no effect and will be removed after 2022-06-01" +#~ msgstr "ec2_eip - ``wait_timeout`` オプションã¯å½±éŸ¿ã‚’å—ã‘ã¦ãŠã‚‰ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "ec2_key - The ``wait_timeout`` option had no effect and will be removed after 2022-06-01" +#~ msgstr "ec2_key - ``wait_timeout`` オプションã¯å½±éŸ¿ã‚’å—ã‘ã¦ãŠã‚‰ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "ec2_key - The ``wait`` option had no effect and will be removed after 2022-06-01" +#~ msgstr "ec2_key - ``wait`` オプションã¯å½±éŸ¿ã‚’å—ã‘ã¦ãŠã‚‰ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "ec2_key - the ``wait_timeout`` option has been deprecated and will be removed in a later release. It has had no effect since Ansible 2.5." +#~ msgstr "ec2_key - ``wait_timeout`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚Ansible 2.5 以é™ã«ã¯å¤‰æ›´ã¯ã‚ã‚Šã¾ã›ã‚“。" + +#~ msgid "ec2_key - the ``wait`` option has been deprecated and will be removed in a later release. It has had no effect since Ansible 2.5." +#~ msgstr "ec2_key - ``wait`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚Ansible 2.5 以é™ã«ã¯å¤‰æ›´ã¯ã‚ã‚Šã¾ã›ã‚“。" + +#~ msgid "ec2_lc - The ``associate_public_ip_address`` option had no effect and will be removed after 2022-06-01" +#~ msgstr "ec2_lc - ``associate_public_ip_address`` オプションã¯å½±éŸ¿ã‚’å—ã‘ã¦ãŠã‚‰ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "ec2_tag - deprecate the ``list`` option in favor of ec2_tag_info" +#~ msgstr "ec2_tag - ``list`` オプションãŒéžæŽ¨å¥¨ã«ãªã‚Šã€ec2_tag_info ãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "ec2_tag - support for ``list`` as a state has been deprecated and will be removed in a later release. The ``ec2_tag_info`` can be used to fetch the tags on an EC2 resource." +#~ msgstr "ec2_tag - 状態ã¨ã—ã¦ã® ``list`` ã®ã‚µãƒãƒ¼ãƒˆã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚``ec2_tag_info`` を使用ã™ã‚‹ã¨ã€EC2 リソースã§ã‚¿ã‚°ã‚’å–å¾—ã§ãã¾ã™ã€‚" + +#~ msgid "win_domain_computer - Deprecated the undocumented ``log_path`` option. This option will be removed in a major release after ``2022-07-01``." +#~ msgstr "win_domain_ computers - ドã‚ュメント化ã•ã‚Œã¦ã„ãªã„ ``log_path`` オプションãŒéžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚ã“ã®ã‚ªãƒ—ション㯠``2022-07-01`` 後ã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "win_domain_controller - the ``log_path`` option has been deprecated and will be removed in a later release. This was undocumented and only related to debugging information for module development." +#~ msgstr "win_domain_controller - ``log_path`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯æ–‡æ›¸åŒ–ã•ã‚Œã¦ãŠã‚‰ãšã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«é–‹ç™ºã®ãƒ‡ãƒãƒƒã‚°æƒ…å ±ã«ã®ã¿é–¢é€£ã—ã¦ã„ã¾ã™ã€‚" + +#~ msgid "win_package - the ``ensure`` alias for the ``state`` option has been deprecated and will be removed in a later release. Please use ``state`` instead of ``ensure``." +#~ msgstr "win_package - ``state`` オプション㮠``ensure`` エイリアスã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚``ensure`` ã®ä»£ã‚ã‚Šã« ``state`` を使用ã—ã¦ãã ã•ã„。" + +#~ msgid "win_package - the ``productid`` alias for the ``product_id`` option has been deprecated and will be removed in a later release. Please use ``product_id`` instead of ``productid``." +#~ msgstr "win_package - ``product_id`` オプション㮠``productid`` エイリアスã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚``productid`` ã®ä»£ã‚ã‚Šã« ``product_id`` を使用ã—ã¦ãã ã•ã„。" + +#~ msgid "win_package - the ``username`` and ``password`` options has been deprecated and will be removed in a later release. The same functionality can be done by using ``become: yes`` and ``become_flags: logon_type=new_credentials logon_flags=netcredentials_only`` on the task." +#~ msgstr "win_package - ``username`` オプションãŠã‚ˆã³ ``password`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚åŒæ§˜ã«ã€ã‚¿ã‚¹ã‚¯ã® ``become: yes`` ãŠã‚ˆã³ ``become_flags: logon_type=new_credentials logon_flags=netcredentials_only`` を使用ã—ã¦å®Ÿè¡Œã§ãã¾ã™ã€‚" + +#~ msgid "win_regedit - Deprecated using forward slashes as a path separator, use backslashes to avoid ambiguity between a forward slash in the key name or a forward slash as a path separator. This feature will be removed in a major release after ``2021-07-01``." +#~ msgstr "win_regedit - スラッシュをパス区切り文å—ã¨ã—ã¦ä½¿ç”¨ã—ã€ãƒãƒƒã‚¯ã‚¹ãƒ©ãƒƒã‚·ãƒ¥ã‚’使用ã—ã¦ã€ã‚ーåã®ã‚¹ãƒ©ãƒƒã‚·ãƒ¥ã¨ãƒ‘ス区切りã®ã‚¹ãƒ©ãƒƒã‚·ãƒ¥ã®æ›–昧ã•ã‚’回é¿ã—ã¾ã™ã€‚ã“ã®æ©Ÿèƒ½ã¯ã€``2021-07-01`` ã®å¾Œã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "data_pipeline - The ``version`` option had no effect and will be removed after 2022-06-01" +#~ msgstr "data_pipeline - ``version`` オプションã¯å½±éŸ¿ã‚’å—ã‘ã¦ãŠã‚‰ãšã€2022-06-01 以é™å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "data_pipeline - the ``version`` option has been deprecated and will be removed in a later release. It has always been ignored by the module." +#~ msgstr "data_pipeline - ``version`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚常ã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚ˆã£ã¦ç„¡è¦–ã•ã‚Œã¦ã„ã¾ã™ã€‚" + +#~ msgid "ec2_eip - the ``wait_timeout`` option has been deprecated and will be removed in a later release. It has had no effect since Ansible 2.3." +#~ msgstr "ec2_eip - ``wait_timeout`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚Ansible 2.3 以é™ã¯å¤‰æ›´ã•ã‚Œã¾ã›ã‚“。" + +#~ msgid "ec2_lc - the ``associate_public_ip_address`` option has been deprecated and will be removed after a later release. It has always been ignored by the module." +#~ msgstr "ec2_lc - ``associate_public_ip_address`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚常ã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚ˆã£ã¦ç„¡è¦–ã•ã‚Œã¦ã„ã¾ã™ã€‚" + +#~ msgid "elb_network_lb - The current default value of the ``state`` option has been deprecated and will change from absent to present after 2022-06-01" +#~ msgstr "elb_network_lb - ``state`` オプションã®ç¾åœ¨ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€2022-06-01 以é™ã« absent ã‹ã‚‰ present ã«å¤‰æ›´ã™ã‚‹äºˆå®šã§ã™ã€‚" + +#~ msgid "elb_network_lb - in a later release, the default behaviour for the ``state`` option will change from ``absent`` to ``present``. To maintain the existing behavior explicitly set state to ``absent``." +#~ msgstr "elb_network_lb - 今後ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€``state`` オプションã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå‹•ä½œãŒ ``absent`` ã‹ã‚‰ ``present`` ã«å¤‰æ›´ãªã‚Šã¾ã™ã€‚æ—¢å˜ã®å‹•ä½œã‚’ç¶æŒã™ã‚‹ã«ã¯ã€çŠ¶æ…‹ã‚’明示的㫠``absent`` ã«è¨å®šã—ã¾ã™ã€‚" + +#~ msgid "iam_managed_policy - The ``fail_on_delete`` option had no effect and will be removed after 2022-06-01" +#~ msgstr "iam_managed_policy - ``fail_on_delete`` オプションã¯å½±éŸ¿ã‚’å—ã‘ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "iam_managed_policy - the ``fail_on_delete`` option has been deprecated and will be removed after a later release. It has always been ignored by the module." +#~ msgstr "iam_managed_policy - ``fail_on_delete`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚常ã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚ˆã£ã¦ç„¡è¦–ã•ã‚Œã¦ã„ã¾ã™ã€‚" + +#~ msgid "iam_policy - The ``policy_document`` will be removed after 2022-06-01. To maintain the existing behavior use the ``policy_json`` option and read the file with the ``lookup`` plugin." +#~ msgstr "iam_policy - ``policy_document`` 㯠2022-06-01 以é™å‰Šé™¤ã•ã‚Œã¾ã™ã€‚æ—¢å˜ã®å‹•ä½œã‚’ç¶æŒã™ã‚‹ã«ã¯ã€``policy_json`` オプションを使用ã—㦠``lookup`` プラグインã§ãƒ•ã‚¡ã‚¤ãƒ«ã‚’èªã¿å–ã‚Šã¾ã™ã€‚" + +#~ msgid "iam_policy - The default value of ``skip_duplicates`` will change after 2022-06-01 from ``true`` to ``false``." +#~ msgstr "iam_policy -``skip_duplicates`` ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã¯ã€2022-06-01 以é™ã€``true`` ã‹ã‚‰``false`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ã€‚" + +#~ msgid "iam_policy - in a later release, the default value for the ``skip_duplicates`` option will change from ``true`` to ``false``. To maintain the existing behavior explicitly set it to ``true``." +#~ msgstr "iam_policy - 今後ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€``skip_duplicates`` オプションã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ãŒ ``true`` ã‹ã‚‰``false`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ã€‚æ—¢å˜ã®å‹•ä½œã‚’ç¶æŒã™ã‚‹ã«ã¯ã€æ˜Žç¤ºçš„ã« ``true`` ã«è¨å®šã—ã¦ãã ã•ã„。" + +#~ msgid "iam_policy - the ``policy_document`` option has been deprecated and will be removed after a later release. To maintain the existing behavior use the ``policy_json`` option and read the file with the ``lookup`` plugin." +#~ msgstr "iam_policy - ``policy_document`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€å¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚æ—¢å˜ã®å‹•ä½œã‚’ç¶æŒã™ã‚‹ã«ã¯ã€``policy_json`` オプションを使用ã—ã€``lookup`` プラグインã§ãƒ•ã‚¡ã‚¤ãƒ«ã‚’èªã¿è¾¼ã‚“ã§ãã ã•ã„。" + +#~ msgid "iam_role - The default value of the purge_policies has been deprecated and will change from true to false after 2022-06-01" +#~ msgstr "iam_role - purge_policies ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€2022-06-01 以é™ã¯ true ã‹ã‚‰ false ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ã€‚" + +#~ msgid "iam_role - in a later release, the ``purge_policies`` option (also know as ``purge_policy``) default value will change from ``true`` to ``false``" +#~ msgstr "iam_role - 今後ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€``purge_policies`` オプション (``purge_policy`` ã¨ã‚‚呼ã°ã‚Œã‚‹) ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ãŒ ``true`` ã‹ã‚‰ ``false`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ã€‚" + +#~ msgid "s3_lifecycle - The ``requester_pays`` option had no effect and will be removed after 2022-06-01" +#~ msgstr "s3_lifecycle - ``requester_pays`` オプションã¯å½±éŸ¿ã‚’å—ã‘ã¦ãŠã‚‰ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "s3_lifecycle - the ``requester_pays`` option has been deprecated and will be removed after a later release. It has always been ignored by the module." +#~ msgstr "s3_lifecycle - ``requester_pays`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚モジュールã§ã¯å¸¸ã«ç„¡è¦–ã•ã‚Œã¦ã„ã¾ã™ã€‚" + +#~ msgid "s3_sync - The ``retries`` option had no effect and will be removed after 2022-06-01" +#~ msgstr "s3_sync - ``retries`` オプションã¯å½±éŸ¿ã‚’å—ã‘ã¦ãŠã‚‰ãšã€2022-06-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "s3_sync - the ``retries`` option has been deprecated and will be removed after 2022-06-01. It has always been ignored by the module." +#~ msgstr "s3_sync - ``retries`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€2022-06-01 以é™ã¯å‰Šé™¤ã•ã‚Œã¾ã™ã€‚モジュールã§ã¯å¸¸ã«ç„¡è¦–ã•ã‚Œã¦ã„ã¾ã™ã€‚" + +#~ msgid "openssl_csr - all values for the ``version`` option except ``1`` are deprecated. The value 1 denotes the current only standardized CSR version." +#~ msgstr "openssl_csr - ``version`` オプション㮠``1`` 以外ã®å€¤ã¯éžæŽ¨å¥¨ã§ã™ã€‚値 1 ã¯ã€ç¾åœ¨å”¯ä¸€æ¨™æº–化ã•ã‚Œã¦ã„ã‚‹ CSR ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’示ã—ã¾ã™ã€‚" + +#~ msgid "The ldap_attr module has been deprecated and will be removed in a later release; use ldap_attrs instead." +#~ msgstr "ldap_attr モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ldap_attrs を使用ã—ã¦ãã ã•ã„。" + +#~ msgid "airbrake_deployment - Add deprecation notice for ``token`` parameter and v2 api deploys. This feature will be removed in community.general 3.0.0." +#~ msgstr "airbrake_deployment - ``token`` パラメーター㨠v2 api ã®ãƒ‡ãƒ—ãƒã‚¤ã«é–¢ã™ã‚‹éžæŽ¨å¥¨ã®å‘ŠçŸ¥ã‚’è¿½åŠ ã—ã¾ã™ã€‚ã“ã®æ©Ÿèƒ½ã¯ community.general 3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "clc_aa_policy - The ``wait`` option had no effect and will be removed in community.general 3.0.0." +#~ msgstr "clc_aa_policy - ``wait`` オプションã¯å½±éŸ¿ã‚’å—ã‘ãšã€community.general 3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "clc_aa_policy - the ``wait`` parameter will be removed. It has always been ignored by the module." +#~ msgstr "clc_aa_policy - ``wait`` パラメーターã¯å‰Šé™¤ã•ã‚Œã¾ã™ã€‚常ã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚ˆã‚Šç„¡è¦–ã•ã‚Œã¦ã„ã¾ã™ã€‚" + +#~ msgid "docker_container - the ``trust_image_content`` option is now deprecated and will be removed in community.general 3.0.0. It has never been used by the module." +#~ msgstr "docker_container - ``trust_image_content`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€community.general 3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚モジュールã§ä½¿ç”¨ã•ã‚Œã‚‹ã“ã¨ã¯ã‚ã‚Šã¾ã›ã‚“。" + +#~ msgid "docker_container - the ``trust_image_content`` option will be removed. It has always been ignored by the module." +#~ msgstr "docker_container - ``trust_image_content`` オプションã¯å‰Šé™¤ã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¾ã§ã‚‚モジュールã¯ã“ã®ã‚ªãƒ—ションを無視ã—ã¦ã„ã¾ã—ãŸã€‚" + +#~ msgid "docker_container - the default of ``container_default_behavior`` will change from ``compatibility`` to ``no_defaults`` in community.general 3.0.0. Set the option to an explicit value to avoid a deprecation warning." +#~ msgstr "docker_container - ``container_default_behavior`` ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ãŒ community.general 3.0.0 㧠``compatibility`` ã‹ã‚‰ ``no_defaults`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ã€‚éžæŽ¨å¥¨ã®è¦å‘Šã‚’防ããŸã‚ã«ã€ã‚ªãƒ—ションを明示的ã«è¨å®šã—ã¾ã™ã€‚" + +#~ msgid "docker_container - the default value for ``network_mode`` will change in community.general 3.0.0, provided at least one network is specified and ``networks_cli_compatible`` is ``true``. See porting guide, module documentation or deprecation warning for more details." +#~ msgstr "docker_container - community.general 3.0.0 ã§ã¯ã€å°‘ãªãã¨ã‚‚ 1 ã¤ã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãŒæŒ‡å®šã•ã‚Œã€``networks_cli_compatible`` ㌠``true`` ã§ã‚ã‚‹å ´åˆã¯ã€``network_mode`` ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ãŒå¤‰æ›´ã—ã¾ã™ã€‚詳細ã¯ç§»æ¤ã‚¬ã‚¤ãƒ‰ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ‰ã‚ュメントã€ã¾ãŸã¯éžæŽ¨å¥¨ã®è¦å‘Šã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "docker_stack - Return values ``out`` and ``err`` have been deprecated and will be removed in community.general 3.0.0. Use ``stdout`` and ``stderr`` instead." +#~ msgstr "docker_stack - 戻り値㮠``out`` ã¨``err`` ã¯éžæŽ¨å¥¨ã§ã‚ã‚Šã€community.general 3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ``stdout`` ã¨``stderr`` を使用ã—ã¦ãã ã•ã„。" + +#~ msgid "docker_stack - the return values ``err`` and ``out`` have been deprecated. Use ``stdout`` and ``stderr`` from now on instead." +#~ msgstr "docker_stack - ``err`` ã¨``out`` ã®æˆ»ã‚Šå€¤ã¯éžæŽ¨å¥¨ã¨ãªã‚Šã¾ã—ãŸã€‚今後㯠``stdout`` 㨠``stderr`` を使用ã—ã¦ãã ã•ã„。" + +#~ msgid "helm - Put ``helm`` module to deprecated. New implementation is available in community.kubernetes collection." +#~ msgstr "helm - ``helm`` モジュールをéžæŽ¨å¥¨ã«ã—ã¾ã—ãŸã€‚æ–°ã—ã„実装㯠community.kubernetes コレクションã§å…¬é–‹ã•ã‚Œã¦ã„ã¾ã™ã€‚" + +#~ msgid "redfish_config - Deprecate ``bios_attribute_name`` and ``bios_attribute_value`` in favor of new `bios_attributes`` option." +#~ msgstr "redfish_config - ``bios_attribute_name`` 㨠``bios_attribute_value`` ã‚’éžæŽ¨å¥¨ã¨ã—ã€æ–°ã—ã„ `bios_attributes`` オプションを採用ã—ã¾ã™ã€‚" + +#~ msgid "redfish_config - the ``bios_attribute_name`` and ``bios_attribute_value`` options will be removed. To maintain the existing behavior use the ``bios_attributes`` option instead." +#~ msgstr "redfish_config - ``bios_attribute_name`` オプションãŠã‚ˆã³ ``bios_attribute_value`` オプションを削除ã—ã¾ã™ã€‚æ—¢å˜ã®å‹•ä½œã‚’ç¶æŒã™ã‚‹ã«ã¯ã€ä»£ã‚ã‚Šã« ``bios_attributes`` オプションを使用ã—ã¾ã™ã€‚" + +#~ msgid "redfish_config and redfish_command - the behavior to select the first System, Manager, or Chassis resource to modify when multiple are present will be removed. Use the new ``resource_id`` option to specify target resource to modify." +#~ msgstr "redfish_config ãŠã‚ˆã³ redfish_command - 複数ã®ãƒªã‚½ãƒ¼ã‚¹ãŒå˜åœ¨ã™ã‚‹å ´åˆã«ä¿®æ£ã™ã‚‹æœ€åˆã® System リソースã€Manager リソースã€ã¾ãŸã¯ Chassis リソースをé¸æŠžã™ã‚‹å‹•ä½œãŒå‰Šé™¤ã•ã‚Œã¾ã™ã€‚æ–°ã—ã„ ``resource_id`` オプションを使用ã—ã¦ã€å¤‰æ›´ã™ã‚‹å¯¾è±¡ã®ãƒªã‚½ãƒ¼ã‚¹ã‚’指定ã—ã¾ã™ã€‚" + +#~ msgid "redfish_config, redfish_command - Behavior to modify the first System, Mananger, or Chassis resource when multiple are present is deprecated. Use the new ``resource_id`` option to specify target resource to modify." +#~ msgstr "redfish_configã€redfish_command - 複数ã®ãƒªã‚½ãƒ¼ã‚¹ãŒå˜åœ¨ã™ã‚‹å ´åˆã€æœ€åˆã® Systemã€Manangerã€ã¾ãŸã¯ Chassis リソースを修æ£ã™ã‚‹å‹•ä½œã¯éžæŽ¨å¥¨ã§ã™ã€‚æ–°ã—ã„ ``resource_id`` オプションを使用ã—ã¦ã€å¤‰æ›´ã™ã‚‹å¯¾è±¡ã®ãƒªã‚½ãƒ¼ã‚¹ã‚’指定ã—ã¦ãã ã•ã„。" + +#~ msgid "xbps - the ``force`` option never had any effect. It is now deprecated, and will be removed in 3.0.0 (https://github.com/ansible-collections/community.general/pull/568)." +#~ msgstr "xbps - ``force`` オプションã«ã¯ä½•ã‚‚効果ãŒã‚ã‚Šã¾ã›ã‚“。ç¾åœ¨éžæŽ¨å¥¨ã«ãªã‚Šã€3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/568)。" + +#~ msgid "The vmware_dns_config module has been deprecated and will be removed in a later release; use vmware_host_dns instead." +#~ msgstr "vmware_dns_config モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ä»Šå¾Œã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚代ã‚ã‚Šã« vmware_host_dns を使用ã—ã¦ãã ã•ã„。" + +#~ msgid "vca - vca_fw, vca_nat, vca_app are deprecated since these modules rely on deprecated part of Pyvcloud library." +#~ msgstr "vca - vca_fw モジュールã€vca_nat モジュールã€vca_app モジュールã¯ã€Pyvcloud ライブラリーã®éžæŽ¨å¥¨ã®éƒ¨åˆ†ã«ä¾å˜ã—ã¦ã„ã‚‹ãŸã‚éžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "vmware_dns_config - Deprecate in favor of new module vmware_host_dns." +#~ msgstr "vmc_dns_config - éžæŽ¨å¥¨ã«ãªã‚Šã€æ–°ã—ã„モジュール vmware_host_dns ãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "vmware_guest - deprecate specifying CDROM configuration as a dict, instead use a list." +#~ msgstr "vmware_guest - CDROM è¨å®šã‚’ dict ã¨ã—ã¦æŒ‡å®šã™ã‚‹ã“ã¨ã‚’éžæŽ¨å¥¨ã¨ã—ã€ä»£ã‚ã‚Šã«ãƒªã‚¹ãƒˆã‚’使用ã—ã¾ã™ã€‚" + +#~ msgid "vmware_tag_info - in a later release, the module will not return ``tag_facts`` since it does not return multiple tags with the same name and different category id. To maintain the existing behavior use ``tag_info`` which is a list of tag metadata." +#~ msgstr "vmware_tag_info - 今後ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€åŒã˜åå‰ã§ç•°ãªã‚‹ã‚«ãƒ†ã‚´ãƒªãƒ¼ ID ã‚’æŒã¤è¤‡æ•°ã®ã‚¿ã‚°ã‚’è¿”ã•ãªã„ãŸã‚ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ ``tag_facts`` ã‚’è¿”ã—ã¾ã›ã‚“。既å˜ã®å‹•ä½œã‚’ç¶æŒã™ã‚‹ã«ã¯ã€ã‚¿ã‚°ã®ãƒ¡ã‚¿ãƒ‡ãƒ¼ã‚¿ã®ãƒªã‚¹ãƒˆã§ã‚ã‚‹ ``tag_info`` を使用ã—ã¦ãã ã•ã„。" + +#~ msgid "zabbix_proxy (module) - deprecates ``interface`` sub-options ``type`` and ``main`` when proxy type is set to passive via ``status=passive``. Make sure these suboptions are removed from your playbook as they were never supported by Zabbix in the first place." +#~ msgstr "zabbix_proxy (モジュール) - ``status=passive`` ã§ãƒ—ãƒã‚シー㌠passive ã«è¨å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€``interface`` ã®ã‚µãƒ–オプション ``type`` 㨠``main`` ã‚’éžæŽ¨å¥¨ã¨ã—ã¾ã™ã€‚ã“れらã®ã‚µãƒ–オプションã¯ãã‚‚ãã‚‚ Zabbix ã§ã¯ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ãªã„ãŸã‚ã€å¿…ãš Playbook ã‹ã‚‰å‰Šé™¤ã—ã¦ãã ã•ã„。" + +#~ msgid "Deprecated bigip_appsvcs_extension module" +#~ msgstr "éžæŽ¨å¥¨ã® bigip_appsvcs_extension モジュール" + +#~ msgid "Deprecated bigip_device_facts module name" +#~ msgstr "éžæŽ¨å¥¨ã® bigip_device_facts モジュールå" + +#~ msgid "Deprecated bigiq_device_facts module name" +#~ msgstr "éžæŽ¨å¥¨ã® bigiq_device_facts モジュールå" + +#~ msgid "Ansible 3 is based on Ansible-Base 2.10, which is the same major release as Ansible 2.10. Therefore, there is no section on ansible-base in this porting guide. If you are upgrading from Ansible 2.9, please first consult the Ansible 2.10 porting guide before continuing with the Ansible 3 porting guide." +#~ msgstr "Ansible 3 ã¯ã€Ansible 2.10 ã¨åŒã˜ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã§ã‚ã‚‹ Ansible-Base 2.10 をベースã«ã—ã¦ã„ã¾ã™ã€‚ãã®ãŸã‚ã€ã“ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰ã«ã¯ã€ansible-base ã«é–¢ã™ã‚‹ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã¯ã‚ã‚Šã¾ã›ã‚“。Ansible 2.9 ã‹ã‚‰ã‚¢ãƒƒãƒ—グレードã™ã‚‹å ´åˆã¯ã€ã¾ãš Ansible 2.10 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰ã‚’å‚ç…§ã—ã¦ã‹ã‚‰ã€Ansible 3 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰ã«é€²ã‚“ã§ãã ã•ã„。" + +#~ msgid "We suggest you read this page along with the `Ansible 3 Changelog <https://github.com/ansible-community/ansible-build-data/blob/main/3/CHANGELOG-v3.rst>`_ to understand what updates you may need to make." +#~ msgstr "å¿…è¦ãªæ›´æ–°ã«ã¤ã„ã¦ç†è§£ã™ã‚‹ã«ã¯ã€ã“ã®ãƒšãƒ¼ã‚¸ã¨ä½µã›ã¦ã€Œ`Ansible 3 Changelog <https://github.com/ansible-community/ansible-build-data/blob/main/3/CHANGELOG-v3.rst>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "Porting Guide for v3.4.0" +#~ msgstr "v3.4.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" + +#~ msgid "dellemc.openmanage" +#~ msgstr "dellemc.openmanage" + +#~ msgid "idrac_user - Issue(192043) 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." +#~ msgstr "idrac_user - Issue(192043)モジュール㯠``unable to perform the import or export operation because there are pending attribute changes or a configuration job is in progress`` メッセージã§ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚ジョブãŒå®Œäº†ã™ã‚‹ã¾ã§å¾…æ©Ÿã—ã€ã‚¿ã‚¹ã‚¯ã‚’å†åº¦å®Ÿè¡Œã—ã¾ã™ã€‚" + +#~ msgid "ome_configuration_compliance_info - Issue(195592) Module may error out with the message ``unable to process the request because an error occurred``. If the issue persists, report it to the system administrator." +#~ msgstr "ome_configuration_compliance_info - Issue(195592) モジュール㯠``unable to process the request because an error occurred`` メッセージã§ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚å•é¡ŒãŒè§£æ±ºã—ãªã„å ´åˆã¯ã€ã‚·ã‚¹ãƒ†ãƒ 管ç†è€…ã«å ±å‘Šã—ã¦ãã ã•ã„。" + +#~ msgid "ome_smart_fabric - Issue(185322) Only three design types are supported by OpenManage Enterprise Modular but the module successfully creates a fabric when the design type is not supported." +#~ msgstr "ome_smart_fabric - Issue(185322)㯠OpenManage Enterprise Modular ã§ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã‚‹ 3 ã¤ã®è¨è¨ˆã‚¿ã‚¤ãƒ—ã®ã¿ã§ã™ãŒã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯è¨è¨ˆã‚¿ã‚¤ãƒ—ãŒã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ãªã„ã¨ã€ãƒ•ã‚¡ãƒ–リックãŒæ£å¸¸ã«ä½œæˆã•ã‚Œã¾ã™ã€‚" + +#~ msgid "ome_smart_fabric_uplink - Issue(186024) ome_smart_fabric_uplink module does not allow the creation of multiple uplinks of the same name even though this is supported by OpenManage Enterprise Modular. If an uplink is created using the same name as an existing uplink, the existing uplink is modified." +#~ msgstr "ome_smart_fabric_uplink - Issue(186024)ome_smart_fabric_uplink モジュールã§ã¯ã€OpenManage Enterprise Modular ã§ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã¦ã‚‚ã€åŒã˜åå‰ã®è¤‡æ•°ã®ã‚¢ãƒƒãƒ—リンクã®ä½œæˆã¯ã§ãã¾ã›ã‚“。アップリンクãŒæ—¢å˜ã®ã‚¢ãƒƒãƒ—リンクã¨åŒã˜åå‰ã‚’使用ã—ã¦ä½œæˆã•ã‚Œã‚‹ã¨ã€æ—¢å˜ã®ã‚¢ãƒƒãƒ—ãŒå¤‰æ›´ã—ã¾ã™ã€‚" + +#~ msgid "ansible-test - Tests run with the ``centos6`` and ``default`` test containers now use a PyPI proxy container to access PyPI when Python 2.6 is used. This allows tests running under Python 2.6 to continue functioning even though PyPI is discontinuing support for non-SNI capable clients." +#~ msgstr "ansible-test - ``centos6`` ãŠã‚ˆã³ ``default`` テストコンテナーã§å®Ÿè¡Œã•ã‚Œã‚‹ãƒ†ã‚¹ãƒˆã§ã¯ã€Python 2.6 ã®ä½¿ç”¨æ™‚ã« PyPI プãƒã‚シーコンテナーを使用ã—㦠PyPI ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãるよã†ã«ãªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã«ã‚ˆã‚Šã€Python 2.6 ã§å®Ÿè¡Œã•ã‚Œã‚‹ãƒ†ã‚¹ãƒˆã¯ã€PyPI 以外ã®ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã®ã‚µãƒãƒ¼ãƒˆãŒã‚ã‚‹å ´åˆã§ã‚‚引ã続ã機能ã—ã¾ã™ã€‚" + +#~ msgid "community.postgresql" +#~ msgstr "community.postgresql" + +#~ msgid "postgresql_query - the default value of the ``as_single_query`` option will be changed to ``yes`` in community.postgresql 2.0.0 (https://github.com/ansible-collections/community.postgresql/issues/85)." +#~ msgstr "postgresql_query - ``as_single_query`` オプションã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ãŒ community.postgresql 2.0.0 㧠``yes`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ (https://github.com/ansible-collections/community.postgresql/issues/85)。" + +#~ msgid "netapp.ontap" +#~ msgstr "netapp.ontap" + +#~ msgid "na_ontap_autosupport - Added REST support to the module." +#~ msgstr "na_ontap_autosupport - モジュール㫠REST サãƒãƒ¼ãƒˆã‚’è¿½åŠ ã€‚" + +#~ msgid "ec2_vpc_endpoint_info - the ``query`` option has been deprecated and will be removed after 2022-12-01 (https://github.com/ansible-collections/community.aws/pull/346). The ec2_vpc_endpoint_info now defaults to listing information about endpoints. The ability to search for information about available services has been moved to the dedicated module ``ec2_vpc_endpoint_service_info``." +#~ msgstr "ec2_vpc_endpoint_info - ``query`` オプションã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€2022-12-01 以é™ã«å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.aws/pull/346）。ec2_vpc_endpoint_info ã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã‚¨ãƒ³ãƒ‰ãƒã‚¤ãƒ³ãƒˆã«é–¢ã™ã‚‹æƒ…å ±ã‚’ä¸€è¦§è¡¨ç¤ºã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚利用å¯èƒ½ãªã‚µãƒ¼ãƒ“スã«é–¢ã™ã‚‹æƒ…å ±ã®æ¤œç´¢æ©Ÿèƒ½ãŒã€å°‚用ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``ec2_vpc_endpoint_service_info`` ã«ç§»å‹•ã—ã¾ã—ãŸã€‚" + +#~ msgid "docker_* modules and plugins, except ``docker_swarm`` connection plugin and ``docker_compose`` and ``docker_stack*` modules - the current default ``localhost`` for ``tls_hostname`` is deprecated. In community.docker 2.0.0 it will be computed from ``docker_host`` instead (https://github.com/ansible-collections/community.docker/pull/134)." +#~ msgstr "docker_* モジュールãŠã‚ˆã³ãƒ—ラグイン（``docker_swarm`` 接続プラグインã€``docker_compose`` モジュールã€ãŠã‚ˆã³ '`docker_stack*` モジュールを除ã）ã¯éžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚``tls_hostname`` ã®ç¾åœ¨ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆ ``localhost`` ã¯éžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚community.docker 2.0.0 ã§ã¯ã€ä»£ã‚ã‚Šã« ``docker_host`` ã‹ã‚‰è¨ˆç®—ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.docker/pull/134）。" + +#~ msgid "Porting Guide for v3.3.0" +#~ msgstr "v3.3.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" + +#~ msgid "community.mysql" +#~ msgstr "community.mysql" + +#~ msgid "mysql_user - the ``REQUIRESSL`` is an alias for the ``ssl`` key in the ``tls_requires`` option in ``community.mysql`` 2.0.0 and support will be dropped altogether in ``community.mysql`` 3.0.0 (https://github.com/ansible-collections/community.mysql/issues/121)." +#~ msgstr "``REQUIRESSL`` ã¯ã€``community.mysql`` 2.0.0 ã® ``tls_requires`` オプションã«ã‚ã‚‹ ``ssl`` ã‚ーã®ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã§ã™ã€‚サãƒãƒ¼ãƒˆã¯ ``community.mysql`` 3.0.0 ã§ã™ã¹ã¦å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.mysql/issues/121）。" + +#~ msgid "vmware_vmkernel_ip_config - deprecate in favor of vmware_vmkernel (https://github.com/ansible-collections/community.vmware/pull/667)." +#~ msgstr "vmware_vmkernel_ip_config - vmware_vmkernel ãŒæŽ¡ç”¨ã•ã‚Œã‚‹ï¼ˆéžæŽ¨å¥¨ï¼‰ï¼ˆhttps://github.com/ansible-collections/community.kubernetes/pull/16）" + +#~ msgid "Support for Python versions earlier than 3.5 is being deprecated" +#~ msgstr "3.5 よりもå‰ã® Python ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ã‚µãƒãƒ¼ãƒˆãŒéžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "Porting Guide for v3.2.0" +#~ msgstr "v3.2.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" + +#~ msgid "docker_swarm - if ``join_token`` is specified, a returned join token with the same value will be replaced by ``VALUE_SPECIFIED_IN_NO_LOG_PARAMETER``. Make sure that you do not blindly use the join tokens from the return value of this module when the module is invoked with ``join_token`` specified! This breaking change appears in a minor release since it is necessary to fix a security issue (https://github.com/ansible-collections/community.docker/pull/103)." +#~ msgstr "docker_swarm - ``join_token`` ãŒæŒ‡å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã€è¿”ã•ã‚Œã‚‹çµåˆãƒˆãƒ¼ã‚¯ãƒ³ãŒ ``VALUE_SPECIFIED_IN_NO_LOG_PARAMETER`` ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒ ``join_token`` ã§å‘¼ã³å‡ºã•ã‚Œã‚‹ã¨ã€ã“ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®æˆ»ã‚Šå€¤ã‹ã‚‰çµåˆãƒˆãƒ¼ã‚¯ãƒ³ã‚’使用ã—ãªã„よã†ã«ã—ã¾ã™ã€‚ã“ã®é‡å¤§ãªå¤‰æ›´ã¯ã€ã‚»ã‚ュリティーã®å•é¡Œã‚’ä¿®æ£ã™ã‚‹ãŸã‚ã«å¿…è¦ãªãŸã‚ã€ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ã«å¤‰æ›´ã«ãªã‚Šã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.docker/pull/103）。" + +#~ msgid "acme module_utils - the ``acme`` module_utils (``ansible_collections.community.crypto.plugins.module_utils.acme``) is deprecated and will be removed in community.crypto 2.0.0. Use the new Python modules in the ``acme`` package instead (``ansible_collections.community.crypto.plugins.module_utils.acme.xxx``) (https://github.com/ansible-collections/community.crypto/pull/184)." +#~ msgstr "acme module_utils - ``acme`` module_utils（``ansible_collections.community.crypto.plugins.module_utils.acme``）ã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€community.crypto 2.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« ``acme`` パッケージã§æ–°ã—ã„ Python モジュールを使用ã—ã¦ãã ã•ã„（``ansible_collections.community.crypto.plugins.module_utils.acme.xxx``)（https://github.com/ansible-collections/community.crypto/pull/184）。" + +#~ msgid "Porting Guide for v3.1.0" +#~ msgstr "v3.1.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" + +#~ msgid "introduce \"skip_version_check\" parameter in grafana_teams and grafana_folder modules (#147)" +#~ msgstr "grafana_teams モジュールãŠã‚ˆã³ grafana_folder モジュールã«ã€Œskip_version_checkã€ãƒ‘ラメーターãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸ(#147)" + +#~ msgid "mysql_replication - the mode options values ``getslave``, ``startslave``, ``stopslave``, ``resetslave``, ``resetslaveall` and the master_use_gtid option ``slave_pos`` are deprecated (see the alternative values) and will be removed in ``community.mysql`` 3.0.0 (https://github.com/ansible-collections/community.mysql/pull/97)." +#~ msgstr "mysql_replication - モードオプションã®å€¤ ``getslave``ã€``startslave``ã€``stopslave``ã€``resetslave``ã€`resetslaveall`ã€ãŠã‚ˆã³ master_use_gtid オプション ``slave_pos`` ã¯éžæŽ¨å¥¨ã¨ãªã‚Šï¼ˆåˆ¥ã®å€¤ã‚’å‚照）ã€``community.mysql`` 3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆåˆ¥ã®å€¤ã‚’å‚照）（https://github.com/ansible-collections/community.mysql/pull/97)）。" + +#~ msgid "mysql_replication - the word ``SLAVE`` in messages returned by the module will be changed to ``REPLICA`` in ``community.mysql`` 2.0.0 (https://github.com/ansible-collections/community.mysql/issues/98)." +#~ msgstr "mysql_replication - モジュールã«ã‚ˆã£ã¦è¿”ã•ã‚ŒãŸãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã® ``SLAVE`` ã¨ã„ã†å˜èªžã¯ ``community.mysql`` 2.0.0 ã§ã¯ ``REPLICA`` ã«å¤‰æ›´ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.mysql/issues/98）。" + +#~ msgid "Removed TMOS v11 support for bigip_gtm_pool and bigip_gtm_wide_ip modules" +#~ msgstr "bigip_gtm_pool ãŠã‚ˆã³ bigip_gtm_wide_ip モジュール㮠TMOS v11 サãƒãƒ¼ãƒˆã‚’削除" + +#~ msgid "Removed quorum and monitor_type parameters in bigip_node module. See porting guides section at https://clouddocs.f5.com/products/orchestration/ansible/devel/usage/porting-guides.html" +#~ msgstr "bigip_node モジュール㧠quorum ãŠã‚ˆã³ monitor_type パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚移æ¤ã‚¬ã‚¤ãƒ‰ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ï¼ˆhttps://clouddocs.f5.com/products/orchestration/ansible/devel/usage/porting-guides.html）をå‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "Removed syslog_settings and pool_settings parameters in bigip_log_destination moduke. See porting guides section at https://clouddocs.f5.com/products/orchestration/ansible/devel/usage/porting-guides.html" +#~ msgstr "bigip_log_destination モジュール㧠syslog_settings パラメーターãŠã‚ˆã³ pool_settings パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚移æ¤ã‚¬ã‚¤ãƒ‰ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ï¼ˆhttps://clouddocs.f5.com/products/orchestration/ansible/devel/usage/porting-guides.html）をå‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "cloudscale_ch.cloud" +#~ msgstr "cloudscale_ch.cloud" + +#~ msgid "The aliases ``server_uuids`` and ``server_uuid`` of the servers parameter in the volume module will be removed in version 3.0.0." +#~ msgstr "ボリュームモジュール㮠server パラメーターã®ã‚¨ã‚¤ãƒªã‚¢ã‚¹ ``server_uuids`` ãŠã‚ˆã³ ``server_uuid`` ã¯ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 3.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "ec2_eip - formally deprecate the ``instance_id`` alias for ``device_id`` (https://github.com/ansible-collections/community.aws/pull/349)." +#~ msgstr "ec2_eip - ``device_id`` ã® ``instance_id`` エイリアスをæ£å¼ã«éžæŽ¨å¥¨åŒ–（https://github.com/ansible-collections/community.aws/pull/349）。" + +#~ msgid "ec2_vpc_endpoint - deprecate the policy_file option and recommend using policy with a lookup (https://github.com/ansible-collections/community.aws/pull/366)." +#~ msgstr "ec2_vpc_endpoint - policy_file オプションをéžæŽ¨å¥¨ã«ã—ã€ãƒ«ãƒƒã‚¯ã‚¢ãƒƒãƒ—ã§ã®ãƒãƒªã‚·ãƒ¼ã®ä½¿ç”¨ã‚’推奨ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.aws/pull/366）" + +#~ msgid "acme_account_info - when ``retrieve_orders=url_list``, ``orders`` will no longer be returned in community.crypto 2.0.0. Use ``order_uris`` instead (https://github.com/ansible-collections/community.crypto/pull/178)." +#~ msgstr "acme_account_info - ``retrieve_orders=url_list`` ã®å ´åˆã€``orders`` 㯠community.crypto 2.0.0 ã§è¿”ã•ã‚Œãªããªã‚Šã¾ã™ã€‚代ã‚ã‚Šã« ``order_uris`` を使用ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.crypto/pull/178）" + +#~ msgid "apt_rpm - deprecated invalid parameter alias ``update-cache``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." +#~ msgstr "apt_rpm - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-cache`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" + +#~ msgid "composer - deprecated invalid parameter aliases ``working-dir``, ``global-command``, ``prefer-source``, ``prefer-dist``, ``no-dev``, ``no-scripts``, ``no-plugins``, ``optimize-autoloader``, ``classmap-authoritative``, ``apcu-autoloader``, ``ignore-platform-reqs``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." +#~ msgstr "composer - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``working-dir``ã€``global-command``ã€``prefer-source``ã€``prefer-dist``ã€``no-dev``ã€``no-scripts``ã€``no-plugins``ã€``optimize-autoloader``ã€``classmap-authoritative``ã€``apcu-autoloader``ã€``ignore-platform-reqs`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927。" + +#~ msgid "github_deploy_key - deprecated invalid parameter alias ``2fa_token``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." +#~ msgstr "github_deploy_key - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``2fa_token`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）" + +#~ msgid "grove - the option ``message`` will be removed in community.general 4.0.0. Use the new option ``message_content`` instead (https://github.com/ansible-collections/community.general/pull/1929)." +#~ msgstr "grove - オプション ``message`` 㯠community.general 4.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã«ã€æ–°ã—ã„オプション ``message_content`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1929）。" + +#~ msgid "homebrew - deprecated invalid parameter alias ``update-brew``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." +#~ msgstr "homebrew - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-brew`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）" + +#~ msgid "homebrew_cask - deprecated invalid parameter alias ``update-brew``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." +#~ msgstr "homebrew_cask - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-brew`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" + +#~ msgid "opkg - deprecated invalid parameter alias ``update-cache``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." +#~ msgstr "opkg - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-cache`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" + +#~ msgid "pacman - deprecated invalid parameter alias ``update-cache``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." +#~ msgstr "pacman - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-cache`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" + +#~ msgid "puppet - deprecated undocumented parameter ``show_diff``, will be removed in 7.0.0. (https://github.com/ansible-collections/community.general/pull/1927)." +#~ msgstr "puppet - ドã‚ュメント化ã•ã‚Œã¦ã„ãªã„éžæŽ¨å¥¨ã®ãƒ‘ラメーター ``show_diff`` ㌠7.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" + +#~ msgid "runit - unused parameter ``dist`` marked for deprecation (https://github.com/ansible-collections/community.general/pull/1830)." +#~ msgstr "runit - 未使用ã®ãƒ‘ラメーター ``dist`` ã¯éžæŽ¨å¥¨ã¨ç¤ºã•ã‚Œã¦ã„ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1830）。" + +#~ msgid "slackpkg - deprecated invalid parameter alias ``update-cache``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." +#~ msgstr "slackpkg - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-cache`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" + +#~ msgid "urmpi - deprecated invalid parameter aliases ``update-cache`` and ``no-recommends``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." +#~ msgstr "urmpi - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-cache`` ãŠã‚ˆã³ ``no-recommends`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" + +#~ msgid "xbps - deprecated invalid parameter alias ``update-cache``, will be removed in 5.0.0 (https://github.com/ansible-collections/community.general/pull/1927)." +#~ msgstr "xbps - éžæŽ¨å¥¨ã®ç„¡åŠ¹ãªãƒ‘ラメーターエイリアス ``update-cache`` ㌠5.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1927）。" + +#~ msgid "xfconf - returning output as facts is deprecated, this will be removed in community.general 4.0.0. Please register the task output in a variable and use it instead. You can already switch to the new behavior now by using the new ``disable_facts`` option (https://github.com/ansible-collections/community.general/pull/1747)." +#~ msgstr "xfconf - 出力をファクトã¨ã—ã¦è¿”ã™ã®ã¯éžæŽ¨å¥¨ã§ã™ã€‚ã“れ㯠community.general 4.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚タスクã®å‡ºåŠ›ã‚’変数ã«ç™»éŒ²ã—ã¦ä»£ã‚ã‚Šã«ä½¿ç”¨ã—ã¦ãã ã•ã„。新ã—ã„``disable_facts`` オプション使用ã™ã‚‹ã¨æ–°ã—ã„挙動ã«åˆ‡ã‚Šæ›¿ãˆã‚‹ã“ã¨ãŒã§ãã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1747。" + +#~ msgid "Porting Guide for v3.0.0" +#~ msgstr "v3.0.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" + +#~ msgid "Issue 1(186024): ome_smart_fabric_uplink module does not allow the creation of multiple uplinks of the same name even though this is supported by OpenManage Enterprise Modular. If an uplink is created using the same name as an existing uplink, the existing uplink is modified." +#~ msgstr "Issue 1(186024): ome_smart_fabric_uplink モジュールã§ã¯ã€OpenManage Enterprise Modular ã§ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã¦ã‚‚ã€åŒã˜åå‰ã®è¤‡æ•°ã®ã‚¢ãƒƒãƒ—リンクã®ä½œæˆã¯ã§ãã¾ã›ã‚“。アップリンクãŒæ—¢å˜ã®ã‚¢ãƒƒãƒ—リンクã¨åŒã˜åå‰ã‚’使用ã—ã¦ä½œæˆã•ã‚Œã‚‹ã¨ã€æ—¢å˜ã®ã‚¢ãƒƒãƒ—ãŒå¤‰æ›´ã—ã¾ã™ã€‚" + +#~ msgid "Issue 2(187956): If an invalid job_id is provided, idrac_lifecycle_controller_job_status_info returns an error message. This error message does not contain information about the exact issue with the invalid job_id." +#~ msgstr "Issue 2(187956): 無効ãªjob_idãŒæä¾›ã•ã‚ŒãŸå ´åˆã€idrac_lifecycle_controller_job_status_infoã¯ã‚¨ãƒ©ãƒ¼ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã‚’è¿”ã—ã¾ã™ã€‚ã“ã®ã‚¨ãƒ©ãƒ¼ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã«ã¯ã€ç„¡åŠ¹ãªjob_idã«é–¢ã™ã‚‹æ£ç¢ºãªå•é¡Œã«ã¤ã„ã¦ã®æƒ…å ±ãŒå«ã¾ã‚Œã¦ã„ã¾ã›ã‚“。" + +#~ msgid "Issue 3(188267): While updating the iDRAC firmware, the idrac_firmware module completes execution before the firmware update job is completed. An incorrect message is displayed in the task output as 'DRAC WSMAN endpoint returned HTTP code '400' Reason 'Bad Request''. This issue may occur if the target iDRAC firmware version is less than 3.30.30.30" +#~ msgstr "Issue 3(188267): iDRACファームウェアã®æ›´æ–°ä¸ã«ã€idrac_firmwareモジュールã¯ã€ãƒ•ã‚¡ãƒ¼ãƒ ウェア更新ジョブãŒå®Œäº†ã™ã‚‹å‰ã«å®Ÿè¡Œã‚’完了ã—ã¾ã™ã€‚タスク出力ã«èª¤ã£ãŸãƒ¡ãƒƒã‚»ãƒ¼ã‚¸'DRAC WSMAN endpoint returned HTTP code '400' Reason 'Bad Request''ãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚ã“ã®å•é¡Œã¯ã€ã‚¿ãƒ¼ã‚²ãƒƒãƒˆiDRACファームウェアãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒ3.30.30.30未満ã®å ´åˆã«ç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™" + +#~ msgid "ansible.utils" +#~ msgstr "ansible.utils" + +#~ msgid "If added custom sub plugins in your collection move from old location `plugins/<sub-plugin-name>` to the new location `plugins/sub_plugins/<sub-plugin-name>` and update the imports as required" +#~ msgstr "コレクションã«ã‚«ã‚¹ã‚¿ãƒ ã‚µãƒ–ãƒ—ãƒ©ã‚°ã‚¤ãƒ³ã‚’è¿½åŠ ã—ãŸå ´åˆã€ä»¥å‰ã®å ´æ‰€ `plugins/<sub-plugin-name>` ã‹ã‚‰æ–°ã—ã„å ´æ‰€ `plugins/sub_plugins/<sub-plugin-name>` ã«ç§»å‹•ã—ã€å¿…è¦ã«å¿œã˜ã¦ã‚¤ãƒ³ãƒãƒ¼ãƒˆã‚’æ›´æ–°ã—ã¾ã™ã€‚" + +#~ msgid "Move sub plugins cli_parsers, fact_diff and validate to `plugins/sub_plugins` folder" +#~ msgstr "サブプラグイン cli_parsersã€fact_diffã€ãŠã‚ˆã³ validate ã‚’ `plugins/sub_plugins` ディレクトリーã«ç§»å‹•ã—ã¾ã™ã€‚" + +#~ msgid "The `cli_parsers` sub plugins folder name is changed to `cli_parse` to have consistent naming convention, that is all the cli_parse subplugins will now be in `plugins/sub_plugins/cli_parse` folder" +#~ msgstr "`cli_parsers` サブプラグインã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼åãŒã€ä¸€è²«æ€§ã®ã‚る命åè¦å‰‡ã‚’æŒã¤ã‚ˆã†ã« `cli_parse` ã«å¤‰æ›´ã«ãªã‚Šã€cli_parse サブプラグインã¯ã™ã¹ã¦ `plugins/sub_plugins/cli_parse` ディレクトリーã«ç½®ã‹ã‚Œã¾ã™ã€‚" + +#~ msgid "floating_ip - ``name`` is required for assigning a new floating IP." +#~ msgstr "floating_ip - æ–°ã—ã„ Floating IP アドレスã®å‰²ã‚Šå½“ã¦ã«ã¯ ``name`` ãŒå¿…è¦ã§ã™ã€‚" + +#~ msgid "If you use Ansible 2.9 and the Google cloud plugins or modules from this collection, community.general 2.0.0 results in errors when trying to use the Google cloud content by FQCN, like ``community.general.gce_img``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.google.gce_img`` for the previous example) and to make sure that you have ``community.google`` installed." +#~ msgstr "Ansible 2.9 ã¨ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® Google Cloud プラグインã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 2.0.0 ã§ã¯ã€``community.general.gce_img`` ã®ã‚ˆã†ã« FQCN 㧠Google Cloud コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (å‰ã®ä¾‹ã§ã¯ ``community.google.gce_img``) を使用ã™ã‚‹ãŸã‚ã« Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã—ã€``community.google`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã‹ã©ã†ã‹ã‚’確èªã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install the ``community.google`` or ``google.cloud`` collections if you are using any of the Google cloud plugins or modules. While ansible-base 2.10 or newer can use the redirects that community.general 2.0.0 adds, the collection they point to (such as community.google) must be installed for them to work." +#~ msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ãŸå ´åˆã€Google cloud プラグインã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.google`` コレクションã¾ãŸã¯ ``google.cloud`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.google ãªã©) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" + +#~ msgid "If you use Ansible 2.9 and the Kubevirt plugins or modules from this collection, community.general 2.0.0 results in errors when trying to use the Kubevirt content by FQCN, like ``community.general.kubevirt_vm``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.kubevirt.kubevirt_vm`` for the previous example) and to make sure that you have ``community.kubevirt`` installed." +#~ msgstr "Ansible 2.9 ã¨ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® Kubevirt プラグインã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 2.0.0 ã§ã¯ã€``community.general.kubevirt_vm`` ã®ã‚ˆã†ãª FQCN ã«ã‚ˆã‚‹ Kubevirt コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN を使用ã™ã‚‹ãŸã‚ã« Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (å‰è¿°ã®ä¾‹ã§ã¯ ``community.kubevirt.kubevirt_vm``)。ã¾ãŸã€``community.kubevirt`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。" + +#~ msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install the ``community.kubevirt`` collection if you are using any of the Kubevirt plugins or modules. While ansible-base 2.10 or newer can use the redirects that community.general 2.0.0 adds, the collection they point to (such as community.google) must be installed for them to work." +#~ msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€Kubevirt プラグインã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.kubevirt`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.google ãªã©) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" + +#~ msgid "If you use Ansible 2.9 and the ``docker`` plugins or modules from this collections, community.general 2.0.0 results in errors when trying to use the docker content by FQCN, like ``community.general.docker_container``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.docker.docker_container`` for the previous example) and to make sure that you have ``community.docker`` installed." +#~ msgstr "Ansible 2.9 ã¨ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``docker`` プラグインやモジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 2.0.0 ã§ã¯ã€``community.general.docker_container`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ docker コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (å‰ã®ä¾‹ã§ã¯ ``community.docker.docker_container``) を使用ã—ã€``community.docker`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install ``community.docker`` if you are using any of the ``docker`` plugins or modules. While ansible-base 2.10 or newer can use the redirects that community.general 2.0.0 adds, the collection they point to (community.docker) must be installed for them to work." +#~ msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ãŸå ´åˆã€``docker`` プラグインã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.docker`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.docker) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" + +#~ msgid "If you use Ansible 2.9 and the ``hashi_vault`` lookup plugin from this collections, community.general 2.0.0 results in errors when trying to use the Hashi Vault content by FQCN, like ``community.general.hashi_vault``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your inventories, variable files, playbooks and roles manually to use the new FQCN (``community.hashi_vault.hashi_vault``) and to make sure that you have ``community.hashi_vault`` installed." +#~ msgstr "Ansible 2.9 ã¨ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``hashi_vault`` lookup プラグインやモジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 2.0.0 ã§ã¯ã€``community.general.hashi_vault`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ Hashi Vault コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (``community.hashi_vault.hashi_vault``) を使用ã—ã€``community.hashi_vault`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã€å¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«ã€Playbookã€ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install ``community.hashi_vault`` if you are using the ``hashi_vault`` plugin. While ansible-base 2.10 or newer can use the redirects that community.general 2.0.0 adds, the collection they point to (community.hashi_vault) must be installed for them to work." +#~ msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€``hashi_vault`` プラグインを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.hashi_vault`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.hashi_vault) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" + +#~ msgid "If you use Ansible 2.9 and the ``hetzner`` modules from this collections, community.general 2.0.0 results in errors when trying to use the hetzner content by FQCN, like ``community.general.hetzner_firewall``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.hrobot.firewall`` for the previous example) and to make sure that you have ``community.hrobot`` installed." +#~ msgstr "Ansible 2.9 ã¨ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``hetzner`` プラグインやモジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 2.0.0 ã§ã¯ã€``community.general.hetzner_firewall`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ hetzner コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (å‰ã®ä¾‹ã§ã¯ ``community.hrobot.firewall``) を使用ã—ã€``community.hrobot`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install ``community.hrobot`` if you are using any of the ``hetzner`` modules. While ansible-base 2.10 or newer can use the redirects that community.general 2.0.0 adds, the collection they point to (community.hrobot) must be installed for them to work." +#~ msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ãŸå ´åˆã€``hetzner`` モジュールを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.hrobot`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.hrobot) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" + +#~ msgid "If you use Ansible 2.9 and the ``oc`` connection plugin from this collections, community.general 2.0.0 results in errors when trying to use the oc content by FQCN, like ``community.general.oc``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your inventories, variable files, playbooks and roles manually to use the new FQCN (``community.okd.oc``) and to make sure that you have ``community.okd`` installed." +#~ msgstr "Ansible 2.9 ã¨ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``oc`` connection プラグインやモジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 2.0.0 ã§ã¯ã€``community.general.oc`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ oc コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (``community.okd.oc``) を使用ã—ã€``community.okd`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã€å¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install ``community.okd`` if you are using the ``oc`` plugin. While ansible-base 2.10 or newer can use the redirects that community.general 2.0.0 adds, the collection they point to (community.okd) must be installed for them to work." +#~ msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€``oc`` プラグインを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.okd`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.okd) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" + +#~ msgid "If you use Ansible 2.9 and the ``postgresql`` modules from this collections, community.general 2.0.0 results in errors when trying to use the postgresql content by FQCN, like ``community.general.postgresql_info``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.postgresql.postgresql_info`` for the previous example) and to make sure that you have ``community.postgresql`` installed." +#~ msgstr "Ansible 2.9 ã¨ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``postgresql`` プラグインやモジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 2.0.0 ã§ã¯ã€``community.general.postgresql_info`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ postgresql コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (å‰ã®ä¾‹ã§ã¯ ``community.postgresql.postgresql_info``) を使用ã—ã€``community.postgresql`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install ``community.postgresql`` if you are using any of the ``postgresql`` modules. While ansible-base 2.10 or newer can use the redirects that community.general 2.0.0 adds, the collection they point to (community.postgresql) must be installed for them to work." +#~ msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€``postgresql`` モジュールを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.postgresql`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.postgresql) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" + +#~ msgid "The Google cloud inventory script ``gce.py`` has been migrated to the ``community.google`` collection. Install the ``community.google`` collection in order to continue using it." +#~ msgstr "Google クラウドインベントリースクリプト ``gce.py`` ã‚’ ``community.google`` コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚使用を継続ã™ã‚‹ã«ã¯ã€``community.google`` コレクションをインストールã—ã¦ãã ã•ã„。" + +#~ msgid "archive - remove path folder itself when ``remove`` parameter is true (https://github.com/ansible-collections/community.general/issues/1041)." +#~ msgstr "archive - ``remove`` パラメーター㌠true ã®å ´åˆã«ãƒ‘スフォルダー自体を削除ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/issues/1041）。" + +#~ msgid "passwordstore lookup plugin - now parsing a password store entry as YAML if possible, skipping the first line (which by convention only contains the password and nothing else). If it cannot be parsed as YAML, the old ``key: value`` parser will be used to process the entry. Can break backwards compatibility if YAML formatted code was parsed in a non-YAML interpreted way, e.g. ``foo: [bar, baz]`` will become a list with two elements in the new version, but a string ``'[bar, baz]'`` in the old (https://github.com/ansible-collections/community.general/issues/1673)." +#~ msgstr "passwordstore lookup プラグイン - パスワードストアã®ã‚¨ãƒ³ãƒˆãƒªãƒ¼ã‚’å¯èƒ½ãªé™ã‚Š YAML ã¨ã—ã¦è§£æžã™ã‚‹ã‚ˆã†ã«ãªã‚Šã€æœ€åˆã®è¡Œ (慣例ã§ã¯ãƒ‘スワードã®ã¿ã‚’å«ã¿ã€ä»–ã«ã¯ä½•ã‚‚ãªã„) をスã‚ップã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚YAML ã¨ã—ã¦è§£æžã§ããªã„å ´åˆã¯ã€å¤ã„ ``key: value`` パーサーãŒã‚¨ãƒ³ãƒˆãƒªãƒ¼ã®å‡¦ç†ã«ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚YAML å½¢å¼ã®ã‚³ãƒ¼ãƒ‰ãŒ YAML ã§ã¯ãªã„解釈方法ã§è§£æžã•ã‚ŒãŸå ´åˆã¯ã€ä¸‹ä½äº’æ›æ€§ã‚’失ã†å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€``foo: [bar, baz]`` ã¯æ–°ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã¯ 2 ã¤ã®è¦ç´ ã‚’æŒã¤ãƒªã‚¹ãƒˆã«ãªã‚Šã¾ã™ãŒã€æ—§ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã¯æ–‡å—列 ``'[bar, baz]'`` ã«ãªã‚Šã¾ã™ (https://github.com/ansible-collections/community.general/issues/1673)。" + +#~ msgid "proxmox_kvm - recognize ``force=yes`` in conjunction with ``state=absent`` to forcibly remove a running VM (https://github.com/ansible-collections/community.general/pull/849)." +#~ msgstr "proxmox_kvm - ``force=yes`` ã‚’ ``state=absent`` ã¨ä½µç”¨ã—ã¦ã€å®Ÿè¡Œä¸ã®ä»®æƒ³ãƒžã‚·ãƒ³ã‚’強制的ã«å‰Šé™¤ã—ã¾ã™ (https://github.com/ansible-collections/community.general/pull/849)。" + +#~ msgid "If you use Ansible 2.9 and the FortiOS modules from this collection, community.network 2.0.0 results in errors when trying to use the FortiOS content by FQCN, like ``community.network.fmgr_device``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.fortios.fmgr_device`` for the previous example) and to make sure that you have ``community.fortios`` installed." +#~ msgstr "ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® Ansible 2.9 㨠FortiOS モジュールを使用ã™ã‚‹å ´åˆã¯ã€community.network 2.0.0 を使用ã™ã‚‹ã¨ã€FQCN 㧠``community.network.fmgr_device`` ã®ã‚ˆã†ãª FortiOS コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã€ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã—ã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN を使用ã—ã€``community.fortios`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã®ã‚’確èªã™ã‚‹ã«ã¯ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (å‰ã®ä¾‹ã® ``community.fortios.fmgr_device``)。" + +#~ msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.network manually, you need to make sure to also install ``community.fortios`` if you are using any of the FortiOS modules. While ansible-base 2.10 or newer can use the redirects that community.network 2.0.0 adds, the collection they point to (community.fortios) must be installed for them to work." +#~ msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.network をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ãŸå ´åˆã€FortiOS モジュールを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.fortios`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.network 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.fortios) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" + +#~ msgid "If you use Ansible 2.9 and the ``cp_publish`` module from this collection, community.network 2.0.0 results in errors when trying to use the module by FQCN, i.e. ``community.network.cp_publish``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``check_point.mgmt.cp_mgmt_publish``) and to make sure that you have ``check_point.mgmt`` installed. If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.network manually, you need to make sure to also install ``check_point.mgmt`` if you are using the ``cp_publish`` module. While ansible-base 2.10 or newer can use the redirects that community.network 2.0.0 adds, the collection they point to (check_point.mgmt) must be installed for them to work." +#~ msgstr "Ansible 2.9 ã¨ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``cp_publish`` モジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.network 2.0.0 ã§ã¯ã€FQCN ã§ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã—ã¾ã™ (``community.network.cp_publish``)。Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (``check_point.mgmt.cp_mgmt_publish``) を使用ã—ã€``check_point.mgmt`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€community.network を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ« (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€``cp_publish`` モジュールを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``check_point.mgmt`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ community.network 2.0.0 ãŒè¿½åŠ ã™ã‚‹ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (check_point.mgmt) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" + +#~ msgid "If you use Ansible 2.9 and the ``fortimanager`` httpapi plugin from this collection, community.network 2.0.0 results in errors when trying to use it by FQCN (``community.network.fortimanager``). Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCN ``fortinet.fortimanager.fortimanager`` and to make sure that you have ``fortinet.fortimanager`` installed." +#~ msgstr "Ansible 2.9 ã¨ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``fortimanager`` httpapi プラグインを使用ã—ã¦ã„ã‚‹å ´åˆã€community.network 2.0.0 ã§ã¯ã€FQCN (``community.network.fortimanager``) ã§ä½¿ç”¨ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN ``fortinet.fortimanager.fortimanager`` を使用ã—ã€``fortinet.fortimanager`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.network manually, you need to make sure to also install ``fortinet.fortimanager`` if you are using the ``fortimanager`` httpapi plugin. While ansible-base 2.10 or newer can use the redirect that community.network 2.0.0 adds, the collection they point to (fortinet.fortimanager) must be installed for it to work." +#~ msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.network をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€``fortimanager`` httpapi プラグインを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``fortinet.fortimanager`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.network 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (fortinet.fortimanager) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" + +#~ msgid "If you use Ansible 2.9 and the ``nso`` modules from this collection, community.network 2.0.0 results in errors when trying to use the nso content by FQCN, like ``community.network.nso_config``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``cisco.nso.nso_config`` for the previous example) and to make sure that you have ``cisco.nso`` installed." +#~ msgstr "Ansible 2.9 ã¨ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``nso`` モジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.network 2.0.0 ã§ã¯ã€``community.network.nso_config`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ nso コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (å‰ã®ä¾‹ã§ã¯``cisco.nso.nso_config``) を使用ã—ã€``cisco.nso`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ã«ã¯ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.network manually, you need to make sure to also install ``cisco.nso`` if you are using any of the ``nso`` modules. While ansible-base 2.10 or newer can use the redirects that community.network 2.0.0 adds, the collection they point to (cisco.nso) must be installed for them to work." +#~ msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.network をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€``nso`` モジュールを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``cisco.nso`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.network 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (cisco.nso) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" + +#~ msgid "If you use Ansible 2.9 and the ``routeros`` plugins or modules from this collections, community.network 2.0.0 results in errors when trying to use the routeros content by FQCN, like ``community.network.routeros_command``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.routeros.command`` for the previous example) and to make sure that you have ``community.routeros`` installed." +#~ msgstr "Ansible 2.9 ã¨ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã® ``routeros`` プラグインやモジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.network 2.0.0 ã§ã¯ã€``community.network.routeros_command`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ routeros コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (å‰ã®ä¾‹ã§ã¯ ``community.routeros.command``) を使用ã—ã€``community.routeros`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.network manually, you need to make sure to also install ``community.routeros`` if you are using any of the ``routeros`` plugins or modules. While ansible-base 2.10 or newer can use the redirects that community.network 2.0.0 adds, the collection they point to (community.routeros) must be installed for them to work." +#~ msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 3.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.network をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€``routeros`` プラグインã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.routeros`` もインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.network 2.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (community.routeros) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" + +#~ msgid "cnos_static_route - move ipaddress import from ansible.netcommon to builtin or package before ipaddress is removed from ansible.netcommon. You need to make sure to have the ipaddress package installed if you are using this module on Python 2.7 (https://github.com/ansible-collections/community.network/pull/129)." +#~ msgstr "cnos_static_route - ansible.netcommon ã‹ã‚‰ ipaddress ãŒå‰Šé™¤ã•ã‚Œã‚‹å‰ã«ã€ansible.netcommon ã‹ã‚‰ ipaddress ã®ã‚¤ãƒ³ãƒãƒ¼ãƒˆã‚’ビルドインã¾ãŸã¯ãƒ‘ッケージã«ç§»å‹•ã—ã¾ã™ã€‚ã“ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’ Python 2.7 ã§ä½¿ã†å ´åˆã¯ã€ipaddress パッケージãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (https://github.com/ansible-collections/community.network/pull/129)。" + +#~ msgid "os10_bgp - Changed \"subnet\" key as list format instead of dictionary format under \"listen\" key to support multiple neighbor prefix for listen command" +#~ msgstr "os10_bgp - listen コマンドã®è¤‡æ•°ã® neighbor 接é 辞をサãƒãƒ¼ãƒˆã™ã‚‹ãŸã‚ã«ã€ã€Œlistenã€ã‚ーã®ã€Œsubnetã€ã‚ーをã€ãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼å½¢å¼ã‹ã‚‰ãƒªã‚¹ãƒˆå½¢å¼ã«å¤‰æ›´ã—ã¾ã—ãŸã€‚" + +#~ msgid "os10_bgp - Changed \"vrf\" key as list format instead of dictionary format to supprot multiple VRF in router BGP and changed the \"vrf\" key name to \"vrfs\"" +#~ msgstr "os10_bgp - ルーター BGP ã§è¤‡æ•°ã® VRF をサãƒãƒ¼ãƒˆã™ã‚‹ãŸã‚ã«ã€ã€Œvrfã€ã‚ーをディクショナリー形å¼ã§ã¯ãªãリスト形å¼ã«å¤‰æ›´ã—ã€ã€Œvrfã€ã‚ーã®åå‰ã‚’「vrfsã€ã«å¤‰æ›´ã—ã¾ã—ãŸã€‚" + +#~ msgid "ngine_io.cloudstack" +#~ msgstr "ngine_io.cloudstack" + +#~ msgid "Authentication option using INI files e.g. ``cloudstack.ini`` has been removed. The only supported option to authenticate is by using the module params with fallback to the ENV variables." +#~ msgstr "INI ファイル (例: ``cloudstack.ini``) を使用ã—ãŸèªè¨¼ã‚ªãƒ—ションã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ç¾åœ¨ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã‚‹èªè¨¼æ–¹æ³•ã¯ã€ENV 変数ã«ãƒ•ã‚©ãƒ¼ãƒ«ãƒãƒƒã‚¯ã—ã¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ‘ラメーターを使用ã™ã‚‹æ–¹æ³•ã®ã¿ã§ã™ã€‚" + +#~ msgid "default zone deprecation - The `zone` param default value, across multiple modules, has been deprecated due to unreliable API (https://github.com/ngine-io/ansible-collection-cloudstack/pull/62)." +#~ msgstr "デフォルトゾーンãŒéžæŽ¨å¥¨ã«ãªã‚‹ - API ã®ä¿¡é ¼æ€§ãŒä½Žã„ãŸã‚ã€è¤‡æ•°ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«é–“㧠`zone` パラメーターã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ãŒéžæŽ¨å¥¨ã«ãªã‚Šã¾ã—㟠(https://github.com/ngine-io/ansible-collection-cloudstack/pull/62)。" + +#~ msgid "cisco.aci" +#~ msgstr "cisco.aci" + +#~ msgid "Change certificate_name to name in aci_aaa_user_certificate module for query operation" +#~ msgstr "クエリーæ“作㮠certificate_name ã®åå‰ã‚’ aci_aaa_user_certificate モジュールã®åå‰ã«å¤‰æ›´ã—ã¾ã™ã€‚" + +#~ msgid "For community.general 3.0.0, the ``ome_device_info``, ``idrac_firmware`` and ``idrac_server_config_profile`` modules will be moved to the `dellemc.openmanage <https://galaxy.ansible.com/dellemc/openmanage>`_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything." +#~ msgstr "community.general 3.0.0 ã®å ´åˆã€``ome_device_info`` モジュールã€``idrac_firmware`` モジュールã€ãŠã‚ˆã³ ``idrac_server_config_profile`` モジュール㯠`dellemc.openmanage <https://galaxy.ansible.com/dellemc/openmanage>`_ コレクションã«ç§»å‹•ã—ã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„るユーザーãŒä½•ã‚‚変更ã™ã‚‹å¿…è¦ãŒãªã„よã†ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’挿入ã—ã¾ã™ã€‚" + +#~ msgid "If you use Ansible 2.9 and explicitly use the DellEMC modules mentioned above from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``dellemc.openmanage.`` instead of ``community.general.``, for example replace ``community.general.ome_device_info`` in a task by ``dellemc.openmanage.ome_device_info``." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ä¸Šè¨˜ã® DellEMC モジュールを明示的ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã‚’ ``community.general.`` ã§ã¯ãªã ``dellemc.openmanage.`` ã§å§‹ã¾ã‚‹ FQCN を使用ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (例: ``dellemc.openmanage.ome_device_info`` ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã§ ``community.general.ome_device_info`` ã‚’ç½®ãæ›ãˆã¾ã™)。" + +#~ msgid "If you use ansible-base and installed ``community.general`` manually and rely on the DellEMC modules mentioned above, you have to make sure to install the ``dellemc.openmanage`` collection as well. If you are using FQCNs, for example ``community.general.ome_device_info`` instead of ``ome_device_info``, it will continue working, but we still recommend to adjust the FQCNs as well." +#~ msgstr "ansible-base を使用ã—㦠``community.general`` を手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã€ä¸Šè¨˜ã® DellEMC モジュールã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ã€``dellemc.openmanage`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã€ãŸã¨ãˆã° ``ome_device_info`` ã®ä»£ã‚ã‚Šã« ``community.general.ome_device_info`` を使用ã—ã¦ã„ã‚‹å ´åˆã€å‹•ä½œã¯ç¶™ç¶šã•ã‚Œã¾ã™ãŒã€ã“ã® FQCN も調整ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "The community.general collection no longer depends on the ansible.netcommon collection (https://github.com/ansible-collections/community.general/pull/1561)." +#~ msgstr "community.general コレクションã¯ã€ansible.netcommon コレクションã«ä¾å˜ã—ãªããªã‚Šã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/1561)。" + +#~ msgid "Removed the existing deprecated modules." +#~ msgstr "æ—¢å˜ã®éžæŽ¨å¥¨ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’削除。" + +#~ msgid "Standardization of ten iDRAC ansible modules based on ansible guidelines." +#~ msgstr "Ansible ガイドラインã«åŸºã¥ã 10 個㮠iDRAC Ansible モジュールã®æ¨™æº–化。" + +#~ msgid "Support for OpenManage Enterprise Modular." +#~ msgstr "OpenManage Enterprise Modular ã®ã‚µãƒãƒ¼ãƒˆã€‚" + +#~ msgid "os10_bgp - Enhanced router bgp keyword support for non-default vrf which are supported for default vrf and additional keyword to support both default and non-default vrf" +#~ msgstr "os10_bgp - デフォルト vrf ã«å¯¾å¿œã—ã¦ã„ã‚‹éžãƒ‡ãƒ•ã‚©ãƒ«ãƒˆ vrf 用ã®ãƒ«ãƒ¼ã‚¿ãƒ¼ bgp ã‚ーワードã®ã‚µãƒãƒ¼ãƒˆã‚’強化ã—ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãŠã‚ˆã³éžãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã® vrf ã®ä¸¡æ–¹ã«å¯¾å¿œã™ã‚‹ãŸã‚ã®è¿½åŠ ã‚ãƒ¼ãƒ¯ãƒ¼ãƒ‰ã‚’è¿½åŠ ã—ã¾ã—ãŸã€‚" + +#~ msgid "os10_snmp role - Added support for snmp V3 features in community, group, host, engineID" +#~ msgstr "os10_snmp role - コミュニティーã€ã‚°ãƒ«ãƒ¼ãƒ—ã€ãƒ›ã‚¹ãƒˆã€engineID ã«ãŠã‘ã‚‹ snmp V3 機能ã®ã‚µãƒãƒ¼ãƒˆã‚’è¿½åŠ ã—ã¾ã—ãŸã€‚" + +#~ msgid "kubernetes.core" +#~ msgstr "kubernetes.core" + +#~ msgid "Add changelog and fragments and document changelog process (https://github.com/ansible-collections/kubernetes.core/pull/131)." +#~ msgstr "変更ãƒã‚°ãŠã‚ˆã³ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã‚’è¿½åŠ ã—ã€å¤‰æ›´ãƒã‚°ãƒ—ãƒã‚»ã‚¹ã‚’文書化ã—ã¾ã™ (https://github.com/ansible-collections/kubernetes.core/pull/131)。" + +#~ msgid "helm - New module for managing Helm charts (https://github.com/ansible-collections/kubernetes.core/pull/61)." +#~ msgstr "helm - Helm ãƒãƒ£ãƒ¼ãƒˆç®¡ç†ç”¨ã®æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/kubernetes.core/pull/61)。" + +#~ msgid "helm_info - New module for retrieving Helm chart information (https://github.com/ansible-collections/kubernetes.core/pull/61)." +#~ msgstr "helm_info - Helm ãƒãƒ£ãƒ¼ãƒˆæƒ…å ±ã‚’å–å¾—ã™ã‚‹æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/kubernetes.core/pull/61)。" + +#~ msgid "helm_plugin - new module to manage Helm plugins (https://github.com/ansible-collections/kubernetes.core/pull/154)." +#~ msgstr "helm_plugin - Helm プラグインを管ç†ã™ã‚‹æ–°ã—ã„モジュール (https://github.com/ansible-collections/kubernetes.core/pull/154)。" + +#~ msgid "helm_plugin_info - new modules to gather information about Helm plugins (https://github.com/ansible-collections/kubernetes.core/pull/154)." +#~ msgstr "helm_plugin_info - Helm プラグインã«é–¢ã™ã‚‹æƒ…å ±ã‚’åŽé›†ã™ã‚‹æ–°ã—ã„モジュール (https://github.com/ansible-collections/kubernetes.core/pull/154)。" + +#~ msgid "helm_repository - New module for managing Helm repositories (https://github.com/ansible-collections/kubernetes.core/pull/61)." +#~ msgstr "helm_repository - Helm リãƒã‚¸ãƒˆãƒªãƒ¼ã‚’管ç†ã™ã‚‹ãŸã‚ã®æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/kubernetes.core/pull/61)。" + +#~ msgid "k8s - Add support for template parameter (https://github.com/ansible-collections/kubernetes.core/pull/230)." +#~ msgstr "k8s - テンプレートパラメーターã®ã‚µãƒãƒ¼ãƒˆã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/ansible-collections/kubernetes.core/pull/230)。" + +#~ msgid "k8s_* - Add support for vaulted kubeconfig and src (https://github.com/ansible-collections/kubernetes.core/pull/193)." +#~ msgstr "k8s_* - Vault 済㿠kubeconfig ãŠã‚ˆã³ src ã®ã‚µãƒãƒ¼ãƒˆã‚’è¿½åŠ ã—ã¾ã™ (https://github.com/ansible-collections/kubernetes.core/pull/193)。" + +#~ msgid "k8s_exec - New module for executing commands on pods via Kubernetes API (https://github.com/ansible-collections/kubernetes.core/pull/14)." +#~ msgstr "k8s_exec - Kubernetes API を使用ã—㦠Pod ã§ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã™ã‚‹æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/kubernetes.core/pull/14)。" + +#~ msgid "k8s_exec - Return rc for the command executed (https://github.com/ansible-collections/kubernetes.core/pull/158)." +#~ msgstr "k8s_exec - 実行ã—ãŸã‚³ãƒžãƒ³ãƒ‰ã® rc ã‚’è¿”ã—ã¾ã™ (https://github.com/ansible-collections/kubernetes.core/pull/158)。" + +#~ msgid "k8s_log - New module for retrieving pod logs (https://github.com/ansible-collections/kubernetes.core/pull/16)." +#~ msgstr "k8s_log - Pod ãƒã‚°ã‚’å–å¾—ã™ã‚‹æ–°è¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (https://github.com/ansible-collections/kubernetes.core/pull/16)。" + +#~ msgid "All Google cloud modules and plugins have now been migrated away from this collection. They can be found in either the `community.google <https://galaxy.ansible.com/community/google>`_ or `google.cloud <https://galaxy.ansible.com/google/cloud>`_ collections. If you use ansible-base 2.10 or newer, redirections have been provided." +#~ msgstr "Google クラウドモジュールãŠã‚ˆã³ãƒ—ラグインã¯ã™ã¹ã¦ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰ç§»è¡Œã•ã‚Œã¾ã—ãŸã€‚ã“れら㯠`community.google <https://galaxy.ansible.com/community/google>`_ コレクションã¾ãŸã¯ `google.cloud <https://galaxy.ansible.com/google/cloud>`_ コレクションã«ã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¦ã„ã¾ã™ã€‚" + +#~ msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.gce_img`` → ``community.google.gce_img``) and make sure to install the community.google or google.cloud collections as appropriate." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN を調整 (``community.general.gce_img`` →``community.google.gce_img``) ã—ã€å¿…è¦ã«å¿œã˜ã¦ community.google コレクションã¾ãŸã¯ google.cloud collections コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" + +#~ msgid "All Kubevirt modules and plugins have now been migrated from community.general to the `community.kubevirt <https://galaxy.ansible.com/community/kubevirt>`_ Ansible collection. If you use ansible-base 2.10 or newer, redirections have been provided." +#~ msgstr "ã™ã¹ã¦ã® Kubevirt モジュールãŠã‚ˆã³ãƒ—ラグインã¯ã€community.general ã‹ã‚‰ `community.kubevirt <https://galaxy.ansible.com/community/kubevirt>`_ Ansibleコレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.kubevirt_vm`` → ``community.kubevirt.kubevirt_vm``) and make sure to install the community.kubevirt collection." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.general.kubevirt_vm`` →``community.kubevirt.kubevirt_vm``) を調整ã—ã€community.kubevirt コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" + +#~ msgid "All ``docker`` modules and plugins have been removed from this collection. They have been migrated to the `community.docker <https://galaxy.ansible.com/community/docker>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided." +#~ msgstr "ã™ã¹ã¦ã® ``docker`` モジュールã¨ãƒ—ラグインãŒã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れら㯠`community.docker <https://galaxy.ansible.com/community/docker>`_ コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.docker_container`` → ``community.docker.docker_container``) and make sure to install the community.docker collection." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.general.docker_container`` →``community.docker.docker_container``) を調整ã—ã€community.docker コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" + +#~ msgid "All ``hetzner`` modules have been removed from this collection. They have been migrated to the `community.hrobot <https://galaxy.ansible.com/community/hrobot>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided." +#~ msgstr "ã™ã¹ã¦ã® ``hetzner`` モジュールãŒã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れら㯠`community.hrobot <https://galaxy.ansible.com/community/hrobot>`_ コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.hetzner_firewall`` → ``community.hrobot.firewall``) and make sure to install the community.hrobot collection." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.general.hetzner_firewall`` →``community.hrobot.firewall``) を調整ã—ã€community.hrobot コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" + +#~ msgid "All ``postgresql`` modules have been removed from this collection. They have been migrated to the `community.postgresql <https://galaxy.ansible.com/community/postgresql>`_ collection." +#~ msgstr "ã™ã¹ã¦ã® ``postgresql`` モジュールã¯ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れら㯠`community.postgresql <https://galaxy.ansible.com/community/postgresql>`_ コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚" + +#~ msgid "If you use ansible-base 2.10 or newer, redirections have been provided. If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.postgresql_info`` → ``community.postgresql.postgresql_info``) and make sure to install the community.postgresql collection." +#~ msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¦ã„ã¾ã™ã€‚Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.general.postgresql_info`` →``community.postgresql.postgresql_info``) を調整ã—ã€å¿…è¦ã«å¿œã˜ã¦ community.postgresql コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" + +#~ msgid "The ``hashi_vault`` lookup plugin has been removed from this collection. It has been migrated to the `community.hashi_vault <https://galaxy.ansible.com/community/hashi_vault>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided." +#~ msgstr "``hashi_vault`` lookup プラグインã¯ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れ㯠`community.hashi_vault <https://galaxy.ansible.com/community/hashi_vault>`_ コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¦ã„ã¾ã™ã€‚" + +#~ msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.hashi_vault`` → ``community.hashi_vault.hashi_vault``) and make sure to install the community.hashi_vault collection." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.general.hashi_vault`` →``community.hashi_vault.hashi_vault``) を調整ã—ã€community.hashi_vault コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" + +#~ msgid "The ``oc`` connection plugin has been removed from this collection. It has been migrated to the `community.okd <https://galaxy.ansible.com/community/okd>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided." +#~ msgstr "``oc`` connection プラグインã¯ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れ㯠`community.okd <https://galaxy.ansible.com/community/okd>`_ コレクションã«ç§»è¡Œã•ã‚Œã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.oc`` → ``community.okd.oc``) and make sure to install the community.okd collection." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.general.oc`` →``community.okd.oc``) を調整ã—ã€community.okd コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" + +#~ msgid "The deprecated ``actionable`` callback plugin has been removed. Use the ``ansible.builtin.default`` callback plugin with ``display_skipped_hosts = no`` and ``display_ok_hosts = no`` options instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``actionable`` コールãƒãƒƒã‚¯ãƒ—ラグインãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã«ã€``ansible.builtin.default`` コールãƒãƒƒã‚¯ãƒ—ラグインを ``display_skipped_hosts = no`` オプションãŠã‚ˆã³ ``display_ok_hosts = no`` オプションã¨ä¸€ç·’ã«ä½¿ç”¨ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``foreman`` module has been removed. Use the modules from the theforeman.foreman collection instead (https://github.com/ansible-collections/community.general/pull/1347) (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``foreman`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« theforeman.foreman コレクションã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347) (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``full_skip`` callback plugin has been removed. Use the ``ansible.builtin.default`` callback plugin with ``display_skipped_hosts = no`` option instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``full_skip`` コールãƒãƒƒã‚¯ãƒ—ラグインãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã«ã€``ansible.builtin.default`` コールãƒãƒƒã‚¯ãƒ—ラグインを ``display_skipped_hosts = no`` オプションã¨ä¸€ç·’ã«ä½¿ç”¨ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``gcdns_record`` module has been removed. Use ``google.cloud.gcp_dns_resource_record_set`` instead (https://github.com/ansible-collections/community.general/pull/1370)." +#~ msgstr "éžæŽ¨å¥¨ã® ``gcdns_record`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_dns_resource_record_set`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" + +#~ msgid "The deprecated ``gcdns_zone`` module has been removed. Use ``google.cloud.gcp_dns_managed_zone`` instead (https://github.com/ansible-collections/community.general/pull/1370)." +#~ msgstr "éžæŽ¨å¥¨ã® ``gcdns_zone`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_dns_managed_zone`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" + +#~ msgid "The deprecated ``gce`` module has been removed. Use ``google.cloud.gcp_compute_instance`` instead (https://github.com/ansible-collections/community.general/pull/1370)." +#~ msgstr "éžæŽ¨å¥¨ã® ``gce`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_compute_instance`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" + +#~ msgid "The deprecated ``gcp_backend_service`` module has been removed. Use ``google.cloud.gcp_compute_backend_service`` instead (https://github.com/ansible-collections/community.general/pull/1370)." +#~ msgstr "éžæŽ¨å¥¨ã® ``gcp_backend_service`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_compute_backend_service`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" + +#~ msgid "The deprecated ``gcp_forwarding_rule`` module has been removed. Use ``google.cloud.gcp_compute_forwarding_rule`` or ``google.cloud.gcp_compute_global_forwarding_rule`` instead (https://github.com/ansible-collections/community.general/pull/1370)." +#~ msgstr "éžæŽ¨å¥¨ã® ``gcp_forwarding_rule`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_compute_forwarding_rule`` ã¾ãŸã¯ ``google.cloud.gcp_compute_global_forwarding_rule`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" + +#~ msgid "The deprecated ``gcp_healthcheck`` module has been removed. Use ``google.cloud.gcp_compute_health_check``, ``google.cloud.gcp_compute_http_health_check`` or ``google.cloud.gcp_compute_https_health_check`` instead (https://github.com/ansible-collections/community.general/pull/1370)." +#~ msgstr "éžæŽ¨å¥¨ã® ``gcp_healthcheck`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_compute_health_check``ã€``google.cloud.gcp_compute_http_health_check``ã€ã¾ãŸã¯ ``google.cloud.gcp_compute_https_health_check`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" + +#~ msgid "The deprecated ``gcp_target_proxy`` module has been removed. Use ``google.cloud.gcp_compute_target_http_proxy`` instead (https://github.com/ansible-collections/community.general/pull/1370)." +#~ msgstr "éžæŽ¨å¥¨ã® ``gcp_target_proxy`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_compute_target_http_proxy`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" + +#~ msgid "The deprecated ``gcp_url_map`` module has been removed. Use ``google.cloud.gcp_compute_url_map`` instead (https://github.com/ansible-collections/community.general/pull/1370)." +#~ msgstr "éžæŽ¨å¥¨ã® ``gcp_url_map`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_compute_url_map`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" + +#~ msgid "The deprecated ``gcspanner`` module has been removed. Use ``google.cloud.gcp_spanner_database`` and/or ``google.cloud.gcp_spanner_instance`` instead (https://github.com/ansible-collections/community.general/pull/1370)." +#~ msgstr "éžæŽ¨å¥¨ã® ``gcspanner`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``google.cloud.gcp_spanner_database`` ã‚„ ``google.cloud.gcp_spanner_instance`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1370)。" + +#~ msgid "The deprecated ``github_hooks`` module has been removed. Use ``community.general.github_webhook`` and ``community.general.github_webhook_info`` instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``github_hooks`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``community.general.github_webhook`` ãŠã‚ˆã³ ``community.general.github_webhook_info`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``katello`` module has been removed. Use the modules from the theforeman.foreman collection instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``katello`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« theforeman.foreman コレクションã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``na_cdot_aggregate`` module has been removed. Use netapp.ontap.na_ontap_aggregate instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``na_cdot_aggregate`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_aggregate を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``na_cdot_license`` module has been removed. Use netapp.ontap.na_ontap_license instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``na_cdot_license`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_license を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``na_cdot_lun`` module has been removed. Use netapp.ontap.na_ontap_lun instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``na_cdot_lun`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_lun を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``na_cdot_qtree`` module has been removed. Use netapp.ontap.na_ontap_qtree instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``na_cdot_qtree`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_qtree を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``na_cdot_svm`` module has been removed. Use netapp.ontap.na_ontap_svm instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``na_cdot_svm`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_svm を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``na_cdot_user_role`` module has been removed. Use netapp.ontap.na_ontap_user_role instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``na_cdot_user_role`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_user_role を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``na_cdot_user`` module has been removed. Use netapp.ontap.na_ontap_user instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``na_cdot_user`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_user を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``na_cdot_volume`` module has been removed. Use netapp.ontap.na_ontap_volume instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``na_cdot_volume`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_volume を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``sf_account_manager`` module has been removed. Use netapp.elementsw.na_elementsw_account instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``sf_account_manager`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.elementsw.na_elementsw_account を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``sf_check_connections`` module has been removed. Use netapp.elementsw.na_elementsw_check_connections instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``sf_check_connections`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.elementsw.na_elementsw_check_connections を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``sf_snapshot_schedule_manager`` module has been removed. Use netapp.elementsw.na_elementsw_snapshot_schedule instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``sf_snapshot_schedule_manager`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.elementsw.na_elementsw_snapshot_schedule を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``sf_volume_access_group_manager`` module has been removed. Use netapp.elementsw.na_elementsw_access_group instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``sf_volume_access_group_manager`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.elementsw.na_elementsw_access_group を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``sf_volume_manager`` module has been removed. Use netapp.elementsw.na_elementsw_volume instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``sf_volume_manager`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.elementsw.na_elementsw_volume を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The deprecated ``stderr`` callback plugin has been removed. Use the ``ansible.builtin.default`` callback plugin with ``display_failed_stderr = yes`` option instead (https://github.com/ansible-collections/community.general/pull/1347)." +#~ msgstr "éžæŽ¨å¥¨ã® ``stderr`` コールãƒãƒƒã‚¯ãƒ—ラグインãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã«ã€``ansible.builtin.default`` コールãƒãƒƒã‚¯ãƒ—ラグインを ``display_failed_stderr = yes`` オプションã¨ä¸€ç·’ã«ä½¿ç”¨ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1347)。" + +#~ msgid "The redirect of the ``conjur_variable`` lookup plugin to ``cyberark.conjur.conjur_variable`` collection was removed (https://github.com/ansible-collections/community.general/pull/1346)." +#~ msgstr "``conjur_variable`` ルックアッププラグイン㮠``cyberark.conjur.conjur_variable`` コレクションã¸ã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒå‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/1346)。" + +#~ msgid "The redirect of the ``firewalld`` module and the ``firewalld`` module_utils to the ``ansible.posix`` collection was removed (https://github.com/ansible-collections/community.general/pull/1346)." +#~ msgstr "``firewalld`` モジュールãŠã‚ˆã³ ``firewalld`` module_utils ã® ``ansible.posix`` コレクションã¸ã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒå‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/1346)。" + +#~ msgid "The redirect to the ``community.digitalocean`` collection was removed for: the ``digital_ocean`` doc fragment, the ``digital_ocean`` module_utils, and the following modules: ``digital_ocean``, ``digital_ocean_account_facts``, ``digital_ocean_account_info``, ``digital_ocean_block_storage``, ``digital_ocean_certificate``, ``digital_ocean_certificate_facts``, ``digital_ocean_certificate_info``, ``digital_ocean_domain``, ``digital_ocean_domain_facts``, ``digital_ocean_domain_info``, ``digital_ocean_droplet``, ``digital_ocean_firewall_facts``, ``digital_ocean_firewall_info``, ``digital_ocean_floating_ip``, ``digital_ocean_floating_ip_facts``, ``digital_ocean_floating_ip_info``, ``digital_ocean_image_facts``, ``digital_ocean_image_info``, ``digital_ocean_load_balancer_facts``, ``digital_ocean_load_balancer_info``, ``digital_ocean_region_facts``, ``digital_ocean_region_info``, ``digital_ocean_size_facts``, ``digital_ocean_size_info``, ``digital_ocean_snapshot_facts``, ``digital_ocean_snapshot_info``, ``digital_ocean_sshkey``, ``digital_ocean_sshkey_facts``, ``digital_ocean_sshkey_info``, ``digital_ocean_tag``, ``digital_ocean_tag_facts``, ``digital_ocean_tag_info``, ``digital_ocean_volume_facts``, ``digital_ocean_volume_info`` (https://github.com/ansible-collections/community.general/pull/1346)." +#~ msgstr "``community.digitalocean`` コレクションã¸ã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒå‰Šé™¤ã•ã‚ŒãŸã®ã¯ã€``digital_ocean`` ドã‚ュメントã®ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã€``digital_ocean`` module_utilsã€ãŠã‚ˆã³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``digital_ocean``ã€``digital_ocean_account_facts``ã€``digital_ocean_account_info``ã€``digital_ocean_block_storage``ã€``digital_ocean_certificate``ã€``digital_ocean_certificate_facts``ã€``digital_ocean_certificate_info``ã€``digital_ocean_domain``ã€``digital_ocean_domain_facts``ã€``digital_ocean_domain_info``ã€``digital_ocean_droplet``ã€``digital_ocean_firewall_facts``ã€``digital_ocean_firewall_info``ã€``digital_ocean_floating_ip``ã€``digital_ocean_floating_ip_facts``ã€``digital_ocean_floating_ip_info``ã€``digital_ocean_image_facts``ã€``digital_ocean_image_info``ã€``digital_ocean_load_balancer_facts``ã€``digital_ocean_load_balancer_info``ã€``digital_ocean_region_facts``ã€``digital_ocean_region_info``ã€``digital_ocean_size_facts``ã€``digital_ocean_size_info``ã€``digital_ocean_snapshot_facts``ã€``digital_ocean_snapshot_info``ã€``digital_ocean_sshkey``ã€``digital_ocean_sshkey_facts``ã€``digital_ocean_sshkey_info``ã€``digital_ocean_tag``ã€``digital_ocean_tag_facts``ã€``digital_ocean_tag_info``ã€``digital_ocean_volume_facts``ã€``digital_ocean_volume_info`` ã§ã™ (https://github.com/ansible-collections/community.general/pull/1346)。" + +#~ msgid "The redirect to the ``community.mysql`` collection was removed for: the ``mysql`` doc fragment, the ``mysql`` module_utils, and the following modules: ``mysql_db``, ``mysql_info``, ``mysql_query``, ``mysql_replication``, ``mysql_user``, ``mysql_variables`` (https://github.com/ansible-collections/community.general/pull/1346)." +#~ msgstr "``community.mysql`` コレクションã¸ã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒå‰Šé™¤ã•ã‚ŒãŸã®ã¯ã€``mysql`` ドã‚ュメントã®ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã€``mysql`` module_utilsã€ãŠã‚ˆã³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``mysql_db``ã€``mysql_info``ã€``mysql_query``ã€``mysql_replication``ã€``mysql_user``ã€``mysql_variables`` ã§ã™ (https://github.com/ansible-collections/community.general/pull/1346)。" + +#~ msgid "The redirect to the ``community.proxysql`` collection was removed for: the ``proxysql`` doc fragment, and the following modules: ``proxysql_backend_servers``, ``proxysql_global_variables``, ``proxysql_manage_config``, ``proxysql_mysql_users``, ``proxysql_query_rules``, ``proxysql_replication_hostgroups``, ``proxysql_scheduler`` (https://github.com/ansible-collections/community.general/pull/1346)." +#~ msgstr "``proxysql`` doc フラグメントã¨ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``proxysql_backend_servers``ã€``proxysql_global_variables``ã€``proxysql_manage_config``ã€``proxysql_mysql_users``ã€``proxysql_query_rules``ã€``proxysql_replication_hostgroups``ã€ãŠã‚ˆã³ ``proxysql_scheduler`` ã§ã€``community.proxysql`` コレクションã¸ã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒå‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.general/pull/1346)。" + +#~ msgid "The redirect to the ``infinidat.infinibox`` collection was removed for: the ``infinibox`` doc fragment, the ``infinibox`` module_utils, and the following modules: ``infini_export``, ``infini_export_client``, ``infini_fs``, ``infini_host``, ``infini_pool``, ``infini_vol`` (https://github.com/ansible-collections/community.general/pull/1346)." +#~ msgstr "``infinidat.infinibox`` コレクションã¸ã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒå‰Šé™¤ã•ã‚ŒãŸã®ã¯ã€``infinibox`` ドã‚ュメントã®ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã€``infinibox`` module_utilsã€ãŠã‚ˆã³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``infini_export``ã€``infini_export_client``ã€``infini_fs``ã€``infini_host``ã€``infini_pool``ã€``infini_vol`` ã§ã™ (https://github.com/ansible-collections/community.general/pull/1346)。" + +#~ msgid "iptables_state - the ``ANSIBLE_ASYNC_DIR`` environment is no longer supported, use the ``async_dir`` shell option instead (https://github.com/ansible-collections/community.general/pull/1371)." +#~ msgstr "iptables_state - ``ANSIBLE_ASYNC_DIR`` 環境ã¯ã‚µãƒãƒ¼ãƒˆå¯¾è±¡å¤–ã«ãªã£ãŸãŸã‚ã€ä»£ã‚ã‚Šã« ``async_dir`` シェルオプションを使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1371)。" + +#~ msgid "memcached cache plugin - do not import ``CacheModule``s directly. Use ``ansible.plugins.loader.cache_loader`` instead (https://github.com/ansible-collections/community.general/pull/1371)." +#~ msgstr "memcached cache プラグイン - ``CacheModule`` を直接インãƒãƒ¼ãƒˆã—ã¾ã›ã‚“。代ã‚ã‚Šã« ``ansible.plugins.loader.cache_loader`` を使用ã—ã¾ã™ (https://github.com/ansible-collections/community.general/pull/1371)。" + +#~ msgid "redis cache plugin - do not import ``CacheModule``s directly. Use ``ansible.plugins.loader.cache_loader`` instead (https://github.com/ansible-collections/community.general/pull/1371)." +#~ msgstr "redis cache プラグイン - ``CacheModule`` を直接インãƒãƒ¼ãƒˆã—ã¾ã›ã‚“。代ã‚ã‚Šã« ``ansible.plugins.loader.cache_loader`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1371)。" + +#~ msgid "xml - when ``content=attribute``, the ``attribute`` option is ignored (https://github.com/ansible-collections/community.general/pull/1371)." +#~ msgstr "XML - ``content=attribute`` ã®å ´åˆã€``attribute`` オプションãŒç„¡è¦–ã•ã‚Œã¾ã™ (https://github.com/ansible-collections/community.general/pull/1371)。" + +#~ msgid "All FortiOS modules and plugins have been removed from this collection. They have been migrated to the `community.fortios <https://galaxy.ansible.com/community/fortios>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided." +#~ msgstr "ã™ã¹ã¦ã® FortiOS モジュールã¨ãƒ—ラグインãŒã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れら㯠`community.fortios <https://galaxy.ansible.com/community/fortios>`_ コレクションã«ç§»è¡Œã•ã‚Œã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.network.fmgr_device`` → ``community.fortios.fmgr_device``) and make sure to install the `community.fortios` collection." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.network.fmgr_device`` →``community.fortios.fmgr_device``) を調整ã—ã€`community.fortios` コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" + +#~ msgid "All ``nso`` modules have been removed from this collection. They have been migrated to the `cisco.nso <https://galaxy.ansible.com/cisco/nso>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided." +#~ msgstr "ã™ã¹ã¦ã® ``nso`` モジュールãŒã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れら㯠`cisco.nso <https://galaxy.ansible.com/cisco/nso>`_ コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.network.nso_config`` → ``cisco.nso.nso_config``) and make sure to install the `cisco.nso` collection." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.network.nso_config`` →``cisco.nso.nso_config``) を調整ã—ã€`cisco.nso` コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" + +#~ msgid "All ``routeros`` modules and plugins have been removed from this collection. They have been migrated to the `community.routeros <https://galaxy.ansible.com/community/routeros>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided." +#~ msgstr "ã™ã¹ã¦ã® ``routeros`` モジュールã¨ãƒ—ラグインãŒã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れら㯠`community.routeros <https://galaxy.ansible.com/community/routeros>`_ コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.network.routeros_command`` → ``community.routeros.command``) and make sure to install the community.routeros collection." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN を調整 (``community.network.routeros_command`` →``community.routeros.command``) ã—ã€community.routeros コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" + +#~ msgid "The ``cp_publish`` module has been removed from this collection. It was a duplicate of ``check_point.mgmt.cp_mgmt_publish`` in the `check_point.mgmt <https://galaxy.ansible.com/check_point/mgmt>`_ collection. If you use ansible-base 2.10 or newer, redirections have been provided. If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.network.cp_publish`` → ``check_point.mgmt.cp_mgmt_publish``) and make sure to install the check_point.mgmt collection." +#~ msgstr "``cp_publish`` モジュールã¯ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れ㯠`check_point.mgmt <https://galaxy.ansible.com/check_point/mgmt>`_ コレクション㮠``check_point.mgmt.cp_mgmt_publish`` ã¨é‡è¤‡ã—ã¦ã„ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.network.cp_publish`` →``check_point.mgmt.cp_mgmt_publish``) を調整ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã¾ãŸã€check_point.mgmt コレクションをインストールã—ã¦ãã ã•ã„。" + +#~ msgid "The ``fortimanager`` httpapi plugin has been removed from this collection. It was a duplicate of the one in the `fortinet.fortimanager <https://galaxy.ansible.com/fortinet/fortimanager>`_ collection. If you use ansible-base 2.10 or newer, a redirection has been provided." +#~ msgstr "``fortimanager`` httpapi プラグインã¯ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“れ㯠`fortinet.fortimanager <https://galaxy.ansible.com/fortinet/fortimanager>`_ コレクションã«ã‚ã‚‹ã‚‚ã®ã¨é‡è¤‡ã—ã¦ã„ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’ãŠä½¿ã„ã®æ–¹ã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒç”¨æ„ã•ã‚Œã¦ã„ã¾ã™ã€‚" + +#~ msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.network.fortimanager`` → ``fortinet.fortimanager.fortimanager``) and make sure to install the `fortinet.fortimanager` collection." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.network.fortimanager`` →``fortinet.fortimanager.fortimanager``) を調整ã—ã€`fortinet.fortimanager` コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" + +#~ msgid "The dependency on the ``check_point.mgmt`` collection has been removed. If you depend on that installing ``community.network`` also installs ``check_point.mgmt``, you have to make sure to install ``check_point.mgmt`` explicitly." +#~ msgstr "``check_point.mgmt`` コレクションã®ä¾å˜é–¢ä¿‚ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚``community.network`` ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã«ã‚ˆã£ã¦ ``check_point.mgmt`` もインストールã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€å¿…ãš ``check_point.mgmt`` を明示的ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "The deprecated Pluribus Networks modules ``pn_cluster``, ``pn_ospf``, ``pn_ospfarea``, ``pn_show``, ``pn_trunk``, ``pn_vlag``, ``pn_vlan``, ``pn_vrouter``, ``pn_vrouterbgp``, ``pn_vrouterif``, ``pn_vrouterlbif`` have been removed (https://github.com/ansible-collections/community.network/pull/176)." +#~ msgstr "éžæŽ¨å¥¨ã® Pluribus Networks モジュール ``pn_cluster``ã€``pn_ospf``ã€``pn_ospfarea``ã€``pn_show``ã€``pn_trunk``ã€``pn_vlag`` ``pn_vlan``ã€``pn_vrouter``ã€``pn_vrouterbgp``ã€``pn_vrouterif``ã€ãŠã‚ˆã³ ``pn_vrouterlbif`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.network/pull/176)。" + +#~ msgid "The deprecated modules ``panos_admin``, ``panos_admpwd``, ``panos_cert_gen_ssh``, ``panos_check``, ``panos_commit``, ``panos_dag``, ``panos_dag_tags``, ``panos_import``, ``panos_interface``, ``panos_lic``, ``panos_loadcfg``, ``panos_match_rule``, ``panos_mgtconfig``, ``panos_nat_rule``, ``panos_object``, ``panos_op``, ``panos_pg``, ``panos_query_rules``, ``panos_restart``, ``panos_sag``, ``panos_security_rule``, ``panos_set`` have been removed. Use modules from the `paloaltonetworks.panos collection <https://galaxy.ansible.com/paloaltonetworks/panos>`_ instead (https://github.com/ansible-collections/community.network/pull/176)." +#~ msgstr "éžæŽ¨å¥¨ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``panos_admin``ã€``panos_admpwd``ã€``panos_cert_gen_ssh``ã€``panos_check``ã€``panos_commit``ã€``panos_dag``ã€``panos_dag_tags`` ``panos_import``ã€``panos_interface``ã€``panos_lic``ã€``panos_loadcfg``ã€``panos_match_rule``ã€``panos_mgtconfig``ã€``panos_nat_rule``ã€``panos_object``ã€``panos_op``ã€``panos_pg``ã€``panos_query_rules``ã€``panos_restart``ã€``panos_sag``ã€``panos_security_rule``ã€ãŠã‚ˆã³ ``panos_set`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« `paloaltonetworks.panos collection <https://galaxy.ansible.com/paloaltonetworks/panos>`_ ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¾ã™ (https://github.com/ansible-collections/community.network/pull/176)。" + +#~ msgid "The redirect to the ``mellanox.onyx`` collection was removed for: the ``onyx`` cliconf plugin, terminal plugin, module_utils, action plugin, doc fragment, and the following modules: ``onyx_aaa``, ``onyx_bfd``, ``onyx_bgp``, ``onyx_buffer_pool``, ``onyx_command``, ``onyx_config``, ``onyx_facts``, ``onyx_igmp``, ``onyx_igmp_interface``, ``onyx_igmp_vlan``, ``onyx_interface``, ``onyx_l2_interface``, ``onyx_l3_interface``, ``onyx_linkagg``, ``onyx_lldp``, ``onyx_lldp_interface``, ``onyx_magp``, ``onyx_mlag_ipl``, ``onyx_mlag_vip``, ``onyx_ntp``, ``onyx_ntp_servers_peers``, ``onyx_ospf``, ``onyx_pfc_interface``, ``onyx_protocol``, ``onyx_ptp_global``, ``onyx_ptp_interface``, ``onyx_qos``, ``onyx_snmp``, ``onyx_snmp_hosts``, ``onyx_snmp_users``, ``onyx_syslog_files``, ``onyx_syslog_remote``, ``onyx_traffic_class``, ``onyx_username``, ``onyx_vlan``, ``onyx_vxlan``, ``onyx_wjh`` (https://github.com/ansible-collections/community.network/pull/175)." +#~ msgstr "``mellanox.onyx`` コレクションã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã¯ã€``onyx`` cliconf プラグインã€ã‚¿ãƒ¼ãƒŸãƒŠãƒ«ãƒ—ラグインã€module_utilsã€action プラグインã€doc フラグメントã€ãŠã‚ˆã³ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``onyx_aaa``ã€``onyx_bfd``ã€``onyx_bgp``ã€``onyx_buffer_pool``ã€``onyx_command``ã€``onyx_config``ã€``onyx_facts``ã€``onyx_igmp``ã€``onyx_igmp_interface``ã€``onyx_igmp_vlan``ã€``onyx_interface``ã€``onyx_l2_interface``ã€``onyx_l3_interface``ã€``onyx_linkagg``ã€``onyx_lldp``ã€``onyx_lldp_interface``ã€``onyx_magp``ã€``onyx_mlag_ipl``ã€``onyx_mlag_vip``ã€``onyx_ntp``ã€``onyx_ntp_servers_peers``ã€``onyx_ospf``ã€``onyx_pfc_interface``ã€``onyx_protocol``ã€``onyx_ptp_global``ã€``onyx_ptp_interface``ã€``onyx_qos``ã€``onyx_snmp``ã€``onyx_snmp_hosts``ã€``onyx_snmp_users``ã€``onyx_syslog_files``ã€``onyx_syslog_remote``ã€``onyx_traffic_class``ã€``onyx_username``ã€``onyx_vlan``ã€``onyx_vxlan``ã€ãŠã‚ˆã³ ``onyx_wjh`` ã«å¯¾ã—ã¦å‰Šé™¤ã•ã‚Œã¾ã—㟠(https://github.com/ansible-collections/community.network/pull/175)。" + +#~ msgid "The ``gluster_heal_info``, ``gluster_peer`` and ``gluster_volume`` modules have migrated to the `gluster.gluster <https://galaxy.ansible.com/gluster/gluster>`_ collection. Ansible-base 2.10.1 adjusted the routing target to point to the modules in that collection, so we will remove these modules in community.general 3.0.0. If you use Ansible 2.9, or use FQCNs ``community.general.gluster_*`` in your playbooks and/or roles, please update them to use the modules from ``gluster.gluster`` instead." +#~ msgstr "``gluster_heal_info`` モジュールã€``gluster_peer`` モジュールã€ãŠã‚ˆã³ ``gluster_volume`` モジュール㯠`gluster.gluster <https://galaxy.ansible.com/gluster/gluster>`_ コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚Ansible-base 2.10.1 ã§ã¯ã€ãƒ«ãƒ¼ãƒ†ã‚£ãƒ³ã‚°ã‚¿ãƒ¼ã‚²ãƒƒãƒˆãŒã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’å‚ç…§ã™ã‚‹ã‚ˆã†ã«èª¿æ•´ã•ã‚ŒãŸãŸã‚ã€community.general 3.0.0 ã§ã“れらã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’削除ã™ã‚‹äºˆå®šã§ã™ã€‚Ansible 2.9 を使用ã—ã¦ã„ã‚‹å ´åˆã‚„ã€Playbook ã‚„ãƒãƒ¼ãƒ«ã§ FQCN ã® ``community.general.gluster_*`` を使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ä»£ã‚ã‚Šã«ã“れらをアップデートã—㦠``gluster.gluster`` ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" + +#~ msgid "The ``dellemc_get_firmware_inventory`` module is deprecated and replaced with ``idrac_firmware_info``." +#~ msgstr "``dellemc_get_firmware_inventory`` モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€``idrac_firmware_info`` ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The ``dellemc_get_system_inventory`` module is deprecated and replaced with ``idrac_system_info``." +#~ msgstr "``dellemc_get_system_inventory`` モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€``idrac_system_info`` ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The dellemc_change_power_state module is deprecated and replaced with the redfish_powerstate module." +#~ msgstr "dellemc_change_power_state モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€redfish_powerstate モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The dellemc_configure_bios module is deprecated and replaced with the idrac_bios module." +#~ msgstr "dellemc_configure_bios モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_bios モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The dellemc_configure_idrac_network module is deprecated and replaced with the idrac_network module." +#~ msgstr "dellemc_configure_idrac_network モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_network モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The dellemc_configure_idrac_timezone module is deprecated and replaced with the idrac_timezone_ntp module." +#~ msgstr "dellemc_configure_idrac_timezone モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_timezone_ntp モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The dellemc_configure_idrac_users module is deprecated and replaced with the idrac_user module." +#~ msgstr "dellemc_configure_idrac_users モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_user モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The dellemc_delete_lc_job and dellemc_delete_lc_job_queue modules are deprecated and replaced with the idrac_lifecycle_controller_jobs module." +#~ msgstr "dellemc_delete_lc_job モジュールãŠã‚ˆã³ dellemc_delete_lc_job_queue モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_lifecycle_controller_jobs モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The dellemc_export_lc_logs module is deprecated and replaced with the idrac_lifecycle_controller_logs module." +#~ msgstr "dellemc_export_lc_logs モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_lifecycle_controller_logs モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The dellemc_get_lc_job_status module is deprecated and replaced with the idrac_lifecycle_controller_job_status_info module." +#~ msgstr "dellemc_get_lc_job_status モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_lifecycle_controller_job_status_info モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The dellemc_get_lcstatus module is deprecated and replaced with the idrac_lifecycle_controller_status_info module." +#~ msgstr "dellemc_get_lcstatus モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_lifecycle_controller_status_info モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The dellemc_idrac_reset module is deprecated and replaced with the idrac_reset module." +#~ msgstr "dellemc_idrac_reset モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_reset モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The dellemc_setup_idrac_syslog module is deprecated and replaced with the idrac_syslog module." +#~ msgstr "dellemc_setup_idrac_syslog モジュールã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€idrac_syslog モジュールã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "We suggest you read this page along with the `Ansible 4 Changelog <https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst>`_ to understand what updates you may need to make." +#~ msgstr "å¿…è¦ãªæ›´æ–°ã«ã¤ã„ã¦ç†è§£ã™ã‚‹ã«ã¯ã€ã“ã®ãƒšãƒ¼ã‚¸ã¨ä½µã›ã¦ã€Œ`Ansible 4 Changelog <https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "Porting Guide for v4.6.0" +#~ msgstr "v4.6.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" + +#~ msgid "containers.podman" +#~ msgstr "containers.podman" + +#~ msgid "Add systemd generation for pods" +#~ msgstr "Pod ã® systemd 生æˆã‚’è¿½åŠ " + +#~ msgid "Generate systemd service files for containers" +#~ msgstr "コンテナー㮠systemd サービスファイルã®ç”Ÿæˆ" + +#~ msgid "enable client.ssl,server.ssl before starting the gluster volume (https://github.com/gluster/gluster-ansible-collection/pull/19)" +#~ msgstr "gluster ボリュームを起動ã™ã‚‹å‰ã« client.ssl,server.ssl を有効ã«ã—ã¾ã™ï¼ˆhttps://github.com/gluster/gluster-ansible-collection/pull/19）。" + +#~ msgid "grafana_dashboard lookup - Providing a mangled version of the API key is no longer preferred." +#~ msgstr "grafana_dashboard lookup - API ã‚ー㮠mangled ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®æä¾›ã¯æŽ¨å¥¨ã•ã‚Œãªããªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "Porting Guide for v4.5.0" +#~ msgstr "v4.5.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" + +#~ msgid "hetzner.hcloud" +#~ msgstr "hetzner.hcloud" + +#~ msgid "Introduction of placement groups" +#~ msgstr "é…置グループã®æ¦‚è¦" + +#~ msgid "remove_stale_lun - Add role for removing stale LUN (https://bugzilla.redhat.com/1966873)." +#~ msgstr "remove_stale_lun - å¤ã„ LUN を削除ã™ã‚‹ãƒãƒ¼ãƒ«ã‚’è¿½åŠ ã—ã¾ã™ï¼ˆhttps://bugzilla.redhat.com/1966873）。" + +#~ msgid "network_cli - The paramiko_ssh setting ``look_for_keys`` was set automatically based on the values of the ``password`` and ``private_key_file`` options passed to network_cli. This option can now be set explicitly, and the automatic setting of ``look_for_keys`` will be removed after 2024-01-01 (https://github.com/ansible-collections/ansible.netcommon/pull/271)." +#~ msgstr "network_cli - paramiko_ssh è¨å®š ``look_for_keys`` ã¯ã€network_cli ã«æ¸¡ã•ã‚Œã‚‹ ``password`` オプションãŠã‚ˆã³ ``private_key_file`` オプションã®å€¤ã«åŸºã¥ã„ã¦è‡ªå‹•çš„ã«è¨å®šã•ã‚Œã¾ã™ã€‚ã“ã®ã‚ªãƒ—ションã¯æ˜Žç¤ºçš„ã«è¨å®šã§ãã€``look_for_keys`` ã®è‡ªå‹•è¨å®šã¯ 2024-01-01 以é™å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/ansible.netcommon/pull/271）。" + +#~ msgid "cisco.ios" +#~ msgstr "cisco.ios" + +#~ msgid "Deprecated ios_bgp in favor of ios_bgp_global and ios_bgp_address_family." +#~ msgstr "ios_bgp_global ãŒéžæŽ¨å¥¨ã¨ãªã‚Šã€ios_bgp 㯠ios_bgp_global ãŠã‚ˆã³ ios_bgp_address_family ãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "Remove testing with provider for ansible-test integration jobs. This helps prepare us to move to network-ee integration tests." +#~ msgstr "ansible-test çµ±åˆã‚¸ãƒ§ãƒ–ã®ãƒ—ãƒãƒã‚¤ãƒ€ãƒ¼ã§ãƒ†ã‚¹ãƒˆã‚’削除ã—ã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€network-eeçµ±åˆãƒ†ã‚¹ãƒˆã«ç§»è¡Œã™ã‚‹ã®ã«ä¾¿åˆ©ã§ã™ã€‚" + +#~ msgid "junipernetworks.junos" +#~ msgstr "junipernetworks.junos" + +#~ msgid "Deprecated router_id from ospfv3 resource module." +#~ msgstr "ospfv3 リソースモジュール㮠router_id ãŒéžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "Porting Guide for v4.4.0" +#~ msgstr "v4.4.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" + +#~ msgid "cisco.iosxr" +#~ msgstr "cisco.iosxr" + +#~ msgid "The iosxr_logging module has been deprecated in favor of the new iosxr_logging_global resource module and will be removed in a release after '2023-08-01'." +#~ msgstr "iosxr_logging モジュールãŒéžæŽ¨å¥¨ã¨ãªã‚Šã€'2023-08-01' ã®å¾Œã«ãƒªãƒªãƒ¼ã‚¹ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚æ–°ã—ã„ iosxr_logging_global リソースモジュールãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The nxos_logging module has been deprecated in favor of the new nxos_logging_global resource module and will be removed in a release after '2023-08-01'." +#~ msgstr "nxos_logging モジュールãŒéžæŽ¨å¥¨ã¨ãªã‚Šã€'2023-08-01' ã®å¾Œã«ãƒªãƒªãƒ¼ã‚¹ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚æ–°ã—ã„ nxos_logging_global リソースモジュールãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "docker_container - the new ``command_handling``'s default value, ``compatibility``, is deprecated and will change to ``correct`` in community.docker 3.0.0. A deprecation warning is emitted by the module in cases where the behavior will change. Please note that ansible-core will output a deprecation warning only once, so if it is shown for an earlier task, there could be more tasks with this warning where it is not shown (https://github.com/ansible-collections/community.docker/pull/186)." +#~ msgstr "docker_container - æ–°ã—ã„ ``command_handling``ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ ``compatibility`` ã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€community.docker 3.0.0 㧠``correct`` ã«å¤‰æ›´ã«ãªã‚Šã¾ã™ã€‚éžæŽ¨å¥¨ã®è¦å‘Šã¯ã€å‹•ä½œãŒå¤‰ã‚ã‚‹å ´åˆã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚ˆã£ã¦å‡ºåŠ›ã•ã‚Œã¾ã™ã€‚ansible-core ã¯éžæŽ¨å¥¨ã®è¦å‘Šã‚’一度ã ã‘出力ã™ã‚‹ãŸã‚ã€ä»¥å‰ã®ã‚¿ã‚¹ã‚¯ã§ã¯è¡¨ç¤ºã•ã‚Œãªã„å ´åˆã€è¡¨ç¤ºã•ã‚Œã¦ã„ãªã„å ´æ‰€ã§ã“ã®è¦å‘Šã§ã‚ˆã‚Šè¡¨ç¤ºã•ã‚Œã‚‹ã‚¿ã‚¹ã‚¯ãŒå¢—ãˆã‚‹å¯èƒ½æ€§ãŒã‚ã‚‹ã“ã¨ã«æ³¨æ„ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.docker/pull/186）。" + +#~ msgid "The junos_logging module has been deprecated in favor of the new junos_logging_global resource module and will be removed in a release after '2023-08-01'." +#~ msgstr "junos_logging モジュールãŒéžæŽ¨å¥¨ã¨ãªã‚Šã€'2023-08-01' ã®å¾Œã«ãƒªãƒªãƒ¼ã‚¹ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚æ–°ã—ã„ junos_logging_global リソースモジュールãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "vyos.vyos" +#~ msgstr "vyos.vyos" + +#~ msgid "The vyos_logging module has been deprecated in favor of the new vyos_logging_global resource module and will be removed in a release after \"2023-08-01\"." +#~ msgstr "vyos_logging モジュールãŒéžæŽ¨å¥¨ã¨ãªã‚Šã€'2023-08-01' ã®å¾Œã«ãƒªãƒªãƒ¼ã‚¹ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚æ–°ã—ã„ vyos_logging_global リソースモジュールãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "Porting Guide for v4.3.0" +#~ msgstr "v4.3.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" + +#~ msgid "netapp.cloudmanager" +#~ msgstr "netapp.cloudmanager" + +#~ msgid "Adding stage environment to all modules in cloudmanager" +#~ msgstr "cloudmanager ã®ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¸ã®ã‚¹ãƒ†ãƒ¼ã‚¸ç’°å¢ƒã®è¿½åŠ " + +#~ msgid "hashi_vault collection - support for Python 3.5 will be dropped in version ``2.0.0`` of ``community.hashi_vault`` (https://github.com/ansible-collections/community.hashi_vault/issues/81)." +#~ msgstr "hashi_vault コレクション - Python3.5ã®ã‚µãƒãƒ¼ãƒˆãŒãƒãƒ¼ã‚¸ãƒ§ãƒ³``2.0.0``ã®``community.hashi_vault``ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.hashi_vault/issues/81）。" + +#~ msgid "Porting Guide for v4.2.0" +#~ msgstr "v4.2.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" + +#~ msgid "vmware_object_custom_attributes_info - added a new module to gather custom attributes of an object (https://github.com/ansible-collections/community.vmware/pull/851)." +#~ msgstr "vmware_object_custom_attributes_info - オブジェクトã®ã‚«ã‚¹ã‚¿ãƒ 属性をåŽé›†ã™ã‚‹æ–°ã—ã„モジュールãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.vmware/pull/851）。" + +#~ msgid "idrac_server_config_profile - Added support for exporting and importing Server Configuration Profile through HTTP/HTTPS share." +#~ msgstr "idrac_server_config_profile - HTTP/HTTPS 共有ã§ã®ã‚µãƒ¼ãƒãƒ¼è¨å®šãƒ—ãƒãƒ•ã‚¡ã‚¤ãƒ«ã®ã‚¨ã‚¯ã‚¹ãƒãƒ¼ãƒˆãŠã‚ˆã³ã‚¤ãƒ³ãƒãƒ¼ãƒˆã®ã‚µãƒãƒ¼ãƒˆãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "ome_device_group - Added support for adding devices to a group using the IP addresses of the devices and group ID." +#~ msgstr "ome_device_group - デãƒã‚¤ã‚¹ãŠã‚ˆã³ã‚°ãƒ«ãƒ¼ãƒ— ID ã® IP アドレスを使用ã—ã¦ã€ãƒ‡ãƒã‚¤ã‚¹ã‚’グループã«è¿½åŠ ã™ã‚‹ãŸã‚ã®ã‚µãƒãƒ¼ãƒˆãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "fortinet.fortios" +#~ msgstr "fortinet.fortios" + +#~ msgid "New module fortios_monitor_fact." +#~ msgstr "æ–°ã—ã„モジュール fortios_monitor_fact。" + +#~ msgid "Support Fortios 7.0." +#~ msgstr "Fortios 7.0 をサãƒãƒ¼ãƒˆã—ã¾ã™ã€‚" + +#~ msgid "Support Log APIs." +#~ msgstr "ãƒã‚° API をサãƒãƒ¼ãƒˆã—ã¾ã™ã€‚" + +#~ msgid "The community.kubernetes collection is being renamed to kubernetes.core. In Ansible 5, community.kubernetes will be replaced by an empty collection which has deprecated redirects for all the current content to kubernetes.core. If you are using FQCNs starting with ``community.kubernetes.``, please update them to ``kubernetes.core.`` now. Note that kubernetes.core has been included in Ansible since Ansible 3.0.0 (https://github.com/ansible-community/community-topics/issues/22)." +#~ msgstr "community.kubernetes コレクション㯠kubernetes.core ã«å¤‰æ›´ã•ã‚Œã¾ã—ãŸã€‚Ansible 5 ã§ã¯ã€community.kubernetes ã¯ã€ç¾åœ¨ã®ã™ã¹ã¦ã®ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã‚’ kubernetes.core ã«ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã™ã‚‹ç©ºã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚FQCN を使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``community.kubernetes.`` ã§å§‹ã¾ã‚‹ FQCN ã‚’ ``kubernetes.core.`` ã«æ›´æ–°ã—ã¦ãã ã•ã„。Ansible 3.0.0 以é™ã€kubernetes.core 㯠Ansible ã«çµ„ã¿è¾¼ã¾ã‚Œã¦ã„る点ã«æ³¨æ„ã—ã¦ãã ã•ã„（https://github.com/ansible-community/community-topics/issues/22）。" + +#~ msgid "win_updates - Deprecated the ``filtered_reason`` return value for each filtered up in favour of ``filtered_reasons``. This has been done to show all the reasons why an update was filtered and not just the first reason." +#~ msgstr "win_updates - フィルター処ç†ã•ã‚ŒãŸãã‚Œãžã‚Œã®``filtered_reason``戻り値ãŒéžæŽ¨å¥¨ã«ãªã‚Šã€``filtered_reasons``ãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚ã“ã‚Œã¯ã€æœ€åˆã®ç†ç”±ã ã‘ã§ãªãã€æ›´æ–°ãŒãƒ•ã‚£ãƒ«ã‚¿ãƒªãƒ³ã‚°ã•ã‚ŒãŸã™ã¹ã¦ã®ç†ç”±ã‚’示ã™ãŸã‚ã«è¡Œã‚ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "win_updates - Deprecated the ``use_scheduled_task`` option as it is no longer used." +#~ msgstr "win_updates - 使用ã•ã‚Œãªããªã£ãŸ ``use_scheduled_task`` オプションãŒéžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "win_updates - Deprecated the ``whitelist`` and ``blacklist`` options in favour of ``accept_list`` and ``reject_list`` respectively to conform to the new standards used in Ansible for these types of options." +#~ msgstr "win_updates - ``whitelist`` オプションãŠã‚ˆã³ ``blacklist`` オプションãŒéžæŽ¨å¥¨ã«ãªã‚Šã¾ã—ãŸã€‚オプションã®ç¨®é¡žã«ã¤ã„㦠Ansible ã§ä½¿ç”¨ã•ã‚Œã‚‹æ–°ã—ã„標準ã«æº–æ‹ ã™ã‚‹ãŸã‚ã«ãã‚Œãžã‚Œ ``accept_list`` 㨠``reject_list`` ãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "ali_instance_info - marked removal version of deprecated parameters ``availability_zone`` and ``instance_names`` (https://github.com/ansible-collections/community.general/issues/2429)." +#~ msgstr "ali_instance_info - éžæŽ¨å¥¨ã®ãƒ‘ラメーター``availability_zone``ã¨``instance_names``ã®å‰Šé™¤ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒç¤ºã•ã‚Œã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.general/issues/2429）。" + +#~ msgid "serverless - deprecating parameter ``functions`` because it was not used in the code (https://github.com/ansible-collections/community.general/pull/2845)." +#~ msgstr "serverless - コードã§ä½¿ç”¨ã•ã‚Œã¦ã„ãªã„ãŸã‚パラメーター ``functions`` ã‚’éžæŽ¨å¥¨åŒ–（https://github.com/ansible-collections/community.general/pull/2845）。" + +#~ msgid "hashi_vault collection - support for Python 2 will be dropped in version ``2.0.0`` of ``community.hashi_vault`` (https://github.com/ansible-collections/community.hashi_vault/issues/81)." +#~ msgstr "hashi_vault コレクション - Python 2 ã®ã‚µãƒãƒ¼ãƒˆãŒãƒãƒ¼ã‚¸ãƒ§ãƒ³``2.0.0``ã®``community.hashi_vault``ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.hashi_vault/issues/81).）。" + +#~ msgid "Porting Guide for v4.1.0" +#~ msgstr "v4.1.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" + +#~ msgid "Add custom_image module" +#~ msgstr "custom_image モジュールã®è¿½åŠ " + +#~ msgid "ome_firmware_baseline - Module supports check mode, and allows the modification and deletion of firmware baselines." +#~ msgstr "ome_firmware_baseline - モジュールã¯ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã‚’サãƒãƒ¼ãƒˆã—ã€ãƒ•ã‚¡ãƒ¼ãƒ ウェアベースラインã®å¤‰æ›´ã‚„削除をå¯èƒ½ã«ã—ã¾ã™ã€‚" + +#~ msgid "ome_firmware_catalog - Module supports check mode, and allows the modification and deletion of firmware catalogs." +#~ msgstr "ome_firmware_catalog - モジュールã¯ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã‚’サãƒãƒ¼ãƒˆã—ã€ãƒ•ã‚¡ãƒ¼ãƒ ウェアカタãƒã‚°ã®å¤‰æ›´ã‚„削除をå¯èƒ½ã«ã—ã¾ã™ã€‚" + +#~ msgid "Improve ``fortios_configuration_fact`` to use multiple selectors concurrently." +#~ msgstr "複数ã®ã‚»ãƒ¬ã‚¯ã‚¿ãƒ¼ã‚’åŒæ™‚ã«ä½¿ç”¨ã™ã‚‹ã‚ˆã†ã« ``fortios_configuration_fact`` を改善ã—ã¾ã™ã€‚" + +#~ msgid "Support ``check_mode`` in all cofigurationAPI-based modules." +#~ msgstr "ã™ã¹ã¦ã® cofigurationAPI ベースã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã® ``check_mode`` をサãƒãƒ¼ãƒˆã—ã¾ã™ã€‚" + +#~ msgid "Support filtering for fact gathering modules ``fortios_configuration_fact`` and ``fortios_monitor_fact``." +#~ msgstr "ファクトåŽé›†ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« ``fortios_configuration_fact`` ãŠã‚ˆã³ ``fortios_monitor_fact`` ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒªãƒ³ã‚°ã‚’サãƒãƒ¼ãƒˆã—ã¾ã™ã€‚" + +#~ msgid "Support moving policy in ``firewall_central_snat_map``." +#~ msgstr "``firewall_central_snat_map`` ã§ã®ç§»è¡Œãƒãƒªã‚·ãƒ¼ã®ã‚µãƒãƒ¼ãƒˆ" + +#~ msgid "Unify schemas for monitor API." +#~ msgstr "モニター API ã®ã‚¹ã‚ーマã®çµ±ä¸€" + +#~ msgid "packages is now a required Python package and gets installed via Ansible 2.10+." +#~ msgstr "パッケージãŒå¿…è¦ãª Python パッケージã«ãªã‚Šã€Ansible 2.10 以é™ã‹ã‚‰ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "win_reboot - Removed ``shutdown_timeout`` and ``shutdown_timeout_sec`` which has not done anything since Ansible 2.5." +#~ msgstr "win_reboot - ``shutdown_timeout`` ãŠã‚ˆã³ ``shutdown_timeout_sec`` を削除ã—ã¾ã—ãŸãŒã€Ansible 2.5 以é™ã¯å®Ÿè¡Œã•ã‚Œã¦ã„ã¾ã›ã‚“。" + +#~ msgid "win_reboot - Unreachable hosts can be ignored with ``ignore_errors: True``, this ability will be removed in a future version. Use ``ignore_unreachable: True`` to ignore unreachable hosts instead. - https://github.com/ansible-collections/ansible.windows/issues/62" +#~ msgstr "win_reboot - ``ignore_errors: True`` ã§åˆ°é”ã§ããªã„ホストを無視ã§ãã¾ã™ã€‚ã“ã®æ©Ÿèƒ½ã¯ä»Šå¾Œã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚代ã‚ã‚Šã« ``ignore_unreachable: True`` を使用ã—ã¦ã€åˆ°é”ä¸èƒ½ãªãƒ›ã‚¹ãƒˆã‚’無視ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/ansible.windows/issues/62）。" + +#~ msgid "All inventory and vault scripts will be removed from community.general in version 4.0.0. If you are referencing them, please update your references to the new `contrib-scripts GitHub repository <https://github.com/ansible-community/contrib-scripts>`_ so your workflow will not break once community.general 4.0.0 is released (https://github.com/ansible-collections/community.general/pull/2697)." +#~ msgstr "インベントリーãŠã‚ˆã³ vault スクリプトã¯ã™ã¹ã¦ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 4.0.0 ã® community.general ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚ãれらをå‚ç…§ã™ã‚‹å ´åˆã¯ã€æ–°ã—ã„ `contrib-scripts GitHub repository <https://github.com/ansible-community/contrib-scripts>`_ ã¸ã®å‚照を更新ã—ã¦ãã ã•ã„。ã“ã‚Œã«ã‚ˆã‚Šã€community.general 4.0.0 ãŒãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã¦ã‚‚ワークフãƒãƒ¼ãŒç ´æã™ã‚‹ã“ã¨ã¯ã‚ã‚Šã¾ã›ã‚“（https://github.com/ansible-collections/community.general/pull/2697）" + +#~ msgid "The nios, nios_next_ip, nios_next_network lookup plugins, the nios documentation fragment, and the nios_host_record, nios_ptr_record, nios_mx_record, nios_fixed_address, nios_zone, nios_member, nios_a_record, nios_aaaa_record, nios_network, nios_dns_view, nios_txt_record, nios_naptr_record, nios_srv_record, nios_cname_record, nios_nsgroup, and nios_network_view module have been deprecated and will be removed from community.general 5.0.0. Please install the `infoblox.nios_modules <https://galaxy.ansible.com/infoblox/nios_modules>`_ collection instead and use its plugins and modules (https://github.com/ansible-collections/community.general/pull/2458)." +#~ msgstr "niosã€nios_next_ipã€nios_next_networkルックアッププラグインã€niosドã‚ュメントフラグメントã€ãŠã‚ˆã³nios_host_recordã€nios_ptr_recordã€nios_mx_recordã€nios_fixed_addressã€nios_zoneã€nios_memberã€nios_a_recordã€nios_aaaa_recordã€nios_networkã€nios_dns_viewã€nios_txt_recordã€nios_naptr_recordã€nios_srv_recordã€nios_cname_recordã€nios_nsgroupã€ãŠã‚ˆã³ nios_network_view モジュールã¯éžæŽ¨å¥¨ã«ãªã‚Šã€community.general 5.0.0ã‹ã‚‰å‰Šé™¤ã•ã‚Œã¾ã™ã€‚代ã‚ã‚Šã« `infoblox.nios_modules <https://galaxy.ansible.com/infoblox/nios_modules>`_ をインストールã—ã€ãã®ãƒ—ラグインã¨ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/2458）。" + +#~ msgid "The vendored copy of ``ipaddress`` will be removed in community.general 4.0.0. Please switch to ``ipaddress`` from the Python 3 standard library, or `from pypi <https://pypi.org/project/ipaddress/>`_, if your code relies on the vendored version of ``ipaddress`` (https://github.com/ansible-collections/community.general/pull/2459)." +#~ msgstr "``ipaddress`` ã®ãƒ™ãƒ³ãƒ€ãƒ¼ã‚³ãƒ”ーã¯ã€community.general 4.0.0 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚Python 3 標準ライブラリーã‹ã‚‰ ``ipaddress`` ã«åˆ‡ã‚Šæ›¿ãˆã‚‹ã‹ã€ã‚³ãƒ¼ãƒ‰ãŒãƒ™ãƒ³ãƒ€ãƒ¼ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® ``ipaddress`` ã«ä¾å˜ã—ã¦ã„ã‚‹å ´åˆã¯ `from pypi <https://pypi.org/project/ipaddress/>`_ ã«åˆ‡ã‚Šæ›¿ãˆã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/2459。" + +#~ msgid "linode - parameter ``backupsenabled`` is deprecated and will be removed in community.general 5.0.0 (https://github.com/ansible-collections/community.general/pull/2410)." +#~ msgstr "linode - パラメーター``backupsenabled``ã¯éžæŽ¨å¥¨ã«ãªã‚Šã€community.general 5.0.0ã§å‰Šé™¤ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/2410）。" + +#~ msgid "lxd inventory plugin - the plugin will require ``ipaddress`` installed when used with Python 2 from community.general 4.0.0 on. ``ipaddress`` is part of the Python 3 standard library, but can be installed for Python 2 from pypi (https://github.com/ansible-collections/community.general/pull/2459)." +#~ msgstr "lxd inventory プラグイン - プラグイン㯠community.general 4.0.0 ã® Python 2 ã§ä½¿ç”¨ã™ã‚‹éš›ã« ``ipaddress`` をインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚``ipaddress`` 㯠Python 3 標準ライブラリーã®ä¸€éƒ¨ã§ã™ãŒã€pypi ã‹ã‚‰ Python 2 用ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ãã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/2459）。" + +#~ msgid "scaleway_security_group_rule - the module will require ``ipaddress`` installed when used with Python 2 from community.general 4.0.0 on. ``ipaddress`` is part of the Python 3 standard library, but can be installed for Python 2 from pypi (https://github.com/ansible-collections/community.general/pull/2459)." +#~ msgstr "scaleway_security_group_rule - モジュールã¯ã€community.general 4.0.0 ã® Python 2 ã§ä½¿ç”¨ã™ã‚‹éš›ã« ``ipaddress`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚``ipaddress`` 㯠Python 3 標準ライブラリーã®ä¸€éƒ¨ã§ã™ãŒã€pypi ã‹ã‚‰ Python 2 用ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ãã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/2459）。" + +#~ msgid "inspur.sm" +#~ msgstr "inspur.sm" + +#~ msgid "add_ad_group - This feature will be removed in inspur.sm.add_ad_group 3.0.0. replaced with inspur.sm.ad_group." +#~ msgstr "add_ad_group - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.add_ad_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.ad_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã‚‹äºˆå®šã§ã™ã€‚" + +#~ msgid "add_ldap_group - This feature will be removed in inspur.sm.add_ldap_group 3.0.0. replaced with inspur.sm.ldap_group." +#~ msgstr "add_ldap_group - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.add_ldap_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.ldap_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚" + +#~ msgid "add_user - This feature will be removed in inspur.sm.add_user 3.0.0. replaced with inspur.sm.user." +#~ msgstr "add_user - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.add_user 3.0.0. ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.user ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚" + +#~ msgid "add_user_group - This feature will be removed in inspur.sm.add_user_group 3.0.0. replaced with inspur.sm.user_group." +#~ msgstr "add_user_group - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.add_user_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.user_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚" + +#~ msgid "del_ad_group - This feature will be removed in inspur.sm.del_ad_group 3.0.0. replaced with inspur.sm.ad_group." +#~ msgstr "del_ad_group - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.del_ad_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.ad_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚" + +#~ msgid "del_ldap_group - This feature will be removed in inspur.sm.del_ldap_group 3.0.0. replaced with inspur.sm.ldap_group." +#~ msgstr "del_ldap_group - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.del_ldap_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.ldap_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚" + +#~ msgid "del_user - This feature will be removed in inspur.sm.del_user 3.0.0. replaced with inspur.sm.user." +#~ msgstr "del_user - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.del_user 3.0.0. ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.user ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚" + +#~ msgid "del_user_group - This feature will be removed in inspur.sm.del_user_group 3.0.0. replaced with inspur.sm.user_group." +#~ msgstr "del_user_group - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.del_user_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.user_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ã€‚" + +#~ msgid "edit_ad_group - This feature will be removed in inspur.sm.edit_ad_group 3.0.0. replaced with inspur.sm.ad_group." +#~ msgstr "edit_ad_group - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.edit_ad_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.ad_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã‚‹äºˆå®šã§ã™ã€‚" + +#~ msgid "edit_ldap_group - This feature will be removed in inspur.sm.edit_ldap_group 3.0.0. replaced with inspur.sm.ldap_group." +#~ msgstr "edit_ldap_group - ã“ã®æ©Ÿèƒ½ã¯ã€inspur.sm.edit_ldap_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.ldap_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã‚‹äºˆå®šã§ã™ã€‚" + +#~ msgid "edit_user - This feature will be removed in inspur.sm.edit_user 3.0.0. replaced with inspur.sm.user." +#~ msgstr "edit_user - ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.edit_user 3.0.0. ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.user ã«ç½®ãæ›ãˆã‚‰ã‚Œã‚‹äºˆå®šã§ã™ã€‚" + +#~ msgid "edit_user_group - This feature will be removed in inspur.sm.edit_user_group 3.0.0. replaced with inspur.sm.user_group." +#~ msgstr "edit_user_group: ã“ã®æ©Ÿèƒ½ã¯ inspur.sm.edit_user_group 3.0.0 ã§å‰Šé™¤ã•ã‚Œã€inspur.sm.user_group ã«ç½®ãæ›ãˆã‚‰ã‚Œã‚‹äºˆå®šã§ã™ã€‚" + +#~ msgid "Porting Guide for v4.0.0" +#~ msgstr "v4.0.0 ã®ç§»æ¤ã‚¬ã‚¤ãƒ‰" + +#~ msgid "Ansible-core" +#~ msgstr "Ansible-core" + +#~ msgid "ansible-test - The ``pylint`` sanity test no longer correctly detects \"bad\" variable names for non-constants. See https://github.com/PyCQA/pylint/issues/3701 for additional details." +#~ msgstr "ansible-test - ``pylint`` å¥å…¨æ€§ãƒ†ã‚¹ãƒˆã¯ã€éžåˆ¶ç´„ã®ãŸã‚\"bad\" 変数åã‚’æ£ã—ã検出ã—ãªããªã‚Šã¾ã—ãŸã€‚詳細ã¯ã€https://github.com/PyCQA/pylint/issues/3701 ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "Modules for monitor API are not versioned yet." +#~ msgstr "モニター API 用ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã¾ã ãƒãƒ¼ã‚¸ãƒ§ãƒ³åŒ–ã•ã‚Œã¦ã„ã¾ã›ã‚“。" + +#~ msgid "Made SCM collections be reinstalled regardless of ``--force`` being present." +#~ msgstr "作æˆã•ã‚ŒãŸ SCM コレクションã¯ã€``--force`` ãŒå˜åœ¨ã™ã‚‹ã‹ã©ã†ã‹ã«é–¢ã‚らãšå†ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "NetBSD virtualization facts (specifically ``ansible_virtualization_type``) now returns a more accurate value by checking the value of the ``machdep.hypervisor`` ``sysctl`` key. This change is breaking because in some cases previously, we would erroneously report ``xen`` even when the target is not running on Xen. This prevents that behavior in most cases. (https://github.com/ansible/ansible/issues/69352)" +#~ msgstr "NetBSD 仮想化ファクト（具体的ã«ã¯ ``ansible_virtualization_type``）ã¯ã€``machdep.hypervisor`` ``sysctl`` ã‚ーã®å€¤ã‚’ãƒã‚§ãƒƒã‚¯ã™ã‚‹ã“ã¨ã§ã€ã‚ˆã‚Šæ£ç¢ºãªå€¤ã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚以å‰ã¯ã€ã‚¿ãƒ¼ã‚²ãƒƒãƒˆãŒ Xen ã§å®Ÿè¡Œã—ã¦ã„ãªã„å ´åˆã§ã‚‚ ``xen``を誤ã£ã¦å ±å‘Šã—ã¦ã„ãŸãŸã‚ã€ã“ã®å¤‰æ›´ã¯é‡è¦ã§ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ã»ã¨ã‚“ã©ã®å ´åˆã€ãã®å‹•ä½œãŒé˜»æ¢ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible/ansible/issues/69352）。" + +#~ msgid "Replaced the in-tree dependency resolver with an external implementation that pip >= 20.3 uses now by default — ``resolvelib``. (https://github.com/ansible/ansible/issues/71784)" +#~ msgstr "ツリー内ã®ä¾å˜é–¢ä¿‚リゾルãƒãƒ¼ãŒã€pip> = 20.3ãŒãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ä½¿ç”¨ã™ã‚‹å¤–部実装``resolvelib``ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã—ãŸï¼ˆhttps://github.com/ansible/ansible/issues/71784。" + +#~ msgid "The ``meta`` module now supports tags for user-defined tasks. Internal ``meta`` tasks continue to always run. (https://github.com/ansible/ansible/issues/64558)" +#~ msgstr "``meta`` モジュールã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼å®šç¾©ã®ã‚¿ã‚¹ã‚¯ã®ã‚¿ã‚°ã‚’サãƒãƒ¼ãƒˆã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚内部 ``meta`` タスクã¯å¸¸ã«å®Ÿè¡Œã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible/ansible/issues/64558）。" + +#~ msgid "Removed vendored ipaddress package from collection. If you use ansible_collections.ansible.netcommon.plugins.module_utils.compat.ipaddress in your collection, you will need to change this to import ipaddress instead. If your content using ipaddress supports Python 2.7, you will additionally need to make sure that the user has the ipaddress package installed. Please refer to https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_best_practices.html#importing-and-using-shared-code to see how to safely import external packages that may be missing from the user's system A backport of ipaddress for Python 2.7 is available at https://pypi.org/project/ipaddress/" +#~ msgstr "コレクションã‹ã‚‰ãƒ™ãƒ³ãƒ€ãƒ¼åŒ–ã•ã‚ŒãŸ ipaddress パッケージãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚コレクションã®ansible_collections.ansible.netcommon.plugins.module_utils.compat.ipaddress を使用ã™ã‚‹å ´åˆã¯ã€ä»£ã‚ã‚Šã« ipaddress をインãƒãƒ¼ãƒˆã™ã‚‹ãŸã‚ã«ã“れを変更ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ipaddress を使用ã™ã‚‹ã‚³ãƒ³ãƒ†ãƒ³ãƒ„㌠Python 2.7 ã«å¯¾å¿œã—ã¦ã„ã‚‹å ´åˆã¯ã€ã•ã‚‰ã«ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒ ipaddress パッケージãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ユーザーã®ã‚·ã‚¹ãƒ†ãƒ A ã«æ¬ è½ã—ã¦ã„ã‚‹å¯èƒ½æ€§ã®ã‚る外部パッケージを安全ã«ã‚¤ãƒ³ãƒãƒ¼ãƒˆã™ã‚‹æ–¹æ³•ã«ã¤ã„ã¦ã¯ã€https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_best_practices.html#importing-and-using-shared-codeã‚’å‚ç…§ã—ã¦ãã ã•ã„。Python 2.7用ã®ipaddressã®ãƒãƒƒã‚¯ãƒãƒ¼ãƒˆã¯ã€https://pypi.org/project/ipaddress/ã§åˆ©ç”¨ã§ãã¾ã™ã€‚" + +#~ msgid "If you use Ansible 2.9 and these plugins or modules from this collection, community.general 3.0.0 results in errors when trying to use the DellEMC content by FQCN, like ``community.general.idrac_firmware``. Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``dellemc.openmanage.idrac_firmware`` for the previous example) and to make sure that you have ``dellemc.openmanage`` installed." +#~ msgstr "Ansible 2.9 ã¨ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒ—ラグインやモジュールを使用ã—ã¦ã„ã‚‹å ´åˆã€community.general 3.0.0 ã§ã¯ã€``community.general.idrac_firmware`` ã®ã‚ˆã†ã« FQCN ã«ã‚ˆã‚‹ DellEMC コンテンツを使用ã—よã†ã¨ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚Ansible 2.9 ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ããªã„ãŸã‚ã€æ–°ã—ã„ FQCN (å‰ã®ä¾‹ã§ã¯ ``dellemc.openmanage.idrac_firmware``) を使用ã—ã€``dellemc.openmanage`` ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã™ã‚‹ãŸã‚ã«ã€Playbook ã¨ãƒãƒ¼ãƒ«ã‚’手動ã§èª¿æ•´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "If you use ansible-base 2.10 or newer and did not install Ansible 4.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install the ``dellemc.openmanage`` collection if you are using any of these plugins or modules. While ansible-base 2.10 or newer can use the redirects that community.general 3.0.0 adds, the collection they point to (such as dellemc.openmanage) must be installed for them to work." +#~ msgstr "ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã¦ã€Ansible 4.0.0 をインストールã›ãšã€æ‰‹å‹•ã§ community.general をインストール (ã¾ãŸã¯ã‚¢ãƒƒãƒ—グレード) ã—ã€ã“ã®ãƒ—ラグインã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€``dellemc.openmanage`` コレクションもインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ansible-base 2.10 以é™ã§ã¯ã€community.general 3.0.0 ãŒè¿½åŠ ã—ãŸãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (dellemc.openmanage ãªã©) ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ã¨å‹•ä½œã—ã¾ã›ã‚“。" + +#~ msgid "gitlab_deploy_key - if for an already existing key title a different public key was given as parameter nothing happened, now this changed so that the public key is updated to the new value (https://github.com/ansible-collections/community.general/pull/1661)." +#~ msgstr "gitlab_deploy_key - æ—¢å˜ã®éµã‚¿ã‚¤ãƒˆãƒ«ã«å¯¾ã—ã¦ã€ãƒ‘ラメーターã¨ã—ã¦åˆ¥ã®å…¬é–‹éµãŒä½•ã‚‚èµ·ã“らãªã‹ã£ãŸå ´åˆã€ã“ã‚ŒãŒå¤‰æ›´ã•ã‚Œã€å…¬é–‹éµãŒæ–°ã—ã„値ã«æ›´æ–°ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1661）。" + +#~ msgid "java_keystore - instead of failing, now overwrites keystore if the alias (name) is changed. This was originally the intended behavior, but did not work due to a logic error. Make sure that your playbooks and roles do not depend on the old behavior of failing instead of overwriting (https://github.com/ansible-collections/community.general/issues/1671)." +#~ msgstr "java_keystore - 失敗ã™ã‚‹ä»£ã‚ã‚Šã«ã€ã‚¨ã‚¤ãƒªã‚¢ã‚¹ï¼ˆåå‰ï¼‰ãŒå¤‰æ›´ã—ãŸå ´åˆã«ã‚ーストアを上書ãã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã¯å…ƒã€…æ„図ã•ã‚ŒãŸå‹•ä½œã§ã—ãŸãŒã€è«–ç†ã‚¨ãƒ©ãƒ¼ã®ãŸã‚ã«æ©Ÿèƒ½ã—ã¾ã›ã‚“ã§ã—ãŸã€‚Playbook ã¨ãƒãƒ¼ãƒ«ãŒã€ä¸Šæ›¸ãã™ã‚‹ä»£ã‚ã‚Šã«å¤±æ•—ã™ã‚‹ã¨ã„ã†å¤ã„動作ã«ä¾å˜ã—ã¦ã„ãªã„ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/issues/1671）。" + +#~ msgid "java_keystore - instead of failing, now overwrites keystore if the passphrase is changed. Make sure that your playbooks and roles do not depend on the old behavior of failing instead of overwriting (https://github.com/ansible-collections/community.general/issues/1671)." +#~ msgstr "java_keystore - 失敗ã™ã‚‹ä»£ã‚ã‚Šã«ã€ãƒ‘スフレーズãŒå¤‰æ›´ã—ãŸå ´åˆã«ã‚ーストアを上書ãã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚Playbook ã¨ãƒãƒ¼ãƒ«ãŒã€ä¸Šæ›¸ãã™ã‚‹ä»£ã‚ã‚Šã«å¤±æ•—ã™ã‚‹ã¨ã„ã†å¤ã„動作ã«ä¾å˜ã—ã¦ã„ãªã„ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/issues/1671）。" + +#~ msgid "one_image - use pyone instead of python-oca (https://github.com/ansible-collections/community.general/pull/2032)." +#~ msgstr "one_image - python-oca ã®ä»£ã‚ã‚Šã« pyone を使用ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/2032）。" + +#~ msgid "Generic FortiOS Module - FOS module to issue generic request with Ansible." +#~ msgstr "汎用 FortiOS モジュール - Ansible ã§æ±Žç”¨è¦æ±‚を発行ã™ã‚‹ãŸã‚ã® FOS モジュール。" + +#~ msgid "Support for FOS Monitor API - several modules are new for monitor API." +#~ msgstr "FOS Monitor API ã®ã‚µãƒãƒ¼ãƒˆ - 複数ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒãƒ¢ãƒ‹ã‚¿ãƒ¼ API 用ã«æ–°ãŸã«è¿½åŠ ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "Unified Collection - The fortios collection itself will be adapting any FOS platforms." +#~ msgstr "çµ±åˆã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ - fortios コレクション自体ãŒã€FOS プラットフォームã«é©å¿œã—ã¾ã™ã€‚" + +#~ msgid "auth field now required for anything other than Basic authentication" +#~ msgstr "Basic èªè¨¼ä»¥å¤–ã®ã™ã¹ã¦ã®ãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ã«èªè¨¼ãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ãŒå¿…è¦ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "All role variables are now prefixed with ``foreman_`` to avoid clashes with similarly named variables from roles outside this collection." +#~ msgstr "ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³å¤–ã®ãƒãƒ¼ãƒ«ã‹ã‚‰ã®åŒæ§˜ã®åå‰ã®å¤‰æ•°ã¨ã®è¡çªã‚’回é¿ã™ã‚‹ãŸã‚ã€ã™ã¹ã¦ã®ãƒãƒ¼ãƒ«å¤‰æ•°ã«ã¯ ``foreman_`` ã®ãƒ—レフィックスãŒä»˜ã‘られã¾ã—ãŸã€‚" + +#~ msgid "A collection can be reinstalled with new version requirements without using the ``--force`` flag. The collection's dependencies will also be updated if necessary with the new requirements. Use ``--upgrade`` to force transitive dependency updates." +#~ msgstr "コレクションã¯ã€``--force`` フラグを使用ã›ãšã«ã€æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®è¦ä»¶ã§å†ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ãã¾ã™ã€‚ã¾ãŸã€æ–°ã—ã„è¦ä»¶ã§å¿…è¦ãªå ´åˆã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ä¾å˜é–¢ä¿‚ã‚‚æ›´æ–°ã•ã‚Œã¾ã™ã€‚``--upgrade`` を使用ã—ã¦ã€æŽ¨ç§»çš„ãªä¾å˜é–¢ä¿‚ã®æ›´æ–°ã‚’強制ã—ã¾ã™ã€‚" + +#~ msgid "AnsibleModule - use ``ArgumentSpecValidator`` class for validating argument spec and remove private methods related to argument spec validation. Any modules using private methods should now use the ``ArgumentSpecValidator`` class or the appropriate validation function." +#~ msgstr "AnsibleModule - 引数仕様を検証ã™ã‚‹ãŸã‚ã« ``ArgumentSpecValidator`` クラスを使用ã—ã€å¼•æ•°ä»•æ§˜ã®æ¤œè¨¼ã«é–¢é€£ã™ã‚‹ãƒ—ライベートメソッドを削除ã—ã¾ã™ã€‚プライベートメソッドを使用ã™ã‚‹ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€``ArgumentSpecValidator`` クラスã¾ãŸã¯é©åˆ‡ãªæ¤œè¨¼æ©Ÿèƒ½ã‚’使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "Declared ``resolvelib >= 0.5.3, < 0.6.0`` a direct dependency of ansible-core. Refs: - https://github.com/sarugaku/resolvelib - https://pypi.org/p/resolvelib - https://pradyunsg.me/blog/2020/03/27/pip-resolver-testing" +#~ msgstr "ansible-core ã®ç›´æŽ¥ã®ä¾å˜é–¢ä¿‚``resolvelib >= 0.5.3, < 0.6.0`` ãŒå®£è¨€ã•ã‚Œã¾ã™ã€‚https://github.com/sarugaku/resolvelibã€https://pypi.org/p/resolvelibã€https://pradyunsg.me/blog/2020/03/27/pip-resolver-testing ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "It became possible to install Ansible Collections from local folders and namespaces folder similar to SCM structure with multiple collections." +#~ msgstr "複数ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’æŒã¤ SCM æ§‹é€ ã¨åŒæ§˜ã«ã€ãƒãƒ¼ã‚«ãƒ«ãƒ•ã‚©ãƒ«ãƒ€ãƒ¼ãŠã‚ˆã³ namespace フォルダーã‹ã‚‰ Ansible Collections をインストールã§ãるよã†ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "It became possible to upgrade Ansible collections from Galaxy servers using the ``--upgrade`` option with ``ansible-galaxy collection install``." +#~ msgstr "``ansible-galaxy collection install`` 㧠``--upgrade`` オプションを使用ã—ã¦ã€Galaxy サーãƒãƒ¼ã‹ã‚‰ Ansible コレクションをアップグレードã§ãるよã†ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "Support for role argument specification validation at role execution time. When a role contains an argument spec, an implicit validation task is inserted at the start of role execution." +#~ msgstr "ãƒãƒ¼ãƒ«å®Ÿè¡Œæ™‚ã«ãƒãƒ¼ãƒ«å¼•æ•°ã®ä»•æ§˜æ¤œè¨¼ã®ã‚µãƒãƒ¼ãƒˆã€‚ãƒãƒ¼ãƒ«ã«å¼•æ•°ã®ä»•æ§˜ãŒå«ã¾ã‚Œã‚‹å ´åˆã¯ã€æš—黙的ãªæ¤œè¨¼ã‚¿ã‚¹ã‚¯ãŒãƒãƒ¼ãƒ«å®Ÿè¡Œã®é–‹å§‹æ™‚ã«æŒ¿å…¥ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "add ``ArgumentSpecValidator`` class for validating parameters against an argument spec outside of ``AnsibleModule`` (https://github.com/ansible/ansible/pull/73335)" +#~ msgstr "``AnsibleModule`` (https://github.com/ansible/ansible/pull/73335) ã«å«ã¾ã‚Œãªã„引数仕様ã«å¯¾ã—ã¦ãƒ‘ラメーターを検証ã™ã‚‹ ``ArgumentSpecValidator`` ã‚¯ãƒ©ã‚¹ã‚’è¿½åŠ ã—ã¾ã™ã€‚" + +#~ msgid "Remove deprecated connection arguments from netconf_config" +#~ msgstr "netconf_config ã‹ã‚‰éžæŽ¨å¥¨ã®æŽ¥ç¶šå¼•æ•°ã‚’削除" + +#~ msgid "arista.eos" +#~ msgstr "arista.eos" + +#~ msgid "Requires ansible.netcommon v2.0.0+ to support `ansible_network_single_user_mode` and `ansible_network_import_modules` - Please refer to ansible.netcommon `changelog <https://github.com/ansible-collections/ansible.netcommon/blob/main/changelogs/CHANGELOG.rst#ansible-netcommon-collection-release-notes>`_ for more details." +#~ msgstr "`ansible_network_single_user_mode` ãŠã‚ˆã³ `ansible_network_import_modules` をサãƒãƒ¼ãƒˆã™ã‚‹ã«ã¯ã€ansible.netcommon v2.0.0 以é™ãŒå¿…è¦ã§ã™ã€‚詳細ã¯ã€ansible.netcommon ã® `changelog <https://github.com/ansible-collections/ansible.netcommon/blob/main/changelogs/CHANGELOG.rst#ansible-netcommon-collection-release-notes>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "cisco.asa" +#~ msgstr "cisco.asa" + +#~ msgid "Please refer to ansible.netcommon `changelog <https://github.com/ansible-collections/ansible.netcommon/blob/main/changelogs/CHANGELOG.rst#ansible-netcommon-collection-release-notes>` for more details." +#~ msgstr "詳細ã¯ã€ansible.netcommon ã® `changelog <https://github.com/ansible-collections/ansible.netcommon/blob/main/changelogs/CHANGELOG.rst#ansible-netcommon-collection-release-notes>` ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "Requires ansible.netcommon v2.0.0+ to support `ansible_network_single_user_mode` and `ansible_network_import_modules`." +#~ msgstr "`ansible_network_single_user_mode` ãŠã‚ˆã³ `ansible_network_import_modules` をサãƒãƒ¼ãƒˆã™ã‚‹ã«ã¯ã€ansible.netcommon v2.0.0 以é™ãŒå¿…è¦ã§ã™ã€‚" + +#~ msgid "Please refer to ansible.netcommon `changelog <https://github.com/ansible-collections/ansible.netcommon/blob/main/changelogs/CHANGELOG.rst#ansible-netcommon-collection-release-notes>`_ for more details." +#~ msgstr "詳細ã¯ã€ansible.netcommon `changelog <https://github.com/ansible-collections/ansible.netcommon/blob/main/changelogs/CHANGELOG.rst#ansible-netcommon-collection-release-notes>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "ipaddress is no longer in ansible.netcommon. For Python versions without ipaddress (< 3.0), the ipaddress package is now required." +#~ msgstr "ipaddress 㯠ansible.netcommon ã§ã¯ãªããªã‚Šã¾ã—ãŸã€‚ipaddress (< 3.0) ã®ãªã„ Python ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã¯ã€ipaddress パッケージãŒå¿…è¦ã«ãªã‚Šã¾ã—ãŸã€‚" + +#~ msgid "mysql_replication - add deprecation warning that the ``Is_Slave`` and ``Is_Master`` return values will be replaced with ``Is_Primary`` and ``Is_Replica`` in ``community.mysql`` 3.0.0 (https://github.com/ansible-collections/community.mysql/pull/147)." +#~ msgstr "mysql_replication - ``Is_Slave`` ãŠã‚ˆã³ ``Is_Master`` ã®æˆ»ã‚Šå€¤ãŒ ``community.mysql`` 3.0.0 ã® ``Is_Primary`` ãŠã‚ˆã³ ``Is_Replica`` ã«ç½®ãæ›ãˆã‚‰ã‚ŒãŸã“ã¨ã‚’示ã™éžæŽ¨å¥¨ã®è¦å‘Šã‚’è¿½åŠ ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.mysql/pull/147）。" + +#~ msgid "mysql_replication - the choices of the ``state`` option containing ``master`` will be finally replaced with the alternative ``primary`` choices in ``community.mysql`` 3.0.0, add deprecation warnings (https://github.com/ansible-collections/community.mysql/pull/150)." +#~ msgstr "mysql_replication - ``master`` ãŒå«ã¾ã‚Œã‚‹ ``state`` オプションã®é¸æŠžãŒã€æœ€çµ‚çš„ã« ``community.mysql`` 3.0.0 ã®ä»£æ›¿ ``primary`` ã®é¸æŠžè‚¢ã«ç½®ãæ›ãˆã‚‰ã‚Œã€éžæŽ¨å¥¨ã®è¦å‘Šã‚’è¿½åŠ ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.mysql/pull/150）。" + +#~ msgid "mysql_replication - the return value ``Is_Slave`` and ``Is_Master`` will be replaced with ``Is_Replica`` and ``Is_Primary`` in ``community.mysql`` 3.0.0 (https://github.com/ansible-collections/community.mysql/issues/145)." +#~ msgstr "mysql_replication - 戻り値 ``Is_Slave`` ãŠã‚ˆã³ ``Is_Master`` ã¯ã€``community.mysql`` 3.0.0 㧠``Is_Replica`` ãŠã‚ˆã³ ``Is_Primary`` ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.mysql/issues/145）。" + +#~ msgid "mysql_replication - the word ``master`` in messages returned by the module will be replaced with ``primary`` in ``community.mysql`` 3.0.0 (https://github.com/ansible-collections/community.mysql/issues/145)." +#~ msgstr "mysql_replication - モジュールã«ã‚ˆã£ã¦è¿”ã•ã‚ŒãŸãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã®å˜èªž ``master`` ã¯ã€``community.mysql`` 3.0.0 㧠``primary`` ã«ç½®ãæ›ãˆã‚‰ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.mysql/issues/145）。" + +#~ msgid "mysql_replication - the word ``slave`` in messages returned by the module replaced with ``replica`` (https://github.com/ansible-collections/community.mysql/issues/98)." +#~ msgstr "mysql_replication - ``replica`` ã«ç½®ãæ›ãˆã‚‰ã‚ŒãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚ˆã£ã¦è¿”ã•ã‚ŒãŸãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã®å˜èªž ``slave`` ã§ã™ï¼ˆhttps://github.com/ansible-collections/community.mysql/issues/98）。" + +#~ msgid "New module fortios_configuration_fact" +#~ msgstr "æ–°ã—ã„モジュール fortios_configuration_fact" + +#~ msgid "New module fortios_json_generic" +#~ msgstr "æ–°ã—ã„モジュール fortios_json_generic" + +#~ msgid "New module fortios_monitor" +#~ msgstr "æ–°ã—ã„モジュール fortios_monitor" + +#~ msgid "New module fortios_monitor_fact" +#~ msgstr "æ–°ã—ã„モジュール fortios_monitor_fact" + +#~ msgid "refactored client to inherit from AnsibleModule" +#~ msgstr "AnsibleModule ã‹ã‚‰ç¶™æ‰¿ã™ã‚‹ãƒªãƒ•ã‚¡ã‚¯ã‚¿ãƒ¼ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆ" + +#~ msgid "supports OpenID Connect authentication protocol" +#~ msgstr "OpenID Connect ã«ã‚ˆã‚‹èªè¨¼ãƒ—ãƒãƒˆã‚³ãƒ«ã®ã‚µãƒãƒ¼ãƒˆ" + +#~ msgid "supports bearer tokens for authentication" +#~ msgstr "èªè¨¼ç”¨ã®ãƒ™ã‚¢ãƒ©ãƒ¼ãƒˆãƒ¼ã‚¯ãƒ³ã®ã‚µãƒãƒ¼ãƒˆ" + +#~ msgid "Requires ansible.netcommon v2.0.0+ to support `ansible_network_single_user_mode` and `ansible_network_import_modules`" +#~ msgstr "`ansible_network_single_user_mode` をサãƒãƒ¼ãƒˆã™ã‚‹ã«ã¯ã€ansible.netcommon v2.0.0 以é™ãŠã‚ˆã³ `ansible_network_import_modules` ãŒå¿…è¦ã§ã™ã€‚" + +#~ msgid "Removed `SharedPluginLoaderObj` class from ansible.plugins.strategy. It was deprecated in favor of using the standard plugin loader." +#~ msgstr "標準ã®ãƒ—ラグインãƒãƒ¼ãƒ€ãƒ¼ã®ä½¿ç”¨ãŒæŽ¡ç”¨ã•ã‚ŒãŸãŸã‚ã€ansible.plugins.strategy ã‹ã‚‰ `SharedPluginLoaderObj` クラスãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "Removed `_get_item()` alias from callback plugin base class which had been deprecated in favor of `_get_item_label()`." +#~ msgstr "éžæŽ¨å¥¨ã«ãªã£ã¦ã„㟠`_get_item()` エイリアスをコールãƒãƒƒã‚¯ãƒ—ラグインベースクラスã‹ã‚‰å‰Šé™¤ã•ã‚Œã€`_get_item_label()` ãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The \"user\" parameter was previously deprecated and is now removed in favor of \"scope\"" +#~ msgstr "「userã€ãƒ‘ラメーターã¯éžæŽ¨å¥¨ã¨ãªã£ã¦ãŠã‚Šã€å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚「scopeã€ãŒæŽ¡ç”¨ã•ã‚Œã¦ã„ã¾ã™ã€‚" + +#~ msgid "The deprecated ``ansible.constants.BECOME_METHODS`` has been removed." +#~ msgstr "éžæŽ¨å¥¨ã® ``ansible.constants.BECOME_METHODS`` ã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The deprecated ``ansible.constants.get_config()`` has been removed." +#~ msgstr "éžæŽ¨å¥¨ã® ``ansible.constants.get_config()`` ã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "The deprecated ``ansible.constants.mk_boolean()`` has been removed." +#~ msgstr "éžæŽ¨å¥¨ã® ``ansible.constants.mk_boolean()`` ã¯å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "`with_*` loops are no longer optimized for modules whose `name` parameters can take lists (mostly package managers). Use `name` instead of looping over individual names with `with_items` and friends." +#~ msgstr "`with_*` ループã¯ã€`name` パラメーターãŒãƒªã‚¹ãƒˆï¼ˆã»ã¨ã‚“ã©ã®å ´åˆã¯ãƒ‘ッケージマãƒãƒ¼ã‚¸ãƒ£ãƒ¼ï¼‰ã‚’å–ã‚‹ã“ã¨ãŒã§ãるモジュールå‘ã‘ã«æœ€é©åŒ–ã•ã‚Œãªããªã‚Šã¾ã—ãŸã€‚`with_items` ãŠã‚ˆã³ãƒ•ãƒ¬ãƒ³ã‚ºã‚’使用ã—ã¦å€‹åˆ¥åã«ãƒ«ãƒ¼ãƒ—ã™ã‚‹ä»£ã‚ã‚Šã«ã€`name` を使用ã—ã¾ã™ã€‚" + +#~ msgid "The ``ome_device_info``, ``idrac_firmware`` and ``idrac_server_config_profile`` modules have now been migrated from community.general to the `dellemc.openmanage <https://galaxy.ansible.com/dellemc/openmanage>`_ Ansible collection. If you use ansible-base 2.10 or newer, redirections have been provided." +#~ msgstr "``ome_device_info``ã€``idrac_firmware``ã€ãŠã‚ˆã³ ``idrac_server_config_profile`` モジュールã¯ã€community.general ã‹ã‚‰ `dellemc.openmanage <https://galaxy.ansible.com/dellemc/openmanage>`_ Ansibleコレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚ansible-base 2.10 以é™ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆãŒæä¾›ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.idrac_firmware`` → ``dellemc.openmanage.idrac_firmware``) and make sure to install the dellemc.openmanage collection." +#~ msgstr "Ansible 2.9 を使用ã—ã€ã“ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ãŸå ´åˆã¯ã€FQCN (``community.general.idrac_firmware`` →``dellemc.openmanage.idrac_firmware``) を調整ã—ã€dellemc.openmanage コレクションをインストールã™ã‚‹ã‚ˆã†ã«ã—ã¦ãã ã•ã„。" + +#~ msgid "The deprecated ali_instance_facts module has been removed. Use ali_instance_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ali_instance_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ali_instance_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated gluster_heal_info module has been removed. Use gluster.gluster.gluster_heal_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® gluster_heal_info モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« gluster.gluster.gluster_heal_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated gluster_peer module has been removed. Use gluster.gluster.gluster_peer instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® gluster_peer モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« gluster.gluster.gluster_peer を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated gluster_volume module has been removed. Use gluster.gluster.gluster_volume instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® gluster_volume モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« gluster.gluster.gluster_volume を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）" + +#~ msgid "The deprecated helm module has been removed. Use community.kubernetes.helm instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® helm モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« community.kubernetes.helm を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated hpilo_facts module has been removed. Use hpilo_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® hpilo_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« hpilo_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated idrac_redfish_facts module has been removed. Use idrac_redfish_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® idrac_redfish_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« idrac_redfish_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated jenkins_job_facts module has been removed. Use jenkins_job_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® jenkins_job_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« jenkins_job_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ldap_attr module has been removed. Use ldap_attrs instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ldap_attr モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ldap_attrs を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated memset_memstore_facts module has been removed. Use memset_memstore_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® memset_memstore_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« memset_memstore_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated memset_server_facts module has been removed. Use memset_server_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® memset_server_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« memset_server_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated na_ontap_gather_facts module has been removed. Use netapp.ontap.na_ontap_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® na_ontap_gather_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« netapp.ontap.na_ontap_volume を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.general/pull/1924)。" + +#~ msgid "The deprecated nginx_status_facts module has been removed. Use nginx_status_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® nginx_status_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« nginx_status_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated one_image_facts module has been removed. Use one_image_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® one_image_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« one_image_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated onepassword_facts module has been removed. Use onepassword_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® onepassword_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« onepassword_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated oneview_datacenter_facts module has been removed. Use oneview_datacenter_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® oneview_datacenter_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_datacenter_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated oneview_enclosure_facts module has been removed. Use oneview_enclosure_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® oneview_enclosure_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_enclosure_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated oneview_ethernet_network_facts module has been removed. Use oneview_ethernet_network_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® oneview_ethernet_network_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_ethernet_network_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated oneview_fc_network_facts module has been removed. Use oneview_fc_network_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® oneview_fc_network_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_fc_network_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated oneview_fcoe_network_facts module has been removed. Use oneview_fcoe_network_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® oneview_fcoe_network_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_fcoe_network_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated oneview_logical_interconnect_group_facts module has been removed. Use oneview_logical_interconnect_group_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® oneview_logical_interconnect_group_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_logical_interconnect_group_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated oneview_network_set_facts module has been removed. Use oneview_network_set_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® oneview_network_set_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_network_set_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924).）。" + +#~ msgid "The deprecated oneview_san_manager_facts module has been removed. Use oneview_san_manager_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® oneview_san_manager_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« oneview_san_manager_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated online_server_facts module has been removed. Use online_server_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® online_server_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« online_server_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated online_user_facts module has been removed. Use online_user_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® online_user_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« online_user_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt module has been removed. Use ovirt.ovirt.ovirt_vm instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_vm を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_affinity_label_facts module has been removed. Use ovirt.ovirt.ovirt_affinity_label_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_affinity_label_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_affinity_label_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_api_facts module has been removed. Use ovirt.ovirt.ovirt_api_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_api_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_api_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_cluster_facts module has been removed. Use ovirt.ovirt.ovirt_cluster_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_cluster_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_cluster_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_datacenter_facts module has been removed. Use ovirt.ovirt.ovirt_datacenter_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_datacenter_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_datacenter_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_disk_facts module has been removed. Use ovirt.ovirt.ovirt_disk_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_disk_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_disk_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_event_facts module has been removed. Use ovirt.ovirt.ovirt_event_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_event_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_event_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_external_provider_facts module has been removed. Use ovirt.ovirt.ovirt_external_provider_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_external_provider_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_external_provider_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_group_facts module has been removed. Use ovirt.ovirt.ovirt_group_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_group_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_group_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_host_facts module has been removed. Use ovirt.ovirt.ovirt_host_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_host_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_host_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_host_storage_facts module has been removed. Use ovirt.ovirt.ovirt_host_storage_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_host_storage_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_host_storage_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_network_facts module has been removed. Use ovirt.ovirt.ovirt_network_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_network_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_network_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_nic_facts module has been removed. Use ovirt.ovirt.ovirt_nic_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_nic_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_nic_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_permission_facts module has been removed. Use ovirt.ovirt.ovirt_permission_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_permission_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_permission_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_quota_facts module has been removed. Use ovirt.ovirt.ovirt_quota_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_quota_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_quota_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_scheduling_policy_facts module has been removed. Use ovirt.ovirt.ovirt_scheduling_policy_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_scheduling_policy_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_scheduling_policy_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_snapshot_facts module has been removed. Use ovirt.ovirt.ovirt_snapshot_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_snapshot_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_snapshot_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_storage_domain_facts module has been removed. Use ovirt.ovirt.ovirt_storage_domain_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_storage_domain_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_storage_domain_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_storage_template_facts module has been removed. Use ovirt.ovirt.ovirt_storage_template_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_storage_template_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_storage_template_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_storage_vm_facts module has been removed. Use ovirt.ovirt.ovirt_storage_vm_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_storage_vm_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_storage_vm_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_tag_facts module has been removed. Use ovirt.ovirt.ovirt_tag_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_tag_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_tag_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_template_facts module has been removed. Use ovirt.ovirt.ovirt_template_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_template_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_template_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_user_facts module has been removed. Use ovirt.ovirt.ovirt_user_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_user_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_user_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_vm_facts module has been removed. Use ovirt.ovirt.ovirt_vm_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_vm_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_vm_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated ovirt_vmpool_facts module has been removed. Use ovirt.ovirt.ovirt_vmpool_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® ovirt_vmpool_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ovirt.ovirt.ovirt_vmpool_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated purefa_facts module has been removed. Use purestorage.flasharray.purefa_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® purefa_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« purestorage.flasharray.purefa_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated purefb_facts module has been removed. Use purestorage.flasharray.purefb_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® purefb_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« purestorage.flasharray.purefb_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated python_requirements_facts module has been removed. Use python_requirements_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® python_requirements_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« python_requirements_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated redfish_facts module has been removed. Use redfish_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® redfish_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« redfish_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated scaleway_image_facts module has been removed. Use scaleway_image_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® scaleway_image_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« scaleway_image_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated scaleway_ip_facts module has been removed. Use scaleway_ip_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® scaleway_ip_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« scaleway_ip_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated scaleway_organization_facts module has been removed. Use scaleway_organization_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® scaleway_organization_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« scaleway_organization_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated scaleway_security_group_facts module has been removed. Use scaleway_security_group_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® scaleway_security_group_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« scaleway_security_group_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated scaleway_server_facts module has been removed. Use scaleway_server_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® scaleway_server_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« scaleway_server_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated scaleway_snapshot_facts module has been removed. Use scaleway_snapshot_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® scaleway_snapshot_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« scaleway_snapshot_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated scaleway_volume_facts module has been removed. Use scaleway_volume_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® scaleway_volume_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« scaleway_volume_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated smartos_image_facts module has been removed. Use smartos_image_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® smartos_image_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« smartos_image_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated vertica_facts module has been removed. Use vertica_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® vertica_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« vertica_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The deprecated xenserver_guest_facts module has been removed. Use xenserver_guest_info instead (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "éžæŽ¨å¥¨ã® xenserver_guest_facts モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« xenserver_guest_info を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "The ovirt_facts docs fragment has been removed (https://github.com/ansible-collections/community.general/pull/1924)." +#~ msgstr "ovirt_facts ドã‚ュメントã®ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.general/pull/1924）。" + +#~ msgid "airbrake_deployment - removed deprecated ``token`` parameter. Use ``project_id`` and ``project_key`` instead (https://github.com/ansible-collections/community.general/pull/1926)." +#~ msgstr "airbrake_deployment - éžæŽ¨å¥¨ã® ``token`` パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``project_id`` ãŠã‚ˆã³ ``project_key`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" + +#~ msgid "bigpanda - the alias ``message`` has been removed. Use ``deployment_message`` instead (https://github.com/ansible-collections/community.general/pull/1926)." +#~ msgstr "bigpanda - エイリアス ``message`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``deployment_message`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" + +#~ msgid "cisco_spark, cisco_webex - the alias ``message`` has been removed. Use ``msg`` instead (https://github.com/ansible-collections/community.general/pull/1926)." +#~ msgstr "cisco_spark, cisco_webex - エイリアス ``message`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``msg`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" + +#~ msgid "clc_aa_policy - the ``wait`` parameter has been removed. It did not have any effect (https://github.com/ansible-collections/community.general/pull/1926)." +#~ msgstr "clc_aa_policy - ``wait`` パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚影響ã¯ã‚ã‚Šã¾ã›ã‚“（https://github.com/ansible-collections/community.general/pull/1926）。" + +#~ msgid "datadog_monitor - the alias ``message`` has been removed. Use ``notification_message`` instead (https://github.com/ansible-collections/community.general/pull/1926)." +#~ msgstr "datadog_monitor - エイリアス ``message`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``notification_message`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" + +#~ msgid "django_manage - the parameter ``liveserver`` has been removed (https://github.com/ansible-collections/community.general/pull/1926)." +#~ msgstr "django_manage - パラメーター ``liveserver`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.general/pull/1926）。" + +#~ msgid "idrac_redfish_config - the parameters ``manager_attribute_name`` and ``manager_attribute_value`` have been removed. Use ``manager_attributes`` instead (https://github.com/ansible-collections/community.general/pull/1926)." +#~ msgstr "idrac_redfish_config - ``manager_attribute_name`` パラメーターãŠã‚ˆã³ ``manager_attribute_value`` パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``manager_attributes`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" + +#~ msgid "iso_extract - the alias ``thirsty`` has been removed. Use ``force`` instead (https://github.com/ansible-collections/community.general/pull/1926)." +#~ msgstr "iso_extract - エイリアス ``thirsty`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``force`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" + +#~ msgid "ldap_entry - the ``params`` parameter is now completely removed. Using it already triggered an error since community.general 0.1.2 (https://github.com/ansible-collections/community.general/pull/2257)." +#~ msgstr "ldap_entry - ``params`` パラメーターã¯å®Œå…¨ã«å‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚community.general 0.1.2 以é™ã€ã“れを使用ã™ã‚‹ã¨ã‚¨ãƒ©ãƒ¼ãŒãƒˆãƒªã‚¬ãƒ¼ã•ã‚Œã¦ã„ã¾ã™ã€‚https://github.com/ansible-collections/community.general/pull/2257）" + +#~ msgid "pulp_repo - the ``feed_client_cert`` parameter no longer defaults to the value of the ``client_cert`` parameter (https://github.com/ansible-collections/community.general/pull/1926)." +#~ msgstr "pulp_repo - ``feed_client_cert`` パラメーターã«ã‚ˆã‚Šã€``client_cert`` パラメーターã®å€¤ã«ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆè¨å®šã•ã‚Œãªããªã‚Šã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.general/pull/1926）。" + +#~ msgid "pulp_repo - the ``feed_client_key`` parameter no longer defaults to the value of the ``client_key`` parameter (https://github.com/ansible-collections/community.general/pull/1926)." +#~ msgstr "pulp_repo - ``feed_client_key`` パラメーターã«ã‚ˆã‚Šã€``client_key`` パラメーターã®å€¤ã«ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆè¨å®šã•ã‚Œãªããªã‚Šã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.general/pull/1926）。" + +#~ msgid "pulp_repo - the alias ``ca_cert`` has been removed. Use ``feed_ca_cert`` instead (https://github.com/ansible-collections/community.general/pull/1926)." +#~ msgstr "pulp_repo - ``ca_cert`` モジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``feed_ca_cert`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" + +#~ msgid "rax - unused parameter ``service`` removed (https://github.com/ansible-collections/community.general/pull/2020)." +#~ msgstr "rax - 未使用ã®ãƒ‘ラメーター ``service`` ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.general/pull/2020）。" + +#~ msgid "redfish modules - issuing a data modification command without specifying the ID of the target System, Chassis or Manager resource when there is more than one is no longer allowed. Use the ``resource_id`` option to specify the target ID (https://github.com/ansible-collections/community.general/pull/1926)." +#~ msgstr "redfish モジュール - 複数ã®ãƒªã‚½ãƒ¼ã‚¹ãŒè¨±å¯ã•ã‚Œãªããªã£ãŸã¨ãã«ã€ã‚¿ãƒ¼ã‚²ãƒƒãƒˆã‚·ã‚¹ãƒ†ãƒ ã€ã‚·ãƒ£ãƒ¼ã‚·ã€ã¾ãŸã¯ãƒžãƒãƒ¼ã‚¸ãƒ£ãƒ¼ã®ãƒªã‚½ãƒ¼ã‚¹ã® ID を指定ã›ãšã«ãƒ‡ãƒ¼ã‚¿å¤‰æ›´ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã™ã‚‹ã“ã¨ã¯ã§ããªããªã‚Šã¾ã—ãŸã€‚``resource_id`` オプションを使用ã—ã¦ã‚¿ãƒ¼ã‚²ãƒƒãƒˆIDを指定ã—ã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/1926）。" + +#~ msgid "redfish_config - the parameters ``bios_attribute_name`` and ``bios_attribute_value`` have been removed. Use ``bios_attributes`` instead (https://github.com/ansible-collections/community.general/pull/1926)." +#~ msgstr "redfish_config - ``bios_attribute_name`` パラメーターãŠã‚ˆã³ ``bios_attribute_value`` パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``bios_attributes`` を使用ã—ã¦ãã ã•ã„（https://github.com/ansible-collections/community.general/pull/1926）。" + +#~ msgid "syspatch - the ``apply`` parameter has been removed. This is the default mode, so simply removing it will not change the behavior (https://github.com/ansible-collections/community.general/pull/1926)." +#~ msgstr "syspatch - ``apply`` パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ã“ã‚Œã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãƒ¢ãƒ¼ãƒ‰ã§ã‚ã‚‹ãŸã‚ã€å‰Šé™¤ã—ã¦ã‚‚動作ã¯å¤‰æ›´ã•ã‚Œã¾ã›ã‚“（https://github.com/ansible-collections/community.general/pull/1926）。" + +#~ msgid "xbps - the ``force`` parameter has been removed. It did not have any effect (https://github.com/ansible-collections/community.general/pull/1926)." +#~ msgstr "xbps - ``force`` パラメーターãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚影響ã¯ã‚ã‚Šã¾ã›ã‚“（https://github.com/ansible-collections/community.general/pull/1926）。" + +#~ msgid "The deprecated ``community.network.ce_sflow`` parameters: ``rate_limit``, ``rate_limit_slot``, and ``forward_enp_slot`` have been removed (https://github.com/ansible-collections/community.network/pull/255)." +#~ msgstr "éžæŽ¨å¥¨ã® ``community.network.ce_sflow`` パラメーター（``rate_limit``ã€``rate_limit_slot``ã€ãŠã‚ˆã³ ``forward_enp_slot`` ）ãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸï¼ˆhttps://github.com/ansible-collections/community.network/pull/255）。" + +#~ msgid "The deprecated ``community.network.sros`` netconf plugin has been removed. Use ``nokia.sros.md`` instead (https://github.com/ansible-collections/community.network/pull/255)." +#~ msgstr "éžæŽ¨å¥¨ã® ``community.network.sros`` netconf プラグインãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚代ã‚ã‚Šã« ``nokia.sros.md`` を使用ã—ã¦ãã ã•ã„ (https://github.com/ansible-collections/community.network/pull/255）。" + +#~ msgid "Removed module fortios_facts" +#~ msgstr "fortios_facts モジュールを削除" + +#~ msgid "Removed module fortios_registration_forticare" +#~ msgstr "fortios_registration_forticare モジュールを削除" + +#~ msgid "Removed module fortios_registration_vdom" +#~ msgstr "fortios_registration_vdom モジュールを削除" + +#~ msgid "Removed module fortios_system_config_backup_restore" +#~ msgstr "fortios_system_config_backup_restore モジュールを削除" + +#~ msgid "Removed module fortios_system_vmlicense" +#~ msgstr "fortios_system_vmlicense モジュールを削除" + +#~ msgid "Starting in 2.14, shell and command modules will no longer have the option to warn and suggest modules in lieu of commands. The ``warn`` parameter to these modules is now deprecated and defaults to ``False``. Similarly, the ``COMMAND_WARNINGS`` configuration option is also deprecated and defaults to ``False``. These will be removed and their presence will become an error in 2.14." +#~ msgstr "2.14 以é™ã€ã‚·ã‚§ãƒ«ãŠã‚ˆã³ã‚³ãƒžãƒ³ãƒ‰ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã§ã¯ã€ã‚³ãƒžãƒ³ãƒ‰ã®ä»£ã‚ã‚Šã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®è¦å‘ŠãŠã‚ˆã³æ案ã®ã‚ªãƒ—ションãŒãªããªã‚Šã¾ã—ãŸã€‚ã“れらã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã® ``warn`` パラメーターã¯éžæŽ¨å¥¨ã¨ãªã‚Šã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ ``False`` ã«ãªã‚Šã¾ã—ãŸã€‚åŒæ§˜ã«ã€``COMMAND_WARNINGS`` è¨å®šã‚ªãƒ—ションもéžæŽ¨å¥¨ã§ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã¯ ``False`` ã«è¨å®šã•ã‚Œã¾ã™ã€‚ã“れらã¯å‰Šé™¤ã•ã‚Œã€2.14 ã§ã¯ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚" + +#~ msgid "apt_key - the parameter ``key`` does not have any effect, has been deprecated and will be removed in ansible-core version 2.14 (https://github.com/ansible/ansible/pull/70319)." +#~ msgstr "apt_key - パラメーター ``key`` ã«ã¯å½±éŸ¿ãŒãªãã€éžæŽ¨å¥¨ã«ãªã‚Šã€ansible-core ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.14 ã§å‰Šé™¤ã•ã‚Œã‚‹äºˆå®šã§ã™ï¼ˆhttps://github.com/ansible/ansible/pull/70319）。" + +#~ msgid "psrp - Set the minimum version of ``pypsrp`` to ``0.4.0``." +#~ msgstr "psrp - ``pypsrp`` ã®æœ€å°ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’ ``0.4.0`` ã«è¨å®šã—ã¾ã™ã€‚" + +#~ msgid "Deprecate cli_parse module and textfsm, ttp, xml, json parser plugins as they are moved to ansible.utils collection (https://github.com/ansible-collections/ansible.netcommon/pull/182 https://github.com/ansible-collections/ansible.utils/pull/28)" +#~ msgstr "cli_parse モジュール㨠textfsmã€ttpã€xmlã€json パーサープラグイン㌠ansible.utils コレクションã«ç§»å‹•ã—ãŸãŸã‚ã€éžæŽ¨å¥¨ã«ãªã‚Šã¾ã™ï¼ˆhttps://github.com/ansible-collections/ansible.netcommon/pull/182 https://github.com/ansible-collections/ansible.utils/pull/28）。" + +#~ msgid "Deprecated nxos_bgp_af in favour of nxos_bgp_address_family resource module." +#~ msgstr "nxos_bgp_af ãŒéžæŽ¨å¥¨ã«ãªã‚Šã€nxos_bgp_address_familyリソースモジュールãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "Deprecated nxos_bgp_neighbor_af in favour of nxos_bgp_neighbor_address_family resource module." +#~ msgstr "nxos_bgp_neighbor_af ã‚’éžæŽ¨å¥¨ã«ã—ã€nxos_bgp_neighbor_address_family リソースモジュールãŒæŽ¡ç”¨ã•ã‚Œã¾ã—ãŸã€‚" + +#~ msgid "cpanm - parameter ``system_lib`` deprecated in favor of using ``become`` (https://github.com/ansible-collections/community.general/pull/2218)." +#~ msgstr "cpanm - パラメーター ``system_lib`` ãŒéžæŽ¨å¥¨ã«ãªã‚Šã€https://github.com/ansible-collections/community.general/pull/360) ã®ä½¿ç”¨ãŒæŽ¡ç”¨ã•ã‚Œã¾ã™ï¼ˆhttps://github.com/ansible-collections/community.general/pull/2218）。" + +#~ msgid "This section lists porting guides that can help you in updating playbooks, plugins and other parts of your Ansible infrastructure from one version of Ansible to the next." +#~ msgstr "本セクションã§ã¯ã€Ansible ã®ã‚ã‚‹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‹ã‚‰æ¬¡ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«ã€Ansible インフラストラクãƒãƒ£ãƒ¼ã® Playbookã€ãƒ—ラグインãªã©ã‚’æ›´æ–°ã™ã‚‹ã®ã«å½¹ã«ç«‹ã¤ç§»æ¤ã‚¬ã‚¤ãƒ‰ã‚’紹介ã—ã¾ã™ã€‚" diff --git a/docs/docsite/rst/locales/ja/LC_MESSAGES/reference_appendices.po b/docs/docsite/rst/locales/ja/LC_MESSAGES/reference_appendices.po index 8e790570..2319fba3 100644 --- a/docs/docsite/rst/locales/ja/LC_MESSAGES/reference_appendices.po +++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/reference_appendices.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Ansible devel\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-10-05 13:53+0200\n" +"POT-Creation-Date: 2021-11-09 14:07+0100\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" @@ -80,154 +80,159 @@ msgstr "値ã¯ã€``|`` ã¾ãŸã¯ ``>`` を使用ã™ã‚‹ã“ã¨ã§è¤‡æ•°ã®è¡Œã«ã msgid "While in the above ``>`` example all newlines are folded into spaces, there are two ways to enforce a newline to be kept::" msgstr "上記㮠``>`` ã®ä¾‹ã§ã¯ã€æ”¹è¡Œã¯ã™ã¹ã¦ã‚¹ãƒšãƒ¼ã‚¹ã«å¤‰æ›ã•ã‚Œã¾ã™ãŒã€å¼·åˆ¶çš„ã«æ”¹è¡Œã‚’è¡Œã†æ–¹æ³•ãŒ 2 種類ã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:112 +#: ../../rst/reference_appendices/YAMLSyntax.rst:111 +msgid "Alternatively, it can be enforced by including newline ``\\n`` characters::" +msgstr "ã‚ã‚‹ã„ã¯ã€æ”¹è¡Œ ``\\n" +"`` æ–‡å—ã‚’å«ã‚ã‚‹ã“ã¨ã§å¼·åˆ¶ã§ãã¾ã™ã€‚" + +#: ../../rst/reference_appendices/YAMLSyntax.rst:115 msgid "Let's combine what we learned so far in an arbitrary YAML example. This really has nothing to do with Ansible, but will give you a feel for the format::" msgstr "ã“ã‚Œã¾ã§ã«èª¬æ˜Žã—ãŸå†…容をã€ä»»æ„ã® YAML ã®ä¾‹ã«ã¾ã¨ã‚ã¦ã¿ã¾ã—ょã†ã€‚以下ã¯ã€Ansible ã¨ã¯é–¢ä¿‚ã‚ã‚Šã¾ã›ã‚“ãŒã€ã©ã®ã‚ˆã†ãªå½¢å¼ã«ãªã‚‹ã‹ã‚’示ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:135 +#: ../../rst/reference_appendices/YAMLSyntax.rst:138 msgid "That's all you really need to know about YAML to start writing `Ansible` playbooks." msgstr "`Ansible` Playbook ã®è¨˜è¿°ã‚’開始ã™ã‚‹ã«ã‚ãŸã‚Šã€ä»¥ä¸ŠãŒ YAML ã«ã¤ã„ã¦ç†è§£ã—ã¦ãŠãå¿…è¦ã®ã‚る内容ã§ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:138 +#: ../../rst/reference_appendices/YAMLSyntax.rst:141 msgid "Gotchas" msgstr "Gotchas" -#: ../../rst/reference_appendices/YAMLSyntax.rst:140 +#: ../../rst/reference_appendices/YAMLSyntax.rst:143 msgid "While you can put just about anything into an unquoted scalar, there are some exceptions. A colon followed by a space (or newline) ``\": \"`` is an indicator for a mapping. A space followed by the pound sign ``\" #\"`` starts a comment." msgstr "引用符ã§å›²ã¾ã‚Œã¦ã„ãªã„スカラーã«ã¯ä½•ã§ã‚‚挿入ã§ãã¾ã™ãŒã€ä¸€éƒ¨ä¾‹å¤–ãŒã‚ã‚Šã¾ã™ã€‚コãƒãƒ³ã®å¾Œã«ã‚¹ãƒšãƒ¼ã‚¹ (ã¾ãŸã¯æ”¹è¡Œ) を続ã‘ã¦è¨˜è¿° (``\": \"``) ã—ãŸå ´åˆã¯ã€ãƒžãƒƒãƒ”ングを示ã™ã‚¤ãƒ³ã‚¸ã‚±ãƒ¼ã‚¿ãƒ¼ã«ãªã‚Šã¾ã™ã€‚スペースã«ç¶šã‘ã¦ãƒãƒ³ãƒ‰è¨˜å·ã‚’記述 (``\" #\"``) ã—ãŸå ´åˆã¯ã€ã‚³ãƒ¡ãƒ³ãƒˆã®é–‹å§‹ã‚’表ã—ã¾ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:144 +#: ../../rst/reference_appendices/YAMLSyntax.rst:147 msgid "Because of this, the following is going to result in a YAML syntax error::" msgstr "ã“ã®ãŸã‚ã€ä»¥ä¸‹ã®ã‚ˆã†ãªå ´åˆã«ã¯ã€YAML 構文ãŒã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:150 +#: ../../rst/reference_appendices/YAMLSyntax.rst:153 msgid "...but this will work::" msgstr "...ãŸã ã—ã€ä»¥ä¸‹ã¯æœ‰åŠ¹ã§ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:154 +#: ../../rst/reference_appendices/YAMLSyntax.rst:157 msgid "You will want to quote hash values using colons followed by a space or the end of the line::" msgstr "コãƒãƒ³ã‚’使用ã—ã¦ãƒãƒƒã‚·ãƒ¥è¨˜å·ã‚’引用ã—ã€ãã®å¾Œã‚ã«ã‚¹ãƒšãƒ¼ã‚¹ã‚’指定ã™ã‚‹ã‹ã€è¡Œæœ«ã«ã—ã¦ãã ã•ã„。" -#: ../../rst/reference_appendices/YAMLSyntax.rst:160 +#: ../../rst/reference_appendices/YAMLSyntax.rst:163 msgid "...and then the colon will be preserved." msgstr "...ãã—ã¦ã‚³ãƒãƒ³ãŒä¿å˜ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:162 +#: ../../rst/reference_appendices/YAMLSyntax.rst:165 msgid "Alternatively, you can use double quotes::" msgstr "ã¾ãŸã¯ã€äºŒé‡å¼•ç”¨ç¬¦ã‚’使用ã—ã¦ãã ã•ã„。" -#: ../../rst/reference_appendices/YAMLSyntax.rst:168 +#: ../../rst/reference_appendices/YAMLSyntax.rst:171 msgid "The difference between single quotes and double quotes is that in double quotes you can use escapes::" msgstr "二é‡å¼•ç”¨ç¬¦ã§ã¯ã‚¨ã‚¹ã‚±ãƒ¼ãƒ—を使用ã§ãる点ãŒã€ä¸€é‡å¼•ç”¨ç¬¦ã¨äºŒé‡å¼•ç”¨ç¬¦ã¨ã®ç›¸é•ç‚¹ã§ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:173 +#: ../../rst/reference_appendices/YAMLSyntax.rst:176 msgid "The list of allowed escapes can be found in the YAML Specification under \"Escape Sequences\" (YAML 1.1) or \"Escape Characters\" (YAML 1.2)." msgstr "使用å¯èƒ½ãªã‚¨ã‚¹ã‚±ãƒ¼ãƒ—ã®ä¸€è¦§ã¯ã€YAML 仕様ã®ã€ŒEscape Sequencesã€(YAML 1.1) ã¾ãŸã¯ã€ŒEscape Charactersã€(YAML 1.2) ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/reference_appendices/YAMLSyntax.rst:175 +#: ../../rst/reference_appendices/YAMLSyntax.rst:178 msgid "The following is invalid YAML:" msgstr "以下ã¯ç„¡åŠ¹ãª YAML ã§ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:182 +#: ../../rst/reference_appendices/YAMLSyntax.rst:185 msgid "Further, Ansible uses \"{{ var }}\" for variables. If a value after a colon starts with a \"{\", YAML will think it is a dictionary, so you must quote it, like so::" msgstr "ã•ã‚‰ã«ã€Ansible ã¯å¤‰æ•°ã« \"{{ var }}\" を使用ã—ã¾ã™ã€‚コãƒãƒ³ã®å¾Œã« \"{\" ãŒæŒ‡å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€ãã®å€¤ãŒãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼ã§ã‚る㨠YAML ãŒèªè˜ã™ã‚‹ãŸã‚ã€ä»¥ä¸‹ã®ã‚ˆã†ã«å¼•ç”¨ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™::" -#: ../../rst/reference_appendices/YAMLSyntax.rst:187 +#: ../../rst/reference_appendices/YAMLSyntax.rst:190 msgid "If your value starts with a quote the entire value must be quoted, not just part of it. Here are some additional examples of how to properly quote things::" msgstr "値を引用符ã§ã™ã‚‹å ´åˆã¯ã€å€¤ã®ä¸€éƒ¨ã ã‘ã§ãªãã€å€¤å…¨ä½“を引用符ã§å›²ã‚€å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚値を引用ã™ã‚‹æ–¹æ³•ã«ã¤ã„ã¦æ£ã—ã„例を以下ã«ç¤ºã—ã¾ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:193 +#: ../../rst/reference_appendices/YAMLSyntax.rst:196 msgid "Not valid::" msgstr "以下ã¯æœ‰åŠ¹ã§ã¯ã‚ã‚Šã¾ã›ã‚“。" -#: ../../rst/reference_appendices/YAMLSyntax.rst:197 +#: ../../rst/reference_appendices/YAMLSyntax.rst:200 msgid "In addition to ``'`` and ``\"`` there are a number of characters that are special (or reserved) and cannot be used as the first character of an unquoted scalar: ``[] {} > | * & ! % # ` @ ,``." msgstr "``'`` ãŠã‚ˆã³ ``\"`` 以外ã«ã€å¼•ç”¨ç¬¦ã§å›²ã¾ã‚Œã¦ã„ãªã„スカラーã®æœ€åˆã®æ–‡å—ã¨ã—ã¦ä½¿ç”¨ã§ããªã„ç‰¹æ®Šæ–‡å— (予約文å—) ãŒã„ãã¤ã‹ã‚ã‚Šã¾ã™ (``[] {} > | * & ! % # ` @ ,`` ãªã©)。" -#: ../../rst/reference_appendices/YAMLSyntax.rst:200 +#: ../../rst/reference_appendices/YAMLSyntax.rst:203 msgid "You should also be aware of ``? : -``. In YAML, they are allowed at the beginning of a string if a non-space character follows, but YAML processor implementations differ, so it's better to use quotes." msgstr "ã¾ãŸã€``? : -`` ã«ã¯å¸¸ã«æ³¨æ„ã—ã¦ãã ã•ã„。YAML ã§ã¯ã€ã‚¹ãƒšãƒ¼ã‚¹ä»¥å¤–ã®æ–‡å—ãŒç¶šãå ´åˆã¯ã€æ–‡å—列ã®å…ˆé ã§è¨±å¯ã•ã‚Œã¾ã™ãŒã€YAML プãƒã‚»ãƒƒã‚µãƒ¼ã®å®Ÿè£…ã¯ç•°ãªã‚‹ãŸã‚ã€å¼•ç”¨ç¬¦ã‚’使用ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:203 +#: ../../rst/reference_appendices/YAMLSyntax.rst:206 msgid "In Flow Collections, the rules are a bit more strict::" msgstr "フãƒãƒ¼ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€ãƒ«ãƒ¼ãƒ«ã¯ã‚‚ã†å°‘ã—厳密ã§ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:209 +#: ../../rst/reference_appendices/YAMLSyntax.rst:212 msgid "Boolean conversion is helpful, but this can be a problem when you want a literal `yes` or other boolean values as a string. In these cases just use quotes::" msgstr "ブール値ã®å¤‰æ›ã¯ä¾¿åˆ©ã§ã™ãŒã€ãƒªãƒ†ãƒ©ãƒ«ã® `yes` ã‚„ã€æ–‡å—列ã¨ã—ã¦ä»–ã®ãƒ–ール値を指定ã™ã‚‹å ´åˆãªã©å•é¡Œã«ãªã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚ã“ã®å ´åˆã¯ã€å¼•ç”¨ç¬¦ã ã‘を使用ã—ã¾ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:216 +#: ../../rst/reference_appendices/YAMLSyntax.rst:219 msgid "YAML converts certain strings into floating-point values, such as the string `1.0`. If you need to specify a version number (in a requirements.yml file, for example), you will need to quote the value if it looks like a floating-point value::" msgstr "YAML ã¯ã€ç‰¹å®šã®æ–‡å—列を文å—列 `1.0` ãªã©ã®æµ®å‹•å°æ•°ç‚¹å€¤ã«å¤‰æ›ã—ã¾ã™ã€‚(ãŸã¨ãˆã° requirements.yml ファイルã§) ãƒãƒ¼ã‚¸ãƒ§ãƒ³ç•ªå·ã‚’指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã€ãã‚ŒãŒæµ®å‹•å°æ•°ç‚¹ã®å€¤ã®ã‚ˆã†ã«è¦‹ãˆã‚‹å ´åˆã¯ã€ãã®å€¤ã‚’引用符ã§å›²ã‚€å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:226 +#: ../../rst/reference_appendices/YAMLSyntax.rst:229 #: ../../rst/reference_appendices/faq.rst:813 #: ../../rst/reference_appendices/glossary.rst:529 #: ../../rst/reference_appendices/test_strategies.rst:267 msgid ":ref:`working_with_playbooks`" msgstr ":ref:`working_with_playbooks`" -#: ../../rst/reference_appendices/YAMLSyntax.rst:227 +#: ../../rst/reference_appendices/YAMLSyntax.rst:230 msgid "Learn what playbooks can do and how to write/run them." msgstr "Playbook ã§ã§ãã‚‹ã“ã¨ã¨ã€Playbook を記述ãŠã‚ˆã³å®Ÿè¡Œã™ã‚‹æ–¹æ³•ã‚’å¦ã³ã¾ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:228 +#: ../../rst/reference_appendices/YAMLSyntax.rst:231 msgid "`YAMLLint <http://yamllint.com/>`_" msgstr "`YAMLLint <http://yamllint.com/>`_" -#: ../../rst/reference_appendices/YAMLSyntax.rst:229 +#: ../../rst/reference_appendices/YAMLSyntax.rst:232 msgid "YAML Lint (online) helps you debug YAML syntax if you are having problems" msgstr "YAML ヒント (オンライン) ã¯ã€å•é¡ŒãŒç™ºç”Ÿã—ãŸå ´åˆã« YAML 構文ã®ãƒ‡ãƒãƒƒã‚°ã«å½¹ç«‹ã¡ã¾ã™ã€‚" -#: ../../rst/reference_appendices/YAMLSyntax.rst:230 +#: ../../rst/reference_appendices/YAMLSyntax.rst:233 msgid "`GitHub examples directory <https://github.com/ansible/ansible-examples>`_" msgstr "`GitHub examples ディレクトリー <https://github.com/ansible/ansible-examples>`_" -#: ../../rst/reference_appendices/YAMLSyntax.rst:231 +#: ../../rst/reference_appendices/YAMLSyntax.rst:234 msgid "Complete playbook files from the github project source" msgstr "Github プãƒã‚¸ã‚§ã‚¯ãƒˆã‚½ãƒ¼ã‚¹ã®å®Œå…¨ãª Playbook ファイル" -#: ../../rst/reference_appendices/YAMLSyntax.rst:232 +#: ../../rst/reference_appendices/YAMLSyntax.rst:235 msgid "`Wikipedia YAML syntax reference <https://en.wikipedia.org/wiki/YAML>`_" msgstr "`Wikipedia YAML 構文リファレンス <https://en.wikipedia.org/wiki/YAML>`_" -#: ../../rst/reference_appendices/YAMLSyntax.rst:233 +#: ../../rst/reference_appendices/YAMLSyntax.rst:236 msgid "A good guide to YAML syntax" msgstr "YAML 構文ã®é©åˆ‡ãªã‚¬ã‚¤ãƒ‰" -#: ../../rst/reference_appendices/YAMLSyntax.rst:234 +#: ../../rst/reference_appendices/YAMLSyntax.rst:237 msgid "`Mailing List <https://groups.google.com/group/ansible-project>`_" msgstr "`メーリングリスト <https://groups.google.com/group/ansible-project>`_" -#: ../../rst/reference_appendices/YAMLSyntax.rst:235 +#: ../../rst/reference_appendices/YAMLSyntax.rst:238 msgid "Questions? Help? Ideas? Stop by the list on Google Groups" msgstr "ã”質å•ã¯ã”ã–ã„ã¾ã™ã‹ã€‚サãƒãƒ¼ãƒˆãŒå¿…è¦ã§ã™ã‹ã€‚ã”æ案ã¯ã”ã–ã„ã¾ã™ã‹ã€‚Google グループã®ä¸€è¦§ã‚’ã”覧ãã ã•ã„。" -#: ../../rst/reference_appendices/YAMLSyntax.rst:236 +#: ../../rst/reference_appendices/YAMLSyntax.rst:239 #: ../../rst/reference_appendices/common_return_values.rst:250 #: ../../rst/reference_appendices/glossary.rst:535 -#: ../../rst/reference_appendices/release_and_maintenance.rst:237 +#: ../../rst/reference_appendices/release_and_maintenance.rst:30 #: ../../rst/reference_appendices/test_strategies.rst:273 msgid ":ref:`communication_irc`" msgstr ":ref:`communication_irc`" -#: ../../rst/reference_appendices/YAMLSyntax.rst:237 +#: ../../rst/reference_appendices/YAMLSyntax.rst:240 msgid "How to join Ansible chat channels (join #yaml for yaml-specific questions)" msgstr "Ansible ãƒãƒ£ãƒƒãƒˆãƒãƒ£ãƒ³ãƒãƒ«ã«å‚åŠ ã™ã‚‹æ–¹æ³• (yaml 固有ã®è³ªå•ã¯ #yaml ã«å‚åŠ ã—ã¦ãã ã•ã„)" -#: ../../rst/reference_appendices/YAMLSyntax.rst:239 +#: ../../rst/reference_appendices/YAMLSyntax.rst:242 msgid "`YAML 1.1 Specification <https://yaml.org/spec/1.1/>`_" msgstr "`YAML 1.1 Specification <https://yaml.org/spec/1.1/>`_" -#: ../../rst/reference_appendices/YAMLSyntax.rst:239 +#: ../../rst/reference_appendices/YAMLSyntax.rst:242 msgid "The Specification for YAML 1.1, which PyYAML and libyaml are currently implementing" msgstr "PyYAML ãŠã‚ˆã³ libyaml ãŒç¾åœ¨å®Ÿè£…ã•ã‚Œã¦ã„ã‚‹ YAML 1.1 ã®ä»•æ§˜" -#: ../../rst/reference_appendices/YAMLSyntax.rst:241 +#: ../../rst/reference_appendices/YAMLSyntax.rst:244 msgid "`YAML 1.2 Specification <https://yaml.org/spec/1.2/spec.html>`_" msgstr "`YAML 1.2 仕様 <https://yaml.org/spec/1.2/spec.html>`_" -#: ../../rst/reference_appendices/YAMLSyntax.rst:242 +#: ../../rst/reference_appendices/YAMLSyntax.rst:245 msgid "For completeness, YAML 1.2 is the successor of 1.1" msgstr "完全を期ã™ãŸã‚ã€YAML 1.2 㯠1.1 ã®å¾Œç¶™ã¨ãªã‚Šã¾ã™ã€‚" @@ -449,7 +454,7 @@ msgstr "開発メーリングリスト" #: ../../rst/reference_appendices/common_return_values.rst:251 #: ../../rst/reference_appendices/glossary.rst:536 -#: ../../rst/reference_appendices/release_and_maintenance.rst:238 +#: ../../rst/reference_appendices/release_and_maintenance.rst:31 #: ../../rst/reference_appendices/test_strategies.rst:274 msgid "How to join Ansible chat channels" msgstr "Ansible ãƒãƒ£ãƒƒãƒˆãƒãƒ£ãƒ³ãƒãƒ«ã¸ã®å‚åŠ æ–¹æ³•" @@ -4030,7 +4035,7 @@ msgstr "INTERPRETER_PYTHON" #: ../../rst/reference_appendices/config.rst:2336 #: ../../rst/reference_appendices/config.rst:4230 msgid "Path to the Python interpreter to be used for module execution on remote targets, or an automatic discovery mode. Supported discovery modes are ``auto`` (the default), ``auto_silent``, ``auto_legacy``, and ``auto_legacy_silent``. All discovery modes employ a lookup table to use the included system Python (on distributions known to include one), falling back to a fixed ordered list of well-known Python interpreter locations if a platform-specific default is not available. The fallback behavior will issue a warning that the interpreter should be set explicitly (since interpreters installed later may change which one is used). This warning behavior can be disabled by setting ``auto_silent`` or ``auto_legacy_silent``. The value of ``auto_legacy`` provides all the same behavior, but for backwards-compatibility with older Ansible releases that always defaulted to ``/usr/bin/python``, will use that interpreter if present." -msgstr "リモートターゲットã¾ãŸã¯è‡ªå‹•æ¤œå‡ºãƒ¢ãƒ¼ãƒ‰ã§ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«å®Ÿè¡Œã«ä½¿ç”¨ã•ã‚Œã‚‹ Python インタープリターã¸ã®ãƒ‘ス。サãƒãƒ¼ãƒˆã•ã‚Œã¦ã„る検出モードã¯ã€``auto`` (デフォルト)ã€``auto_silent``ã€``auto_legacy``ã€ãŠã‚ˆã³ ``auto_legacy_silent`` ã§ã™ã€‚ã™ã¹ã¦ã®æ¤œå‡ºãƒ¢ãƒ¼ãƒ‰ã¯ã€å«ã¾ã‚Œã¦ã„るシステム㮠Python (å«ã‚€ã“ã¨ãŒãƒ‡ã‚£ã‚¹ãƒˆãƒªãƒ“ューションã§) を使用ã™ã‚‹ãŸã‚ã«ãƒ«ãƒƒã‚¯ã‚¢ãƒƒãƒ—テーブルを使用ã—ã€ãƒ—ラットフォーム固有ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãŒä½¿ç”¨ã§ããªã„å ´åˆã¯ã€ã‚ˆã知られ㟠Python インタープリターã®ä½ç½®ã®å›ºå®šã•ã‚ŒãŸé †åºãƒªã‚¹ãƒˆã«ãƒ•ã‚©ãƒ¼ãƒ«ãƒãƒƒã‚¯ã—ã¾ã™ã€‚フォールãƒãƒƒã‚¯å‹•ä½œã§ã¯ã€ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ—リターを明示的ã«è¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚‹ã¨ã„ã†è¦å‘ŠãŒå‡ºåŠ›ã•ã‚Œã¾ã™ (後ã‹ã‚‰ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚ŒãŸã‚¤ãƒ³ã‚¿ãƒ¼ãƒ—リターãŒã€ä½¿ç”¨ã™ã‚‹ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ—リターを変更ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚‹ã‹ã‚‰ã§ã™)。ã“ã®è¦å‘Šå‹•ä½œã‚’無効ã«ã™ã‚‹ã«ã¯ã€``auto_silent`` ã¾ãŸã¯ ``auto_legacy_silent`` ã‚’è¨å®šã—ã¾ã™ã€‚ ``auto_legacy`` ã®å€¤ã¯ã™ã¹ã¦åŒã˜å‹•ä½œã‚’指定ã—ã¾ã™ãŒã€ä»¥å‰ã® Ansible リリースã¨ã®ä¸‹ä½äº’æ›æ€§ã‚’確ä¿ã™ã‚‹ãŸã‚ã«å¸¸ã«ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ ``/usr/bin/python`` ã«è¨å®šã•ã‚Œã¦ã„ãŸå ´åˆã«ã¯ã€ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ—リターãŒã‚ã‚Œã°ã€ãれを使用ã—ã¾ã™ã€‚" +msgstr "リモートターゲットã¾ãŸã¯è‡ªå‹•æ¤œå‡ºãƒ¢ãƒ¼ãƒ‰ã§ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«å®Ÿè¡Œã«ä½¿ç”¨ã•ã‚Œã‚‹ Python インタープリターã¸ã®ãƒ‘ス。サãƒãƒ¼ãƒˆã•ã‚Œã¦ã„る検出モードã¯ã€``auto`` (デフォルト)ã€``auto_silent``ã€``auto_legacy``ã€ãŠã‚ˆã³ ``auto_legacy_silent`` ã§ã™ã€‚ã™ã¹ã¦ã®æ¤œå‡ºãƒ¢ãƒ¼ãƒ‰ã¯ã€å«ã¾ã‚Œã¦ã„るシステム㮠Python (å«ã‚€ã“ã¨ãŒãƒ‡ã‚£ã‚¹ãƒˆãƒªãƒ“ューションã§) を使用ã™ã‚‹ãŸã‚ã«ãƒ«ãƒƒã‚¯ã‚¢ãƒƒãƒ—テーブルを使用ã—ã€ãƒ—ラットフォーム固有ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãŒä½¿ç”¨ã§ããªã„å ´åˆã¯ã€ã‚ˆã知られ㟠Python インタープリターã®ä½ç½®ã®å›ºå®šã•ã‚ŒãŸé †åºãƒªã‚¹ãƒˆã«ãƒ•ã‚©ãƒ¼ãƒ«ãƒãƒƒã‚¯ã—ã¾ã™ã€‚フォールãƒãƒƒã‚¯å‹•ä½œã§ã¯ã€ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ—リターを明示的ã«è¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚‹ã¨ã„ã†è¦å‘ŠãŒå‡ºåŠ›ã•ã‚Œã¾ã™ (後ã‹ã‚‰ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚ŒãŸã‚¤ãƒ³ã‚¿ãƒ¼ãƒ—リターãŒã€ä½¿ç”¨ã™ã‚‹ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ—リターを変更ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚‹ã‹ã‚‰ã§ã™)。ã“ã®è¦å‘Šå‹•ä½œã‚’無効ã«ã™ã‚‹ã«ã¯ã€``auto_silent`` ã¾ãŸã¯ ``auto_legacy_silent`` ã‚’è¨å®šã—ã¾ã™ã€‚ ``auto_legacy`` ã®å€¤ã¯ã™ã¹ã¦åŒã˜å‹•ä½œã‚’指定ã—ã¾ã™ãŒã€ä»¥å‰ã® Ansible リリースã¨ã®ä¸‹ä½äº’æ›æ€§ã‚’確ä¿ã™ã‚‹ãŸã‚ã«å¸¸ã«ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ ``/usr/bin/python`` ã«è¨å®šã•ã‚Œã¦ã„ãŸå ´åˆã«ã¯ã€ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ—リターãŒã‚ã‚Œã°ã€ãれを使用ã—ã¾ã™ã€‚" #: ../../rst/reference_appendices/config.rst:2337 msgid "``auto``" @@ -6888,7 +6893,6 @@ msgid "Used only for 2.10. The installable package (RPM/Python/Deb package) gene msgstr "2.10 ã§ã®ã¿ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚`ansible/ansible リãƒã‚¸ãƒˆãƒªãƒ¼ <https://github.com/ansible/ansible>`_ ã‹ã‚‰ç”Ÿæˆã•ã‚ŒãŸã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«å¯èƒ½ãªãƒ‘ッケージ (RPM/Python/Deb パッケージ) ã§ã™ã€‚「``ansible-core``ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" #: ../../rst/reference_appendices/glossary.rst:31 -#: ../../rst/reference_appendices/release_and_maintenance.rst:10 msgid "ansible-core" msgstr "ansible-core" @@ -9142,463 +9146,43 @@ msgstr "コードを修æ£ã—㦠github ã¸ã®ãƒ—ルè¦æ±‚ã‚’é€ä¿¡ã™ã‚‹å ´åˆã msgid "Releases and maintenance" msgstr "リリースãŠã‚ˆã³ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹" -#: ../../rst/reference_appendices/release_and_maintenance.rst:7 -msgid "This section describes release cycles, rules, and maintenance schedules for both Ansible community projects: the Ansible community package and ``ansible-core``. The two projects have different versioning systems, maintenance structures, contents, and workflows." -msgstr "ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€Ansibleコミュニティプãƒã‚¸ã‚§ã‚¯ãƒˆã®ä¸¡æ–¹ (Ansibleコミュニティパッケージã¨``ansible-core``) ã®ãƒªãƒªãƒ¼ã‚¹ã‚µã‚¤ã‚¯ãƒ«ã€ãƒ«ãƒ¼ãƒ«ã€ãŠã‚ˆã³ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ã‚¹ã‚±ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã¤ã„ã¦èª¬æ˜Žã—ã¾ã™ã€‚ã“ã®2ã¤ã®ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ç®¡ç†ã‚·ã‚¹ãƒ†ãƒ ã€ä¿å®ˆæ§‹é€ ã€ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã€ãŠã‚ˆã³ãƒ¯ãƒ¼ã‚¯ãƒ•ãƒãƒ¼ã¯ç•°ãªã‚Šã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:10 -msgid "Ansible community package" -msgstr "Ansibleコミュニティパッケージ" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:12 -msgid "Uses new versioning (2.10, then 3.0.0)" -msgstr "æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ç®¡ç†ã‚’使用ã™ã‚‹ï¼ˆ2.10ã€æ¬¡ã«3.0.0）" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:12 -msgid "Continues \"classic Ansible\" versioning (2.10, then 2.11)" -msgstr "従æ¥ã® Ansible ãƒãƒ¼ã‚¸ãƒ§ãƒ³ç®¡ç†ã‚’続行ã™ã‚‹ï¼ˆ2.10ã€æ¬¡ã«2.11）" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:13 -msgid "Follows semantic versioning rules" -msgstr "セマンティックãƒãƒ¼ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°ãƒ«ãƒ¼ãƒ«ã«å¾“ã†" - #: ../../rst/reference_appendices/release_and_maintenance.rst:13 -msgid "Does not use semantic versioning" -msgstr "セマンティックãƒãƒ¼ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°ã‚’使用ã—ãªã„" +msgid "See the `the devel release and maintenance page <https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html>`_ for up to date information." +msgstr "最新ã®æƒ…å ±ã«ã¤ã„ã¦ã¯ã€`the devel release and maintenance page <https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html>`_ ã«ã‚¢ã‚¯ã‚»ã‚¹ã—ã¦ãã ã•ã„。" -#: ../../rst/reference_appendices/release_and_maintenance.rst:14 -msgid "Maintains only one version at a time" -msgstr "一度ã«1ã¤ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ã¿ã‚’ç¶æŒã™ã‚‹" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:14 -msgid "Maintains latest version plus two older versions" -msgstr "最新ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¨ä»¥å‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’2ã¤ç¶æŒã™ã‚‹" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:15 -msgid "Includes language, runtime, and selected Collections" -msgstr "言語ã€ãƒ©ãƒ³ã‚¿ã‚¤ãƒ ã€ãŠã‚ˆã³é¸æŠžã—ãŸã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãŒå«ã¾ã‚Œã‚‹" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:15 -msgid "Includes language, runtime, and builtin plugins" -msgstr "言語ã€ãƒ©ãƒ³ã‚¿ã‚¤ãƒ ã€ãŠã‚ˆã³çµ„ã¿è¾¼ã¿ãƒ—ラグインãŒå«ã¾ã‚Œã‚‹" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:16 -msgid "Developed and maintained in Collection repositories" -msgstr "コレクションリãƒã‚¸ãƒˆãƒªã§é–‹ç™ºãŠã‚ˆã³ä¿å®ˆã•ã‚Œã¦ã„ã‚‹" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:16 -msgid "Developed and maintained in ansible/ansible repository" -msgstr "ansible / ansibleリãƒã‚¸ãƒˆãƒªã§é–‹ç™ºãŠã‚ˆã³ä¿å®ˆã•ã‚Œã¦ã„ã‚‹" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:19 -msgid "Many community users install the Ansible community package. The Ansible community package offers the functionality that existed in Ansible 2.9, with more than 85 Collections containing thousands of modules and plugins. The ``ansible-core`` option is primarily for developers and users who want to install only the collections they need." -msgstr "多ãã®ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒAnsibleコミュニティパッケージをインストールã—ã¾ã™ã€‚Ansibleコミュニティパッケージã§ã¯ã€Ansible 2.9ã«å˜åœ¨ã—ã¦ã„ãŸæ©Ÿèƒ½ã¨ã€85を超ãˆã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (æ•°åƒã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¨ãƒ—ラグインをå«ã‚€) ãŒæä¾›ã•ã‚Œã¾ã™ã€‚``ansible-core``オプションã¯ä¸»ã«ã€å¿…è¦ãªã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã ã‘をインストールã™ã‚‹é–‹ç™ºè€…ã¨ãƒ¦ãƒ¼ã‚¶ãƒ¼å‘ã‘ã§ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:27 -msgid "Release cycle overview" -msgstr "リリースサイクルã®æ¦‚è¦" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:29 -msgid "The two community releases are related - the release cycle follows this pattern:" -msgstr "2ã¤ã®ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ãƒªãƒªãƒ¼ã‚¹ã¯é–¢é€£ã—ã¦ãŠã‚Šã€ãƒªãƒªãƒ¼ã‚¹ã‚µã‚¤ã‚¯ãƒ«ã¯ä»¥ä¸‹ã®ã‚ˆã†ãªãƒ‘ターンã«ãªã£ã¦ã„ã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:31 -msgid "Release of a new ansible-core major version, for example, ansible-core 2.11" -msgstr "æ–°ã—ã„ansible-coreメジャーãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒªãƒªãƒ¼ã‚¹ï¼ˆansible-core 2.11ãªã©ï¼‰" +#: ../../rst/reference_appendices/release_and_maintenance.rst:17 +msgid "This link takes you to a different version of the Ansible documentation. Use the version selection on the left or your browser back button to return to this version of the documentation." +msgstr "ã“ã®ãƒªãƒ³ã‚¯ã¯ã€Ansible ã®ãƒ‰ã‚ュメントã®åˆ¥ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«ç§»å‹•ã—ã¾ã™ã€‚å·¦å´ã¾ãŸã¯ãƒ–ラウザーã®æˆ»ã‚‹ãƒœã‚¿ãƒ³ã‚’使用ã—ã¦ã€ã“ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒ‰ã‚ュメントã«æˆ»ã‚Šã¾ã™ã€‚" -#: ../../rst/reference_appendices/release_and_maintenance.rst:33 -msgid "New release of ansible-core and two prior versions are now maintained (in this case, ansible-base 2.10, Ansible 2.9)" -msgstr "ansible-coreã®æ–°ã—ã„リリースã¨2ã¤å‰ã¾ã§ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒç¶æŒã•ã‚Œã‚‹ã‚ˆã†ã«ï¼ˆä»Šå›žã®å ´åˆã¯ansible-base 2.10ã¨Ansible 2.9）" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:34 -msgid "Work on new features for ansible-core continues in the ``devel`` branch" -msgstr "ansible-coreã®æ–°æ©Ÿèƒ½ã«é–¢ã™ã‚‹ä½œæ¥ã¯``devel``ブランãƒã§ç¶™ç¶šã•ã‚Œã‚‹" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:36 -msgid "Collection freeze (no new Collections or new versions of existing Collections) on the Ansible community package" -msgstr "Ansibleコミュニティパッケージã§ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒ•ãƒªãƒ¼ã‚ºï¼ˆæ–°ã—ã„コレクションや既å˜ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯ã‚ã‚Šã¾ã›ã‚“）" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:37 -msgid "Release candidate for Ansible community package, testing, additional release candidates as necessary" -msgstr "Ansibleコミュニティパッケージã®ãƒªãƒªãƒ¼ã‚¹å€™è£œã€ãƒ†ã‚¹ãƒˆã€å¿…è¦ã«å¿œã˜ã¦è¿½åŠ ã®ãƒªãƒªãƒ¼ã‚¹å€™è£œ" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:38 -msgid "Release of a new Ansible community package major version based on the new ansible-core, for example, Ansible 4.0.0 based on ansible-core 2.11" -msgstr "æ–°ã—ã„ansible-coreã«åŸºã¥ãæ–°ã—ã„Ansibleコミュニティパッケージメジャーãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒªãƒªãƒ¼ã‚¹ï¼ˆä¾‹: ansible-core2.11ã«åŸºã¥ãAnsible4.0.0)" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:40 -msgid "Newest release of the Ansible community package is the only version now maintained" -msgstr "Ansibleコミュニティパッケージã®æœ€æ–°ãƒªãƒªãƒ¼ã‚¹ã ã‘ãŒç¾åœ¨ç¶æŒã•ã‚Œã¦ã„ã‚‹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã‚ã‚‹" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:41 -msgid "Work on new features continues in Collections" -msgstr "新機能ã®ä½œæ¥ã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã§ç¶™ç¶šã•ã‚Œã‚‹" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:42 -msgid "Individual Collections can make multiple minor and/or major releases" -msgstr "個々ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã¯ã€è¤‡æ•°ã®ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ãŠã‚ˆã³/ã¾ãŸã¯ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã‚’作æˆã§ãã‚‹" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:44 -msgid "Minor releases of three maintained ansible-core versions every three weeks (2.11.1)" -msgstr "3ã¤ã®ansible-core管ç†ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’3週間毎ã«ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ï¼ˆ2.11.1）" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:45 -msgid "Minor releases of the single maintained Ansible community package version every three weeks (4.1.0)" -msgstr "Ansibleコミュニティーパッケージã®ç®¡ç†ãƒãƒ¼ã‚¸ãƒ§ãƒ³1ã¤ã‚’3週間毎ã«ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ï¼ˆ4.1.0）" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:46 -msgid "Feature freeze on ansible-core" -msgstr "ansible-core 機能ã®ãƒ•ãƒªãƒ¼ã‚º" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:47 -msgid "Release candidate for ansible-core, testing, additional release candidates as necessary" -msgstr " ansible-core ã®ãƒªãƒªãƒ¼ã‚¹å€™è£œã€ãƒ†ã‚¹ãƒˆã€å¿…è¦ã«å¿œã˜ã¦è¿½åŠ ã®ãƒªãƒªãƒ¼ã‚¹å€™è£œ" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:48 -msgid "Release of the next ansible-core major version, cycle begins again" -msgstr "次ã®ansible-coreメジャーãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒªãƒªãƒ¼ã‚¹ã€‚サイクルã®å†é–‹" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:51 -msgid "Ansible community package release cycle" -msgstr "Ansible コミュニティーパッケージã®ãƒªãƒªãƒ¼ã‚¹ã‚µã‚¤ã‚¯ãƒ«" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:53 -msgid "The Ansible community team typically releases two major versions of the community package per year, on a flexible release cycle that trails the release of ``ansible-core``. This cycle can be extended to allow for larger changes to be properly implemented and tested before a new release is made available. See :ref:`roadmaps` for upcoming release details. Between major versions, we release a new minor version of the Ansible community package every three weeks. Minor releases include new backwards-compatible features, modules and plugins, as well as bug fixes." -msgstr "Ansible コミュニティーãƒãƒ¼ãƒ ã¯é€šå¸¸ã€1å¹´ã«2回メジャーãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’リリースã—ã€æŸ”軟ãªãƒªãƒªãƒ¼ã‚¹ã‚µã‚¤ã‚¯ãƒ«ã§ ``ansible-core`` ã®ãƒªãƒªãƒ¼ã‚¹ã«ç¶šãã¾ã™ã€‚ã“ã®ã‚µã‚¤ã‚¯ãƒ«ã¯ã€æ–°ã—ã„リリースをæä¾›ã™ã‚‹å‰ã«è¦æ¨¡ã®å¤§ãã„変更をæ£ã—ã実装ã—ã¦ãƒ†ã‚¹ãƒˆã§ãるよã†ã«ã€å»¶æœŸã§ãるよã†ã«ãªã£ã¦ã„ã¾ã™ã€‚今後ã®ãƒªãƒªãƒ¼ã‚¹ã®è©³ç´°ã¯ã€:ref:`roadmaps`ã‚’å‚ç…§ã—ã¦ãã ã•ã„。次ã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã‚‹ã¾ã§ã«ã€Ansible コミュニティーパッケージã®æ–°è¦ãƒžã‚¤ãƒŠãƒ¼ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒ3週間毎ã«ãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã¾ã™ã€‚マイナーリリースã«ã¯ã€å¾Œæ–¹äº’æ›æ€§ã®ã‚る機能ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€ãƒ—ラグインã ã‘ã§ãªãã€ãƒã‚°ä¿®æ£ãŒå«ã¾ã‚Œã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:55 -msgid "Starting with version 2.10, the Ansible community team guarantees maintenance for only one major community package release at a time. For example, when Ansible 4.0.0 gets released, the team will stop making new 3.x releases. Community members may maintain older versions if desired." -msgstr "ãƒãƒ¼ã‚¸ãƒ§ãƒ³2.10以é™ã€Ansibleコミュニティãƒãƒ¼ãƒ ã¯ã€ä¸€åº¦ã«ä¸»è¦ãªã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ãƒ‘ッケージリリースã®ä¿å®ˆã®ä¿è¨¼ã™ã‚‹ã®ã¯1ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ã¿ã§ã™ã€‚ãŸã¨ãˆã°ã€Ansible ãƒãƒ¼ãƒ ã§ã¯ã€Ansible 4.0.0ãŒãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã‚‹ã¨ã€æ–°ã—ã„3.xリリースã®ä½œæˆã‚’åœæ¢ã—ã¾ã™ã€‚コミュニティメンãƒãƒ¼ã¯ã€å¿…è¦ã«å¿œã˜ã¦å¤ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’ç¶æŒã§ãã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:59 -msgid "Older, unmaintained versions of the Ansible community package might contain unfixed security vulnerabilities (*CVEs*). If you are using a release of the Ansible community package that is no longer maintained, we strongly encourage you to upgrade as soon as possible in order to benefit from the latest features and security fixes." -msgstr "メンテナンスã•ã‚Œã¦ã„ãªã„以å‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®Ansibleコミュニティパッケージã«ã¯ã€ä¿®æ£ã•ã‚Œã¦ã„ãªã„ã‚»ã‚ュリティã®è„†å¼±æ€§ï¼ˆ* CVE *）ãŒå«ã¾ã‚Œã¦ã„ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚メンテナンスãŒçµ‚了ã—ãŸAnsibleコミュニティパッケージã®ãƒªãƒªãƒ¼ã‚¹ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ã§ãã‚‹ã ã‘æ—©ãアップグレードã—ã¦ã€æœ€æ–°ã®æ©Ÿèƒ½ã¨ã‚»ã‚ュリティ修æ£ã‚’利用ã™ã‚‹ã“ã¨ã‚’å¼·ããŠå‹§ã‚ã—ã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:61 -msgid "Each major release of the Ansible community package accepts the latest released version of each included Collection and the latest released version of ansible-core. For specific schedules and deadlines, see the :ref:`ansible_roadmaps` for each version. Major releases of the Ansible community package can contain breaking changes in the modules and other plugins within the included Collections and/or in core features." -msgstr "Ansible コミュニティーパッケージã®å„メジャーリリースã«ã¯ã€è¿½åŠ ã™ã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã”ã¨ã®æœ€æ–°ã®ãƒªãƒªãƒ¼ã‚¹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¨ã€æœ€æ–°ãƒªãƒªãƒ¼ã‚¹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® ansible-core ã‚’è¿½åŠ ã§ãã¾ã™ã€‚具体的ãªã‚¹ã‚±ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚„期é™ã«ã¤ã„ã¦ã¯ã€å„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®:ref:`ansible_roadmaps`ã‚’å‚ç…§ã—ã¦ãã ã•ã„。Ansible コミュニティーパッケージã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã«å«ã¾ã‚Œã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚„コア機能ã«ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚„ãã®ä»–ã®å¤§è¦æ¨¡ãªå¤‰æ›´ãŒå«ã¾ã‚Œã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:63 -msgid "The Ansible community package follows semantic versioning rules. Minor releases of the Ansible community package accept only backwards-compatible changes in included Collections, in other words, not Collections major releases. Collections must also use semantic versioning, so the Collection version numbers reflect this rule. For example, if Ansible 3.0.0 releases with community.general 2.0.0, then all minor releases of Ansible 3.x (such as Ansible 3.1.0 or Ansible 3.5.0) must include a 2.x release of community.general (such as 2.8.0 or 2.9.5) and not 3.x.x or later major releases." -msgstr "Ansibleコミュニティパッケージã¯ã€ã‚»ãƒžãƒ³ãƒ†ã‚£ãƒƒã‚¯ãƒãƒ¼ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°ãƒ«ãƒ¼ãƒ«ã‚’使用ã—ã¾ã™ã€‚Ansibleコミュニティパッケージã®ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ã¯ã€åŒæ¢±ã•ã‚Œã¦ã„るコレクションã¨ä¸‹ä½äº’æ›æ€§ã®ã‚る変更ã®ã¿ã‚’å—ã‘入れã¾ã™ã€‚ã¤ã¾ã‚Šã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã¯å—ã‘入れã¾ã›ã‚“。コレクションもセマンティックãƒãƒ¼ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°ã‚’使用ã™ã‚‹å¿…è¦ãŒã‚ã‚‹ãŸã‚ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ç•ªå·ã‚‚ã“ã®ãƒ«ãƒ¼ãƒ«ã‚’åæ˜ ã—ã¦ã„ã¾ã™ã€‚ãŸã¨ãˆã°ã€community.general 2.0.0 ãŒå«ã¾ã‚Œã‚‹ Ansible 3.0.0 リリースã®å ´åˆã«ã¯ã€Ansible 3.x ã®å…¨ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ (Ansbile 3.1.0 ã¾ãŸã¯ Ansible 3.5.0ãªã©)ã«ã¯ã€3.0.0 以é™ã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã§ã¯ãªã〠community.general (2.8.0 ã¾ãŸã¯ 2.9.5ãªã©)ã®2.xリリースをå«ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:65 -msgid "Work in Collections is tracked within the individual Collection repositories." -msgstr "コレクションã§ã®ä½œæ¥ã¯ã€å€‹ã€…ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãƒªãƒã‚¸ãƒˆãƒªå†…ã§è¿½è·¡ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:67 -msgid "You can refer to the :ref:`Ansible package porting guides<porting_guides>` for tips on updating your playbooks to run on newer versions of Ansible. For Ansible 2.10 and later releases, you can install the Ansible package with ``pip``. See :ref:`intro_installation_guide` for details. For older releases, you can download the Ansible release from `<https://releases.ansible.com/ansible/>`_." -msgstr "Ansible Playbook ã‚’æ›´æ–°ã—ã¦æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§å®Ÿè¡Œã™ã‚‹ã¨ãã®ãƒ’ントã«ã¤ã„ã¦ã¯ã€ã€Œ:ref:`Ansible package porting guides<porting_guides>`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。Ansible 2.10 以é™ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€``pip`` 㧠Ansible パッケージをインストールã§ãã¾ã™ã€‚詳細ã¯ã€ã€Œ:ref:`intro_installation_guide`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。å¤ã„リリースã§ã¯ã€Ansible リリース㯠`<https://releases.ansible.com/ansible/>`_ ã‹ã‚‰ãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰ã§ãã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:69 -msgid "This table links to the release notes for each major Ansible release. These release notes (changelogs) contain the dates and significant changes in each minor release." -msgstr "以下ã®è¡¨ã«ã¯ã€Ansible ã®å„メジャーリリースã®ãƒªãƒªãƒ¼ã‚¹ãƒŽãƒ¼ãƒˆã¸ã®ãƒªãƒ³ã‚¯ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ã“ã®ã‚ˆã†ãªãƒªãƒªãƒ¼ã‚¹ãƒŽãƒ¼ãƒˆ (変更ãƒã‚°) ã«ã¯ã€å„マイナーリリースã®æ—¥ä»˜ã‚„ã€å¤§ããªå¤‰æ›´ãŒå«ã¾ã‚Œã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:72 -msgid "Ansible Community Package Release" -msgstr "Ansible コミュニティーパッケージã®ãƒªãƒªãƒ¼ã‚¹" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:72 -#: ../../rst/reference_appendices/release_and_maintenance.rst:110 -msgid "Status" -msgstr "ステータス" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:74 -msgid "5.0.0" -msgstr "5.0.0" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:74 -msgid "In development (unreleased)" -msgstr "é–‹ç™ºä¸ (未リリース)" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:75 -msgid "`4.x Release Notes`_" -msgstr "`4.x Release Notes`_" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:75 -msgid "Current" -msgstr "ç¾è¡Œ" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:76 -msgid "`3.x Release Notes`_" -msgstr "`3.x Release Notes`_" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:76 -#: ../../rst/reference_appendices/release_and_maintenance.rst:77 -#: ../../rst/reference_appendices/release_and_maintenance.rst:116 -#: ../../rst/reference_appendices/release_and_maintenance.rst:117 -#: ../../rst/reference_appendices/release_and_maintenance.rst:118 -#: ../../rst/reference_appendices/release_and_maintenance.rst:119 -#: ../../rst/reference_appendices/release_and_maintenance.rst:120 -msgid "Unmaintained (end of life)" -msgstr "メンテナンス対象外 (エンドオフライフ)" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:77 -msgid "`2.10 Release Notes`_" -msgstr "`2.10 Release Notes`_" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:87 -msgid "ansible-core release cycle" -msgstr "ansible-core リリースサイクル" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:89 -msgid "``ansible-core`` is developed and released on a flexible release cycle. This cycle can be extended in order to allow for larger changes to be properly implemented and tested before a new release is made available. See :ref:`roadmaps` for upcoming release details." -msgstr "``ansible-core`` ã¯ã€æŸ”軟ãªãƒªãƒªãƒ¼ã‚¹ã‚µã‚¤ã‚¯ãƒ«ã§é–‹ç™ºãŠã‚ˆã³ãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã¾ã™ã€‚ã“ã®ã‚µã‚¤ã‚¯ãƒ«ã¯ã€å¤§è¦æ¨¡ãªå¤‰æ›´ã‚’æ£ã—ã実装ã—ã¦ã€ãƒ†ã‚¹ãƒˆã—ã¦ã‹ã‚‰æ–°ã—ã„リリースãŒå…¬é–‹ã•ã‚Œã‚‹ã‚ˆã†ã«ã€å»¶é•·ã™ã‚‹ã“ã¨ãŒå¯èƒ½ã§ã™ã€‚今後ã®ãƒªãƒªãƒ¼ã‚¹ã®è©³ç´°ã¯ã€ã€Œ:ref:`roadmaps`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:91 -msgid "``ansible-core`` has a graduated maintenance structure that extends to three major releases. For more information, read about the :ref:`development_and_stable_version_maintenance_workflow` or see the chart in :ref:`release_schedule` for the degrees to which current releases are maintained." -msgstr "``ansible-core`` ã«ã¯ã€3 ã¤ã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã§å±•é–‹ã•ã‚Œã‚‹æ®µéšŽçš„ãªãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹æ§‹é€ ãŒã‚ã‚Šã¾ã™ã€‚詳細ã¯ã€ã€Œ:ref:`development_and_stable_version_maintenance_workflow`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。ã¾ãŸã€ç¾åœ¨ã®ãƒªãƒªãƒ¼ã‚¹ãŒã©ã®ç¨‹åº¦ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ã•ã‚Œã¦ã„ã‚‹ã‹ã«ã¤ã„ã¦ã¯ã€:ref:`release_schedule` ã®è¡¨ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:97 -msgid "Older, unmaintained versions of ``ansible-core`` can contain unfixed security vulnerabilities (*CVEs*). If you are using a release of ``ansible-core`` that is no longer maintained, we strongly encourage you to upgrade as soon as possible to benefit from the latest features and security fixes. ``ansible-core`` maintenance continues for 3 releases. Thus the latest release receives security and general bug fixes when it is first released, security and critical bug fixes when the next ``ansible-core`` version is released, and **only** security fixes once the follow on to that version is released." -msgstr "``ansible-core``ã®ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ã•ã‚Œã¦ã„ãªã„以å‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«ã¯ã€ã‚»ã‚ュリティー脆弱性 (*CVE*) ãŒå«ã¾ã‚Œã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚ä¿å®ˆã®ãªã„``ansible-core``ã®ãƒªãƒªãƒ¼ã‚¹ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã«ã¯ã€æœ€æ–°ã®æ©Ÿèƒ½ãŠã‚ˆã³ã‚»ã‚ュリティー修æ£ã‚’活用ã§ãるよã†ã«ã€ã™ãã«ã‚¢ãƒƒãƒ—グレードã™ã‚‹ã“ã¨ã‚’å¼·ã推奨ã—ã¾ã™ã€‚``ansible-core``ã®ä¿å®ˆã¯ã€3リリース分継続ã•ã‚Œã¾ã™ã€‚ãã®ãŸã‚ã€æœ€æ–°ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€åˆå›žãƒªãƒªãƒ¼ã‚¹æ™‚ã«ã‚»ã‚ュリティーã¨ä¸€èˆ¬çš„ãªãƒã‚°ä¿®æ£ãŒã€æ¬¡ã®``ansible-core``ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã‚‹ã¨ã€ã‚»ã‚ュリティーã¨é‡å¤§ãªãƒã‚°ä¿®æ£ãŒã€ãã®æ¬¡ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã‚‹ã¨ã€ã‚»ã‚ュリティー修æ£**ã®ã¿**ãŒæä¾›ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:99 -msgid "You can refer to the :ref:`core_porting_guides` for tips on updating your playbooks to run on newer versions of ``ansible-core``." -msgstr "Playbook ã‚’æ›´æ–°ã—ã¦``ansible-core`` ã®æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§å®Ÿè¡Œã™ã‚‹ã¨ãã®ãƒ’ントã¯ã€ã€Œ:ref:`core_porting_guides`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:101 -msgid "You can install ``ansible-core`` with ``pip``. See :ref:`intro_installation_guide` for details." -msgstr "``pip`` 㧠``ansible-core`` をインストールã§ãã¾ã™ã€‚詳細ã¯ã€ã€Œ:ref:`intro_installation_guide`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:105 -msgid "This table links to the release notes for each major ``ansible-core`` release. These release notes (changelogs) contain the dates and significant changes in each minor release." -msgstr "以下ã®è¡¨ã«ã¯ã€``ansible-core`` ã®å„メジャーリリースã®ãƒªãƒªãƒ¼ã‚¹ãƒŽãƒ¼ãƒˆã¸ã®ãƒªãƒ³ã‚¯ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ã“ã®ã‚ˆã†ãªãƒªãƒªãƒ¼ã‚¹ãƒŽãƒ¼ãƒˆ (変更ãƒã‚°) ã«ã¯ã€å„マイナーリリースã®æ—¥ä»˜ã‚„ã€å¤§ããªå¤‰æ›´ãŒå«ã¾ã‚Œã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:110 -msgid "``ansible-core`` / ``ansible-base`` Release" -msgstr "``ansible-core`` / ``ansible-base`` リリース" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:112 -msgid "devel" -msgstr "devel" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:112 -msgid "In development (ansible-core 2.12 unreleased, trunk)" -msgstr "é–‹ç™ºä¸ (未リリース㮠ansible-core 2.12 (trunk))" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:113 -msgid "`2.11 ansible-core Release Notes`_" -msgstr "`2.11 ansible-core Release Notes`_" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:113 -msgid "Maintained (security **and** general bug fixes)" -msgstr "メンテナンス対象 (ã‚»ã‚ュリティー **ãŠã‚ˆã³** 一般的ãªãƒã‚°ã®ä¿®æ£)" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:114 -msgid "`2.10 ansible-base Release Notes`_" -msgstr "`2.10 ansible-base Release Notes`_" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:114 -msgid "Maintained (security **and** critical bug fixes)" -msgstr "メンテナンス対象 (ã‚»ã‚ュリティー **ãŠã‚ˆã³** é‡å¤§ãªãƒã‚°ã®ä¿®æ£)" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:115 -msgid "`2.9 Release Notes`_" -msgstr "`2.9 Release Notes`_" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:115 -msgid "Maintained (pre-collections) (security fixes only)" -msgstr "ä¿å®ˆã‚り（事å‰åŽé›†ï¼‰ï¼ˆã‚»ã‚ュリティ修æ£ã®ã¿ï¼‰" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:116 -msgid "`2.8 Release Notes`_" -msgstr "`2.8 Release Notes`_" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:117 -msgid "`2.7 Release Notes`_" -msgstr "`2.7 Release Notes`_" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:118 -msgid "`2.6 Release Notes`_" -msgstr "`2.6 Release Notes`_" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:119 -msgid "`2.5 Release Notes`_" -msgstr "`2.5 リリースノート`_" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:120 -msgid "<2.5" -msgstr "2.5 よりå‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:139 -msgid "Preparing for a new release" -msgstr "æ–°ã—ã„リリースã®æº–å‚™" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:144 -msgid "Feature freezes" -msgstr "機能フリーズ" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:146 -msgid "During final preparations for a new release, core developers and maintainers focus on improving the release candidate, not on adding or reviewing new features. We may impose a feature freeze." -msgstr "æ–°ã—ã„リリースã®æœ€çµ‚準備ä¸ã€ã‚³ã‚¢é–‹ç™ºè€…ã¨ãƒ¡ãƒ³ãƒ†ãƒŠã¯ã€æ–°æ©Ÿèƒ½ã®è¿½åŠ やレビューã§ã¯ãªãã€ãƒªãƒªãƒ¼ã‚¹å€™è£œã®æ”¹å–„ã«é›†ä¸ã—ã¾ã™ã€‚機能フリーズを指示ã™ã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:148 -msgid "A feature freeze means that we delay new features and fixes that are not related to the pending release so we can ship the new release as soon as possible." -msgstr "機能フリーズã¨ã¯ã€ä¿ç•™ä¸ã®ãƒªãƒªãƒ¼ã‚¹ã«é–¢é€£ã®ãªã„新機能や修æ£ã‚’é…らã›ã¦ã€æ–°ã—ã„リリースをã§ãã‚‹ã ã‘æ—©ã出è·ã§ãるよã†ã«ã™ã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:152 -msgid "Release candidates" -msgstr "リリースã®å€™è£œ (Release Candidate)" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:154 -msgid "We create at least one release candidate before each new major release of Ansible or ``ansible-core``. Release candidates allow the Ansible community to try out new features, test existing playbooks on the release candidate, and report bugs or issues they find." -msgstr "Ansibleã¾ãŸã¯``ansible-core``ã®æ–°ã—ã„メジャーリリースã®å‰ã«æ¯Žå›žã€å°‘ãªãã¨ã‚‚1ã¤ã®ãƒªãƒªãƒ¼ã‚¹å€™è£œã‚’作æˆã—ã¾ã™ã€‚リリース候補を使用ã™ã‚‹ã“ã¨ã§ã€Ansibleコミュニティã¯æ–°æ©Ÿèƒ½ã‚’試ã—ãŸã‚Šã€ãƒªãƒªãƒ¼ã‚¹å€™è£œã§æ—¢å˜ã®Playbookをテストã—ãŸã‚Šã€è¦‹ã¤ã‹ã£ãŸãƒã‚°ã‚„å•é¡Œã‚’å ±å‘Šã—ãŸã‚Šã§ãã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:156 -msgid "Ansible and ``ansible-core`` tag the first release candidate (RC1) which is usually scheduled to last five business days. If no major bugs or issues are identified during this period, the release candidate becomes the final release." -msgstr "Ansible ãŠã‚ˆã³ ``ansible-core`` ã¯ã€æœ€åˆã®ãƒªãƒªãƒ¼ã‚¹å€™è£œã®ã‚¿ã‚° (RC1) ãŒä»˜ã‘られã¾ã™ã€‚通常ã€RC1 ã¯æœ€å¾Œã®5å–¶æ¥æ—¥ã«ã‚¹ã‚±ã‚¸ãƒ¥ãƒ¼ãƒ«ã•ã‚Œã¾ã™ã€‚ã“ã®æœŸé–“ã«ãƒ¡ã‚¸ãƒ£ãƒ¼ãªãƒã‚°ã‚„å•é¡ŒãŒç‰¹å®šã•ã‚Œãªã„å ´åˆã«ã¯ã€ãƒªãƒªãƒ¼ã‚¹å€™è£œãŒæœ€çµ‚リリースã¨ãªã‚Šã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:158 -msgid "If there are major problems with the first candidate, the team and the community fix them and tag a second release candidate (RC2). This second candidate lasts for a shorter duration than the first. If no problems have been reported for an RC2 after two business days, the second release candidate becomes the final release." -msgstr "最åˆã®å€™è£œã«å¤§ããªå•é¡ŒãŒã‚ã‚‹å ´åˆã¯ã€ãƒãƒ¼ãƒ ãŠã‚ˆã³ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ãƒ¼ãŒä¿®æ£ã‚’åŠ ãˆã¦ã€2 番目ã®å€™è£œã®ã‚¿ã‚° (RC2) ãŒä»˜ã‘られã¾ã™ã€‚2 番目ã®å€™è£œã¯ã€1 番目よりも期間ã¯çŸããªã‚Šã¾ã™ã€‚2 å–¶æ¥æ—¥ãŒçµŒéŽã—ã¦å•é¡ŒãŒå ±å‘Šã•ã‚Œãªã„å ´åˆã¯ã€ã“ã®2番目ã®ãƒªãƒªãƒ¼ã‚¹å€™è£œãŒæœ€çµ‚çš„ãªãƒªãƒªãƒ¼ã‚¹ã¨ãªã‚Šã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:160 -msgid "If there are major problems in RC2, the cycle begins again with another release candidate and repeats until the maintainers agree that all major problems have been fixed." -msgstr "RC2ã«é‡å¤§ãªå•é¡ŒãŒã‚ã‚‹å ´åˆã«ã¯ã€ã‚µã‚¤ã‚¯ãƒ«ã¯åˆ¥ã®ãƒªãƒªãƒ¼ã‚¹å€™è£œã‹ã‚‰å†é–‹ã•ã‚Œã€ã™ã¹ã¦ã®ä¸»è¦ãªå•é¡ŒãŒä¿®æ£ã•ã‚ŒãŸã“ã¨ã«ãƒ¡ãƒ³ãƒ†ãƒŠãŒåŒæ„ã™ã‚‹ã¾ã§ç¹°ã‚Šè¿”ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:166 -msgid "Development and maintenance workflows" -msgstr "開発ã¨ä¿å®ˆã®ãƒ¯ãƒ¼ã‚¯ãƒ•ãƒãƒ¼" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:168 -msgid "In between releases, the Ansible community develops new features, maintains existing functionality, and fixes bugs in ``ansible-core`` and in the collections included in the Ansible community package." -msgstr "次ã®ãƒªãƒªãƒ¼ã‚¹ã¾ã§ã®é–“ã«ã€Ansibleコミュニティã¯æ–°ã—ã„機能を開発ã—ã¦æ—¢å˜ã®æ©Ÿèƒ½ã®ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ã‚’è¡Œã„ã€``ansible-core`` ã‚„ Ansible コミュニティーパッケージã«å«ã¾ã‚Œã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒã‚°ã‚’ä¿®æ£ã—ã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:171 -msgid "Ansible community package workflow" -msgstr "Ansible コミュニティパッケージã®ãƒ¯ãƒ¼ã‚¯ãƒ•ãƒãƒ¼" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:173 -msgid "The Ansible community develops and maintains the features and functionality included in the Ansible community package in Collections repositories, with a workflow that looks like this:" -msgstr "Ansibleコミュニティã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãƒªãƒã‚¸ãƒˆãƒªã®Ansibleコミュニティパッケージã«å«ã¾ã‚Œã‚‹æ©Ÿèƒ½ã‚’開発ãŠã‚ˆã³ä¿å®ˆã—ã¾ã™ã€‚ワークフãƒãƒ¼ã¯æ¬¡ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:175 -msgid "Developers add new features and bug fixes to the individual Collections, following each Collection's rules on contributing." -msgstr "開発者ã¯ã€è²¢çŒ®ã«é–¢ã™ã‚‹å„コレクションã®ãƒ«ãƒ¼ãƒ«ã«å¾“ã£ã¦ã€å€‹ã€…ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«æ–°æ©Ÿèƒ½ã¨ãƒã‚°ä¿®æ£ã‚’è¿½åŠ ã™ã‚‹ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:176 -#: ../../rst/reference_appendices/release_and_maintenance.rst:190 -msgid "Each new feature and each bug fix includes a changelog fragment describing the work." -msgstr "å„新機能ã¨å„ãƒã‚°ä¿®æ£ã«ã¯ã€ä½œæ¥ã‚’説明ã™ã‚‹å¤‰æ›´ãƒã‚°ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆãŒå«ã¾ã‚Œã¦ã„る。" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:177 -msgid "Release engineers create a minor release for the current version every three weeks to ensure that the latest bug fixes are available to users." -msgstr "リリースエンジニアã¯ã€æœ€æ–°ã®ãƒã‚°ä¿®æ£ã‚’ユーザーãŒåˆ©ç”¨ã§ãるよã†ã«ã€ç¾åœ¨ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ã‚’3週間ã”ã¨ã«ä½œæˆã™ã‚‹ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:178 -msgid "At the end of the development period, the release engineers announce which Collections, and which major version of each included Collection, will be included in the next release of the Ansible community package. New Collections and new major versions may not be added after this, and the work of creating a new release begins." -msgstr "開発期間ã®çµ‚ã‚ã‚Šã«ã€ãƒªãƒªãƒ¼ã‚¹ã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ã¯ã€Ansibleコミュニティパッケージã®æ¬¡ã®ãƒªãƒªãƒ¼ã‚¹ã«å«ã¾ã‚Œã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã¨ã€è¿½åŠ 済ã¿ã®å„コレクションã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’発表ã—ã¾ã™ã€‚ã“れ以é™ã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãŠã‚ˆã³ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯æ–°ãŸã«è¿½åŠ ã§ããšã€æ–°ã—ã„リリースã®ä½œæˆæº–å‚™ãŒé–‹å§‹ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:180 -msgid "We generally do not provide fixes for unmaintained releases of the Ansible community package, however, there can sometimes be exceptions for critical issues." -msgstr "通常ã€Ansible コミュニティーパッケージã§ä¿å®ˆã•ã‚Œã¦ã„ãªã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«å¯¾ã™ã‚‹ä¿®æ£ã¯æä¾›ã—ã¦ã„ã¾ã›ã‚“ãŒã€é‡å¤§ãªå•é¡Œã«é–¢ã—ã¦ã¯ä¾‹å¤–ã§å¯¾å¿œã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:182 -msgid "Some Collections are maintained by the Ansible team, some by Partner organizations, and some by community teams. For more information on adding features or fixing bugs in Ansible-maintained Collections, see :ref:`contributing_maintained_collections`." -msgstr "Ansibleãƒãƒ¼ãƒ ã€ãƒ‘ートナー組織ã€ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ãƒãƒ¼ãƒ ãŒã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’ãã‚Œãžã‚Œéƒ¨åˆ†çš„ã«ç®¡ç†ã—ã¦ã„ã¾ã™ã€‚ Ansibleã§ç®¡ç†ã•ã‚Œã¦ã„るコレクションã®æ©Ÿèƒ½ã®è¿½åŠ ã‚„ãƒã‚°ã®ä¿®æ£ã®è©³ç´°ã«ã¤ã„ã¦ã¯ã€:ref:`contributing_maintained_collections` ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:185 -msgid "ansible-core workflow" -msgstr "ansible-core ワークフãƒãƒ¼" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:187 -msgid "The Ansible community develops and maintains ``ansible-core`` on GitHub_, with a workflow that looks like this:" -msgstr "Ansibleコミュニティã¯ã€GitHub_ã®``ansible-core``ã§é–‹ç™ºã¨ç¶æŒã‚’è¡Œã£ã¦ãŠã‚Šã€æ¬¡ã®ã‚ˆã†ãªãƒ¯ãƒ¼ã‚¯ãƒ•ãƒãƒ¼ã‚’使用ã—ã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:189 -msgid "Developers add new features and bug fixes to the ``devel`` branch." -msgstr "開発者ã¯ã€``devel``ブランãƒã«æ–°æ©Ÿèƒ½ã¨ãƒã‚°ä¿®æ£ã‚’è¿½åŠ ã™ã‚‹ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:191 -msgid "The development team backports bug fixes to one, two, or three stable branches, depending on the severity of the bug. They do not backport new features." -msgstr "開発ãƒãƒ¼ãƒ ã¯ã€ãƒã‚°ã®é‡å¤§åº¦ã«å¿œã˜ã¦ã€ãƒã‚°ä¿®æ£ã‚’1ã¤ã€2ã¤ã€ã¾ãŸã¯3ã¤ã®å®‰å®šã—ãŸãƒ–ランãƒã«ãƒãƒƒã‚¯ãƒãƒ¼ãƒˆã—ã€æ–°æ©Ÿèƒ½ã®ãƒãƒƒã‚¯ãƒãƒ¼ãƒˆã¯è¡Œã‚ãªã„。" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:192 -msgid "Release engineers create a minor release for each maintained version every three weeks to ensure that the latest bug fixes are available to users." -msgstr "リリースエンジニアã¯ã€æœ€æ–°ã®ãƒã‚°ä¿®æ£ã‚’ユーザーãŒåˆ©ç”¨ã§ãるよã†ã«ã€å„ä¿å®ˆãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ã‚’3週間ã”ã¨ã«ä½œæˆã™ã‚‹ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:193 -msgid "At the end of the development period, the release engineers impose a feature freeze and the work of creating a new release begins." -msgstr "開発期間ã®çµ‚ã‚ã‚Šã«ã€ãƒªãƒªãƒ¼ã‚¹ã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ã¯æ©Ÿèƒ½ã‚’フリーズã—ã€æ–°ã—ã„リリースã®æº–備を開始ã™ã‚‹ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:195 -msgid "We generally do not provide fixes for unmaintained releases of ``ansible-core``, however, there can sometimes be exceptions for critical issues." -msgstr "通常ã€ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ã•ã‚Œã¦ã„ãªã„``ansible-core``リリースã«å¯¾ã™ã‚‹ä¿®æ£ã¯æä¾›ã—ã¦ã„ã¾ã›ã‚“ãŒã€é‡å¤§ãªå•é¡Œã«é–¢ã—ã¦ã¯ä¾‹å¤–ã§å¯¾å¿œã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:197 -msgid "For more information on adding features or fixing bugs in ``ansible-core`` see :ref:`community_development_process`." -msgstr "``ansible-core`` ã®æ©Ÿèƒ½ã®è¿½åŠ ã¾ãŸã¯ãƒã‚°ã®ä¿®æ£ã®è©³ç´°ã«ã¤ã„ã¦ã¯ã€:ref:`community_development_process`ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:204 -msgid "Changelogs" -msgstr "変更ãƒã‚° (Changelog)" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:206 -msgid "We generate changelogs based on fragments. When creating new features for existing modules and plugins or fixing bugs, create a changelog fragment describing the change. A changelog entry is not needed for new modules or plugins. Details for those items will be generated from the module documentation." -msgstr "変更ãƒã‚°ã¯ã€ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã«åŸºã¥ã„ã¦ç”Ÿæˆã•ã‚Œã¾ã™ã€‚æ—¢å˜ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚„プラグインã®æ–°ã—ã„機能を作æˆã—ãŸã‚Šã€ãƒã‚°ã‚’ä¿®æ£ã—ãŸã‚Šã™ã‚‹ã¨ãã¯ã€å¤‰æ›´ç‚¹ã‚’記述ã—ãŸå¤‰æ›´ãƒã‚°ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã‚’作æˆã—ã¾ã™ã€‚変更ãƒã‚°ã®ã‚¨ãƒ³ãƒˆãƒªãƒ¼ã¯ã€æ–°ã—ã„モジュールやプラグインã«ã¯å¿…è¦ã‚ã‚Šã¾ã›ã‚“。ãれらã®é …ç›®ã®è©³ç´°ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ‰ã‚ュメントã‹ã‚‰ç”Ÿæˆã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:208 -msgid "To add changelog fragments to Collections in the Ansible community package, we recommend the `antsibull-changelog utility <https://github.com/ansible-community/antsibull-changelog/blob/main/docs/changelogs.rst>`_." -msgstr "Ansibleコミュニティパッケージã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«å¤‰æ›´ãƒã‚°ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã‚’è¿½åŠ ã™ã‚‹ã«ã¯ã€`antsibull-changelog utility <https://github.com/ansible-community/antsibull-changelog/blob/main/docs/changelogs.rst>`_を推奨ã—ã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:210 -msgid "To add changelog fragments for new features and bug fixes in ``ansible-core``, see the :ref:`changelog examples and instructions<changelogs_how_to>` in the Community Guide." -msgstr "``ansible-core``ã«æ–°æ©Ÿèƒ½ã¨ãƒã‚°ä¿®æ£ã®å¤‰æ›´ãƒã‚°ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã‚’è¿½åŠ ã™ã‚‹ã«ã¯ã€ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ã‚¬ã‚¤ãƒ‰ã®:ref:`changelog examples and instructions<changelogs_how_to>`ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:213 -msgid "Deprecation cycles" -msgstr "éžæŽ¨å¥¨ã‚µã‚¤ã‚¯ãƒ«" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:215 -msgid "Sometimes we remove a feature, normally in favor of a reimplementation that we hope does a better job. To do this we have a deprecation cycle. First we mark a feature as 'deprecated'. This is normally accompanied with warnings to the user as to why we deprecated it, what alternatives they should switch to and when (which version) we are scheduled to remove the feature permanently." -msgstr "通常ã€å†å®Ÿè£…ã—ã¦ã‚¸ãƒ§ãƒ–実行ã®æ”¹å–„を希望ã™ã‚‹å ´åˆãªã©ã€æ©Ÿèƒ½ã‚’削除ã™ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ã“れを行ã†ãŸã‚ã«ã€éžæŽ¨å¥¨ã®ã‚µã‚¤ã‚¯ãƒ«ãŒã‚ã‚Šã¾ã™ã€‚ã¾ãšã€æ©Ÿèƒ½ã‚’「éžæŽ¨å¥¨ã€ã¨ã—ã¦ãƒžãƒ¼ã‚¯ã—ã¾ã™ã€‚ã“ã‚Œã«ã¯é€šå¸¸ã€éžæŽ¨å¥¨ã«ãªã£ãŸç†ç”±ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒåˆ‡ã‚Šæ›¿ãˆã‚‹å¿…è¦ã®ã‚る代替手段ã€ãŠã‚ˆã³æ©Ÿèƒ½ã‚’完全ã«å‰Šé™¤ã™ã‚‹äºˆå®šã®æ™‚期 (ãƒãƒ¼ã‚¸ãƒ§ãƒ³) ã«é–¢ã™ã‚‹è¦å‘ŠãŒä¼´ã„ã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:218 -msgid "Ansible community package deprecation cycle" -msgstr "Ansibleコミュニティパッケージã®éžæŽ¨å¥¨ã‚µã‚¤ã‚¯ãƒ«" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:220 -msgid "Since Ansible is a package of individual collections, the deprecation cycle depends on the collection maintainers. We recommend the collection maintainers deprecate a feature in one Ansible major version and do not remove that feature for one year, or at least until the next major Ansible version. For example, deprecate the feature in 3.1.0, and do not remove the feature until 5.0.0, or 4.0.0 at the earliest. Collections should use semantic versioning, such that the major collection version cannot be changed within an Ansible major version. Thus the removal should not happen before the next major Ansible community package release. This is up to each collection maintainer and cannot be guaranteed." -msgstr "Ansible ã¯å€‹åˆ¥ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒ‘ッケージã§ã‚ã‚‹ãŸã‚ã€éžæŽ¨å¥¨ã®ã‚µã‚¤ã‚¯ãƒ«ã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒ¡ãƒ³ãƒ†ãƒŠãƒ¼ã«ã‚ˆã£ã¦ç•°ãªã‚Šã¾ã™ã€‚コレクションメンテナー㯠1 ã¤ã® Ansible メジャーãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã“ã®æ©Ÿèƒ½ã‚’éžæŽ¨å¥¨ã«ã—ã€1 å¹´é–“ã§ãã®æ©Ÿèƒ½ã‚’削除ã™ã‚‹ã‹ã€å°‘ãªãã¨ã‚‚次㮠Ansible ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¾ã§ã«å‰Šé™¤ã—ãªã„ã“ã¨ã‚’推奨ã—ã¾ã™ã€‚ãŸã¨ãˆã°ã€3.1.0 ã§ã“ã®æ©Ÿèƒ½ã‚’éžæŽ¨å¥¨ã«ã—ãŸå ´åˆã¯ã€æœ€ä½Žã§ã‚‚ 5.0.0 ã¾ãŸã¯ 4.0.0 ã¾ã§ã®æ©Ÿèƒ½ã‚’削除ã—ãªã„ã§ãã ã•ã„。コレクションã¯ã‚»ãƒžãƒ³ãƒ†ã‚£ãƒƒã‚¯ãƒãƒ¼ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°ã‚’使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã—ãŸãŒã£ã¦ã€ãƒ¡ã‚¸ãƒ£ãƒ¼ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯ã€Ansible メジャーãƒãƒ¼ã‚¸ãƒ§ãƒ³å†…ã§å¤‰æ›´ã§ãã¾ã›ã‚“。ã—ãŸãŒã£ã¦ã€æ¬¡ã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã® Ansible コミュニティーパッケージリリースã®å‰ã«å‰Šé™¤ã™ã‚‹ã“ã¨ã¯ã§ãã¾ã›ã‚“。ã“ã‚Œã¯ã€å„コレクションã®ãƒ¡ãƒ³ãƒ†ãƒŠãƒ¼ã®å½¹å‰²ã§ã‚ã‚Šã€ä¿è¨¼ã•ã‚Œã¦ã„ã‚‹ã‚‚ã®ã§ã¯ã‚ã‚Šã¾ã›ã‚“。" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:223 -msgid "ansible-core deprecation cycle" -msgstr "ansible-core éžæŽ¨å¥¨ã‚µã‚¤ã‚¯ãƒ«" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:225 -msgid "The deprecation cycle in ``ansible-core`` is normally across 4 feature releases (2.x.y, where the x marks a feature release and the y a bugfix release), so the feature is normally removed in the 4th release after we announce the deprecation. For example, something deprecated in 2.9 will be removed in 2.13, assuming we do not jump to 3.x before that point. The tracking is tied to the number of releases, not the release numbering." -msgstr "``ansible-core`` ã®éžæŽ¨å¥¨ã‚µã‚¤ã‚¯ãƒ«ã¯é€šå¸¸ 4 ã¤ã®æ©Ÿèƒ½ãƒªãƒªãƒ¼ã‚¹ (ãŸã¨ãˆã° 2.x.y ã§ã¯ã€x ã¯æ©Ÿèƒ½ãƒªãƒªãƒ¼ã‚¹ã‚’示ã—ã€y ã¯ãƒã‚°ä¿®æ£ãƒªãƒªãƒ¼ã‚¹ã‚’示ã—ã¾ã™) ã«ã¾ãŸãŒã‚‹ãŸã‚ã€æ©Ÿèƒ½ã¯é€šå¸¸ã€éžæŽ¨å¥¨ã‚’発表ã—ã¦ã‹ã‚‰ 4 番目ã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚ãŸã¨ãˆã°ã€2.9 ã§éžæŽ¨å¥¨ã«ãªã£ãŸã‚‚ã®ã¯ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒãã®ã¾ã¾ 3.x ã«ç¶šãã¨ä»®å®šã™ã‚‹ã¨ã€2.13 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚追跡ã¯ã€ãƒªãƒªãƒ¼ã‚¹ç•ªå·ã§ã¯ãªãã€ãƒªãƒªãƒ¼ã‚¹ã®æ•°ã«é–¢é€£ä»˜ã‘られã¦ã„ã¾ã™ã€‚" - -#: ../../rst/reference_appendices/release_and_maintenance.rst:229 +#: ../../rst/reference_appendices/release_and_maintenance.rst:22 msgid ":ref:`community_committer_guidelines`" msgstr ":ref:`community_committer_guidelines`" -#: ../../rst/reference_appendices/release_and_maintenance.rst:230 +#: ../../rst/reference_appendices/release_and_maintenance.rst:23 msgid "Guidelines for Ansible core contributors and maintainers" msgstr "Ansible ã§ä¸å¿ƒã¨ãªã‚‹è²¢çŒ®è€…ãŠã‚ˆã³ãƒ¡ãƒ³ãƒ†ãƒŠãƒ¼å‘ã‘ガイドライン" -#: ../../rst/reference_appendices/release_and_maintenance.rst:231 +#: ../../rst/reference_appendices/release_and_maintenance.rst:24 msgid ":ref:`testing_strategies`" msgstr ":ref:`testing_strategies`" -#: ../../rst/reference_appendices/release_and_maintenance.rst:232 +#: ../../rst/reference_appendices/release_and_maintenance.rst:25 msgid "Testing strategies" msgstr "ストラテジーã®ãƒ†ã‚¹ãƒˆ" -#: ../../rst/reference_appendices/release_and_maintenance.rst:233 +#: ../../rst/reference_appendices/release_and_maintenance.rst:26 msgid ":ref:`ansible_community_guide`" msgstr ":ref:`ansible_community_guide`" -#: ../../rst/reference_appendices/release_and_maintenance.rst:234 +#: ../../rst/reference_appendices/release_and_maintenance.rst:27 msgid "Community information and contributing" msgstr "ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ãƒ¼æƒ…å ±ãŠã‚ˆã³è²¢çŒ®" -#: ../../rst/reference_appendices/release_and_maintenance.rst:235 +#: ../../rst/reference_appendices/release_and_maintenance.rst:28 msgid "`Development Mailing List <https://groups.google.com/group/ansible-devel>`_" msgstr "`開発メーリングリスト <https://groups.google.com/group/ansible-devel>`_" -#: ../../rst/reference_appendices/release_and_maintenance.rst:236 +#: ../../rst/reference_appendices/release_and_maintenance.rst:29 msgid "Mailing list for development topics" msgstr "開発トピックã®ãƒ¡ãƒ¼ãƒªãƒ³ã‚°ãƒªã‚¹ãƒˆ" @@ -10595,3 +10179,318 @@ msgstr "RHAAP ã¯ã€Red Hat ãŒã‚µãƒãƒ¼ãƒˆã™ã‚‹ Ansible AWX ã®è£½å“ãƒãƒ¼ã‚¸ #~ msgid "Ansible Tower is the downstream Red-Hat supported product version of Ansible AWX. Find out more about Ansible Tower features and how to download it on the `Ansible Tower webpage <https://www.ansible.com/products/tower>`_. Ansible Tower is part of the Red Hat Ansible Automation subscription, and comes bundled with amazing support from Red Hat, Inc." #~ msgstr "Ansible Tower ã¯ã€Red Hat ãŒã‚µãƒãƒ¼ãƒˆã™ã‚‹ Ansible AWX ã®è£½å“ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ (ダウンストリーム) ã§ã™ã€‚Ansible Tower ã®æ©Ÿèƒ½ã¨ãã®ãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰æ–¹æ³•ã®è©³ç´°ã¯ã€`Ansible Tower web ページ <https://www.ansible.com/products/tower>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。Ansible Tower ã¯ã€Red Hat Ansible Automation サブスクリプションã«å«ã¾ã‚Œã€Red Hat, Inc ã®ã‚µãƒãƒ¼ãƒˆãŒåˆ©ç”¨ã§ãã¾ã™ã€‚" +#~ msgid "This section describes release cycles, rules, and maintenance schedules for both Ansible community projects: the Ansible community package and ``ansible-core``. The two projects have different versioning systems, maintenance structures, contents, and workflows." +#~ msgstr "ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€Ansibleコミュニティプãƒã‚¸ã‚§ã‚¯ãƒˆã®ä¸¡æ–¹ (Ansibleコミュニティパッケージã¨``ansible-core``) ã®ãƒªãƒªãƒ¼ã‚¹ã‚µã‚¤ã‚¯ãƒ«ã€ãƒ«ãƒ¼ãƒ«ã€ãŠã‚ˆã³ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ã‚¹ã‚±ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã¤ã„ã¦èª¬æ˜Žã—ã¾ã™ã€‚ã“ã®2ã¤ã®ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ç®¡ç†ã‚·ã‚¹ãƒ†ãƒ ã€ä¿å®ˆæ§‹é€ ã€ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã€ãŠã‚ˆã³ãƒ¯ãƒ¼ã‚¯ãƒ•ãƒãƒ¼ã¯ç•°ãªã‚Šã¾ã™ã€‚" + +#~ msgid "Ansible community package" +#~ msgstr "Ansibleコミュニティパッケージ" + +#~ msgid "Uses new versioning (2.10, then 3.0.0)" +#~ msgstr "æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ç®¡ç†ã‚’使用ã™ã‚‹ï¼ˆ2.10ã€æ¬¡ã«3.0.0）" + +#~ msgid "Continues \"classic Ansible\" versioning (2.10, then 2.11)" +#~ msgstr "従æ¥ã® Ansible ãƒãƒ¼ã‚¸ãƒ§ãƒ³ç®¡ç†ã‚’続行ã™ã‚‹ï¼ˆ2.10ã€æ¬¡ã«2.11）" + +#~ msgid "Follows semantic versioning rules" +#~ msgstr "セマンティックãƒãƒ¼ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°ãƒ«ãƒ¼ãƒ«ã«å¾“ã†" + +#~ msgid "Does not use semantic versioning" +#~ msgstr "セマンティックãƒãƒ¼ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°ã‚’使用ã—ãªã„" + +#~ msgid "Maintains only one version at a time" +#~ msgstr "一度ã«1ã¤ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ã¿ã‚’ç¶æŒã™ã‚‹" + +#~ msgid "Maintains latest version plus two older versions" +#~ msgstr "最新ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¨ä»¥å‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’2ã¤ç¶æŒã™ã‚‹" + +#~ msgid "Includes language, runtime, and selected Collections" +#~ msgstr "言語ã€ãƒ©ãƒ³ã‚¿ã‚¤ãƒ ã€ãŠã‚ˆã³é¸æŠžã—ãŸã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãŒå«ã¾ã‚Œã‚‹" + +#~ msgid "Includes language, runtime, and builtin plugins" +#~ msgstr "言語ã€ãƒ©ãƒ³ã‚¿ã‚¤ãƒ ã€ãŠã‚ˆã³çµ„ã¿è¾¼ã¿ãƒ—ラグインãŒå«ã¾ã‚Œã‚‹" + +#~ msgid "Developed and maintained in Collection repositories" +#~ msgstr "コレクションリãƒã‚¸ãƒˆãƒªã§é–‹ç™ºãŠã‚ˆã³ä¿å®ˆã•ã‚Œã¦ã„ã‚‹" + +#~ msgid "Developed and maintained in ansible/ansible repository" +#~ msgstr "ansible / ansibleリãƒã‚¸ãƒˆãƒªã§é–‹ç™ºãŠã‚ˆã³ä¿å®ˆã•ã‚Œã¦ã„ã‚‹" + +#~ msgid "Many community users install the Ansible community package. The Ansible community package offers the functionality that existed in Ansible 2.9, with more than 85 Collections containing thousands of modules and plugins. The ``ansible-core`` option is primarily for developers and users who want to install only the collections they need." +#~ msgstr "多ãã®ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒAnsibleコミュニティパッケージをインストールã—ã¾ã™ã€‚Ansibleコミュニティパッケージã§ã¯ã€Ansible 2.9ã«å˜åœ¨ã—ã¦ã„ãŸæ©Ÿèƒ½ã¨ã€85を超ãˆã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ (æ•°åƒã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¨ãƒ—ラグインをå«ã‚€) ãŒæä¾›ã•ã‚Œã¾ã™ã€‚``ansible-core``オプションã¯ä¸»ã«ã€å¿…è¦ãªã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã ã‘をインストールã™ã‚‹é–‹ç™ºè€…ã¨ãƒ¦ãƒ¼ã‚¶ãƒ¼å‘ã‘ã§ã™ã€‚" + +#~ msgid "Release cycle overview" +#~ msgstr "リリースサイクルã®æ¦‚è¦" + +#~ msgid "The two community releases are related - the release cycle follows this pattern:" +#~ msgstr "2ã¤ã®ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ãƒªãƒªãƒ¼ã‚¹ã¯é–¢é€£ã—ã¦ãŠã‚Šã€ãƒªãƒªãƒ¼ã‚¹ã‚µã‚¤ã‚¯ãƒ«ã¯ä»¥ä¸‹ã®ã‚ˆã†ãªãƒ‘ターンã«ãªã£ã¦ã„ã¾ã™ã€‚" + +#~ msgid "Release of a new ansible-core major version, for example, ansible-core 2.11" +#~ msgstr "æ–°ã—ã„ansible-coreメジャーãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒªãƒªãƒ¼ã‚¹ï¼ˆansible-core 2.11ãªã©ï¼‰" + +#~ msgid "New release of ansible-core and two prior versions are now maintained (in this case, ansible-base 2.10, Ansible 2.9)" +#~ msgstr "ansible-coreã®æ–°ã—ã„リリースã¨2ã¤å‰ã¾ã§ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒç¶æŒã•ã‚Œã‚‹ã‚ˆã†ã«ï¼ˆä»Šå›žã®å ´åˆã¯ansible-base 2.10ã¨Ansible 2.9）" + +#~ msgid "Work on new features for ansible-core continues in the ``devel`` branch" +#~ msgstr "ansible-coreã®æ–°æ©Ÿèƒ½ã«é–¢ã™ã‚‹ä½œæ¥ã¯``devel``ブランãƒã§ç¶™ç¶šã•ã‚Œã‚‹" + +#~ msgid "Collection freeze (no new Collections or new versions of existing Collections) on the Ansible community package" +#~ msgstr "Ansibleコミュニティパッケージã§ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒ•ãƒªãƒ¼ã‚ºï¼ˆæ–°ã—ã„コレクションや既å˜ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯ã‚ã‚Šã¾ã›ã‚“）" + +#~ msgid "Release candidate for Ansible community package, testing, additional release candidates as necessary" +#~ msgstr "Ansibleコミュニティパッケージã®ãƒªãƒªãƒ¼ã‚¹å€™è£œã€ãƒ†ã‚¹ãƒˆã€å¿…è¦ã«å¿œã˜ã¦è¿½åŠ ã®ãƒªãƒªãƒ¼ã‚¹å€™è£œ" + +#~ msgid "Release of a new Ansible community package major version based on the new ansible-core, for example, Ansible 4.0.0 based on ansible-core 2.11" +#~ msgstr "æ–°ã—ã„ansible-coreã«åŸºã¥ãæ–°ã—ã„Ansibleコミュニティパッケージメジャーãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒªãƒªãƒ¼ã‚¹ï¼ˆä¾‹: ansible-core2.11ã«åŸºã¥ãAnsible4.0.0)" + +#~ msgid "Newest release of the Ansible community package is the only version now maintained" +#~ msgstr "Ansibleコミュニティパッケージã®æœ€æ–°ãƒªãƒªãƒ¼ã‚¹ã ã‘ãŒç¾åœ¨ç¶æŒã•ã‚Œã¦ã„ã‚‹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã‚ã‚‹" + +#~ msgid "Work on new features continues in Collections" +#~ msgstr "新機能ã®ä½œæ¥ã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã§ç¶™ç¶šã•ã‚Œã‚‹" + +#~ msgid "Individual Collections can make multiple minor and/or major releases" +#~ msgstr "個々ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã¯ã€è¤‡æ•°ã®ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ãŠã‚ˆã³/ã¾ãŸã¯ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã‚’作æˆã§ãã‚‹" + +#~ msgid "Minor releases of three maintained ansible-core versions every three weeks (2.11.1)" +#~ msgstr "3ã¤ã®ansible-core管ç†ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’3週間毎ã«ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ï¼ˆ2.11.1）" + +#~ msgid "Minor releases of the single maintained Ansible community package version every three weeks (4.1.0)" +#~ msgstr "Ansibleコミュニティーパッケージã®ç®¡ç†ãƒãƒ¼ã‚¸ãƒ§ãƒ³1ã¤ã‚’3週間毎ã«ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ï¼ˆ4.1.0）" + +#~ msgid "Feature freeze on ansible-core" +#~ msgstr "ansible-core 機能ã®ãƒ•ãƒªãƒ¼ã‚º" + +#~ msgid "Release candidate for ansible-core, testing, additional release candidates as necessary" +#~ msgstr " ansible-core ã®ãƒªãƒªãƒ¼ã‚¹å€™è£œã€ãƒ†ã‚¹ãƒˆã€å¿…è¦ã«å¿œã˜ã¦è¿½åŠ ã®ãƒªãƒªãƒ¼ã‚¹å€™è£œ" + +#~ msgid "Release of the next ansible-core major version, cycle begins again" +#~ msgstr "次ã®ansible-coreメジャーãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒªãƒªãƒ¼ã‚¹ã€‚サイクルã®å†é–‹" + +#~ msgid "Ansible community package release cycle" +#~ msgstr "Ansible コミュニティーパッケージã®ãƒªãƒªãƒ¼ã‚¹ã‚µã‚¤ã‚¯ãƒ«" + +#~ msgid "The Ansible community team typically releases two major versions of the community package per year, on a flexible release cycle that trails the release of ``ansible-core``. This cycle can be extended to allow for larger changes to be properly implemented and tested before a new release is made available. See :ref:`roadmaps` for upcoming release details. Between major versions, we release a new minor version of the Ansible community package every three weeks. Minor releases include new backwards-compatible features, modules and plugins, as well as bug fixes." +#~ msgstr "Ansible コミュニティーãƒãƒ¼ãƒ ã¯é€šå¸¸ã€1å¹´ã«2回メジャーãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’リリースã—ã€æŸ”軟ãªãƒªãƒªãƒ¼ã‚¹ã‚µã‚¤ã‚¯ãƒ«ã§ ``ansible-core`` ã®ãƒªãƒªãƒ¼ã‚¹ã«ç¶šãã¾ã™ã€‚ã“ã®ã‚µã‚¤ã‚¯ãƒ«ã¯ã€æ–°ã—ã„リリースをæä¾›ã™ã‚‹å‰ã«è¦æ¨¡ã®å¤§ãã„変更をæ£ã—ã実装ã—ã¦ãƒ†ã‚¹ãƒˆã§ãるよã†ã«ã€å»¶æœŸã§ãるよã†ã«ãªã£ã¦ã„ã¾ã™ã€‚今後ã®ãƒªãƒªãƒ¼ã‚¹ã®è©³ç´°ã¯ã€:ref:`roadmaps`ã‚’å‚ç…§ã—ã¦ãã ã•ã„。次ã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã‚‹ã¾ã§ã«ã€Ansible コミュニティーパッケージã®æ–°è¦ãƒžã‚¤ãƒŠãƒ¼ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒ3週間毎ã«ãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã¾ã™ã€‚マイナーリリースã«ã¯ã€å¾Œæ–¹äº’æ›æ€§ã®ã‚る機能ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€ãƒ—ラグインã ã‘ã§ãªãã€ãƒã‚°ä¿®æ£ãŒå«ã¾ã‚Œã¾ã™ã€‚" + +#~ msgid "Starting with version 2.10, the Ansible community team guarantees maintenance for only one major community package release at a time. For example, when Ansible 4.0.0 gets released, the team will stop making new 3.x releases. Community members may maintain older versions if desired." +#~ msgstr "ãƒãƒ¼ã‚¸ãƒ§ãƒ³2.10以é™ã€Ansibleコミュニティãƒãƒ¼ãƒ ã¯ã€ä¸€åº¦ã«ä¸»è¦ãªã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ãƒ‘ッケージリリースã®ä¿å®ˆã®ä¿è¨¼ã™ã‚‹ã®ã¯1ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ã¿ã§ã™ã€‚ãŸã¨ãˆã°ã€Ansible ãƒãƒ¼ãƒ ã§ã¯ã€Ansible 4.0.0ãŒãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã‚‹ã¨ã€æ–°ã—ã„3.xリリースã®ä½œæˆã‚’åœæ¢ã—ã¾ã™ã€‚コミュニティメンãƒãƒ¼ã¯ã€å¿…è¦ã«å¿œã˜ã¦å¤ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’ç¶æŒã§ãã¾ã™ã€‚" + +#~ msgid "Older, unmaintained versions of the Ansible community package might contain unfixed security vulnerabilities (*CVEs*). If you are using a release of the Ansible community package that is no longer maintained, we strongly encourage you to upgrade as soon as possible in order to benefit from the latest features and security fixes." +#~ msgstr "メンテナンスã•ã‚Œã¦ã„ãªã„以å‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®Ansibleコミュニティパッケージã«ã¯ã€ä¿®æ£ã•ã‚Œã¦ã„ãªã„ã‚»ã‚ュリティã®è„†å¼±æ€§ï¼ˆ* CVE *）ãŒå«ã¾ã‚Œã¦ã„ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚メンテナンスãŒçµ‚了ã—ãŸAnsibleコミュニティパッケージã®ãƒªãƒªãƒ¼ã‚¹ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ã§ãã‚‹ã ã‘æ—©ãアップグレードã—ã¦ã€æœ€æ–°ã®æ©Ÿèƒ½ã¨ã‚»ã‚ュリティ修æ£ã‚’利用ã™ã‚‹ã“ã¨ã‚’å¼·ããŠå‹§ã‚ã—ã¾ã™ã€‚" + +#~ msgid "Each major release of the Ansible community package accepts the latest released version of each included Collection and the latest released version of ansible-core. For specific schedules and deadlines, see the :ref:`ansible_roadmaps` for each version. Major releases of the Ansible community package can contain breaking changes in the modules and other plugins within the included Collections and/or in core features." +#~ msgstr "Ansible コミュニティーパッケージã®å„メジャーリリースã«ã¯ã€è¿½åŠ ã™ã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã”ã¨ã®æœ€æ–°ã®ãƒªãƒªãƒ¼ã‚¹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¨ã€æœ€æ–°ãƒªãƒªãƒ¼ã‚¹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® ansible-core ã‚’è¿½åŠ ã§ãã¾ã™ã€‚具体的ãªã‚¹ã‚±ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚„期é™ã«ã¤ã„ã¦ã¯ã€å„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®:ref:`ansible_roadmaps`ã‚’å‚ç…§ã—ã¦ãã ã•ã„。Ansible コミュニティーパッケージã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã«å«ã¾ã‚Œã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚„コア機能ã«ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚„ãã®ä»–ã®å¤§è¦æ¨¡ãªå¤‰æ›´ãŒå«ã¾ã‚Œã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "The Ansible community package follows semantic versioning rules. Minor releases of the Ansible community package accept only backwards-compatible changes in included Collections, in other words, not Collections major releases. Collections must also use semantic versioning, so the Collection version numbers reflect this rule. For example, if Ansible 3.0.0 releases with community.general 2.0.0, then all minor releases of Ansible 3.x (such as Ansible 3.1.0 or Ansible 3.5.0) must include a 2.x release of community.general (such as 2.8.0 or 2.9.5) and not 3.x.x or later major releases." +#~ msgstr "Ansibleコミュニティパッケージã¯ã€ã‚»ãƒžãƒ³ãƒ†ã‚£ãƒƒã‚¯ãƒãƒ¼ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°ãƒ«ãƒ¼ãƒ«ã‚’使用ã—ã¾ã™ã€‚Ansibleコミュニティパッケージã®ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ã¯ã€åŒæ¢±ã•ã‚Œã¦ã„るコレクションã¨ä¸‹ä½äº’æ›æ€§ã®ã‚る変更ã®ã¿ã‚’å—ã‘入れã¾ã™ã€‚ã¤ã¾ã‚Šã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã¯å—ã‘入れã¾ã›ã‚“。コレクションもセマンティックãƒãƒ¼ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°ã‚’使用ã™ã‚‹å¿…è¦ãŒã‚ã‚‹ãŸã‚ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ç•ªå·ã‚‚ã“ã®ãƒ«ãƒ¼ãƒ«ã‚’åæ˜ ã—ã¦ã„ã¾ã™ã€‚ãŸã¨ãˆã°ã€community.general 2.0.0 ãŒå«ã¾ã‚Œã‚‹ Ansible 3.0.0 リリースã®å ´åˆã«ã¯ã€Ansible 3.x ã®å…¨ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ (Ansbile 3.1.0 ã¾ãŸã¯ Ansible 3.5.0ãªã©)ã«ã¯ã€3.0.0 以é™ã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã§ã¯ãªã〠community.general (2.8.0 ã¾ãŸã¯ 2.9.5ãªã©)ã®2.xリリースをå«ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "Work in Collections is tracked within the individual Collection repositories." +#~ msgstr "コレクションã§ã®ä½œæ¥ã¯ã€å€‹ã€…ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãƒªãƒã‚¸ãƒˆãƒªå†…ã§è¿½è·¡ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "You can refer to the :ref:`Ansible package porting guides<porting_guides>` for tips on updating your playbooks to run on newer versions of Ansible. For Ansible 2.10 and later releases, you can install the Ansible package with ``pip``. See :ref:`intro_installation_guide` for details. For older releases, you can download the Ansible release from `<https://releases.ansible.com/ansible/>`_." +#~ msgstr "Ansible Playbook ã‚’æ›´æ–°ã—ã¦æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§å®Ÿè¡Œã™ã‚‹ã¨ãã®ãƒ’ントã«ã¤ã„ã¦ã¯ã€ã€Œ:ref:`Ansible package porting guides<porting_guides>`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。Ansible 2.10 以é™ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€``pip`` 㧠Ansible パッケージをインストールã§ãã¾ã™ã€‚詳細ã¯ã€ã€Œ:ref:`intro_installation_guide`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。å¤ã„リリースã§ã¯ã€Ansible リリース㯠`<https://releases.ansible.com/ansible/>`_ ã‹ã‚‰ãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰ã§ãã¾ã™ã€‚" + +#~ msgid "This table links to the release notes for each major Ansible release. These release notes (changelogs) contain the dates and significant changes in each minor release." +#~ msgstr "以下ã®è¡¨ã«ã¯ã€Ansible ã®å„メジャーリリースã®ãƒªãƒªãƒ¼ã‚¹ãƒŽãƒ¼ãƒˆã¸ã®ãƒªãƒ³ã‚¯ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ã“ã®ã‚ˆã†ãªãƒªãƒªãƒ¼ã‚¹ãƒŽãƒ¼ãƒˆ (変更ãƒã‚°) ã«ã¯ã€å„マイナーリリースã®æ—¥ä»˜ã‚„ã€å¤§ããªå¤‰æ›´ãŒå«ã¾ã‚Œã¾ã™ã€‚" + +#~ msgid "Ansible Community Package Release" +#~ msgstr "Ansible コミュニティーパッケージã®ãƒªãƒªãƒ¼ã‚¹" + +#~ msgid "Status" +#~ msgstr "ステータス" + +#~ msgid "5.0.0" +#~ msgstr "5.0.0" + +#~ msgid "In development (unreleased)" +#~ msgstr "é–‹ç™ºä¸ (未リリース)" + +#~ msgid "`4.x Release Notes`_" +#~ msgstr "`4.x Release Notes`_" + +#~ msgid "Current" +#~ msgstr "ç¾è¡Œ" + +#~ msgid "`3.x Release Notes`_" +#~ msgstr "`3.x Release Notes`_" + +#~ msgid "Unmaintained (end of life)" +#~ msgstr "メンテナンス対象外 (エンドオフライフ)" + +#~ msgid "`2.10 Release Notes`_" +#~ msgstr "`2.10 Release Notes`_" + +#~ msgid "ansible-core release cycle" +#~ msgstr "ansible-core リリースサイクル" + +#~ msgid "``ansible-core`` is developed and released on a flexible release cycle. This cycle can be extended in order to allow for larger changes to be properly implemented and tested before a new release is made available. See :ref:`roadmaps` for upcoming release details." +#~ msgstr "``ansible-core`` ã¯ã€æŸ”軟ãªãƒªãƒªãƒ¼ã‚¹ã‚µã‚¤ã‚¯ãƒ«ã§é–‹ç™ºãŠã‚ˆã³ãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã¾ã™ã€‚ã“ã®ã‚µã‚¤ã‚¯ãƒ«ã¯ã€å¤§è¦æ¨¡ãªå¤‰æ›´ã‚’æ£ã—ã実装ã—ã¦ã€ãƒ†ã‚¹ãƒˆã—ã¦ã‹ã‚‰æ–°ã—ã„リリースãŒå…¬é–‹ã•ã‚Œã‚‹ã‚ˆã†ã«ã€å»¶é•·ã™ã‚‹ã“ã¨ãŒå¯èƒ½ã§ã™ã€‚今後ã®ãƒªãƒªãƒ¼ã‚¹ã®è©³ç´°ã¯ã€ã€Œ:ref:`roadmaps`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "``ansible-core`` has a graduated maintenance structure that extends to three major releases. For more information, read about the :ref:`development_and_stable_version_maintenance_workflow` or see the chart in :ref:`release_schedule` for the degrees to which current releases are maintained." +#~ msgstr "``ansible-core`` ã«ã¯ã€3 ã¤ã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã§å±•é–‹ã•ã‚Œã‚‹æ®µéšŽçš„ãªãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹æ§‹é€ ãŒã‚ã‚Šã¾ã™ã€‚詳細ã¯ã€ã€Œ:ref:`development_and_stable_version_maintenance_workflow`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。ã¾ãŸã€ç¾åœ¨ã®ãƒªãƒªãƒ¼ã‚¹ãŒã©ã®ç¨‹åº¦ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ã•ã‚Œã¦ã„ã‚‹ã‹ã«ã¤ã„ã¦ã¯ã€:ref:`release_schedule` ã®è¡¨ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "Older, unmaintained versions of ``ansible-core`` can contain unfixed security vulnerabilities (*CVEs*). If you are using a release of ``ansible-core`` that is no longer maintained, we strongly encourage you to upgrade as soon as possible to benefit from the latest features and security fixes. ``ansible-core`` maintenance continues for 3 releases. Thus the latest release receives security and general bug fixes when it is first released, security and critical bug fixes when the next ``ansible-core`` version is released, and **only** security fixes once the follow on to that version is released." +#~ msgstr "``ansible-core``ã®ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ã•ã‚Œã¦ã„ãªã„以å‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«ã¯ã€ã‚»ã‚ュリティー脆弱性 (*CVE*) ãŒå«ã¾ã‚Œã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚ä¿å®ˆã®ãªã„``ansible-core``ã®ãƒªãƒªãƒ¼ã‚¹ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã«ã¯ã€æœ€æ–°ã®æ©Ÿèƒ½ãŠã‚ˆã³ã‚»ã‚ュリティー修æ£ã‚’活用ã§ãるよã†ã«ã€ã™ãã«ã‚¢ãƒƒãƒ—グレードã™ã‚‹ã“ã¨ã‚’å¼·ã推奨ã—ã¾ã™ã€‚``ansible-core``ã®ä¿å®ˆã¯ã€3リリース分継続ã•ã‚Œã¾ã™ã€‚ãã®ãŸã‚ã€æœ€æ–°ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€åˆå›žãƒªãƒªãƒ¼ã‚¹æ™‚ã«ã‚»ã‚ュリティーã¨ä¸€èˆ¬çš„ãªãƒã‚°ä¿®æ£ãŒã€æ¬¡ã®``ansible-core``ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã‚‹ã¨ã€ã‚»ã‚ュリティーã¨é‡å¤§ãªãƒã‚°ä¿®æ£ãŒã€ãã®æ¬¡ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã‚‹ã¨ã€ã‚»ã‚ュリティー修æ£**ã®ã¿**ãŒæä¾›ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "You can refer to the :ref:`core_porting_guides` for tips on updating your playbooks to run on newer versions of ``ansible-core``." +#~ msgstr "Playbook ã‚’æ›´æ–°ã—ã¦``ansible-core`` ã®æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§å®Ÿè¡Œã™ã‚‹ã¨ãã®ãƒ’ントã¯ã€ã€Œ:ref:`core_porting_guides`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "You can install ``ansible-core`` with ``pip``. See :ref:`intro_installation_guide` for details." +#~ msgstr "``pip`` 㧠``ansible-core`` をインストールã§ãã¾ã™ã€‚詳細ã¯ã€ã€Œ:ref:`intro_installation_guide`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "This table links to the release notes for each major ``ansible-core`` release. These release notes (changelogs) contain the dates and significant changes in each minor release." +#~ msgstr "以下ã®è¡¨ã«ã¯ã€``ansible-core`` ã®å„メジャーリリースã®ãƒªãƒªãƒ¼ã‚¹ãƒŽãƒ¼ãƒˆã¸ã®ãƒªãƒ³ã‚¯ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ã“ã®ã‚ˆã†ãªãƒªãƒªãƒ¼ã‚¹ãƒŽãƒ¼ãƒˆ (変更ãƒã‚°) ã«ã¯ã€å„マイナーリリースã®æ—¥ä»˜ã‚„ã€å¤§ããªå¤‰æ›´ãŒå«ã¾ã‚Œã¾ã™ã€‚" + +#~ msgid "``ansible-core`` / ``ansible-base`` Release" +#~ msgstr "``ansible-core`` / ``ansible-base`` リリース" + +#~ msgid "devel" +#~ msgstr "devel" + +#~ msgid "In development (ansible-core 2.12 unreleased, trunk)" +#~ msgstr "é–‹ç™ºä¸ (未リリース㮠ansible-core 2.12 (trunk))" + +#~ msgid "`2.11 ansible-core Release Notes`_" +#~ msgstr "`2.11 ansible-core Release Notes`_" + +#~ msgid "Maintained (security **and** general bug fixes)" +#~ msgstr "メンテナンス対象 (ã‚»ã‚ュリティー **ãŠã‚ˆã³** 一般的ãªãƒã‚°ã®ä¿®æ£)" + +#~ msgid "`2.10 ansible-base Release Notes`_" +#~ msgstr "`2.10 ansible-base Release Notes`_" + +#~ msgid "Maintained (security **and** critical bug fixes)" +#~ msgstr "メンテナンス対象 (ã‚»ã‚ュリティー **ãŠã‚ˆã³** é‡å¤§ãªãƒã‚°ã®ä¿®æ£)" + +#~ msgid "`2.9 Release Notes`_" +#~ msgstr "`2.9 Release Notes`_" + +#~ msgid "Maintained (pre-collections) (security fixes only)" +#~ msgstr "ä¿å®ˆã‚り（事å‰åŽé›†ï¼‰ï¼ˆã‚»ã‚ュリティ修æ£ã®ã¿ï¼‰" + +#~ msgid "`2.8 Release Notes`_" +#~ msgstr "`2.8 Release Notes`_" + +#~ msgid "`2.7 Release Notes`_" +#~ msgstr "`2.7 Release Notes`_" + +#~ msgid "`2.6 Release Notes`_" +#~ msgstr "`2.6 Release Notes`_" + +#~ msgid "`2.5 Release Notes`_" +#~ msgstr "`2.5 リリースノート`_" + +#~ msgid "<2.5" +#~ msgstr "2.5 よりå‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³" + +#~ msgid "Preparing for a new release" +#~ msgstr "æ–°ã—ã„リリースã®æº–å‚™" + +#~ msgid "Feature freezes" +#~ msgstr "機能フリーズ" + +#~ msgid "During final preparations for a new release, core developers and maintainers focus on improving the release candidate, not on adding or reviewing new features. We may impose a feature freeze." +#~ msgstr "æ–°ã—ã„リリースã®æœ€çµ‚準備ä¸ã€ã‚³ã‚¢é–‹ç™ºè€…ã¨ãƒ¡ãƒ³ãƒ†ãƒŠã¯ã€æ–°æ©Ÿèƒ½ã®è¿½åŠ やレビューã§ã¯ãªãã€ãƒªãƒªãƒ¼ã‚¹å€™è£œã®æ”¹å–„ã«é›†ä¸ã—ã¾ã™ã€‚機能フリーズを指示ã™ã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "A feature freeze means that we delay new features and fixes that are not related to the pending release so we can ship the new release as soon as possible." +#~ msgstr "機能フリーズã¨ã¯ã€ä¿ç•™ä¸ã®ãƒªãƒªãƒ¼ã‚¹ã«é–¢é€£ã®ãªã„新機能や修æ£ã‚’é…らã›ã¦ã€æ–°ã—ã„リリースをã§ãã‚‹ã ã‘æ—©ã出è·ã§ãるよã†ã«ã™ã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚" + +#~ msgid "Release candidates" +#~ msgstr "リリースã®å€™è£œ (Release Candidate)" + +#~ msgid "We create at least one release candidate before each new major release of Ansible or ``ansible-core``. Release candidates allow the Ansible community to try out new features, test existing playbooks on the release candidate, and report bugs or issues they find." +#~ msgstr "Ansibleã¾ãŸã¯``ansible-core``ã®æ–°ã—ã„メジャーリリースã®å‰ã«æ¯Žå›žã€å°‘ãªãã¨ã‚‚1ã¤ã®ãƒªãƒªãƒ¼ã‚¹å€™è£œã‚’作æˆã—ã¾ã™ã€‚リリース候補を使用ã™ã‚‹ã“ã¨ã§ã€Ansibleコミュニティã¯æ–°æ©Ÿèƒ½ã‚’試ã—ãŸã‚Šã€ãƒªãƒªãƒ¼ã‚¹å€™è£œã§æ—¢å˜ã®Playbookをテストã—ãŸã‚Šã€è¦‹ã¤ã‹ã£ãŸãƒã‚°ã‚„å•é¡Œã‚’å ±å‘Šã—ãŸã‚Šã§ãã¾ã™ã€‚" + +#~ msgid "Ansible and ``ansible-core`` tag the first release candidate (RC1) which is usually scheduled to last five business days. If no major bugs or issues are identified during this period, the release candidate becomes the final release." +#~ msgstr "Ansible ãŠã‚ˆã³ ``ansible-core`` ã¯ã€æœ€åˆã®ãƒªãƒªãƒ¼ã‚¹å€™è£œã®ã‚¿ã‚° (RC1) ãŒä»˜ã‘られã¾ã™ã€‚通常ã€RC1 ã¯æœ€å¾Œã®5å–¶æ¥æ—¥ã«ã‚¹ã‚±ã‚¸ãƒ¥ãƒ¼ãƒ«ã•ã‚Œã¾ã™ã€‚ã“ã®æœŸé–“ã«ãƒ¡ã‚¸ãƒ£ãƒ¼ãªãƒã‚°ã‚„å•é¡ŒãŒç‰¹å®šã•ã‚Œãªã„å ´åˆã«ã¯ã€ãƒªãƒªãƒ¼ã‚¹å€™è£œãŒæœ€çµ‚リリースã¨ãªã‚Šã¾ã™ã€‚" + +#~ msgid "If there are major problems with the first candidate, the team and the community fix them and tag a second release candidate (RC2). This second candidate lasts for a shorter duration than the first. If no problems have been reported for an RC2 after two business days, the second release candidate becomes the final release." +#~ msgstr "最åˆã®å€™è£œã«å¤§ããªå•é¡ŒãŒã‚ã‚‹å ´åˆã¯ã€ãƒãƒ¼ãƒ ãŠã‚ˆã³ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ãƒ¼ãŒä¿®æ£ã‚’åŠ ãˆã¦ã€2 番目ã®å€™è£œã®ã‚¿ã‚° (RC2) ãŒä»˜ã‘られã¾ã™ã€‚2 番目ã®å€™è£œã¯ã€1 番目よりも期間ã¯çŸããªã‚Šã¾ã™ã€‚2 å–¶æ¥æ—¥ãŒçµŒéŽã—ã¦å•é¡ŒãŒå ±å‘Šã•ã‚Œãªã„å ´åˆã¯ã€ã“ã®2番目ã®ãƒªãƒªãƒ¼ã‚¹å€™è£œãŒæœ€çµ‚çš„ãªãƒªãƒªãƒ¼ã‚¹ã¨ãªã‚Šã¾ã™ã€‚" + +#~ msgid "If there are major problems in RC2, the cycle begins again with another release candidate and repeats until the maintainers agree that all major problems have been fixed." +#~ msgstr "RC2ã«é‡å¤§ãªå•é¡ŒãŒã‚ã‚‹å ´åˆã«ã¯ã€ã‚µã‚¤ã‚¯ãƒ«ã¯åˆ¥ã®ãƒªãƒªãƒ¼ã‚¹å€™è£œã‹ã‚‰å†é–‹ã•ã‚Œã€ã™ã¹ã¦ã®ä¸»è¦ãªå•é¡ŒãŒä¿®æ£ã•ã‚ŒãŸã“ã¨ã«ãƒ¡ãƒ³ãƒ†ãƒŠãŒåŒæ„ã™ã‚‹ã¾ã§ç¹°ã‚Šè¿”ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "Development and maintenance workflows" +#~ msgstr "開発ã¨ä¿å®ˆã®ãƒ¯ãƒ¼ã‚¯ãƒ•ãƒãƒ¼" + +#~ msgid "In between releases, the Ansible community develops new features, maintains existing functionality, and fixes bugs in ``ansible-core`` and in the collections included in the Ansible community package." +#~ msgstr "次ã®ãƒªãƒªãƒ¼ã‚¹ã¾ã§ã®é–“ã«ã€Ansibleコミュニティã¯æ–°ã—ã„機能を開発ã—ã¦æ—¢å˜ã®æ©Ÿèƒ½ã®ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ã‚’è¡Œã„ã€``ansible-core`` ã‚„ Ansible コミュニティーパッケージã«å«ã¾ã‚Œã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒã‚°ã‚’ä¿®æ£ã—ã¾ã™ã€‚" + +#~ msgid "Ansible community package workflow" +#~ msgstr "Ansible コミュニティパッケージã®ãƒ¯ãƒ¼ã‚¯ãƒ•ãƒãƒ¼" + +#~ msgid "The Ansible community develops and maintains the features and functionality included in the Ansible community package in Collections repositories, with a workflow that looks like this:" +#~ msgstr "Ansibleコミュニティã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãƒªãƒã‚¸ãƒˆãƒªã®Ansibleコミュニティパッケージã«å«ã¾ã‚Œã‚‹æ©Ÿèƒ½ã‚’開発ãŠã‚ˆã³ä¿å®ˆã—ã¾ã™ã€‚ワークフãƒãƒ¼ã¯æ¬¡ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" + +#~ msgid "Developers add new features and bug fixes to the individual Collections, following each Collection's rules on contributing." +#~ msgstr "開発者ã¯ã€è²¢çŒ®ã«é–¢ã™ã‚‹å„コレクションã®ãƒ«ãƒ¼ãƒ«ã«å¾“ã£ã¦ã€å€‹ã€…ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«æ–°æ©Ÿèƒ½ã¨ãƒã‚°ä¿®æ£ã‚’è¿½åŠ ã™ã‚‹ã€‚" + +#~ msgid "Each new feature and each bug fix includes a changelog fragment describing the work." +#~ msgstr "å„新機能ã¨å„ãƒã‚°ä¿®æ£ã«ã¯ã€ä½œæ¥ã‚’説明ã™ã‚‹å¤‰æ›´ãƒã‚°ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆãŒå«ã¾ã‚Œã¦ã„る。" + +#~ msgid "Release engineers create a minor release for the current version every three weeks to ensure that the latest bug fixes are available to users." +#~ msgstr "リリースエンジニアã¯ã€æœ€æ–°ã®ãƒã‚°ä¿®æ£ã‚’ユーザーãŒåˆ©ç”¨ã§ãるよã†ã«ã€ç¾åœ¨ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ã‚’3週間ã”ã¨ã«ä½œæˆã™ã‚‹ã€‚" + +#~ msgid "At the end of the development period, the release engineers announce which Collections, and which major version of each included Collection, will be included in the next release of the Ansible community package. New Collections and new major versions may not be added after this, and the work of creating a new release begins." +#~ msgstr "開発期間ã®çµ‚ã‚ã‚Šã«ã€ãƒªãƒªãƒ¼ã‚¹ã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ã¯ã€Ansibleコミュニティパッケージã®æ¬¡ã®ãƒªãƒªãƒ¼ã‚¹ã«å«ã¾ã‚Œã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã¨ã€è¿½åŠ 済ã¿ã®å„コレクションã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’発表ã—ã¾ã™ã€‚ã“れ以é™ã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãŠã‚ˆã³ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯æ–°ãŸã«è¿½åŠ ã§ããšã€æ–°ã—ã„リリースã®ä½œæˆæº–å‚™ãŒé–‹å§‹ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "We generally do not provide fixes for unmaintained releases of the Ansible community package, however, there can sometimes be exceptions for critical issues." +#~ msgstr "通常ã€Ansible コミュニティーパッケージã§ä¿å®ˆã•ã‚Œã¦ã„ãªã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«å¯¾ã™ã‚‹ä¿®æ£ã¯æä¾›ã—ã¦ã„ã¾ã›ã‚“ãŒã€é‡å¤§ãªå•é¡Œã«é–¢ã—ã¦ã¯ä¾‹å¤–ã§å¯¾å¿œã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "Some Collections are maintained by the Ansible team, some by Partner organizations, and some by community teams. For more information on adding features or fixing bugs in Ansible-maintained Collections, see :ref:`contributing_maintained_collections`." +#~ msgstr "Ansibleãƒãƒ¼ãƒ ã€ãƒ‘ートナー組織ã€ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ãƒãƒ¼ãƒ ãŒã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’ãã‚Œãžã‚Œéƒ¨åˆ†çš„ã«ç®¡ç†ã—ã¦ã„ã¾ã™ã€‚ Ansibleã§ç®¡ç†ã•ã‚Œã¦ã„るコレクションã®æ©Ÿèƒ½ã®è¿½åŠ ã‚„ãƒã‚°ã®ä¿®æ£ã®è©³ç´°ã«ã¤ã„ã¦ã¯ã€:ref:`contributing_maintained_collections` ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "ansible-core workflow" +#~ msgstr "ansible-core ワークフãƒãƒ¼" + +#~ msgid "The Ansible community develops and maintains ``ansible-core`` on GitHub_, with a workflow that looks like this:" +#~ msgstr "Ansibleコミュニティã¯ã€GitHub_ã®``ansible-core``ã§é–‹ç™ºã¨ç¶æŒã‚’è¡Œã£ã¦ãŠã‚Šã€æ¬¡ã®ã‚ˆã†ãªãƒ¯ãƒ¼ã‚¯ãƒ•ãƒãƒ¼ã‚’使用ã—ã¾ã™ã€‚" + +#~ msgid "Developers add new features and bug fixes to the ``devel`` branch." +#~ msgstr "開発者ã¯ã€``devel``ブランãƒã«æ–°æ©Ÿèƒ½ã¨ãƒã‚°ä¿®æ£ã‚’è¿½åŠ ã™ã‚‹ã€‚" + +#~ msgid "The development team backports bug fixes to one, two, or three stable branches, depending on the severity of the bug. They do not backport new features." +#~ msgstr "開発ãƒãƒ¼ãƒ ã¯ã€ãƒã‚°ã®é‡å¤§åº¦ã«å¿œã˜ã¦ã€ãƒã‚°ä¿®æ£ã‚’1ã¤ã€2ã¤ã€ã¾ãŸã¯3ã¤ã®å®‰å®šã—ãŸãƒ–ランãƒã«ãƒãƒƒã‚¯ãƒãƒ¼ãƒˆã—ã€æ–°æ©Ÿèƒ½ã®ãƒãƒƒã‚¯ãƒãƒ¼ãƒˆã¯è¡Œã‚ãªã„。" + +#~ msgid "Release engineers create a minor release for each maintained version every three weeks to ensure that the latest bug fixes are available to users." +#~ msgstr "リリースエンジニアã¯ã€æœ€æ–°ã®ãƒã‚°ä¿®æ£ã‚’ユーザーãŒåˆ©ç”¨ã§ãるよã†ã«ã€å„ä¿å®ˆãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®ãƒžã‚¤ãƒŠãƒ¼ãƒªãƒªãƒ¼ã‚¹ã‚’3週間ã”ã¨ã«ä½œæˆã™ã‚‹ã€‚" + +#~ msgid "At the end of the development period, the release engineers impose a feature freeze and the work of creating a new release begins." +#~ msgstr "開発期間ã®çµ‚ã‚ã‚Šã«ã€ãƒªãƒªãƒ¼ã‚¹ã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ã¯æ©Ÿèƒ½ã‚’フリーズã—ã€æ–°ã—ã„リリースã®æº–備を開始ã™ã‚‹ã€‚" + +#~ msgid "We generally do not provide fixes for unmaintained releases of ``ansible-core``, however, there can sometimes be exceptions for critical issues." +#~ msgstr "通常ã€ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ã•ã‚Œã¦ã„ãªã„``ansible-core``リリースã«å¯¾ã™ã‚‹ä¿®æ£ã¯æä¾›ã—ã¦ã„ã¾ã›ã‚“ãŒã€é‡å¤§ãªå•é¡Œã«é–¢ã—ã¦ã¯ä¾‹å¤–ã§å¯¾å¿œã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "For more information on adding features or fixing bugs in ``ansible-core`` see :ref:`community_development_process`." +#~ msgstr "``ansible-core`` ã®æ©Ÿèƒ½ã®è¿½åŠ ã¾ãŸã¯ãƒã‚°ã®ä¿®æ£ã®è©³ç´°ã«ã¤ã„ã¦ã¯ã€:ref:`community_development_process`ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "Changelogs" +#~ msgstr "変更ãƒã‚° (Changelog)" + +#~ msgid "We generate changelogs based on fragments. When creating new features for existing modules and plugins or fixing bugs, create a changelog fragment describing the change. A changelog entry is not needed for new modules or plugins. Details for those items will be generated from the module documentation." +#~ msgstr "変更ãƒã‚°ã¯ã€ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã«åŸºã¥ã„ã¦ç”Ÿæˆã•ã‚Œã¾ã™ã€‚æ—¢å˜ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚„プラグインã®æ–°ã—ã„機能を作æˆã—ãŸã‚Šã€ãƒã‚°ã‚’ä¿®æ£ã—ãŸã‚Šã™ã‚‹ã¨ãã¯ã€å¤‰æ›´ç‚¹ã‚’記述ã—ãŸå¤‰æ›´ãƒã‚°ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã‚’作æˆã—ã¾ã™ã€‚変更ãƒã‚°ã®ã‚¨ãƒ³ãƒˆãƒªãƒ¼ã¯ã€æ–°ã—ã„モジュールやプラグインã«ã¯å¿…è¦ã‚ã‚Šã¾ã›ã‚“。ãれらã®é …ç›®ã®è©³ç´°ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ‰ã‚ュメントã‹ã‚‰ç”Ÿæˆã•ã‚Œã¾ã™ã€‚" + +#~ msgid "To add changelog fragments to Collections in the Ansible community package, we recommend the `antsibull-changelog utility <https://github.com/ansible-community/antsibull-changelog/blob/main/docs/changelogs.rst>`_." +#~ msgstr "Ansibleコミュニティパッケージã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«å¤‰æ›´ãƒã‚°ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã‚’è¿½åŠ ã™ã‚‹ã«ã¯ã€`antsibull-changelog utility <https://github.com/ansible-community/antsibull-changelog/blob/main/docs/changelogs.rst>`_を推奨ã—ã¾ã™ã€‚" + +#~ msgid "To add changelog fragments for new features and bug fixes in ``ansible-core``, see the :ref:`changelog examples and instructions<changelogs_how_to>` in the Community Guide." +#~ msgstr "``ansible-core``ã«æ–°æ©Ÿèƒ½ã¨ãƒã‚°ä¿®æ£ã®å¤‰æ›´ãƒã‚°ãƒ•ãƒ©ã‚°ãƒ¡ãƒ³ãƒˆã‚’è¿½åŠ ã™ã‚‹ã«ã¯ã€ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ã‚¬ã‚¤ãƒ‰ã®:ref:`changelog examples and instructions<changelogs_how_to>`ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "Deprecation cycles" +#~ msgstr "éžæŽ¨å¥¨ã‚µã‚¤ã‚¯ãƒ«" + +#~ msgid "Sometimes we remove a feature, normally in favor of a reimplementation that we hope does a better job. To do this we have a deprecation cycle. First we mark a feature as 'deprecated'. This is normally accompanied with warnings to the user as to why we deprecated it, what alternatives they should switch to and when (which version) we are scheduled to remove the feature permanently." +#~ msgstr "通常ã€å†å®Ÿè£…ã—ã¦ã‚¸ãƒ§ãƒ–実行ã®æ”¹å–„を希望ã™ã‚‹å ´åˆãªã©ã€æ©Ÿèƒ½ã‚’削除ã™ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ã“れを行ã†ãŸã‚ã«ã€éžæŽ¨å¥¨ã®ã‚µã‚¤ã‚¯ãƒ«ãŒã‚ã‚Šã¾ã™ã€‚ã¾ãšã€æ©Ÿèƒ½ã‚’「éžæŽ¨å¥¨ã€ã¨ã—ã¦ãƒžãƒ¼ã‚¯ã—ã¾ã™ã€‚ã“ã‚Œã«ã¯é€šå¸¸ã€éžæŽ¨å¥¨ã«ãªã£ãŸç†ç”±ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒåˆ‡ã‚Šæ›¿ãˆã‚‹å¿…è¦ã®ã‚る代替手段ã€ãŠã‚ˆã³æ©Ÿèƒ½ã‚’完全ã«å‰Šé™¤ã™ã‚‹äºˆå®šã®æ™‚期 (ãƒãƒ¼ã‚¸ãƒ§ãƒ³) ã«é–¢ã™ã‚‹è¦å‘ŠãŒä¼´ã„ã¾ã™ã€‚" + +#~ msgid "Ansible community package deprecation cycle" +#~ msgstr "Ansibleコミュニティパッケージã®éžæŽ¨å¥¨ã‚µã‚¤ã‚¯ãƒ«" + +#~ msgid "Since Ansible is a package of individual collections, the deprecation cycle depends on the collection maintainers. We recommend the collection maintainers deprecate a feature in one Ansible major version and do not remove that feature for one year, or at least until the next major Ansible version. For example, deprecate the feature in 3.1.0, and do not remove the feature until 5.0.0, or 4.0.0 at the earliest. Collections should use semantic versioning, such that the major collection version cannot be changed within an Ansible major version. Thus the removal should not happen before the next major Ansible community package release. This is up to each collection maintainer and cannot be guaranteed." +#~ msgstr "Ansible ã¯å€‹åˆ¥ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒ‘ッケージã§ã‚ã‚‹ãŸã‚ã€éžæŽ¨å¥¨ã®ã‚µã‚¤ã‚¯ãƒ«ã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒ¡ãƒ³ãƒ†ãƒŠãƒ¼ã«ã‚ˆã£ã¦ç•°ãªã‚Šã¾ã™ã€‚コレクションメンテナー㯠1 ã¤ã® Ansible メジャーãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã“ã®æ©Ÿèƒ½ã‚’éžæŽ¨å¥¨ã«ã—ã€1 å¹´é–“ã§ãã®æ©Ÿèƒ½ã‚’削除ã™ã‚‹ã‹ã€å°‘ãªãã¨ã‚‚次㮠Ansible ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¾ã§ã«å‰Šé™¤ã—ãªã„ã“ã¨ã‚’推奨ã—ã¾ã™ã€‚ãŸã¨ãˆã°ã€3.1.0 ã§ã“ã®æ©Ÿèƒ½ã‚’éžæŽ¨å¥¨ã«ã—ãŸå ´åˆã¯ã€æœ€ä½Žã§ã‚‚ 5.0.0 ã¾ãŸã¯ 4.0.0 ã¾ã§ã®æ©Ÿèƒ½ã‚’削除ã—ãªã„ã§ãã ã•ã„。コレクションã¯ã‚»ãƒžãƒ³ãƒ†ã‚£ãƒƒã‚¯ãƒãƒ¼ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°ã‚’使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã—ãŸãŒã£ã¦ã€ãƒ¡ã‚¸ãƒ£ãƒ¼ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯ã€Ansible メジャーãƒãƒ¼ã‚¸ãƒ§ãƒ³å†…ã§å¤‰æ›´ã§ãã¾ã›ã‚“。ã—ãŸãŒã£ã¦ã€æ¬¡ã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒªãƒªãƒ¼ã‚¹ã® Ansible コミュニティーパッケージリリースã®å‰ã«å‰Šé™¤ã™ã‚‹ã“ã¨ã¯ã§ãã¾ã›ã‚“。ã“ã‚Œã¯ã€å„コレクションã®ãƒ¡ãƒ³ãƒ†ãƒŠãƒ¼ã®å½¹å‰²ã§ã‚ã‚Šã€ä¿è¨¼ã•ã‚Œã¦ã„ã‚‹ã‚‚ã®ã§ã¯ã‚ã‚Šã¾ã›ã‚“。" + +#~ msgid "ansible-core deprecation cycle" +#~ msgstr "ansible-core éžæŽ¨å¥¨ã‚µã‚¤ã‚¯ãƒ«" + +#~ msgid "The deprecation cycle in ``ansible-core`` is normally across 4 feature releases (2.x.y, where the x marks a feature release and the y a bugfix release), so the feature is normally removed in the 4th release after we announce the deprecation. For example, something deprecated in 2.9 will be removed in 2.13, assuming we do not jump to 3.x before that point. The tracking is tied to the number of releases, not the release numbering." +#~ msgstr "``ansible-core`` ã®éžæŽ¨å¥¨ã‚µã‚¤ã‚¯ãƒ«ã¯é€šå¸¸ 4 ã¤ã®æ©Ÿèƒ½ãƒªãƒªãƒ¼ã‚¹ (ãŸã¨ãˆã° 2.x.y ã§ã¯ã€x ã¯æ©Ÿèƒ½ãƒªãƒªãƒ¼ã‚¹ã‚’示ã—ã€y ã¯ãƒã‚°ä¿®æ£ãƒªãƒªãƒ¼ã‚¹ã‚’示ã—ã¾ã™) ã«ã¾ãŸãŒã‚‹ãŸã‚ã€æ©Ÿèƒ½ã¯é€šå¸¸ã€éžæŽ¨å¥¨ã‚’発表ã—ã¦ã‹ã‚‰ 4 番目ã®ãƒªãƒªãƒ¼ã‚¹ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚ãŸã¨ãˆã°ã€2.9 ã§éžæŽ¨å¥¨ã«ãªã£ãŸã‚‚ã®ã¯ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒãã®ã¾ã¾ 3.x ã«ç¶šãã¨ä»®å®šã™ã‚‹ã¨ã€2.13 ã§å‰Šé™¤ã•ã‚Œã¾ã™ã€‚追跡ã¯ã€ãƒªãƒªãƒ¼ã‚¹ç•ªå·ã§ã¯ãªãã€ãƒªãƒªãƒ¼ã‚¹ã®æ•°ã«é–¢é€£ä»˜ã‘られã¦ã„ã¾ã™ã€‚" + diff --git a/docs/docsite/rst/locales/ja/LC_MESSAGES/roadmap.po b/docs/docsite/rst/locales/ja/LC_MESSAGES/roadmap.po index 0d4763a1..158307d6 100644 --- a/docs/docsite/rst/locales/ja/LC_MESSAGES/roadmap.po +++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/roadmap.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Ansible devel\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-10-05 13:53+0200\n" +"POT-Creation-Date: 2021-11-09 14:07+0100\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" @@ -497,12 +497,12 @@ msgid "Ansible-5.0.0 release." msgstr "Ansible-5.0.0 リリース" #: ../../rst/roadmap/COLLECTIONS_5.rst -msgid "2022-01-04" -msgstr "2022-01-04" +msgid "2021-12-21" +msgstr "2021-12-21" #: ../../rst/roadmap/COLLECTIONS_5.rst:34 -msgid "Release of Ansible-5.1.0 (bugfix + compatible features: every three weeks. Note: this comes 4 week after 5.0.0 due to the winter holiday season)." -msgstr "Ansible-5.1.0ã®ãƒªãƒªãƒ¼ã‚¹ï¼ˆãƒã‚°ä¿®æ£+互æ›æ€§ã®ã‚る機能：3週間ã”ã¨ã€‚注：冬å£ä¼‘暇ã®æ™‚期ã§ã‚ã‚‹ãŸã‚ã€5.0.0ã®4週間後ã«è¡Œã‚ã‚Œã¾ã™ï¼‰ã€‚" +msgid "Release of Ansible-5.1.0 (bugfix + compatible features: every three weeks.)" +msgstr "Ansible-5.1.0 ã®ãƒªãƒªãƒ¼ã‚¹ (ãƒã‚°ä¿®æ£ + 互æ›æ€§ã®ã‚る機能: 3 週間ã”ã¨)" #: ../../rst/roadmap/COLLECTIONS_5.rst:36 msgid "No new modules or major features accepted after this date. In practice, this means we will freeze the semver collection versions to compatible release versions. For example, if the version of community.crypto on this date was community.crypto 2.1.0; Ansible-5.0.0 could ship with community.crypto 2.1.1. It would not ship with community.crypto 2.2.0." @@ -1603,3 +1603,9 @@ msgstr "ç¾åœ¨ã® Ansible ãŠã‚ˆã³ ``ansible-base`` ã®ãƒãƒ¼ãƒ‰ãƒžãƒƒãƒ—を確 #~ msgid "Post on the ``#ansible-community`` Freenode IRC channel" #~ msgstr "Freenode IRC ãƒãƒ£ãƒ³ãƒãƒ« ``#ansible-community`` ã§ç™ºè¨€" +#~ msgid "2022-01-04" +#~ msgstr "2022-01-04" + +#~ msgid "Release of Ansible-5.1.0 (bugfix + compatible features: every three weeks. Note: this comes 4 week after 5.0.0 due to the winter holiday season)." +#~ msgstr "Ansible-5.1.0ã®ãƒªãƒªãƒ¼ã‚¹ï¼ˆãƒã‚°ä¿®æ£+互æ›æ€§ã®ã‚る機能：3週間ã”ã¨ã€‚注：冬å£ä¼‘暇ã®æ™‚期ã§ã‚ã‚‹ãŸã‚ã€5.0.0ã®4週間後ã«è¡Œã‚ã‚Œã¾ã™ï¼‰ã€‚" + diff --git a/docs/docsite/rst/locales/ja/LC_MESSAGES/scenario_guides.po b/docs/docsite/rst/locales/ja/LC_MESSAGES/scenario_guides.po index 614285f7..4092a8f4 100644 --- a/docs/docsite/rst/locales/ja/LC_MESSAGES/scenario_guides.po +++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/scenario_guides.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Ansible devel\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-10-05 13:53+0200\n" +"POT-Creation-Date: 2021-11-09 14:07+0100\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" @@ -17,13 +17,22 @@ msgstr "" "Generated-By: Babel 2.9.0\n" #: ../../rst/scenario_guides/cloud_guides.rst:5 -#: ../../rst/scenario_guides/guides.rst:12 -msgid "Public Cloud Guides" -msgstr "パブリッククラウドガイド" +#: ../../rst/scenario_guides/guides.rst:17 +msgid "Legacy Public Cloud Guides" +msgstr "従æ¥ã®ãƒ‘ブリッククラウドガイド" #: ../../rst/scenario_guides/cloud_guides.rst:7 -msgid "The guides in this section cover using Ansible with a range of public cloud platforms. They explore particular use cases in greater depth and provide a more \"top-down\" explanation of some basic features." -msgstr "本セクションã®ã‚¬ã‚¤ãƒ‰ã§ã¯ã€ã•ã¾ã–ã¾ãªãƒ‘ブリッククラウドプラットフォームã§ã® Ansible ã®ä½¿ç”¨ã‚’説明ã—ã¾ã™ã€‚特定ã®ãƒ¦ãƒ¼ã‚¹ã‚±ãƒ¼ã‚¹ã‚’より深ã掘り下ã’ã€ã„ãã¤ã‹ã®åŸºæœ¬çš„ãªæ©Ÿèƒ½ã‚’「トップダウンã€ã§èª¬æ˜Žã—ã¾ã™ã€‚" +msgid "The legacy guides in this section may be out of date. They cover using Ansible with a range of public cloud platforms. They explore particular use cases in greater depth and provide a more \"top-down\" explanation of some basic features." +msgstr "本セクションã®å¾“æ¥ã®ã‚¬ã‚¤ãƒ‰ã¯ã€æƒ…å ±ãŒå¤ããªã£ã¦ã„ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚ガイドã§ã¯ã€ã•ã¾ã–ã¾ãªãƒ‘ブリッククラウドプラットフォームã§ã® Ansible ã®ä½¿ç”¨ã‚’説明ã—ã¾ã™ã€‚特定ã®ãƒ¦ãƒ¼ã‚¹ã‚±ãƒ¼ã‚¹ã‚’より深ã掘り下ã’ã€ã„ãã¤ã‹ã®åŸºæœ¬çš„ãªæ©Ÿèƒ½ã‚’「トップダウンã€ã§èª¬æ˜Žã—ã¾ã™ã€‚" + +#: ../../rst/scenario_guides/cloud_guides.rst:9 +msgid "Guides for using public clouds are moving into collections. We are migrating these guides into collections. Please update your links for the following guides:" +msgstr "パブリッククラウド使用ã®ã‚¬ã‚¤ãƒ‰ã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«ç§»ã•ã‚Œã¦ã„ã¾ã™ã€‚ã“れらã®ã‚¬ã‚¤ãƒ‰ã‚’コレクションã«ç§»è¡Œã—ã¦ã„ã¾ã™ã€‚以下ã®ã‚¬ã‚¤ãƒ‰ã®ãƒªãƒ³ã‚¯ã‚’æ›´æ–°ã—ã¦ãã ã•ã„。" + +#: ../../rst/scenario_guides/cloud_guides.rst:11 +#: ../../rst/scenario_guides/guides.rst:15 +msgid ":ref:`ansible_collections.amazon.aws.docsite.aws_intro`" +msgstr ":ref:`ansible_collections.amazon.aws.docsite.aws_intro`" #: ../../rst/scenario_guides/guide_aci.rst:4 msgid "Cisco ACI Guide" @@ -816,7 +825,6 @@ msgid "`User Mailing List <https://groups.google.com/group/ansible-project>`_" msgstr "`ユーザーメーリングリスト <https://groups.google.com/group/ansible-project>`_" #: ../../rst/scenario_guides/guide_aci.rst:659 -#: ../../rst/scenario_guides/guide_aws.rst:282 msgid "Have a question? Stop by the google group!" msgstr "ã”質å•ã¯ã”ã–ã„ã¾ã™ã‹ã€‚Google Group ã‚’ã”覧ãã ã•ã„。" @@ -825,7 +833,6 @@ msgid "Alibaba Cloud Compute Services Guide" msgstr "Alibaba Cloud コンピュートサービスガイド" #: ../../rst/scenario_guides/guide_alicloud.rst:7 -#: ../../rst/scenario_guides/guide_aws.rst:7 #: ../../rst/scenario_guides/guide_cloudstack.rst:7 #: ../../rst/scenario_guides/guide_gce.rst:7 #: ../../rst/scenario_guides/guide_online.rst:6 @@ -871,7 +878,6 @@ msgid "Normally, you'll use the following pattern for plays that provision Alicl msgstr "通常ã€Alicloud リソースをプãƒãƒ“ジョニングã™ã‚‹ãƒ—レイã«ã¯æ¬¡ã®ãƒ‘ターンを使用ã—ã¾ã™ã€‚" #: ../../rst/scenario_guides/guide_alicloud.rst:28 -#: ../../rst/scenario_guides/guide_aws.rst:31 #: ../../rst/scenario_guides/guide_vultr.rst:45 msgid "Authentication" msgstr "èªè¨¼" @@ -893,7 +899,6 @@ msgid "Note that if you store your credentials in a vars_file, you need to refer msgstr "èªè¨¼æƒ…å ±ã‚’ vars_file ã«ä¿å˜ã™ã‚‹å ´åˆã¯ã€å„ Alicloud モジュールã§èªè¨¼æƒ…å ±ã‚’å‚ç…§ã™ã‚‹å¿…è¦ãŒã‚ã‚‹ã“ã¨ã«æ³¨æ„ã—ã¦ãã ã•ã„。以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" #: ../../rst/scenario_guides/guide_alicloud.rst:54 -#: ../../rst/scenario_guides/guide_aws.rst:57 #: ../../rst/scenario_guides/guide_rax.rst:86 msgid "Provisioning" msgstr "プãƒãƒ“ジョニング" @@ -918,258 +923,13 @@ msgstr "上記ã®ã‚µãƒ³ãƒ—ル Playbook ã§ã¯ã€ã“ã® Playbook ã§ä½œæˆã•ã‚Œã msgid "Each Alicloud module offers a variety of parameter options. Not all options are demonstrated in the above example. See each individual module for further details and examples." msgstr "å„ Alicloud モジュールã¯ã€ã•ã¾ã–ã¾ãªãƒ‘ラメーターオプションをæä¾›ã—ã¾ã™ã€‚上記ã®ä¾‹ã§ã€ã™ã¹ã¦ã®ã‚ªãƒ—ションãŒç¤ºã•ã‚Œã¦ã„ã‚‹ã‚ã‘ã§ã¯ã‚ã‚Šã¾ã›ã‚“。詳細ãŠã‚ˆã³ã‚µãƒ³ãƒ—ルã¯ã€å„モジュールをå‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/scenario_guides/guide_aws.rst:2 +#: ../../rst/scenario_guides/guide_aws.rst:4 msgid "Amazon Web Services Guide" msgstr "Amazon Web Services ガイド" -#: ../../rst/scenario_guides/guide_aws.rst:9 -msgid "Ansible contains a number of modules for controlling Amazon Web Services (AWS). The purpose of this section is to explain how to put Ansible modules together (and use inventory scripts) to use Ansible in AWS context." -msgstr "Ansible ã«ã¯ã€Amazon Web Services (AWS) を制御ã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒå¤šæ•°å«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã®ç›®çš„ã¯ã€AWS ã®ã‚³ãƒ³ãƒ†ã‚スト㧠Ansible を使用ã™ã‚‹ãŸã‚ã«ã€Ansible モジュールをã©ã®ã‚ˆã†ã«çµ„ã¿åˆã‚ã›ã‚‹ã‹ (インベントリースクリプトを使用ã™ã‚‹ã‹) を説明ã™ã‚‹ã“ã¨ã§ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:12 -msgid "Requirements for the AWS modules are minimal." -msgstr "AWS モジュールã®è¦ä»¶ã¯æœ€å°é™ã§ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:14 -msgid "All of the modules require and are tested against recent versions of botocore and boto3. Starting with the 2.0 AWS collection releases, it is generally the policy of the collections to support the versions of these libraries released 12 months prior to the most recent major collection revision. Individual modules may require a more recent library version to support specific features or may require the boto library, check the module documentation for the minimum required version for each module. You must have the boto3 Python module installed on your control machine. You can install these modules from your OS distribution or using the python package installer: ``pip install boto3``." -msgstr "ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€botocore ãŠã‚ˆã³ boto3 ã®æœ€æ–°ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’å¿…è¦ã¨ã—ã€ãれらã«å¯¾ã—ã¦ãƒ†ã‚¹ãƒˆã•ã‚Œã¦ã„ã¾ã™ã€‚2.0 AWS コレクションリリース以é™ã€é€šå¸¸ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒãƒªã‚·ãƒ¼ã¯ã€æœ€æ–°ã®ãƒ¡ã‚¸ãƒ£ãƒ¼ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãƒªãƒ“ジョン㮠12 カ月å‰ã«ãƒªãƒªãƒ¼ã‚¹ã•ã‚ŒãŸã“れらã®ãƒ©ã‚¤ãƒ–ラリーã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’サãƒãƒ¼ãƒˆã™ã‚‹ã“ã¨ã§ã™ã€‚個々ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã§ã¯ã€ç‰¹å®šã®æ©Ÿèƒ½ã‚’サãƒãƒ¼ãƒˆã™ã‚‹ãŸã‚ã«æœ€æ–°ã®ãƒ©ã‚¤ãƒ–ラリーãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒå¿…è¦ãªå ´åˆã‚„ã€boto ライブラリーãŒå¿…è¦ãªå ´åˆãŒã‚ã‚Šã¾ã™ã€‚モジュールã®ãƒ‰ã‚ュメントã§ã€å„モジュールã«å¿…è¦ãªæœ€ä½Žãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’確èªã—ã¦ãã ã•ã„。制御マシン㫠boto3 Python モジュールãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“れらã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€OS ディストリビューションã‹ã‚‰ã€ã¾ãŸã¯ python パッケージインストーラーを使用ã—ã¦ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ãã¾ã™ (``pip install boto3``)。" - -#: ../../rst/scenario_guides/guide_aws.rst:16 -msgid "Starting with the 2.0 releases of both collections, Python 2.7 support will be ended in accordance with AWS' `end of Python 2.7 support <https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-python-2-7-in-aws-sdk-for-python-and-aws-cli-v1/>`_ and Python 3.6 or greater will be required." -msgstr "両方ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã§ 2.0 リリース以é™ã€Python 2.7 サãƒãƒ¼ãƒˆã¯ AWS ã® `Python 2.7 サãƒãƒ¼ãƒˆã®çµ‚了 <https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-python-2-7-in-aws-sdk-for-python-and-aws-cli-v1/>`_ 㨠Python 3.6 以上ã«å¿œã˜ã¦çµ‚了ã—ã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:19 -msgid "Whereas classically Ansible will execute tasks in its host loop against multiple remote machines, most cloud-control steps occur on your local machine with reference to the regions to control." -msgstr "従æ¥ã€Ansible ã¯ãƒ›ã‚¹ãƒˆãƒ«ãƒ¼ãƒ—内ã®ã‚¿ã‚¹ã‚¯ã‚’複数ã®ãƒªãƒ¢ãƒ¼ãƒˆãƒžã‚·ãƒ³ã«å¯¾ã—ã¦å®Ÿè¡Œã—ã¾ã™ãŒã€ã»ã¨ã‚“ã©ã®ã‚¯ãƒ©ã‚¦ãƒ‰åˆ¶å¾¡æ‰‹é †ã¯ã€åˆ¶å¾¡ã™ã‚‹ãƒªãƒ¼ã‚¸ãƒ§ãƒ³ã‚’å‚ç…§ã™ã‚‹ãƒãƒ¼ã‚«ãƒ«ãƒžã‚·ãƒ³ã§å®Ÿè¡Œã—ã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:21 -msgid "In your playbook steps we'll typically be using the following pattern for provisioning steps::" -msgstr "Playbook ã®æ‰‹é †ã§ã¯ã€é€šå¸¸ã€ãƒ—ãƒãƒ“ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°æ‰‹é †ã«ä»¥ä¸‹ã®ãƒ‘ターンを使用ã—ã¾ã™::" - -#: ../../rst/scenario_guides/guide_aws.rst:33 -msgid "Authentication with the AWS-related modules is handled by either specifying your access and secret key as ENV variables or module arguments." -msgstr "AWS 関連ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ãŸèªè¨¼ã¯ã€ENV 変数ã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«å¼•æ•°ã¨ã—ã¦ã‚¢ã‚¯ã‚»ã‚¹ãŠã‚ˆã³ç§˜å¯†éµã‚’指定ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šå‡¦ç†ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:36 -msgid "For environment variables::" -msgstr "環境変数ã®å ´åˆ::" - -#: ../../rst/scenario_guides/guide_aws.rst:41 -msgid "For storing these in a vars_file, ideally encrypted with ansible-vault::" -msgstr "vars_file ã«ä¿å˜ã™ã‚‹ã«ã¯ã€ansible-vault ã§æš—å·åŒ–ã™ã‚‹ã“ã¨ãŒç†æƒ³çš„ã§ã™::" - -#: ../../rst/scenario_guides/guide_aws.rst:47 -msgid "Note that if you store your credentials in vars_file, you need to refer to them in each AWS-module. For example::" -msgstr "èªè¨¼æƒ…å ±ã‚’ vars_file ã«ä¿å˜ã™ã‚‹å ´åˆã¯ã€å„ AWS モジュールã§èªè¨¼æƒ…å ±ã‚’å‚ç…§ã™ã‚‹å¿…è¦ãŒã‚ã‚‹ã“ã¨ã«æ³¨æ„ã—ã¦ãã ã•ã„。以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:59 -msgid "The ec2 module provisions and de-provisions instances within EC2." -msgstr "ec2 モジュールã¯ã€EC2 内ã§ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã®ãƒ—ãƒãƒ“ジョニングãŠã‚ˆã³ãƒ—ãƒãƒ“ジョニング解除を行ã„ã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:61 -msgid "An example of making sure there are only 5 instances tagged 'Demo' in EC2 follows." -msgstr "EC2 ã§ã€ŒDemoã€ã¨ã‚¿ã‚°ä»˜ã‘ã•ã‚ŒãŸã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ãŒ 5 個ã«ãªã‚‹ã‚ˆã†ã«ã™ã‚‹ä¾‹ã‚’以下ã«ç¤ºã—ã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:63 -msgid "In the example below, the \"exact_count\" of instances is set to 5. This means if there are 0 instances already existing, then 5 new instances would be created. If there were 2 instances, only 3 would be created, and if there were 8 instances, 3 instances would be terminated." -msgstr "以下ã®ä¾‹ã§ã¯ã€ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã®ã€Œexact_countã€ã¯ 5 ã«è¨å®šã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ã€ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ãŒãªã„å ´åˆã¯ã€æ–°è¦ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ãŒ 5 個作æˆã•ã‚Œã‚‹ã“ã¨ã‚’示ã—ã¦ã„ã¾ã™ã€‚インスタンス㌠2 個ã‚ã‚‹å ´åˆã¯ã€3 個作æˆã•ã‚Œã€ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ãŒ 8 個ã‚ã‚‹å ´åˆã¯ã€3 個ã®ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ãŒçµ‚了ã—ã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:67 -msgid "What is being counted is specified by the \"count_tag\" parameter. The parameter \"instance_tags\" is used to apply tags to the newly created instance.::" -msgstr "カウントã•ã‚Œã‚‹ã‚‚ã®ã¯ã€Œcount_tagã€ãƒ‘ラメーターã§æŒ‡å®šã—ã¾ã™ã€‚「instance_tagsã€ãƒ‘ラメーターã¯ã€æ–°ãŸã«ä½œæˆã•ã‚ŒãŸã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã‚’ã‚¿ã‚°ã«é©ç”¨ã™ã‚‹ãŸã‚ã«ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:91 -msgid "The data about what instances are created is being saved by the \"register\" keyword in the variable named \"ec2\"." -msgstr "作æˆã•ã‚Œã‚‹ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã«é–¢ã™ã‚‹ãƒ‡ãƒ¼ã‚¿ã¯ã€ã€Œec2ã€ã¨ã„ã†å¤‰æ•°ã®ã€Œregisterã€ã‚ーワードã«ã‚ˆã£ã¦ä¿å˜ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:93 -msgid "From this, we'll use the add_host module to dynamically create a host group consisting of these new instances. This facilitates performing configuration actions on the hosts immediately in a subsequent task.::" -msgstr "ã“ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‹ã‚‰ add_host モジュールを使用ã—ã€ã“れらã®æ–°è¦ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã§æ§‹æˆã•ã‚Œã‚‹ãƒ›ã‚¹ãƒˆã‚°ãƒ«ãƒ¼ãƒ—ã‚’å‹•çš„ã«ä½œæˆã—ã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€å¾Œç¶šã®ã‚¿ã‚¹ã‚¯ã§ã€ãƒ›ã‚¹ãƒˆã§ã®è¨å®šã‚¢ã‚¯ã‚·ãƒ§ãƒ³ã‚’ã™ãã«å®Ÿè¡Œã§ãã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:120 -msgid "With the host group now created, a second play at the bottom of the same provisioning playbook file might now have some configuration steps::" -msgstr "ã“ã‚Œã§ãƒ›ã‚¹ãƒˆã‚°ãƒ«ãƒ¼ãƒ—ãŒä½œæˆã•ã‚ŒãŸã®ã§ã€åŒã˜ãƒ—ãƒãƒ“ジョニング Playbook ファイルã®ä¸‹éƒ¨ã«ã‚ã‚‹2ã¤ç›®ã®ãƒ—レイã§ã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ãªè¨å®šã‚¹ãƒ†ãƒƒãƒ—ãŒå¿…è¦ã«ãªã‚Šã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:141 -msgid "Security Groups" -msgstr "ã‚»ã‚ュリティーグループ" - -#: ../../rst/scenario_guides/guide_aws.rst:143 -msgid "Security groups on AWS are stateful. The response of a request from your instance is allowed to flow in regardless of inbound security group rules and vice-versa. In case you only want allow traffic with AWS S3 service, you need to fetch the current IP ranges of AWS S3 for one region and apply them as an egress rule.::" -msgstr "AWS ã®ã‚»ã‚ュリティーグループã¯ã‚¹ãƒ†ãƒ¼ãƒˆãƒ•ãƒ«ã§ã™ã€‚インスタンスã‹ã‚‰ã®è¦æ±‚ã®å¿œç”ã¯ã€å—ä¿¡ã‚»ã‚ュリティーグループルールã«é–¢ä¿‚ãªãæµå…¥ãŒè¨±å¯ã•ã‚Œã€ãã®é€†ã‚‚åŒæ§˜ã§ã™ã€‚AWS S3 サービスを使用ã™ã‚‹ãƒˆãƒ©ãƒ•ã‚£ãƒƒã‚¯ã®ã¿ã‚’許å¯ã™ã‚‹å ´åˆã¯ã€ã‚るリージョンã«å¯¾ã—㦠AWS S3 ã®ç¾åœ¨ã® IP 範囲をå–å¾—ã—ã€ãれを egress ルールã¨ã—ã¦é©ç”¨ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:172 -#: ../../rst/scenario_guides/guide_rax.rst:155 -msgid "Host Inventory" -msgstr "ホストインベントリー" - -#: ../../rst/scenario_guides/guide_aws.rst:174 -msgid "Once your nodes are spun up, you'll probably want to talk to them again. With a cloud setup, it's best to not maintain a static list of cloud hostnames in text files. Rather, the best way to handle this is to use the aws_ec2 inventory plugin. See :ref:`dynamic_inventory`." -msgstr "ノードãŒèµ·å‹•ã—ãŸã‚‰ã€ãŠãらãå†é€šä¿¡ã™ã‚‹ã‚ˆã†ã«ã—ãŸã„ã§ã—ょã†ã€‚クラウドè¨å®šã§ã¯ã€ãƒ†ã‚ストファイルã«ã€ã‚¯ãƒ©ã‚¦ãƒ‰ãƒ›ã‚¹ãƒˆåã®é™çš„リストをç¶æŒã—ãªã„ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚ã“れを処ç†ã™ã‚‹æœ€å–„ã®æ–¹æ³•ã¯ã€aws_ec2 インベントリープラグインを使用ã™ã‚‹ã“ã¨ã§ã™ã€‚:ref:`dynamic_inventory` ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/scenario_guides/guide_aws.rst:177 -msgid "The plugin will also return instances that were created outside of Ansible and allow Ansible to manage them." -msgstr "ã“ã®ãƒ—ラグインã«ã‚ˆã‚Šã€Ansible 外ã§ä½œæˆã•ã‚ŒãŸã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã‚‚é¸æŠžã•ã‚Œã€Ansible ãŒã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã‚’管ç†ã§ãるよã†ã«ãªã‚Šã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:182 -msgid "Tags And Groups And Variables" -msgstr "ã‚¿ã‚°ã€ã‚°ãƒ«ãƒ¼ãƒ—ã€ãŠã‚ˆã³å¤‰æ•°" - -#: ../../rst/scenario_guides/guide_aws.rst:184 -msgid "When using the inventory plugin, you can configure extra inventory structure based on the metadata returned by AWS." -msgstr "インベントリープラグインを使用ã™ã‚‹å ´åˆã¯ã€AWS ã«ã‚ˆã‚Šè¿”ã•ã‚Œã‚‹ãƒ¡ã‚¿ãƒ‡ãƒ¼ã‚¿ã«åŸºã¥ã„ã¦è¿½åŠ ã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼æ§‹é€ ã‚’è¨å®šã§ãã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:186 -msgid "For instance, you might use ``keyed_groups`` to create groups from instance tags::" -msgstr "ãŸã¨ãˆã°ã€``keyed_groups`` を使用ã—ã¦ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã‚¿ã‚°ã‹ã‚‰ã‚°ãƒ«ãƒ¼ãƒ—を作æˆã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:194 -msgid "You can then target all instances with a \"class\" tag where the value is \"webserver\" in a play::" -msgstr "次ã«ã€ã€Œclassã€ã‚¿ã‚°ã®ä»˜ã„ãŸã™ã¹ã¦ã®ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã‚’ターゲットã«ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã“ã§ã€å€¤ã¯ãƒ—レイ内ã®ã€Œwebserverã€ã«ãªã‚Šã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:200 -msgid "You can also use these groups with 'group_vars' to set variables that are automatically applied to matching instances. See :ref:`splitting_out_vars`." -msgstr "「group_varsã€ã§ã“れらã®ã‚°ãƒ«ãƒ¼ãƒ—を使用ã—ã¦ã€ä¸€è‡´ã™ã‚‹ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã«è‡ªå‹•çš„ã«é©ç”¨ã•ã‚Œã‚‹å¤‰æ•°ã‚’è¨å®šã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚「:ref:`splitting_out_vars`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/scenario_guides/guide_aws.rst:205 -msgid "Autoscaling with Ansible Pull" -msgstr "Ansible Pull を使用ã—ãŸè‡ªå‹•ã‚¹ã‚±ãƒ¼ãƒªãƒ³ã‚°" - -#: ../../rst/scenario_guides/guide_aws.rst:207 -msgid "Amazon Autoscaling features automatically increase or decrease capacity based on load. There are also Ansible modules shown in the cloud documentation that can configure autoscaling policy." -msgstr "Amazon Autoscaling 機能ã¯ã€è² è·ã«å¿œã˜ã¦å®¹é‡ã‚’自動的ã«å¢—減ã—ã¾ã™ã€‚ã¾ãŸã€ã‚¯ãƒ©ã‚¦ãƒ‰ãƒ‰ã‚ュメントã§èª¬æ˜Žã•ã‚Œã‚‹ã‚ˆã†ã«ã€è‡ªå‹•ã‚¹ã‚±ãƒ¼ãƒªãƒ³ã‚°ãƒãƒªã‚·ãƒ¼ã‚’è¨å®šã™ã‚‹ Ansible モジュールãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:210 -msgid "When nodes come online, it may not be sufficient to wait for the next cycle of an ansible command to come along and configure that node." -msgstr "ノードãŒã‚ªãƒ³ãƒ©ã‚¤ãƒ³ã«ãªã‚‹ã¨ã€ansible コマンドã®æ¬¡ã®ã‚µã‚¤ã‚¯ãƒ«ãŒåæ˜ ã•ã‚Œã¦ãã®ãƒŽãƒ¼ãƒ‰ã‚’è¨å®šã™ã‚‹ã®ã‚’å¾…ã¤ã“ã¨ãŒã§ããªã„å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:212 -msgid "To do this, pre-bake machine images which contain the necessary ansible-pull invocation. Ansible-pull is a command line tool that fetches a playbook from a git server and runs it locally." -msgstr "ãã®ãŸã‚ã«ã¯ã€å¿…è¦ãª ansible-pull 呼ã³å‡ºã—ã‚’å«ã‚€ãƒžã‚·ãƒ³ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’事å‰ã«ä½œæˆã—ã¾ã™ã€‚ansible-pull ã¯ã€git サーãƒãƒ¼ã‹ã‚‰ Playbook ã‚’å–å¾—ã—ã€ãƒãƒ¼ã‚«ãƒ«ã§å®Ÿè¡Œã™ã‚‹ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ãƒ„ールã§ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:214 -msgid "One of the challenges of this approach is that there needs to be a centralized way to store data about the results of pull commands in an autoscaling context. For this reason, the autoscaling solution provided below in the next section can be a better approach." -msgstr "ã“ã®ã‚¢ãƒ—ãƒãƒ¼ãƒã®èª²é¡Œã® 1 ã¤ã¨ã—ã¦ã€pull コマンドã®çµæžœã«é–¢ã™ã‚‹ãƒ‡ãƒ¼ã‚¿ã‚’自動スケーリングコンテã‚ストã«ä¿å˜ã™ã‚‹é›†ä¸çš„ãªæ–¹æ³•ãŒå¿…è¦ã«ãªã‚Šã¾ã™ã€‚ã“ã®ãŸã‚ã€æ¬¡ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§æä¾›ã•ã‚Œã‚‹è‡ªå‹•ã‚¹ã‚±ãƒ¼ãƒªãƒ³ã‚°ã‚½ãƒªãƒ¥ãƒ¼ã‚·ãƒ§ãƒ³ã®æ–¹ãŒé©åˆ‡ã§ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:217 -msgid "Read :ref:`ansible-pull` for more information on pull-mode playbooks." -msgstr "pull モード㮠Playbook ã®è©³ç´°ã¯ã€ã€Œ:ref:`ansible-pull`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/scenario_guides/guide_aws.rst:222 -msgid "Autoscaling with Ansible Tower" -msgstr "Ansible Tower を使用ã—ãŸè‡ªå‹•ã‚¹ã‚±ãƒ¼ãƒªãƒ³ã‚°" - -#: ../../rst/scenario_guides/guide_aws.rst:224 -msgid ":ref:`ansible_tower` also contains a very nice feature for auto-scaling use cases. In this mode, a simple curl script can call a defined URL and the server will \"dial out\" to the requester and configure an instance that is spinning up. This can be a great way to reconfigure ephemeral nodes. See the Tower install and product documentation for more details." -msgstr "ã¾ãŸã€:ref:`ansible_tower` ã¯ã€è‡ªå‹•ã‚¹ã‚±ãƒ¼ãƒªãƒ³ã‚°ã®ãƒ¦ãƒ¼ã‚¹ã‚±ãƒ¼ã‚¹ã«ã¯éžå¸¸ã«å„ªã‚ŒãŸæ©Ÿèƒ½ã‚‚å«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ã“ã®ãƒ¢ãƒ¼ãƒ‰ã§ã¯ã€ç°¡å˜ãª curl スクリプトã¯å®šç¾©ã•ã‚ŒãŸ URL を呼ã³å‡ºã™ã“ã¨ãŒã§ãã€ã‚µãƒ¼ãƒãƒ¼ã¯è¦æ±‚å…ƒã«å¯¾ã—ã¦ã€Œãƒ€ã‚¤ãƒ¤ãƒ«ã‚¢ã‚¦ãƒˆã€ã—ã€èµ·å‹•ã—ã¦ã„るインスタンスを構æˆã—ã¾ã™ã€‚ã“ã‚Œã¯ã€ä¸€æ™‚ノードをå†è¨å®šã™ã‚‹å„ªã‚ŒãŸæ–¹æ³•ã«ãªã‚Šã¾ã™ã€‚詳細ã¯ã€Tower ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã¨è£½å“ã®ãƒ‰ã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/scenario_guides/guide_aws.rst:228 -msgid "A benefit of using the callback in Tower over pull mode is that job results are still centrally recorded and less information has to be shared with remote hosts." -msgstr "pull モード㧠Tower ã®ã‚³ãƒ¼ãƒ«ãƒãƒƒã‚¯ã‚’使用ã™ã‚‹åˆ©ç‚¹ã¯ã€ã‚¸ãƒ§ãƒ–ã®çµæžœãŒå¼•ã続ãä¸å¤®ã§è¨˜éŒ²ã•ã‚Œã€ãƒªãƒ¢ãƒ¼ãƒˆãƒ›ã‚¹ãƒˆã¨å…±æœ‰ã™ã‚‹å¿…è¦ã®ã‚ã‚‹æƒ…å ±ãŒå°‘ãªããªã‚‹ã“ã¨ã§ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:234 -msgid "Ansible With (And Versus) CloudFormation" -msgstr "CloudFormation を使用ã—㟠Ansible (Ansible 㨠CloudFormation ã®æ¯”較)" - -#: ../../rst/scenario_guides/guide_aws.rst:236 -msgid "CloudFormation is a Amazon technology for defining a cloud stack as a JSON or YAML document." -msgstr "CloudFormation ã¯ã€ã‚¯ãƒ©ã‚¦ãƒ‰ã‚¹ã‚¿ãƒƒã‚¯ã‚’ JSON ã¾ãŸã¯ YAML ã®ãƒ‰ã‚ュメントã¨ã—ã¦å®šç¾©ã™ã‚‹ Amazon テクノãƒã‚¸ãƒ¼ã§ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:238 -msgid "Ansible modules provide an easier to use interface than CloudFormation in many examples, without defining a complex JSON/YAML document. This is recommended for most users." -msgstr "Ansible モジュールã¯ã€è¤‡é›‘㪠JSON/YAML ドã‚ュメントを定義ã›ãšã«ã€å¤šãã®ä¾‹ã§ CloudFormation よりも簡å˜ã«ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ã‚’使用ã§ãã¾ã™ã€‚ã“ã‚Œã¯ã€ã»ã¨ã‚“ã©ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«æŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:241 -msgid "However, for users that have decided to use CloudFormation, there is an Ansible module that can be used to apply a CloudFormation template to Amazon." -msgstr "ãŸã ã—ã€CloudFormation を使用ã™ã‚‹ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«ã¯ã€CloudFormation テンプレートを Amazon ã«é©ç”¨ã™ã‚‹ã®ã«ä½¿ç”¨ã§ãã‚‹ Ansible モジュールãŒã‚ã‚Šã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:244 -msgid "When using Ansible with CloudFormation, typically Ansible will be used with a tool like Packer to build images, and CloudFormation will launch those images, or ansible will be invoked through user data once the image comes online, or a combination of the two." -msgstr "CloudFormation 㧠Ansible を使用ã™ã‚‹å ´åˆã¯ã€é€šå¸¸ã€Ansible ã‚’ Packer ãªã©ã®ãƒ„ールã§ä½¿ç”¨ã—ã¦ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’作æˆã—ã€CloudFormation ãŒãã®ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’èµ·å‹•ã™ã‚‹ã‹ã€ã‚¤ãƒ¡ãƒ¼ã‚¸ãŒã‚ªãƒ³ãƒ©ã‚¤ãƒ³ã«ãªã‚‹ã¨ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãƒ‡ãƒ¼ã‚¿ã‚’通ã˜ã¦ ansible ãŒå‘¼ã³å‡ºã•ã‚Œã‚‹ã‹ã€ãã®çµ„ã¿åˆã‚ã›ã¨ãªã‚Šã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:247 -msgid "Please see the examples in the Ansible CloudFormation module for more details." -msgstr "詳細ã¯ã€Ansible CloudFormation モジュールã®ã‚µãƒ³ãƒ—ルをå‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/scenario_guides/guide_aws.rst:252 -msgid "AWS Image Building With Ansible" -msgstr "Ansible ã§ã® AWS イメージã®æ§‹ç¯‰" - -#: ../../rst/scenario_guides/guide_aws.rst:254 -msgid "Many users may want to have images boot to a more complete configuration rather than configuring them entirely after instantiation. To do this, one of many programs can be used with Ansible playbooks to define and upload a base image, which will then get its own AMI ID for usage with the ec2 module or other Ansible AWS modules such as ec2_asg or the cloudformation module. Possible tools include Packer, aminator, and Ansible's ec2_ami module." -msgstr "多ãã®å ´åˆã€ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹åŒ–後ã«ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’完全ã«è¨å®šã™ã‚‹ã®ã§ã¯ãªãã€ã‚ˆã‚Šå®Œå…¨ãªè¨å®šã§ã®èµ·å‹•ã‚’望ã¿ã¾ã™ã€‚ã“れを行ã†ã«ã¯ã€Ansible Playbook ã¨ã¨ã‚‚ã«å¤šãã®ãƒ—ãƒã‚°ãƒ©ãƒ ã®ä¸ã‹ã‚‰ 1 ã¤ä½¿ç”¨ã—ã¦ãƒ™ãƒ¼ã‚¹ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’定義ã—ã€ã‚¢ãƒƒãƒ—ãƒãƒ¼ãƒ‰ã§ãã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ec2 モジュールã€ec2_asg モジュールや cloudformation モジュールãªã©ã®ãã®ä»–ã® Ansible AWS モジュールã¨ä½¿ç”¨ã™ã‚‹ãŸã‚ã€ç‹¬è‡ªã® AMI ID ã‚’å–å¾—ã—ã¾ã™ã€‚ツールã«ã¯ Packerã€aminatorã€ãŠã‚ˆã³ Ansible ã® ec2_ami モジュールãŒå«ã¾ã‚Œã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:259 -msgid "Generally speaking, we find most users using Packer." -msgstr "一般的ã«ã¯ã€Packer ãŒä½¿ç”¨ã•ã‚Œã¾ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:261 -msgid "See the Packer documentation of the `Ansible local Packer provisioner <https://www.packer.io/docs/provisioners/ansible/ansible-local>`_ and `Ansible remote Packer provisioner <https://www.packer.io/docs/provisioners/ansible/ansible>`_." -msgstr "`Ansible local Packer provisioner <https://www.packer.io/docs/provisioners/ansible/ansible-local>`_ ãŠã‚ˆã³ `Ansible remote Packer provisioner <https://www.packer.io/docs/provisioners/ansible/ansible>`_ ã® Packer ドã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/scenario_guides/guide_aws.rst:263 -msgid "If you do not want to adopt Packer at this time, configuring a base-image with Ansible after provisioning (as shown above) is acceptable." -msgstr "ç¾æ™‚点ã§ã¯ã€Packer を使用ã—ãªã„å ´åˆã¯ã€ãƒ—ãƒãƒ“ジョニング後㫠(上記ã®ã‚ˆã†ã«) Ansible を使用ã—ãŸãƒ™ãƒ¼ã‚¹ã‚¤ãƒ¡ãƒ¼ã‚¸ã®è¨å®šãŒå¯èƒ½ã§ã™ã€‚" - -#: ../../rst/scenario_guides/guide_aws.rst:268 -msgid "Next Steps: Explore Modules" -msgstr "次ã®ã‚¹ãƒ†ãƒƒãƒ—: モジュールã®æ¤œè¨¼" - -#: ../../rst/scenario_guides/guide_aws.rst:270 -msgid "Ansible ships with lots of modules for configuring a wide array of EC2 services. Browse the \"Cloud\" category of the module documentation for a full list with examples." -msgstr "Ansible ã«ã¯ã€ã•ã¾ã–ã¾ãª EC2 サービスをè¨å®šã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒå¤šæ•°åŒæ¢±ã•ã‚Œã¦ã„ã¾ã™ã€‚例をå«ã‚€å®Œå…¨ãªä¸€è¦§ã«ã¤ã„ã¦ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ‰ã‚ュメントã®ã€Œã‚¯ãƒ©ã‚¦ãƒ‰ã€ã‚«ãƒ†ã‚´ãƒªãƒ¼ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" - -#: ../../rst/scenario_guides/guide_aws.rst:275 -msgid ":ref:`list_of_collections`" -msgstr ":ref:`list_of_collections`" - -#: ../../rst/scenario_guides/guide_aws.rst:276 -msgid "Browse existing collections, modules, and plugins" -msgstr "æ—¢å˜ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€ãŠã‚ˆã³ãƒ—ラグインã®é–²è¦§" - -#: ../../rst/scenario_guides/guide_aws.rst:277 -#: ../../rst/scenario_guides/guide_vagrant.rst:135 -#: ../../rst/scenario_guides/kubernetes_scenarios/k8s_inventory.rst:92 -#: ../../rst/scenario_guides/kubernetes_scenarios/scenario_k8s_object.rst:87 -#: ../../rst/scenario_guides/vmware_scenarios/vmware_intro.rst:52 -#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory.rst:88 -#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory_filters.rst:213 -#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory_hostnames.rst:125 -#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory_vm_attributes.rst:1181 -msgid ":ref:`working_with_playbooks`" -msgstr ":ref:`working_with_playbooks`" - -#: ../../rst/scenario_guides/guide_aws.rst:278 -#: ../../rst/scenario_guides/guide_vagrant.rst:136 -#: ../../rst/scenario_guides/kubernetes_scenarios/k8s_inventory.rst:93 -#: ../../rst/scenario_guides/kubernetes_scenarios/scenario_k8s_object.rst:88 -#: ../../rst/scenario_guides/vmware_scenarios/vmware_intro.rst:53 -#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory.rst:89 -#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory_filters.rst:214 -#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory_hostnames.rst:126 -#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory_vm_attributes.rst:1182 -msgid "An introduction to playbooks" -msgstr "Playbook ã®æ¦‚è¦" - -#: ../../rst/scenario_guides/guide_aws.rst:279 -msgid ":ref:`playbooks_delegation`" -msgstr ":ref:`playbooks_delegation`" - -#: ../../rst/scenario_guides/guide_aws.rst:280 -msgid "Delegation, useful for working with loud balancers, clouds, and locally executed steps." -msgstr "å§”è² (ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚µãƒ¼ã€ã‚¯ãƒ©ã‚¦ãƒ‰ã€ãƒãƒ¼ã‚«ãƒ«ã§å®Ÿè¡Œã—ãŸæ‰‹é †ã‚’使用ã™ã‚‹éš›ã«å½¹ã«ç«‹ã¡ã¾ã™)" - -#: ../../rst/scenario_guides/guide_aws.rst:281 -msgid "`User Mailing List <https://groups.google.com/group/ansible-devel>`_" -msgstr "`ユーザーメーリングリスト <https://groups.google.com/group/ansible-devel>`_" - -#: ../../rst/scenario_guides/guide_aws.rst:283 -msgid ":ref:`communication_irc`" -msgstr ":ref:`communication_irc`" - -#: ../../rst/scenario_guides/guide_aws.rst:284 -msgid "How to join Ansible chat channels" -msgstr "Ansible ãƒãƒ£ãƒƒãƒˆãƒãƒ£ãƒ³ãƒãƒ«ã¸ã®å‚åŠ æ–¹æ³•" +#: ../../rst/scenario_guides/guide_aws.rst:6 +msgid "The content on this page has moved. Please see the updated :ref:`ansible_collections.amazon.aws.docsite.aws_intro` in the AWS collection." +msgstr "ã“ã®ãƒšãƒ¼ã‚¸ã®ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã¯ç§»å‹•ã—ã¾ã—ãŸã€‚AWSコレクションã«ã‚ã‚‹æ›´æ–°ã•ã‚ŒãŸ :ref:`ansible_collections.amazon.aws.docsite.aws_intro` ã‚’ã”覧ãã ã•ã„。" #: ../../rst/scenario_guides/guide_azure.rst:2 msgid "Microsoft Azure Guide" @@ -3089,8 +2849,8 @@ msgid "Rackspace Cloud Guide" msgstr "Rackspace Cloud ガイド" #: ../../rst/scenario_guides/guide_rax.rst:9 -msgid "This section of the documentation is under construction. We are in the process of adding more examples about the Rackspace modules and how they work together. Once complete, there will also be examples for Rackspace Cloud in `ansible-examples <https://github.com/ansible/ansible-examples/>`_." -msgstr "本ガイドã«è¨˜è¼‰ã™ã‚‹ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã¯ä½œæˆä¸ã§ã™ã€‚ã“ã“ã§ã¯ã€Rackspace モジュールやãã‚ŒãŒã©ã®ã‚ˆã†ã«é€£æºã™ã‚‹ã‹ã«ã¤ã„ã¦ã®ä¾‹ã‚’è¿½åŠ ã™ã‚‹ãƒ—ãƒã‚»ã‚¹ã§ã™ã€‚完了後ã¯ã€`ansible-examples <https://github.com/ansible/ansible-examples/>`_ ã« Rackspace Cloud ã®ä¾‹ã‚‚ã‚ã‚Šã¾ã™ã€‚" +msgid "Rackspace functionality in Ansible is not maintained and users should consider the `OpenStack collection <https://galaxy.ansible.com/openstack/cloud>`_ instead." +msgstr "Ansible ã® Rackspace 機能ã¯ç¶æŒã•ã‚Œãšã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ã¯ä»£ã‚ã‚Šã« `OpenStack collection <https://galaxy.ansible.com/openstack/cloud>`_ を検討ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" #: ../../rst/scenario_guides/guide_rax.rst:11 msgid "Ansible contains a number of core modules for interacting with Rackspace Cloud." @@ -3192,6 +2952,10 @@ msgstr "ã“ã‚Œã§ãƒ›ã‚¹ãƒˆã‚°ãƒ«ãƒ¼ãƒ—ãŒä½œæˆã•ã‚Œã€ã“ã® Playbook ã®æ¬¡ã msgid "The method above ties the configuration of a host with the provisioning step. This isn't always what you want, and leads us to the next section." msgstr "上記ã®æ–¹æ³•ã§ãƒ—ãƒãƒ“ジョニングステップã§ãƒ›ã‚¹ãƒˆã®è¨å®šã‚’çµ±åˆã—ã¾ã™ã€‚ã“ã‚Œã¯å¿…ãšã—も望ã¾ã—ã„ã“ã¨ã§ã¯ãªãã€æ¬¡ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã«ã¤ãªãŒã‚Šã¾ã™ã€‚" +#: ../../rst/scenario_guides/guide_rax.rst:155 +msgid "Host Inventory" +msgstr "ホストインベントリー" + #: ../../rst/scenario_guides/guide_rax.rst:157 msgid "Once your nodes are spun up, you'll probably want to talk to them again. The best way to handle this is to use the \"rax\" inventory plugin, which dynamically queries Rackspace Cloud and tells Ansible what nodes you have to manage. You might want to use this even if you are spinning up cloud instances via other tools, including the Rackspace Cloud user interface. The inventory plugin can be used to group resources by metadata, region, OS, and so on. Utilizing metadata is highly recommended in \"rax\" and can provide an easy way to sort between host groups and roles. If you don't want to use the ``rax.py`` dynamic inventory script, you could also still choose to manually manage your INI inventory file, though this is less recommended." msgstr "ノードãŒèµ·å‹•ã—ãŸã‚‰ã€å†ã³ãƒŽãƒ¼ãƒ‰ã¨ã‚„ã‚Šå–ã‚Šã—ãŸããªã‚‹ã§ã—ょã†ã€‚ã“れを処ç†ã™ã‚‹æœ€å–„ã®æ–¹æ³•ã¯ã€ã€Œraxã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ—ラグインを使用ã™ã‚‹ã“ã¨ã§ã™ã€‚ã“ã‚Œã¯ã€Rackspace Cloud ã«å‹•çš„ã«ã‚¯ã‚¨ãƒªãƒ¼ã‚’実行ã—ã€ç®¡ç†ã™ã‚‹å¿…è¦ãŒã‚るノードを Ansible ã«é€šçŸ¥ã—ã¾ã™ã€‚Rackspace Cloud ユーザーインターフェースãªã©ã€ä»–ã®ãƒ„ールã§ã‚¯ãƒ©ã‚¦ãƒ‰ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã‚’èµ·å‹•ã—ã¦ã„ã‚‹å ´åˆã§ã‚‚ã€ã“ã®ãƒ—ラグインを使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚インベントリープラグインã¯ã€ãƒ¡ã‚¿ãƒ‡ãƒ¼ã‚¿ã€ãƒªãƒ¼ã‚¸ãƒ§ãƒ³ã€OS ãªã©ã§ãƒªã‚½ãƒ¼ã‚¹ã‚’グループ化ã™ã‚‹ãŸã‚ã«ä½¿ç”¨ã§ãã¾ã™ã€‚メタデータã®ä½¿ç”¨ã¯ã€Œraxã€ã§å¼·ã推奨ã•ã‚Œã€ãƒ›ã‚¹ãƒˆã‚°ãƒ«ãƒ¼ãƒ—ã¨ãƒãƒ¼ãƒ«ã¨ã®é–“ã§ç°¡å˜ã«ä¸¦ã¹æ›¿ãˆã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚``rax.py`` ダイナミックインベントリースクリプトを使用ã—ãŸããªã„å ´åˆã¯ã€INI インベントリーファイルを手動ã§ç®¡ç†ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ãŒã€ã“ã‚Œã¯ã‚ã¾ã‚ŠãŠå‹§ã‚ã§ãã¾ã›ã‚“。" @@ -3593,6 +3357,28 @@ msgstr "`Vagrant Issue Tracker <https://github.com/hashicorp/vagrant/issues?q=is msgid "The open issues for the Ansible provisioner in the Vagrant project" msgstr "Vagrant プãƒã‚¸ã‚§ã‚¯ãƒˆã§ã® Ansible プãƒãƒ“ジョナーã«é–¢ã™ã‚‹æœªè§£æ±ºãªå•é¡Œ" +#: ../../rst/scenario_guides/guide_vagrant.rst:135 +#: ../../rst/scenario_guides/kubernetes_scenarios/k8s_inventory.rst:92 +#: ../../rst/scenario_guides/kubernetes_scenarios/scenario_k8s_object.rst:87 +#: ../../rst/scenario_guides/vmware_scenarios/vmware_intro.rst:52 +#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory.rst:88 +#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory_filters.rst:213 +#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory_hostnames.rst:125 +#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory_vm_attributes.rst:1181 +msgid ":ref:`working_with_playbooks`" +msgstr ":ref:`working_with_playbooks`" + +#: ../../rst/scenario_guides/guide_vagrant.rst:136 +#: ../../rst/scenario_guides/kubernetes_scenarios/k8s_inventory.rst:93 +#: ../../rst/scenario_guides/kubernetes_scenarios/scenario_k8s_object.rst:88 +#: ../../rst/scenario_guides/vmware_scenarios/vmware_intro.rst:53 +#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory.rst:89 +#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory_filters.rst:214 +#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory_hostnames.rst:126 +#: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory_vm_attributes.rst:1182 +msgid "An introduction to playbooks" +msgstr "Playbook ã®æ¦‚è¦" + #: ../../rst/scenario_guides/guide_vmware.rst:5 msgid "VMware Guide" msgstr "VMware ガイド" @@ -3745,12 +3531,12 @@ msgstr "ã™ã¹ã¦ã® Vultr テストを実行ã—ã¾ã™ã€‚" msgid "To run a specific test, for example vultr_account_info:" msgstr "特定ã®ãƒ†ã‚¹ãƒˆ (例: vultr_account_info) を実行ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/scenario_guides/guides.rst:28 +#: ../../rst/scenario_guides/guides.rst:32 #: ../../rst/scenario_guides/network_guides.rst:5 msgid "Network Technology Guides" msgstr "ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ†ã‚¯ãƒŽãƒã‚¸ãƒ¼ã‚¬ã‚¤ãƒ‰" -#: ../../rst/scenario_guides/guides.rst:36 +#: ../../rst/scenario_guides/guides.rst:40 msgid "Virtualization & Containerization Guides" msgstr "仮想化ãŠã‚ˆã³ã‚³ãƒ³ãƒ†ãƒŠãƒ¼åŒ–ガイド" @@ -3759,8 +3545,16 @@ msgid "Scenario Guides" msgstr "シナリオガイド" #: ../../rst/scenario_guides/guides.rst:9 -msgid "The guides in this section cover integrating Ansible with a variety of platforms, products, and technologies. They explore particular use cases in greater depth and provide a more \"top-down\" explanation of some basic features." -msgstr "本セクションã®ã‚¬ã‚¤ãƒ‰ã§ã¯ã€Ansible ã¨ã•ã¾ã–ã¾ãªãƒ—ラットフォームã€è£½å“ã€ãŠã‚ˆã³ãƒ†ã‚¯ãƒŽãƒã‚¸ãƒ¼ã®çµ±åˆã‚’説明ã—ã¾ã™ã€‚特定ã®ãƒ¦ãƒ¼ã‚¹ã‚±ãƒ¼ã‚¹ã‚’より深ã掘り下ã’ã€ã„ãã¤ã‹ã®åŸºæœ¬çš„ãªæ©Ÿèƒ½ã‚’「トップダウンã€ã§èª¬æ˜Žã—ã¾ã™ã€‚" +msgid "The guides in this section are migrating into collections. Remaining guides may be out of date." +msgstr "本セクションã®ã‚¬ã‚¤ãƒ‰ã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«ç§»è¡Œã—ã¦ã„ã¾ã™ã€‚残ã•ã‚ŒãŸã‚¬ã‚¤ãƒ‰ã¯ã€æƒ…å ±ãŒå¤ããªã£ã¦ã„ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" + +#: ../../rst/scenario_guides/guides.rst:11 +msgid "These guides cover integrating Ansible with a variety of platforms, products, and technologies. They explore particular use cases in greater depth and provide a more \"top-down\" explanation of some basic features." +msgstr "ã“れらã®ã‚¬ã‚¤ãƒ‰ã§ã¯ã€Ansible ã¨ã•ã¾ã–ã¾ãªãƒ—ラットフォームã€è£½å“ã€ãŠã‚ˆã³ãƒ†ã‚¯ãƒŽãƒã‚¸ãƒ¼ã®çµ±åˆã‚’説明ã—ã¾ã™ã€‚特定ã®ãƒ¦ãƒ¼ã‚¹ã‚±ãƒ¼ã‚¹ã‚’より深ã掘り下ã’ã€ã„ãã¤ã‹ã®åŸºæœ¬çš„ãªæ©Ÿèƒ½ã‚’「トップダウンã€ã§èª¬æ˜Žã—ã¾ã™ã€‚" + +#: ../../rst/scenario_guides/guides.rst:13 +msgid "We are migrating these guides into collections. Please update your links for the following guides:" +msgstr "ã“れらã®ã‚¬ã‚¤ãƒ‰ã‚’コレクションã«ç§»è¡Œã—ã¦ã„ã¾ã™ã€‚以下ã®ã‚¬ã‚¤ãƒ‰ã®ãƒªãƒ³ã‚¯ã‚’æ›´æ–°ã—ã¦ãã ã•ã„。" #: ../../rst/scenario_guides/kubernetes_scenarios/k8s_intro.rst:5 msgid "Introduction to Ansible for Kubernetes" @@ -8262,3 +8056,171 @@ msgstr "``open-vm-tools`` 㧠``netplan`` ãŒã‚µãƒãƒ¼ãƒˆã•ã‚Œã‚‹ã®ã‚’å¾…ã¡ã #~ msgid "If you find a bug or have a suggestion regarding modules, please file issues at `Ansible Kubernetes collection <https://github.com/ansible-collections/community.kubernetes>`_. If you find a bug regarding OpenShift client, please file issues at `OpenShift REST Client issues <https://github.com/openshift/openshift-restclient-python/issues>`_. If you find a bug regarding Kubectl binary, please file issues at `Kubectl issue tracker <https://github.com/kubernetes/kubectl>`_" #~ msgstr "ãƒã‚°ãŒè¦‹ã¤ã‹ã£ãŸå ´åˆã‚„モジュールã«é–¢ã™ã‚‹æ案をãŠå¯„ã›ã„ãŸã ã‘ã‚‹å ´åˆã¯ã€`Ansible Kubernetes コレクション <https://github.com/ansible-collections/community.kubernetes>`_ ã«ãƒ•ã‚¡ã‚¤ãƒ«ã®å•é¡Œã‚’å ±å‘Šã—ã¦ãã ã•ã„。OpenShift クライアントã«é–¢ã™ã‚‹ãƒã‚°ãŒè¦‹ã¤ã‹ã£ãŸå ´åˆã¯ã€`OpenShift REST クライアントã®å•é¡Œ <https://github.com/openshift/openshift-restclient-python/issues>`_ ã«å•é¡Œã‚’作æˆã—ã¦ãã ã•ã„。Kubectl ãƒã‚¤ãƒŠãƒªãƒ¼ã«é–¢ã™ã‚‹ãƒã‚°ã¯ã€`Kubectl issue tracker <https://github.com/kubernetes/kubectl>`_ ã§å•é¡Œã‚’作æˆã—ã¦ãã ã•ã„。" +#~ msgid "Ansible contains a number of modules for controlling Amazon Web Services (AWS). The purpose of this section is to explain how to put Ansible modules together (and use inventory scripts) to use Ansible in AWS context." +#~ msgstr "Ansible ã«ã¯ã€Amazon Web Services (AWS) を制御ã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒå¤šæ•°å«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã®ç›®çš„ã¯ã€AWS ã®ã‚³ãƒ³ãƒ†ã‚スト㧠Ansible を使用ã™ã‚‹ãŸã‚ã«ã€Ansible モジュールをã©ã®ã‚ˆã†ã«çµ„ã¿åˆã‚ã›ã‚‹ã‹ (インベントリースクリプトを使用ã™ã‚‹ã‹) を説明ã™ã‚‹ã“ã¨ã§ã™ã€‚" + +#~ msgid "Requirements for the AWS modules are minimal." +#~ msgstr "AWS モジュールã®è¦ä»¶ã¯æœ€å°é™ã§ã™ã€‚" + +#~ msgid "All of the modules require and are tested against recent versions of botocore and boto3. Starting with the 2.0 AWS collection releases, it is generally the policy of the collections to support the versions of these libraries released 12 months prior to the most recent major collection revision. Individual modules may require a more recent library version to support specific features or may require the boto library, check the module documentation for the minimum required version for each module. You must have the boto3 Python module installed on your control machine. You can install these modules from your OS distribution or using the python package installer: ``pip install boto3``." +#~ msgstr "ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€botocore ãŠã‚ˆã³ boto3 ã®æœ€æ–°ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’å¿…è¦ã¨ã—ã€ãれらã«å¯¾ã—ã¦ãƒ†ã‚¹ãƒˆã•ã‚Œã¦ã„ã¾ã™ã€‚2.0 AWS コレクションリリース以é™ã€é€šå¸¸ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã®ãƒãƒªã‚·ãƒ¼ã¯ã€æœ€æ–°ã®ãƒ¡ã‚¸ãƒ£ãƒ¼ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãƒªãƒ“ジョン㮠12 カ月å‰ã«ãƒªãƒªãƒ¼ã‚¹ã•ã‚ŒãŸã“れらã®ãƒ©ã‚¤ãƒ–ラリーã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’サãƒãƒ¼ãƒˆã™ã‚‹ã“ã¨ã§ã™ã€‚個々ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã§ã¯ã€ç‰¹å®šã®æ©Ÿèƒ½ã‚’サãƒãƒ¼ãƒˆã™ã‚‹ãŸã‚ã«æœ€æ–°ã®ãƒ©ã‚¤ãƒ–ラリーãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒå¿…è¦ãªå ´åˆã‚„ã€boto ライブラリーãŒå¿…è¦ãªå ´åˆãŒã‚ã‚Šã¾ã™ã€‚モジュールã®ãƒ‰ã‚ュメントã§ã€å„モジュールã«å¿…è¦ãªæœ€ä½Žãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’確èªã—ã¦ãã ã•ã„。制御マシン㫠boto3 Python モジュールãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“れらã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€OS ディストリビューションã‹ã‚‰ã€ã¾ãŸã¯ python パッケージインストーラーを使用ã—ã¦ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ãã¾ã™ (``pip install boto3``)。" + +#~ msgid "Starting with the 2.0 releases of both collections, Python 2.7 support will be ended in accordance with AWS' `end of Python 2.7 support <https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-python-2-7-in-aws-sdk-for-python-and-aws-cli-v1/>`_ and Python 3.6 or greater will be required." +#~ msgstr "両方ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã§ 2.0 リリース以é™ã€Python 2.7 サãƒãƒ¼ãƒˆã¯ AWS ã® `Python 2.7 サãƒãƒ¼ãƒˆã®çµ‚了 <https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-python-2-7-in-aws-sdk-for-python-and-aws-cli-v1/>`_ 㨠Python 3.6 以上ã«å¿œã˜ã¦çµ‚了ã—ã¾ã™ã€‚" + +#~ msgid "Whereas classically Ansible will execute tasks in its host loop against multiple remote machines, most cloud-control steps occur on your local machine with reference to the regions to control." +#~ msgstr "従æ¥ã€Ansible ã¯ãƒ›ã‚¹ãƒˆãƒ«ãƒ¼ãƒ—内ã®ã‚¿ã‚¹ã‚¯ã‚’複数ã®ãƒªãƒ¢ãƒ¼ãƒˆãƒžã‚·ãƒ³ã«å¯¾ã—ã¦å®Ÿè¡Œã—ã¾ã™ãŒã€ã»ã¨ã‚“ã©ã®ã‚¯ãƒ©ã‚¦ãƒ‰åˆ¶å¾¡æ‰‹é †ã¯ã€åˆ¶å¾¡ã™ã‚‹ãƒªãƒ¼ã‚¸ãƒ§ãƒ³ã‚’å‚ç…§ã™ã‚‹ãƒãƒ¼ã‚«ãƒ«ãƒžã‚·ãƒ³ã§å®Ÿè¡Œã—ã¾ã™ã€‚" + +#~ msgid "In your playbook steps we'll typically be using the following pattern for provisioning steps::" +#~ msgstr "Playbook ã®æ‰‹é †ã§ã¯ã€é€šå¸¸ã€ãƒ—ãƒãƒ“ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°æ‰‹é †ã«ä»¥ä¸‹ã®ãƒ‘ターンを使用ã—ã¾ã™::" + +#~ msgid "Authentication with the AWS-related modules is handled by either specifying your access and secret key as ENV variables or module arguments." +#~ msgstr "AWS 関連ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ãŸèªè¨¼ã¯ã€ENV 変数ã¾ãŸã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«å¼•æ•°ã¨ã—ã¦ã‚¢ã‚¯ã‚»ã‚¹ãŠã‚ˆã³ç§˜å¯†éµã‚’指定ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šå‡¦ç†ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "For environment variables::" +#~ msgstr "環境変数ã®å ´åˆ::" + +#~ msgid "For storing these in a vars_file, ideally encrypted with ansible-vault::" +#~ msgstr "vars_file ã«ä¿å˜ã™ã‚‹ã«ã¯ã€ansible-vault ã§æš—å·åŒ–ã™ã‚‹ã“ã¨ãŒç†æƒ³çš„ã§ã™::" + +#~ msgid "Note that if you store your credentials in vars_file, you need to refer to them in each AWS-module. For example::" +#~ msgstr "èªè¨¼æƒ…å ±ã‚’ vars_file ã«ä¿å˜ã™ã‚‹å ´åˆã¯ã€å„ AWS モジュールã§èªè¨¼æƒ…å ±ã‚’å‚ç…§ã™ã‚‹å¿…è¦ãŒã‚ã‚‹ã“ã¨ã«æ³¨æ„ã—ã¦ãã ã•ã„。以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" + +#~ msgid "The ec2 module provisions and de-provisions instances within EC2." +#~ msgstr "ec2 モジュールã¯ã€EC2 内ã§ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã®ãƒ—ãƒãƒ“ジョニングãŠã‚ˆã³ãƒ—ãƒãƒ“ジョニング解除を行ã„ã¾ã™ã€‚" + +#~ msgid "An example of making sure there are only 5 instances tagged 'Demo' in EC2 follows." +#~ msgstr "EC2 ã§ã€ŒDemoã€ã¨ã‚¿ã‚°ä»˜ã‘ã•ã‚ŒãŸã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ãŒ 5 個ã«ãªã‚‹ã‚ˆã†ã«ã™ã‚‹ä¾‹ã‚’以下ã«ç¤ºã—ã¾ã™ã€‚" + +#~ msgid "In the example below, the \"exact_count\" of instances is set to 5. This means if there are 0 instances already existing, then 5 new instances would be created. If there were 2 instances, only 3 would be created, and if there were 8 instances, 3 instances would be terminated." +#~ msgstr "以下ã®ä¾‹ã§ã¯ã€ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã®ã€Œexact_countã€ã¯ 5 ã«è¨å®šã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ã€ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ãŒãªã„å ´åˆã¯ã€æ–°è¦ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ãŒ 5 個作æˆã•ã‚Œã‚‹ã“ã¨ã‚’示ã—ã¦ã„ã¾ã™ã€‚インスタンス㌠2 個ã‚ã‚‹å ´åˆã¯ã€3 個作æˆã•ã‚Œã€ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ãŒ 8 個ã‚ã‚‹å ´åˆã¯ã€3 個ã®ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ãŒçµ‚了ã—ã¾ã™ã€‚" + +#~ msgid "What is being counted is specified by the \"count_tag\" parameter. The parameter \"instance_tags\" is used to apply tags to the newly created instance.::" +#~ msgstr "カウントã•ã‚Œã‚‹ã‚‚ã®ã¯ã€Œcount_tagã€ãƒ‘ラメーターã§æŒ‡å®šã—ã¾ã™ã€‚「instance_tagsã€ãƒ‘ラメーターã¯ã€æ–°ãŸã«ä½œæˆã•ã‚ŒãŸã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã‚’ã‚¿ã‚°ã«é©ç”¨ã™ã‚‹ãŸã‚ã«ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "The data about what instances are created is being saved by the \"register\" keyword in the variable named \"ec2\"." +#~ msgstr "作æˆã•ã‚Œã‚‹ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã«é–¢ã™ã‚‹ãƒ‡ãƒ¼ã‚¿ã¯ã€ã€Œec2ã€ã¨ã„ã†å¤‰æ•°ã®ã€Œregisterã€ã‚ーワードã«ã‚ˆã£ã¦ä¿å˜ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "From this, we'll use the add_host module to dynamically create a host group consisting of these new instances. This facilitates performing configuration actions on the hosts immediately in a subsequent task.::" +#~ msgstr "ã“ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‹ã‚‰ add_host モジュールを使用ã—ã€ã“れらã®æ–°è¦ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã§æ§‹æˆã•ã‚Œã‚‹ãƒ›ã‚¹ãƒˆã‚°ãƒ«ãƒ¼ãƒ—ã‚’å‹•çš„ã«ä½œæˆã—ã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€å¾Œç¶šã®ã‚¿ã‚¹ã‚¯ã§ã€ãƒ›ã‚¹ãƒˆã§ã®è¨å®šã‚¢ã‚¯ã‚·ãƒ§ãƒ³ã‚’ã™ãã«å®Ÿè¡Œã§ãã¾ã™ã€‚" + +#~ msgid "With the host group now created, a second play at the bottom of the same provisioning playbook file might now have some configuration steps::" +#~ msgstr "ã“ã‚Œã§ãƒ›ã‚¹ãƒˆã‚°ãƒ«ãƒ¼ãƒ—ãŒä½œæˆã•ã‚ŒãŸã®ã§ã€åŒã˜ãƒ—ãƒãƒ“ジョニング Playbook ファイルã®ä¸‹éƒ¨ã«ã‚ã‚‹2ã¤ç›®ã®ãƒ—レイã§ã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ãªè¨å®šã‚¹ãƒ†ãƒƒãƒ—ãŒå¿…è¦ã«ãªã‚Šã¾ã™ã€‚" + +#~ msgid "Security Groups" +#~ msgstr "ã‚»ã‚ュリティーグループ" + +#~ msgid "Security groups on AWS are stateful. The response of a request from your instance is allowed to flow in regardless of inbound security group rules and vice-versa. In case you only want allow traffic with AWS S3 service, you need to fetch the current IP ranges of AWS S3 for one region and apply them as an egress rule.::" +#~ msgstr "AWS ã®ã‚»ã‚ュリティーグループã¯ã‚¹ãƒ†ãƒ¼ãƒˆãƒ•ãƒ«ã§ã™ã€‚インスタンスã‹ã‚‰ã®è¦æ±‚ã®å¿œç”ã¯ã€å—ä¿¡ã‚»ã‚ュリティーグループルールã«é–¢ä¿‚ãªãæµå…¥ãŒè¨±å¯ã•ã‚Œã€ãã®é€†ã‚‚åŒæ§˜ã§ã™ã€‚AWS S3 サービスを使用ã™ã‚‹ãƒˆãƒ©ãƒ•ã‚£ãƒƒã‚¯ã®ã¿ã‚’許å¯ã™ã‚‹å ´åˆã¯ã€ã‚るリージョンã«å¯¾ã—㦠AWS S3 ã®ç¾åœ¨ã® IP 範囲をå–å¾—ã—ã€ãれを egress ルールã¨ã—ã¦é©ç”¨ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "Once your nodes are spun up, you'll probably want to talk to them again. With a cloud setup, it's best to not maintain a static list of cloud hostnames in text files. Rather, the best way to handle this is to use the aws_ec2 inventory plugin. See :ref:`dynamic_inventory`." +#~ msgstr "ノードãŒèµ·å‹•ã—ãŸã‚‰ã€ãŠãらãå†é€šä¿¡ã™ã‚‹ã‚ˆã†ã«ã—ãŸã„ã§ã—ょã†ã€‚クラウドè¨å®šã§ã¯ã€ãƒ†ã‚ストファイルã«ã€ã‚¯ãƒ©ã‚¦ãƒ‰ãƒ›ã‚¹ãƒˆåã®é™çš„リストをç¶æŒã—ãªã„ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚ã“れを処ç†ã™ã‚‹æœ€å–„ã®æ–¹æ³•ã¯ã€aws_ec2 インベントリープラグインを使用ã™ã‚‹ã“ã¨ã§ã™ã€‚:ref:`dynamic_inventory` ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "The plugin will also return instances that were created outside of Ansible and allow Ansible to manage them." +#~ msgstr "ã“ã®ãƒ—ラグインã«ã‚ˆã‚Šã€Ansible 外ã§ä½œæˆã•ã‚ŒãŸã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã‚‚é¸æŠžã•ã‚Œã€Ansible ãŒã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã‚’管ç†ã§ãるよã†ã«ãªã‚Šã¾ã™ã€‚" + +#~ msgid "Tags And Groups And Variables" +#~ msgstr "ã‚¿ã‚°ã€ã‚°ãƒ«ãƒ¼ãƒ—ã€ãŠã‚ˆã³å¤‰æ•°" + +#~ msgid "When using the inventory plugin, you can configure extra inventory structure based on the metadata returned by AWS." +#~ msgstr "インベントリープラグインを使用ã™ã‚‹å ´åˆã¯ã€AWS ã«ã‚ˆã‚Šè¿”ã•ã‚Œã‚‹ãƒ¡ã‚¿ãƒ‡ãƒ¼ã‚¿ã«åŸºã¥ã„ã¦è¿½åŠ ã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼æ§‹é€ ã‚’è¨å®šã§ãã¾ã™ã€‚" + +#~ msgid "For instance, you might use ``keyed_groups`` to create groups from instance tags::" +#~ msgstr "ãŸã¨ãˆã°ã€``keyed_groups`` を使用ã—ã¦ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã‚¿ã‚°ã‹ã‚‰ã‚°ãƒ«ãƒ¼ãƒ—を作æˆã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" + +#~ msgid "You can then target all instances with a \"class\" tag where the value is \"webserver\" in a play::" +#~ msgstr "次ã«ã€ã€Œclassã€ã‚¿ã‚°ã®ä»˜ã„ãŸã™ã¹ã¦ã®ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã‚’ターゲットã«ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã“ã§ã€å€¤ã¯ãƒ—レイ内ã®ã€Œwebserverã€ã«ãªã‚Šã¾ã™ã€‚" + +#~ msgid "You can also use these groups with 'group_vars' to set variables that are automatically applied to matching instances. See :ref:`splitting_out_vars`." +#~ msgstr "「group_varsã€ã§ã“れらã®ã‚°ãƒ«ãƒ¼ãƒ—を使用ã—ã¦ã€ä¸€è‡´ã™ã‚‹ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã«è‡ªå‹•çš„ã«é©ç”¨ã•ã‚Œã‚‹å¤‰æ•°ã‚’è¨å®šã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚「:ref:`splitting_out_vars`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "Autoscaling with Ansible Pull" +#~ msgstr "Ansible Pull を使用ã—ãŸè‡ªå‹•ã‚¹ã‚±ãƒ¼ãƒªãƒ³ã‚°" + +#~ msgid "Amazon Autoscaling features automatically increase or decrease capacity based on load. There are also Ansible modules shown in the cloud documentation that can configure autoscaling policy." +#~ msgstr "Amazon Autoscaling 機能ã¯ã€è² è·ã«å¿œã˜ã¦å®¹é‡ã‚’自動的ã«å¢—減ã—ã¾ã™ã€‚ã¾ãŸã€ã‚¯ãƒ©ã‚¦ãƒ‰ãƒ‰ã‚ュメントã§èª¬æ˜Žã•ã‚Œã‚‹ã‚ˆã†ã«ã€è‡ªå‹•ã‚¹ã‚±ãƒ¼ãƒªãƒ³ã‚°ãƒãƒªã‚·ãƒ¼ã‚’è¨å®šã™ã‚‹ Ansible モジュールãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "When nodes come online, it may not be sufficient to wait for the next cycle of an ansible command to come along and configure that node." +#~ msgstr "ノードãŒã‚ªãƒ³ãƒ©ã‚¤ãƒ³ã«ãªã‚‹ã¨ã€ansible コマンドã®æ¬¡ã®ã‚µã‚¤ã‚¯ãƒ«ãŒåæ˜ ã•ã‚Œã¦ãã®ãƒŽãƒ¼ãƒ‰ã‚’è¨å®šã™ã‚‹ã®ã‚’å¾…ã¤ã“ã¨ãŒã§ããªã„å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "To do this, pre-bake machine images which contain the necessary ansible-pull invocation. Ansible-pull is a command line tool that fetches a playbook from a git server and runs it locally." +#~ msgstr "ãã®ãŸã‚ã«ã¯ã€å¿…è¦ãª ansible-pull 呼ã³å‡ºã—ã‚’å«ã‚€ãƒžã‚·ãƒ³ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’事å‰ã«ä½œæˆã—ã¾ã™ã€‚ansible-pull ã¯ã€git サーãƒãƒ¼ã‹ã‚‰ Playbook ã‚’å–å¾—ã—ã€ãƒãƒ¼ã‚«ãƒ«ã§å®Ÿè¡Œã™ã‚‹ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ãƒ„ールã§ã™ã€‚" + +#~ msgid "One of the challenges of this approach is that there needs to be a centralized way to store data about the results of pull commands in an autoscaling context. For this reason, the autoscaling solution provided below in the next section can be a better approach." +#~ msgstr "ã“ã®ã‚¢ãƒ—ãƒãƒ¼ãƒã®èª²é¡Œã® 1 ã¤ã¨ã—ã¦ã€pull コマンドã®çµæžœã«é–¢ã™ã‚‹ãƒ‡ãƒ¼ã‚¿ã‚’自動スケーリングコンテã‚ストã«ä¿å˜ã™ã‚‹é›†ä¸çš„ãªæ–¹æ³•ãŒå¿…è¦ã«ãªã‚Šã¾ã™ã€‚ã“ã®ãŸã‚ã€æ¬¡ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§æä¾›ã•ã‚Œã‚‹è‡ªå‹•ã‚¹ã‚±ãƒ¼ãƒªãƒ³ã‚°ã‚½ãƒªãƒ¥ãƒ¼ã‚·ãƒ§ãƒ³ã®æ–¹ãŒé©åˆ‡ã§ã™ã€‚" + +#~ msgid "Read :ref:`ansible-pull` for more information on pull-mode playbooks." +#~ msgstr "pull モード㮠Playbook ã®è©³ç´°ã¯ã€ã€Œ:ref:`ansible-pull`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "Autoscaling with Ansible Tower" +#~ msgstr "Ansible Tower を使用ã—ãŸè‡ªå‹•ã‚¹ã‚±ãƒ¼ãƒªãƒ³ã‚°" + +#~ msgid ":ref:`ansible_tower` also contains a very nice feature for auto-scaling use cases. In this mode, a simple curl script can call a defined URL and the server will \"dial out\" to the requester and configure an instance that is spinning up. This can be a great way to reconfigure ephemeral nodes. See the Tower install and product documentation for more details." +#~ msgstr "ã¾ãŸã€:ref:`ansible_tower` ã¯ã€è‡ªå‹•ã‚¹ã‚±ãƒ¼ãƒªãƒ³ã‚°ã®ãƒ¦ãƒ¼ã‚¹ã‚±ãƒ¼ã‚¹ã«ã¯éžå¸¸ã«å„ªã‚ŒãŸæ©Ÿèƒ½ã‚‚å«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ã“ã®ãƒ¢ãƒ¼ãƒ‰ã§ã¯ã€ç°¡å˜ãª curl スクリプトã¯å®šç¾©ã•ã‚ŒãŸ URL を呼ã³å‡ºã™ã“ã¨ãŒã§ãã€ã‚µãƒ¼ãƒãƒ¼ã¯è¦æ±‚å…ƒã«å¯¾ã—ã¦ã€Œãƒ€ã‚¤ãƒ¤ãƒ«ã‚¢ã‚¦ãƒˆã€ã—ã€èµ·å‹•ã—ã¦ã„るインスタンスを構æˆã—ã¾ã™ã€‚ã“ã‚Œã¯ã€ä¸€æ™‚ノードをå†è¨å®šã™ã‚‹å„ªã‚ŒãŸæ–¹æ³•ã«ãªã‚Šã¾ã™ã€‚詳細ã¯ã€Tower ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã¨è£½å“ã®ãƒ‰ã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "A benefit of using the callback in Tower over pull mode is that job results are still centrally recorded and less information has to be shared with remote hosts." +#~ msgstr "pull モード㧠Tower ã®ã‚³ãƒ¼ãƒ«ãƒãƒƒã‚¯ã‚’使用ã™ã‚‹åˆ©ç‚¹ã¯ã€ã‚¸ãƒ§ãƒ–ã®çµæžœãŒå¼•ã続ãä¸å¤®ã§è¨˜éŒ²ã•ã‚Œã€ãƒªãƒ¢ãƒ¼ãƒˆãƒ›ã‚¹ãƒˆã¨å…±æœ‰ã™ã‚‹å¿…è¦ã®ã‚ã‚‹æƒ…å ±ãŒå°‘ãªããªã‚‹ã“ã¨ã§ã™ã€‚" + +#~ msgid "Ansible With (And Versus) CloudFormation" +#~ msgstr "CloudFormation を使用ã—㟠Ansible (Ansible 㨠CloudFormation ã®æ¯”較)" + +#~ msgid "CloudFormation is a Amazon technology for defining a cloud stack as a JSON or YAML document." +#~ msgstr "CloudFormation ã¯ã€ã‚¯ãƒ©ã‚¦ãƒ‰ã‚¹ã‚¿ãƒƒã‚¯ã‚’ JSON ã¾ãŸã¯ YAML ã®ãƒ‰ã‚ュメントã¨ã—ã¦å®šç¾©ã™ã‚‹ Amazon テクノãƒã‚¸ãƒ¼ã§ã™ã€‚" + +#~ msgid "Ansible modules provide an easier to use interface than CloudFormation in many examples, without defining a complex JSON/YAML document. This is recommended for most users." +#~ msgstr "Ansible モジュールã¯ã€è¤‡é›‘㪠JSON/YAML ドã‚ュメントを定義ã›ãšã«ã€å¤šãã®ä¾‹ã§ CloudFormation よりも簡å˜ã«ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ã‚’使用ã§ãã¾ã™ã€‚ã“ã‚Œã¯ã€ã»ã¨ã‚“ã©ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«æŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "However, for users that have decided to use CloudFormation, there is an Ansible module that can be used to apply a CloudFormation template to Amazon." +#~ msgstr "ãŸã ã—ã€CloudFormation を使用ã™ã‚‹ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«ã¯ã€CloudFormation テンプレートを Amazon ã«é©ç”¨ã™ã‚‹ã®ã«ä½¿ç”¨ã§ãã‚‹ Ansible モジュールãŒã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "When using Ansible with CloudFormation, typically Ansible will be used with a tool like Packer to build images, and CloudFormation will launch those images, or ansible will be invoked through user data once the image comes online, or a combination of the two." +#~ msgstr "CloudFormation 㧠Ansible を使用ã™ã‚‹å ´åˆã¯ã€é€šå¸¸ã€Ansible ã‚’ Packer ãªã©ã®ãƒ„ールã§ä½¿ç”¨ã—ã¦ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’作æˆã—ã€CloudFormation ãŒãã®ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’èµ·å‹•ã™ã‚‹ã‹ã€ã‚¤ãƒ¡ãƒ¼ã‚¸ãŒã‚ªãƒ³ãƒ©ã‚¤ãƒ³ã«ãªã‚‹ã¨ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãƒ‡ãƒ¼ã‚¿ã‚’通ã˜ã¦ ansible ãŒå‘¼ã³å‡ºã•ã‚Œã‚‹ã‹ã€ãã®çµ„ã¿åˆã‚ã›ã¨ãªã‚Šã¾ã™ã€‚" + +#~ msgid "Please see the examples in the Ansible CloudFormation module for more details." +#~ msgstr "詳細ã¯ã€Ansible CloudFormation モジュールã®ã‚µãƒ³ãƒ—ルをå‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "AWS Image Building With Ansible" +#~ msgstr "Ansible ã§ã® AWS イメージã®æ§‹ç¯‰" + +#~ msgid "Many users may want to have images boot to a more complete configuration rather than configuring them entirely after instantiation. To do this, one of many programs can be used with Ansible playbooks to define and upload a base image, which will then get its own AMI ID for usage with the ec2 module or other Ansible AWS modules such as ec2_asg or the cloudformation module. Possible tools include Packer, aminator, and Ansible's ec2_ami module." +#~ msgstr "多ãã®å ´åˆã€ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹åŒ–後ã«ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’完全ã«è¨å®šã™ã‚‹ã®ã§ã¯ãªãã€ã‚ˆã‚Šå®Œå…¨ãªè¨å®šã§ã®èµ·å‹•ã‚’望ã¿ã¾ã™ã€‚ã“れを行ã†ã«ã¯ã€Ansible Playbook ã¨ã¨ã‚‚ã«å¤šãã®ãƒ—ãƒã‚°ãƒ©ãƒ ã®ä¸ã‹ã‚‰ 1 ã¤ä½¿ç”¨ã—ã¦ãƒ™ãƒ¼ã‚¹ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’定義ã—ã€ã‚¢ãƒƒãƒ—ãƒãƒ¼ãƒ‰ã§ãã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ec2 モジュールã€ec2_asg モジュールや cloudformation モジュールãªã©ã®ãã®ä»–ã® Ansible AWS モジュールã¨ä½¿ç”¨ã™ã‚‹ãŸã‚ã€ç‹¬è‡ªã® AMI ID ã‚’å–å¾—ã—ã¾ã™ã€‚ツールã«ã¯ Packerã€aminatorã€ãŠã‚ˆã³ Ansible ã® ec2_ami モジュールãŒå«ã¾ã‚Œã¾ã™ã€‚" + +#~ msgid "Generally speaking, we find most users using Packer." +#~ msgstr "一般的ã«ã¯ã€Packer ãŒä½¿ç”¨ã•ã‚Œã¾ã™ã€‚" + +#~ msgid "See the Packer documentation of the `Ansible local Packer provisioner <https://www.packer.io/docs/provisioners/ansible/ansible-local>`_ and `Ansible remote Packer provisioner <https://www.packer.io/docs/provisioners/ansible/ansible>`_." +#~ msgstr "`Ansible local Packer provisioner <https://www.packer.io/docs/provisioners/ansible/ansible-local>`_ ãŠã‚ˆã³ `Ansible remote Packer provisioner <https://www.packer.io/docs/provisioners/ansible/ansible>`_ ã® Packer ドã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid "If you do not want to adopt Packer at this time, configuring a base-image with Ansible after provisioning (as shown above) is acceptable." +#~ msgstr "ç¾æ™‚点ã§ã¯ã€Packer を使用ã—ãªã„å ´åˆã¯ã€ãƒ—ãƒãƒ“ジョニング後㫠(上記ã®ã‚ˆã†ã«) Ansible を使用ã—ãŸãƒ™ãƒ¼ã‚¹ã‚¤ãƒ¡ãƒ¼ã‚¸ã®è¨å®šãŒå¯èƒ½ã§ã™ã€‚" + +#~ msgid "Next Steps: Explore Modules" +#~ msgstr "次ã®ã‚¹ãƒ†ãƒƒãƒ—: モジュールã®æ¤œè¨¼" + +#~ msgid "Ansible ships with lots of modules for configuring a wide array of EC2 services. Browse the \"Cloud\" category of the module documentation for a full list with examples." +#~ msgstr "Ansible ã«ã¯ã€ã•ã¾ã–ã¾ãª EC2 サービスをè¨å®šã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒå¤šæ•°åŒæ¢±ã•ã‚Œã¦ã„ã¾ã™ã€‚例をå«ã‚€å®Œå…¨ãªä¸€è¦§ã«ã¤ã„ã¦ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒ‰ã‚ュメントã®ã€Œã‚¯ãƒ©ã‚¦ãƒ‰ã€ã‚«ãƒ†ã‚´ãƒªãƒ¼ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#~ msgid ":ref:`list_of_collections`" +#~ msgstr ":ref:`list_of_collections`" + +#~ msgid "Browse existing collections, modules, and plugins" +#~ msgstr "æ—¢å˜ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€ãŠã‚ˆã³ãƒ—ラグインã®é–²è¦§" + +#~ msgid ":ref:`playbooks_delegation`" +#~ msgstr ":ref:`playbooks_delegation`" + +#~ msgid "Delegation, useful for working with loud balancers, clouds, and locally executed steps." +#~ msgstr "å§”è² (ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚µãƒ¼ã€ã‚¯ãƒ©ã‚¦ãƒ‰ã€ãƒãƒ¼ã‚«ãƒ«ã§å®Ÿè¡Œã—ãŸæ‰‹é †ã‚’使用ã™ã‚‹éš›ã«å½¹ã«ç«‹ã¡ã¾ã™)" + +#~ msgid "`User Mailing List <https://groups.google.com/group/ansible-devel>`_" +#~ msgstr "`ユーザーメーリングリスト <https://groups.google.com/group/ansible-devel>`_" + +#~ msgid ":ref:`communication_irc`" +#~ msgstr ":ref:`communication_irc`" + +#~ msgid "How to join Ansible chat channels" +#~ msgstr "Ansible ãƒãƒ£ãƒƒãƒˆãƒãƒ£ãƒ³ãƒãƒ«ã¸ã®å‚åŠ æ–¹æ³•" + +#~ msgid "This section of the documentation is under construction. We are in the process of adding more examples about the Rackspace modules and how they work together. Once complete, there will also be examples for Rackspace Cloud in `ansible-examples <https://github.com/ansible/ansible-examples/>`_." +#~ msgstr "本ガイドã«è¨˜è¼‰ã™ã‚‹ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã¯ä½œæˆä¸ã§ã™ã€‚ã“ã“ã§ã¯ã€Rackspace モジュールやãã‚ŒãŒã©ã®ã‚ˆã†ã«é€£æºã™ã‚‹ã‹ã«ã¤ã„ã¦ã®ä¾‹ã‚’è¿½åŠ ã™ã‚‹ãƒ—ãƒã‚»ã‚¹ã§ã™ã€‚完了後ã¯ã€`ansible-examples <https://github.com/ansible/ansible-examples/>`_ ã« Rackspace Cloud ã®ä¾‹ã‚‚ã‚ã‚Šã¾ã™ã€‚" + diff --git a/docs/docsite/rst/locales/ja/LC_MESSAGES/user_guide.po b/docs/docsite/rst/locales/ja/LC_MESSAGES/user_guide.po index 7eed1728..0a874244 100644 --- a/docs/docsite/rst/locales/ja/LC_MESSAGES/user_guide.po +++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/user_guide.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Ansible devel\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-10-05 13:53+0200\n" +"POT-Creation-Date: 2021-11-09 14:07+0100\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" @@ -687,93 +687,93 @@ msgstr "`Mailing List <https://groups.google.com/forum/#!forum/ansible-project>` #: ../../rst/user_guide/become.rst:755 ../../rst/user_guide/intro_adhoc.rst:210 #: ../../rst/user_guide/intro_bsd.rst:104 -#: ../../rst/user_guide/intro_dynamic_inventory.rst:247 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:251 #: ../../rst/user_guide/intro_getting_started.rst:196 -#: ../../rst/user_guide/intro_inventory.rst:789 -#: ../../rst/user_guide/intro_patterns.rst:199 +#: ../../rst/user_guide/intro_inventory.rst:791 +#: ../../rst/user_guide/intro_patterns.rst:225 #: ../../rst/user_guide/modules.rst:34 -#: ../../rst/user_guide/modules_intro.rst:50 +#: ../../rst/user_guide/modules_intro.rst:60 #: ../../rst/user_guide/modules_support.rst:68 #: ../../rst/user_guide/playbooks_best_practices.rst:167 -#: ../../rst/user_guide/playbooks_intro.rst:155 +#: ../../rst/user_guide/playbooks_intro.rst:159 #: ../../rst/user_guide/playbooks_reuse.rst:221 #: ../../rst/user_guide/playbooks_reuse_includes.rst:32 #: ../../rst/user_guide/playbooks_reuse_roles.rst:623 -#: ../../rst/user_guide/sample_setup.rst:285 +#: ../../rst/user_guide/sample_setup.rst:321 msgid "Questions? Help? Ideas? Stop by the list on Google Groups" msgstr "ã”質å•ã¯ã”ã–ã„ã¾ã™ã‹ã€‚サãƒãƒ¼ãƒˆãŒå¿…è¦ã§ã™ã‹ã€‚ã”æ案ã¯ã”ã–ã„ã¾ã™ã‹ã€‚Google グループã®ä¸€è¦§ã‚’ã”覧ãã ã•ã„。" #: ../../rst/user_guide/become.rst:756 -#: ../../rst/user_guide/collections_using.rst:382 +#: ../../rst/user_guide/collections_using.rst:387 #: ../../rst/user_guide/intro_adhoc.rst:211 #: ../../rst/user_guide/intro_bsd.rst:105 -#: ../../rst/user_guide/intro_dynamic_inventory.rst:248 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:252 #: ../../rst/user_guide/intro_getting_started.rst:197 -#: ../../rst/user_guide/intro_inventory.rst:790 -#: ../../rst/user_guide/intro_patterns.rst:200 +#: ../../rst/user_guide/intro_inventory.rst:792 +#: ../../rst/user_guide/intro_patterns.rst:226 #: ../../rst/user_guide/modules.rst:35 -#: ../../rst/user_guide/modules_intro.rst:51 +#: ../../rst/user_guide/modules_intro.rst:61 #: ../../rst/user_guide/modules_support.rst:69 -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:111 -#: ../../rst/user_guide/playbooks_async.rst:174 +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:123 +#: ../../rst/user_guide/playbooks_async.rst:188 #: ../../rst/user_guide/playbooks_blocks.rst:188 -#: ../../rst/user_guide/playbooks_conditionals.rst:507 -#: ../../rst/user_guide/playbooks_debugger.rst:328 -#: ../../rst/user_guide/playbooks_delegation.rst:157 -#: ../../rst/user_guide/playbooks_environment.rst:140 -#: ../../rst/user_guide/playbooks_error_handling.rst:244 +#: ../../rst/user_guide/playbooks_conditionals.rst:535 +#: ../../rst/user_guide/playbooks_debugger.rst:341 +#: ../../rst/user_guide/playbooks_delegation.rst:173 +#: ../../rst/user_guide/playbooks_environment.rst:152 +#: ../../rst/user_guide/playbooks_error_handling.rst:272 #: ../../rst/user_guide/playbooks_filters.rst:1851 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:741 -#: ../../rst/user_guide/playbooks_lookups.rst:36 -#: ../../rst/user_guide/playbooks_loops.rst:446 -#: ../../rst/user_guide/playbooks_prompts.rst:115 -#: ../../rst/user_guide/playbooks_strategies.rst:224 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:863 +#: ../../rst/user_guide/playbooks_lookups.rst:38 +#: ../../rst/user_guide/playbooks_loops.rst:488 +#: ../../rst/user_guide/playbooks_prompts.rst:123 +#: ../../rst/user_guide/playbooks_strategies.rst:250 #: ../../rst/user_guide/playbooks_tags.rst:431 #: ../../rst/user_guide/playbooks_templating.rst:60 -#: ../../rst/user_guide/playbooks_tests.rst:402 -#: ../../rst/user_guide/playbooks_variables.rst:465 -#: ../../rst/user_guide/windows_dsc.rst:504 -#: ../../rst/user_guide/windows_faq.rst:250 -#: ../../rst/user_guide/windows_setup.rst:582 -#: ../../rst/user_guide/windows_usage.rst:512 -#: ../../rst/user_guide/windows_winrm.rst:913 +#: ../../rst/user_guide/playbooks_tests.rst:438 +#: ../../rst/user_guide/playbooks_variables.rst:511 +#: ../../rst/user_guide/windows_dsc.rst:506 +#: ../../rst/user_guide/windows_faq.rst:254 +#: ../../rst/user_guide/windows_setup.rst:605 +#: ../../rst/user_guide/windows_usage.rst:516 +#: ../../rst/user_guide/windows_winrm.rst:935 msgid ":ref:`communication_irc`" msgstr ":ref:`communication_irc`" #: ../../rst/user_guide/become.rst:757 -#: ../../rst/user_guide/collections_using.rst:383 +#: ../../rst/user_guide/collections_using.rst:388 #: ../../rst/user_guide/intro_adhoc.rst:212 #: ../../rst/user_guide/intro_bsd.rst:106 -#: ../../rst/user_guide/intro_dynamic_inventory.rst:249 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:253 #: ../../rst/user_guide/intro_getting_started.rst:198 -#: ../../rst/user_guide/intro_inventory.rst:791 -#: ../../rst/user_guide/intro_patterns.rst:201 +#: ../../rst/user_guide/intro_inventory.rst:793 +#: ../../rst/user_guide/intro_patterns.rst:227 #: ../../rst/user_guide/modules.rst:36 -#: ../../rst/user_guide/modules_intro.rst:52 +#: ../../rst/user_guide/modules_intro.rst:62 #: ../../rst/user_guide/modules_support.rst:70 -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:112 -#: ../../rst/user_guide/playbooks_async.rst:175 +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:124 +#: ../../rst/user_guide/playbooks_async.rst:189 #: ../../rst/user_guide/playbooks_blocks.rst:189 -#: ../../rst/user_guide/playbooks_conditionals.rst:508 -#: ../../rst/user_guide/playbooks_debugger.rst:329 -#: ../../rst/user_guide/playbooks_delegation.rst:158 -#: ../../rst/user_guide/playbooks_environment.rst:141 -#: ../../rst/user_guide/playbooks_error_handling.rst:245 +#: ../../rst/user_guide/playbooks_conditionals.rst:536 +#: ../../rst/user_guide/playbooks_debugger.rst:342 +#: ../../rst/user_guide/playbooks_delegation.rst:174 +#: ../../rst/user_guide/playbooks_environment.rst:153 +#: ../../rst/user_guide/playbooks_error_handling.rst:273 #: ../../rst/user_guide/playbooks_filters.rst:1852 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:742 -#: ../../rst/user_guide/playbooks_lookups.rst:37 -#: ../../rst/user_guide/playbooks_loops.rst:447 -#: ../../rst/user_guide/playbooks_prompts.rst:116 -#: ../../rst/user_guide/playbooks_strategies.rst:225 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:864 +#: ../../rst/user_guide/playbooks_lookups.rst:39 +#: ../../rst/user_guide/playbooks_loops.rst:489 +#: ../../rst/user_guide/playbooks_prompts.rst:124 +#: ../../rst/user_guide/playbooks_strategies.rst:251 #: ../../rst/user_guide/playbooks_tags.rst:432 #: ../../rst/user_guide/playbooks_templating.rst:61 -#: ../../rst/user_guide/playbooks_tests.rst:403 -#: ../../rst/user_guide/playbooks_variables.rst:466 -#: ../../rst/user_guide/windows_dsc.rst:505 -#: ../../rst/user_guide/windows_faq.rst:251 -#: ../../rst/user_guide/windows_setup.rst:583 -#: ../../rst/user_guide/windows_usage.rst:513 -#: ../../rst/user_guide/windows_winrm.rst:914 +#: ../../rst/user_guide/playbooks_tests.rst:439 +#: ../../rst/user_guide/playbooks_variables.rst:512 +#: ../../rst/user_guide/windows_dsc.rst:507 +#: ../../rst/user_guide/windows_faq.rst:255 +#: ../../rst/user_guide/windows_setup.rst:606 +#: ../../rst/user_guide/windows_usage.rst:517 +#: ../../rst/user_guide/windows_winrm.rst:936 msgid "How to join Ansible chat channels" msgstr "Ansible ãƒãƒ£ãƒƒãƒˆãƒãƒ£ãƒ³ãƒãƒ«ã¸ã®å‚åŠ æ–¹æ³•" @@ -922,6 +922,9 @@ msgid "To install a collection from a git repository at the command line, use th msgstr "git リãƒã‚¸ãƒˆãƒªãƒ¼ã‹ã‚‰ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã™ã‚‹ã«ã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³åã¾ãŸã¯ ``tar.gz`` ファイルã¸ã®ãƒ‘スã§ã¯ãªãã€ãƒªãƒã‚¸ãƒˆãƒªãƒ¼ã® URI を使用ã—ã¾ã™ã€‚``git+`` を使用ã—㦠URI をプレフィックスã—ã¾ã™ï¼ˆã¾ãŸã¯ ``git@`` を使用ã—ã¦ã€ssh èªè¨¼ã§ãƒ—ライベートリãƒã‚¸ãƒˆãƒªãƒ¼ã‚’使用ã—ã¾ã™ï¼‰ã€‚コンマ区切り㮠`git commit-ish <https://git-scm.com/docs/gitglossary#def_commit-ish>`_ 構文を使用ã—ã¦ã€ãƒ–ランãƒã€ã‚³ãƒŸãƒƒãƒˆã€ã¾ãŸã¯ã‚¿ã‚°ã‚’指定ã§ãã¾ã™ã€‚" #: ../../rst/shared_snippets/installing_collections_git_repo.txt:10 +#: ../../rst/user_guide/intro_patterns.rst:20 +#: ../../rst/user_guide/intro_patterns.rst:33 +#: ../../rst/user_guide/playbooks_checkmode.rst:33 #: ../../rst/user_guide/playbooks_tags.rst:285 #: ../../rst/user_guide/playbooks_tags.rst:315 msgid "For example:" @@ -1331,27 +1334,31 @@ msgstr "ã“ã®ã‚ˆã†ãª Playbook を作æˆã™ã‚‹éš›ã®ã„ãã¤ã‹ã®æŽ¨å¥¨äº‹é msgid "This will have an implied entry in the ``collections:`` keyword of ``my_namespace.my_collection`` just as with roles." msgstr "ã“ã‚Œã¯ã€ãƒãƒ¼ãƒ«ã¨åŒæ§˜ã«ã€``my_namespace.my_collection`` ã® ``collections:`` ã‚ーワードã«æš—黙的ãªã‚¨ãƒ³ãƒˆãƒªãƒ¼ã‚’æŒã¡ã¾ã™ã€‚" -#: ../../rst/user_guide/collections_using.rst:376 +#: ../../rst/user_guide/collections_using.rst:375 +msgid "Playbook names, like other collection resources, have a restricted set of valid characters. Names can contain only lowercase alphanumeric characters, plus _ and must start with an alpha character. The dash ``-`` character is not valid for playbook names in collections. Playbooks whose names contain invalid characters are not addressable: this is a limitation of the Python importer that is used to load collection resources." +msgstr "ä»–ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãƒªã‚½ãƒ¼ã‚¹ãªã©ã® Playbook åã§ã¯ã€æœ‰åŠ¹ãªæ–‡å—ã®ã‚»ãƒƒãƒˆãŒåˆ¶é™ã•ã‚Œã¦ã„ã¾ã™ã€‚åå‰ã«ã¯ã€å°æ–‡å—ã®è‹±æ•°å—㨠_ ã®ã¿ã‚’å«ã‚ã‚‹ã“ã¨ãŒã§ãã€ã‚¢ãƒ«ãƒ•ã‚¡ãƒ™ãƒƒãƒˆè¨˜å·ã§é–‹å§‹ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ダッシュ ``-`` ã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³å†…ã® Playbook åã«ã¯æœ‰åŠ¹ã§ã¯ã‚ã‚Šã¾ã›ã‚“。åå‰ã«ç„¡åŠ¹ãªæ–‡å—ãŒå«ã¾ã‚Œã‚‹Playbookã«ã‚¢ãƒ‰ãƒ¬ã‚¹ã‚’指定ã™ã‚‹ã“ã¨ã¯ã§ãã¾ã›ã‚“。ã“ã‚Œã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãƒªã‚½ãƒ¼ã‚¹ã®èªã¿è¾¼ã¿ã«ä½¿ç”¨ã•ã‚Œã‚‹ Python インãƒãƒ¼ã‚¿ãƒ¼ã®åˆ¶é™ã§ã™ã€‚" + +#: ../../rst/user_guide/collections_using.rst:381 msgid ":ref:`developing_collections`" msgstr ":ref:`developing_collections`" -#: ../../rst/user_guide/collections_using.rst:377 +#: ../../rst/user_guide/collections_using.rst:382 msgid "Develop or modify a collection." msgstr "コレクションを開発ã™ã‚‹ã‹ã€ã¾ãŸã¯å¤‰æ›´ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/collections_using.rst:378 +#: ../../rst/user_guide/collections_using.rst:383 msgid ":ref:`collections_galaxy_meta`" msgstr ":ref:`collections_galaxy_meta`" -#: ../../rst/user_guide/collections_using.rst:379 +#: ../../rst/user_guide/collections_using.rst:384 msgid "Understand the collections metadata structure." msgstr "コレクションã®ãƒ¡ã‚¿ãƒ‡ãƒ¼ã‚¿æ§‹é€ ã‚’ç†è§£ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/collections_using.rst:380 +#: ../../rst/user_guide/collections_using.rst:385 msgid "`Mailing List <https://groups.google.com/group/ansible-devel>`_" msgstr "`メーリングリスト <https://groups.google.com/group/ansible-devel>`_" -#: ../../rst/user_guide/collections_using.rst:381 +#: ../../rst/user_guide/collections_using.rst:386 msgid "The development mailing list" msgstr "開発メーリングリスト" @@ -1572,8 +1579,8 @@ msgid "Using an example from @zoradache on reddit, to show the 'uptime in days/h msgstr "reddit ã® @zoradache æ°ã®ä¾‹ã‚’å‚考ã«ã€ã€Œæ—¥/時間/分å˜ä½ã§ã®ç¨¼åƒæ™‚é–“ã€ã‚’表示ã—ã¦ã„ã¾ã™ (ファクトãŒåŽé›†ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’å‰æã¨ã—ã¦ã„ã¾ã™) (https://www.reddit.com/r/ansible/comments/gj5a93/trying_to_get_uptime_from_seconds/fqj2qr3/)。" #: ../../rst/user_guide/complex_data_manipulation.rst:309 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:727 -#: ../../rst/user_guide/playbooks_variables.rst:453 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:849 +#: ../../rst/user_guide/playbooks_variables.rst:499 msgid ":ref:`playbooks_filters`" msgstr ":ref:`playbooks_filters`" @@ -1921,59 +1928,59 @@ msgstr "ã“ã“ã§èª¬æ˜Žã—㟠lamp_haproxy ã®ä¾‹ã§ã™ã€‚" #: ../../rst/user_guide/intro_adhoc.rst:207 #: ../../rst/user_guide/intro_bsd.rst:99 #: ../../rst/user_guide/intro_getting_started.rst:189 -#: ../../rst/user_guide/intro_inventory.rst:786 -#: ../../rst/user_guide/intro_patterns.rst:196 -#: ../../rst/user_guide/modules_intro.rst:43 +#: ../../rst/user_guide/intro_inventory.rst:788 +#: ../../rst/user_guide/intro_patterns.rst:222 +#: ../../rst/user_guide/modules_intro.rst:53 #: ../../rst/user_guide/modules_support.rst:65 #: ../../rst/user_guide/playbooks_best_practices.rst:156 -#: ../../rst/user_guide/playbooks_conditionals.rst:497 -#: ../../rst/user_guide/playbooks_lookups.rst:26 +#: ../../rst/user_guide/playbooks_conditionals.rst:525 +#: ../../rst/user_guide/playbooks_lookups.rst:28 #: ../../rst/user_guide/playbooks_reuse.rst:206 #: ../../rst/user_guide/playbooks_reuse_includes.rst:15 #: ../../rst/user_guide/playbooks_reuse_roles.rst:604 #: ../../rst/user_guide/playbooks_roles.rst:15 -#: ../../rst/user_guide/sample_setup.rst:274 +#: ../../rst/user_guide/sample_setup.rst:310 msgid ":ref:`working_with_playbooks`" msgstr ":ref:`working_with_playbooks`" #: ../../rst/user_guide/guide_rolling_upgrade.rst:318 -#: ../../rst/user_guide/playbooks_async.rst:171 +#: ../../rst/user_guide/playbooks_async.rst:185 #: ../../rst/user_guide/playbooks_blocks.rst:183 -#: ../../rst/user_guide/playbooks_conditionals.rst:498 -#: ../../rst/user_guide/playbooks_debugger.rst:325 -#: ../../rst/user_guide/playbooks_delegation.rst:150 -#: ../../rst/user_guide/playbooks_environment.rst:137 -#: ../../rst/user_guide/playbooks_error_handling.rst:235 +#: ../../rst/user_guide/playbooks_conditionals.rst:526 +#: ../../rst/user_guide/playbooks_debugger.rst:338 +#: ../../rst/user_guide/playbooks_delegation.rst:166 +#: ../../rst/user_guide/playbooks_environment.rst:149 +#: ../../rst/user_guide/playbooks_error_handling.rst:263 #: ../../rst/user_guide/playbooks_filters.rst:1838 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:726 -#: ../../rst/user_guide/playbooks_lookups.rst:27 -#: ../../rst/user_guide/playbooks_loops.rst:435 -#: ../../rst/user_guide/playbooks_prompts.rst:108 -#: ../../rst/user_guide/playbooks_startnstep.rst:38 -#: ../../rst/user_guide/playbooks_strategies.rst:217 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:848 +#: ../../rst/user_guide/playbooks_lookups.rst:29 +#: ../../rst/user_guide/playbooks_loops.rst:477 +#: ../../rst/user_guide/playbooks_prompts.rst:116 +#: ../../rst/user_guide/playbooks_startnstep.rst:44 +#: ../../rst/user_guide/playbooks_strategies.rst:243 #: ../../rst/user_guide/playbooks_tags.rst:426 #: ../../rst/user_guide/playbooks_templating.rst:47 -#: ../../rst/user_guide/playbooks_tests.rst:389 -#: ../../rst/user_guide/playbooks_variables.rst:450 -#: ../../rst/user_guide/windows_dsc.rst:497 -#: ../../rst/user_guide/windows_faq.rst:245 -#: ../../rst/user_guide/windows_setup.rst:575 -#: ../../rst/user_guide/windows_usage.rst:505 -#: ../../rst/user_guide/windows_winrm.rst:906 +#: ../../rst/user_guide/playbooks_tests.rst:425 +#: ../../rst/user_guide/playbooks_variables.rst:496 +#: ../../rst/user_guide/windows_dsc.rst:499 +#: ../../rst/user_guide/windows_faq.rst:249 +#: ../../rst/user_guide/windows_setup.rst:598 +#: ../../rst/user_guide/windows_usage.rst:509 +#: ../../rst/user_guide/windows_winrm.rst:928 msgid "An introduction to playbooks" msgstr "Playbook ã®æ¦‚è¦" #: ../../rst/user_guide/guide_rolling_upgrade.rst:319 #: ../../rst/user_guide/playbooks_blocks.rst:184 -#: ../../rst/user_guide/playbooks_conditionals.rst:499 +#: ../../rst/user_guide/playbooks_conditionals.rst:527 #: ../../rst/user_guide/playbooks_filters.rst:1845 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:735 -#: ../../rst/user_guide/playbooks_loops.rst:436 -#: ../../rst/user_guide/playbooks_strategies.rst:220 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:857 +#: ../../rst/user_guide/playbooks_loops.rst:478 +#: ../../rst/user_guide/playbooks_strategies.rst:246 #: ../../rst/user_guide/playbooks_tags.rst:427 #: ../../rst/user_guide/playbooks_templating.rst:52 -#: ../../rst/user_guide/playbooks_tests.rst:396 -#: ../../rst/user_guide/playbooks_variables.rst:457 +#: ../../rst/user_guide/playbooks_tests.rst:432 +#: ../../rst/user_guide/playbooks_variables.rst:503 msgid ":ref:`playbooks_reuse_roles`" msgstr ":ref:`playbooks_reuse_roles`" @@ -1982,18 +1989,18 @@ msgid "An introduction to playbook roles" msgstr "Playbook ã®ãƒãƒ¼ãƒ«ã®æ¦‚è¦" #: ../../rst/user_guide/guide_rolling_upgrade.rst:321 -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:105 -#: ../../rst/user_guide/playbooks_conditionals.rst:503 -#: ../../rst/user_guide/playbooks_error_handling.rst:240 +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:117 +#: ../../rst/user_guide/playbooks_conditionals.rst:531 +#: ../../rst/user_guide/playbooks_error_handling.rst:268 #: ../../rst/user_guide/playbooks_filters.rst:1841 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:731 -#: ../../rst/user_guide/playbooks_lookups.rst:30 -#: ../../rst/user_guide/playbooks_loops.rst:442 -#: ../../rst/user_guide/playbooks_prompts.rst:111 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:853 +#: ../../rst/user_guide/playbooks_lookups.rst:32 +#: ../../rst/user_guide/playbooks_loops.rst:484 +#: ../../rst/user_guide/playbooks_prompts.rst:119 #: ../../rst/user_guide/playbooks_reuse.rst:208 #: ../../rst/user_guide/playbooks_reuse_includes.rst:19 #: ../../rst/user_guide/playbooks_reuse_roles.rst:608 -#: ../../rst/user_guide/playbooks_tests.rst:392 +#: ../../rst/user_guide/playbooks_tests.rst:428 msgid ":ref:`playbooks_variables`" msgstr ":ref:`playbooks_variables`" @@ -2382,7 +2389,7 @@ msgid "You can also filter this output to display only certain facts, see the :r msgstr "ã“ã®å‡ºåŠ›ã‚’フィルターã§çµžã‚Šè¾¼ã‚“ã§ã€ç‰¹å®šã®ãƒ•ã‚¡ã‚¯ãƒˆã®ã¿ã‚’表示ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚詳細㯠:ref:`ansible.builtin.setup <setup_module>` モジュールã®ãƒ‰ã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" #: ../../rst/user_guide/intro_adhoc.rst:194 -#: ../../rst/user_guide/intro_patterns.rst:146 +#: ../../rst/user_guide/intro_patterns.rst:168 msgid "Patterns and ad-hoc commands" msgstr "パターンãŠã‚ˆã³ã‚¢ãƒ‰ãƒ›ãƒƒã‚¯ã‚³ãƒžãƒ³ãƒ‰" @@ -2404,19 +2411,19 @@ msgstr "Ansible è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã®è©³ç´°" #: ../../rst/user_guide/intro_adhoc.rst:205 #: ../../rst/user_guide/playbooks_best_practices.rst:158 -#: ../../rst/user_guide/playbooks_intro.rst:146 +#: ../../rst/user_guide/playbooks_intro.rst:150 #: ../../rst/user_guide/playbooks_reuse_includes.rst:25 #: ../../rst/user_guide/playbooks_reuse_roles.rst:616 -#: ../../rst/user_guide/sample_setup.rst:276 +#: ../../rst/user_guide/sample_setup.rst:312 msgid ":ref:`list_of_collections`" msgstr ":ref:`list_of_collections`" #: ../../rst/user_guide/intro_adhoc.rst:206 #: ../../rst/user_guide/playbooks_best_practices.rst:159 -#: ../../rst/user_guide/playbooks_intro.rst:147 +#: ../../rst/user_guide/playbooks_intro.rst:151 #: ../../rst/user_guide/playbooks_reuse_includes.rst:26 #: ../../rst/user_guide/playbooks_reuse_roles.rst:617 -#: ../../rst/user_guide/sample_setup.rst:277 +#: ../../rst/user_guide/sample_setup.rst:313 msgid "Browse existing collections, modules, and plugins" msgstr "æ—¢å˜ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã€ãŠã‚ˆã³ãƒ—ラグインã®é–²è¦§" @@ -2426,19 +2433,19 @@ msgstr "è¨å®šç®¡ç†ãŠã‚ˆã³ãƒ‡ãƒ—ãƒã‚¤ãƒ¡ãƒ³ãƒˆã« Ansible ã®ä½¿ç”¨" #: ../../rst/user_guide/intro_adhoc.rst:209 #: ../../rst/user_guide/intro_bsd.rst:103 -#: ../../rst/user_guide/intro_dynamic_inventory.rst:246 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:250 #: ../../rst/user_guide/intro_getting_started.rst:195 -#: ../../rst/user_guide/intro_inventory.rst:788 -#: ../../rst/user_guide/intro_patterns.rst:198 +#: ../../rst/user_guide/intro_inventory.rst:790 +#: ../../rst/user_guide/intro_patterns.rst:224 #: ../../rst/user_guide/modules.rst:33 -#: ../../rst/user_guide/modules_intro.rst:49 +#: ../../rst/user_guide/modules_intro.rst:59 #: ../../rst/user_guide/modules_support.rst:67 #: ../../rst/user_guide/playbooks_best_practices.rst:166 -#: ../../rst/user_guide/playbooks_intro.rst:154 +#: ../../rst/user_guide/playbooks_intro.rst:158 #: ../../rst/user_guide/playbooks_reuse.rst:220 #: ../../rst/user_guide/playbooks_reuse_includes.rst:31 #: ../../rst/user_guide/playbooks_reuse_roles.rst:622 -#: ../../rst/user_guide/sample_setup.rst:284 +#: ../../rst/user_guide/sample_setup.rst:320 msgid "`Mailing List <https://groups.google.com/group/ansible-project>`_" msgstr "`Mailing List <https://groups.google.com/group/ansible-project>`_" @@ -2528,18 +2535,18 @@ msgstr "BSD サãƒãƒ¼ãƒˆã¯ Ansible ã«ã¨ã£ã¦é‡è¦ã§ã™ã€‚貢献者ã®å¤§å #: ../../rst/user_guide/intro_bsd.rst:97 #: ../../rst/user_guide/intro_getting_started.rst:187 -#: ../../rst/user_guide/intro_inventory.rst:784 -#: ../../rst/user_guide/intro_patterns.rst:194 +#: ../../rst/user_guide/intro_inventory.rst:786 +#: ../../rst/user_guide/intro_patterns.rst:220 #: ../../rst/user_guide/modules.rst:23 -#: ../../rst/user_guide/modules_intro.rst:41 +#: ../../rst/user_guide/modules_intro.rst:51 #: ../../rst/user_guide/modules_support.rst:63 msgid ":ref:`intro_adhoc`" msgstr ":ref:`intro_adhoc`" #: ../../rst/user_guide/intro_bsd.rst:98 #: ../../rst/user_guide/intro_getting_started.rst:188 -#: ../../rst/user_guide/intro_inventory.rst:785 -#: ../../rst/user_guide/intro_patterns.rst:195 +#: ../../rst/user_guide/intro_inventory.rst:787 +#: ../../rst/user_guide/intro_patterns.rst:221 msgid "Examples of basic commands" msgstr "基本コマンドã®ä¾‹" @@ -2548,12 +2555,12 @@ msgid "Learning ansible's configuration management language" msgstr "Ansible ã®è¨å®šç®¡ç†è¨€èªžã®æ¦‚è¦" #: ../../rst/user_guide/intro_bsd.rst:101 -#: ../../rst/user_guide/modules_intro.rst:45 +#: ../../rst/user_guide/modules_intro.rst:55 #: ../../rst/user_guide/playbooks_best_practices.rst:160 -#: ../../rst/user_guide/playbooks_intro.rst:148 +#: ../../rst/user_guide/playbooks_intro.rst:152 #: ../../rst/user_guide/playbooks_reuse_includes.rst:27 #: ../../rst/user_guide/playbooks_reuse_roles.rst:618 -#: ../../rst/user_guide/sample_setup.rst:278 +#: ../../rst/user_guide/sample_setup.rst:314 msgid ":ref:`developing_modules`" msgstr ":ref:`developing_modules`" @@ -2666,108 +2673,105 @@ msgid "Explicit use of OpenStack inventory script" msgstr "OpenStack インベントリースクリプトã®æ˜Žç¤ºçš„ãªä½¿ç”¨" #: ../../rst/user_guide/intro_dynamic_inventory.rst:123 -msgid "Download the latest version of the OpenStack dynamic inventory script and make it executable::" +msgid "Download the latest version of the OpenStack dynamic inventory script and make it executable." msgstr "最新ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® OpenStack ã®å‹•çš„インベントリースクリプトをダウンãƒãƒ¼ãƒ‰ã—ã€å®Ÿè¡Œå¯èƒ½ã«ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:129 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:131 msgid "Do not name it `openstack.py`. This name will conflict with imports from openstacksdk." msgstr "`openstack.py` ã¨ã„ã†åå‰ã¯ã¤ã‘ãªã„ã§ãã ã•ã„。ã“ã®åå‰ã¯ã€openstacksdk ã‹ã‚‰ã®ã‚¤ãƒ³ãƒãƒ¼ãƒˆã¨ç«¶åˆã—ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:131 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:133 msgid "Source an OpenStack RC file:" msgstr "OpenStack RC ファイルをèªã¿è¾¼ã¿ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:139 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:141 msgid "An OpenStack RC file contains the environment variables required by the client tools to establish a connection with the cloud provider, such as the authentication URL, user name, password and region name. For more information on how to download, create or source an OpenStack RC file, please refer to `Set environment variables using the OpenStack RC file <https://docs.openstack.org/user-guide/common/cli_set_environment_variables_using_openstack_rc.html>`_." msgstr "OpenStack RC ファイルã«ã¯ã€èªè¨¼ URLã€ãƒ¦ãƒ¼ã‚¶ãƒ¼åã€ãƒ‘スワードã€ãƒªãƒ¼ã‚¸ãƒ§ãƒ³åãªã©ã€ã‚¯ãƒ©ã‚¦ãƒ‰ãƒ—ãƒãƒã‚¤ãƒ€ãƒ¼ã¨ã®æŽ¥ç¶šã‚’確立ã™ã‚‹ãŸã‚ã«ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆãƒ„ールã§å¿…è¦ãªç’°å¢ƒå¤‰æ•°ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚OpenStack RC ファイルã®ãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰ã€ä½œæˆã€ã¾ãŸã¯ã‚½ãƒ¼ã‚¹ã«é–¢ã™ã‚‹è©³ç´°ã¯ã€ã€Œ`Set environment variables using the OpenStack RC file <https://docs.openstack.org/user-guide/common/cli_set_environment_variables_using_openstack_rc.html>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:141 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:143 msgid "You can confirm the file has been successfully sourced by running a simple command, such as `nova list` and ensuring it returns no errors." msgstr "`nova list` ãªã©ã®å˜ç´”ãªã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¦ã‚¨ãƒ©ãƒ¼ã‚’è¿”ã•ãªã„よã†ã«ã™ã‚‹ã“ã¨ã§ã€ãƒ•ã‚¡ã‚¤ãƒ«ãŒæ£å¸¸ã«èªã¿è¾¼ã¾ã‚ŒãŸã“ã¨ã‚’確èªã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:145 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:147 msgid "The OpenStack command line clients are required to run the `nova list` command. For more information on how to install them, please refer to `Install the OpenStack command-line clients <https://docs.openstack.org/user-guide/common/cli_install_openstack_command_line_clients.html>`_." msgstr "`nova list` コマンドを実行ã™ã‚‹ã«ã¯ã€OpenStack コマンドラインクライアントãŒå¿…è¦ã§ã™ã€‚インストール方法ã®è©³ç´°ã¯ã€ã€Œ`Install the OpenStack command-line clients <https://docs.openstack.org/user-guide/common/cli_install_openstack_command_line_clients.html>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:147 -msgid "You can test the OpenStack dynamic inventory script manually to confirm it is working as expected::" -msgstr "OpenStack ã®å‹•çš„インベントリースクリプトを手動ã§ãƒ†ã‚¹ãƒˆã—ã¦ã€æƒ³å®šã©ãŠã‚Šã«æ©Ÿèƒ½ã—ã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚" +#: ../../rst/user_guide/intro_dynamic_inventory.rst:149 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:182 +msgid "You can test the OpenStack dynamic inventory script manually to confirm it is working as expected:" +msgstr "OpenStack 動的インベントリースクリプトを手動ã§ãƒ†ã‚¹ãƒˆã—ã¦ã€æƒ³å®šã©ãŠã‚Šã«æ©Ÿèƒ½ã—ã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:151 -#: ../../rst/user_guide/intro_dynamic_inventory.rst:184 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:155 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:188 msgid "After a few moments you should see some JSON output with information about your compute instances." msgstr "ã—ã°ã‚‰ãã™ã‚‹ã¨ã€Compute インスタンスã«é–¢ã™ã‚‹æƒ…å ±ãŒå«ã¾ã‚Œã‚‹ JSON 出力ãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:153 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:157 msgid "Once you confirm the dynamic inventory script is working as expected, you can tell Ansible to use the `openstack_inventory.py` script as an inventory file, as illustrated below:" msgstr "動的インベントリースクリプトãŒæƒ³å®šã©ãŠã‚Šã«æ©Ÿèƒ½ã—ã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ãŸã‚‰ã€ä»¥ä¸‹ã®ã‚ˆã†ã« Ansible ㌠`openstack_inventory.py` スクリプトをインベントリーファイルã¨ã—ã¦ä½¿ç”¨ã™ã‚‹ã‚ˆã†ã«æŒ‡å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:160 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:164 msgid "Implicit use of OpenStack inventory script" msgstr "OpenStack インベントリースクリプトã®æš—黙的ãªä½¿ç”¨" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:162 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:166 msgid "Download the latest version of the OpenStack dynamic inventory script, make it executable and copy it to `/etc/ansible/hosts`:" msgstr "最新ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® OpenStack 動的インベントリースクリプトをダウンãƒãƒ¼ãƒ‰ã—ã€å®Ÿè¡Œå¯èƒ½ã«ã—ã€ã“れを `/etc/ansible/hosts` ã«ã‚³ãƒ”ーã—ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:170 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:174 msgid "Download the sample configuration file, modify it to suit your needs and copy it to `/etc/ansible/openstack.yml`:" msgstr "サンプルè¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã‚’ダウンãƒãƒ¼ãƒ‰ã—ã€å¿…è¦ã«å¿œã˜ã¦å¤‰æ›´ã—ã€ã“れを `/etc/ansible/openstack.yml` ã«ã‚³ãƒ”ーã—ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:178 -msgid "You can test the OpenStack dynamic inventory script manually to confirm it is working as expected:" -msgstr "OpenStack 動的インベントリースクリプトを手動ã§ãƒ†ã‚¹ãƒˆã—ã¦ã€æƒ³å®šã©ãŠã‚Šã«æ©Ÿèƒ½ã—ã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚" - -#: ../../rst/user_guide/intro_dynamic_inventory.rst:187 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:191 msgid "Refreshing the cache" msgstr "ã‚ャッシュã®æ›´æ–°" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:189 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:193 msgid "Note that the OpenStack dynamic inventory script will cache results to avoid repeated API calls. To explicitly clear the cache, you can run the openstack_inventory.py (or hosts) script with the ``--refresh`` parameter:" msgstr "OpenStack 動的インベントリースクリプトã¯ã€API 呼ã³å‡ºã—ãŒç¹°ã‚Šè¿”ã—è¡Œã‚れるã®ã‚’防ããŸã‚ã«ã€çµæžœã‚’ã‚ャッシュã™ã‚‹ã“ã¨ã«æ³¨æ„ã—ã¦ãã ã•ã„。ã‚ャッシュを明示的ã«æ¶ˆåŽ»ã™ã‚‹ã«ã¯ã€``--refresh`` パラメーターを使用ã—㦠openstack_inventory.py (ã¾ãŸã¯ hosts) スクリプトを実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:198 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:202 msgid "Other inventory scripts" msgstr "ãã®ä»–ã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚¹ã‚¯ãƒªãƒ—ト" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:200 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:204 msgid "In Ansible 2.10 and later, inventory scripts moved to their associated collections. Many are now in the `community.general scripts/inventory directory <https://github.com/ansible-collections/community.general/tree/main/scripts/inventory>`_. We recommend you use :ref:`inventory_plugins` instead." msgstr "Ansible 2.10 以é™ã§ã¯ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚¹ã‚¯ãƒªãƒ—トã¯é–¢é€£ã™ã‚‹ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«ç§»å‹•ã—ã¾ã—ãŸã€‚ç¾åœ¨ã€å¤šãã®ã‚¹ã‚¯ãƒªãƒ—ト㯠`community.general scripts/inventory directory <https://github.com/ansible-collections/community.general/tree/main/scripts/inventory>`_ ã«ã‚ã‚Šã¾ã™ã€‚代ã‚ã‚Šã« :ref:`inventory_plugins` を使用ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:205 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:209 msgid "Using inventory directories and multiple inventory sources" msgstr "インベントリーディレクトリーãŠã‚ˆã³è¤‡æ•°ã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚½ãƒ¼ã‚¹ã®ä½¿ç”¨" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:207 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:211 msgid "If the location given to ``-i`` in Ansible is a directory (or as so configured in ``ansible.cfg``), Ansible can use multiple inventory sources at the same time. When doing so, it is possible to mix both dynamic and statically managed inventory sources in the same ansible run. Instant hybrid cloud!" msgstr "Ansible 㧠``-i`` ã«æŒ‡å®šã•ã‚Œã‚‹å ´æ‰€ãŒãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã®å ´åˆ (ã¾ãŸã¯ ``ansible.cfg`` ã§ãã®ã‚ˆã†ã«è¨å®šã•ã‚Œã¦ã„ã‚‹å ´åˆ)ã€Ansible ã¯è¤‡æ•°ã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚½ãƒ¼ã‚¹ã‚’åŒæ™‚ã«ä½¿ç”¨ã§ãã¾ã™ã€‚ã“れを実行ã™ã‚‹å ´åˆã¯ã€åŒã˜ Ansible 実行ã§å‹•çš„ãŠã‚ˆã³é™çš„ã«ç®¡ç†ã•ã‚Œã¦ã„るインベントリーソースを混在ã•ã›ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:211 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:215 msgid "In an inventory directory, executable files are treated as dynamic inventory sources and most other files as static sources. Files which end with any of the following are ignored:" msgstr "インベントリーディレクトリã§ã¯ã€å®Ÿè¡Œãƒ•ã‚¡ã‚¤ãƒ«ã¯å‹•çš„インベントリーソースã¨ã—ã¦ã€ãã®ä»–ã®ã»ã¨ã‚“ã©ã®ãƒ•ã‚¡ã‚¤ãƒ«ã¯é™çš„ソースã¨ã—ã¦æ‰±ã‚ã‚Œã¾ã™ã€‚以下ã®ã„ãšã‚Œã‹ã§çµ‚ã‚るファイルã¯ç„¡è¦–ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:217 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:221 msgid "You can replace this list with your own selection by configuring an ``inventory_ignore_extensions`` list in ``ansible.cfg``, or setting the :envvar:`ANSIBLE_INVENTORY_IGNORE` environment variable. The value in either case must be a comma-separated list of patterns, as shown above." msgstr "ã“ã®ä¸€è¦§ã¯ã€``ansible.cfg`` 㧠``inventory_ignore_extensions`` 一覧をè¨å®šã™ã‚‹ã‹ã€:envvar:`ANSIBLE_INVENTORY_IGNORE` 環境変数をè¨å®šã—ã¦ç‹¬è‡ªã®é¸æŠžã«ç½®ãæ›ãˆã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã„ãšã‚Œã®å€¤ã‚‚ã€ä¸Šè¨˜ã®ã‚ˆã†ã«ãƒ‘ターンã®ã‚³ãƒ³ãƒžåŒºåˆ‡ã‚Šã®ä¸€è¦§ã§ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:219 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:223 msgid "Any ``group_vars`` and ``host_vars`` subdirectories in an inventory directory are interpreted as expected, making inventory directories a powerful way to organize different sets of configurations. See :ref:`using_multiple_inventory_sources` for more information." msgstr "インベントリーディレクトリー㮠``group_vars`` サブディレクトリーãŠã‚ˆã³ ``host_vars`` サブディレクトリーã¯æƒ³å®šã©ãŠã‚Šã«è§£é‡ˆã•ã‚Œã‚‹ãŸã‚ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã¯ã•ã¾ã–ã¾ãªæ§‹æˆã‚»ãƒƒãƒˆã‚’æ•´ç†ã™ã‚‹ãŸã‚ã®å¼·åŠ›ãªæ–¹æ³•ã«ãªã‚Šã¾ã™ã€‚詳細ã¯ã€ã€Œ:ref:`using_multiple_inventory_sources`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:224 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:228 msgid "Static groups of dynamic groups" msgstr "動的グループã®é™çš„グループ" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:226 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:230 msgid "When defining groups of groups in the static inventory file, the child groups must also be defined in the static inventory file, otherwise ansible returns an error. If you want to define a static group of dynamic child groups, define the dynamic groups as empty in the static inventory file. For example:" msgstr "é™çš„インベントリーファイルã§ã‚°ãƒ«ãƒ¼ãƒ—ã®ã‚°ãƒ«ãƒ¼ãƒ—を定義ã™ã‚‹å ´åˆã¯ã€åグループもé™çš„インベントリーファイルã§å®šç¾©ã•ã‚Œã¦ã„ãªã‘ã‚Œã°ã€Ansible ã¯ã‚¨ãƒ©ãƒ¼ã‚’è¿”ã—ã¾ã™ã€‚å‹•çš„ãªåグループã®é™çš„グループを定義ã™ã‚‹å ´åˆã¯ã€é™çš„インベントリーファイルã§å‹•çš„グループを空ã«å®šç¾©ã—ã¦ãã ã•ã„。以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:244 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:248 #: ../../rst/user_guide/intro_getting_started.rst:185 msgid ":ref:`intro_inventory`" msgstr ":ref:`intro_inventory`" -#: ../../rst/user_guide/intro_dynamic_inventory.rst:245 +#: ../../rst/user_guide/intro_dynamic_inventory.rst:249 msgid "All about static inventory files" msgstr "é™çš„インベントリーファイルã®è©³ç´°" @@ -2903,8 +2907,8 @@ msgid "Ansible does not store playbooks for you; they are simply YAML documents msgstr "Ansible ã¯ã€Playbook ã‚’ä¿å˜ã—ã¾ã›ã‚“。Playbook ã¯ã€ä¿å˜ãŠã‚ˆã³ç®¡ç†ã™ã‚‹å˜ç´”㪠YAML ドã‚ュメントã§ã‚ã‚Šã€å¿…è¦ã«å¿œã˜ã¦å®Ÿè¡Œã™ã‚‹ãŸã‚ã« Ansible ã«æ¸¡ã—ã¾ã™ã€‚" #: ../../rst/user_guide/intro_getting_started.rst:106 -msgid "In a directory of your choice you can create your first playbook in a file called mytask.yml:" -msgstr "ä»»æ„ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã§ã¯ã€mytask.yml ã¨ã„ã†åå‰ã®ãƒ•ã‚¡ã‚¤ãƒ«ã«æœ€åˆã® Playbook を作æˆã§ãã¾ã™ã€‚" +msgid "In a directory of your choice you can create your first playbook in a file called mytask.yaml:" +msgstr "ä»»æ„ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã§ã¯ã€mytask.yaml ã¨ã„ã†åå‰ã®ãƒ•ã‚¡ã‚¤ãƒ«ã«æœ€åˆã® Playbook を作æˆã§ãã¾ã™ã€‚" #: ../../rst/user_guide/intro_getting_started.rst:117 msgid "You can run this command as follows:" @@ -3589,46 +3593,46 @@ msgid "That file only includes hosts that are part of the \"test\" environment. msgstr "ã“ã®ãƒ•ã‚¡ã‚¤ãƒ«ã«ã¯ã€ã€Œãƒ†ã‚¹ãƒˆã€ç’°å¢ƒã«å«ã¾ã‚Œã‚‹ãƒ›ã‚¹ãƒˆã®ã¿ãŒå«ã¾ã‚Œã¾ã™ã€‚:file:`inventory_staging` ã¨å‘¼ã°ã‚Œã‚‹åˆ¥ã®ãƒ•ã‚¡ã‚¤ãƒ«ã®ã€Œã‚¹ãƒ†ãƒ¼ã‚¸ãƒ³ã‚°ã€ãƒžã‚·ãƒ³ã‚’定義ã—ã¾ã™ã€‚" #: ../../rst/user_guide/intro_inventory.rst:729 -msgid "To apply a playbook called :file:`site.yml` to all the app servers in the test environment, use the following command::" +msgid "To apply a playbook called :file:`site.yml` to all the app servers in the test environment, use the following command:" msgstr "`site.yml` ã¨ã„ã†åå‰ã® Playbook をテスト環境ã®ã™ã¹ã¦ã®ã‚¢ãƒ—リケーションサーãƒãƒ¼ã«é©ç”¨ã™ã‚‹ã«ã¯ã€æ¬¡ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_inventory.rst:738 +#: ../../rst/user_guide/intro_inventory.rst:740 msgid "Example: Group by function" msgstr "例: 機能別ã«ã‚°ãƒ«ãƒ¼ãƒ—化" -#: ../../rst/user_guide/intro_inventory.rst:740 +#: ../../rst/user_guide/intro_inventory.rst:742 msgid "In the previous section you already saw an example for using groups in order to cluster hosts that have the same function. This allows you, for instance, to define firewall rules inside a playbook or role affecting only database servers:" msgstr "å‰ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€åŒã˜æ©Ÿèƒ½ã‚’æŒã¤ãƒ›ã‚¹ãƒˆã‚’クラスター化ã™ã‚‹ãŸã‚ã«ã€ã‚°ãƒ«ãƒ¼ãƒ—を使用ã™ã‚‹ä¾‹ã‚’ã™ã§ã«æ示ã—ã¦ã„ã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã‚µãƒ¼ãƒãƒ¼ã ã‘ã«å½±éŸ¿ã™ã‚‹ Playbook ã¾ãŸã¯ãƒãƒ¼ãƒ«å†…ã§ãƒ•ã‚¡ã‚¤ã‚¢ã‚¦ã‚©ãƒ¼ãƒ«ãƒ«ãƒ¼ãƒ«ã‚’定義ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/intro_inventory.rst:758 +#: ../../rst/user_guide/intro_inventory.rst:760 msgid "Example: Group by location" msgstr "例: å ´æ‰€åˆ¥ã«ã‚°ãƒ«ãƒ¼ãƒ—化" -#: ../../rst/user_guide/intro_inventory.rst:760 +#: ../../rst/user_guide/intro_inventory.rst:762 msgid "Other tasks might be focused on where a certain host is located. Let's say that ``db01.test.example.com`` and ``app01.test.example.com`` are located in DC1 while ``db02.test.example.com`` is in DC2:" msgstr "ã¾ãŸã€ç‰¹å®šã®ãƒ›ã‚¹ãƒˆãŒã©ã“ã«ã‚ã‚‹ã‹ã«ç„¦ç‚¹ã‚’当ã¦ãŸã‚¿ã‚¹ã‚¯ã‚‚ã‚ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€``db01.test.example.com`` 㨠``app01.test.example.com`` ㌠DC1 ã«ã‚ã‚Šã€``db02.test.example.com`` ㌠DC2 ã«ã‚ã‚‹ã¨ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_inventory.rst:773 +#: ../../rst/user_guide/intro_inventory.rst:775 msgid "In practice, you might even end up mixing all these setups as you might need to, on one day, update all nodes in a specific data center while, on another day, update all the application servers no matter their location." msgstr "実際ã«ã¯ã€ãŸã¨ãˆã°ç‰¹å®šã®ãƒ‡ãƒ¼ã‚¿ã‚»ãƒ³ã‚¿ãƒ¼å†…ã®ã™ã¹ã¦ã®ãƒŽãƒ¼ãƒ‰ã‚’æ›´æ–°ã™ã‚‹æ—¥ã¨ã€ç½®ã‹ã‚Œã¦ã„ã‚‹å ´æ‰€ã«é–¢ä¿‚ãªãã™ã¹ã¦ã®ã‚¢ãƒ—リケーションサーãƒãƒ¼ã‚’æ›´æ–°ã™ã‚‹æ—¥ãŒå¿…è¦ã«ãªã‚‹ãŸã‚ã€ã“れらã™ã¹ã¦ã®è¨å®šã‚’組ã¿åˆã‚ã›ã¦ä½¿ç”¨ã™ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/intro_inventory.rst:780 +#: ../../rst/user_guide/intro_inventory.rst:782 msgid ":ref:`inventory_plugins`" msgstr ":ref:`inventory_plugins`" -#: ../../rst/user_guide/intro_inventory.rst:781 +#: ../../rst/user_guide/intro_inventory.rst:783 msgid "Pulling inventory from dynamic or static sources" msgstr "動的ソースã¾ãŸã¯é™çš„ソースã‹ã‚‰ã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã®ãƒ—ル" -#: ../../rst/user_guide/intro_inventory.rst:782 +#: ../../rst/user_guide/intro_inventory.rst:784 msgid ":ref:`intro_dynamic_inventory`" msgstr ":ref:`intro_dynamic_inventory`" -#: ../../rst/user_guide/intro_inventory.rst:783 +#: ../../rst/user_guide/intro_inventory.rst:785 msgid "Pulling inventory from dynamic sources, such as cloud providers" msgstr "クラウドプãƒãƒã‚¤ãƒ€ãƒ¼ãªã©ã®å‹•çš„ソースã‹ã‚‰ã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã®ãƒ—ル" -#: ../../rst/user_guide/intro_inventory.rst:787 +#: ../../rst/user_guide/intro_inventory.rst:789 msgid "Learning Ansible's configuration, deployment, and orchestration language." msgstr "Ansible ã®è¨å®šã€ãƒ‡ãƒ—ãƒã‚¤ãƒ¡ãƒ³ãƒˆã€ãŠã‚ˆã³ã‚ªãƒ¼ã‚±ã‚¹ãƒˆãƒ¬ãƒ¼ã‚·ãƒ§ãƒ³è¨€èªžã«ã¤ã„ã¦" @@ -3645,232 +3649,223 @@ msgid "Using patterns" msgstr "パターンã®ä½¿ç”¨" #: ../../rst/user_guide/intro_patterns.rst:14 -msgid "You use a pattern almost any time you execute an ad hoc command or a playbook. The pattern is the only element of an :ref:`ad hoc command<intro_adhoc>` that has no flag. It is usually the second element::" -msgstr "アドホックコマンドã¾ãŸã¯ Playbook を実行ã™ã‚‹éš›ã¯ã€ã»ã¼å¸¸ã«ãƒ‘ターンを使用ã—ã¾ã™ã€‚パターンã¯ã€ãƒ•ãƒ©ã‚°ã®ãªã„ :ref:`ad hoc command<intro_adhoc>` ã®å”¯ä¸€ã®è¦ç´ ã§ã™ã€‚通常㯠2 番目ã®è¦ç´ ã«ãªã‚Šã¾ã™ã€‚" - -#: ../../rst/user_guide/intro_patterns.rst:18 -#: ../../rst/user_guide/intro_patterns.rst:29 -#: ../../rst/user_guide/playbooks_checkmode.rst:31 -#: ../../rst/user_guide/playbooks_filters.rst:676 -#: ../../rst/user_guide/playbooks_tests.rst:307 -#: ../../rst/user_guide/playbooks_tests.rst:328 -msgid "For example::" -msgstr "例::" +msgid "You use a pattern almost any time you execute an ad hoc command or a playbook. The pattern is the only element of an :ref:`ad hoc command<intro_adhoc>` that has no flag. It is usually the second element:" +msgstr "アドホックコマンドã¾ãŸã¯ Playbook を実行ã™ã‚‹éš›ã¯ã€ã»ã¼å¸¸ã«ãƒ‘ターンを使用ã—ã¾ã™ã€‚パターンã¯ã€ãƒ•ãƒ©ã‚°ã®ãªã„ :ref:`アドホックコマンド<intro_adhoc>` ã®å”¯ä¸€ã®è¦ç´ ã§ã™ã€‚通常㯠2 番目ã®è¦ç´ ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:22 +#: ../../rst/user_guide/intro_patterns.rst:26 msgid "In a playbook the pattern is the content of the ``hosts:`` line for each play:" msgstr "Playbook ã§ã¯ã€ãƒ‘ターンã¯å„プレイ㮠``hosts:`` è¡Œã®å†…容ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:34 +#: ../../rst/user_guide/intro_patterns.rst:40 msgid "Since you often want to run a command or playbook against multiple hosts at once, patterns often refer to inventory groups. Both the ad hoc command and the playbook above will execute against all machines in the ``webservers`` group." msgstr "多ãã®å ´åˆã¯ã€ã‚³ãƒžãƒ³ãƒ‰ã¾ãŸã¯ Playbook を複数ã®ãƒ›ã‚¹ãƒˆã«å¯¾ã—ã¦ä¸€åº¦ã«å®Ÿè¡Œã™ã‚‹ãŸã‚ã€ãƒ‘ターンã¯å¤šãã®å ´åˆã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚°ãƒ«ãƒ¼ãƒ—ã‚’å‚ç…§ã—ã¾ã™ã€‚アドホックコマンドã¨ä¸Šè¨˜ã® Playbook ã¯ã€``webservers`` グループã®ã™ã¹ã¦ã®ãƒžã‚·ãƒ³ã«å¯¾ã—ã¦å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:39 +#: ../../rst/user_guide/intro_patterns.rst:45 msgid "Common patterns" msgstr "一般的ãªãƒ‘ターン" -#: ../../rst/user_guide/intro_patterns.rst:41 +#: ../../rst/user_guide/intro_patterns.rst:47 msgid "This table lists common patterns for targeting inventory hosts and groups." msgstr "以下ã®è¡¨ã¯ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ›ã‚¹ãƒˆãŠã‚ˆã³ã‚°ãƒ«ãƒ¼ãƒ—を対象ã«è¨å®šã™ã‚‹ä¸€èˆ¬çš„ãªãƒ‘ターンを示ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:47 -#: ../../rst/user_guide/playbooks_loops.rst:394 +#: ../../rst/user_guide/intro_patterns.rst:53 +#: ../../rst/user_guide/playbooks_loops.rst:434 msgid "Description" msgstr "説明" -#: ../../rst/user_guide/intro_patterns.rst:47 +#: ../../rst/user_guide/intro_patterns.rst:53 msgid "Pattern(s)" msgstr "パターン" -#: ../../rst/user_guide/intro_patterns.rst:47 +#: ../../rst/user_guide/intro_patterns.rst:53 msgid "Targets" msgstr "ターゲット" -#: ../../rst/user_guide/intro_patterns.rst:49 +#: ../../rst/user_guide/intro_patterns.rst:55 msgid "All hosts" msgstr "ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆ" -#: ../../rst/user_guide/intro_patterns.rst:49 +#: ../../rst/user_guide/intro_patterns.rst:55 msgid "all (or \\*)" msgstr "all (ã¾ãŸã¯ \\*)" -#: ../../rst/user_guide/intro_patterns.rst:51 +#: ../../rst/user_guide/intro_patterns.rst:57 msgid "One host" msgstr "1 å°ã®ãƒ›ã‚¹ãƒˆ" -#: ../../rst/user_guide/intro_patterns.rst:51 +#: ../../rst/user_guide/intro_patterns.rst:57 msgid "host1" msgstr "host1" -#: ../../rst/user_guide/intro_patterns.rst:53 +#: ../../rst/user_guide/intro_patterns.rst:59 msgid "Multiple hosts" msgstr "複数ã®ãƒ›ã‚¹ãƒˆ" -#: ../../rst/user_guide/intro_patterns.rst:53 +#: ../../rst/user_guide/intro_patterns.rst:59 msgid "host1:host2 (or host1,host2)" msgstr "host1:host2 (ã¾ãŸã¯ host1,host2)" -#: ../../rst/user_guide/intro_patterns.rst:55 +#: ../../rst/user_guide/intro_patterns.rst:61 msgid "One group" msgstr "1 ã¤ã®ã‚°ãƒ«ãƒ¼ãƒ—" -#: ../../rst/user_guide/intro_patterns.rst:55 +#: ../../rst/user_guide/intro_patterns.rst:61 msgid "webservers" msgstr "webservers" -#: ../../rst/user_guide/intro_patterns.rst:57 +#: ../../rst/user_guide/intro_patterns.rst:63 msgid "Multiple groups" msgstr "複数グループ" -#: ../../rst/user_guide/intro_patterns.rst:57 +#: ../../rst/user_guide/intro_patterns.rst:63 msgid "webservers:dbservers" msgstr "webservers:dbservers" -#: ../../rst/user_guide/intro_patterns.rst:57 +#: ../../rst/user_guide/intro_patterns.rst:63 msgid "all hosts in webservers plus all hosts in dbservers" msgstr "webservers 上ã®ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã¨ã€dbservers 上ã®ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆ" -#: ../../rst/user_guide/intro_patterns.rst:59 +#: ../../rst/user_guide/intro_patterns.rst:65 msgid "Excluding groups" msgstr "グループã®é™¤å¤–" -#: ../../rst/user_guide/intro_patterns.rst:59 +#: ../../rst/user_guide/intro_patterns.rst:65 msgid "webservers:!atlanta" msgstr "webservers:!atlanta" -#: ../../rst/user_guide/intro_patterns.rst:59 +#: ../../rst/user_guide/intro_patterns.rst:65 msgid "all hosts in webservers except those in atlanta" msgstr "atlanta 上ã®ãƒ›ã‚¹ãƒˆã‚’除ã webservers ã®ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆ" -#: ../../rst/user_guide/intro_patterns.rst:61 +#: ../../rst/user_guide/intro_patterns.rst:67 msgid "Intersection of groups" msgstr "グループã®äº¤å·®éƒ¨åˆ†" -#: ../../rst/user_guide/intro_patterns.rst:61 +#: ../../rst/user_guide/intro_patterns.rst:67 msgid "webservers:&staging" msgstr "webservers:&staging" -#: ../../rst/user_guide/intro_patterns.rst:61 +#: ../../rst/user_guide/intro_patterns.rst:67 msgid "any hosts in webservers that are also in staging" msgstr "ステージ状態ã«ã‚ã‚‹ webservers ã®ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆ" -#: ../../rst/user_guide/intro_patterns.rst:64 +#: ../../rst/user_guide/intro_patterns.rst:70 msgid "You can use either a comma (``,``) or a colon (``:``) to separate a list of hosts. The comma is preferred when dealing with ranges and IPv6 addresses." msgstr "ホストã®ãƒªã‚¹ãƒˆã‚’分離ã™ã‚‹ã«ã¯ã€ã‚³ãƒ³ãƒž (``,``) ã¾ãŸã¯ã‚³ãƒãƒ³ (``:``) ã®ã„ãšã‚Œã‹ã‚’使用ã§ãã¾ã™ã€‚コンマã¯ã€ç¯„囲ãŠã‚ˆã³ IPv6 アドレスを処ç†ã™ã‚‹å ´åˆã«æŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:66 -msgid "Once you know the basic patterns, you can combine them. This example::" +#: ../../rst/user_guide/intro_patterns.rst:72 +msgid "Once you know the basic patterns, you can combine them. This example:" msgstr "基本的ãªãƒ‘ターンを把æ¡ã—ãŸã‚‰ã€ãれを組ã¿åˆã‚ã›ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:70 +#: ../../rst/user_guide/intro_patterns.rst:78 msgid "targets all machines in the groups 'webservers' and 'dbservers' that are also in the group 'staging', except any machines in the group 'phoenix'." msgstr "「phoenixã€ã‚°ãƒ«ãƒ¼ãƒ—ã®ãƒžã‚·ãƒ³ã‚’除ãã€ã€Œstagingã€ã‚°ãƒ«ãƒ¼ãƒ—ã«ã‚る「webserversã€ã‚°ãƒ«ãƒ¼ãƒ—ãŠã‚ˆã³ã€Œdbserversã€ã‚°ãƒ«ãƒ¼ãƒ—ã«ã‚ã‚‹ã™ã¹ã¦ã®ãƒžã‚·ãƒ³ã‚’対象ã¨ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:73 -msgid "You can use wildcard patterns with FQDNs or IP addresses, as long as the hosts are named in your inventory by FQDN or IP address::" +#: ../../rst/user_guide/intro_patterns.rst:81 +msgid "You can use wildcard patterns with FQDNs or IP addresses, as long as the hosts are named in your inventory by FQDN or IP address:" msgstr "ホストãŒã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã§ FQDN ã¾ãŸã¯ IP アドレスã«ã‚ˆã‚Šåå‰ãŒä»˜ã‘られã¦ã„ã‚‹é™ã‚Šã€FQDN ã¾ãŸã¯ IP アドレスã§ãƒ¯ã‚¤ãƒ«ãƒ‰ã‚«ãƒ¼ãƒ‰ãƒ‘ターンを使用ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:79 -msgid "You can mix wildcard patterns and groups at the same time::" +#: ../../rst/user_guide/intro_patterns.rst:89 +msgid "You can mix wildcard patterns and groups at the same time:" msgstr "ワイルドカードパターンãŠã‚ˆã³ã‚°ãƒ«ãƒ¼ãƒ—ã‚’åŒæ™‚ã«çµ„ã¿åˆã‚ã›ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:84 +#: ../../rst/user_guide/intro_patterns.rst:96 msgid "Limitations of patterns" msgstr "パターンã®åˆ¶é™" -#: ../../rst/user_guide/intro_patterns.rst:86 +#: ../../rst/user_guide/intro_patterns.rst:98 msgid "Patterns depend on inventory. If a host or group is not listed in your inventory, you cannot use a pattern to target it. If your pattern includes an IP address or hostname that does not appear in your inventory, you will see an error like this:" msgstr "パターンã¯ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã«ã‚ˆã£ã¦ç•°ãªã‚Šã¾ã™ã€‚ホストã¾ãŸã¯ã‚°ãƒ«ãƒ¼ãƒ—ãŒã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã«è¨˜è¼‰ã•ã‚Œã¦ã„ãªã„å ´åˆã¯ã€ã‚¿ãƒ¼ã‚²ãƒƒãƒˆã«ãƒ‘ターンを使用ã™ã‚‹ã“ã¨ã¯ã§ãã¾ã›ã‚“。インベントリーã«è¡¨ç¤ºã•ã‚Œãªã„ IP アドレスã¾ãŸã¯ãƒ›ã‚¹ãƒˆåãŒãƒ‘ターンã«å«ã¾ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ãªã‚¨ãƒ©ãƒ¼ãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:93 +#: ../../rst/user_guide/intro_patterns.rst:105 msgid "Your pattern must match your inventory syntax. If you define a host as an :ref:`alias<inventory_aliases>`:" msgstr "ãŠä½¿ã„ã®ãƒ‘ターンã¯ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼æ§‹æ–‡ã«ä¸€è‡´ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ホストを :ref:`エイリアス<inventory_aliases>` ã¨ã—ã¦å®šç¾©ã™ã‚‹å ´åˆã¯ã€ä»¥ä¸‹ã‚’指定ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:103 -msgid "you must use the alias in your pattern. In the example above, you must use ``host1`` in your pattern. If you use the IP address, you will once again get the error::" +#: ../../rst/user_guide/intro_patterns.rst:115 +msgid "you must use the alias in your pattern. In the example above, you must use ``host1`` in your pattern. If you use the IP address, you will once again get the error:" msgstr "パターンã§ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã‚’使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚上記ã®ä¾‹ã§ã¯ã€ãƒ‘ターン㧠``host1`` を使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚IP アドレスを使用ã™ã‚‹å ´åˆã¯ã€ã‚¨ãƒ©ãƒ¼ãŒå†åº¦è¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:108 +#: ../../rst/user_guide/intro_patterns.rst:122 msgid "Advanced pattern options" msgstr "詳細ãªãƒ‘ターンオプション" -#: ../../rst/user_guide/intro_patterns.rst:110 +#: ../../rst/user_guide/intro_patterns.rst:124 msgid "The common patterns described above will meet most of your needs, but Ansible offers several other ways to define the hosts and groups you want to target." msgstr "上記ã®ä¸€èˆ¬çš„ãªãƒ‘ターンã¯ã»ã¨ã‚“ã©ã®ãƒ‹ãƒ¼ã‚ºã«å¯¾å¿œã—ã¾ã™ãŒã€Ansible ã§ã¯ã€å¯¾è±¡ã¨ã™ã‚‹ãƒ›ã‚¹ãƒˆãŠã‚ˆã³ã‚°ãƒ«ãƒ¼ãƒ—を定義ã™ã‚‹ä»–ã®æ–¹æ³•ã‚‚ã„ãã¤ã‹æä¾›ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:113 +#: ../../rst/user_guide/intro_patterns.rst:127 msgid "Using variables in patterns" msgstr "パターンã«ãŠã‘る変数ã®ä½¿ç”¨" -#: ../../rst/user_guide/intro_patterns.rst:115 -msgid "You can use variables to enable passing group specifiers via the ``-e`` argument to ansible-playbook::" +#: ../../rst/user_guide/intro_patterns.rst:129 +msgid "You can use variables to enable passing group specifiers via the ``-e`` argument to ansible-playbook:" msgstr "変数を使ã†ã¨ã€ansible-playbook ã® ``-e`` 引数ã§ã‚°ãƒ«ãƒ¼ãƒ—指定åを渡ã›ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:120 +#: ../../rst/user_guide/intro_patterns.rst:136 msgid "Using group position in patterns" msgstr "パターンã«ãŠã‘るグループã®ä½ç½®ã®ä½¿ç”¨" -#: ../../rst/user_guide/intro_patterns.rst:122 -msgid "You can define a host or subset of hosts by its position in a group. For example, given the following group::" +#: ../../rst/user_guide/intro_patterns.rst:138 +msgid "You can define a host or subset of hosts by its position in a group. For example, given the following group:" msgstr "グループ内ã®ä½ç½®ã«ã‚ˆã£ã¦ã€ãƒ›ã‚¹ãƒˆã‚„ホストã®ã‚µãƒ–セットを定義ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€æ¬¡ã®ã‚ˆã†ãªã‚°ãƒ«ãƒ¼ãƒ—ãŒæŒ‡å®šã•ã‚ŒãŸå ´åˆã§ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:129 -msgid "you can use subscripts to select individual hosts or ranges within the webservers group::" +#: ../../rst/user_guide/intro_patterns.rst:147 +msgid "you can use subscripts to select individual hosts or ranges within the webservers group:" msgstr "subscripts を使用ã—ã¦ã€webservers グループ内ã®ãƒ›ã‚¹ãƒˆã¾ãŸã¯ç¯„囲を個別ã«é¸æŠžã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:139 +#: ../../rst/user_guide/intro_patterns.rst:159 msgid "Using regexes in patterns" msgstr "パターンã§æ£è¦è¡¨ç¾ã®ä½¿ç”¨" -#: ../../rst/user_guide/intro_patterns.rst:141 -msgid "You can specify a pattern as a regular expression by starting the pattern with ``~``::" +#: ../../rst/user_guide/intro_patterns.rst:161 +msgid "You can specify a pattern as a regular expression by starting the pattern with ``~``:" msgstr "パターンをæ£è¦è¡¨ç¾ã¨ã—ã¦æŒ‡å®šã™ã‚‹ã«ã¯ã€``~`` ã§ãƒ‘ターンを開始ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:148 +#: ../../rst/user_guide/intro_patterns.rst:170 msgid "You can change the behavior of the patterns defined in ad-hoc commands using command-line options. You can also limit the hosts you target on a particular run with the ``--limit`` flag." msgstr "コマンドラインオプションを使用ã—ã¦ã€ã‚¢ãƒ‰ãƒ›ãƒƒã‚¯ã‚³ãƒžãƒ³ãƒ‰ã§å®šç¾©ã•ã‚ŒãŸãƒ‘ターンã®å‹•ä½œã‚’変更ã§ãã¾ã™ã€‚ã¾ãŸã€``--limit`` フラグを使用ã—ã¦ã€ç‰¹å®šã®å®Ÿè¡Œã§å¯¾è±¡ã¨ã™ã‚‹ãƒ›ã‚¹ãƒˆã‚’制é™ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:151 +#: ../../rst/user_guide/intro_patterns.rst:173 msgid "Limit to one host" msgstr "1 å°ã®ãƒ›ã‚¹ãƒˆã«åˆ¶é™ã™ã‚‹" -#: ../../rst/user_guide/intro_patterns.rst:157 +#: ../../rst/user_guide/intro_patterns.rst:179 msgid "Limit to multiple hosts" msgstr "複数ã®ãƒ›ã‚¹ãƒˆã«åˆ¶é™ã™ã‚‹" -#: ../../rst/user_guide/intro_patterns.rst:163 +#: ../../rst/user_guide/intro_patterns.rst:185 msgid "Negated limit. Note that single quotes MUST be used to prevent bash interpolation." msgstr "å¦å®šçš„ãªåˆ¶é™ã€‚bash ã®è£œé–“を防ããŸã‚ã«ã€ä¸€é‡å¼•ç”¨ç¬¦ã‚’使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:169 +#: ../../rst/user_guide/intro_patterns.rst:191 msgid "Limit to host group" msgstr "ホストグループã«åˆ¶é™ã™ã‚‹" -#: ../../rst/user_guide/intro_patterns.rst:176 +#: ../../rst/user_guide/intro_patterns.rst:198 msgid "Patterns and ansible-playbook flags" msgstr "パターンãŠã‚ˆã³ ansible-playbook フラグ" -#: ../../rst/user_guide/intro_patterns.rst:178 -msgid "You can change the behavior of the patterns defined in playbooks using command-line options. For example, you can run a playbook that defines ``hosts: all`` on a single host by specifying ``-i 127.0.0.2,`` (note the trailing comma). This works even if the host you target is not defined in your inventory. You can also limit the hosts you target on a particular run with the ``--limit`` flag::" +#: ../../rst/user_guide/intro_patterns.rst:200 +msgid "You can change the behavior of the patterns defined in playbooks using command-line options. For example, you can run a playbook that defines ``hosts: all`` on a single host by specifying ``-i 127.0.0.2,`` (note the trailing comma). This works even if the host you target is not defined in your inventory. You can also limit the hosts you target on a particular run with the ``--limit`` flag:" msgstr "コマンドラインオプションを使用ã—㦠Playbook ã§å®šç¾©ã—ãŸãƒ‘ターンã®å‹•ä½œã‚’変更ã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€``-i 127.0.0.2,`` (末尾ã®ã‚³ãƒ³ãƒž) を指定ã—ã¦ã€å˜ä¸€ã®ãƒ›ã‚¹ãƒˆã§ ``hosts: all`` を定義ã™ã‚‹ Playbook を実行ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã‚Œã¯ã€å¯¾è±¡ã¨ã™ã‚‹ãƒ›ã‚¹ãƒˆãŒã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã«å®šç¾©ã•ã‚Œã¦ã„ãªã„å ´åˆã§ã‚‚有効ã§ã™ã€‚ã¾ãŸã€``--limit`` フラグを使用ã—ã¦ã€ç‰¹å®šã®å®Ÿè¡Œã§å¯¾è±¡ã¨ã™ã‚‹ãƒ›ã‚¹ãƒˆã‚’制é™ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:182 -msgid "Finally, you can use ``--limit`` to read the list of hosts from a file by prefixing the file name with ``@``::" +#: ../../rst/user_guide/intro_patterns.rst:206 +msgid "Finally, you can use ``--limit`` to read the list of hosts from a file by prefixing the file name with ``@``:" msgstr "最後㫠``--limit`` を使用ã—ã¦ã€ãƒ•ã‚¡ã‚¤ãƒ«åã®å‰ã« ``@`` を付ã‘ã‚‹ã“ã¨ã§ã€ãƒ•ã‚¡ã‚¤ãƒ«ã‹ã‚‰ãƒ›ã‚¹ãƒˆã®ãƒªã‚¹ãƒˆã‚’èªã¿è¾¼ã‚€ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:186 +#: ../../rst/user_guide/intro_patterns.rst:212 msgid "If :ref:`RETRY_FILES_ENABLED` is set to ``True``, a ``.retry`` file will be created after the ``ansible-playbook`` run containing a list of failed hosts from all plays. This file is overwritten each time ``ansible-playbook`` finishes running." msgstr ":ref:`RETRY_FILES_ENABLED` ㌠``True`` ã«è¨å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€``ansible-playbook`` ã®å®Ÿè¡Œå¾Œã«ã€ã™ã¹ã¦ã®ãƒ—レイã§å¤±æ•—ã—ãŸãƒ›ã‚¹ãƒˆã®ãƒªã‚¹ãƒˆã‚’å«ã‚€ ``.retry`` ファイルãŒä½œæˆã•ã‚Œã¾ã™ã€‚ã“ã®ãƒ•ã‚¡ã‚¤ãƒ«ã¯ã€``ansible-playbook`` ã®å®Ÿè¡ŒãŒçµ‚了ã™ã‚‹ãŸã³ã«ä¸Šæ›¸ãã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/intro_patterns.rst:188 +#: ../../rst/user_guide/intro_patterns.rst:214 msgid "ansible-playbook site.yml --limit @site.retry" msgstr "ansible-playbook site.yml --limit @site.retry" -#: ../../rst/user_guide/intro_patterns.rst:190 +#: ../../rst/user_guide/intro_patterns.rst:216 msgid "To apply your knowledge of patterns with Ansible commands and playbooks, read :ref:`intro_adhoc` and :ref:`playbooks_intro`." msgstr "Ansible コマンドãŠã‚ˆã³ Playbook ã§ãƒ‘ターンã«é–¢ã™ã‚‹çŸ¥è˜ã‚’活用ã™ã‚‹ã«ã¯ã€ã€Œ:ref:`intro_adhoc`ã€ãŠã‚ˆã³ã€Œ:ref:`playbooks_intro`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/intro_patterns.rst:197 +#: ../../rst/user_guide/intro_patterns.rst:223 msgid "Learning the Ansible configuration management language" msgstr "Ansible ã®è¨å®šç®¡ç†è¨€èªžã«ã¤ã„ã¦" @@ -3895,26 +3890,26 @@ msgid "Users can also write their own modules. These modules can control system msgstr "ユーザーã¯è‡ªåˆ†ã§ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’書ãã“ã¨ã‚‚ã§ãã¾ã™ã€‚ã“れらã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€ã‚µãƒ¼ãƒ“スã€ãƒ‘ッケージã€ãƒ•ã‚¡ã‚¤ãƒ«ãªã© (実際ã«ã¯ã©ã‚“ãªã‚‚ã®ã§ã‚‚) ã®ã‚·ã‚¹ãƒ†ãƒ リソースを制御ã—ãŸã‚Šã€ã‚·ã‚¹ãƒ†ãƒ コマンドを実行ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" #: ../../rst/user_guide/modules.rst:24 -#: ../../rst/user_guide/modules_intro.rst:42 +#: ../../rst/user_guide/modules_intro.rst:52 #: ../../rst/user_guide/modules_support.rst:64 msgid "Examples of using modules in /usr/bin/ansible" msgstr "/usr/bin/ansible ã«ãŠã‘るモジュールã®ä½¿ç”¨ä¾‹" #: ../../rst/user_guide/modules.rst:25 -#: ../../rst/user_guide/playbooks_async.rst:170 +#: ../../rst/user_guide/playbooks_async.rst:184 #: ../../rst/user_guide/playbooks_blocks.rst:182 -#: ../../rst/user_guide/playbooks_debugger.rst:324 -#: ../../rst/user_guide/playbooks_delegation.rst:149 -#: ../../rst/user_guide/playbooks_environment.rst:136 -#: ../../rst/user_guide/playbooks_error_handling.rst:234 -#: ../../rst/user_guide/playbooks_prompts.rst:107 -#: ../../rst/user_guide/playbooks_startnstep.rst:37 +#: ../../rst/user_guide/playbooks_debugger.rst:337 +#: ../../rst/user_guide/playbooks_delegation.rst:165 +#: ../../rst/user_guide/playbooks_environment.rst:148 +#: ../../rst/user_guide/playbooks_error_handling.rst:262 +#: ../../rst/user_guide/playbooks_prompts.rst:115 +#: ../../rst/user_guide/playbooks_startnstep.rst:43 #: ../../rst/user_guide/playbooks_tags.rst:425 #: ../../rst/user_guide/playbooks_templating.rst:46 -#: ../../rst/user_guide/playbooks_tests.rst:388 -#: ../../rst/user_guide/windows_dsc.rst:496 -#: ../../rst/user_guide/windows_usage.rst:504 -#: ../../rst/user_guide/windows_winrm.rst:905 +#: ../../rst/user_guide/playbooks_tests.rst:424 +#: ../../rst/user_guide/windows_dsc.rst:498 +#: ../../rst/user_guide/windows_usage.rst:508 +#: ../../rst/user_guide/windows_winrm.rst:927 msgid ":ref:`playbooks_intro`" msgstr ":ref:`playbooks_intro`" @@ -3927,17 +3922,17 @@ msgid ":ref:`developing_modules_general`" msgstr ":ref:`developing_modules_general`" #: ../../rst/user_guide/modules.rst:28 -#: ../../rst/user_guide/modules_intro.rst:46 +#: ../../rst/user_guide/modules_intro.rst:56 msgid "How to write your own modules" msgstr "独自ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ä½œæˆæ–¹æ³•" #: ../../rst/user_guide/modules.rst:29 -#: ../../rst/user_guide/modules_intro.rst:47 +#: ../../rst/user_guide/modules_intro.rst:57 msgid ":ref:`developing_api`" msgstr ":ref:`developing_api`" #: ../../rst/user_guide/modules.rst:30 -#: ../../rst/user_guide/modules_intro.rst:48 +#: ../../rst/user_guide/modules_intro.rst:58 msgid "Examples of using modules with the Python API" msgstr "Python API ã§ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã™ã‚‹ä¾‹" @@ -3958,34 +3953,34 @@ msgid "Modules (also referred to as \"task plugins\" or \"library plugins\") are msgstr "モジュール (「タスクプラグインã€ã¾ãŸã¯ã€Œãƒ©ã‚¤ãƒ–ラリープラグインã€ã¨ã‚‚呼ã°ã‚Œã‚‹) ã¯ã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã¾ãŸã¯ Playbook タスクã§ä½¿ç”¨å¯èƒ½ãªã‚³ãƒ¼ãƒ‰ã®å€‹åˆ¥å˜ä½ã§ã™ã€‚Ansible ã¯ã€å„モジュールを実行ã—ã€é€šå¸¸ã®ãƒªãƒ¢ãƒ¼ãƒˆç®¡ç†ãƒŽãƒ¼ãƒ‰ã§å®Ÿè¡Œã—ã€æˆ»ã‚Šå€¤ã‚’åŽé›†ã—ã¾ã™ã€‚Ansible 2.10 以é™ã§ã¯ã€ã»ã¨ã‚“ã©ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã§ãƒ›ã‚¹ãƒˆã•ã‚Œã¾ã™ã€‚" #: ../../rst/user_guide/modules_intro.rst:8 -msgid "You can execute modules from the command line::" +msgid "You can execute modules from the command line." msgstr "コマンドラインã‹ã‚‰ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’実行ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/modules_intro.rst:14 +#: ../../rst/user_guide/modules_intro.rst:16 msgid "Each module supports taking arguments. Nearly all modules take ``key=value`` arguments, space delimited. Some modules take no arguments, and the command/shell modules simply take the string of the command you want to run." msgstr "å„モジュールã¯ã€å¼•æ•°ã‚’å–ã‚‹ã“ã¨ã‚’サãƒãƒ¼ãƒˆã—ã¦ã„ã¾ã™ã€‚ã»ã¼ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€ã‚¹ãƒšãƒ¼ã‚¹ã§åŒºåˆ‡ã‚‰ã‚ŒãŸ ``key=value`` ã®å¼•æ•°ã‚’å–ã‚Šã¾ã™ã€‚一部ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯å¼•æ•°ã‚’å–らãšã€ã‚³ãƒžãƒ³ãƒ‰/シェルモジュールã¯å˜ã«å®Ÿè¡Œã—ãŸã„コマンドã®æ–‡å—列をå–ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/modules_intro.rst:16 -msgid "From playbooks, Ansible modules are executed in a very similar way::" +#: ../../rst/user_guide/modules_intro.rst:18 +msgid "From playbooks, Ansible modules are executed in a very similar way." msgstr "Playbook ã‹ã‚‰ã€Ansible モジュールã¯åŒã˜ã‚ˆã†ãªæ–¹æ³•ã§å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/modules_intro.rst:21 -msgid "Another way to pass arguments to a module is using YAML syntax, also called 'complex args' ::" +#: ../../rst/user_guide/modules_intro.rst:25 +msgid "Another way to pass arguments to a module is using YAML syntax, also called 'complex args'." msgstr "ã‚‚ã—ãã¯ã€ã€Œcomplex argsã€ã¨ã‚‚呼ã°ã‚Œã‚‹ YAML 構文を使用ã—ã¦ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«å¼•æ•°ã‚’渡ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/modules_intro.rst:28 +#: ../../rst/user_guide/modules_intro.rst:34 msgid "All modules return JSON format data. This means modules can be written in any programming language. Modules should be idempotent, and should avoid making any changes if they detect that the current state matches the desired final state. When used in an Ansible playbook, modules can trigger 'change events' in the form of notifying :ref:`handlers <handlers>` to run additional tasks." msgstr "ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ JSON å½¢å¼ã®ãƒ‡ãƒ¼ã‚¿ã‚’è¿”ã—ã¾ã™ã€‚ã“ã‚Œã¯ã€ã©ã®ãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚°è¨€èªžã§ã‚‚モジュールを作æˆã§ãã¾ã™ã€‚モジュールã¯å†ªç‰ã§ã‚ã‚Šã€ç¾åœ¨ã®çŠ¶æ…‹ãŒå¿…è¦ãªæœ€çµ‚状態ã¨ä¸€è‡´ã™ã‚‹ã“ã¨ã‚’検知ã™ã‚‹ã¨ã€å¤‰æ›´ã¯å›žé¿ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚Ansible Playbook ã§ä½¿ç”¨ã™ã‚‹ã¨ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ :ref:`handlers <handlers>` ã«é€šçŸ¥ã™ã‚‹å½¢å¼ã§ã€Œå¤‰æ›´ã‚¤ãƒ™ãƒ³ãƒˆã€ã‚’トリガーã—ã¦è¿½åŠ ã®ã‚¿ã‚¹ã‚¯ã‚’実行ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/modules_intro.rst:30 -msgid "You can access the documentation for each module from the command line with the ansible-doc tool::" +#: ../../rst/user_guide/modules_intro.rst:36 +msgid "You can access the documentation for each module from the command line with the ansible-doc tool." msgstr "å„モジュールã®ãƒ‰ã‚ュメントã¯ã€ansible-doc ツールを使用ã—ã¦ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã‹ã‚‰ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/modules_intro.rst:34 -msgid "For a list of all available modules, see the :ref:`Collection docs <list_of_collections>`, or run the following at a command prompt::" +#: ../../rst/user_guide/modules_intro.rst:42 +msgid "For a list of all available modules, see the :ref:`Collection docs <list_of_collections>`, or run the following at a command prompt." msgstr "利用å¯èƒ½ãªãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ä¸€è¦§ã¯ã€ã€Œ:ref:`Collection docs <list_of_collections>`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。ã¾ãŸã¯ã€ã‚³ãƒžãƒ³ãƒ‰ãƒ—ãƒãƒ³ãƒ—トã§æ¬¡ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/modules_intro.rst:44 +#: ../../rst/user_guide/modules_intro.rst:54 #: ../../rst/user_guide/modules_support.rst:66 msgid "Examples of using modules with /usr/bin/ansible-playbook" msgstr "/usr/bin/ansible-playbook ã§ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã™ã‚‹ä¾‹" @@ -4145,18 +4140,18 @@ msgid "Lookups and action plugins both use a special 'search magic' to find thin msgstr "lookup ãŠã‚ˆã³ action プラグインã¯ã©ã¡ã‚‰ã‚‚特殊ãªã€Œæ¤œç´¢ãƒžã‚¸ãƒƒã‚¯ã€ã‚’使用ã—ã¾ã™ã€‚ã“ã‚Œã«ã¯ç¾åœ¨ã®ãƒ—レイãŒè€ƒæ…®ã•ã‚Œã€ã‚¿ã‚¹ã‚¯ãŒå«ã¾ã‚Œã‚‹ Playbook ディレクトリー (ã“ã‚Œã«ã¯ãƒãƒ¼ãƒ«ã¨ã‚¤ãƒ³ã‚¯ãƒ«ãƒ¼ãƒ‰ã‚’å«ã‚€) ã§ã€ã‚ˆã‚Šå…·ä½“çš„ãªæŒ‡å®šã‹ã‚‰ã‚ˆã‚Šä¸€èˆ¬çš„ãªæŒ‡å®šãŒä½¿ç”¨ã•ã‚Œã¾ã™ã€‚" #: ../../rst/user_guide/playbook_pathing.rst:28 -msgid "Using this magic, relative paths get attempted first with a 'files|templates|vars' appended (if not already present), depending on action being taken, 'files' is the default. (in other words, include_vars will use vars/). The paths will be searched from most specific to most general (in other words, role before play). dependent roles WILL be traversed (in other words, task is in role2, role2 is a dependency of role1, role2 will be looked at first, then role1, then play). i.e ::" +msgid "Using this magic, relative paths get attempted first with a 'files|templates|vars' appended (if not already present), depending on action being taken, 'files' is the default. (in other words, include_vars will use vars/). The paths will be searched from most specific to most general (in other words, role before play). dependent roles WILL be traversed (in other words, task is in role2, role2 is a dependency of role1, role2 will be looked at first, then role1, then play). i.e :" msgstr "ã“ã®ãƒžã‚¸ãƒƒã‚¯ã‚’使用ã™ã‚‹ã¨ã€ç›¸å¯¾ãƒ‘スãŒå˜åœ¨ã—ã¦ã„ãªã„å ´åˆã¯ã€æœ€åˆã«ã€Œfiles|templates|varsã€ã‚’ä»˜åŠ ã—ã¦è©¦è¡Œã•ã‚Œã¾ã™ã€‚実行ã•ã‚Œã‚‹ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ã«ã‚ˆã£ã¦ã¯ã€Œfilesã€ãŒãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã«ãªã‚Šã¾ã™ (ã¤ã¾ã‚Šã€include_vars 㯠vars/ を使用ã—ã¾ã™)。パスã¯ã€æœ€ã‚‚具体的ãªã‚‚ã®ã‹ã‚‰æœ€ã‚‚一般的ãªã‚‚ã®ã¸æ¤œç´¢ã•ã‚Œã¾ã™ (ã¤ã¾ã‚Šã€play ã®å‰ã« role ãŒã‚ã‚Šã¾ã™)。ä¾å˜ã™ã‚‹ãƒãƒ¼ãƒ«ã¯ã€æ¨ªæ–ã•ã‚Œã¾ã™ (ã¤ã¾ã‚Šã€ã‚¿ã‚¹ã‚¯ãŒ role2 ã«ã‚ã‚Šã€role2 ㌠role1 ã®ä¾å˜é–¢ä¿‚ã«ã‚ã‚‹å ´åˆã¯ã€role2 ãŒæœ€åˆã«æ¤œç´¢ã•ã‚Œã€æ¬¡ã« role1ã€ãã—㦠play ãŒæ¤œç´¢ã•ã‚Œã¾ã™)。ã¤ã¾ã‚Šã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbook_pathing.rst:36 +#: ../../rst/user_guide/playbook_pathing.rst:38 msgid "By default, Ansible does not search the current working directory unless it happens to coincide with one of the paths above. If you `include` a task file from a role, it will NOT trigger role behavior, this only happens when running as a role, `include_role` will work. A new variable `ansible_search_path` var will have the search path used, in order (but without the appended subdirs). Using 5 \"v\"s (`-vvvvv`) should show the detail of the search as it happens." msgstr "デフォルトã§ã¯ã€Ansible ã¯ä¸Šè¨˜ã®ãƒ‘スã®ã„ãšã‚Œã‹ã«ä¸€è‡´ã—ãªã„é™ã‚Šã€ç¾åœ¨ã®ä½œæ¥ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã‚’検索ã—ã¾ã›ã‚“。ãƒãƒ¼ãƒ«ã‹ã‚‰ã‚¿ã‚¹ã‚¯ãƒ•ã‚¡ã‚¤ãƒ«ã‚’ `include` ã—ãŸå ´åˆã¯ã€ãƒãƒ¼ãƒ«ã®å‹•ä½œã‚’誘発ã™ã‚‹ã“ã¨ã¯ã‚ã‚Šã¾ã›ã‚“。ã“ã‚Œã¯ãƒãƒ¼ãƒ«ã¨ã—ã¦å®Ÿè¡Œã—ãŸå ´åˆã«ã®ã¿ç™ºç”Ÿã—ã€`include_role` ã¯å‹•ä½œã—ã¾ã™ã€‚æ–°ã—ã„変数 `ansible_search_path` ã«ã¯ã€ä½¿ç”¨ã•ã‚Œã‚‹æ¤œç´¢ãƒ‘スãŒé †ç•ªã«å…¥ã‚Šã¾ã™ (ãŸã ã—ã€ä»˜åŠ ã•ã‚ŒãŸã‚µãƒ–ディレクトリーã¯å«ã¾ã‚Œã¾ã›ã‚“)。5ã¤ã®ã€Œvã€(`-vvvvv`) を使用ã—ã¦ã€æ¤œç´¢ã®è©³ç´°ã‚’表示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbook_pathing.rst:38 +#: ../../rst/user_guide/playbook_pathing.rst:40 msgid "As for includes, they try the path of the included file first and fall back to the play/role that includes them." msgstr "インクルードã«é–¢ã—ã¦ã¯ã€æœ€åˆã«ã‚¤ãƒ³ã‚¯ãƒ«ãƒ¼ãƒ‰ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã®ãƒ‘スを試ã—ã€ãã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’å«ã‚€ãƒ—レイã¾ãŸã¯ãƒãƒ¼ãƒ«ã«ãƒ•ã‚©ãƒ¼ãƒ«ãƒãƒƒã‚¯ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbook_pathing.rst:42 +#: ../../rst/user_guide/playbook_pathing.rst:44 msgid "The current working directory might vary depending on the connection plugin and if the action is local or remote. For the remote it is normally the directory on which the login shell puts the user. For local it is either the directory you executed ansible from or in some cases the playbook directory." msgstr "ç¾åœ¨ã®ä½œæ¥ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã¯ã€æŽ¥ç¶šãƒ—ラグインã¨ã€ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ãŒãƒãƒ¼ã‚«ãƒ«ã‹ãƒªãƒ¢ãƒ¼ãƒˆã‹ã«ã‚ˆã£ã¦ç•°ãªã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚リモートã®å ´åˆã€é€šå¸¸ã€ãƒã‚°ã‚¤ãƒ³ã‚·ã‚§ãƒ«ãŒãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚’é…ç½®ã™ã‚‹ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã«ãªã‚Šã¾ã™ã€‚ãƒãƒ¼ã‚«ãƒ«ã®å ´åˆã¯ã€ansibleを実行ã—ãŸãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã‹ã€å ´åˆã«ã‚ˆã£ã¦ã¯Playbokディレクトリã«ãªã‚Šã¾ã™ã€‚" @@ -4206,93 +4201,93 @@ msgid "You can use the same ``unsafe`` data type in variables you define, to pre msgstr "定義ã—ãŸå¤‰æ•°ã«åŒã˜ ``unsafe`` データ型を使用ã™ã‚‹ã¨ã€ãƒ†ãƒ³ãƒ—ãƒ¬ãƒ¼ãƒˆã‚¨ãƒ©ãƒ¼ã‚„æƒ…å ±ã®æ¼ãˆã„を防ãã“ã¨ãŒã§ãã¾ã™ã€‚:ref:`vars_prompts<unsafe_prompts>` ã«ã‚ˆã‚Šæä¾›ã•ã‚ŒãŸå€¤ã‚’安全ã§ãªã„ã‚‚ã®ã¨ã—ã¦ãƒžãƒ¼ã‚¯ä»˜ã‘ã§ãã¾ã™ã€‚Playbook 㧠``unsafe`` を使用ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚最も一般的ãªãƒ¦ãƒ¼ã‚¹ã‚±ãƒ¼ã‚¹ã«ã¯ã€ãƒ†ãƒ³ãƒ—レートã®ã‚ˆã†ãª ``{`` ã‚„ ``%`` ãªã©ã®ç‰¹æ®Šæ–‡å—を許å¯ã™ã‚‹ãƒ‘スワードãŒå«ã¾ã‚Œã¦ã„ã¾ã™ãŒã€ãƒ†ãƒ³ãƒ—レート化ã™ã¹ãã§ã¯ã‚ã‚Šã¾ã›ã‚“。以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" #: ../../rst/user_guide/playbooks_advanced_syntax.rst:26 -msgid "In a playbook::" +msgid "In a playbook:" msgstr "Playbook ã®å ´åˆã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:35 -msgid "For complex variables such as hashes or arrays, use ``!unsafe`` on the individual elements::" +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:37 +msgid "For complex variables such as hashes or arrays, use ``!unsafe`` on the individual elements:" msgstr "ãƒãƒƒã‚·ãƒ¥ã‚„é…列ãªã©ã®è¤‡é›‘ãªå¤‰æ•°ã®å ´åˆã¯ã€å€‹ã€…ã®è¦ç´ 㧠``!unsafe`` を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:48 +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:52 msgid "YAML anchors and aliases: sharing variable values" msgstr "YAML アンカーãŠã‚ˆã³ã‚¨ã‚¤ãƒªã‚¢ã‚¹: 変数値ã®å…±æœ‰" -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:50 -msgid "`YAML anchors and aliases <https://yaml.org/spec/1.2/spec.html#id2765878>`_ help you define, maintain, and use shared variable values in a flexible way. You define an anchor with ``&``, then refer to it using an alias, denoted with ``*``. Here's an example that sets three values with an anchor, uses two of those values with an alias, and overrides the third value::" +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:54 +msgid "`YAML anchors and aliases <https://yaml.org/spec/1.2/spec.html#id2765878>`_ help you define, maintain, and use shared variable values in a flexible way. You define an anchor with ``&``, then refer to it using an alias, denoted with ``*``. Here's an example that sets three values with an anchor, uses two of those values with an alias, and overrides the third value:" msgstr "`YAML アンカーãŠã‚ˆã³ã‚¨ã‚¤ãƒªã‚¢ã‚¹ <https://yaml.org/spec/1.2/spec.html#id2765878>`_ ã¯ã€æŸ”軟ãªæ–¹æ³•ã§å…±æœ‰å¤‰æ•°ã®å€¤ã‚’定義ã€ç¶æŒã€ãŠã‚ˆã³ä½¿ç”¨ã™ã‚‹ã®ã«å½¹ç«‹ã¡ã¾ã™ã€‚``&`` ã§ã‚¢ãƒ³ã‚«ãƒ¼ã‚’定義ã—ã€``*`` ã§ç¤ºã™ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã‚’使用ã—ã¦å‚ç…§ã—ã¾ã™ã€‚ã“ã“ã§ã¯ã€ã‚¢ãƒ³ã‚«ãƒ¼ã§ 3 ã¤ã®å€¤ã‚’è¨å®šã—ã€ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã§ã“れらã®å€¤ã‚’ 2 ã¤ä½¿ç”¨ã—ã€3 番目ã®å€¤ã‚’上書ãã™ã‚‹ä¾‹ã‚’以下ã«ç¤ºã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:67 +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:73 msgid "Here, ``app1`` and ``app2`` share the values for ``opts`` and ``port`` using the anchor ``&jvm_opts`` and the alias ``*jvm_opts``. The value for ``path`` is merged by ``<<`` or `merge operator <https://yaml.org/type/merge.html>`_." msgstr "ã“ã“ã§ã€``app1`` ãŠã‚ˆã³ ``app2`` ã¯ã€ã‚¢ãƒ³ã‚«ãƒ¼ ``&jvm_opts`` ãŠã‚ˆã³ã‚¨ã‚¤ãƒªã‚¢ã‚¹ ``*jvm_opts`` を使用ã—ã¦ã€``opts`` 㨠``port`` ã®å€¤ã‚’共有ã—ã¾ã™ã€‚``path`` ã®å€¤ã¯ã€``<<`` ã¾ãŸã¯ `merge operator <https://yaml.org/type/merge.html>`_ ã«ã‚ˆã£ã¦ãƒžãƒ¼ã‚¸ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:70 -msgid "Anchors and aliases also let you share complex sets of variable values, including nested variables. If you have one variable value that includes another variable value, you can define them separately::" +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:76 +msgid "Anchors and aliases also let you share complex sets of variable values, including nested variables. If you have one variable value that includes another variable value, you can define them separately:" msgstr "アンカーãŠã‚ˆã³ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã‚’使用ã™ã‚‹ã¨ã€å…¥ã‚Œåã«ãªã£ãŸå¤‰æ•°ãªã©ã€è¤‡é›‘ãªå¤‰æ•°å€¤ã®ã‚»ãƒƒãƒˆã‚’共有ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚ã‚る変数値ã«åˆ¥ã®å¤‰æ•°å€¤ãŒå«ã¾ã‚Œã¦ã„ã‚‹å ´åˆã¯ã€ãã®å¤‰æ•°å€¤ã‚’別々ã«å®šç¾©ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:76 -msgid "This is inefficient and, at scale, means more maintenance. To incorporate the version value in the name, you can use an anchor in ``app_version`` and an alias in ``custom_name``::" +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:84 +msgid "This is inefficient and, at scale, means more maintenance. To incorporate the version value in the name, you can use an anchor in ``app_version`` and an alias in ``custom_name``:" msgstr "ã“ã‚Œã¯éžåŠ¹çŽ‡çš„ã§ã‚ã‚Šã€å¤§è¦æ¨¡ãªå ´åˆã«ã¯ã€ã‚ˆã‚Šå¤šãã®ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ãŒè¡Œã‚ã‚Œã¾ã™ã€‚åå‰ã« version ã®å€¤ã‚’組ã¿è¾¼ã‚€ã«ã¯ã€``app_version`` ã«ã‚¢ãƒ³ã‚«ãƒ¼ã¨ã€``custom_name`` ã®ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã‚’使用ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:85 -msgid "Now, you can re-use the value of ``app_version`` within the value of ``custom_name`` and use the output in a template::" +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:95 +msgid "Now, you can re-use the value of ``app_version`` within the value of ``custom_name`` and use the output in a template:" msgstr "ã“ã‚Œã§ã€``custom_name`` ã®å€¤ã® ``app_version`` ã®å€¤ã‚’å†åˆ©ç”¨ã—ã€ãƒ†ãƒ³ãƒ—レートã§å‡ºåŠ›ã‚’使用ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:101 +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:113 msgid "You've anchored the value of ``version`` with the ``&my_version`` anchor, and re-used it with the ``*my_version`` alias. Anchors and aliases let you access nested values inside dictionaries." msgstr "``version`` ã®å€¤ã‚’ ``&my_version`` ã¨ã„ã†ã‚¢ãƒ³ã‚«ãƒ¼ã§å›ºå®šã—ã€``*my_version`` ã¨ã„ã†ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã§å†åˆ©ç”¨ã—ã¦ã„ã¾ã™ã€‚アンカーã¨ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã‚’使用ã™ã‚‹ã“ã¨ã§ã€ãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼å†…ã®ãƒã‚¹ãƒˆã—ãŸå€¤ã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:106 -#: ../../rst/user_guide/playbooks_conditionals.rst:504 -#: ../../rst/user_guide/playbooks_error_handling.rst:241 +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:118 +#: ../../rst/user_guide/playbooks_conditionals.rst:532 +#: ../../rst/user_guide/playbooks_error_handling.rst:269 #: ../../rst/user_guide/playbooks_filters.rst:1842 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:732 -#: ../../rst/user_guide/playbooks_lookups.rst:31 -#: ../../rst/user_guide/playbooks_loops.rst:443 -#: ../../rst/user_guide/playbooks_prompts.rst:112 -#: ../../rst/user_guide/playbooks_tests.rst:393 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:854 +#: ../../rst/user_guide/playbooks_lookups.rst:33 +#: ../../rst/user_guide/playbooks_loops.rst:485 +#: ../../rst/user_guide/playbooks_prompts.rst:120 +#: ../../rst/user_guide/playbooks_tests.rst:429 msgid "All about variables" msgstr "変数ã®è©³ç´°" -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:107 +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:119 msgid ":ref:`complex_data_manipulation`" msgstr ":ref:`complex_data_manipulation`" -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:108 +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:120 msgid "Doing complex data manipulation in Ansible" msgstr "Ansible ã§ã®è¤‡é›‘ãªãƒ‡ãƒ¼ã‚¿æ“作ã®å®Ÿè¡Œ" -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:109 -#: ../../rst/user_guide/windows_dsc.rst:502 -#: ../../rst/user_guide/windows_faq.rst:248 -#: ../../rst/user_guide/windows_setup.rst:580 -#: ../../rst/user_guide/windows_usage.rst:510 -#: ../../rst/user_guide/windows_winrm.rst:911 +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:121 +#: ../../rst/user_guide/windows_dsc.rst:504 +#: ../../rst/user_guide/windows_faq.rst:252 +#: ../../rst/user_guide/windows_setup.rst:603 +#: ../../rst/user_guide/windows_usage.rst:514 +#: ../../rst/user_guide/windows_winrm.rst:933 msgid "`User Mailing List <https://groups.google.com/group/ansible-project>`_" msgstr "`User Mailing List <https://groups.google.com/group/ansible-project>`_" -#: ../../rst/user_guide/playbooks_advanced_syntax.rst:110 -#: ../../rst/user_guide/playbooks_async.rst:173 +#: ../../rst/user_guide/playbooks_advanced_syntax.rst:122 +#: ../../rst/user_guide/playbooks_async.rst:187 #: ../../rst/user_guide/playbooks_blocks.rst:187 -#: ../../rst/user_guide/playbooks_conditionals.rst:506 -#: ../../rst/user_guide/playbooks_debugger.rst:327 -#: ../../rst/user_guide/playbooks_delegation.rst:156 -#: ../../rst/user_guide/playbooks_environment.rst:139 -#: ../../rst/user_guide/playbooks_error_handling.rst:243 +#: ../../rst/user_guide/playbooks_conditionals.rst:534 +#: ../../rst/user_guide/playbooks_debugger.rst:340 +#: ../../rst/user_guide/playbooks_delegation.rst:172 +#: ../../rst/user_guide/playbooks_environment.rst:151 +#: ../../rst/user_guide/playbooks_error_handling.rst:271 #: ../../rst/user_guide/playbooks_filters.rst:1850 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:740 -#: ../../rst/user_guide/playbooks_lookups.rst:35 -#: ../../rst/user_guide/playbooks_loops.rst:445 -#: ../../rst/user_guide/playbooks_prompts.rst:114 -#: ../../rst/user_guide/playbooks_strategies.rst:223 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:862 +#: ../../rst/user_guide/playbooks_lookups.rst:37 +#: ../../rst/user_guide/playbooks_loops.rst:487 +#: ../../rst/user_guide/playbooks_prompts.rst:122 +#: ../../rst/user_guide/playbooks_strategies.rst:249 #: ../../rst/user_guide/playbooks_tags.rst:430 #: ../../rst/user_guide/playbooks_templating.rst:59 -#: ../../rst/user_guide/playbooks_tests.rst:401 -#: ../../rst/user_guide/playbooks_variables.rst:464 -#: ../../rst/user_guide/windows_dsc.rst:503 -#: ../../rst/user_guide/windows_faq.rst:249 -#: ../../rst/user_guide/windows_setup.rst:581 -#: ../../rst/user_guide/windows_usage.rst:511 -#: ../../rst/user_guide/windows_winrm.rst:912 +#: ../../rst/user_guide/playbooks_tests.rst:437 +#: ../../rst/user_guide/playbooks_variables.rst:510 +#: ../../rst/user_guide/windows_dsc.rst:505 +#: ../../rst/user_guide/windows_faq.rst:253 +#: ../../rst/user_guide/windows_setup.rst:604 +#: ../../rst/user_guide/windows_usage.rst:515 +#: ../../rst/user_guide/windows_winrm.rst:934 msgid "Have a question? Stop by the google group!" msgstr "ã”質å•ã¯ã”ã–ã„ã¾ã™ã‹ã€‚Google Group ã‚’ã”覧ãã ã•ã„。" @@ -4309,123 +4304,123 @@ msgid "Asynchronous ad hoc tasks" msgstr "éžåŒæœŸã‚¢ãƒ‰ãƒ›ãƒƒã‚¯ã‚¿ã‚¹ã‚¯" #: ../../rst/user_guide/playbooks_async.rst:14 -msgid "You can execute long-running operations in the background with :ref:`ad hoc tasks <intro_adhoc>`. For example, to execute ``long_running_operation`` asynchronously in the background, with a timeout (``-B``) of 3600 seconds, and without polling (``-P``)::" -msgstr ":ref:`ad hoc tasks <intro_adhoc>` を使用ã™ã‚‹ã¨ã€ãƒãƒƒã‚¯ã‚°ãƒ©ã‚¦ãƒ³ãƒ‰ã§é•·æ™‚間実行ã•ã‚Œã‚‹æ“作を実行ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€``long_running_operation`` ã‚’ãƒãƒƒã‚¯ã‚°ãƒ©ã‚¦ãƒ³ãƒ‰ã§éžåŒæœŸçš„ã«å®Ÿè¡Œã—ã€ã‚¿ã‚¤ãƒ アウト (``-B``) ã‚’ 3600 秒ã«è¨å®šã—ã€ãƒãƒ¼ãƒªãƒ³ã‚° (``-P``) ã‚’è¡Œã‚ãªã„å ´åˆã¯æ¬¡ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" +msgid "You can execute long-running operations in the background with :ref:`ad hoc tasks <intro_adhoc>`. For example, to execute ``long_running_operation`` asynchronously in the background, with a timeout (``-B``) of 3600 seconds, and without polling (``-P``):" +msgstr ":ref:`アドホックタスク <intro_adhoc>` を使用ã™ã‚‹ã¨ã€ãƒãƒƒã‚¯ã‚°ãƒ©ã‚¦ãƒ³ãƒ‰ã§é•·æ™‚間実行ã•ã‚Œã‚‹æ“作を実行ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€``long_running_operation`` ã‚’ãƒãƒƒã‚¯ã‚°ãƒ©ã‚¦ãƒ³ãƒ‰ã§éžåŒæœŸçš„ã«å®Ÿè¡Œã—ã€ã‚¿ã‚¤ãƒ アウト (``-B``) ã‚’ 3600 秒ã«è¨å®šã—ã€ãƒãƒ¼ãƒªãƒ³ã‚° (``-P``) ã‚’è¡Œã‚ãªã„å ´åˆã¯æ¬¡ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:18 -msgid "To check on the job status later, use the ``async_status`` module, passing it the job ID that was returned when you ran the original job in the background::" +#: ../../rst/user_guide/playbooks_async.rst:20 +msgid "To check on the job status later, use the ``async_status`` module, passing it the job ID that was returned when you ran the original job in the background:" msgstr "後ã§ã‚¸ãƒ§ãƒ–ステータスを確èªã™ã‚‹ã«ã¯ã€``async_status`` モジュールを使用ã—ã€ãƒãƒƒã‚¯ã‚°ãƒ©ã‚¦ãƒ³ãƒ‰ã§å…ƒã®ã‚¸ãƒ§ãƒ–ã®å®Ÿè¡Œæ™‚ã«è¿”ã•ã‚ŒãŸã‚¸ãƒ§ãƒ– ID を渡ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:22 -msgid "Ansible can also check on the status of your long-running job automatically with polling. In most cases, Ansible will keep the connection to your remote node open between polls. To run for 30 minutes and poll for status every 60 seconds::" +#: ../../rst/user_guide/playbooks_async.rst:26 +msgid "Ansible can also check on the status of your long-running job automatically with polling. In most cases, Ansible will keep the connection to your remote node open between polls. To run for 30 minutes and poll for status every 60 seconds:" msgstr "Ansible ã¯ã€ãƒãƒ¼ãƒªãƒ³ã‚°ã«ã‚ˆã£ã¦é•·æ™‚間実行ã™ã‚‹ã‚¸ãƒ§ãƒ–ã®çŠ¶æ…‹ã‚’自動的ã«ç¢ºèªã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚ã»ã¨ã‚“ã©ã®å ´åˆã€Ansible ã¯ãƒãƒ¼ãƒªãƒ³ã‚°ã®é–“もリモートノードã¸ã®æŽ¥ç¶šã‚’ç¶æŒã—ã¾ã™ã€‚30 分間実行ã—ã€60 秒ã”ã¨ã«ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã‚’ãƒãƒ¼ãƒªãƒ³ã‚°ã™ã‚‹ã«ã¯æ¬¡ã®ã‚ˆã†ã«ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:26 +#: ../../rst/user_guide/playbooks_async.rst:32 msgid "Poll mode is smart so all jobs will be started before polling begins on any machine. Be sure to use a high enough ``--forks`` value if you want to get all of your jobs started very quickly. After the time limit (in seconds) runs out (``-B``), the process on the remote nodes will be terminated." msgstr "ãƒãƒ¼ãƒªãƒ³ã‚°ãƒ¢ãƒ¼ãƒ‰ã¯é«˜æ€§èƒ½ã§ã‚ã‚‹ãŸã‚ã€ã©ã®ãƒžã‚·ãƒ³ã§ã‚‚ãƒãƒ¼ãƒªãƒ³ã‚°ãŒé–‹å§‹ã™ã‚‹å‰ã«ã™ã¹ã¦ã®ã‚¸ãƒ§ãƒ–ãŒé–‹å§‹ã—ã¾ã™ã€‚ã™ã¹ã¦ã®ã‚¸ãƒ§ãƒ–ã‚’éžå¸¸ã«è¿…速ã«é–‹å§‹ã—ãŸã„å ´åˆã¯ ``--forks`` ã‚’å分ãªé«˜ã•ã«ã—ã¦ãã ã•ã„。制é™æ™‚é–“ (秒å˜ä½) ãŒãªããªã‚‹ã¨ (``-B``)ã€ãƒªãƒ¢ãƒ¼ãƒˆãƒŽãƒ¼ãƒ‰ã®ãƒ—ãƒã‚»ã‚¹ã¯çµ‚了ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:28 +#: ../../rst/user_guide/playbooks_async.rst:34 msgid "Asynchronous mode is best suited to long-running shell commands or software upgrades. Running the copy module asynchronously, for example, does not do a background file transfer." msgstr "éžåŒæœŸãƒ¢ãƒ¼ãƒ‰ã¯ã€é•·æ™‚間実行ã™ã‚‹ã‚·ã‚§ãƒ«ã‚³ãƒžãƒ³ãƒ‰ã‚„ソフトウェアã®ã‚¢ãƒƒãƒ—グレードã«æœ€é©ã§ã™ã€‚ãŸã¨ãˆã°ã€copy モジュールをéžåŒæœŸã§å®Ÿè¡Œã—ã¦ã‚‚ã€ãƒãƒƒã‚¯ã‚°ãƒ©ã‚¦ãƒ³ãƒ‰ã§ã®ãƒ•ã‚¡ã‚¤ãƒ«è»¢é€ã¯è¡Œã‚ã‚Œã¾ã›ã‚“。" -#: ../../rst/user_guide/playbooks_async.rst:31 +#: ../../rst/user_guide/playbooks_async.rst:37 msgid "Asynchronous playbook tasks" msgstr "éžåŒæœŸ Playbook タスク" -#: ../../rst/user_guide/playbooks_async.rst:33 +#: ../../rst/user_guide/playbooks_async.rst:39 msgid ":ref:`Playbooks <working_with_playbooks>` also support asynchronous mode and polling, with a simplified syntax. You can use asynchronous mode in playbooks to avoid connection timeouts or to avoid blocking subsequent tasks. The behavior of asynchronous mode in a playbook depends on the value of `poll`." msgstr ":ref:`Playbook <working_with_playbooks>` ã¯ã€éžåŒæœŸãƒ¢ãƒ¼ãƒ‰ã¨ãƒãƒ¼ãƒªãƒ³ã‚°ã‚‚サãƒãƒ¼ãƒˆã—ã¦ãŠã‚Šã€æ§‹æ–‡ã‚‚ç°¡ç´ åŒ–ã•ã‚Œã¦ã„ã¾ã™ã€‚éžåŒæœŸãƒ¢ãƒ¼ãƒ‰ã‚’ Playbook ã§ä½¿ç”¨ã™ã‚‹ã¨ã€æŽ¥ç¶šã®ã‚¿ã‚¤ãƒ アウトやã€å¾Œç¶šã‚¿ã‚¹ã‚¯ã®ãƒ–ãƒãƒƒã‚¯ã‚’回é¿ã§ãã¾ã™ã€‚Playbook ã§ã®éžåŒæœŸãƒ¢ãƒ¼ãƒ‰ã®å‹•ä½œã¯ã€`poll` ã®å€¤ã«ä¾å˜ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:36 +#: ../../rst/user_guide/playbooks_async.rst:42 msgid "Avoid connection timeouts: poll > 0" msgstr "接続ã®ã‚¿ã‚¤ãƒ アウトã®å›žé¿: poll > 0" -#: ../../rst/user_guide/playbooks_async.rst:38 +#: ../../rst/user_guide/playbooks_async.rst:44 msgid "If you want to set a longer timeout limit for a certain task in your playbook, use ``async`` with ``poll`` set to a positive value. Ansible will still block the next task in your playbook, waiting until the async task either completes, fails or times out. However, the task will only time out if it exceeds the timeout limit you set with the ``async`` parameter." msgstr "Playbook 内ã®ç‰¹å®šã®ã‚¿ã‚¹ã‚¯ã«ã‚ˆã‚Šé•·ã„タイムアウト制é™ã‚’è¨å®šã™ã‚‹å ´åˆã¯ã€``async`` を使用ã—ã€``poll`` ã‚’æ£ã®å€¤ã«è¨å®šã—ã¾ã™ã€‚Ansible ã¯ã€Playbook 内ã«è¨˜è¼‰ã•ã‚Œã‚‹æ¬¡ã®ã‚¿ã‚¹ã‚¯ã‚’ブãƒãƒƒã‚¯ã—ã€éžåŒæœŸã‚¿ã‚¹ã‚¯ãŒå®Œäº†ã™ã‚‹ã‹ã€å¤±æ•—ã™ã‚‹ã‹ã€ã‚¿ã‚¤ãƒ アウトã«ãªã‚‹ã¾ã§å¾…æ©Ÿã—ã¾ã™ã€‚ãŸã ã—ã€ã‚¿ã‚¹ã‚¯ãŒã‚¿ã‚¤ãƒ アウトã«ãªã‚‹ã®ã¯ã€``async`` パラメーターã§è¨å®šã—ãŸã‚¿ã‚¤ãƒ アウト制é™ã‚’超ãˆãŸå ´åˆã®ã¿ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:40 -msgid "To avoid timeouts on a task, specify its maximum runtime and how frequently you would like to poll for status::" +#: ../../rst/user_guide/playbooks_async.rst:46 +msgid "To avoid timeouts on a task, specify its maximum runtime and how frequently you would like to poll for status:" msgstr "タスクã§ã‚¿ã‚¤ãƒ アウトを回é¿ã™ã‚‹ã«ã¯ã€æœ€å¤§ãƒ©ãƒ³ã‚¿ã‚¤ãƒ ã¨ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã‚’ãƒãƒ¼ãƒªãƒ³ã‚°ã™ã‚‹é »åº¦ã‚’指定ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:55 +#: ../../rst/user_guide/playbooks_async.rst:63 msgid "The default poll value is set by the :ref:`DEFAULT_POLL_INTERVAL` setting. There is no default for the async time limit. If you leave off the 'async' keyword, the task runs synchronously, which is Ansible's default." msgstr "デフォルトã®ãƒãƒ¼ãƒ«å€¤ã¯ã€:ref:`DEFAULT_POLL_INTERVAL` ã®è¨å®šã§è¨å®šã•ã‚Œã¾ã™ã€‚éžåŒæœŸæ™‚間制é™ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã¯ã‚ã‚Šã¾ã›ã‚“。「asyncã€ã‚ーワードをçœç•¥ã™ã‚‹ã¨ã€ã‚¿ã‚¹ã‚¯ã¯åŒæœŸçš„ã«å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚ã“れ㌠Ansible ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:61 +#: ../../rst/user_guide/playbooks_async.rst:69 msgid "As of Ansible 2.3, async does not support check mode and will fail the task when run in check mode. See :ref:`check_mode_dry` on how to skip a task in check mode." msgstr "Ansible 2.3 ã®æ™‚点ã§ã¯ã€éžåŒæœŸã¯ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã‚’サãƒãƒ¼ãƒˆã—ã¦ãŠã‚‰ãšã€ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã§å®Ÿè¡Œã™ã‚‹ã¨ã‚¿ã‚¹ã‚¯ãŒå¤±æ•—ã—ã¾ã™ã€‚ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã§ã‚¿ã‚¹ã‚¯ã‚’スã‚ップã™ã‚‹æ–¹æ³•ã¯ã€ã€Œ:ref:`check_mode_dry`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_async.rst:66 +#: ../../rst/user_guide/playbooks_async.rst:74 msgid "When an async task completes with polling enabled, the temporary async job cache file (by default in ~/.ansible_async/) is automatically removed." msgstr "ãƒãƒ¼ãƒªãƒ³ã‚°ã‚’有効ã«ã—ã¦éžåŒæœŸã‚¿ã‚¹ã‚¯ãŒå®Œäº†ã™ã‚‹ã¨ã€ä¸€æ™‚çš„ãªéžåŒæœŸã‚¸ãƒ§ãƒ–ã‚ャッシュファイル (デフォルトã§ã¯ ~/.ansible_async/ ã«ã‚ã‚‹) ãŒè‡ªå‹•çš„ã«å‰Šé™¤ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:70 +#: ../../rst/user_guide/playbooks_async.rst:78 msgid "Run tasks concurrently: poll = 0" msgstr "タスクã®åŒæ™‚実行: poll = 0" -#: ../../rst/user_guide/playbooks_async.rst:72 +#: ../../rst/user_guide/playbooks_async.rst:80 msgid "If you want to run multiple tasks in a playbook concurrently, use ``async`` with ``poll`` set to 0. When you set ``poll: 0``, Ansible starts the task and immediately moves on to the next task without waiting for a result. Each async task runs until it either completes, fails or times out (runs longer than its ``async`` value). The playbook run ends without checking back on async tasks." msgstr "Playbook 内ã®è¤‡æ•°ã®ã‚¿ã‚¹ã‚¯ã‚’åŒæ™‚ã«å®Ÿè¡Œã™ã‚‹å ´åˆã¯ã€``async`` を使用ã—ã€``poll`` ã‚’ 0 ã«è¨å®šã—ã¾ã™ã€‚``poll: 0`` ã‚’è¨å®šã™ã‚‹ã¨ã€Ansible ã¯ã‚¿ã‚¹ã‚¯ã‚’開始ã—ã€çµæžœã‚’å¾…ãŸãšã«ç›´ã¡ã«æ¬¡ã®ã‚¿ã‚¹ã‚¯ã«ç§»ã‚Šã¾ã™ã€‚å„éžåŒæœŸã‚¿ã‚¹ã‚¯ã¯ã€å®Œäº†ã™ã‚‹ã‹ã€å¤±æ•—ã™ã‚‹ã‹ã€ã‚¿ã‚¤ãƒ アウトã«ã™ã‚‹ (``async`` ã®å€¤ã‚ˆã‚Šã‚‚é•·ã実行ã•ã‚Œã‚‹) ã¾ã§å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚Playbook ã®å®Ÿè¡Œã¯ã€éžåŒæœŸã‚¿ã‚¹ã‚¯ã‚’å†åº¦ãƒã‚§ãƒƒã‚¯ã›ãšã«çµ‚了ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:74 -msgid "To run a playbook task asynchronously::" +#: ../../rst/user_guide/playbooks_async.rst:82 +msgid "To run a playbook task asynchronously:" msgstr "Playbook タスクをéžåŒæœŸçš„ã«å®Ÿè¡Œã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:89 +#: ../../rst/user_guide/playbooks_async.rst:99 msgid "Do not specify a poll value of 0 with operations that require exclusive locks (such as yum transactions) if you expect to run other commands later in the playbook against those same resources." msgstr "排他的ãƒãƒƒã‚¯ã‚’å¿…è¦ã¨ã™ã‚‹æ“作 (yum トランザクションãªã©) ã§ã¯ã€åŒã˜ãƒªã‚½ãƒ¼ã‚¹ã«å¯¾ã—㦠Playbook ã®å¾ŒåŠã§ä»–ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã™ã‚‹ã“ã¨ã‚’想定ã—ã¦ã€poll 値㫠0 を指定ã—ãªã„ã§ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_async.rst:92 +#: ../../rst/user_guide/playbooks_async.rst:102 msgid "Using a higher value for ``--forks`` will result in kicking off asynchronous tasks even faster. This also increases the efficiency of polling." msgstr "``--forks`` ã®å€¤ã‚’増やã™ã¨ã€éžåŒæœŸã‚¿ã‚¹ã‚¯ã®é–‹å§‹ãŒé€Ÿããªã‚Šã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ãƒãƒ¼ãƒªãƒ³ã‚°ã®åŠ¹çŽ‡ãŒé«˜ã¾ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:95 +#: ../../rst/user_guide/playbooks_async.rst:105 msgid "When running with ``poll: 0``, Ansible will not automatically cleanup the async job cache file. You will need to manually clean this up with the :ref:`async_status <async_status_module>` module with ``mode: cleanup``." msgstr "``poll: 0`` ã§å®Ÿè¡Œã™ã‚‹ã¨ã€Ansible ã¯éžåŒæœŸã‚¸ãƒ§ãƒ–ã‚ャッシュファイルを自動的ã«ã‚¯ãƒªãƒ¼ãƒ³ã‚¢ãƒƒãƒ—ã—ã¾ã›ã‚“。``mode: cleanup`` 㧠:ref:`async_status <async_status_module>` モジュールを使用ã—ã¦æ‰‹å‹•ã§ã‚¯ãƒªãƒ¼ãƒ³ã‚¢ãƒƒãƒ—ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:99 -msgid "If you need a synchronization point with an async task, you can register it to obtain its job ID and use the :ref:`async_status <async_status_module>` module to observe it in a later task. For example::" +#: ../../rst/user_guide/playbooks_async.rst:109 +msgid "If you need a synchronization point with an async task, you can register it to obtain its job ID and use the :ref:`async_status <async_status_module>` module to observe it in a later task. For example:" msgstr "éžåŒæœŸã‚¿ã‚¹ã‚¯ã¨ã®åŒæœŸãƒã‚¤ãƒ³ãƒˆãŒå¿…è¦ãªå ´åˆã¯ã€ã“れを登録ã—ã¦ã‚¸ãƒ§ãƒ– ID ã‚’å–å¾—ã—ã€:ref:`async_status <async_status_module>` モジュールを使用ã—ã¦å¾Œç¶šã®ã‚¿ã‚¹ã‚¯ã§ç¢ºèªã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:118 +#: ../../rst/user_guide/playbooks_async.rst:130 msgid "If the value of ``async:`` is not high enough, this will cause the \"check on it later\" task to fail because the temporary status file that the ``async_status:`` is looking for will not have been written or no longer exist" msgstr "``async:`` ã®å€¤ãŒå分ã«é«˜ããªã„å ´åˆã¯ã€``async_status:`` ãŒæŽ¢ã—ã¦ã„る一時的ãªã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ãƒ•ã‚¡ã‚¤ãƒ«ãŒæ›¸ãè¾¼ã¾ã‚Œã¦ã„ãªã„ã‹ã€å˜åœ¨ã—ãªããªã£ãŸãŸã‚ã€ã€Œå¾Œã§ç¢ºèªã™ã‚‹ã€ã‚¿ã‚¹ã‚¯ãŒå¤±æ•—ã™ã‚‹ã“ã¨ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:123 +#: ../../rst/user_guide/playbooks_async.rst:135 msgid "Asynchronous playbook tasks always return changed. If the task is using a module that requires the user to annotate changes with ``changed_when``, ``creates``, and so on, then those should be added to the following ``async_status`` task." msgstr "éžåŒæœŸ Playbook タスクã¯å¸¸ã«å¤‰æ›´ã‚’è¿”ã—ã¾ã™ã€‚タスクãŒã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒ ``changed_when`` ãŠã‚ˆã³ ``creates`` を使用ã—ã¦å¤‰æ›´ã«ã‚¢ãƒŽãƒ†ãƒ¼ã‚·ãƒ§ãƒ³ã‚’付ã‘ã‚‹å¿…è¦ãŒã‚るモジュールを使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãれらã®ã‚¿ã‚¹ã‚¯ã‚’以下㮠``async_status`` タスクã«è¿½åŠ ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:127 -msgid "To run multiple asynchronous tasks while limiting the number of tasks running concurrently::" +#: ../../rst/user_guide/playbooks_async.rst:139 +msgid "To run multiple asynchronous tasks while limiting the number of tasks running concurrently:" msgstr "複数ã®éžåŒæœŸã‚¿ã‚¹ã‚¯ã‚’実行ã—ãªãŒã‚‰ã€åŒæ™‚ã«å®Ÿè¡Œã™ã‚‹ã‚¿ã‚¹ã‚¯ã®æ•°ã‚’制é™ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_async.rst:168 -#: ../../rst/user_guide/playbooks_delegation.rst:151 +#: ../../rst/user_guide/playbooks_async.rst:182 +#: ../../rst/user_guide/playbooks_delegation.rst:167 msgid ":ref:`playbooks_strategies`" msgstr ":ref:`playbooks_strategies`" -#: ../../rst/user_guide/playbooks_async.rst:169 +#: ../../rst/user_guide/playbooks_async.rst:183 msgid "Options for controlling playbook execution" msgstr "Playbook ã®å®Ÿè¡Œã‚’制御ã™ã‚‹ã‚ªãƒ—ション" -#: ../../rst/user_guide/playbooks_async.rst:172 +#: ../../rst/user_guide/playbooks_async.rst:186 #: ../../rst/user_guide/playbooks_blocks.rst:186 -#: ../../rst/user_guide/playbooks_conditionals.rst:505 -#: ../../rst/user_guide/playbooks_debugger.rst:326 -#: ../../rst/user_guide/playbooks_delegation.rst:155 -#: ../../rst/user_guide/playbooks_environment.rst:138 -#: ../../rst/user_guide/playbooks_error_handling.rst:242 +#: ../../rst/user_guide/playbooks_conditionals.rst:533 +#: ../../rst/user_guide/playbooks_debugger.rst:339 +#: ../../rst/user_guide/playbooks_delegation.rst:171 +#: ../../rst/user_guide/playbooks_environment.rst:150 +#: ../../rst/user_guide/playbooks_error_handling.rst:270 #: ../../rst/user_guide/playbooks_filters.rst:1849 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:739 -#: ../../rst/user_guide/playbooks_lookups.rst:34 -#: ../../rst/user_guide/playbooks_loops.rst:444 -#: ../../rst/user_guide/playbooks_prompts.rst:113 -#: ../../rst/user_guide/playbooks_strategies.rst:222 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:861 +#: ../../rst/user_guide/playbooks_lookups.rst:36 +#: ../../rst/user_guide/playbooks_loops.rst:486 +#: ../../rst/user_guide/playbooks_prompts.rst:121 +#: ../../rst/user_guide/playbooks_strategies.rst:248 #: ../../rst/user_guide/playbooks_tags.rst:429 #: ../../rst/user_guide/playbooks_templating.rst:58 -#: ../../rst/user_guide/playbooks_tests.rst:400 -#: ../../rst/user_guide/playbooks_variables.rst:463 +#: ../../rst/user_guide/playbooks_tests.rst:436 +#: ../../rst/user_guide/playbooks_variables.rst:509 msgid "`User Mailing List <https://groups.google.com/group/ansible-devel>`_" msgstr "`ユーザーメーリングリスト <https://groups.google.com/group/ansible-devel>`_" @@ -4622,52 +4617,52 @@ msgid "This pulls in variables from the group_vars/os_CentOS.yml file." msgstr "ã“ã‚Œã«ã‚ˆã‚Šã€group_vars/os_CentOS.yml ファイルã‹ã‚‰å¤‰æ•°ãŒãƒ—ルã•ã‚Œã¾ã™ã€‚" #: ../../rst/user_guide/playbooks_best_practices.rst:154 -#: ../../rst/user_guide/playbooks_intro.rst:142 +#: ../../rst/user_guide/playbooks_intro.rst:146 #: ../../rst/user_guide/playbooks_reuse_includes.rst:13 #: ../../rst/user_guide/playbooks_reuse_roles.rst:602 -#: ../../rst/user_guide/sample_setup.rst:272 +#: ../../rst/user_guide/sample_setup.rst:308 msgid ":ref:`yaml_syntax`" msgstr ":ref:`yaml_syntax`" #: ../../rst/user_guide/playbooks_best_practices.rst:155 -#: ../../rst/user_guide/playbooks_intro.rst:143 +#: ../../rst/user_guide/playbooks_intro.rst:147 #: ../../rst/user_guide/playbooks_reuse_includes.rst:14 #: ../../rst/user_guide/playbooks_reuse_roles.rst:603 -#: ../../rst/user_guide/sample_setup.rst:273 +#: ../../rst/user_guide/sample_setup.rst:309 msgid "Learn about YAML syntax" msgstr "YAML 構文ã«ã¤ã„ã¦" #: ../../rst/user_guide/playbooks_best_practices.rst:157 -#: ../../rst/user_guide/sample_setup.rst:275 +#: ../../rst/user_guide/sample_setup.rst:311 msgid "Review the basic playbook features" msgstr "基本的㪠Playbook 機能ã®ç¢ºèª" #: ../../rst/user_guide/playbooks_best_practices.rst:161 #: ../../rst/user_guide/playbooks_reuse_includes.rst:28 -#: ../../rst/user_guide/sample_setup.rst:279 +#: ../../rst/user_guide/sample_setup.rst:315 msgid "Learn how to extend Ansible by writing your own modules" msgstr "独自ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’作æˆã—㦠Ansible ã‚’æ‹¡å¼µã™ã‚‹æ–¹æ³•ã«ã¤ã„ã¦" #: ../../rst/user_guide/playbooks_best_practices.rst:162 -#: ../../rst/user_guide/playbooks_intro.rst:150 -#: ../../rst/user_guide/sample_setup.rst:280 +#: ../../rst/user_guide/playbooks_intro.rst:154 +#: ../../rst/user_guide/sample_setup.rst:316 msgid ":ref:`intro_patterns`" msgstr ":ref:`intro_patterns`" #: ../../rst/user_guide/playbooks_best_practices.rst:163 -#: ../../rst/user_guide/playbooks_intro.rst:151 -#: ../../rst/user_guide/sample_setup.rst:281 +#: ../../rst/user_guide/playbooks_intro.rst:155 +#: ../../rst/user_guide/sample_setup.rst:317 msgid "Learn about how to select hosts" msgstr "ホストã®é¸æŠžæ–¹æ³•ã«ã¤ã„ã¦" #: ../../rst/user_guide/playbooks_best_practices.rst:164 -#: ../../rst/user_guide/playbooks_intro.rst:152 -#: ../../rst/user_guide/sample_setup.rst:282 +#: ../../rst/user_guide/playbooks_intro.rst:156 +#: ../../rst/user_guide/sample_setup.rst:318 msgid "`GitHub examples directory <https://github.com/ansible/ansible-examples>`_" msgstr "`GitHub サンプルディレクトリー <https://github.com/ansible/ansible-examples>`_" #: ../../rst/user_guide/playbooks_best_practices.rst:165 -#: ../../rst/user_guide/sample_setup.rst:283 +#: ../../rst/user_guide/sample_setup.rst:319 msgid "Complete playbook files from the github project source" msgstr "Github プãƒã‚¸ã‚§ã‚¯ãƒˆã‚½ãƒ¼ã‚¹ã®å®Œå…¨ãª Playbook ファイル" @@ -4768,15 +4763,15 @@ msgid "The captured return result of the failed task that triggered the rescue. msgstr "レスã‚ューをトリガーã—ãŸå¤±æ•—ã—ãŸã‚¿ã‚¹ã‚¯ã®æˆ»ã‚Šå€¤ã€‚ã“ã‚Œã¯ã€``register`` ã‚ーワードã§ã“ã®å¤‰æ•°ã‚’使用ã™ã‚‹ã®ã¨åŒã˜ã§ã™ã€‚" #: ../../rst/user_guide/playbooks_blocks.rst:185 -#: ../../rst/user_guide/playbooks_conditionals.rst:500 +#: ../../rst/user_guide/playbooks_conditionals.rst:528 #: ../../rst/user_guide/playbooks_filters.rst:1846 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:736 -#: ../../rst/user_guide/playbooks_loops.rst:437 -#: ../../rst/user_guide/playbooks_strategies.rst:221 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:858 +#: ../../rst/user_guide/playbooks_loops.rst:479 +#: ../../rst/user_guide/playbooks_strategies.rst:247 #: ../../rst/user_guide/playbooks_tags.rst:428 #: ../../rst/user_guide/playbooks_templating.rst:53 -#: ../../rst/user_guide/playbooks_tests.rst:397 -#: ../../rst/user_guide/playbooks_variables.rst:458 +#: ../../rst/user_guide/playbooks_tests.rst:433 +#: ../../rst/user_guide/playbooks_variables.rst:504 msgid "Playbook organization by roles" msgstr "ãƒãƒ¼ãƒ«åˆ¥ã® Playbook ã®çµ„ç¹”" @@ -4793,59 +4788,59 @@ msgid "Using check mode" msgstr "ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã®ä½¿ç”¨" #: ../../rst/user_guide/playbooks_checkmode.rst:15 -msgid "Check mode is just a simulation. It will not generate output for tasks that use :ref:`conditionals based on registered variables <conditionals_registered_vars>` (results of prior tasks). However, it is great for validating configuration management playbooks that run on one node at a time. To run a playbook in check mode::" -msgstr "ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã¯ã‚ãã¾ã§ã‚‚シミュレーションã§ã™ã€‚:ref:`登録変数ã«åŸºã¥ã„ãŸæ¡ä»¶ <conditionals_registered_vars>` (先行タスクã®çµæžœ) を使用ã™ã‚‹ã‚¿ã‚¹ã‚¯ã®å‡ºåŠ›ã¯ç”Ÿæˆã•ã‚Œã¾ã›ã‚“。ã—ã‹ã—ã€ä¸€åº¦ã« 1 ã¤ã®ãƒŽãƒ¼ãƒ‰ã§å®Ÿè¡Œã™ã‚‹æ§‹æˆç®¡ç†ã® Playbook を検証ã™ã‚‹ã«ã¯æœ€é©ã§ã™ã€‚Playbook ã‚’ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã§å®Ÿè¡Œã™ã‚‹ã«ã¯ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" +msgid "Check mode is just a simulation. It will not generate output for tasks that use :ref:`conditionals based on registered variables <conditionals_registered_vars>` (results of prior tasks). However, it is great for validating configuration management playbooks that run on one node at a time. To run a playbook in check mode:" +msgstr "ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã¯ã‚ãã¾ã§ã‚‚シミュレーションã§ã™ã€‚:ref:`conditionals based on registered variables <conditionals_registered_vars>` (先行タスクã®çµæžœ) を使用ã™ã‚‹ã‚¿ã‚¹ã‚¯ã®å‡ºåŠ›ã¯ç”Ÿæˆã•ã‚Œã¾ã›ã‚“。ã—ã‹ã—ã€ä¸€åº¦ã« 1 ã¤ã®ãƒŽãƒ¼ãƒ‰ã§å®Ÿè¡Œã™ã‚‹æ§‹æˆç®¡ç†ã® Playbook を検証ã™ã‚‹ã«ã¯æœ€é©ã§ã™ã€‚Playbook ã‚’ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã§å®Ÿè¡Œã™ã‚‹ã«ã¯ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_checkmode.rst:22 +#: ../../rst/user_guide/playbooks_checkmode.rst:24 msgid "Enforcing or preventing check mode on tasks" msgstr "タスクã§ã®ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã®å¼·åˆ¶ã¾ãŸã¯ç¦æ¢" -#: ../../rst/user_guide/playbooks_checkmode.rst:26 +#: ../../rst/user_guide/playbooks_checkmode.rst:28 msgid "If you want certain tasks to run in check mode always, or never, regardless of whether you run the playbook with or without ``--check``, you can add the ``check_mode`` option to those tasks:" msgstr "Playbook を実行ã™ã‚‹éš›ã« ``--check`` を付ã‘ã‚‹ã‹ã©ã†ã‹ã«é–¢ã‚らãšã€ç‰¹å®šã®ã‚¿ã‚¹ã‚¯ã‚’常ã«ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã§å®Ÿè¡Œã™ã‚‹å ´åˆã¯ã€ãれらã®ã‚¿ã‚¹ã‚¯ã« ``check_mode`` ã‚ªãƒ—ã‚·ãƒ§ãƒ³ã‚’è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_checkmode.rst:28 +#: ../../rst/user_guide/playbooks_checkmode.rst:30 msgid "To force a task to run in check mode, even when the playbook is called without ``--check``, set ``check_mode: yes``." msgstr "``--check`` を使用ã›ãšã« Playbook ãŒå‘¼ã³å‡ºã•ã‚ŒãŸå ´åˆã§ã‚‚ã€ã‚¿ã‚¹ã‚¯ã‚’強制的ã«ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã§å®Ÿè¡Œã™ã‚‹ã«ã¯ã€``check_mode: yes`` ã‚’è¨å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_checkmode.rst:29 +#: ../../rst/user_guide/playbooks_checkmode.rst:31 msgid "To force a task to run in normal mode and make changes to the system, even when the playbook is called with ``--check``, set ``check_mode: no``." msgstr "Playbook ㌠``--check`` ã§å‘¼ã³å‡ºã•ã‚ŒãŸå ´åˆã§ã‚‚ã€ã‚¿ã‚¹ã‚¯ã‚’強制的ã«é€šå¸¸ãƒ¢ãƒ¼ãƒ‰ã§å®Ÿè¡Œã—ã€ã‚·ã‚¹ãƒ†ãƒ ã«å¤‰æ›´ã‚’åŠ ãˆã‚‹ã«ã¯ã€``check_mode: no`` ã‚’è¨å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_checkmode.rst:46 +#: ../../rst/user_guide/playbooks_checkmode.rst:50 msgid "Running single tasks with ``check_mode: yes`` can be useful for testing Ansible modules, either to test the module itself or to test the conditions under which a module would make changes. You can register variables (see :ref:`playbooks_conditionals`) on these tasks for even more detail on the potential changes." msgstr "``check_mode: yes`` を使用ã—ã¦ã‚·ãƒ³ã‚°ãƒ«ã‚¿ã‚¹ã‚¯ã‚’実行ã™ã‚‹ã¨ã€Ansible モジュールをテストã™ã‚‹éš›ã«ä¾¿åˆ©ã§ã™ã€‚モジュール自体をテストã—ãŸã‚Šã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒå¤‰æ›´ã‚’è¡Œã†æ¡ä»¶ã‚’テストã—ãŸã‚Šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“れらã®ã‚¿ã‚¹ã‚¯ã«å¤‰æ•° (:ref:`playbooks_conditionals` ã‚’å‚ç…§) を登録ã™ã‚‹ã¨ã€æ½œåœ¨çš„ãªå¤‰æ›´ã«ã¤ã„ã¦ã•ã‚‰ã«è©³ã—ã知るã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_checkmode.rst:48 +#: ../../rst/user_guide/playbooks_checkmode.rst:52 msgid "Prior to version 2.2 only the equivalent of ``check_mode: no`` existed. The notation for that was ``always_run: yes``." msgstr "ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.2 以å‰ã§ã¯ã€``check_mode: no`` ã«ç›¸å½“ã™ã‚‹ã‚‚ã®ã ã‘ãŒå˜åœ¨ã—ã¦ã„ã¾ã—ãŸã€‚ãã®è¡¨è¨˜æ³•ã¯ ``always_run: yes`` ã§ã—ãŸã€‚" -#: ../../rst/user_guide/playbooks_checkmode.rst:51 +#: ../../rst/user_guide/playbooks_checkmode.rst:55 msgid "Skipping tasks or ignoring errors in check mode" msgstr "タスクをスã‚ップã¾ãŸã¯ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã§ã‚¨ãƒ©ãƒ¼ã‚’無視ã™ã‚‹" -#: ../../rst/user_guide/playbooks_checkmode.rst:55 -msgid "If you want to skip a task or ignore errors on a task when you run Ansible in check mode, you can use a boolean magic variable ``ansible_check_mode``, which is set to ``True`` when Ansible runs in check mode. For example::" +#: ../../rst/user_guide/playbooks_checkmode.rst:59 +msgid "If you want to skip a task or ignore errors on a task when you run Ansible in check mode, you can use a boolean magic variable ``ansible_check_mode``, which is set to ``True`` when Ansible runs in check mode. For example:" msgstr "Ansible ã‚’ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã§å®Ÿè¡Œã™ã‚‹éš›ã«ã€ã‚¿ã‚¹ã‚¯ã‚’スã‚ップã—ãŸã‚Šã€ã‚¿ã‚¹ã‚¯ã®ã‚¨ãƒ©ãƒ¼ã‚’無視ã—ãŸã‚Šã™ã‚‹å ´åˆã¯ã€ãƒ–ール型ã®ãƒžã‚¸ãƒƒã‚¯å¤‰æ•° ``ansible_check_mode`` を使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã®å¤‰æ•°ã¯ã€Ansible ã‚’ãƒã‚§ãƒƒã‚¯ãƒ¢ãƒ¼ãƒ‰ã§å®Ÿè¡Œã™ã‚‹ã¨ã€``True`` ã«è¨å®šã•ã‚Œã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_checkmode.rst:74 +#: ../../rst/user_guide/playbooks_checkmode.rst:80 msgid "Using diff mode" msgstr "差分モードã®ä½¿ç”¨" -#: ../../rst/user_guide/playbooks_checkmode.rst:76 +#: ../../rst/user_guide/playbooks_checkmode.rst:82 msgid "The ``--diff`` option for ansible-playbook can be used alone or with ``--check``. When you run in diff mode, any module that supports diff mode reports the changes made or, if used with ``--check``, the changes that would have been made. Diff mode is most common in modules that manipulate files (for example, the template module) but other modules might also show 'before and after' information (for example, the user module)." msgstr "ansible-playbook ã® ``--diff`` オプションã¯ã€å˜ç‹¬ã§ã‚‚ ``--check`` ã¨ä½µç”¨ã—ã¦ã‚‚構ã„ã¾ã›ã‚“。差分モードã§å®Ÿè¡Œã™ã‚‹ã¨ã€å·®åˆ†ãƒ¢ãƒ¼ãƒ‰ã‚’サãƒãƒ¼ãƒˆã—ã¦ã„ã‚‹ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒã€è¡Œã‚ã‚ŒãŸå¤‰æ›´ã‚’å ±å‘Šã—ã¾ã™ (``--check`` ã¨ä½µç”¨ã™ã‚‹å ´åˆã¯ã€è¡Œã‚ã‚ŒãŸã§ã‚ã‚ã†å¤‰æ›´ã‚’å ±å‘Šã—ã¾ã™)。差分モードã¯ã€ãƒ•ã‚¡ã‚¤ãƒ«ã‚’æ“作ã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (template モジュールãªã©) ã§æœ€ã‚‚一般的ã§ã™ãŒã€ãã®ä»–ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã§ã‚‚「変更å‰ã¨å¤‰æ›´å¾Œã€ã®æƒ…å ±ã‚’è¡¨ç¤ºã™ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ (user モジュールãªã©)。" -#: ../../rst/user_guide/playbooks_checkmode.rst:78 -msgid "Diff mode produces a large amount of output, so it is best used when checking a single host at a time. For example::" +#: ../../rst/user_guide/playbooks_checkmode.rst:84 +msgid "Diff mode produces a large amount of output, so it is best used when checking a single host at a time. For example:" msgstr "差分モードã¯å¤§é‡ã®å‡ºåŠ›ã‚’生æˆã™ã‚‹ãŸã‚ã€ä¸€åº¦ã« 1 ã¤ã®ãƒ›ã‚¹ãƒˆã‚’確èªã™ã‚‹ã¨ãã«ä½¿ã†ã®ãŒæœ€é©ã§ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_checkmode.rst:85 +#: ../../rst/user_guide/playbooks_checkmode.rst:93 msgid "Enforcing or preventing diff mode on tasks" msgstr "タスクã§ã®å·®åˆ†ãƒ¢ãƒ¼ãƒ‰ã®å¼·åˆ¶ã¾ãŸã¯ç¦æ¢" -#: ../../rst/user_guide/playbooks_checkmode.rst:87 -msgid "Because the ``--diff`` option can reveal sensitive information, you can disable it for a task by specifying ``diff: no``. For example::" +#: ../../rst/user_guide/playbooks_checkmode.rst:95 +msgid "Because the ``--diff`` option can reveal sensitive information, you can disable it for a task by specifying ``diff: no``. For example:" msgstr "``--diff`` オプションã¯æ©Ÿå¯†æƒ…å ±ã‚’è¡¨ç¤ºã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚‹ãŸã‚ã€``diff: no`` を指定ã—ã¦ã‚¿ã‚¹ã‚¯ã«å¯¾ã—ã¦ã“れを無効ã«ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" #: ../../rst/user_guide/playbooks_conditionals.rst:5 @@ -4893,283 +4888,283 @@ msgid "You can perform cleanup tasks only when a filesystem is getting full." msgstr "ファイルシステムãŒæº€æ¯ã«ãªã£ãŸå ´åˆã«ã®ã¿ã€ã‚¯ãƒªãƒ¼ãƒ³ã‚¢ãƒƒãƒ—タスクを実行ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" #: ../../rst/user_guide/playbooks_conditionals.rst:45 -msgid "See :ref:`commonly_used_facts` for a list of facts that frequently appear in conditional statements. Not all facts exist for all hosts. For example, the 'lsb_major_release' fact used in an example below only exists when the lsb_release package is installed on the target host. To see what facts are available on your systems, add a debug task to your playbook::" +msgid "See :ref:`commonly_used_facts` for a list of facts that frequently appear in conditional statements. Not all facts exist for all hosts. For example, the 'lsb_major_release' fact used in an example below only exists when the lsb_release package is installed on the target host. To see what facts are available on your systems, add a debug task to your playbook:" msgstr "æ¡ä»¶æ–‡ã«é »ç¹ã«ç¾ã‚Œã‚‹ãƒ•ã‚¡ã‚¯ãƒˆã®ä¸€è¦§ã¯ã€:ref:`commonly_used_facts` ã‚’å‚ç…§ã—ã¦ãã ã•ã„。ã™ã¹ã¦ã®ãƒ•ã‚¡ã‚¯ãƒˆãŒã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã«å˜åœ¨ã™ã‚‹ã‚ã‘ã§ã¯ã‚ã‚Šã¾ã›ã‚“。ãŸã¨ãˆã°ã€ä»¥ä¸‹ã®ä¾‹ã§ä½¿ç”¨ã•ã‚Œã¦ã„る「lsb_major_releaseã€ãƒ•ã‚¡ã‚¯ãƒˆã¯ã€ã‚¿ãƒ¼ã‚²ãƒƒãƒˆãƒ›ã‚¹ãƒˆã« lsb_release パッケージãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹å ´åˆã«ã®ã¿å˜åœ¨ã—ã¾ã™ã€‚システム上ã§åˆ©ç”¨å¯èƒ½ãªãƒ•ã‚¡ã‚¯ãƒˆã‚’確èªã™ã‚‹ã«ã¯ã€Playbook ã«ãƒ‡ãƒãƒƒã‚°ã‚¿ã‚¹ã‚¯ã‚’è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:51 +#: ../../rst/user_guide/playbooks_conditionals.rst:53 msgid "Here is a sample conditional based on a fact:" msgstr "以下ã¯ã€ãƒ•ã‚¡ã‚¯ãƒˆã«åŸºã¥ãæ¡ä»¶åˆ†å²ã®ä¾‹ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:60 +#: ../../rst/user_guide/playbooks_conditionals.rst:62 msgid "If you have multiple conditions, you can group them with parentheses:" msgstr "複数ã®æ¡ä»¶ãŒã‚ã‚‹å ´åˆã¯ã€æ‹¬å¼§ã§ã‚°ãƒ«ãƒ¼ãƒ—化ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:70 -msgid "You can use `logical operators <https://jinja.palletsprojects.com/en/latest/templates/#logic>`_ to combine conditions. When you have multiple conditions that all need to be true (that is, a logical ``and``), you can specify them as a list::" +#: ../../rst/user_guide/playbooks_conditionals.rst:72 +msgid "You can use `logical operators <https://jinja.palletsprojects.com/en/latest/templates/#logic>`_ to combine conditions. When you have multiple conditions that all need to be true (that is, a logical ``and``), you can specify them as a list:" msgstr "`logical operators <https://jinja.palletsprojects.com/en/latest/templates/#logic>`_ を使用ã—ã¦æ¡ä»¶ã‚’組ã¿åˆã‚ã›ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã™ã¹ã¦ãŒ True ã§ã‚ã‚‹å¿…è¦ãŒã‚る複数ã®æ¡ä»¶ãŒã‚ã‚‹å ´åˆ (ã¤ã¾ã‚Šã€è«–ç†çš„㪠``and``)ã€ãれらをリストã¨ã—ã¦æŒ‡å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:79 -msgid "If a fact or variable is a string, and you need to run a mathematical comparison on it, use a filter to ensure that Ansible reads the value as an integer::" +#: ../../rst/user_guide/playbooks_conditionals.rst:83 +msgid "If a fact or variable is a string, and you need to run a mathematical comparison on it, use a filter to ensure that Ansible reads the value as an integer:" msgstr "ファクトã¾ãŸã¯å¤‰æ•°ãŒæ–‡å—列ã§ã€ãã‚Œã«å¯¾ã—ã¦æ•°å¦æ¯”較を実行ã™ã‚‹å¿…è¦ãŒã‚ã‚‹å ´åˆã¯ã€ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã‚’使用ã—㦠Ansible ãŒå€¤ã‚’æ•´æ•°ã¨ã—ã¦èªã¿å–るよã†ã«ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:88 +#: ../../rst/user_guide/playbooks_conditionals.rst:94 msgid "Conditions based on registered variables" msgstr "登録済ã¿ã®å¤‰æ•°ã«åŸºã¥ãæ¡ä»¶" -#: ../../rst/user_guide/playbooks_conditionals.rst:90 +#: ../../rst/user_guide/playbooks_conditionals.rst:96 msgid "Often in a playbook you want to execute or skip a task based on the outcome of an earlier task. For example, you might want to configure a service after it is upgraded by an earlier task. To create a conditional based on a registered variable:" msgstr "Playbook ã§ã¯ã€ä»¥å‰ã®ã‚¿ã‚¹ã‚¯ã®çµæžœã«åŸºã¥ã„ã¦ã‚¿ã‚¹ã‚¯ã‚’実行ã¾ãŸã¯ã‚¹ã‚ップã—ãŸã„å ´åˆãŒã‚ˆãã‚ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€ä»¥å‰ã®ã‚¿ã‚¹ã‚¯ã«ã‚ˆã£ã¦ã‚µãƒ¼ãƒ“スãŒã‚¢ãƒƒãƒ—グレードã•ã‚ŒãŸå¾Œã«ã€ãã®ã‚µãƒ¼ãƒ“スをè¨å®šã—ãŸã„å ´åˆãªã©ã§ã™ã€‚登録ã•ã‚ŒãŸå¤‰æ•°ã«åŸºã¥ã„ã¦æ¡ä»¶åˆ†å²ã‚’作æˆã™ã‚‹ã«ã¯ã€æ¬¡ã®ã‚ˆã†ã«ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:92 +#: ../../rst/user_guide/playbooks_conditionals.rst:98 msgid "Register the outcome of the earlier task as a variable." msgstr "以å‰ã®ã‚¿ã‚¹ã‚¯ã®çµæžœã‚’変数ã¨ã—ã¦ç™»éŒ²ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:93 +#: ../../rst/user_guide/playbooks_conditionals.rst:99 msgid "Create a conditional test based on the registered variable." msgstr "登録ã—ãŸå¤‰æ•°ã«åŸºã¥ã„ã¦æ¡ä»¶åˆ†å²ãƒ†ã‚¹ãƒˆã‚’作æˆã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:95 -msgid "You create the name of the registered variable using the ``register`` keyword. A registered variable always contains the status of the task that created it as well as any output that task generated. You can use registered variables in templates and action lines as well as in conditional ``when`` statements. You can access the string contents of the registered variable using ``variable.stdout``. For example::" +#: ../../rst/user_guide/playbooks_conditionals.rst:101 +msgid "You create the name of the registered variable using the ``register`` keyword. A registered variable always contains the status of the task that created it as well as any output that task generated. You can use registered variables in templates and action lines as well as in conditional ``when`` statements. You can access the string contents of the registered variable using ``variable.stdout``. For example:" msgstr "登録ã•ã‚ŒãŸå¤‰æ•°ã®åå‰ã¯ã€``register`` ã‚ーワードを使用ã—ã¦ä½œæˆã—ã¾ã™ã€‚登録ã•ã‚ŒãŸå¤‰æ•°ã«ã¯ã€ãã®ã‚ーワードを作æˆã—ãŸã‚¿ã‚¹ã‚¯ã®ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã¨ã€ãã®ã‚¿ã‚¹ã‚¯ãŒç”Ÿæˆã—ãŸå‡ºåŠ›ãŒå¸¸ã«å«ã¾ã‚Œã¦ã„ã¾ã™ã€‚登録ã•ã‚ŒãŸå¤‰æ•°ã¯ã€ãƒ†ãƒ³ãƒ—レートやアクション行ã€ãŠã‚ˆã³æ¡ä»¶ä»˜ãã® ``when`` æ–‡ã§ä½¿ç”¨ã§ãã¾ã™ã€‚登録ã•ã‚ŒãŸå¤‰æ•°ã®æ–‡å—列内容ã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ã«ã¯ã€``variable.stdout`` を使用ã—ã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:110 -msgid "You can use registered results in the loop of a task if the variable is a list. If the variable is not a list, you can convert it into a list, with either ``stdout_lines`` or with ``variable.stdout.split()``. You can also split the lines by other fields::" +#: ../../rst/user_guide/playbooks_conditionals.rst:118 +msgid "You can use registered results in the loop of a task if the variable is a list. If the variable is not a list, you can convert it into a list, with either ``stdout_lines`` or with ``variable.stdout.split()``. You can also split the lines by other fields:" msgstr "登録ã•ã‚ŒãŸçµæžœã¯ã€å¤‰æ•°ãŒãƒªã‚¹ãƒˆã®å ´åˆã€ã‚¿ã‚¹ã‚¯ã®ãƒ«ãƒ¼ãƒ—内ã§ä½¿ç”¨ã§ãã¾ã™ã€‚変数ãŒãƒªã‚¹ãƒˆã§ãªã„å ´åˆã¯ã€``stdout_lines`` ã¾ãŸã¯ ``variable.stdout.split()`` ã§ãƒªã‚¹ãƒˆã«å¤‰æ›ã§ãã¾ã™ã€‚ã¾ãŸã€ä»–ã®ãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ã§è¡Œã‚’分割ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:128 +#: ../../rst/user_guide/playbooks_conditionals.rst:138 msgid "The string content of a registered variable can be empty. If you want to run another task only on hosts where the stdout of your registered variable is empty, check the registered variable's string contents for emptiness:" msgstr "登録ã•ã‚ŒãŸå¤‰æ•°ã®æ–‡å—列内容ã¯ç©ºã«ãªã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚登録ã•ã‚ŒãŸå¤‰æ•°ã®æ¨™æº–出力ãŒç©ºã®ãƒ›ã‚¹ãƒˆã§ã®ã¿åˆ¥ã®ã‚¿ã‚¹ã‚¯ã‚’実行ã—ãŸã„å ´åˆã¯ã€ç™»éŒ²ã•ã‚ŒãŸå¤‰æ•°ã®æ–‡å—列内容ãŒç©ºã§ã‚ã‚‹ã‹ã©ã†ã‹ã‚’ãƒã‚§ãƒƒã‚¯ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:146 +#: ../../rst/user_guide/playbooks_conditionals.rst:156 msgid "Ansible always registers something in a registered variable for every host, even on hosts where a task fails or Ansible skips a task because a condition is not met. To run a follow-up task on these hosts, query the registered variable for ``is skipped`` (not for \"undefined\" or \"default\"). See :ref:`registered_variables` for more information. Here are sample conditionals based on the success or failure of a task. Remember to ignore errors if you want Ansible to continue executing on a host when a failure occurs:" msgstr "タスクãŒå¤±æ•—ã—ãŸãƒ›ã‚¹ãƒˆã‚„ã€æ¡ä»¶ãŒæº€ãŸã•ã‚Œãšã« Ansible ãŒã‚¿ã‚¹ã‚¯ã‚’スã‚ップã—ãŸãƒ›ã‚¹ãƒˆã§ã‚ã£ã¦ã‚‚ã€Ansible ã¯å¸¸ã«ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã®ç™»éŒ²å¤‰æ•°ã«ä½•ã‹ã‚’登録ã—ã¾ã™ã€‚ã“れらã®ãƒ›ã‚¹ãƒˆã§ãƒ•ã‚©ãƒãƒ¼ã‚¢ãƒƒãƒ—タスクを実行ã™ã‚‹ã«ã¯ã€ç™»éŒ²æ¸ˆã¿ã®å¤‰æ•°ã« ``is skipped`` を照会ã—ã¾ã™ (「undefinedã€ã‚„「defaultã€ã§ã¯ã‚ã‚Šã¾ã›ã‚“)。詳細ã¯ã€ã€Œ:ref:`registered_variables`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。以下ã¯ã€ã‚¿ã‚¹ã‚¯ã®æˆåŠŸã¾ãŸã¯å¤±æ•—ã«åŸºã¥ãæ¡ä»¶åˆ†å²ã®ã‚µãƒ³ãƒ—ルã§ã™ã€‚失敗ã—ãŸã¨ãã«ãƒ›ã‚¹ãƒˆä¸Šã§ Ansible ã®å®Ÿè¡Œã‚’継続ã•ã›ãŸã„å ´åˆã¯ã€ã‚¨ãƒ©ãƒ¼ã‚’無視ã™ã‚‹ã“ã¨ã‚’忘れãªã„ã§ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_conditionals.rst:168 +#: ../../rst/user_guide/playbooks_conditionals.rst:178 msgid "Older versions of Ansible used ``success`` and ``fail``, but ``succeeded`` and ``failed`` use the correct tense. All of these options are now valid." msgstr "å¤ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Ansible ã§ã¯ã€``success`` ãŠã‚ˆã³ ``fail`` ãŒä½¿ç”¨ã•ã‚Œã¦ã„ã¾ã—ãŸãŒã€``succeeded`` ãŠã‚ˆã³ ``failed`` ã¯æ£ã—ã„時制を使用ã—ã¾ã™ã€‚ã“ã®ã‚ªãƒ—ションã¯ã™ã¹ã¦æœ‰åŠ¹ã«ãªã‚Šã¾ã—ãŸã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:172 +#: ../../rst/user_guide/playbooks_conditionals.rst:182 msgid "Conditionals based on variables" msgstr "変数ã«åŸºã¥ãæ¡ä»¶åˆ†å²" -#: ../../rst/user_guide/playbooks_conditionals.rst:174 +#: ../../rst/user_guide/playbooks_conditionals.rst:184 msgid "You can also create conditionals based on variables defined in the playbooks or inventory. Because conditionals require boolean input (a test must evaluate as True to trigger the condition), you must apply the ``| bool`` filter to non boolean variables, such as string variables with content like 'yes', 'on', '1', or 'true'. You can define variables like this:" msgstr "ã¾ãŸã€Playbook やインベントリーã§å®šç¾©ã•ã‚ŒãŸå¤‰æ•°ã«åŸºã¥ã„ã¦ã€æ¡ä»¶åˆ†å²ã‚’作æˆã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚æ¡ä»¶åˆ†å²ã«ã¯ãƒ–ール値ã®å…¥åŠ›ãŒå¿…è¦ãªãŸã‚ (æ¡ä»¶ã‚’æˆç«‹ã•ã›ã‚‹ãŸã‚ã«ã¯ã€ãƒ†ã‚¹ãƒˆãŒ True ã¨è©•ä¾¡ã•ã‚Œãªã‘ã‚Œã°ãªã‚Šã¾ã›ã‚“)ã€ã€Œyesã€ã€ã€Œonã€ã€ã€Œ1ã€ã€ã€Œtrueã€ãªã©ã®å†…容をæŒã¤æ–‡å—列変数ãªã©ã€ãƒ–ール値以外ã®å¤‰æ•°ã«ã¯ã€``| bool`` フィルターをé©ç”¨ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚変数ã¯æ¬¡ã®ã‚ˆã†ã«å®šç¾©ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:182 +#: ../../rst/user_guide/playbooks_conditionals.rst:192 msgid "With the variables above, Ansible would run one of these tasks and skip the other:" msgstr "上記ã®å¤‰æ•°ã‚’使用ã™ã‚‹ã¨ã€Ansible ã¯ã“れらã®ã‚¿ã‚¹ã‚¯ã®ã„ãšã‚Œã‹ã‚’実行ã—ã€ä»–ã®ã‚¿ã‚¹ã‚¯ã‚’çœç•¥ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:195 +#: ../../rst/user_guide/playbooks_conditionals.rst:205 msgid "If a required variable has not been set, you can skip or fail using Jinja2's `defined` test. For example:" msgstr "å¿…è¦ãªå¤‰æ•°ãŒè¨å®šã•ã‚Œã¦ã„ãªã„å ´åˆã¯ã€çœç•¥ã™ã‚‹ã‹ã€Jinja2 ã® `定義済ã¿` テストを使用ã—ã¦å¤±æ•—ã—ã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:208 +#: ../../rst/user_guide/playbooks_conditionals.rst:218 msgid "This is especially useful in combination with the conditional import of vars files (see below). As the examples show, you do not need to use `{{ }}` to use variables inside conditionals, as these are already implied." msgstr "ã“ã‚Œã¯ã€å¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«ã®æ¡ä»¶åˆ†å²ã‚¤ãƒ³ãƒãƒ¼ãƒˆã¨ã®çµ„ã¿åˆã‚ã›ã§ç‰¹ã«æœ‰åŠ¹ã§ã™ (以下å‚ç…§)。ã“れらã®ä¾‹ãŒç¤ºã™ã‚ˆã†ã«ã€æ¡ä»¶åˆ†å²ã®ä¸ã§å¤‰æ•°ã‚’使用ã™ã‚‹ãŸã‚ã« `{{ }}` を使用ã™ã‚‹å¿…è¦ã¯ã‚ã‚Šã¾ã›ã‚“。ãれらã¯ã™ã§ã«æš—示ã•ã‚Œã¦ã„ã‚‹ãŸã‚ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:214 +#: ../../rst/user_guide/playbooks_conditionals.rst:224 msgid "Using conditionals in loops" msgstr "ループã§ã®æ¡ä»¶åˆ†å²ã®ä½¿ç”¨" -#: ../../rst/user_guide/playbooks_conditionals.rst:216 +#: ../../rst/user_guide/playbooks_conditionals.rst:226 msgid "If you combine a ``when`` statement with a :ref:`loop <playbooks_loops>`, Ansible processes the condition separately for each item. This is by design, so you can execute the task on some items in the loop and skip it on other items. For example:" msgstr "``when`` 文㨠:ref:`loop <playbooks_loops>` を組ã¿åˆã‚ã›ãŸå ´åˆã€Ansible ã¯å„アイテムã«å¯¾ã—ã¦å€‹åˆ¥ã«æ¡ä»¶ã‚’処ç†ã—ã¾ã™ã€‚ã“ã‚Œã¯æ„図的ãªã‚‚ã®ã§ã€ãƒ«ãƒ¼ãƒ—内ã®ä¸€éƒ¨ã®ã‚¢ã‚¤ãƒ†ãƒ ã§ã‚¿ã‚¹ã‚¯ã‚’実行ã—ã€ä»–ã®ã‚¢ã‚¤ãƒ†ãƒ ã§ã¯ã‚¹ã‚ップã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:226 +#: ../../rst/user_guide/playbooks_conditionals.rst:236 msgid "If you need to skip the whole task when the loop variable is undefined, use the `|default` filter to provide an empty iterator. For example, when looping over a list:" msgstr "ループ変数ãŒæœªå®šç¾©ã®ã¨ãã«ã‚¿ã‚¹ã‚¯å…¨ä½“ã‚’çœç•¥ã™ã‚‹å¿…è¦ãŒã‚ã‚‹å ´åˆã¯ã€`|default` フィルターを使用ã—ã¦ç©ºã®ã‚¤ãƒ†ãƒ¬ãƒ¼ã‚¿ãƒ¼ã‚’指定ã—ã¾ã™ã€‚ãŸã¨ãˆã°ã€ãƒªã‚¹ãƒˆã‚’ループã™ã‚‹å ´åˆã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:235 +#: ../../rst/user_guide/playbooks_conditionals.rst:245 msgid "You can do the same thing when looping over a dict:" msgstr "åŒã˜ã“ã¨ãŒã€ãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼ã‚’ループã™ã‚‹ã¨ãã«ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:247 +#: ../../rst/user_guide/playbooks_conditionals.rst:257 msgid "Loading custom facts" msgstr "カスタムファクトã®èªã¿è¾¼ã¿ä¸" -#: ../../rst/user_guide/playbooks_conditionals.rst:249 +#: ../../rst/user_guide/playbooks_conditionals.rst:259 msgid "You can provide your own facts, as described in :ref:`developing_modules`. To run them, just make a call to your own custom fact gathering module at the top of your list of tasks, and variables returned there will be accessible to future tasks:" msgstr ":ref:`developing_modules` ã§èª¬æ˜Žã—ã¦ã„るよã†ã«ã€ç‹¬è‡ªã®ãƒ•ã‚¡ã‚¯ãƒˆã‚’æä¾›ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãれらを実行ã™ã‚‹ã«ã¯ã€ã‚¿ã‚¹ã‚¯ãƒªã‚¹ãƒˆã®å…ˆé ã«ã‚る独自ã®ã‚«ã‚¹ã‚¿ãƒ ファクトåŽé›†ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’呼ã³å‡ºã™ã ã‘ã§ã€ãã“ã‹ã‚‰è¿”ã•ã‚ŒãŸå¤‰æ•°ã¯å°†æ¥ã®ã‚¿ã‚¹ã‚¯ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãるよã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:264 +#: ../../rst/user_guide/playbooks_conditionals.rst:274 msgid "Conditionals with re-use" msgstr "å†åˆ©ç”¨ã«ã‚ˆã‚‹æ¡ä»¶åˆ†å²" -#: ../../rst/user_guide/playbooks_conditionals.rst:266 +#: ../../rst/user_guide/playbooks_conditionals.rst:276 msgid "You can use conditionals with re-usable tasks files, playbooks, or roles. Ansible executes these conditional statements differently for dynamic re-use (includes) and for static re-use (imports). See :ref:`playbooks_reuse` for more information on re-use in Ansible." msgstr "æ¡ä»¶åˆ†å²ã¯ã€å†åˆ©ç”¨å¯èƒ½ãªã‚¿ã‚¹ã‚¯ãƒ•ã‚¡ã‚¤ãƒ«ã€Playbookã€ã¾ãŸã¯ãƒãƒ¼ãƒ«ã§ä½¿ç”¨ã§ãã¾ã™ã€‚Ansible ã¯ã“れらã®æ¡ä»¶æ–‡ã‚’ã€å‹•çš„å†åˆ©ç”¨ (インクルード) ãŠã‚ˆã³é™çš„å†åˆ©ç”¨ (インãƒãƒ¼ãƒˆ) ã§ç•°ãªã‚‹æ–¹æ³•ã§å®Ÿè¡Œã—ã¾ã™ã€‚Ansible ã§ã®å†åˆ©ç”¨ã®è©³ç´°ã¯ã€ã€Œ:ref:`playbooks_reuse`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_conditionals.rst:271 +#: ../../rst/user_guide/playbooks_conditionals.rst:281 msgid "Conditionals with imports" msgstr "インãƒãƒ¼ãƒˆã®ã‚ã‚‹æ¡ä»¶åˆ†å²" -#: ../../rst/user_guide/playbooks_conditionals.rst:273 -msgid "When you add a conditional to an import statement, Ansible applies the condition to all tasks within the imported file. This behavior is the equivalent of :ref:`tag_inheritance`. Ansible applies the condition to every task, and evaluates each task separately. For example, you might have a playbook called ``main.yml`` and a tasks file called ``other_tasks.yml``::" +#: ../../rst/user_guide/playbooks_conditionals.rst:283 +msgid "When you add a conditional to an import statement, Ansible applies the condition to all tasks within the imported file. This behavior is the equivalent of :ref:`tag_inheritance`. Ansible applies the condition to every task, and evaluates each task separately. For example, you might have a playbook called ``main.yml`` and a tasks file called ``other_tasks.yml``:" msgstr "インãƒãƒ¼ãƒˆã‚¹ãƒ†ãƒ¼ãƒˆãƒ¡ãƒ³ãƒˆã«æ¡ä»¶åˆ†å²ã‚’è¿½åŠ ã™ã‚‹ã¨ã€Ansible ã¯ã‚¤ãƒ³ãƒãƒ¼ãƒˆã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«å†…ã®ã™ã¹ã¦ã®ã‚¿ã‚¹ã‚¯ã«ãã®æ¡ä»¶ã‚’é©ç”¨ã—ã¾ã™ã€‚ã“ã®å‹•ä½œã¯ã€:ref:`tag_inheritance` ã¨åŒç‰ã§ã™ã€‚Ansible ã¯ã€ã™ã¹ã¦ã®ã‚¿ã‚¹ã‚¯ã«æ¡ä»¶ã‚’é©ç”¨ã—ã€å„タスクを個別ã«è©•ä¾¡ã—ã¾ã™ã€‚ãŸã¨ãˆã°ã€``main.yml`` ã¨ã„ㆠPlaybookã¨ã€``other_tasks.yml`` ã¨ã„ã†ã‚¿ã‚¹ã‚¯ãƒ•ã‚¡ã‚¤ãƒ«ãŒã‚ã‚‹ã¨ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:289 -#: ../../rst/user_guide/playbooks_conditionals.rst:329 -msgid "Ansible expands this at execution time to the equivalent of::" +#: ../../rst/user_guide/playbooks_conditionals.rst:301 +#: ../../rst/user_guide/playbooks_conditionals.rst:345 +msgid "Ansible expands this at execution time to the equivalent of:" msgstr "Ansible ã¯ã€å®Ÿè¡Œæ™‚ã«ã“れを以下ã«ç›¸å½“ã™ã‚‹ã‚‚ã®ã«æ‹¡å¼µã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:303 +#: ../../rst/user_guide/playbooks_conditionals.rst:317 msgid "Thus if ``x`` is initially undefined, the ``debug`` task will be skipped. If this is not the behavior you want, use an ``include_*`` statement to apply a condition only to that statement itself." msgstr "ã—ãŸãŒã£ã¦ã€``x`` ãŒæœ€åˆã«æœªå®šç¾©ã§ã‚ã‚Œã°ã€``debug`` ã®ã‚¿ã‚¹ã‚¯ã¯ã‚¹ã‚ップã•ã‚Œã¾ã™ã€‚ã“ã®ã‚ˆã†ãªå‹•ä½œã‚’望ã¾ãªã„å ´åˆã¯ã€``include_*`` 文を使用ã—ã¦ã€ãã®æ–‡è‡ªä½“ã«ã®ã¿æ¡ä»¶ã‚’é©ç”¨ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:305 +#: ../../rst/user_guide/playbooks_conditionals.rst:319 msgid "You can apply conditions to ``import_playbook`` as well as to the other ``import_*`` statements. When you use this approach, Ansible returns a 'skipped' message for every task on every host that does not match the criteria, creating repetitive output. In many cases the :ref:`group_by module <group_by_module>` can be a more streamlined way to accomplish the same objective; see :ref:`os_variance`." msgstr "``import_playbook`` ã«ã¯ã€ä»–ã® ``import_*`` æ–‡ã¨åŒæ§˜ã«æ¡ä»¶ã‚’é©ç”¨ã§ãã¾ã™ã€‚ã“ã®æ–¹æ³•ã‚’使用ã™ã‚‹ã¨ã€Ansible ã¯åŸºæº–ã«ä¸€è‡´ã—ãªã„ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆä¸Šã®ã™ã¹ã¦ã®ã‚¿ã‚¹ã‚¯ã«å¯¾ã—ã¦ã€Œskippedã€ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã‚’è¿”ã—ã€å復的ãªå‡ºåŠ›ã‚’作æˆã—ã¾ã™ã€‚多ãã®å ´åˆã€:ref:`group_by モジュール <group_by_module>` ã¯ã€åŒã˜ç›®çš„ã‚’é”æˆã™ã‚‹ãŸã‚ã®ã‚ˆã‚Šåˆç†çš„ãªæ–¹æ³•ã¨ãªã‚Šã¾ã™ã€‚「:ref:`os_variance`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_conditionals.rst:310 +#: ../../rst/user_guide/playbooks_conditionals.rst:324 msgid "Conditionals with includes" msgstr "includes ã‚’æŒã¤æ¡ä»¶åˆ†å²" -#: ../../rst/user_guide/playbooks_conditionals.rst:312 -msgid "When you use a conditional on an ``include_*`` statement, the condition is applied only to the include task itself and not to any other tasks within the included file(s). To contrast with the example used for conditionals on imports above, look at the same playbook and tasks file, but using an include instead of an import::" +#: ../../rst/user_guide/playbooks_conditionals.rst:326 +msgid "When you use a conditional on an ``include_*`` statement, the condition is applied only to the include task itself and not to any other tasks within the included file(s). To contrast with the example used for conditionals on imports above, look at the same playbook and tasks file, but using an include instead of an import:" msgstr "``include_*`` æ–‡ã«æ¡ä»¶åˆ†å²ã‚’使用ã™ã‚‹ã¨ã€ãã®æ¡ä»¶ã¯ã‚¤ãƒ³ã‚¯ãƒ«ãƒ¼ãƒ‰ã‚¿ã‚¹ã‚¯è‡ªä½“ã«ã®ã¿é©ç”¨ã•ã‚Œã€ã‚¤ãƒ³ã‚¯ãƒ«ãƒ¼ãƒ‰ãƒ•ã‚¡ã‚¤ãƒ«å†…ã®ä»–ã®ã‚¿ã‚¹ã‚¯ã«ã¯é©ç”¨ã•ã‚Œã¾ã›ã‚“。上記ã®ã‚¤ãƒ³ãƒãƒ¼ãƒˆã«å¯¾ã™ã‚‹æ¡ä»¶åˆ†å²ã®ä¾‹ã¨å¯¾æ¯”ã™ã‚‹ãŸã‚ã«ã€åŒã˜ Playbook ã¨ã‚¿ã‚¹ã‚¯ãƒ•ã‚¡ã‚¤ãƒ«ã‚’見ã¦ãã ã•ã„。ãŸã ã—ã€ã‚¤ãƒ³ãƒãƒ¼ãƒˆã®ä»£ã‚ã‚Šã«ã‚¤ãƒ³ã‚¯ãƒ«ãƒ¼ãƒ‰ã‚’使用ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:347 +#: ../../rst/user_guide/playbooks_conditionals.rst:365 msgid "By using ``include_tasks`` instead of ``import_tasks``, both tasks from ``other_tasks.yml`` will be executed as expected. For more information on the differences between ``include`` v ``import`` see :ref:`playbooks_reuse`." msgstr "``import_tasks`` ã®ä»£ã‚ã‚Šã« ``include_tasks`` を使用ã™ã‚‹ã¨ã€``other_tasks.yml`` ã‹ã‚‰ã®ä¸¡æ–¹ã®ã‚¿ã‚¹ã‚¯ãŒæƒ³å®šã©ãŠã‚Šã«å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚``include`` 㨠``import`` ã®ç›¸é•ç‚¹ã¯ã€ã€Œ:ref:`playbooks_reuse`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_conditionals.rst:350 +#: ../../rst/user_guide/playbooks_conditionals.rst:368 msgid "Conditionals with roles" msgstr "ãƒãƒ¼ãƒ«ã‚’å«ã‚€æ¡ä»¶åˆ†å²" -#: ../../rst/user_guide/playbooks_conditionals.rst:352 +#: ../../rst/user_guide/playbooks_conditionals.rst:370 msgid "There are three ways to apply conditions to roles:" msgstr "状態をãƒãƒ¼ãƒ«ã«é©ç”¨ã™ã‚‹æ–¹æ³•ã¯ 3 ã¤ã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:354 +#: ../../rst/user_guide/playbooks_conditionals.rst:372 msgid "Add the same condition or conditions to all tasks in the role by placing your ``when`` statement under the ``roles`` keyword. See the example in this section." msgstr "``when`` 文を ``roles`` ã‚ーワードã®ä¸‹ã«ç½®ãã“ã¨ã§ã€ãƒãƒ¼ãƒ«å†…ã®ã™ã¹ã¦ã®ã‚¿ã‚¹ã‚¯ã«åŒã˜æ¡ä»¶ã‚’è¿½åŠ ã—ã¾ã™ã€‚ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã®ä¾‹ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_conditionals.rst:355 +#: ../../rst/user_guide/playbooks_conditionals.rst:373 msgid "Add the same condition or conditions to all tasks in the role by placing your ``when`` statement on a static ``import_role`` in your playbook." msgstr "Playbook ã®é™çš„ ``import_role`` ã« ``when`` 文をé…ç½®ã—ã¦ã€ãƒãƒ¼ãƒ«å†…ã®ã™ã¹ã¦ã®ã‚¿ã‚¹ã‚¯ã«åŒã˜æ¡ä»¶ã‚’è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:356 +#: ../../rst/user_guide/playbooks_conditionals.rst:374 msgid "Add a condition or conditions to individual tasks or blocks within the role itself. This is the only approach that allows you to select or skip some tasks within the role based on your ``when`` statement. To select or skip tasks within the role, you must have conditions set on individual tasks or blocks, use the dynamic ``include_role`` in your playbook, and add the condition or conditions to the include. When you use this approach, Ansible applies the condition to the include itself plus any tasks in the role that also have that ``when`` statement." msgstr "ãƒãƒ¼ãƒ«è‡ªä½“ã®ä¸ã®å€‹ã€…ã®ã‚¿ã‚¹ã‚¯ã¾ãŸã¯ãƒ–ãƒãƒƒã‚¯ã«æ¡ä»¶ã‚’è¿½åŠ ã—ã¾ã™ã€‚ã“ã‚Œã¯ã€``when`` æ–‡ã«åŸºã¥ã„ã¦ãƒãƒ¼ãƒ«å†…ã®ä¸€éƒ¨ã®ã‚¿ã‚¹ã‚¯ã‚’é¸æŠžã¾ãŸã¯ã‚¹ã‚ップã™ã‚‹ã“ã¨ãŒã§ãる唯一ã®æ–¹æ³•ã§ã™ã€‚ãƒãƒ¼ãƒ«å†…ã®ã‚¿ã‚¹ã‚¯ã‚’é¸æŠžã¾ãŸã¯ã‚¹ã‚ップã™ã‚‹ã«ã¯ã€å€‹ã€…ã®ã‚¿ã‚¹ã‚¯ã¾ãŸã¯ãƒ–ãƒãƒƒã‚¯ã«æ¡ä»¶ã‚’è¨å®šã—ã€Playbook ã§å‹•çš„ ``include_role`` を使用ã—ã€æ¡ä»¶ã‚’インクルードã«è¿½åŠ ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®æ–¹æ³•ã‚’使用ã™ã‚‹ã¨ã€Ansible ã¯æ¡ä»¶ã‚’インクルード自体ã«åŠ ãˆã¦ã€``when`` ã®æ–‡ã‚’æŒã¤ãƒãƒ¼ãƒ«å†…ã®ã™ã¹ã¦ã®ã‚¿ã‚¹ã‚¯ã«é©ç”¨ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:358 +#: ../../rst/user_guide/playbooks_conditionals.rst:376 msgid "When you incorporate a role in your playbook statically with the ``roles`` keyword, Ansible adds the conditions you define to all the tasks in the role. For example:" msgstr "``roles`` ã‚ーワードを使用ã—㦠Playbook ã«ãƒãƒ¼ãƒ«ã‚’é™çš„ã«çµ„ã¿è¾¼ã‚€ã¨ã€Ansible ã¯å®šç¾©ã—ãŸæ¡ä»¶ã‚’ãƒãƒ¼ãƒ«å†…ã®ã™ã¹ã¦ã®ã‚¿ã‚¹ã‚¯ã«è¿½åŠ ã—ã¾ã™ã€‚ãŸã¨ãˆã°ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:370 +#: ../../rst/user_guide/playbooks_conditionals.rst:388 msgid "Selecting variables, files, or templates based on facts" msgstr "ファクトã«åŸºã¥ã„ãŸå¤‰æ•°ã€ãƒ•ã‚¡ã‚¤ãƒ«ã€ã¾ãŸã¯ãƒ†ãƒ³ãƒ—レートã®é¸æŠž" -#: ../../rst/user_guide/playbooks_conditionals.rst:372 +#: ../../rst/user_guide/playbooks_conditionals.rst:390 msgid "Sometimes the facts about a host determine the values you want to use for certain variables or even the file or template you want to select for that host. For example, the names of packages are different on CentOS and on Debian. The configuration files for common services are also different on different OS flavors and versions. To load different variables file, templates, or other files based on a fact about the hosts:" msgstr "ホストã«é–¢ã™ã‚‹ãƒ•ã‚¡ã‚¯ãƒˆã«ã‚ˆã£ã¦ã€ç‰¹å®šã®å¤‰æ•°ã«ä½¿ç”¨ã™ã‚‹å€¤ã‚„ã€ãã®ãƒ›ã‚¹ãƒˆç”¨ã«é¸æŠžã™ã‚‹ãƒ•ã‚¡ã‚¤ãƒ«ã‚„テンプレートãŒæ±ºå®šã™ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€ãƒ‘ッケージã®åå‰ã¯ CentOS 㨠Debian ã§ã¯ç•°ãªã‚Šã¾ã™ã€‚ã¾ãŸã€ä¸€èˆ¬çš„ãªã‚µãƒ¼ãƒ“スã®è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã‚‚ã€OS ã®ãƒ•ãƒ¬ãƒ¼ãƒãƒ¼ã‚„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã”ã¨ã«ç•°ãªã‚Šã¾ã™ã€‚ホストã«é–¢ã™ã‚‹ãƒ•ã‚¡ã‚¯ãƒˆã«åŸºã¥ã„ã¦ã€ç•°ãªã‚‹å¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«ã‚„テンプレートãªã©ã‚’èªã¿è¾¼ã‚€ã«ã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:374 +#: ../../rst/user_guide/playbooks_conditionals.rst:392 msgid "name your vars files, templates, or files to match the Ansible fact that differentiates them" msgstr "変数ファイルã€ãƒ†ãƒ³ãƒ—レートã€ã¾ãŸã¯ãƒ•ã‚¡ã‚¤ãƒ«ã‚’区別ã™ã‚‹ Ansible ファクトã«åˆã‚ã›ã¦åå‰ã‚’付ã‘ã‚‹" -#: ../../rst/user_guide/playbooks_conditionals.rst:376 +#: ../../rst/user_guide/playbooks_conditionals.rst:394 msgid "select the correct vars file, template, or file for each host with a variable based on that Ansible fact" msgstr "Ansible ファクトã«åŸºã¥ã„ã¦å¤‰æ•°ã‚’使用ã—ã¦ã€å„ホストã®æ£ã—ã„変数ファイルã€ãƒ†ãƒ³ãƒ—レートã€ã¾ãŸã¯ãƒ•ã‚¡ã‚¤ãƒ«ã‚’é¸æŠžã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:378 +#: ../../rst/user_guide/playbooks_conditionals.rst:396 msgid "Ansible separates variables from tasks, keeping your playbooks from turning into arbitrary code with nested conditionals. This approach results in more streamlined and auditable configuration rules because there are fewer decision points to track." msgstr "Ansible ã¯ã€å¤‰æ•°ã¨ã‚¿ã‚¹ã‚¯ã‚’分離ã™ã‚‹ã“ã¨ã§ã€Playbook ãŒãƒã‚¹ãƒˆã•ã‚ŒãŸæ¡ä»¶åˆ†å²ã«ã‚ˆã‚‹ä»»æ„ã®ã‚³ãƒ¼ãƒ‰ã«ãªã‚‰ãªã„よã†ã«ã—ã¦ã„ã¾ã™ã€‚ã“ã®ã‚¢ãƒ—ãƒãƒ¼ãƒã§ã¯ã€è¿½è·¡ã™ã¹ã決定ãƒã‚¤ãƒ³ãƒˆãŒå°‘ãªããªã‚‹ãŸã‚ã€ã‚ˆã‚Šåˆç†çš„ã§ç›£æŸ»å¯èƒ½ãªè¨å®šãƒ«ãƒ¼ãƒ«ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:381 +#: ../../rst/user_guide/playbooks_conditionals.rst:399 msgid "Selecting variables files based on facts" msgstr "ファクトã«åŸºã¥ã変数ファイルã®é¸æŠž" -#: ../../rst/user_guide/playbooks_conditionals.rst:383 -msgid "You can create a playbook that works on multiple platforms and OS versions with a minimum of syntax by placing your variable values in vars files and conditionally importing them. If you want to install Apache on some CentOS and some Debian servers, create variables files with YAML keys and values. For example::" +#: ../../rst/user_guide/playbooks_conditionals.rst:401 +msgid "You can create a playbook that works on multiple platforms and OS versions with a minimum of syntax by placing your variable values in vars files and conditionally importing them. If you want to install Apache on some CentOS and some Debian servers, create variables files with YAML keys and values. For example:" msgstr "変数ã®å€¤ã‚’ vars ファイルã«ç½®ãã€æ¡ä»¶ä»˜ãã§ã‚¤ãƒ³ãƒãƒ¼ãƒˆã™ã‚‹ã“ã¨ã§ã€æœ€å°é™ã®æ§‹æ–‡ã§è¤‡æ•°ã®ãƒ—ラットフォームや OS ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§å‹•ä½œã™ã‚‹ Playbook を作æˆã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚一部㮠CentOS ã¨ä¸€éƒ¨ã® Debian サーãƒãƒ¼ã« Apache をインストールã™ã‚‹å ´åˆã¯ã€YAML ã®ã‚ーã¨å€¤ã§å¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«ã‚’作æˆã—ã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:390 -msgid "Then import those variables files based on the facts you gather on the hosts in your playbook::" +#: ../../rst/user_guide/playbooks_conditionals.rst:410 +msgid "Then import those variables files based on the facts you gather on the hosts in your playbook:" msgstr "次ã«ã€Playbook ã®ãƒ›ã‚¹ãƒˆã«åŽé›†ã™ã‚‹ãƒ•ã‚¡ã‚¯ãƒˆã«åŸºã¥ã„ã¦ã€ã“れらã®å¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«ã‚’インãƒãƒ¼ãƒˆã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:404 +#: ../../rst/user_guide/playbooks_conditionals.rst:426 msgid "Ansible gathers facts on the hosts in the webservers group, then interpolates the variable \"ansible_facts['os_family']\" into a list of filenames. If you have hosts with Red Hat operating systems (CentOS, for example), Ansible looks for 'vars/RedHat.yml'. If that file does not exist, Ansible attempts to load 'vars/os_defaults.yml'. For Debian hosts, Ansible first looks for 'vars/Debian.yml', before falling back on 'vars/os_defaults.yml'. If no files in the list are found, Ansible raises an error." msgstr "Ansible 㯠webservers グループã«å±žã™ã‚‹ãƒ›ã‚¹ãƒˆã®ãƒ•ã‚¡ã‚¯ãƒˆã‚’åŽé›†ã—ã€å¤‰æ•°ã€Œansible_facts['os_family']ã€ã‚’ファイルåã®ãƒªã‚¹ãƒˆã«è£œé–“ã—ã¾ã™ã€‚Red Hat オペレーティングシステムをæ載ã—ãŸãƒ›ã‚¹ãƒˆ (CentOS ãªã©) ãŒã‚ã‚‹å ´åˆã€Ansible ã¯ã€Œvars/RedHat.ymlã€ã‚’探ã—ã¾ã™ã€‚ã“ã®ãƒ•ã‚¡ã‚¤ãƒ«ãŒå˜åœ¨ã—ãªã„å ´åˆã€Ansibleã¯ã€Œvars/os_defaults.ymlã€ã®èªã¿è¾¼ã¿ã‚’試ã¿ã¾ã™ã€‚Debian ホストã®å ´åˆã€Ansible ã¯ã¾ãšã€Œvars/Debian.ymlã€ã‚’探ã—ã€ãã®å¾Œã§ã€Œvars/os_defaults.ymlã€ã«ãƒ•ã‚©ãƒ¼ãƒ«ãƒãƒƒã‚¯ã—ã¾ã™ã€‚リスト内ã®ãƒ•ã‚¡ã‚¤ãƒ«ãŒè¦‹ã¤ã‹ã‚‰ãªã„å ´åˆã¯ã€Ansible ãŒã‚¨ãƒ©ãƒ¼ã‚’出力ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:407 +#: ../../rst/user_guide/playbooks_conditionals.rst:429 msgid "Selecting files and templates based on facts" msgstr "ファクトã«åŸºã¥ãファイルã¨ãƒ†ãƒ³ãƒ—レートã®é¸æŠž" -#: ../../rst/user_guide/playbooks_conditionals.rst:409 +#: ../../rst/user_guide/playbooks_conditionals.rst:431 msgid "You can use the same approach when different OS flavors or versions require different configuration files or templates. Select the appropriate file or template based on the variables assigned to each host. This approach is often much cleaner than putting a lot of conditionals into a single template to cover multiple OS or package versions." msgstr "OS ã®ãƒ•ãƒ¬ãƒ¼ãƒãƒ¼ã‚„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«ã‚ˆã£ã¦ã€è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã‚„テンプレートãŒç•°ãªã‚‹å ´åˆã‚‚åŒæ§˜ã®æ–¹æ³•ã§å¯¾å¿œã§ãã¾ã™ã€‚å„ホストã«å‰²ã‚Šå½“ã¦ã‚‰ã‚ŒãŸå¤‰æ•°ã«åŸºã¥ã„ã¦ã€é©åˆ‡ãªãƒ•ã‚¡ã‚¤ãƒ«ã‚„テンプレートをé¸æŠžã—ã¾ã™ã€‚ã“ã®æ–¹æ³•ã¯ã€è¤‡æ•°ã® OS やパッケージã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«å¯¾å¿œã™ã‚‹ãŸã‚ã« 1 ã¤ã®ãƒ†ãƒ³ãƒ—レートã«å¤šãã®æ¡ä»¶åˆ†å²ã‚’入れるよりもã€ã¯ã‚‹ã‹ã«ã™ã£ãã‚Šã™ã‚‹ã“ã¨ãŒå¤šã„ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:411 -msgid "For example, you can template out a configuration file that is very different between, say, CentOS and Debian::" +#: ../../rst/user_guide/playbooks_conditionals.rst:433 +msgid "For example, you can template out a configuration file that is very different between, say, CentOS and Debian:" msgstr "例ãˆã°ã€CentOS 㨠Debian ã®é–“ã§å¤§ããç•°ãªã‚‹è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã‚’テンプレート化ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:427 +#: ../../rst/user_guide/playbooks_conditionals.rst:451 msgid "Commonly-used facts" msgstr "一般的ã«ä½¿ç”¨ã•ã‚Œã‚‹ãƒ•ã‚¡ã‚¯ãƒˆ" -#: ../../rst/user_guide/playbooks_conditionals.rst:429 +#: ../../rst/user_guide/playbooks_conditionals.rst:453 msgid "The following Ansible facts are frequently used in conditionals." msgstr "以下㮠Ansible ファクトã¯ã€æ¡ä»¶åˆ†å²ã§é »ç¹ã«ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:434 +#: ../../rst/user_guide/playbooks_conditionals.rst:458 msgid "ansible_facts['distribution']" msgstr "ansible_facts['distribution']" -#: ../../rst/user_guide/playbooks_conditionals.rst:436 -#: ../../rst/user_guide/playbooks_conditionals.rst:474 -msgid "Possible values (sample, not complete list)::" +#: ../../rst/user_guide/playbooks_conditionals.rst:460 +#: ../../rst/user_guide/playbooks_conditionals.rst:500 +msgid "Possible values (sample, not complete list):" msgstr "使用ã§ãる値 (完全リストã§ã¯ãªã一部ã§ã™):" -#: ../../rst/user_guide/playbooks_conditionals.rst:465 +#: ../../rst/user_guide/playbooks_conditionals.rst:491 msgid "ansible_facts['distribution_major_version']" msgstr "ansible_facts['distribution_major_version']" -#: ../../rst/user_guide/playbooks_conditionals.rst:467 +#: ../../rst/user_guide/playbooks_conditionals.rst:493 msgid "The major version of the operating system. For example, the value is `16` for Ubuntu 16.04." msgstr "オペレーティングシステムã®ãƒ¡ã‚¸ãƒ£ãƒ¼ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã™ã€‚ãŸã¨ãˆã°ã€Ubuntu 16.04 ã®å ´åˆã¯ `16` ã¨ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_conditionals.rst:472 +#: ../../rst/user_guide/playbooks_conditionals.rst:498 msgid "ansible_facts['os_family']" msgstr "ansible_facts['os_family']" -#: ../../rst/user_guide/playbooks_conditionals.rst:501 -#: ../../rst/user_guide/playbooks_error_handling.rst:236 +#: ../../rst/user_guide/playbooks_conditionals.rst:529 +#: ../../rst/user_guide/playbooks_error_handling.rst:264 #: ../../rst/user_guide/playbooks_filters.rst:1847 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:737 -#: ../../rst/user_guide/playbooks_intro.rst:144 -#: ../../rst/user_guide/playbooks_loops.rst:438 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:859 +#: ../../rst/user_guide/playbooks_intro.rst:148 +#: ../../rst/user_guide/playbooks_loops.rst:480 #: ../../rst/user_guide/playbooks_reuse.rst:214 #: ../../rst/user_guide/playbooks_reuse_includes.rst:17 #: ../../rst/user_guide/playbooks_reuse_roles.rst:606 #: ../../rst/user_guide/playbooks_templating.rst:54 -#: ../../rst/user_guide/playbooks_tests.rst:398 -#: ../../rst/user_guide/playbooks_variables.rst:459 -#: ../../rst/user_guide/windows_dsc.rst:498 -#: ../../rst/user_guide/windows_faq.rst:246 -#: ../../rst/user_guide/windows_setup.rst:576 -#: ../../rst/user_guide/windows_usage.rst:506 -#: ../../rst/user_guide/windows_winrm.rst:907 +#: ../../rst/user_guide/playbooks_tests.rst:434 +#: ../../rst/user_guide/playbooks_variables.rst:505 +#: ../../rst/user_guide/windows_dsc.rst:500 +#: ../../rst/user_guide/windows_faq.rst:250 +#: ../../rst/user_guide/windows_setup.rst:599 +#: ../../rst/user_guide/windows_usage.rst:510 +#: ../../rst/user_guide/windows_winrm.rst:929 msgid ":ref:`playbooks_best_practices`" msgstr ":ref:`playbooks_best_practices`" -#: ../../rst/user_guide/playbooks_conditionals.rst:502 -#: ../../rst/user_guide/playbooks_error_handling.rst:237 +#: ../../rst/user_guide/playbooks_conditionals.rst:530 +#: ../../rst/user_guide/playbooks_error_handling.rst:265 #: ../../rst/user_guide/playbooks_filters.rst:1848 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:738 -#: ../../rst/user_guide/playbooks_loops.rst:439 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:860 +#: ../../rst/user_guide/playbooks_loops.rst:481 #: ../../rst/user_guide/playbooks_reuse.rst:215 #: ../../rst/user_guide/playbooks_reuse_includes.rst:18 #: ../../rst/user_guide/playbooks_reuse_roles.rst:607 #: ../../rst/user_guide/playbooks_templating.rst:55 -#: ../../rst/user_guide/playbooks_tests.rst:399 -#: ../../rst/user_guide/playbooks_variables.rst:460 -#: ../../rst/user_guide/windows_dsc.rst:499 -#: ../../rst/user_guide/windows_faq.rst:247 -#: ../../rst/user_guide/windows_setup.rst:577 -#: ../../rst/user_guide/windows_usage.rst:507 -#: ../../rst/user_guide/windows_winrm.rst:908 +#: ../../rst/user_guide/playbooks_tests.rst:435 +#: ../../rst/user_guide/playbooks_variables.rst:506 +#: ../../rst/user_guide/windows_dsc.rst:501 +#: ../../rst/user_guide/windows_faq.rst:251 +#: ../../rst/user_guide/windows_setup.rst:600 +#: ../../rst/user_guide/windows_usage.rst:511 +#: ../../rst/user_guide/windows_winrm.rst:930 msgid "Tips and tricks for playbooks" msgstr "Playbook ã®ãƒ’ントã¨è£æŠ€" @@ -5281,252 +5276,252 @@ msgstr "プレイ㫠``debugger`` ã‚ーワードをè¨å®šã™ã‚‹ä¾‹:" msgid "Example of setting the ``debugger`` keyword at multiple levels:" msgstr "複数ã®ãƒ¬ãƒ™ãƒ«ã§ ``debugger`` ã‚ーワードをè¨å®šã™ã‚‹ä¾‹:" -#: ../../rst/user_guide/playbooks_debugger.rst:86 +#: ../../rst/user_guide/playbooks_debugger.rst:85 msgid "In this example, the debugger is set to ``never`` at the play level and to ``on_failed`` at the task level. If the task fails, Ansible invokes the debugger, because the definition on the task overrides the definition on its parent play." msgstr "ã“ã®ä¾‹ã§ã¯ã€ãƒ‡ãƒãƒƒã‚¬ãƒ¼ã¯ã€ãƒ—レイレベルã§ã¯ ``never`` ã«ã€ã‚¿ã‚¹ã‚¯ãƒ¬ãƒ™ãƒ«ã§ã¯ ``on_failed`` ã«è¨å®šã•ã‚Œã¦ã„ã¾ã™ã€‚タスクãŒå¤±æ•—ã—ãŸå ´åˆã€ã‚¿ã‚¹ã‚¯ã®å®šç¾©ãŒè¦ªãƒ—レイã®å®šç¾©ã‚’上書ãã™ã‚‹ãŸã‚ã€Ansible ã¯ãƒ‡ãƒãƒƒã‚¬ãƒ¼ã‚’èµ·å‹•ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:89 +#: ../../rst/user_guide/playbooks_debugger.rst:88 msgid "Enabling the debugger in configuration or an environment variable" msgstr "è¨å®šã¾ãŸã¯ç’°å¢ƒå¤‰æ•°ã§ã®ãƒ‡ãƒãƒƒã‚¬ãƒ¼ã®æœ‰åŠ¹åŒ–" -#: ../../rst/user_guide/playbooks_debugger.rst:93 +#: ../../rst/user_guide/playbooks_debugger.rst:92 msgid "You can enable the task debugger globally with a setting in ansible.cfg or with an environment variable. The only options are ``True`` or ``False``. If you set the configuration option or environment variable to ``True``, Ansible runs the debugger on failed tasks by default." msgstr "タスクデãƒãƒƒã‚¬ãƒ¼ã‚’ã‚°ãƒãƒ¼ãƒãƒ«ã«æœ‰åŠ¹ã«ã™ã‚‹ã«ã¯ã€ansible.cfg 内ã®è¨å®šã¾ãŸã¯ç’°å¢ƒå¤‰æ•°ã‚’使用ã—ã¾ã™ã€‚オプション㯠``True`` ã¾ãŸã¯ ``False`` ã®ã¿ã§ã™ã€‚è¨å®šã‚ªãƒ—ションã¾ãŸã¯ç’°å¢ƒå¤‰æ•°ã‚’ ``True`` ã«è¨å®šã—ãŸå ´åˆã€Ansible ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§å¤±æ•—ã—ãŸã‚¿ã‚¹ã‚¯ã«å¯¾ã—ã¦ãƒ‡ãƒãƒƒã‚¬ãƒ¼ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:95 -msgid "To enable the task debugger from ansible.cfg, add this setting to the defaults section::" +#: ../../rst/user_guide/playbooks_debugger.rst:94 +msgid "To enable the task debugger from ansible.cfg, add this setting to the defaults section:" msgstr "ansible.cfg ã‹ã‚‰ã‚¿ã‚¹ã‚¯ãƒ‡ãƒãƒƒã‚¬ãƒ¼ã‚’有効ã«ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®è¨å®šã‚’ defaults セクションã«è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:100 -msgid "To enable the task debugger with an environment variable, pass the variable when you run your playbook::" +#: ../../rst/user_guide/playbooks_debugger.rst:101 +msgid "To enable the task debugger with an environment variable, pass the variable when you run your playbook:" msgstr "環境変数ã§ã‚¿ã‚¹ã‚¯ãƒ‡ãƒãƒƒã‚¬ãƒ¼ã‚’有効ã«ã™ã‚‹ã«ã¯ã€Playbook ã®å®Ÿè¡Œæ™‚ã«å¤‰æ•°ã‚’渡ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:104 +#: ../../rst/user_guide/playbooks_debugger.rst:107 msgid "When you enable the debugger globally, every failed task invokes the debugger, unless the role, play, block, or task explicitly disables the debugger. If you need more granular control over what conditions trigger the debugger, use the ``debugger`` keyword." msgstr "ã‚°ãƒãƒ¼ãƒãƒ«ã«ãƒ‡ãƒãƒƒã‚¬ã‚’有効ã«ã™ã‚‹ã¨ã€ãƒãƒ¼ãƒ«ã€ãƒ—レイã€ãƒ–ãƒãƒƒã‚¯ã€ã¾ãŸã¯ã‚¿ã‚¹ã‚¯ãŒæ˜Žç¤ºçš„ã«ãƒ‡ãƒãƒƒã‚¬â€•ã‚’無効ã«ã—ã¦ã„ãªã„é™ã‚Šã€å¤±æ•—ã—ãŸã‚¿ã‚¹ã‚¯ã¯ã™ã¹ã¦ãƒ‡ãƒãƒƒã‚¬â€•ã‚’èµ·å‹•ã—ã¾ã™ã€‚ã©ã®ã‚ˆã†ãªæ¡ä»¶ã§ãƒ‡ãƒãƒƒã‚¬ãƒ¼ãŒèµ·å‹•ã™ã‚‹ã‹ã‚’より詳細ã«åˆ¶å¾¡ã™ã‚‹å¿…è¦ãŒã‚ã‚‹å ´åˆã¯ã€``debugger`` ã‚ーワードを使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:107 +#: ../../rst/user_guide/playbooks_debugger.rst:110 msgid "Enabling the debugger as a strategy" msgstr "ストラテジーã¨ã—ã¦ã®ãƒ‡ãƒãƒƒã‚¬ãƒ¼ã®æœ‰åŠ¹åŒ–" -#: ../../rst/user_guide/playbooks_debugger.rst:109 +#: ../../rst/user_guide/playbooks_debugger.rst:112 msgid "If you are running legacy playbooks or roles, you may see the debugger enabled as a :ref:`strategy <strategy_plugins>`. You can do this at the play level, in ansible.cfg, or with the environment variable ``ANSIBLE_STRATEGY=debug``. For example:" msgstr "レガシー㮠Playbook ã‚„ãƒãƒ¼ãƒ«ã‚’実行ã—ã¦ã„ã‚‹å ´åˆã¯ã€:ref:`strategy <strategy_plugins>` ã¨ã—ã¦ãƒ‡ãƒãƒƒã‚¬ãƒ¼ãŒæœ‰åŠ¹ã«ãªã£ã¦ã„ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®è¨å®šã¯ã€ãƒ—レイレベルã€ansible.cfgã€ã¾ãŸã¯ç’°å¢ƒå¤‰æ•° ``ANSIBLE_STRATEGY=debug`` ã§è¡Œã†ã“ã¨ãŒã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:118 -msgid "Or in ansible.cfg::" +#: ../../rst/user_guide/playbooks_debugger.rst:121 +msgid "Or in ansible.cfg:" msgstr "ã¾ãŸã¯ ansible.cfg ã§ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:125 +#: ../../rst/user_guide/playbooks_debugger.rst:130 msgid "This backwards-compatible method, which matches Ansible versions before 2.5, may be removed in a future release." msgstr "ã“ã®å¾Œæ–¹äº’æ›æ€§ã®ã‚る方法ã¯ã€Ansible ã® 2.5 以å‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«å¯¾å¿œã—ã¦ã„ã¾ã™ãŒã€å°†æ¥ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯å‰Šé™¤ã•ã‚Œã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:128 +#: ../../rst/user_guide/playbooks_debugger.rst:133 msgid "Resolving errors in the debugger" msgstr "デãƒãƒƒã‚¬ãƒ¼ã§ã‚¨ãƒ©ãƒ¼ã®è§£æ±º" -#: ../../rst/user_guide/playbooks_debugger.rst:130 +#: ../../rst/user_guide/playbooks_debugger.rst:135 msgid "After Ansible invokes the debugger, you can use the seven :ref:`debugger commands <available_commands>` to resolve the error that Ansible encountered. Consider this example playbook, which defines the ``var1`` variable but uses the undefined ``wrong_var`` variable in a task by mistake." msgstr "Ansible ãŒãƒ‡ãƒãƒƒã‚¬ãƒ¼ã‚’èµ·å‹•ã—ãŸå¾Œã€7 ã¤ã® :ref:`debugger コマンド <available_commands>` を使用ã—ã¦ã€AnsibleãŒéé‡ã—ãŸã‚¨ãƒ©ãƒ¼ã‚’解決ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã® Playbook ã®ä¾‹ã§ã¯ ``var1`` 変数を定義ã—ã¦ã„ã¾ã™ãŒã€æœªå®šç¾©ã® ``wrong_var`` 変数を誤ã£ã¦ã‚¿ã‚¹ã‚¯ã§ä½¿ç”¨ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:143 +#: ../../rst/user_guide/playbooks_debugger.rst:148 msgid "If you run this playbook, Ansible invokes the debugger when the task fails. From the debug prompt, you can change the module arguments or the variables and run the task again." msgstr "ã“ã® Playbook を実行ã™ã‚‹ã¨ã€Ansible ã¯ã‚¿ã‚¹ã‚¯ã®å¤±æ•—時ã«ãƒ‡ãƒãƒƒã‚¬ãƒ¼ã‚’呼ã³å‡ºã—ã¾ã™ã€‚デãƒãƒƒã‚°ãƒ—ãƒãƒ³ãƒ—トã‹ã‚‰ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«å¼•æ•°ã¾ãŸã¯å¤‰æ•°ã‚’変更ã—ã¦ã€ã‚¿ã‚¹ã‚¯ã‚’å†åº¦å®Ÿè¡Œã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:178 +#: ../../rst/user_guide/playbooks_debugger.rst:183 msgid "Changing the task arguments in the debugger to use ``var1`` instead of ``wrong_var`` makes the task run successfully." msgstr "デãƒãƒƒã‚¬ã§ã‚¿ã‚¹ã‚¯ã®å¼•æ•° ``wrong_var`` ã®ä»£ã‚ã‚Šã« ``var1`` を使用ã™ã‚‹ã‚ˆã†ã«å¤‰æ›´ã™ã‚‹ã¨ã€ã‚¿ã‚¹ã‚¯ãŒæ£å¸¸ã«å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:183 +#: ../../rst/user_guide/playbooks_debugger.rst:188 msgid "Available debug commands" msgstr "利用å¯èƒ½ãªãƒ‡ãƒãƒƒã‚°ã‚³ãƒžãƒ³ãƒ‰" -#: ../../rst/user_guide/playbooks_debugger.rst:185 +#: ../../rst/user_guide/playbooks_debugger.rst:190 msgid "You can use these seven commands at the debug prompt:" msgstr "ã“れら㮠7 ã¤ã®ã‚³ãƒžãƒ³ãƒ‰ã¯ã€ãƒ‡ãƒãƒƒã‚°ãƒ—ãƒãƒ³ãƒ—トã§ä½¿ç”¨ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:191 +#: ../../rst/user_guide/playbooks_debugger.rst:196 msgid "Command" msgstr "コマンド" -#: ../../rst/user_guide/playbooks_debugger.rst:191 +#: ../../rst/user_guide/playbooks_debugger.rst:196 msgid "Shortcut" msgstr "ショートカット" -#: ../../rst/user_guide/playbooks_debugger.rst:191 +#: ../../rst/user_guide/playbooks_debugger.rst:196 msgid "Action" msgstr "アクション" -#: ../../rst/user_guide/playbooks_debugger.rst:193 +#: ../../rst/user_guide/playbooks_debugger.rst:198 msgid "print" msgstr "print" -#: ../../rst/user_guide/playbooks_debugger.rst:193 +#: ../../rst/user_guide/playbooks_debugger.rst:198 msgid "p" msgstr "p" -#: ../../rst/user_guide/playbooks_debugger.rst:193 +#: ../../rst/user_guide/playbooks_debugger.rst:198 msgid "Print information about the task" msgstr "タスクã«é–¢ã™ã‚‹æƒ…å ±ã‚’å‡ºåŠ›ã™ã‚‹" -#: ../../rst/user_guide/playbooks_debugger.rst:195 +#: ../../rst/user_guide/playbooks_debugger.rst:200 msgid "task.args[*key*] = *value*" msgstr "task.args[*key*] = *value*" -#: ../../rst/user_guide/playbooks_debugger.rst:195 -#: ../../rst/user_guide/playbooks_debugger.rst:197 +#: ../../rst/user_guide/playbooks_debugger.rst:200 +#: ../../rst/user_guide/playbooks_debugger.rst:202 msgid "no shortcut" msgstr "ショートカットãªã—" -#: ../../rst/user_guide/playbooks_debugger.rst:195 +#: ../../rst/user_guide/playbooks_debugger.rst:200 msgid "Update module arguments" msgstr "モジュール引数を更新ã™ã‚‹" -#: ../../rst/user_guide/playbooks_debugger.rst:197 +#: ../../rst/user_guide/playbooks_debugger.rst:202 msgid "task_vars[*key*] = *value*" msgstr "task_vars[*key*] = *value*" -#: ../../rst/user_guide/playbooks_debugger.rst:197 +#: ../../rst/user_guide/playbooks_debugger.rst:202 msgid "Update task variables (you must ``update_task`` next)" msgstr "タスク変数を更新ã™ã‚‹ (次回 ``update_task`` ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™)" -#: ../../rst/user_guide/playbooks_debugger.rst:199 +#: ../../rst/user_guide/playbooks_debugger.rst:204 msgid "update_task" msgstr "update_task" -#: ../../rst/user_guide/playbooks_debugger.rst:199 +#: ../../rst/user_guide/playbooks_debugger.rst:204 msgid "u" msgstr "u" -#: ../../rst/user_guide/playbooks_debugger.rst:199 +#: ../../rst/user_guide/playbooks_debugger.rst:204 msgid "Recreate a task with updated task variables" msgstr "æ›´æ–°ã•ã‚ŒãŸã‚¿ã‚¹ã‚¯å¤‰æ•°ã§ã‚¿ã‚¹ã‚¯ã‚’å†ä½œæˆã™ã‚‹" -#: ../../rst/user_guide/playbooks_debugger.rst:201 +#: ../../rst/user_guide/playbooks_debugger.rst:206 msgid "redo" msgstr "redo" -#: ../../rst/user_guide/playbooks_debugger.rst:201 +#: ../../rst/user_guide/playbooks_debugger.rst:206 msgid "r" msgstr "r" -#: ../../rst/user_guide/playbooks_debugger.rst:201 +#: ../../rst/user_guide/playbooks_debugger.rst:206 msgid "Run the task again" msgstr "タスクをå†åº¦å®Ÿè¡Œã™ã‚‹" -#: ../../rst/user_guide/playbooks_debugger.rst:203 +#: ../../rst/user_guide/playbooks_debugger.rst:208 msgid "continue" msgstr "continue" -#: ../../rst/user_guide/playbooks_debugger.rst:203 +#: ../../rst/user_guide/playbooks_debugger.rst:208 msgid "c" msgstr "c" -#: ../../rst/user_guide/playbooks_debugger.rst:203 +#: ../../rst/user_guide/playbooks_debugger.rst:208 msgid "Continue executing, starting with the next task" msgstr "実行を継続ã™ã‚‹ (次ã®ã‚¿ã‚¹ã‚¯ã‹ã‚‰é–‹å§‹)" -#: ../../rst/user_guide/playbooks_debugger.rst:205 +#: ../../rst/user_guide/playbooks_debugger.rst:210 msgid "quit" msgstr "quit" -#: ../../rst/user_guide/playbooks_debugger.rst:205 +#: ../../rst/user_guide/playbooks_debugger.rst:210 msgid "q" msgstr "q" -#: ../../rst/user_guide/playbooks_debugger.rst:205 +#: ../../rst/user_guide/playbooks_debugger.rst:210 msgid "Quit the debugger" msgstr "デãƒãƒƒã‚¬ãƒ¼ã‚’終了ã™ã‚‹" -#: ../../rst/user_guide/playbooks_debugger.rst:209 +#: ../../rst/user_guide/playbooks_debugger.rst:214 msgid "For more details, see the individual descriptions and examples below." msgstr "詳細ã¯ã€ä»¥ä¸‹ã®å€‹åˆ¥ã®èª¬æ˜ŽãŠã‚ˆã³ä¾‹ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_debugger.rst:214 +#: ../../rst/user_guide/playbooks_debugger.rst:219 msgid "Print command" msgstr "コマンドを出力ã™ã‚‹" -#: ../../rst/user_guide/playbooks_debugger.rst:216 -msgid "``print *task/task.args/task_vars/host/result*`` prints information about the task::" +#: ../../rst/user_guide/playbooks_debugger.rst:221 +msgid "``print *task/task.args/task_vars/host/result*`` prints information about the task." msgstr "``print *task/task.args/task_vars/host/result*`` ã¯ã€ã‚¿ã‚¹ã‚¯ã«é–¢ã™ã‚‹æƒ…å ±ã‚’å‡ºåŠ›ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:241 +#: ../../rst/user_guide/playbooks_debugger.rst:248 msgid "Update args command" msgstr "args コマンドを更新ã™ã‚‹" -#: ../../rst/user_guide/playbooks_debugger.rst:243 -msgid "``task.args[*key*] = *value*`` updates a module argument. This sample playbook has an invalid package name::" +#: ../../rst/user_guide/playbooks_debugger.rst:250 +msgid "``task.args[*key*] = *value*`` updates a module argument. This sample playbook has an invalid package name." msgstr "``task.args[*key*] = *value*`` モジュール引数を更新ã—ã¾ã™ã€‚ã“ã®ã‚µãƒ³ãƒ—ル Playbook ã«ã¯ç„¡åŠ¹ãªãƒ‘ッケージåãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:254 -msgid "When you run the playbook, the invalid package name triggers an error, and Ansible invokes the debugger. You can fix the package name by viewing, then updating the module argument::" +#: ../../rst/user_guide/playbooks_debugger.rst:263 +msgid "When you run the playbook, the invalid package name triggers an error, and Ansible invokes the debugger. You can fix the package name by viewing, then updating the module argument." msgstr "Playbook を実行ã™ã‚‹ã¨ã€ãƒ‘ッケージåãŒç„¡åŠ¹ã§ã‚ã‚‹ãŸã‚ã«ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã—ã€Ansible ãŒãƒ‡ãƒãƒƒã‚¬ãƒ¼ã‚’èµ·å‹•ã—ã¾ã™ã€‚パッケージåã‚’ä¿®æ£ã™ã‚‹ã«ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®å¼•æ•°ã‚’表示ã—ã¦ã‹ã‚‰æ›´æ–°ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:263 +#: ../../rst/user_guide/playbooks_debugger.rst:274 msgid "After you update the module argument, use ``redo`` to run the task again with the new args." msgstr "モジュール引数を更新ã—ãŸã‚‰ã€``redo`` を使用ã—ã¦ã€æ–°ã—ã„引数ã§ã‚¿ã‚¹ã‚¯ã‚’å†åº¦å®Ÿè¡Œã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:268 +#: ../../rst/user_guide/playbooks_debugger.rst:279 msgid "Update vars command" msgstr "vars コマンドã®æ›´æ–°" -#: ../../rst/user_guide/playbooks_debugger.rst:270 -msgid "``task_vars[*key*] = *value*`` updates the ``task_vars``. You could fix the playbook above by viewing, then updating the task variables instead of the module args::" +#: ../../rst/user_guide/playbooks_debugger.rst:281 +msgid "``task_vars[*key*] = *value*`` updates the ``task_vars``. You could fix the playbook above by viewing, then updating the task variables instead of the module args." msgstr "``task_vars[*key*] = *value*`` ã¯ã€``task_vars`` ã‚’æ›´æ–°ã—ã¾ã™ã€‚モジュール引数ã§ã¯ãªãタスク変数を表示ã—ã¦ã‹ã‚‰æ›´æ–°ã—ã¦ã€ä¸Šè¨˜ã® Playbook ã‚’ä¿®æ£ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:280 +#: ../../rst/user_guide/playbooks_debugger.rst:293 msgid "After you update the task variables, you must use ``update_task`` to load the new variables before using ``redo`` to run the task again." msgstr "タスク変数を更新ã—ãŸã‚‰ã€``redo`` を使用ã—ã¦ã‚¿ã‚¹ã‚¯ã‚’å†å®Ÿè¡Œã™ã‚‹å‰ã«ã€``update_task`` を使用ã—ã¦æ–°ã—ã„変数をèªã¿è¾¼ã‚€å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:283 +#: ../../rst/user_guide/playbooks_debugger.rst:296 msgid "In 2.5 this was updated from ``vars`` to ``task_vars`` to avoid conflicts with the ``vars()`` python function." msgstr "ã“ã‚Œã¯ã€python 関数 ``vars()`` ã¨ç«¶åˆã—ãªã„よã†ã«ã€2.5 㧠``vars`` ã‹ã‚‰ ``task_vars`` ã«æ›´æ–°ã•ã‚Œã¾ã—ãŸã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:288 +#: ../../rst/user_guide/playbooks_debugger.rst:301 msgid "Update task command" msgstr "task コマンドã®æ›´æ–°" -#: ../../rst/user_guide/playbooks_debugger.rst:292 +#: ../../rst/user_guide/playbooks_debugger.rst:305 msgid "``u`` or ``update_task`` recreates the task from the original task data structure and templates with updated task variables. See the entry :ref:`update_vars_command` for an example of use." msgstr "``u`` ã¾ãŸã¯ ``update_task`` ã¯ã€æ›´æ–°ã•ã‚ŒãŸã‚¿ã‚¹ã‚¯å¤‰æ•°ã‚’æŒã¤å…ƒã®ã‚¿ã‚¹ã‚¯ãƒ‡ãƒ¼ã‚¿æ§‹é€ ã¨ãƒ†ãƒ³ãƒ—レートã‹ã‚‰ã‚¿ã‚¹ã‚¯ã‚’å†ä½œæˆã—ã¾ã™ã€‚使用例ã¯ã€ã‚¨ãƒ³ãƒˆãƒªãƒ¼:ref:`update_vars_command` ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_debugger.rst:297 +#: ../../rst/user_guide/playbooks_debugger.rst:310 msgid "Redo command" msgstr "コマンドã®ã‚„ã‚Šç›´ã—" -#: ../../rst/user_guide/playbooks_debugger.rst:299 +#: ../../rst/user_guide/playbooks_debugger.rst:312 msgid "``r`` or ``redo`` runs the task again." msgstr "``r`` ã¾ãŸã¯ ``redo`` ã¯ã‚¿ã‚¹ã‚¯ã‚’å†å®Ÿè¡Œã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:304 +#: ../../rst/user_guide/playbooks_debugger.rst:317 msgid "Continue command" msgstr "コマンドã®ç¶šè¡Œ" -#: ../../rst/user_guide/playbooks_debugger.rst:306 +#: ../../rst/user_guide/playbooks_debugger.rst:319 msgid "``c`` or ``continue`` continues executing, starting with the next task." msgstr "``c`` ã¾ãŸã¯ ``continue`` ã¯ã€æ¬¡ã®ã‚¿ã‚¹ã‚¯ã‹ã‚‰é–‹å§‹ã—ã¦å®Ÿè¡Œã‚’継続ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:311 +#: ../../rst/user_guide/playbooks_debugger.rst:324 msgid "Quit command" msgstr "Quit コマンド" -#: ../../rst/user_guide/playbooks_debugger.rst:313 +#: ../../rst/user_guide/playbooks_debugger.rst:326 msgid "``q`` or ``quit`` quits the debugger. The playbook execution is aborted." msgstr "``q`` ã¾ãŸã¯ ``quit`` ã¯ãƒ‡ãƒãƒƒã‚¬ãƒ¼ã‚’終了ã—ã¾ã™ã€‚Playbook ã®å®Ÿè¡Œã¯ä¸æ¢ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_debugger.rst:316 +#: ../../rst/user_guide/playbooks_debugger.rst:329 msgid "How the debugger interacts with the free strategy" msgstr "デãƒãƒƒã‚¬ãƒ¼ãŒãƒ•ãƒªãƒ¼ã‚¹ãƒˆãƒ©ãƒ†ã‚¸ãƒ¼ã¨ã©ã®ã‚ˆã†ã«ç›¸äº’作用ã™ã‚‹ã‹" -#: ../../rst/user_guide/playbooks_debugger.rst:318 +#: ../../rst/user_guide/playbooks_debugger.rst:331 msgid "With the default ``linear`` strategy enabled, Ansible halts execution while the debugger is active, and runs the debugged task immediately after you enter the ``redo`` command. With the ``free`` strategy enabled, however, Ansible does not wait for all hosts, and may queue later tasks on one host before a task fails on another host. With the ``free`` strategy, Ansible does not queue or execute any tasks while the debugger is active. However, all queued tasks remain in the queue and run as soon as you exit the debugger. If you use ``redo`` to reschedule a task from the debugger, other queued tasks may execute before your rescheduled task. For more information about strategies, see :ref:`playbooks_strategies`." msgstr "デフォルト㮠``linear`` ストラテジーを有効ã«ã™ã‚‹ã¨ã€Ansible ã¯ãƒ‡ãƒãƒƒã‚¬â€•ãŒã‚¢ã‚¯ãƒ†ã‚£ãƒ–ãªé–“ã¯å®Ÿè¡Œã‚’åœæ¢ã—ã€``redo`` コマンドを入力ã—ãŸç›´å¾Œã«ãƒ‡ãƒãƒƒã‚°ã•ã‚ŒãŸã‚¿ã‚¹ã‚¯ã‚’実行ã—ã¾ã™ã€‚ã—ã‹ã—ã€``free`` ストラテジーを有効ã«ã™ã‚‹ã¨ã€Ansible ã¯ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã‚’å¾…ãŸãšã«ã€åˆ¥ã®ãƒ›ã‚¹ãƒˆã§ã‚¿ã‚¹ã‚¯ãŒå¤±æ•—ã™ã‚‹å‰ã«ã€ã‚るホストã§å¾Œã®ã‚¿ã‚¹ã‚¯ã‚’ã‚ューã«å…¥ã‚Œã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚``free`` ストラテジーを使用ã™ã‚‹ã¨ã€ãƒ‡ãƒãƒƒã‚¬ãƒ¼ãŒã‚¢ã‚¯ãƒ†ã‚£ãƒ–ãªé–“ã€Ansible ã¯ã€ã‚¿ã‚¹ã‚¯ã®ç…§ä¼šã‚„実行を行ã„ã¾ã›ã‚“。ãŸã ã—ã€ã‚ューã«å…¥ã‚Œã‚‰ã‚ŒãŸã‚¿ã‚¹ã‚¯ã¯ã™ã¹ã¦ã‚ューã«æ®‹ã‚Šã€ãƒ‡ãƒãƒƒã‚¬ãƒ¼ã‚’終了ã™ã‚‹ã¨ã™ãã«å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚``redo`` を使用ã—ã¦ãƒ‡ãƒãƒƒã‚¬ãƒ¼ã‹ã‚‰ã‚¿ã‚¹ã‚¯ã‚’å†ã‚¹ã‚±ã‚¸ãƒ¥ãƒ¼ãƒ«ã™ã‚‹ã¨ã€å†ã‚¹ã‚±ã‚¸ãƒ¥ãƒ¼ãƒ«ã•ã‚ŒãŸã‚¿ã‚¹ã‚¯ã®å‰ã«ã‚ューã«å…¥ã‚Œã‚‰ã‚ŒãŸä»–ã®ã‚¿ã‚¹ã‚¯ãŒå®Ÿè¡Œã™ã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚ストラテジーã®è©³ç´°ã«ã¤ã„ã¦ã¯ã€Œ:ref:`playbooks_strategies`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_debugger.rst:322 +#: ../../rst/user_guide/playbooks_debugger.rst:335 msgid ":ref:`playbooks_start_and_step`" msgstr ":ref:`playbooks_start_and_step`" -#: ../../rst/user_guide/playbooks_debugger.rst:323 +#: ../../rst/user_guide/playbooks_debugger.rst:336 msgid "Running playbooks while debugging or testing" msgstr "デãƒãƒƒã‚°æ™‚ã¾ãŸã¯ãƒ†ã‚¹ãƒˆæ™‚ã® Playbook ã®å®Ÿè¡Œ" @@ -5551,90 +5546,90 @@ msgid "Delegating tasks" msgstr "タスクã®å§”è²" #: ../../rst/user_guide/playbooks_delegation.rst:21 -msgid "If you want to perform a task on one host with reference to other hosts, use the ``delegate_to`` keyword on a task. This is ideal for managing nodes in a load balanced pool or for controlling outage windows. You can use delegation with the :ref:`serial <rolling_update_batch_size>` keyword to control the number of hosts executing at one time::" +msgid "If you want to perform a task on one host with reference to other hosts, use the ``delegate_to`` keyword on a task. This is ideal for managing nodes in a load balanced pool or for controlling outage windows. You can use delegation with the :ref:`serial <rolling_update_batch_size>` keyword to control the number of hosts executing at one time:" msgstr "ã‚るホストã§ä»–ã®ãƒ›ã‚¹ãƒˆã‚’å‚ç…§ã—ãªãŒã‚‰ã‚¿ã‚¹ã‚¯ã‚’実行ã—ãŸã„å ´åˆã¯ã€ã‚¿ã‚¹ã‚¯ã« ``delegate_to`` ã‚ーワードを使用ã—ã¾ã™ã€‚ã“ã‚Œã¯ã€è² è·åˆ†æ•£ã•ã‚ŒãŸãƒ—ールã®ãƒŽãƒ¼ãƒ‰ã‚’管ç†ã—ãŸã‚Šã€éšœå®³ç™ºç”Ÿæ™‚ã®ã‚¦ã‚£ãƒ³ãƒ‰ã‚¦ã‚’制御ã™ã‚‹ã®ã«æœ€é©ã§ã™ã€‚:ref:`serial <rolling_update_batch_size>` ã‚ーワードã§å§”è²ã‚’使用ã™ã‚‹ã¨ã€ä¸€åº¦ã«å®Ÿè¡Œã™ã‚‹ãƒ›ã‚¹ãƒˆã®æ•°ã‚’制御ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_delegation.rst:41 -msgid "The first and third tasks in this play run on 127.0.0.1, which is the machine running Ansible. There is also a shorthand syntax that you can use on a per-task basis: ``local_action``. Here is the same playbook as above, but using the shorthand syntax for delegating to 127.0.0.1::" +#: ../../rst/user_guide/playbooks_delegation.rst:43 +msgid "The first and third tasks in this play run on 127.0.0.1, which is the machine running Ansible. There is also a shorthand syntax that you can use on a per-task basis: ``local_action``. Here is the same playbook as above, but using the shorthand syntax for delegating to 127.0.0.1:" msgstr "ã“ã“ã§ã¯ã€1 番目㨠3 番目ã®ã‚¿ã‚¹ã‚¯ã‚’ 127.0.0.1 ã§å®Ÿè¡Œã—ã¦ã„ã¾ã™ãŒã€ã“れ㯠Ansible を実行ã—ã¦ã„るマシンã§ã™ã€‚ã¾ãŸã€ã‚¿ã‚¹ã‚¯ã”ã¨ã«ä½¿ç”¨ã§ãる簡略化ã•ã‚ŒãŸæ§‹æ–‡ãŒã‚ã‚Šã¾ã™ (``local_action``)。以下ã¯ã€ä¸Šè¨˜ã¨åŒã˜ Playbook ã§ã™ãŒã€127.0.0.1 ã«å§”è²ã™ã‚‹ãŸã‚ã®çŸç¸®æ§‹æ–‡ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_delegation.rst:55 -msgid "You can use a local action to call 'rsync' to recursively copy files to the managed servers::" +#: ../../rst/user_guide/playbooks_delegation.rst:59 +msgid "You can use a local action to call 'rsync' to recursively copy files to the managed servers:" msgstr "ãƒãƒ¼ã‚«ãƒ«ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ã‚’使用ã—ã¦ã€Œrsyncã€ã‚’呼ã³å‡ºã—ã€ç®¡ç†å¯¾è±¡ã®ã‚µãƒ¼ãƒãƒ¼ã«ãƒ•ã‚¡ã‚¤ãƒ«ã‚’å†å¸°çš„ã«ã‚³ãƒ”ーã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_delegation.rst:64 +#: ../../rst/user_guide/playbooks_delegation.rst:70 msgid "Note that you must have passphrase-less SSH keys or an ssh-agent configured for this to work, otherwise rsync asks for a passphrase." msgstr "ã“ã‚ŒãŒæ©Ÿèƒ½ã™ã‚‹ãŸã‚ã«ã¯ã€ãƒ‘スフレーズãªã—ã® SSH éµã¾ãŸã¯ ssh-agent ãŒè¨å®šã•ã‚Œã¦ã„ãªã‘ã‚Œã°ãªã‚‰ãªã„ã“ã¨ã«æ³¨æ„ã—ã¦ãã ã•ã„。ãã†ã§ãªã‘ã‚Œã°ã€rsync ã¯ãƒ‘スフレーズをè¦æ±‚ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_delegation.rst:66 -msgid "To specify more arguments, use the following syntax::" +#: ../../rst/user_guide/playbooks_delegation.rst:72 +msgid "To specify more arguments, use the following syntax:" msgstr "引数をã•ã‚‰ã«æŒ‡å®šã™ã‚‹å¿…è¦ãŒã‚ã‚‹å ´åˆã¯ã€ä»¥ä¸‹ã®æ§‹æ–‡ã‚’使用ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_delegation.rst:81 +#: ../../rst/user_guide/playbooks_delegation.rst:89 msgid "The `ansible_host` variable and other connection variables, if present, reflects information about the host a task is delegated to, not the inventory_hostname." msgstr "`ansible_host` 変数ã¨ä»–ã®æŽ¥ç¶šå¤‰æ•°ãŒã‚ã‚‹å ´åˆã¯ã€inventory_hostname ã§ã¯ãªãã€ã‚¿ã‚¹ã‚¯ãŒå§”è²ã•ã‚Œã‚‹ãƒ›ã‚¹ãƒˆã«é–¢ã™ã‚‹æƒ…å ±ã‚’åæ˜ ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_delegation.rst:85 +#: ../../rst/user_guide/playbooks_delegation.rst:93 msgid "Although you can ``delegate_to`` a host that does not exist in inventory (by adding IP address, DNS name or whatever requirement the connection plugin has), doing so does not add the host to your inventory and might cause issues. Hosts delegated to in this way do not inherit variables from the \"all\" group', so variables like connection user and key are missing. If you must ``delegate_to`` a non-inventory host, use the :ref:`add host module <add_host_module>`." msgstr "（IP アドレスã€DNS åã€ã¾ãŸã¯æŽ¥ç¶šãƒ—ラグインã®è¦ä»¶ã‚’è¿½åŠ ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šï¼‰ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã«å˜åœ¨ã—ãªã„ホストを ``delegate_to`` ã«ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ã“れを行ã†ã¨ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã«ãƒ›ã‚¹ãƒˆã‚’è¿½åŠ ã›ãšã€å•é¡ŒãŒç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®ã‚ˆã†ã«å§”è²ã•ã‚ŒãŸãƒ›ã‚¹ãƒˆã¯ã€Œã™ã¹ã¦ã€ã‚°ãƒ«ãƒ¼ãƒ—ã‹ã‚‰å¤‰æ•°ã‚’継承ã—ãªã„ãŸã‚ã€æŽ¥ç¶šãƒ¦ãƒ¼ã‚¶ãƒ¼ã¨ã‚ーãªã©ã®å¤‰æ•°ãŒã‚ã‚Šã¾ã›ã‚“。インベントリーホスト以外をã®ãƒ›ã‚¹ãƒˆã‚’ ``delegate_to`` ã«ã™ã‚‹å¿…è¦ãŒã‚ã‚‹å ´åˆã¯ã€:ref:`add host module <add_host_module>` を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_delegation.rst:91 +#: ../../rst/user_guide/playbooks_delegation.rst:99 msgid "Delegation and parallel execution" msgstr "委è²ã¨ä¸¦åˆ—実行" -#: ../../rst/user_guide/playbooks_delegation.rst:92 +#: ../../rst/user_guide/playbooks_delegation.rst:100 msgid "By default Ansible tasks are executed in parallel. Delegating a task does not change this and does not handle concurrency issues (multiple forks writing to the same file). Most commonly, users are affected by this when updating a single file on a single delegated to host for all hosts (using the ``copy``, ``template``, or ``lineinfile`` modules, for example). They will still operate in parallel forks (default 5) and overwrite each other." msgstr "デフォルトã§ã¯ã€Ansible タスクã¯ä¸¦è¡Œã—ã¦å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚タスクを委è²ã—ã¦ã‚‚ã“ã‚Œã¯å¤‰æ›´ã•ã‚Œãšã€åŒæ™‚実行ã®å•é¡Œï¼ˆè¤‡æ•°ã®ãƒ•ã‚©ãƒ¼ã‚¯ãŒåŒã˜ãƒ•ã‚¡ã‚¤ãƒ«ã«æ›¸ã込む）ã¯å‡¦ç†ã•ã‚Œã¾ã›ã‚“。最も一般的ã«ã¯ã€ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã®ãƒ›ã‚¹ãƒˆã«å§”ä»»ã•ã‚ŒãŸå˜ä¸€ã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’æ›´æ–°ã™ã‚‹ã¨ãã«ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ã¯ã“ã‚Œã®å½±éŸ¿ã‚’å—ã‘ã¾ã™ï¼ˆ``copy``ã€``template``〠ã¾ãŸã¯``lineinfile`` モジュールãªã©ï¼‰ã€‚ãれらã¯å¼•ã続ã並列フォーク（デフォルト㯠5）ã§å‹•ä½œã—ã€ç›¸äº’ã«ä¸Šæ›¸ãã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_delegation.rst:95 -msgid "This can be handled in several ways::" +#: ../../rst/user_guide/playbooks_delegation.rst:103 +msgid "This can be handled in several ways:" msgstr "ã“ã‚Œã¯è¤‡æ•°ã®æ–¹æ³•ã§å‡¦ç†ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_delegation.rst:102 +#: ../../rst/user_guide/playbooks_delegation.rst:112 msgid "By using an intermediate play with `serial: 1` or using `throttle: 1` at task level, for more detail see :ref:`playbooks_strategies`" msgstr "`serial: 1` ã§ä¸é–“プレイを使用ã™ã‚‹ã‹ã€ã‚¿ã‚¹ã‚¯ãƒ¬ãƒ™ãƒ«ã§ `throttle: 1` を使用ã—ã¾ã™ã€‚詳細ã¯ã€:ref:`playbooks_strategies`ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_delegation.rst:107 +#: ../../rst/user_guide/playbooks_delegation.rst:117 msgid "Delegating facts" msgstr "ファクトã®å§”è²" -#: ../../rst/user_guide/playbooks_delegation.rst:109 -msgid "Delegating Ansible tasks is like delegating tasks in the real world - your groceries belong to you, even if someone else delivers them to your home. Similarly, any facts gathered by a delegated task are assigned by default to the `inventory_hostname` (the current host), not to the host which produced the facts (the delegated to host). To assign gathered facts to the delegated host instead of the current host, set ``delegate_facts`` to ``true``::" +#: ../../rst/user_guide/playbooks_delegation.rst:119 +msgid "Delegating Ansible tasks is like delegating tasks in the real world - your groceries belong to you, even if someone else delivers them to your home. Similarly, any facts gathered by a delegated task are assigned by default to the `inventory_hostname` (the current host), not to the host which produced the facts (the delegated to host). To assign gathered facts to the delegated host instead of the current host, set ``delegate_facts`` to ``true``:" msgstr "Ansible ã®ã‚¿ã‚¹ã‚¯ã‚’委è²ã™ã‚‹ã“ã¨ã¯ã€ç¾å®Ÿä¸–ç•Œã§ã‚¿ã‚¹ã‚¯ã‚’委è²ã™ã‚‹ã“ã¨ã¨åŒã˜ã§ã™ã€‚ãŸã¨ãˆä»–ã®èª°ã‹ãŒã‚ãªãŸã®å®¶ã«é£Ÿæ–™å“を届ã‘ãŸã¨ã—ã¦ã‚‚ã€ã‚ãªãŸã®é£Ÿæ–™å“ã¯ã‚ãªãŸã®ã‚‚ã®ã§ã™ã€‚åŒæ§˜ã«ã€å§”è²ã•ã‚ŒãŸã‚¿ã‚¹ã‚¯ã«ã‚ˆã£ã¦åŽé›†ã•ã‚ŒãŸãƒ•ã‚¡ã‚¯ãƒˆã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã¯ã€ãƒ•ã‚¡ã‚¯ãƒˆã‚’生æˆã—ãŸãƒ›ã‚¹ãƒˆ (委è²ã•ã‚ŒãŸãƒ›ã‚¹ãƒˆ) ã§ã¯ãªãã€`inventory_hostname` (ç¾åœ¨ã®ãƒ›ã‚¹ãƒˆ) ã«å‰²ã‚Šå½“ã¦ã‚‰ã‚Œã¾ã™ã€‚集ã‚ãŸãƒ•ã‚¡ã‚¯ãƒˆã‚’ç¾åœ¨ã®ãƒ›ã‚¹ãƒˆã§ã¯ãªã委è²ã•ã‚ŒãŸãƒ›ã‚¹ãƒˆã«å‰²ã‚Šå½“ã¦ã‚‹ã«ã¯ã€``delegate_facts`` ã‚’ ``true`` ã«è¨å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_delegation.rst:121 +#: ../../rst/user_guide/playbooks_delegation.rst:133 msgid "This task gathers facts for the machines in the dbservers group and assigns the facts to those machines, even though the play targets the app_servers group. This way you can lookup `hostvars['dbhost1']['ansible_default_ipv4']['address']` even though dbservers were not part of the play, or left out by using `--limit`." msgstr "ã“ã®ã‚¿ã‚¹ã‚¯ã¯ã€ãƒ—レイ㌠app_servers グループを対象ã¨ã—ã¦ã„ã‚‹ã«ã‚‚ã‹ã‹ã‚らãšã€dbservers グループã®ãƒžã‚·ãƒ³ã®ãƒ•ã‚¡ã‚¯ãƒˆã‚’åŽé›†ã—ã€ãれらã®ãƒžã‚·ãƒ³ã«ãƒ•ã‚¡ã‚¯ãƒˆã‚’割り当ã¦ã¾ã™ã€‚ã“ã®ã‚ˆã†ã«ã—ã¦ã€ãŸã¨ãˆ dbservers ãŒãƒ—レイã®ä¸€éƒ¨ã§ãªãã¦ã‚‚ã€ã‚ã‚‹ã„㯠`--limit` を使用ã—ã¦é™¤å¤–ã•ã‚Œã¦ã„ã¦ã‚‚ã€`hostvars['dbhost1']['ansible_default_ipv4']['address']` を調ã¹ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_delegation.rst:126 +#: ../../rst/user_guide/playbooks_delegation.rst:138 msgid "Local playbooks" msgstr "ãƒãƒ¼ã‚«ãƒ«ã® Playbook" -#: ../../rst/user_guide/playbooks_delegation.rst:128 +#: ../../rst/user_guide/playbooks_delegation.rst:140 msgid "It may be useful to use a playbook locally on a remote host, rather than by connecting over SSH. This can be useful for assuring the configuration of a system by putting a playbook in a crontab. This may also be used to run a playbook inside an OS installer, such as an Anaconda kickstart." msgstr "SSH ã§æŽ¥ç¶šã™ã‚‹ã®ã§ã¯ãªãã€ãƒªãƒ¢ãƒ¼ãƒˆãƒ›ã‚¹ãƒˆä¸Šã§ãƒãƒ¼ã‚«ãƒ«ã« Playbook を使用ã™ã‚‹ã“ã¨ãŒä¾¿åˆ©ãªå ´åˆãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€crontab ã« Playbook ã‚’ç½®ãã“ã¨ã§ã€ã‚·ã‚¹ãƒ†ãƒ ã®æ§‹æˆã‚’ä¿è¨¼ã™ã‚‹ã®ã«å½¹ç«‹ã¡ã¾ã™ã€‚ã¾ãŸã€Anaconda ã®ã‚ックスタートãªã©ã€OS インストーラー内㧠Playbook を実行ã™ã‚‹å ´åˆã«ã‚‚使用ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_delegation.rst:131 -msgid "To run an entire playbook locally, just set the ``hosts:`` line to ``hosts: 127.0.0.1`` and then run the playbook like so::" +#: ../../rst/user_guide/playbooks_delegation.rst:143 +msgid "To run an entire playbook locally, just set the ``hosts:`` line to ``hosts: 127.0.0.1`` and then run the playbook like so:" msgstr "Playbook 全体をãƒãƒ¼ã‚«ãƒ«ã§å®Ÿè¡Œã™ã‚‹ã«ã¯ã€``hosts:`` 行を ``hosts: 127.0.0.1`` ã«è¨å®šã—ã€æ¬¡ã®ã‚ˆã†ã« Playbook を実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_delegation.rst:135 -msgid "Alternatively, a local connection can be used in a single playbook play, even if other plays in the playbook use the default remote connection type::" +#: ../../rst/user_guide/playbooks_delegation.rst:149 +msgid "Alternatively, a local connection can be used in a single playbook play, even if other plays in the playbook use the default remote connection type:" msgstr "ã¾ãŸã€Playbook 内ã®ä»–ã®ãƒ—レイãŒãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã®ãƒªãƒ¢ãƒ¼ãƒˆæŽ¥ç¶šã‚¿ã‚¤ãƒ—を使用ã—ã¦ã„ã¦ã‚‚ã€1 ã¤ã® Playbook ã®ãƒ—レイã§ãƒãƒ¼ã‚«ãƒ«æŽ¥ç¶šã‚’使用ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_delegation.rst:143 +#: ../../rst/user_guide/playbooks_delegation.rst:159 msgid "If you set the connection to local and there is no ansible_python_interpreter set, modules will run under /usr/bin/python and not under {{ ansible_playbook_python }}. Be sure to set ansible_python_interpreter: \"{{ ansible_playbook_python }}\" in host_vars/localhost.yml, for example. You can avoid this issue by using ``local_action`` or ``delegate_to: localhost`` instead." msgstr "接続先をãƒãƒ¼ã‚«ãƒ«ã«è¨å®šã—ã€ansible_python_interpreter ãŒè¨å®šã•ã‚Œã¦ã„ãªã„ã¨ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€{{ ansible_playbook_python }} ã§ã¯ãªã /usr/bin/python ã§å®Ÿè¡Œã—ã¾ã™ã€‚ansible_python_interpreter ã‚’å¿…ãšè¨å®šã—ã¦ãã ã•ã„ (host_vars/localhost.yml ã®ã€Œ{{ ansible_playbook_python }}ã€ãªã©)。代ã‚ã‚Šã« ``local_action`` ã¾ãŸã¯ ``delegate_to: localhost`` を使用ã™ã‚‹ã“ã¨ã§ã€ã“ã®å•é¡Œã‚’回é¿ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_delegation.rst:152 +#: ../../rst/user_guide/playbooks_delegation.rst:168 msgid "More ways to control how and where Ansible executes" msgstr "Ansible ã®å®Ÿè¡Œæ–¹æ³•ãŠã‚ˆã³å ´æ‰€ã‚’制御ã™ã‚‹æ–¹æ³•" -#: ../../rst/user_guide/playbooks_delegation.rst:153 +#: ../../rst/user_guide/playbooks_delegation.rst:169 msgid "`Ansible Examples on GitHub <https://github.com/ansible/ansible-examples>`_" msgstr "`Ansible Examples on GitHub <https://github.com/ansible/ansible-examples>`_" -#: ../../rst/user_guide/playbooks_delegation.rst:154 +#: ../../rst/user_guide/playbooks_delegation.rst:170 msgid "Many examples of full-stack deployments" msgstr "フルスタックデプãƒã‚¤ãƒ¡ãƒ³ãƒˆã®ä¾‹ãŒå¤šæ•°ã‚ã‚Šã¾ã™ã€‚" @@ -5655,43 +5650,43 @@ msgid "Setting the remote environment in a task" msgstr "タスクã¸ã®ãƒªãƒ¢ãƒ¼ãƒˆç’°å¢ƒã®è¨å®š" #: ../../rst/user_guide/playbooks_environment.rst:18 -msgid "You can set the environment directly at the task level::" +msgid "You can set the environment directly at the task level." msgstr "タスクレベルã§ç’°å¢ƒã‚’直接指定ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_environment.rst:32 -msgid "You can re-use environment settings by defining them as variables in your play and accessing them in a task as you would access any stored Ansible variable::" +#: ../../rst/user_guide/playbooks_environment.rst:34 +msgid "You can re-use environment settings by defining them as variables in your play and accessing them in a task as you would access any stored Ansible variable." msgstr "環境変数をプレイã®å¤‰æ•°ã¨ã—ã¦å®šç¾©ã—ã€ä¿å˜ã—㟠Ansible 変数ã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ã¨ãã«ã‚¿ã‚¹ã‚¯ã‹ã‚‰ã‚¢ã‚¯ã‚»ã‚¹ã§ãã‚‹ã“ã¨ã§ã€ç’°å¢ƒå¤‰æ•°ã‚’å†åˆ©ç”¨ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_environment.rst:50 -msgid "You can store environment settings for re-use in multiple playbooks by defining them in a group_vars file::" +#: ../../rst/user_guide/playbooks_environment.rst:54 +msgid "You can store environment settings for re-use in multiple playbooks by defining them in a group_vars file." msgstr "複数㮠Playbook ã«å†ä½¿ç”¨ã™ã‚‹ç’°å¢ƒè¨å®šã¯ã€group_vars ファイルã«å®šç¾©ã™ã‚‹ã“ã¨ã§ä¿å˜ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_environment.rst:61 -msgid "You can set the remote environment at the play level::" +#: ../../rst/user_guide/playbooks_environment.rst:67 +msgid "You can set the remote environment at the play level." msgstr "プレイレベルã§ãƒªãƒ¢ãƒ¼ãƒˆç’°å¢ƒã‚’è¨å®šã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_environment.rst:72 +#: ../../rst/user_guide/playbooks_environment.rst:80 msgid "These examples show proxy settings, but you can provide any number of settings this way." msgstr "ã“れらã®ä¾‹ã§ã¯ãƒ—ãƒã‚シーè¨å®šã‚’示ã—ã¦ã„ã¾ã™ãŒã€ã“ã®è¨å®šã‚’ã„ãã¤ã§ã‚‚æä¾›ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_environment.rst:75 +#: ../../rst/user_guide/playbooks_environment.rst:83 msgid "Working with language-specific version managers" msgstr "言語固有ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãƒžãƒãƒ¼ã‚¸ãƒ£ãƒ¼ã®ä½¿ç”¨" -#: ../../rst/user_guide/playbooks_environment.rst:77 -msgid "Some language-specific version managers (such as rbenv and nvm) require you to set environment variables while these tools are in use. When using these tools manually, you usually source some environment variables from a script or from lines added to your shell configuration file. In Ansible, you can do this with the environment keyword at the play level::" +#: ../../rst/user_guide/playbooks_environment.rst:85 +msgid "Some language-specific version managers (such as rbenv and nvm) require you to set environment variables while these tools are in use. When using these tools manually, you usually source some environment variables from a script or from lines added to your shell configuration file. In Ansible, you can do this with the environment keyword at the play level." msgstr "言語固有ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãƒžãƒãƒ¼ã‚¸ãƒ£ãƒ¼ (rbenv ã‚„ nvmãªã©) ã®ä¸ã«ã¯ã€ã“れらã®ãƒ„ールを使用ã™ã‚‹éš›ã«ç’°å¢ƒå¤‰æ•°ã‚’è¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“れらã®ãƒ„ールを手動ã§ä½¿ç”¨ã™ã‚‹å ´åˆã€é€šå¸¸ã¯ã‚¹ã‚¯ãƒªãƒ—トやシェル構æˆãƒ•ã‚¡ã‚¤ãƒ«ã«è¿½åŠ ã—ãŸè¡Œã‹ã‚‰ç’°å¢ƒå¤‰æ•°ã‚’è¨å®šã—ã¾ã™ã€‚Ansible ã§ã¯ã€ãƒ—レイレベルã§ç’°å¢ƒã‚ーワードを使用ã—ã¦ã“れを行ã†ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_environment.rst:114 +#: ../../rst/user_guide/playbooks_environment.rst:124 msgid "The example above uses ``ansible_env`` as part of the PATH. Basing variables on ``ansible_env`` is risky. Ansible populates ``ansible_env`` values by gathering facts, so the value of the variables depends on the remote_user or become_user Ansible used when gathering those facts. If you change remote_user/become_user the values in ``ansible-env`` may not be the ones you expect." msgstr "上ã®ä¾‹ã§ã¯ã€``ansible_env`` ã‚’ PATH ã®ä¸€éƒ¨ã¨ã—ã¦ä½¿ç”¨ã—ã¦ã„ã¾ã™ã€‚変数を ``ansible_env`` ã«åŸºã¥ã‹ã›ã‚‹ã®ã¯ãƒªã‚¹ã‚¯ãŒã‚ã‚Šã¾ã™ã€‚Ansible ã¯ãƒ•ã‚¡ã‚¯ãƒˆã‚’åŽé›†ã—㦠``ansible_env`` ã®å€¤ã‚’生æˆã™ã‚‹ãŸã‚ã€å¤‰æ•°ã®å€¤ã¯ãƒ•ã‚¡ã‚¯ãƒˆã®åŽé›†æ™‚ã« Ansible ãŒä½¿ç”¨ã—㟠remote_user ã‚„ become_user ã«ä¾å˜ã—ã¾ã™ã€‚remote_user/become_user を変更ã—ãŸå ´åˆã€``ansible-env`` ã®å€¤ã¯æœŸå¾…ã—ãŸã‚‚ã®ã¨ã¯ç•°ãªã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_environment.rst:117 +#: ../../rst/user_guide/playbooks_environment.rst:127 msgid "Environment variables are normally passed in clear text (shell plugin dependent) so they are not a recommended way of passing secrets to the module being executed." msgstr "環境変数ã¯ã€é€šå¸¸ã€(シェルプラグインã«ä¾å˜ã™ã‚‹) クリアテã‚ストã«æ¸¡ã•ã‚Œã¾ã™ã€‚ã—ãŸãŒã£ã¦ã€å®Ÿè¡Œã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã‚·ãƒ¼ã‚¯ãƒ¬ãƒƒãƒˆã‚’渡ã™æ–¹æ³•ã¯æŽ¨å¥¨ã•ã‚Œã¾ã›ã‚“。" -#: ../../rst/user_guide/playbooks_environment.rst:119 -msgid "You can also specify the environment at the task level::" +#: ../../rst/user_guide/playbooks_environment.rst:129 +msgid "You can also specify the environment at the task level." msgstr "タスクレベルã§ç’°å¢ƒã‚’指定ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" #: ../../rst/user_guide/playbooks_error_handling.rst:5 @@ -5707,170 +5702,170 @@ msgid "Ignoring failed commands" msgstr "失敗ã—ãŸã‚³ãƒžãƒ³ãƒ‰ã®ç„¡è¦–" #: ../../rst/user_guide/playbooks_error_handling.rst:17 -msgid "By default Ansible stops executing tasks on a host when a task fails on that host. You can use ``ignore_errors`` to continue on in spite of the failure::" +msgid "By default Ansible stops executing tasks on a host when a task fails on that host. You can use ``ignore_errors`` to continue on in spite of the failure." msgstr "デフォルトã§ã¯ã€Ansible ã¯ã€ãƒ›ã‚¹ãƒˆã§ã‚¿ã‚¹ã‚¯ãŒå¤±æ•—ã™ã‚‹ã¨ã€ãƒ›ã‚¹ãƒˆã§ã‚¿ã‚¹ã‚¯ã®å®Ÿè¡Œã‚’åœæ¢ã—ã¾ã™ã€‚``ignore_errors`` を使用ã™ã‚‹ã¨ã€éšœå®³ãŒç™ºç”Ÿã—ã¦ã‚‚続行ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:23 +#: ../../rst/user_guide/playbooks_error_handling.rst:25 msgid "The ``ignore_errors`` directive only works when the task is able to run and returns a value of 'failed'. It does not make Ansible ignore undefined variable errors, connection failures, execution issues (for example, missing packages), or syntax errors." msgstr "``ignore_errors`` ディレクティブã¯ã€ã‚¿ã‚¹ã‚¯ãŒå®Ÿè¡Œå¯èƒ½ã§ã€ã€Œfailedã€ã¨ã„ã†å€¤ã‚’è¿”ã™å ´åˆã«ã®ã¿æ©Ÿèƒ½ã—ã¾ã™ã€‚未定義ã®å¤‰æ•°ã®ã‚¨ãƒ©ãƒ¼ã€æŽ¥ç¶šã®å¤±æ•—ã€å®Ÿè¡Œæ™‚ã®å•é¡Œ (パッケージã®æ¬ è½ãªã©)ã€æ§‹æ–‡ã‚¨ãƒ©ãƒ¼ãªã©ã‚’ Ansible ã«ç„¡è¦–ã•ã›ã‚‹ã‚‚ã®ã§ã¯ã‚ã‚Šã¾ã›ã‚“。" -#: ../../rst/user_guide/playbooks_error_handling.rst:26 +#: ../../rst/user_guide/playbooks_error_handling.rst:28 msgid "Ignoring unreachable host errors" msgstr "到é”ä¸èƒ½ãªãƒ›ã‚¹ãƒˆã‚¨ãƒ©ãƒ¼ã‚’無視" -#: ../../rst/user_guide/playbooks_error_handling.rst:30 -msgid "You can ignore a task failure due to the host instance being 'UNREACHABLE' with the ``ignore_unreachable`` keyword. Ansible ignores the task errors, but continues to execute future tasks against the unreachable host. For example, at the task level::" +#: ../../rst/user_guide/playbooks_error_handling.rst:32 +msgid "You can ignore a task failure due to the host instance being 'UNREACHABLE' with the ``ignore_unreachable`` keyword. Ansible ignores the task errors, but continues to execute future tasks against the unreachable host. For example, at the task level:" msgstr "``ignore_unreachable`` ã‚ーワードã§ã€ãƒ›ã‚¹ãƒˆã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ãŒã€ŒUNREACHABLEã€ã§ã‚ã‚‹ã“ã¨ã«ã‚ˆã‚‹ã‚¿ã‚¹ã‚¯ã®å¤±æ•—を無視ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚Ansible ã¯ã‚¿ã‚¹ã‚¯ã®ã‚¨ãƒ©ãƒ¼ã‚’無視ã—ã¾ã™ãŒã€åˆ°é”ä¸å¯èƒ½ãªãƒ›ã‚¹ãƒˆã«å¯¾ã—ã¦ä»Šå¾Œã®ã‚¿ã‚¹ã‚¯ã‚’実行ã—続ã‘ã¾ã™ã€‚ãŸã¨ãˆã°ã€ã‚¿ã‚¹ã‚¯ãƒ¬ãƒ™ãƒ«ã§ã¯ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:39 -msgid "And at the playbook level::" +#: ../../rst/user_guide/playbooks_error_handling.rst:43 +msgid "And at the playbook level:" msgstr "ã¾ãŸã€Playbook レベルã§ã¯ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:54 +#: ../../rst/user_guide/playbooks_error_handling.rst:60 msgid "Resetting unreachable hosts" msgstr "到é”ã§ããªã„ホストã®ãƒªã‚»ãƒƒãƒˆ" -#: ../../rst/user_guide/playbooks_error_handling.rst:56 +#: ../../rst/user_guide/playbooks_error_handling.rst:62 msgid "If Ansible cannot connect to a host, it marks that host as 'UNREACHABLE' and removes it from the list of active hosts for the run. You can use `meta: clear_host_errors` to reactivate all hosts, so subsequent tasks can try to reach them again." msgstr "Ansible ã¯ãƒ›ã‚¹ãƒˆã«æŽ¥ç¶šã§ããªã„å ´åˆã€ãã®ãƒ›ã‚¹ãƒˆã‚’「UNREACHABLEã€ã¨ãƒžãƒ¼ã‚¯ã—ã€å®Ÿè¡Œæ™‚ã«ã‚¢ã‚¯ãƒ†ã‚£ãƒ–ãªãƒ›ã‚¹ãƒˆã®ãƒªã‚¹ãƒˆã‹ã‚‰å‰Šé™¤ã—ã¾ã™ã€‚`meta: clear_host_errors` を使用ã—ã¦ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã‚’å†æœ‰åŠ¹åŒ–ã™ã‚‹ã“ã¨ã§ã€å¾Œç¶šã®ã‚¿ã‚¹ã‚¯ãŒå†ã³ãƒ›ã‚¹ãƒˆã«åˆ°é”ã—よã†ã¨ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:62 +#: ../../rst/user_guide/playbooks_error_handling.rst:68 msgid "Handlers and failure" msgstr "ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ãŠã‚ˆã³å¤±æ•—" -#: ../../rst/user_guide/playbooks_error_handling.rst:64 +#: ../../rst/user_guide/playbooks_error_handling.rst:70 msgid "Ansible runs :ref:`handlers <handlers>` at the end of each play. If a task notifies a handler but another task fails later in the play, by default the handler does *not* run on that host, which may leave the host in an unexpected state. For example, a task could update a configuration file and notify a handler to restart some service. If a task later in the same play fails, the configuration file might be changed but the service will not be restarted." msgstr "Ansible ã¯ã€å„プレイã®æœ€å¾Œã« :ref:`handlers <handlers>` を実行ã—ã¾ã™ã€‚タスクãŒãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã«é€šçŸ¥ã—ã¦ã‚‚ã€ãƒ—レイã®å¾ŒåŠã§åˆ¥ã®ã‚¿ã‚¹ã‚¯ãŒå¤±æ•—ã™ã‚‹ã¨ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã¯ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã¯ãã®ãƒ›ã‚¹ãƒˆä¸Šã§ **実行ã•ã‚Œãš**ã€ãƒ›ã‚¹ãƒˆãŒäºˆæœŸã›ã¬çŠ¶æ…‹ã«ãªã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€ã‚¿ã‚¹ã‚¯ãŒè¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã‚’æ›´æ–°ã—ã€ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã«ã‚µãƒ¼ãƒ“スã®å†èµ·å‹•ã‚’通知ã—ãŸã¨ã—ã¾ã™ã€‚åŒã˜ãƒ—レイã®å¾ŒåŠã§ã‚¿ã‚¹ã‚¯ãŒå¤±æ•—ã—ãŸå ´åˆã€è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã¯å¤‰æ›´ã™ã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“ãŒã€ã‚µãƒ¼ãƒ“スã¯å†èµ·å‹•ã—ã¾ã›ã‚“。" -#: ../../rst/user_guide/playbooks_error_handling.rst:71 +#: ../../rst/user_guide/playbooks_error_handling.rst:77 msgid "You can change this behavior with the ``--force-handlers`` command-line option, by including ``force_handlers: True`` in a play, or by adding ``force_handlers = True`` to ansible.cfg. When handlers are forced, Ansible will run all notified handlers on all hosts, even hosts with failed tasks. (Note that certain errors could still prevent the handler from running, such as a host becoming unreachable.)" msgstr "ã“ã®å‹•ä½œã¯ã€``force_handlers: True`` をプレイã«å«ã‚ã‚‹ã‹ã€``force_handlers = True`` ã‚’ ansible.cfg ã«è¿½åŠ ã—ã¦ã€``--force-handlers`` コマンドラインオプションã§å¤‰æ›´ã§ãã¾ã™ã€‚ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ãŒå¼·åˆ¶çš„ã«å®Ÿè¡Œã™ã‚‹ã¨ã€Ansible ã¯é€šçŸ¥ã•ã‚ŒãŸã™ã¹ã¦ã®ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã‚’ã€ã‚¿ã‚¹ã‚¯ãŒå¤±æ•—ã—ãŸãƒ›ã‚¹ãƒˆã‚‚å«ã‚ã¦ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã§å®Ÿè¡Œã—ã¾ã™ (ホストãŒåˆ°é”ä¸èƒ½ã«ãªã‚‹ãªã©ã€ç‰¹å®šã®ã‚¨ãƒ©ãƒ¼ã«ã‚ˆã£ã¦ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã®å®Ÿè¡ŒãŒå¦¨ã’られるå¯èƒ½æ€§ãŒã‚ã‚‹ã“ã¨ã«æ³¨æ„ã—ã¦ãã ã•ã„)。" -#: ../../rst/user_guide/playbooks_error_handling.rst:80 +#: ../../rst/user_guide/playbooks_error_handling.rst:86 msgid "Defining failure" msgstr "障害ã®å®šç¾©" -#: ../../rst/user_guide/playbooks_error_handling.rst:82 +#: ../../rst/user_guide/playbooks_error_handling.rst:88 msgid "Ansible lets you define what \"failure\" means in each task using the ``failed_when`` conditional. As with all conditionals in Ansible, lists of multiple ``failed_when`` conditions are joined with an implicit ``and``, meaning the task only fails when *all* conditions are met. If you want to trigger a failure when any of the conditions is met, you must define the conditions in a string with an explicit ``or`` operator." msgstr "Ansible ã§ã¯ã€``failed_when`` æ¡ä»¶åˆ†å²ã‚’使用ã—ã¦ã€å„タスクã§ã€Œå¤±æ•—ã€ã®æ„味を定義ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚Ansible ã®ã™ã¹ã¦ã®æ¡ä»¶åˆ†å²ã¨åŒæ§˜ã«ã€è¤‡æ•°ã® ``failed_when`` æ¡ä»¶ã®ãƒªã‚¹ãƒˆã¯æš—黙㮠``and`` ã§çµåˆã•ã‚Œã¦ãŠã‚Šã€ã“れ㯠*ã™ã¹ã¦ã®* æ¡ä»¶ãŒæº€ãŸã•ã‚ŒãŸã¨ãã«ã®ã¿ã‚¿ã‚¹ã‚¯ãŒå¤±æ•—ã™ã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚ã„ãšã‚Œã‹ã®æ¡ä»¶ãŒæº€ãŸã•ã‚ŒãŸã¨ãã«å¤±æ•—をトリガーã—ãŸã„å ´åˆã¯ã€æ˜Žç¤ºçš„㪠``or`` 演算åを使用ã—ã¦æ–‡å—列ã§æ¡ä»¶ã‚’定義ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:84 -msgid "You may check for failure by searching for a word or phrase in the output of a command::" +#: ../../rst/user_guide/playbooks_error_handling.rst:90 +msgid "You may check for failure by searching for a word or phrase in the output of a command" msgstr "コマンドã®å‡ºåŠ›ã§å˜èªžã¾ãŸã¯ãƒ•ãƒ¬ãƒ¼ã‚ºã‚’検索ã—ã¦ã€éšœå®³ã®æœ‰ç„¡ã‚’確èªã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:91 -msgid "or based on the return code::" +#: ../../rst/user_guide/playbooks_error_handling.rst:99 +msgid "or based on the return code" msgstr "ã¾ãŸã¯ã€æˆ»ã‚Šã‚³ãƒ¼ãƒ‰ã«åŸºã„ã¦ç¢ºèªã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:98 -msgid "You can also combine multiple conditions for failure. This task will fail if both conditions are true::" +#: ../../rst/user_guide/playbooks_error_handling.rst:108 +msgid "You can also combine multiple conditions for failure. This task will fail if both conditions are true:" msgstr "複数ã®æ¡ä»¶ã‚’組ã¿åˆã‚ã›ã¦å¤±æ•—ã•ã›ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚ã“ã®ã‚¿ã‚¹ã‚¯ã¯ã€ä¸¡æ–¹ã®æ¡ä»¶ãŒçœŸã§ã‚ã‚Œã°å¤±æ•—ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:107 -msgid "If you want the task to fail when only one condition is satisfied, change the ``failed_when`` definition to::" +#: ../../rst/user_guide/playbooks_error_handling.rst:119 +msgid "If you want the task to fail when only one condition is satisfied, change the ``failed_when`` definition to" msgstr "æ¡ä»¶ãŒæº€ãŸã•ã‚ŒãŸã¨ãã«ã®ã¿ã‚¿ã‚¹ã‚¯ãŒå¤±æ•—ã™ã‚‹å ´åˆã¯ã€``failed_when`` 定義を以下ã®ã‚ˆã†ã«å¤‰æ›´ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:111 -msgid "If you have too many conditions to fit neatly into one line, you can split it into a multi-line yaml value with ``>``::" -msgstr "æ¡ä»¶ãŒå¤šã™ãŽã¦ 1 è¡Œã«ã†ã¾ãåŽã¾ã‚‰ãªã„å ´åˆã¯ã€``>`` を使用ã—ã¦ã€ã“れを複数行㮠yaml 値ã«åˆ†å‰²ã§ãã¾ã™ã€‚" +#: ../../rst/user_guide/playbooks_error_handling.rst:125 +msgid "If you have too many conditions to fit neatly into one line, you can split it into a multi-line YAML value with ``>``." +msgstr "æ¡ä»¶ãŒå¤šã™ãŽã¦ 1 è¡Œã«ã†ã¾ãåŽã¾ã‚‰ãªã„å ´åˆã¯ã€``>`` を使用ã—ã¦ã€ã“れを複数行㮠YAML 値ã«åˆ†å‰²ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:124 +#: ../../rst/user_guide/playbooks_error_handling.rst:140 msgid "Defining \"changed\"" msgstr "「変更済ã¿ã€ã®å®šç¾©" -#: ../../rst/user_guide/playbooks_error_handling.rst:126 -msgid "Ansible lets you define when a particular task has \"changed\" a remote node using the ``changed_when`` conditional. This lets you determine, based on return codes or output, whether a change should be reported in Ansible statistics and whether a handler should be triggered or not. As with all conditionals in Ansible, lists of multiple ``changed_when`` conditions are joined with an implicit ``and``, meaning the task only reports a change when *all* conditions are met. If you want to report a change when any of the conditions is met, you must define the conditions in a string with an explicit ``or`` operator. For example::" +#: ../../rst/user_guide/playbooks_error_handling.rst:142 +msgid "Ansible lets you define when a particular task has \"changed\" a remote node using the ``changed_when`` conditional. This lets you determine, based on return codes or output, whether a change should be reported in Ansible statistics and whether a handler should be triggered or not. As with all conditionals in Ansible, lists of multiple ``changed_when`` conditions are joined with an implicit ``and``, meaning the task only reports a change when *all* conditions are met. If you want to report a change when any of the conditions is met, you must define the conditions in a string with an explicit ``or`` operator. For example:" msgstr "Ansible ã§ã¯ã€``changed_when`` æ¡ä»¶å¼ã‚’使用ã—ã¦ã€ç‰¹å®šã®ã‚¿ã‚¹ã‚¯ãŒãƒªãƒ¢ãƒ¼ãƒˆãƒŽãƒ¼ãƒ‰ã‚’「変更ã€ã—ãŸã¨ãを定義ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€æˆ»ã‚Šã‚³ãƒ¼ãƒ‰ã‚„出力ã«åŸºã¥ã„ã¦ã€å¤‰æ›´ã‚’ Ansible ã®çµ±è¨ˆã§å ±å‘Šã™ã‚‹ã‹ã©ã†ã‹ã€ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã‚’トリガーã™ã‚‹ã‹ã©ã†ã‹ã‚’決定ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚Ansible ã®ã™ã¹ã¦ã®æ¡ä»¶å¼ã¨åŒæ§˜ã«ã€è¤‡æ•°ã® ``changed_when`` æ¡ä»¶ã®ãƒªã‚¹ãƒˆã¯æš—黙㮠``and`` ã§çµåˆã•ã‚Œã¦ãŠã‚Šã€ã‚¿ã‚¹ã‚¯ã¯ *ã™ã¹ã¦ã®* æ¡ä»¶ãŒæº€ãŸã•ã‚ŒãŸã¨ãã«ã®ã¿å¤‰æ›´ã‚’å ±å‘Šã™ã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚ã„ãšã‚Œã‹ã®æ¡ä»¶ãŒæº€ãŸã•ã‚ŒãŸã¨ãã«å¤‰æ›´ã‚’å ±å‘Šã—ãŸã„å ´åˆã¯ã€æ˜Žç¤ºçš„㪠``or`` 演算åを使用ã—ã¦æ–‡å—列ã§æ¡ä»¶ã‚’定義ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:139 -msgid "You can also combine multiple conditions to override \"changed\" result::" +#: ../../rst/user_guide/playbooks_error_handling.rst:157 +msgid "You can also combine multiple conditions to override \"changed\" result." msgstr "複数ã®æ¡ä»¶ã‚’組ã¿åˆã‚ã›ã¦ã€Œå¤‰æ›´ã€ã®çµæžœã‚’上書ãã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:149 +#: ../../rst/user_guide/playbooks_error_handling.rst:169 msgid "See :ref:`controlling_what_defines_failure` for more conditional syntax examples." msgstr "ãã®ä»–ã®æ¡ä»¶ä»˜ã構文例ã«ã¤ã„ã¦ã¯ã€ã€Œ:ref:`controlling_what_defines_failure`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_error_handling.rst:152 +#: ../../rst/user_guide/playbooks_error_handling.rst:172 msgid "Ensuring success for command and shell" msgstr "コマンドã¨ã‚·ã‚§ãƒ«ã®æˆåŠŸã®ç¢ºèª" -#: ../../rst/user_guide/playbooks_error_handling.rst:154 -msgid "The :ref:`command <command_module>` and :ref:`shell <shell_module>` modules care about return codes, so if you have a command whose successful exit code is not zero, you can do this::" +#: ../../rst/user_guide/playbooks_error_handling.rst:174 +msgid "The :ref:`command <command_module>` and :ref:`shell <shell_module>` modules care about return codes, so if you have a command whose successful exit code is not zero, you can do this:" msgstr ":ref:`command <command_module>` モジュールãŠã‚ˆã³ :ref:`shell <shell_module>` モジュールã¯æˆ»ã‚Šã‚³ãƒ¼ãƒ‰ã‚’処ç†ã™ã‚‹ãŸã‚ã€æ£å¸¸ãªçµ‚了コードãŒã‚¼ãƒã§ã¯ãªã„コマンドãŒã‚ã‚‹å ´åˆã¯ã€ä»¥ä¸‹ã‚’è¡Œã†ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:162 +#: ../../rst/user_guide/playbooks_error_handling.rst:184 msgid "Aborting a play on all hosts" msgstr "ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã§ãƒ—レイをä¸æ¢" -#: ../../rst/user_guide/playbooks_error_handling.rst:164 +#: ../../rst/user_guide/playbooks_error_handling.rst:186 msgid "Sometimes you want a failure on a single host, or failures on a certain percentage of hosts, to abort the entire play on all hosts. You can stop play execution after the first failure happens with ``any_errors_fatal``. For finer-grained control, you can use ``max_fail_percentage`` to abort the run after a given percentage of hosts has failed." msgstr "時ã«ã¯ã€1 ã¤ã®ãƒ›ã‚¹ãƒˆã§ã®å¤±æ•—ã‚„ã€ã‚る割åˆã®ãƒ›ã‚¹ãƒˆã§ã®å¤±æ•—ã«ã‚ˆã‚Šã€ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã§ã®ãƒ—レイ全体をä¸æ¢ã•ã›ãŸã„ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚``any_errors_fatal`` を使用ã™ã‚‹ã¨ã€æœ€åˆã®å¤±æ•—ãŒç™ºç”Ÿã—ãŸå¾Œã«ãƒ—レイã®å®Ÿè¡Œã‚’åœæ¢ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚より細ã‹ã制御ã™ã‚‹ã«ã¯ã€``max_fail_percentage`` を使用ã—ã¦ã€ç‰¹å®šã®å‰²åˆã®ãƒ›ã‚¹ãƒˆã§å¤±æ•—ã—ãŸå¾Œã«å®Ÿè¡Œã‚’ä¸æ¢ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:167 +#: ../../rst/user_guide/playbooks_error_handling.rst:189 msgid "Aborting on the first error: any_errors_fatal" msgstr "最åˆã®ã‚¨ãƒ©ãƒ¼ã§å¼·åˆ¶çµ‚了: any_errors_fatal" -#: ../../rst/user_guide/playbooks_error_handling.rst:169 -msgid "If you set ``any_errors_fatal`` and a task returns an error, Ansible finishes the fatal task on all hosts in the current batch, then stops executing the play on all hosts. Subsequent tasks and plays are not executed. You can recover from fatal errors by adding a :ref:`rescue section <block_error_handling>` to the block. You can set ``any_errors_fatal`` at the play or block level::" +#: ../../rst/user_guide/playbooks_error_handling.rst:191 +msgid "If you set ``any_errors_fatal`` and a task returns an error, Ansible finishes the fatal task on all hosts in the current batch, then stops executing the play on all hosts. Subsequent tasks and plays are not executed. You can recover from fatal errors by adding a :ref:`rescue section <block_error_handling>` to the block. You can set ``any_errors_fatal`` at the play or block level." msgstr "``any_errors_fatal`` ã‚’è¨å®šã—ã€ã‚¿ã‚¹ã‚¯ãŒã‚¨ãƒ©ãƒ¼ã‚’è¿”ã—ãŸå ´åˆã€Ansible ã¯ç¾åœ¨ã®ãƒãƒƒãƒå†…ã®ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã§è‡´å‘½çš„ãªã‚¿ã‚¹ã‚¯ã‚’終了ã—ã€ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã§ãƒ—レイã®å®Ÿè¡Œã‚’åœæ¢ã—ã¾ã™ã€‚後続ã®ã‚¿ã‚¹ã‚¯ã‚„プレイã¯å®Ÿè¡Œã•ã‚Œã¾ã›ã‚“。致命的ãªã‚¨ãƒ©ãƒ¼ã‹ã‚‰å›žå¾©ã™ã‚‹ã«ã¯ã€ãƒ–ãƒãƒƒã‚¯ã« :ref:`rescue section <block_error_handling>` ã‚’è¿½åŠ ã—ã¾ã™ã€‚``any_errors_fatal`` ã¯ã€ãƒ—レイã¾ãŸã¯ãƒ–ãƒãƒƒã‚¯ãƒ¬ãƒ™ãƒ«ã§è¨å®šã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:182 -#, python-format -msgid "You can use this feature when all tasks must be 100% successful to continue playbook execution. For example, if you run a service on machines in multiple data centers with load balancers to pass traffic from users to the service, you want all load balancers to be disabled before you stop the service for maintenance. To ensure that any failure in the task that disables the load balancers will stop all other tasks::" +#: ../../rst/user_guide/playbooks_error_handling.rst:206 +#, fuzzy, python-format +msgid "You can use this feature when all tasks must be 100% successful to continue playbook execution. For example, if you run a service on machines in multiple data centers with load balancers to pass traffic from users to the service, you want all load balancers to be disabled before you stop the service for maintenance. To ensure that any failure in the task that disables the load balancers will stop all other tasks:" msgstr "ã“ã®æ©Ÿèƒ½ã¯ã€Playbook ã®å®Ÿè¡Œã‚’継続ã™ã‚‹ãŸã‚ã«ã€ã™ã¹ã¦ã®ã‚¿ã‚¹ã‚¯ãŒ 100ï¼… æˆåŠŸã™ã‚‹å¿…è¦ãŒã‚ã‚‹å ´åˆã«ä½¿ç”¨ã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€è¤‡æ•°ã®ãƒ‡ãƒ¼ã‚¿ã‚»ãƒ³ã‚¿ãƒ¼ã«ã‚るマシンã§ã‚µãƒ¼ãƒ“スを実行ã—ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‹ã‚‰ã®ãƒˆãƒ©ãƒ•ã‚£ãƒƒã‚¯ã‚’サービスã«æ¸¡ã™ãŸã‚ã«ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚µãƒ¼ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ã®ãŸã‚ã«ã‚µãƒ¼ãƒ“スをåœæ¢ã™ã‚‹å‰ã«ã€ã™ã¹ã¦ã®ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚µãƒ¼ã‚’無効ã«ã—ã¾ã™ã€‚ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚µãƒ¼ã‚’無効ã«ã™ã‚‹ã‚¿ã‚¹ã‚¯ã«éšœå®³ãŒç™ºç”Ÿã—ã¦ã‚‚ã€ä»–ã®ã™ã¹ã¦ã®ã‚¿ã‚¹ã‚¯ã‚’åœæ¢ã•ã›ã‚‹ã«ã¯ã€æ¬¡ã®ã‚ˆã†ã«ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:207 +#: ../../rst/user_guide/playbooks_error_handling.rst:233 msgid "In this example Ansible starts the software upgrade on the front ends only if all of the load balancers are successfully disabled." msgstr "ã“ã®ä¾‹ã§ã¯ã€ã™ã¹ã¦ã®ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚µãƒ¼ãŒæ£å¸¸ã«ç„¡åŠ¹ã«ãªã£ã¦ã„ã‚‹å ´åˆã«ã®ã¿ã€Ansible ãŒã€ãƒ•ãƒãƒ³ãƒˆã‚¨ãƒ³ãƒ‰ã§ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ã®ã‚¢ãƒƒãƒ—グレードを開始ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:212 +#: ../../rst/user_guide/playbooks_error_handling.rst:238 msgid "Setting a maximum failure percentage" msgstr "最大失敗率ã®è¨å®š" -#: ../../rst/user_guide/playbooks_error_handling.rst:214 -msgid "By default, Ansible continues to execute tasks as long as there are hosts that have not yet failed. In some situations, such as when executing a rolling update, you may want to abort the play when a certain threshold of failures has been reached. To achieve this, you can set a maximum failure percentage on a play::" +#: ../../rst/user_guide/playbooks_error_handling.rst:240 +msgid "By default, Ansible continues to execute tasks as long as there are hosts that have not yet failed. In some situations, such as when executing a rolling update, you may want to abort the play when a certain threshold of failures has been reached. To achieve this, you can set a maximum failure percentage on a play:" msgstr "デフォルトã§ã¯ã€Ansible ã¯ã¾ã 失敗ã—ã¦ã„ãªã„ホストãŒã‚ã‚‹é™ã‚Šã€ã‚¿ã‚¹ã‚¯ã‚’実行ã—続ã‘ã¾ã™ã€‚ãƒãƒ¼ãƒªãƒ³ã‚°ã‚¢ãƒƒãƒ—デートを実行ã™ã‚‹å ´åˆãªã©ã€ã‚る一定ã®å¤±æ•—率ã«é”ã—ãŸã¨ãã«ãƒ—レイをä¸æ–ã—ãŸã„å ´åˆãŒã‚ã‚Šã¾ã™ã€‚ã“れをå¯èƒ½ã«ã™ã‚‹ã«ã¯ã€ãƒ—レイã®æœ€å¤§å¤±æ•—率をè¨å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:221 +#: ../../rst/user_guide/playbooks_error_handling.rst:249 msgid "The ``max_fail_percentage`` setting applies to each batch when you use it with :ref:`serial <rolling_update_batch_size>`. In the example above, if more than 3 of the 10 servers in the first (or any) batch of servers failed, the rest of the play would be aborted." msgstr "``max_fail_percentage`` ã®è¨å®šã¯ã€:ref:`serial <rolling_update_batch_size>` ã¨ä¸€ç·’ã«ä½¿ç”¨ã™ã‚‹ã¨ã€å„ãƒãƒƒãƒã«é©ç”¨ã•ã‚Œã¾ã™ã€‚上ã®ä¾‹ã§ã¯ã€æœ€åˆã® (ã‚ã‚‹ã„ã¯ä»»æ„ã®) ãƒãƒƒãƒã«å«ã¾ã‚Œã‚‹ 10 å°ã®ã‚µãƒ¼ãƒãƒ¼ã®ã†ã¡ 3 å°ä»¥ä¸ŠãŒæ•…éšœã—ãŸå ´åˆã€æ®‹ã‚Šã®ãƒ—レイã¯ä¸æ¢ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:225 +#: ../../rst/user_guide/playbooks_error_handling.rst:253 msgid "The percentage set must be exceeded, not equaled. For example, if serial were set to 4 and you wanted the task to abort the play when 2 of the systems failed, set the max_fail_percentage at 49 rather than 50." msgstr "è¨å®šã•ã‚ŒãŸãƒ‘ーセンテージã¯ã€åŒç‰ã§ã¯ãªãã€è¶…ãˆãªã‘ã‚Œã°ãªã‚Šã¾ã›ã‚“。ãŸã¨ãˆã°ã€serial㌠4 ã«è¨å®šã•ã‚Œã¦ã„ã¦ã€2 ã¤ã®ã‚·ã‚¹ãƒ†ãƒ ãŒæ•…éšœã—ãŸã¨ãã«ãƒ—レイをä¸æ¢ã™ã‚‹ã‚¿ã‚¹ã‚¯ã«ã—ãŸã„å ´åˆã¯ã€max_fail_percentage ã‚’ 50 ã§ã¯ãªã 49 ã«è¨å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_error_handling.rst:228 +#: ../../rst/user_guide/playbooks_error_handling.rst:256 msgid "Controlling errors in blocks" msgstr "ブãƒãƒƒã‚¯ã®ã‚¨ãƒ©ãƒ¼ã‚’制御" -#: ../../rst/user_guide/playbooks_error_handling.rst:230 +#: ../../rst/user_guide/playbooks_error_handling.rst:258 msgid "You can also use blocks to define responses to task errors. This approach is similar to exception handling in many programming languages. See :ref:`block_error_handling` for details and examples." msgstr "ブãƒãƒƒã‚¯ã‚’使用ã—ã¦ã‚¿ã‚¹ã‚¯ã‚¨ãƒ©ãƒ¼ã¸ã®å¿œç”を定義ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚ã“ã®æ–¹æ³•ã¯ã€å¤šãã®ãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚°è¨€èªžã§ã®ä¾‹å¤–処ç†ã«ä¼¼ã¦ã„ã¾ã™ã€‚詳細ã¨ä¾‹ã¯ã€ã€Œ:ref:`block_error_handling`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_error_handling.rst:238 +#: ../../rst/user_guide/playbooks_error_handling.rst:266 #: ../../rst/user_guide/playbooks_filters.rst:1839 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:729 -#: ../../rst/user_guide/playbooks_lookups.rst:28 -#: ../../rst/user_guide/playbooks_loops.rst:440 -#: ../../rst/user_guide/playbooks_prompts.rst:109 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:851 +#: ../../rst/user_guide/playbooks_lookups.rst:30 +#: ../../rst/user_guide/playbooks_loops.rst:482 +#: ../../rst/user_guide/playbooks_prompts.rst:117 #: ../../rst/user_guide/playbooks_reuse.rst:210 #: ../../rst/user_guide/playbooks_reuse_includes.rst:21 #: ../../rst/user_guide/playbooks_reuse_roles.rst:610 #: ../../rst/user_guide/playbooks_templating.rst:48 -#: ../../rst/user_guide/playbooks_tests.rst:390 -#: ../../rst/user_guide/playbooks_variables.rst:451 +#: ../../rst/user_guide/playbooks_tests.rst:426 +#: ../../rst/user_guide/playbooks_variables.rst:497 msgid ":ref:`playbooks_conditionals`" msgstr ":ref:`playbooks_conditionals`" -#: ../../rst/user_guide/playbooks_error_handling.rst:239 +#: ../../rst/user_guide/playbooks_error_handling.rst:267 #: ../../rst/user_guide/playbooks_filters.rst:1840 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:730 -#: ../../rst/user_guide/playbooks_lookups.rst:29 -#: ../../rst/user_guide/playbooks_loops.rst:441 -#: ../../rst/user_guide/playbooks_prompts.rst:110 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:852 +#: ../../rst/user_guide/playbooks_lookups.rst:31 +#: ../../rst/user_guide/playbooks_loops.rst:483 +#: ../../rst/user_guide/playbooks_prompts.rst:118 #: ../../rst/user_guide/playbooks_templating.rst:49 -#: ../../rst/user_guide/playbooks_tests.rst:391 -#: ../../rst/user_guide/playbooks_variables.rst:452 +#: ../../rst/user_guide/playbooks_tests.rst:427 +#: ../../rst/user_guide/playbooks_variables.rst:498 msgid "Conditional statements in playbooks" msgstr "Playbook ã®æ¡ä»¶åˆ†å²æ–‡" @@ -6203,8 +6198,6 @@ msgstr "``recursive=False`` (デフォルト) ã®å ´åˆã¯ã€ãƒã‚¹ãƒˆã•ã‚ŒãŸã #: ../../rst/user_guide/playbooks_filters.rst:553 #: ../../rst/user_guide/playbooks_filters.rst:595 #: ../../rst/user_guide/playbooks_filters.rst:682 -#: ../../rst/user_guide/playbooks_tests.rst:319 -#: ../../rst/user_guide/playbooks_tests.rst:342 msgid "This would result in::" msgstr "ã“ã‚Œã«ã‚ˆã‚Šã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" @@ -6304,6 +6297,10 @@ msgstr "製å“" msgid "The product filter returns the `cartesian product <https://docs.python.org/3/library/itertools.html#itertools.product>`_ of the input iterables. This is roughly equivalent to nested for-loops in a generator expression." msgstr "製å“フィルターã¯ã€å…¥åŠ›ã•ã‚ŒãŸã‚¤ãƒ†ãƒ©ãƒ–ル㮠`cartesian product <https://docs.python.org/3/library/itertools.html#itertools.product>`_ ã‚’è¿”ã—ã¾ã™ã€‚ã“ã‚Œã¯ã‚¸ã‚§ãƒãƒ¬ãƒ¼ã‚¿å¼ã®å…¥ã‚Œåã«ãªã£ãŸ for-loop ã¨ã»ã¼åŒã˜ã§ã™ã€‚" +#: ../../rst/user_guide/playbooks_filters.rst:676 +msgid "For example::" +msgstr "例::" + #: ../../rst/user_guide/playbooks_filters.rst:689 msgid "Selecting JSON data: JSON queries" msgstr "JSON データã®é¸æŠž: JSON クエリー" @@ -7003,33 +7000,33 @@ msgid "This can then be used to reference hashes in Pod specifications::" msgstr "ã“ã‚Œã¯ã€Pod 仕様ã®ãƒãƒƒã‚·ãƒ¥ã‚’å‚ç…§ã™ã‚‹ãŸã‚ã«ä½¿ç”¨ã§ãã¾ã™ã€‚" #: ../../rst/user_guide/playbooks_filters.rst:1837 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:725 -#: ../../rst/user_guide/playbooks_loops.rst:434 -#: ../../rst/user_guide/playbooks_strategies.rst:216 -#: ../../rst/user_guide/playbooks_variables.rst:449 -#: ../../rst/user_guide/windows_faq.rst:244 -#: ../../rst/user_guide/windows_setup.rst:574 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:847 +#: ../../rst/user_guide/playbooks_loops.rst:476 +#: ../../rst/user_guide/playbooks_strategies.rst:242 +#: ../../rst/user_guide/playbooks_variables.rst:495 +#: ../../rst/user_guide/windows_faq.rst:248 +#: ../../rst/user_guide/windows_setup.rst:597 msgid ":ref:`about_playbooks`" msgstr ":ref:`about_playbooks`" #: ../../rst/user_guide/playbooks_filters.rst:1843 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:733 -#: ../../rst/user_guide/playbooks_lookups.rst:32 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:855 +#: ../../rst/user_guide/playbooks_lookups.rst:34 #: ../../rst/user_guide/playbooks_reuse.rst:212 #: ../../rst/user_guide/playbooks_reuse_includes.rst:23 #: ../../rst/user_guide/playbooks_reuse_roles.rst:612 #: ../../rst/user_guide/playbooks_templating.rst:50 -#: ../../rst/user_guide/playbooks_tests.rst:394 -#: ../../rst/user_guide/playbooks_variables.rst:455 +#: ../../rst/user_guide/playbooks_tests.rst:430 +#: ../../rst/user_guide/playbooks_variables.rst:501 msgid ":ref:`playbooks_loops`" msgstr ":ref:`playbooks_loops`" #: ../../rst/user_guide/playbooks_filters.rst:1844 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:734 -#: ../../rst/user_guide/playbooks_lookups.rst:33 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:856 +#: ../../rst/user_guide/playbooks_lookups.rst:35 #: ../../rst/user_guide/playbooks_templating.rst:51 -#: ../../rst/user_guide/playbooks_tests.rst:395 -#: ../../rst/user_guide/playbooks_variables.rst:456 +#: ../../rst/user_guide/playbooks_tests.rst:431 +#: ../../rst/user_guide/playbooks_variables.rst:502 msgid "Looping in playbooks" msgstr "Playbook ã§ã®ãƒ«ãƒ¼ãƒ—" @@ -7046,10 +7043,10 @@ msgid "The ``ipaddr()`` filter migrated to the `ansible.netcommon <https://galax msgstr "``ipaddr()`` フィルター㯠`ansible.netcommon <https://galaxy.ansible.com/ansible/netcommon>`_ コレクションã«ç§»è¡Œã—ã¾ã—ãŸã€‚ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«æ‰‹é †ã«å¾“ã£ã¦ãã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã‚’インストールã—ã¾ã™ã€‚" #: ../../rst/user_guide/playbooks_filters_ipaddr.rst:21 -msgid "To use this filter in Ansible, you need to install the `netaddr`_ Python library on a computer on which you use Ansible (it is not required on remote hosts). It can usually be installed with either your system package manager or using ``pip``::" +msgid "To use this filter in Ansible, you need to install the `netaddr`_ Python library on a computer on which you use Ansible (it is not required on remote hosts). It can usually be installed with either your system package manager or using ``pip``:" msgstr "ã“ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã‚’ Ansible ã§ä½¿ç”¨ã™ã‚‹ã«ã¯ã€Ansible を使用ã™ã‚‹ã‚³ãƒ³ãƒ”ューター㫠`netaddr`_ Python ライブラリーをインストールã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ (リモートホストã§ã¯å¿…è¦ã‚ã‚Šã¾ã›ã‚“)。通常ã¯ã€ã‚·ã‚¹ãƒ†ãƒ ã®ãƒ‘ッケージマãƒãƒ¼ã‚¸ãƒ£ãƒ¼ã‹ã€``pip`` を使用ã—ã¦ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:34 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:36 #: ../../rst/user_guide/playbooks_roles.rst:7 #: ../../rst/user_guide/windows_dsc.rst:5 #: ../../rst/user_guide/windows_usage.rst:9 @@ -7057,396 +7054,396 @@ msgstr "ã“ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã‚’ Ansible ã§ä½¿ç”¨ã™ã‚‹ã«ã¯ã€Ansible を使ç msgid "Topics" msgstr "トピック" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:37 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:39 msgid "Basic tests" msgstr "基本的ãªãƒ†ã‚¹ãƒˆ" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:39 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:41 msgid "``ipaddr()`` is designed to return the input value if a query is True, and ``False`` if a query is False. This way it can be easily used in chained filters. To use the filter, pass a string to it:" msgstr "``ipaddr()`` ã¯ã€ã‚¯ã‚¨ãƒªãƒ¼ãŒ True ã®å ´åˆã¯å…¥åŠ›å€¤ã‚’è¿”ã—ã€False ã®å ´åˆã¯``False`` ã‚’è¿”ã™ã‚ˆã†ã«è¨è¨ˆã•ã‚Œã¦ã„ã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€é€£éŽ–ã—ãŸãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã§ç°¡å˜ã«ä½¿ã†ã“ã¨ãŒã§ãã¾ã™ï¼Žã“ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã‚’使用ã™ã‚‹ã«ã¯ã€æ–‡å—列を渡ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:47 -msgid "You can also pass the values as variables::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:49 +msgid "You can also pass the values as variables:" msgstr "変数ã¨ã—ã¦å€¤ã‚’渡ã™ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:51 -msgid "Here are some example test results of various input strings::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:55 +msgid "Here are some example test results of various input strings:" msgstr "以下ã¯ã€ã•ã¾ã–ã¾ãªå…¥åŠ›æ–‡å—列ã®ãƒ†ã‚¹ãƒˆçµæžœã®ä¾‹ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:69 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:75 msgid "Sometimes you need either IPv4 or IPv6 addresses. To filter only for a particular type, ``ipaddr()`` filter has two \"aliases\", ``ipv4()`` and ``ipv6()``." msgstr "IPv4 アドレスã¾ãŸã¯ IPv6 アドレスã®ã„ãšã‚Œã‹ãŒå¿…è¦ã«ãªã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚特定ã®ã‚¿ã‚¤ãƒ—ã«å¯¾ã—ã¦ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã§çµžã‚Šè¾¼ã‚€ãŸã‚ã€``ipaddr()`` フィルターã«ã¯ ``ipv4()`` 㨠``ipv6()`` ã¨ã„ㆠ2 ã¤ã®ã€Œã‚¨ã‚¤ãƒªã‚¢ã‚¹ã€ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:72 -msgid "Example use of an IPv4 filter::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:78 +msgid "Example use of an IPv4 filter:" msgstr "IPv4 フィルターã®ä½¿ç”¨ä¾‹:" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:76 -msgid "A similar example of an IPv6 filter::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:84 +msgid "A similar example of an IPv6 filter:" msgstr "åŒæ§˜ã®ã€IPv6 フィルターã®ä½¿ç”¨ä¾‹:" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:80 -msgid "Here's some example test results to look for IPv4 addresses::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:90 +msgid "Here's some example test results to look for IPv4 addresses:" msgstr "以下ã¯ã€IPv4 アドレスを検索ã™ã‚‹ãƒ†ã‚¹ãƒˆçµæžœã®ä¾‹ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:88 -msgid "And the same data filtered for IPv6 addresses::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:100 +msgid "And the same data filtered for IPv6 addresses:" msgstr "IPv6 アドレスã«ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ãŒè¨å®šã•ã‚ŒãŸãƒ‡ãƒ¼ã‚¿:" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:98 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:112 msgid "Filtering lists" msgstr "リストã¸ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼è¨å®š" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:100 -msgid "You can filter entire lists - ``ipaddr()`` will return a list with values valid for a particular query::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:114 +msgid "You can filter entire lists - ``ipaddr()`` will return a list with values valid for a particular query." msgstr "リスト全体ã«ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã‚’è¨å®šã§ãã¾ã™ã€‚``ipaddr()`` ã¯ã€ç‰¹å®šã®ã‚¯ã‚¨ãƒªãƒ¼ã«æœ‰åŠ¹ãªå€¤ã‚’æŒã¤ãƒªã‚¹ãƒˆã‚’è¿”ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:117 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:133 msgid "Wrapping IPv6 addresses in [ ] brackets" msgstr "[ ] 括弧㧠IPv6 アドレスã®ãƒ©ãƒƒãƒ”ング" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:119 -msgid "Some configuration files require IPv6 addresses to be \"wrapped\" in square brackets (``[ ]``). To accomplish that, you can use the ``ipwrap()`` filter. It will wrap all IPv6 addresses and leave any other strings intact::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:135 +msgid "Some configuration files require IPv6 addresses to be \"wrapped\" in square brackets (``[ ]``). To accomplish that, you can use the ``ipwrap()`` filter. It will wrap all IPv6 addresses and leave any other strings intact." msgstr "一部ã®è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã§ã¯ã€IPv6 アドレスを角括弧 (``[ ]``) ã§ã€Œå›²ã‚€ã€å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“れを行ã†ã«ã¯ã€``ipwrap()`` フィルターを使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã‚Œã¯ã€ã™ã¹ã¦ã® IPv6 アドレスを囲ã¿ã€ãã®ä»–ã®æ–‡å—列ã¯ãã®ã¾ã¾æ®‹ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:126 -msgid "As you can see, ``ipwrap()`` did not filter out non-IP address values, which is usually what you want when for example you are mixing IP addresses with hostnames. If you still want to filter out all non-IP address values, you can chain both filters together::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:144 +msgid "As you can see, ``ipwrap()`` did not filter out non-IP address values, which is usually what you want when for example you are mixing IP addresses with hostnames. If you still want to filter out all non-IP address values, you can chain both filters together." msgstr "ã”覧ã®ã‚ˆã†ã«ã€``ipwrap()`` ã¯ã€IP アドレス以外ã®å€¤ã«ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã‚’è¨å®šã—ã¦é™¤å¤–ã—ã¦ã„ã¾ã›ã‚“。ã“ã‚Œã¯ã€IP アドレスã¨ãƒ›ã‚¹ãƒˆåãŒæ··åœ¨ã—ã¦ã„ã‚‹å ´åˆãªã©ã«å¿…è¦ã¨ãªã‚‹ã‚‚ã®ã§ã™ã€‚ãã‚Œã§ã‚‚ãªãŠã€IP アドレス以外ã®ã™ã¹ã¦ã®å€¤ã«ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã‚’è¨å®šã—ã¦é™¤å¤–ã—ãŸã„å ´åˆã¯ã€ä¸¡æ–¹ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã‚’連鎖ã•ã›ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:136 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:156 msgid "Basic queries" msgstr "基本クエリー" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:138 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:158 msgid "You can provide a single argument to each ``ipaddr()`` filter. The filter will then treat it as a query and return values modified by that query. Lists will contain only values that you are querying for." msgstr "``ipaddr()`` ã®å„フィルターã«ã¯ã€1 ã¤ã®å¼•æ•°ã‚’指定ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚フィルターã¯ãれをクエリーã¨ã—ã¦æ‰±ã„ã€ãã®ã‚¯ã‚¨ãƒªãƒ¼ã§å¤‰æ›´ã•ã‚ŒãŸå€¤ã‚’è¿”ã—ã¾ã™ã€‚リストã«ã¯ã€ã‚¯ã‚¨ãƒªãƒ¼ã§æŒ‡å®šã—ãŸå€¤ã®ã¿ãŒå«ã¾ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:142 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:162 msgid "Types of queries include:" msgstr "クエリーã®ç¨®é¡žã¯æ¬¡ã®ã¨ãŠã‚Šã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:144 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:164 msgid "query by name: ``ansible.netcommon.ipaddr('address')``, ``ansible.netcommon.ipv4('network')``;" msgstr "åå‰ã«ã‚ˆã‚‹ã‚¯ã‚¨ãƒªãƒ¼: ``ansible.netcommon.ipaddr('address')``ã€``ansible.netcommon.ipv4('network')``" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:145 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:165 msgid "query by CIDR range: ``ansible.netcommon.ipaddr('192.168.0.0/24')``, ``ansible.netcommon.ipv6('2001:db8::/32')``;" msgstr "CIDR 範囲ã«ã‚ˆã‚‹ã‚¯ã‚¨ãƒªãƒ¼: ``ansible.netcommon.ipaddr('192.168.0.0/24')``ã€``ansible.netcommon.ipv6('2001:db8::/32')``" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:146 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:166 msgid "query by index number: ``ansible.netcommon.ipaddr('1')``, ``ansible.netcommon.ipaddr('-1')``;" msgstr "インデックス番å·ã«ã‚ˆã‚‹ã‚¯ã‚¨ãƒªãƒ¼: ``ansible.netcommon.ipaddr('1')``ã€``ansible.netcommon.ipaddr('-1')``" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:148 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:168 msgid "If a query type is not recognized, Ansible will raise an error." msgstr "クエリータイプãŒèªè˜ã•ã‚Œãªã„ã¨ã€Ansible ã¯ã‚¨ãƒ©ãƒ¼ã‚’発生ã•ã›ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:152 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:172 msgid "Getting information about hosts and networks" msgstr "ホストãŠã‚ˆã³ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã«é–¢ã™ã‚‹æƒ…å ±ã®å–å¾—" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:154 -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:357 -msgid "Here's our test list again::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:174 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:411 +msgid "Here's our test list again:" msgstr "ã“ã“ã§ã¯ã€ãƒ†ã‚¹ãƒˆãƒªã‚¹ãƒˆã‚’å†åº¦ä½¿ç”¨ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:159 -msgid "Let's take the list above and get only those elements that are host IP addresses and not network ranges::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:181 +msgid "Let's take the list above and get only those elements that are host IP addresses and not network ranges:" msgstr "上ã®ãƒªã‚¹ãƒˆã‹ã‚‰ã€ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ç¯„囲ã§ã¯ãªãホスト IP アドレスã®è¦ç´ ã ã‘ã‚’å–り出ã—ã¦ã¿ã¾ã—ょã†ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:165 -msgid "As you can see, even though some values had a host address with a CIDR prefix, they were dropped by the filter. If you want host IP addresses with their correct CIDR prefixes (as is common with IPv6 addressing), you can use the ``ipaddr('host')`` filter::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:189 +msgid "As you can see, even though some values had a host address with a CIDR prefix, they were dropped by the filter. If you want host IP addresses with their correct CIDR prefixes (as is common with IPv6 addressing), you can use the ``ipaddr('host')`` filter." msgstr "ã”覧ã®ã‚ˆã†ã«ã€CIDR プレフィックスをæŒã¤ãƒ›ã‚¹ãƒˆã‚¢ãƒ‰ãƒ¬ã‚¹ã‚’æŒã¤å€¤ãŒã‚ã£ã¦ã‚‚ã€ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã«ã‚ˆã£ã¦ç ´æ£„ã•ã‚Œã¦ã„ã¾ã™ã€‚æ£ã—ã„ CIDR プレフィックスをæŒã¤ãƒ›ã‚¹ãƒˆ IP アドレスãŒå¿…è¦ãªå ´åˆ (IPv6 アドレスã§ã¯ä¸€èˆ¬çš„) ã¯ã€``ipaddr('host')`` フィルターを使用ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:173 -msgid "Filtering by IP address type also works::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:199 +msgid "Filtering by IP address type also works." msgstr "IP アドレスタイプã«ã‚ˆã‚‹ãƒ•ã‚£ãƒ«ã‚¿ãƒªãƒ³ã‚°ã‚‚機能ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:181 -msgid "You can check if IP addresses or network ranges are accessible on a public Internet, or if they are in private networks::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:209 +msgid "You can check if IP addresses or network ranges are accessible on a public Internet, or if they are in private networks:" msgstr "IP アドレスやãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ç¯„囲ãŒã€ãƒ‘ブリックãªã‚¤ãƒ³ã‚¿ãƒ¼ãƒãƒƒãƒˆä¸Šã§ã‚¢ã‚¯ã‚»ã‚¹å¯èƒ½ã‹ã€ãƒ—ライベートãªãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ä¸Šã«ã‚ã‚‹ã‹ã©ã†ã‹ã‚’確èªã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:190 -msgid "You can check which values are specifically network ranges::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:220 +msgid "You can check which values are specifically network ranges:" msgstr "特定ã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ç¯„囲ã®å€¤ã‚’確èªã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:195 -msgid "You can also check how many IP addresses can be in a certain range::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:227 +msgid "You can also check how many IP addresses can be in a certain range." msgstr "特定ã®ç¯„囲内ã«ã‚ã‚‹ IP アドレスã®æ•°ã‚’確èªã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:200 -msgid "By specifying a network range as a query, you can check if a given value is in that range::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:234 +msgid "By specifying a network range as a query, you can check if a given value is in that range." msgstr "クエリーã«ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã®ç¯„囲を指定ã™ã‚‹ã“ã¨ã§ã€æŒ‡å®šã—ãŸå€¤ãŒãã®ç¯„囲内ã«ã‚ã‚‹ã‹ã©ã†ã‹ã‚’調ã¹ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:206 -msgid "If you specify a positive or negative integer as a query, ``ipaddr()`` will treat this as an index and will return the specific IP address from a network range, in the 'host/prefix' format::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:242 +msgid "If you specify a positive or negative integer as a query, ``ipaddr()`` will treat this as an index and will return the specific IP address from a network range, in the 'host/prefix' format." msgstr "æ£ã¾ãŸã¯è² ã®æ•´æ•°ã‚’クエリーã¨ã—ã¦æŒ‡å®šã™ã‚‹ã¨ã€``ipaddr()`` ã¯ã“れをインデックスã¨ã—ã¦æ‰±ã„ã€ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã®ç¯„囲ã‹ã‚‰ç‰¹å®šã® IP アドレスを「host/prefixã€å½¢å¼ã§è¿”ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:222 -msgid "You can also select IP addresses from a range by their index, from the start or end of the range::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:260 +msgid "You can also select IP addresses from a range by their index, from the start or end of the range." msgstr "ã¾ãŸã€ç¯„囲内㮠IP アドレスをã€ç¯„囲ã®æœ€åˆã¾ãŸã¯æœ€å¾Œã‹ã‚‰ã€ã‚¤ãƒ³ãƒ‡ãƒƒã‚¯ã‚¹ã§é¸æŠžã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:238 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:278 msgid "Getting information from host/prefix values" msgstr "ホスト/プレフィックスã®å€¤ã‹ã‚‰ã®æƒ…å ±ã®å–å¾—" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:240 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:280 msgid "You frequently use a combination of IP addresses and subnet prefixes (\"CIDR\"), this is even more common with IPv6. The ``ansible.netcommon.ipaddr()`` filter can extract useful data from these prefixes." msgstr "IP アドレスã¨ã‚µãƒ–ãƒãƒƒãƒˆãƒ—レフィックス (「CIDRã€) ã®çµ„ã¿åˆã‚ã›ãŒé »ç¹ã«ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚ã“れ㯠IPv6 ã§ã¯ã‚ˆã‚Šä¸€èˆ¬çš„ã§ã™ã€‚``ansible.netcommon.ipaddr()`` フィルターã¯ã€ã“れらã®ãƒ—レフィックスã‹ã‚‰æœ‰ç”¨ãªãƒ‡ãƒ¼ã‚¿ã‚’抽出ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:244 -msgid "Here's an example set of two host prefixes (with some \"control\" values)::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:284 +msgid "Here's an example set of two host prefixes (with some \"control\" values):" msgstr "以下ã¯ã€ãƒ›ã‚¹ãƒˆãƒ—レフィックス (「制御ã€ã®å€¤ã‚’å«ã‚€) ã®ä¾‹ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:248 -msgid "First, let's make sure that we only work with correct host/prefix values, not just subnets or single IP addresses::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:290 +msgid "First, let's make sure that we only work with correct host/prefix values, not just subnets or single IP addresses." msgstr "ã¾ãšã€ã‚µãƒ–ãƒãƒƒãƒˆã‚„å˜ä¸€ã® IP アドレスã§ã¯ãªãã€æ£ã—ã„ホスト/プレフィックスã®å€¤ã®ã¿ã‚’扱ã†ã“ã¨ã‚’確èªã—ã¾ã—ょã†ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:254 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:298 msgid "In Debian-based systems, the network configuration stored in the ``/etc/network/interfaces`` file uses a combination of IP address, network address, netmask and broadcast address to configure an IPv4 network interface. We can get these values from a single 'host/prefix' combination:" msgstr "Debian ベースã®ã‚·ã‚¹ãƒ†ãƒ ã§ã¯ã€``/etc/network/interfaces`` ファイルã«ä¿å˜ã•ã‚Œã¦ã„ã‚‹ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯è¨å®šã§ã¯ã€IP アドレスã€ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚¢ãƒ‰ãƒ¬ã‚¹ã€ãƒãƒƒãƒˆãƒžã‚¹ã‚¯ã€ãƒ–ãƒãƒ¼ãƒ‰ã‚ャストアドレスã®çµ„ã¿åˆã‚ã›ã‚’使用ã—ã¦ã€IPv4 ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ã‚’è¨å®šã—ã¾ã™ã€‚ã“れらã®å€¤ã¯ã€1ã¤ã®ã€Œhost/prefixã€ã®çµ„ã¿åˆã‚ã›ã‹ã‚‰å¾—ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:273 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:317 msgid "In the above example, we needed to handle the fact that values were stored in a list, which is unusual in IPv4 networks, where only a single IP address can be set on an interface. However, IPv6 networks can have multiple IP addresses set on an interface:" msgstr "上ã®ä¾‹ã§ã¯ã€å€¤ãŒãƒªã‚¹ãƒˆã«æ ¼ç´ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’処ç†ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã—ãŸã€‚ã“ã‚Œã¯ã€1 ã¤ã®ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ã« 1 ã¤ã® IP アドレスã—ã‹è¨å®šã§ããªã„ IPv4 ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã§ã¯çã—ã„ã“ã¨ã§ã™ã€‚ã—ã‹ã—ã€IPv6 ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã§ã¯ã€1 ã¤ã®ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ã«è¤‡æ•°ã® IP アドレスをè¨å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:295 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:339 msgid "If needed, you can extract subnet and prefix information from the 'host/prefix' value:" msgstr "å¿…è¦ãªå ´åˆã¯ã€ã€Œhost/prefixã€å€¤ã‹ã‚‰ã‚µãƒ–ãƒãƒƒãƒˆãŠã‚ˆã³ãƒ—ãƒ¬ãƒ•ã‚£ãƒƒã‚¯ã‚¹æƒ…å ±ã‚’æŠ½å‡ºã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:306 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:350 msgid "Converting subnet masks to CIDR notation" msgstr "サブãƒãƒƒãƒˆãƒžã‚¹ã‚¯ã® CIDR 表記ã¸ã®å¤‰æ›" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:308 -msgid "Given a subnet in the form of network address and subnet mask, the ``ipaddr()`` filter can convert it into CIDR notation. This can be useful for converting Ansible facts gathered about network configuration from subnet masks into CIDR format::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:352 +msgid "Given a subnet in the form of network address and subnet mask, the ``ipaddr()`` filter can convert it into CIDR notation. This can be useful for converting Ansible facts gathered about network configuration from subnet masks into CIDR format." msgstr "ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚¢ãƒ‰ãƒ¬ã‚¹ã¨ã‚µãƒ–ãƒãƒƒãƒˆãƒžã‚¹ã‚¯ã®å½¢å¼ã§ã‚µãƒ–ãƒãƒƒãƒˆãŒä¸Žãˆã‚‰ã‚Œã‚‹ã¨ã€``ipaddr()`` フィルターã¯ãれを CIDR 表記ã«å¤‰æ›ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã‚Œã¯ã€ã‚µãƒ–ãƒãƒƒãƒˆãƒžã‚¹ã‚¯ã‹ã‚‰ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯æ§‹æˆã«ã¤ã„ã¦åŽé›†ã—㟠Ansible ã®ãƒ•ã‚¡ã‚¯ãƒˆã‚’ CIDR å½¢å¼ã«å¤‰æ›ã™ã‚‹éš›ã«ä¾¿åˆ©ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:323 -msgid "First concatenate the network and netmask::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:369 +msgid "First concatenate the network and netmask:" msgstr "最åˆã«ã€ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã¨ãƒãƒƒãƒˆãƒžã‚¹ã‚¯ã‚’連çµã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:328 -msgid "This result can be converted to canonical form with ``ipaddr()`` to produce a subnet in CIDR format::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:376 +msgid "This result can be converted to canonical form with ``ipaddr()`` to produce a subnet in CIDR format." msgstr "ã“ã‚Œã«ã‚ˆã‚Šã€``ipaddr()`` ã§æ£å‰‡å½¢å¼ã«å¤‰æ›ã—ã¦ã€CIDR å½¢å¼ã§ã‚µãƒ–ãƒãƒƒãƒˆã‚’生æˆã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:338 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:388 msgid "Getting information about the network in CIDR notation" msgstr "CIDR 表記ã§ã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯æƒ…å ±ã®å–å¾—" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:340 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:390 msgid "Given an IP address, the ``ipaddr()`` filter can produce the network address in CIDR notation. This can be useful when you want to obtain the network address from the IP address in CIDR format." msgstr "IP アドレスを指定ã™ã‚‹ã¨ã€``ipaddr()`` フィルターã¯ã€CIDR 表記ã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚¢ãƒ‰ãƒ¬ã‚¹ã‚’生æˆã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã‚Œã¯ã€CIDR å½¢å¼ã® IP アドレスã‹ã‚‰ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚¢ãƒ‰ãƒ¬ã‚¹ã‚’å–å¾—ã—ãŸã„å ´åˆã«ä¾¿åˆ©ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:343 -msgid "Here's an example of IP address::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:393 +msgid "Here's an example of IP address:" msgstr "以下㯠IP アドレスã®ä¾‹ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:348 -msgid "This can be used to obtain the network address in CIDR notation format::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:400 +msgid "This can be used to obtain the network address in CIDR notation format." msgstr "ã“ã‚Œã¯ã€CIDR 表記形å¼ã§ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚¢ãƒ‰ãƒ¬ã‚¹ã‚’å–å¾—ã™ã‚‹ã®ã«ä½¿ç”¨ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:355 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:409 msgid "IP address conversion" msgstr "IP アドレス変æ›" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:362 -msgid "You can convert IPv4 addresses into IPv6 addresses::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:418 +msgid "You can convert IPv4 addresses into IPv6 addresses." msgstr "IPv4 アドレスを IPv6 アドレスã«å¤‰æ›ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:367 -msgid "Converting from IPv6 to IPv4 works very rarely::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:425 +msgid "Converting from IPv6 to IPv4 works very rarely" msgstr "IPv6 ã‹ã‚‰ IPv4 ã¸ã®å¤‰æ›ã¯ã»ã¨ã‚“ã©æ©Ÿèƒ½ã—ã¾ã›ã‚“。" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:372 -msgid "But we can make a double conversion if needed::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:432 +msgid "But we can make a double conversion if needed:" msgstr "ãŸã ã—ã€å¿…è¦ã«å¿œã˜ã¦äºŒé‡å¤‰æ›ã‚’è¡Œã†ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:377 -msgid "You can convert IP addresses to integers, the same way that you can convert integers into IP addresses::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:439 +msgid "You can convert IP addresses to integers, the same way that you can convert integers into IP addresses." msgstr "æ•´æ•°ã‚’ IP アドレスã«å¤‰æ›ã™ã‚‹ã®ã¨åŒã˜æ–¹æ³•ã§ã€IP アドレスを整数ã«å¤‰æ›ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:383 -msgid "You can convert IPv4 address to `Hexadecimal notation <https://en.wikipedia.org/wiki/Hexadecimal>`_ with optional delimiter::" -msgstr "ä»»æ„ã®åŒºåˆ‡ã‚Šæ–‡å—を使用ã—ã¦ã€IPv4 アドレスを `16 進表記 <https://en.wikipedia.org/wiki/Hexadecimal>`_ ã«å¤‰æ›ã§ãã¾ã™ã€‚" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:447 +msgid "You can convert IPv4 address to `Hexadecimal notation <https://en.wikipedia.org/wiki/Hexadecimal>`_ with optional delimiter:" +msgstr "ä»»æ„ã®åŒºåˆ‡ã‚Šæ–‡å—を使用ã—ã¦ã€IPv4 アドレスを `16進数表記 <https://en.wikipedia.org/wiki/Hexadecimal>`_ ã«å¤‰æ›ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:390 -msgid "You can convert IP addresses to PTR records::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:456 +msgid "You can convert IP addresses to PTR records:" msgstr "IP アドレスを PTR レコードã«å¤‰æ›ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:403 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:471 msgid "Converting IPv4 address to a 6to4 address" msgstr "IPv4 アドレス㮠6to4 アドレスã¸ã®å¤‰æ›" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:405 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:473 msgid "A `6to4`_ tunnel is a way to access the IPv6 Internet from an IPv4-only network. If you have a public IPv4 address, you can automatically configure its IPv6 equivalent in the ``2002::/16`` network range. After conversion you will gain access to a ``2002:xxxx:xxxx::/48`` subnet which could be split into 65535 ``/64`` subnets if needed." msgstr "`6to4`_ トンãƒãƒ«ã¯ã€IPv4 ã®ã¿ã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‹ã‚‰ IPv6 インターãƒãƒƒãƒˆã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ãŸã‚ã®æ‰‹æ®µã§ã™ã€‚パブリック IPv4 アドレスãŒã‚ã‚‹å ´åˆã¯ã€ãã® IPv6 相当ã®ã‚¢ãƒ‰ãƒ¬ã‚¹ã‚’ ``2002::/16`` ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ç¯„囲内ã«è‡ªå‹•çš„ã«è¨å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚変æ›å¾Œã¯ã€``2002:xxxx:xxxx::/48`` サブãƒãƒƒãƒˆã¸ã®ã‚¢ã‚¯ã‚»ã‚¹ãŒå¯èƒ½ã«ãªã‚Šã€å¿…è¦ã«å¿œã˜ã¦ 65535 ``/64`` サブãƒãƒƒãƒˆã«åˆ†å‰²ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:411 -msgid "To convert your IPv4 address, just send it through the ``'6to4'`` filter. It will be automatically converted to a router address (with a ``::1/48`` host address)::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:479 +msgid "To convert your IPv4 address, just send it through the ``'6to4'`` filter. It will be automatically converted to a router address (with a ``::1/48`` host address)." msgstr "IPv4 アドレスを変æ›ã™ã‚‹ã«ã¯ã€``'6to4'`` フィルターã«é€šã™ã ã‘ã§ã™ã€‚自動的ã«ãƒ«ãƒ¼ã‚¿ãƒ¼ã‚¢ãƒ‰ãƒ¬ã‚¹ (ホストアドレス㯠``::1/48``) ã«å¤‰æ›ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:421 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:491 msgid "Finding IP addresses within a range" msgstr "範囲内㮠IP アドレスã®æ¤œç´¢" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:423 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:493 msgid "To find usable IP addresses within an IP range, try these ``ipaddr`` filters:" msgstr "IP 範囲内ã§ä½¿ç”¨å¯èƒ½ãª IP アドレスを見ã¤ã‘ã‚‹ã«ã¯ã€ä»¥ä¸‹ã® ``ipaddr`` フィルターを試行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:425 -msgid "To find the next usable IP address in a range, use ``next_usable`` ::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:495 +msgid "To find the next usable IP address in a range, use ``next_usable``:" msgstr "範囲内ã®æ¬¡ã®ä½¿ç”¨å¯èƒ½ãª IP アドレスを見ã¤ã‘ã‚‹ã«ã¯ã€``next_usable`` を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:430 -msgid "To find the last usable IP address from a range, use ``last_usable``::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:502 +msgid "To find the last usable IP address from a range, use ``last_usable``." msgstr "範囲ã‹ã‚‰æœ€å¾Œã®ä½¿ç”¨å¯èƒ½ãª IP アドレスを見ã¤ã‘ã‚‹ã«ã¯ã€``last_usable`` を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:435 -msgid "To find the available range of IP addresses from the given network address, use ``range_usable``::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:509 +msgid "To find the available range of IP addresses from the given network address, use ``range_usable``." msgstr "指定ã—ãŸãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚¢ãƒ‰ãƒ¬ã‚¹ã‹ã‚‰åˆ©ç”¨å¯èƒ½ãª IP アドレスã®ç¯„囲を検索ã™ã‚‹ã«ã¯ã€``range_usable`` を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:440 -msgid "To find the peer IP address for a point to point link, use ``peer``::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:516 +msgid "To find the peer IP address for a point to point link, use ``peer``." msgstr "ãƒã‚¤ãƒ³ãƒˆãƒ„ーãƒã‚¤ãƒ³ãƒˆã®ãƒªãƒ³ã‚¯ã®ãƒ”ã‚¢ IP アドレスを検索ã™ã‚‹ã«ã¯ã€``peer`` を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:447 -msgid "To return the nth ip from a network, use the filter ``nthhost``::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:525 +msgid "To return the nth ip from a network, use the filter ``nthhost``." msgstr "ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‹ã‚‰ nth ip ã«æˆ»ã‚‹ã«ã¯ã€ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ ``nthhost`` を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:452 -msgid "``nthhost`` also supports a negative value::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:532 +msgid "``nthhost`` also supports a negative value." msgstr "``nthhost`` ã¯ã€è² ã®å€¤ã‚‚サãƒãƒ¼ãƒˆã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:457 -msgid "To find the next nth usable IP address in relation to another within a range, use ``next_nth_usable`` In the example, ``next_nth_usable`` returns the second usable IP address for the given IP range::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:539 +msgid "To find the next nth usable IP address in relation to another within a range, use ``next_nth_usable`` In the example, ``next_nth_usable`` returns the second usable IP address for the given IP range:" msgstr "範囲内ã®åˆ¥ã® IP ã¨ã®é–¢ä¿‚ã§ã€æ¬¡ã® n 番目ã«ä½¿ç”¨å¯èƒ½ãª IP アドレスを見ã¤ã‘ã‚‹ã«ã¯ã€``next_nth_usable`` を使用ã—ã¾ã™ã€‚ã“ã®ä¾‹ã§ã¯ã€``next_nth_usable`` ãŒã€æŒ‡å®šã® IP 範囲㫠2 番目ã®ä½¿ç”¨å¯èƒ½ãª IP アドレスを返ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:463 -msgid "If there is no usable address, it returns an empty string::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:547 +msgid "If there is no usable address, it returns an empty string." msgstr "使用å¯èƒ½ãªã‚¢ãƒ‰ãƒ¬ã‚¹ãŒãªã„å ´åˆã¯ã€ç©ºã®æ–‡å—列を返ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:468 -msgid "Just like ``next_nth_ansible``, you have ``previous_nth_usable`` to find the previous usable address::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:554 +msgid "Just like ``next_nth_ansible``, you have ``previous_nth_usable`` to find the previous usable address:" msgstr "``next_nth_ansible`` ã¨åŒæ§˜ã« ``previous_nth_usable`` ãŒã‚ã‚Šã€ä»¥å‰ã®ä½¿ç”¨å¯èƒ½ãªã‚¢ãƒ‰ãƒ¬ã‚¹ã‚’見ã¤ã‘ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:475 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:563 msgid "Testing if a address belong to a network range" msgstr "アドレスãŒãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ç¯„囲ã«å±žã™ã‚‹ã‹ã©ã†ã‹ã®ãƒ†ã‚¹ãƒˆ" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:477 -msgid "The ``network_in_usable`` filter returns whether an address passed as an argument is usable in a network. Usable addresses are addresses that can be assigned to a host. The network ID and the broadcast address are not usable addresses.::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:565 +msgid "The ``network_in_usable`` filter returns whether an address passed as an argument is usable in a network. Usable addresses are addresses that can be assigned to a host. The network ID and the broadcast address are not usable addresses." msgstr "``network_in_usable`` フィルターã¯ã€å¼•æ•°ã¨ã—ã¦æ¸¡ã•ã‚ŒãŸã‚¢ãƒ‰ãƒ¬ã‚¹ãŒãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ä¸Šã§ä½¿ç”¨å¯èƒ½ã‹ã©ã†ã‹ã‚’è¿”ã—ã¾ã™ã€‚使用å¯èƒ½ãªã‚¢ãƒ‰ãƒ¬ã‚¹ã¨ã¯ã€ãƒ›ã‚¹ãƒˆã«å‰²ã‚Šå½“ã¦ã‚‹ã“ã¨ãŒã§ãるアドレスã§ã™ã€‚ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ ID やブãƒãƒ¼ãƒ‰ã‚ャストアドレスã¯ä½¿ç”¨å¯èƒ½ãªã‚¢ãƒ‰ãƒ¬ã‚¹ã§ã¯ã‚ã‚Šã¾ã›ã‚“。" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:490 -msgid "The ``network_in_network`` filter returns whether an address or a network passed as argument is in a network.::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:580 +msgid "The ``network_in_network`` filter returns whether an address or a network passed as argument is in a network." msgstr "``network_in_network`` フィルターã¯ã€å¼•æ•°ã¨ã—ã¦æ¸¡ã•ã‚ŒãŸã‚¢ãƒ‰ãƒ¬ã‚¹ã¾ãŸã¯ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãŒãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯å†…ã«ã‚ã‚‹ã‹ã©ã†ã‹ã‚’è¿”ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:505 -msgid "To check whether multiple addresses belong to a network, use the ``reduce_on_network`` filter::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:597 +msgid "To check whether multiple addresses belong to a network, use the ``reduce_on_network`` filter." msgstr "複数ã®ã‚¢ãƒ‰ãƒ¬ã‚¹ãŒãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã«å±žã™ã‚‹ã‹ã©ã†ã‹ã‚’確èªã™ã‚‹ã«ã¯ã€``reduce_on_network`` フィルターを使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:512 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:606 msgid "IP Math" msgstr "IP 計算" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:516 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:610 msgid "The ``ipmath()`` filter can be used to do simple IP math/arithmetic." msgstr "``ipmath()`` フィルターã¯ã€å˜ç´”㪠IP 計算/演算をã™ã‚‹ã®ã«ä½¿ç”¨ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:518 -msgid "Here are a few simple examples::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:612 +msgid "Here are a few simple examples:" msgstr "以下ã¯ç°¡å˜ãªä¾‹ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:552 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:648 msgid "Subnet manipulation" msgstr "サブãƒãƒƒãƒˆæ“作" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:554 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:650 msgid "The ``ipsubnet()`` filter can be used to manipulate network subnets in several ways." msgstr "``ipsubnet()`` フィルターã¯ã€ã•ã¾ã–ã¾ãªæ–¹æ³•ã§ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚µãƒ–ãƒãƒƒãƒˆã‚’æ“作ã™ã‚‹ã®ã«ä½¿ç”¨ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:556 -msgid "Here is an example IP address and subnet::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:652 +msgid "Here is an example IP address and subnet:" msgstr "IP アドレスã¨ã‚µãƒ–ãƒãƒƒãƒˆã®ä¾‹ã‚’以下ã«ç¤ºã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:561 -msgid "To check if a given string is a subnet, pass it through the filter without any arguments. If the given string is an IP address, it will be converted into a subnet::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:659 +msgid "To check if a given string is a subnet, pass it through the filter without any arguments. If the given string is an IP address, it will be converted into a subnet." msgstr "特定ã®æ–‡å—列ãŒã‚µãƒ–ãƒãƒƒãƒˆã§ã‚ã‚‹ã‹ã©ã†ã‹ã‚’確èªã™ã‚‹ã«ã¯ã€å¼•æ•°ãªã—ã§ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã‚’渡ã—ã¾ã™ã€‚指定ã®æ–‡å—列㌠IP アドレスã®å ´åˆã¯ã€ã‚µãƒ–ãƒãƒƒãƒˆã«å¤‰æ›ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:571 -msgid "If you specify a subnet size as the first parameter of the ``ipsubnet()`` filter, and the subnet size is **smaller than the current one**, you will get the number of subnets a given subnet can be split into::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:671 +msgid "If you specify a subnet size as the first parameter of the ``ipsubnet()`` filter, and the subnet size is **smaller than the current one**, you will get the number of subnets a given subnet can be split into." msgstr "``ipsubnet()`` フィルターã®æœ€åˆã®ãƒ‘ラメーターã«ã‚µãƒ–ãƒãƒƒãƒˆã‚µã‚¤ã‚ºã‚’指定ã—ã€ãã®ã‚µãƒ–ãƒãƒƒãƒˆã‚µã‚¤ã‚ºãŒ **ç¾åœ¨ã®ã‚‚ã®ã‚ˆã‚Šå°ã•ã„å ´åˆ**ã€æŒ‡å®šã•ã‚ŒãŸã‚µãƒ–ãƒãƒƒãƒˆãŒåˆ†å‰²ã§ãるサブãƒãƒƒãƒˆã®æ•°ãŒå¾—られã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:578 -msgid "The second argument of the ``ipsubnet()`` filter is an index number; by specifying it you can get a new subnet with the specified size::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:680 +msgid "The second argument of the ``ipsubnet()`` filter is an index number; by specifying it you can get a new subnet with the specified size." msgstr "``ipsubnet()`` フィルターã®ç¬¬ 2 引数ã¯ã‚¤ãƒ³ãƒ‡ãƒƒã‚¯ã‚¹ç•ªå·ã§ã€ã“れを指定ã™ã‚‹ã“ã¨ã§ã€æŒ‡å®šã—ãŸã‚µã‚¤ã‚ºã®æ–°ã—ã„サブãƒãƒƒãƒˆã‚’å¾—ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:597 -msgid "If you specify an IP address instead of a subnet, and give a subnet size as the first argument, the ``ipsubnet()`` filter will instead return the biggest subnet that contains that given IP address::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:701 +msgid "If you specify an IP address instead of a subnet, and give a subnet size as the first argument, the ``ipsubnet()`` filter will instead return the biggest subnet that contains that given IP address." msgstr "サブãƒãƒƒãƒˆã®ä»£ã‚ã‚Šã« IP アドレスを指定ã—ã€ç¬¬ 1 引数ã«ã‚µãƒ–ãƒãƒƒãƒˆã‚µã‚¤ã‚ºã‚’指定ã—ãŸå ´åˆã€``ipsubnet()`` フィルターã¯ã€ä»£ã‚ã‚Šã«æŒ‡å®šã•ã‚ŒãŸ IP アドレスをå«ã‚€æœ€å¤§ã®ã‚µãƒ–ãƒãƒƒãƒˆã‚’è¿”ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:604 -msgid "By specifying an index number as a second argument, you can select smaller and smaller subnets::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:710 +msgid "By specifying an index number as a second argument, you can select smaller and smaller subnets." msgstr "第 2 引数ã«ã‚¤ãƒ³ãƒ‡ãƒƒã‚¯ã‚¹ç•ªå·ã‚’指定ã™ã‚‹ã“ã¨ã§ã€ã‚ˆã‚Šå°ã•ãªã‚µãƒ–ãƒãƒƒãƒˆã‚’é¸æŠžã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:623 -msgid "By specifying another subnet as a second argument, if the second subnet includes the first, you can determine the rank of the first subnet in the second ::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:731 +msgid "By specifying another subnet as a second argument, if the second subnet includes the first, you can determine the rank of the first subnet in the second." msgstr "別ã®ã‚µãƒ–ãƒãƒƒãƒˆã‚’ 2 番目ã®å¼•æ•°ã¨ã—ã¦æŒ‡å®šã™ã‚‹ã“ã¨ã§ã€2 番目ã®ã‚µãƒ–ãƒãƒƒãƒˆã«æœ€åˆã®ã‚µãƒ–ãƒãƒƒãƒˆãŒå«ã¾ã‚Œã‚‹å ´åˆã¯ã€2 番目ã®ã‚µãƒ–ãƒãƒƒãƒˆã§æœ€åˆã®ã‚µãƒ–ãƒãƒƒãƒˆã®é †ä½ã‚’決定ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:642 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:752 msgid "If the second subnet doesn't include the first subnet, the ``ipsubnet()`` filter raises an error." msgstr "2 ã¤ç›®ã®ã‚µãƒ–ãƒãƒƒãƒˆã« 1 ã¤ç›®ã®ã‚µãƒ–ãƒãƒƒãƒˆãŒå«ã¾ã‚Œã¦ã„ãªã„å ´åˆã€``ipsubnet()`` フィルターã¯ã‚¨ãƒ©ãƒ¼ã‚’出力ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:645 -msgid "You can use the ``ipsubnet()`` filter with the ``ipaddr()`` filter to, for example, split a given ``/48`` prefix into smaller ``/64`` subnets::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:755 +msgid "You can use the ``ipsubnet()`` filter with the ``ipaddr()`` filter to, for example, split a given ``/48`` prefix into smaller ``/64`` subnets:" msgstr "``ipsubnet()`` フィルター㨠``ipaddr()`` フィルターを併用ã™ã‚‹ã“ã¨ã§ã€ãŸã¨ãˆã°ã€``/48`` プレフィックスをよりå°ã•ãª ``/64`` サブãƒãƒƒãƒˆã«åˆ†å‰²ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:651 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:763 msgid "Because of the size of IPv6 subnets, iteration over all of them to find the correct one may take some time on slower computers, depending on the size difference between the subnets." msgstr "IPv6 サブãƒãƒƒãƒˆã¯ã‚µã‚¤ã‚ºãŒå¤§ãã„ãŸã‚ã€æ£ã—ã„サブãƒãƒƒãƒˆã‚’見ã¤ã‘ã‚‹ãŸã‚ã«ã™ã¹ã¦ã®ã‚µãƒ–ãƒãƒƒãƒˆã‚’å復処ç†ã™ã‚‹ã¨ã€é…ã„コンピューターã§ã¯ã‚µãƒ–ãƒãƒƒãƒˆé–“ã®ã‚µã‚¤ã‚ºå·®ã«å¿œã˜ã¦æ™‚é–“ãŒã‹ã‹ã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:657 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:769 msgid "Subnet Merging" msgstr "サブãƒãƒƒãƒˆã®ãƒžãƒ¼ã‚¸" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:661 -msgid "The ``cidr_merge()`` filter can be used to merge subnets or individual addresses into their minimal representation, collapsing overlapping subnets and merging adjacent ones wherever possible::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:773 +msgid "The ``cidr_merge()`` filter can be used to merge subnets or individual addresses into their minimal representation, collapsing overlapping subnets and merging adjacent ones wherever possible." msgstr "``cidr_merge()`` フィルターã¯ã€ã‚µãƒ–ãƒãƒƒãƒˆã‚„個々ã®ã‚¢ãƒ‰ãƒ¬ã‚¹ã‚’最å°ã®è¡¨ç¾ã«çµ±åˆã™ã‚‹ãŸã‚ã«ä½¿ç”¨ã™ã‚‹ã“ã¨ãŒã§ãã€é‡è¤‡ã™ã‚‹ã‚µãƒ–ãƒãƒƒãƒˆã‚’折りãŸãŸã¿ã€å¯èƒ½ãªé™ã‚Šéš£æŽ¥ã™ã‚‹ã‚µãƒ–ãƒãƒƒãƒˆã‚’マージã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:671 -msgid "Changing the action from 'merge' to 'span' will instead return the smallest subnet which contains all of the inputs::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:785 +msgid "Changing the action from 'merge' to 'span' will instead return the smallest subnet which contains all of the inputs." msgstr "アクションを「mergeã€ã‹ã‚‰ã€Œspanã€ã«å¤‰æ›´ã™ã‚‹ã¨ã€ä»£ã‚ã‚Šã«å…¥åŠ›ã®ã™ã¹ã¦ã‚’å«ã‚€æœ€å°ã®ã‚µãƒ–ãƒãƒƒãƒˆã‚’è¿”ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:682 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:798 msgid "MAC address filter" msgstr "MAC アドレスフィルター" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:684 -msgid "You can use the ``hwaddr()`` filter to check if a given string is a MAC address or convert it between various formats. Examples::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:800 +msgid "You can use the ``hwaddr()`` filter to check if a given string is a MAC address or convert it between various formats. Examples:" msgstr "``hwaddr()`` フィルターを使用ã—ã¦ã€ä¸Žãˆã‚‰ã‚ŒãŸæ–‡å—列㌠MAC アドレスã§ã‚ã‚‹ã‹ã©ã†ã‹ã‚’確èªã—ãŸã‚Šã€ã•ã¾ã–ã¾ãªãƒ•ã‚©ãƒ¼ãƒžãƒƒãƒˆé–“ã§å¤‰æ›ã—ãŸã‚Šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:702 -msgid "The supported formats result in the following conversions for the ``1a:2b:3c:4d:5e:6f`` MAC address::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:820 +msgid "The supported formats result in the following conversions for the ``1a:2b:3c:4d:5e:6f`` MAC address:" msgstr "サãƒãƒ¼ãƒˆã•ã‚Œã‚‹å½¢å¼ã«ã‚ˆã‚Šã€ä»¥ä¸‹ã®å¤‰æ›ã§ã€MAC アドレス ``1a:2b:3c:4d:5e:6f`` ã«å¯¾ã—ã¦ã€ä»¥ä¸‹ã®ã‚ˆã†ãªå¤‰æ›ãŒè¡Œã‚ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:714 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:834 msgid "Generate an IPv6 address in Stateless Configuration (SLAAC)" msgstr "ステートレスè¨å®š (SLAAC) 㧠IPv6 アドレスを生æˆã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:716 -msgid "the filter ``slaac()`` generates an IPv6 address for a given network and a MAC Address in Stateless Configuration::" +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:836 +msgid "the filter ``slaac()`` generates an IPv6 address for a given network and a MAC Address in Stateless Configuration." msgstr "フィルター ``slaac()`` ã¯ã€ã‚¹ãƒ†ãƒ¼ãƒˆãƒ¬ã‚¹è¨å®šã®æŒ‡å®šã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãŠã‚ˆã³ MAC アドレス㫠IPv6 アドレスを生æˆã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:723 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:845 msgid "`ansible.netcommon <https://galaxy.ansible.com/ansible/netcommon>`_" msgstr "`ansible.netcommon <https://galaxy.ansible.com/ansible/netcommon>`_" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:724 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:846 msgid "Ansible network collection for common code" msgstr "一般的ãªã‚³ãƒ¼ãƒ‰ã® Ansible ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³" -#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:728 +#: ../../rst/user_guide/playbooks_filters_ipaddr.rst:850 msgid "Introduction to Jinja2 filters and their uses" msgstr "Jinja2 フィルターã®æ¦‚è¦ãŠã‚ˆã³ãã®ç”¨é€”" @@ -7463,94 +7460,94 @@ msgid "Handler example" msgstr "ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã®ä¾‹" #: ../../rst/user_guide/playbooks_handlers.rst:14 -msgid "This playbook, ``verify-apache.yml``, contains a single play with a handler::" +msgid "This playbook, ``verify-apache.yml``, contains a single play with a handler." msgstr "ã“ã® Playbook ``verify-apache.yml`` ã«ã¯ã€ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã‚’使用ã—㟠1 ã¤ã®ãƒ—レイãŒå«ã¾ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_handlers.rst:47 -msgid "In this example playbook, the second task notifies the handler. A single task can notify more than one handler::" +#: ../../rst/user_guide/playbooks_handlers.rst:49 +msgid "In this example playbook, the second task notifies the handler. A single task can notify more than one handler." msgstr "ã“ã® Playbook ã®ä¾‹ã§ã¯ã€2 番目ã®ã‚¿ã‚¹ã‚¯ãŒãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã«é€šçŸ¥ã—ã¾ã™ã€‚å˜ä¸€ã®ã‚¿ã‚¹ã‚¯ã¯è¤‡æ•°ã®ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã«é€šçŸ¥ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_handlers.rst:69 +#: ../../rst/user_guide/playbooks_handlers.rst:73 msgid "Controlling when handlers run" msgstr "ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã®å®Ÿè¡Œæ™‚ã®åˆ¶å¾¡" -#: ../../rst/user_guide/playbooks_handlers.rst:71 +#: ../../rst/user_guide/playbooks_handlers.rst:75 msgid "By default, handlers run after all the tasks in a particular play have been completed. This approach is efficient, because the handler only runs once, regardless of how many tasks notify it. For example, if multiple tasks update a configuration file and notify a handler to restart Apache, Ansible only bounces Apache once to avoid unnecessary restarts." msgstr "デフォルトã§ã¯ã€ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã¯ã€ç‰¹å®šã®ãƒ—レイã«ãŠã‘ã‚‹ã™ã¹ã¦ã®ã‚¿ã‚¹ã‚¯ãŒå®Œäº†ã—ãŸå¾Œã«å®Ÿè¡Œã—ã¾ã™ã€‚ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã¯ã€ã„ãã¤ã®ã‚¿ã‚¹ã‚¯ãŒé€šçŸ¥ã—ãŸã‹ã«é–¢ã‚らãšã€ä¸€åº¦ã ã‘実行ã™ã‚‹ãŸã‚ã€ã“ã®ã‚¢ãƒ—ãƒãƒ¼ãƒã¯åŠ¹çŽ‡çš„ã§ã™ã€‚ãŸã¨ãˆã°ã€è¤‡æ•°ã®ã‚¿ã‚¹ã‚¯ãŒè¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã‚’æ›´æ–°ã—ã€ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã« Apache ã®å†èµ·å‹•ã‚’通知ã—ãŸå ´åˆã€Ansible 㯠Apache ã‚’ 1 回ã ã‘ãƒã‚¦ãƒ³ã‚¹ã•ã›ã€ä¸è¦ãªå†èµ·å‹•ã‚’回é¿ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_handlers.rst:73 -msgid "If you need handlers to run before the end of the play, add a task to flush them using the :ref:`meta module <meta_module>`, which executes Ansible actions::" +#: ../../rst/user_guide/playbooks_handlers.rst:77 +msgid "If you need handlers to run before the end of the play, add a task to flush them using the :ref:`meta module <meta_module>`, which executes Ansible actions." msgstr "プレイã®çµ‚了å‰ã«ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã‚’実行ã™ã‚‹å¿…è¦ãŒã‚ã‚‹å ´åˆã¯ã€Ansible アクションを実行ã™ã‚‹ :ref:`meta module <meta_module>` を使用ã—ã¦ã€ã‚¿ã‚¹ã‚¯ã‚’フラッシュã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_handlers.rst:85 +#: ../../rst/user_guide/playbooks_handlers.rst:91 msgid "The ``meta: flush_handlers`` task triggers any handlers that have been notified at that point in the play." msgstr "``meta: flush_handlers`` タスクã¯ã€ãƒ—レイã®ãã®æ™‚点ã§é€šçŸ¥ã•ã‚ŒãŸãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã‚’発生ã•ã›ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_handlers.rst:88 +#: ../../rst/user_guide/playbooks_handlers.rst:94 msgid "Using variables with handlers" msgstr "ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã§ã®å¤‰æ•°ã®ä½¿ç”¨" -#: ../../rst/user_guide/playbooks_handlers.rst:90 +#: ../../rst/user_guide/playbooks_handlers.rst:96 msgid "You may want your Ansible handlers to use variables. For example, if the name of a service varies slightly by distribution, you want your output to show the exact name of the restarted service for each target machine. Avoid placing variables in the name of the handler. Since handler names are templated early on, Ansible may not have a value available for a handler name like this::" msgstr "Ansible ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã§å¤‰æ•°ã‚’使用ã—ãŸã„å ´åˆãŒã‚ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€ã‚µãƒ¼ãƒ“スã®åå‰ãŒãƒ‡ã‚£ã‚¹ãƒˆãƒªãƒ“ューションã«ã‚ˆã£ã¦ã‚ãšã‹ã«ç•°ãªã‚‹å ´åˆã«ã€ã‚¿ãƒ¼ã‚²ãƒƒãƒˆãƒžã‚·ãƒ³ã”ã¨ã«å†èµ·å‹•ã—ãŸã‚µãƒ¼ãƒ“スã®æ£ç¢ºãªåå‰ã‚’出力ã™ã‚‹ã¨ã—ã¾ã™ã€‚ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã®åå‰ã«å¤‰æ•°ã‚’入れãªã„ã§ãã ã•ã„。ãƒãƒ³ãƒ‰ãƒ©ãƒ¼åã¯åˆæœŸæ®µéšŽã§ãƒ†ãƒ³ãƒ—レート化ã•ã‚Œã¦ã„ã‚‹ãŸã‚ã€Ansible ã§ã¯æ¬¡ã®ã‚ˆã†ãªãƒãƒ³ãƒ‰ãƒ©ãƒ¼åã«åˆ©ç”¨ã§ãる値ãŒãªã„å ´åˆãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_handlers.rst:96 +#: ../../rst/user_guide/playbooks_handlers.rst:102 msgid "If the variable used in the handler name is not available, the entire play fails. Changing that variable mid-play **will not** result in newly created handler." msgstr "ãƒãƒ³ãƒ‰ãƒ©ãƒ¼åã§ä½¿ç”¨ã•ã‚Œã‚‹å¤‰æ•°ãŒåˆ©ç”¨ã§ããªã„å ´åˆã¯ã€ãƒ—レイ全体ãŒå¤±æ•—ã—ã¾ã™ã€‚変数 mid-play を変更ã™ã‚‹ã¨ã€æ–°ã—ã作æˆã•ã‚ŒãŸãƒãƒ³ãƒ‰ãƒ©ãƒ¼ãŒ **作æˆã•ã‚Œã¾ã›ã‚“**。" -#: ../../rst/user_guide/playbooks_handlers.rst:98 +#: ../../rst/user_guide/playbooks_handlers.rst:104 msgid "Instead, place variables in the task parameters of your handler. You can load the values using ``include_vars`` like this:" msgstr "代ã‚ã‚Šã«ã€ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã®ã‚¿ã‚¹ã‚¯ãƒ‘ラメーターã«å¤‰æ•°ã‚’é…ç½®ã—ã¾ã™ã€‚以下ã®ã‚ˆã†ã« ``include_vars`` を使用ã—ã¦ã€å€¤ã‚’èªã¿è¾¼ã‚€ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_handlers.rst:112 -msgid "Handlers can also \"listen\" to generic topics, and tasks can notify those topics as follows::" +#: ../../rst/user_guide/playbooks_handlers.rst:118 +msgid "Handlers can also \"listen\" to generic topics, and tasks can notify those topics as follows:" msgstr "ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã¯ä¸€èˆ¬çš„ãªãƒˆãƒ”ックを「リッスンã€ã™ã‚‹ã“ã¨ã‚‚ã§ãã€ã‚¿ã‚¹ã‚¯ã¯æ¬¡ã®ã‚ˆã†ã«ãれらã®ãƒˆãƒ”ックã«é€šçŸ¥ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_handlers.rst:132 +#: ../../rst/user_guide/playbooks_handlers.rst:140 msgid "This use makes it much easier to trigger multiple handlers. It also decouples handlers from their names, making it easier to share handlers among playbooks and roles (especially when using 3rd party roles from a shared source like Galaxy)." msgstr "ã“ã‚Œã«ã‚ˆã‚Šã€è¤‡æ•°ã®ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã‚’ç°¡å˜ã«ç™ºç”Ÿã•ã›ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã¾ãŸã€ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã‚’åå‰ã‹ã‚‰åˆ‡ã‚Šé›¢ã™ã“ã¨ã§ã€Playbook ã‚„ãƒãƒ¼ãƒ«é–“ã§ã®ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã®å…±æœ‰ãŒå®¹æ˜“ã«ãªã‚Šã¾ã™ (特㫠Galaxy ã®ã‚ˆã†ãªå…±æœ‰ã‚½ãƒ¼ã‚¹ã‹ã‚‰ã‚µãƒ¼ãƒ‰ãƒ‘ーティーã®ãƒãƒ¼ãƒ«ã‚’使用ã™ã‚‹å ´åˆ)。" -#: ../../rst/user_guide/playbooks_handlers.rst:137 +#: ../../rst/user_guide/playbooks_handlers.rst:145 msgid "Handlers always run in the order they are defined, not in the order listed in the notify-statement. This is also the case for handlers using `listen`." msgstr "ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã¯ã€notify-statement ã«è¨˜è¼‰ã•ã‚Œã¦ã„ã‚‹é †ç•ªã§ã¯ãªãã€å¸¸ã«å®šç¾©ã•ã‚Œã¦ã„ã‚‹é †ç•ªã§å®Ÿè¡Œã—ã¾ã™ã€‚ã“ã‚Œã¯ã€`listen` を使用ã—ã¦ã„ã‚‹ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã«ã‚‚当ã¦ã¯ã¾ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_handlers.rst:138 +#: ../../rst/user_guide/playbooks_handlers.rst:146 msgid "Handler names and `listen` topics live in a global namespace." msgstr "ãƒãƒ³ãƒ‰ãƒ©ãƒ¼å㨠`listen` トピックã¯ã€ã‚°ãƒãƒ¼ãƒãƒ«ãªåå‰ç©ºé–“ã«ã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_handlers.rst:139 +#: ../../rst/user_guide/playbooks_handlers.rst:147 msgid "Handler names are templatable and `listen` topics are not." msgstr "ãƒãƒ³ãƒ‰ãƒ©ãƒ¼åã¯ä¸€æ™‚çš„ãªã‚‚ã®ã§ã™ãŒã€`listen` トピックã¯ä¸€æ™‚çš„ã§ã¯ã‚ã‚Šã¾ã›ã‚“。" -#: ../../rst/user_guide/playbooks_handlers.rst:140 +#: ../../rst/user_guide/playbooks_handlers.rst:148 msgid "Use unique handler names. If you trigger more than one handler with the same name, the first one(s) get overwritten. Only the last one defined will run." msgstr "ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã®åå‰ã¯ä¸€æ„ã«ã—ã¦ãã ã•ã„。åŒã˜åå‰ã§è¤‡æ•°ã®ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã‚’発生ã•ã›ã‚‹å ´åˆã€æœ€åˆã®ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã¯ä¸Šæ›¸ãã•ã‚Œã¾ã™ã€‚最後ã«å®šç¾©ã•ã‚ŒãŸã‚‚ã®ã ã‘ãŒå®Ÿè¡Œã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_handlers.rst:141 +#: ../../rst/user_guide/playbooks_handlers.rst:149 msgid "You can notify a handler defined inside a static include." msgstr "é™çš„インクルードã®ä¸ã§å®šç¾©ã•ã‚ŒãŸãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã‚’通知ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_handlers.rst:142 +#: ../../rst/user_guide/playbooks_handlers.rst:150 msgid "You cannot notify a handler defined inside a dynamic include." msgstr "å‹•çš„ãªã‚¤ãƒ³ã‚¯ãƒ«ãƒ¼ãƒ‰å†…ã§å®šç¾©ã•ã‚ŒãŸãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã‚’通知ã™ã‚‹ã“ã¨ã¯ã§ãã¾ã›ã‚“。" -#: ../../rst/user_guide/playbooks_handlers.rst:143 +#: ../../rst/user_guide/playbooks_handlers.rst:151 msgid "A handler can not run import_role or include_role." msgstr "ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã¯ import_role ã¾ãŸã¯ include_role を実行ã§ãã¾ã›ã‚“。" -#: ../../rst/user_guide/playbooks_handlers.rst:145 +#: ../../rst/user_guide/playbooks_handlers.rst:153 msgid "When using handlers within roles, note that:" msgstr "ãƒãƒ¼ãƒ«å†…ã§ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã‚’使用ã™ã‚‹å ´åˆã¯ã€ä»¥ä¸‹ã«æ³¨æ„ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_handlers.rst:147 +#: ../../rst/user_guide/playbooks_handlers.rst:155 msgid "handlers notified within ``pre_tasks``, ``tasks``, and ``post_tasks`` sections are automatically flushed at the end of section where they were notified." msgstr "``pre_tasks`` セクションã€``tasks`` セクションã€ãŠã‚ˆã³ ``post_tasks`` セクション内ã§é€šçŸ¥ã•ã‚Œã‚‹ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã¯ã€é€šçŸ¥ã•ã‚ŒãŸã‚»ã‚¯ã‚·ãƒ§ãƒ³ã®æœ€å¾Œã«è‡ªå‹•çš„ã«ãƒ•ãƒ©ãƒƒã‚·ãƒ¥ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_handlers.rst:148 +#: ../../rst/user_guide/playbooks_handlers.rst:156 msgid "handlers notified within ``roles`` section are automatically flushed at the end of ``tasks`` section, but before any ``tasks`` handlers." msgstr "``roles``セクション内ã§é€šçŸ¥ã•ã‚Œã‚‹ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã¯ã€``tasks`` セクションã®æœ€å¾Œã§ã¯ãªãã€``tasks`` ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã®å‰ã«è‡ªå‹•çš„ã«ãƒ•ãƒ©ãƒƒã‚·ãƒ¥ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_handlers.rst:149 +#: ../../rst/user_guide/playbooks_handlers.rst:157 msgid "handlers are play scoped and as such can be used outside of the role they are defined in." msgstr "ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã¯ã‚¹ã‚³ãƒ¼ãƒ—ã®ã‚るプレイã§ã‚ã‚‹ãŸã‚ã€ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã¯å®šç¾©ã•ã‚Œã¦ã„ã‚‹ãƒãƒ¼ãƒ«ã®å¤–ã§ä½¿ç”¨ã§ãã¾ã™ã€‚" @@ -7611,106 +7608,106 @@ msgid "In Ansible 2.10 and later, we recommend you use the fully-qualified colle msgstr "Ansible 2.10 以é™ã§ã¯ã€è¤‡æ•°ã®ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«åŒã˜åå‰ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒå«ã¾ã‚Œã¦ã„ã‚‹ã“ã¨ãŒã‚ã‚‹ãŸã‚ (例: ``user``)ã€æ£ã—ã„モジュールãŒé¸æŠžã•ã‚Œã‚‹ã‚ˆã†ã«ã€Playbook ã§å®Œå…¨ä¿®é£¾ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³åを使用ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚「:ref:`collections_using_playbook`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" #: ../../rst/user_guide/playbooks_intro.rst:40 -msgid "In this example, the first play targets the web servers; the second play targets the database servers::" +msgid "In this example, the first play targets the web servers; the second play targets the database servers." msgstr "ã“ã®ä¾‹ã§ã¯ã€ç¬¬ 1 ã®ãƒ—レイ㯠Web サーãƒãƒ¼ã‚’対象ã¨ã—ã€ç¬¬ 2 ã®ãƒ—レイã¯ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã‚µãƒ¼ãƒãƒ¼ã‚’対象ã¨ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_intro.rst:71 +#: ../../rst/user_guide/playbooks_intro.rst:73 msgid "Your playbook can include more than just a hosts line and tasks. For example, the playbook above sets a ``remote_user`` for each play. This is the user account for the SSH connection. You can add other :ref:`playbook_keywords` at the playbook, play, or task level to influence how Ansible behaves. Playbook keywords can control the :ref:`connection plugin <connection_plugins>`, whether to use :ref:`privilege escalation <become>`, how to handle errors, and more. To support a variety of environments, Ansible lets you set many of these parameters as command-line flags, in your Ansible configuration, or in your inventory. Learning the :ref:`precedence rules <general_precedence_rules>` for these sources of data will help you as you expand your Ansible ecosystem." msgstr "Playbook ã«ã¯ã€ãƒ›ã‚¹ãƒˆãƒ©ã‚¤ãƒ³ã¨ã‚¿ã‚¹ã‚¯ä»¥å¤–ã®æƒ…å ±ã‚‚å«ã‚ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€ä¸Šè¨˜ã® Playbook ã§ã¯ã€å„プレイ㫠``remote_user`` ã‚’è¨å®šã—ã¦ã„ã¾ã™ã€‚ã“ã‚Œã¯ã€SSH 接続用ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã§ã™ã€‚Playbookã€ãƒ—レイã€ã¾ãŸã¯ã‚¿ã‚¹ã‚¯ãƒ¬ãƒ™ãƒ«ã§ä»–ã® :ref:`playbook_keywords` ã‚’è¿½åŠ ã—ã¦ã€Ansible ã®å‹•ä½œã«å½±éŸ¿ã‚’与ãˆã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚Playbook ã®ã‚ーワードã§ã¯ã€:ref:`connection プラグイン <connection_plugins>` ã§ã€:ref:`ç‰¹æ¨©æ˜‡æ ¼ <become>` を使用ã™ã‚‹ã‹ã©ã†ã‹ã€ã‚¨ãƒ©ãƒ¼ã‚’ã©ã®ã‚ˆã†ã«å‡¦ç†ã™ã‚‹ã‹ãªã©ã‚’制御ã§ãã¾ã™ã€‚ã•ã¾ã–ã¾ãªç’°å¢ƒã«å¯¾å¿œã™ã‚‹ãŸã‚ã€Ansible ã§ã¯ã€ã“れらã®ãƒ‘ラメーターã®å¤šãをコマンドラインフラグã€Ansible ã®æ§‹æˆã€ã¾ãŸã¯ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã§è¨å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“れらã®ãƒ‡ãƒ¼ã‚¿ã‚½ãƒ¼ã‚¹ã® :ref:`å„ªå…ˆé †ä½ã®ãƒ«ãƒ¼ãƒ« <general_precedence_rules>` ã‚’å¦ã¶ã“ã¨ã¯ã€Ansible ã®ã‚¨ã‚³ã‚·ã‚¹ãƒ†ãƒ ã‚’æ‹¡å¼µã™ã‚‹éš›ã«å½¹ç«‹ã¡ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_intro.rst:76 +#: ../../rst/user_guide/playbooks_intro.rst:78 msgid "Task execution" msgstr "タスクã®å®Ÿè¡Œ" -#: ../../rst/user_guide/playbooks_intro.rst:78 +#: ../../rst/user_guide/playbooks_intro.rst:80 msgid "By default, Ansible executes each task in order, one at a time, against all machines matched by the host pattern. Each task executes a module with specific arguments. When a task has executed on all target machines, Ansible moves on to the next task. You can use :ref:`strategies <playbooks_strategies>` to change this default behavior. Within each play, Ansible applies the same task directives to all hosts. If a task fails on a host, Ansible takes that host out of the rotation for the rest of the playbook." msgstr "デフォルトã§ã¯ã€Ansible ã¯ã€ãƒ›ã‚¹ãƒˆãƒ‘ターンã«ä¸€è‡´ã™ã‚‹ã™ã¹ã¦ã®ãƒžã‚·ãƒ³ã«å¯¾ã—ã¦ã€å„タスクを 1 ã¤ãšã¤é †ç•ªã«å®Ÿè¡Œã—ã¾ã™ã€‚å„タスクã¯ã€ç‰¹å®šã®å¼•æ•°ã‚’æŒã¤ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’実行ã—ã¾ã™ã€‚タスクãŒã™ã¹ã¦ã®ã‚¿ãƒ¼ã‚²ãƒƒãƒˆãƒžã‚·ãƒ³ã§å®Ÿè¡Œã™ã‚‹ã¨ã€Ansible ã¯æ¬¡ã®ã‚¿ã‚¹ã‚¯ã«ç§»ã‚Šã¾ã™ã€‚ã“ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã®å‹•ä½œã‚’変更ã™ã‚‹ã«ã¯ã€:ref:`ストラテジー <playbooks_strategies>` を使用ã—ã¾ã™ã€‚å„プレイã®ä¸ã§ã€Ansible ã¯åŒã˜ã‚¿ã‚¹ã‚¯ãƒ‡ã‚£ãƒ¬ã‚¯ãƒ†ã‚£ãƒ–ã‚’ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã«é©ç”¨ã—ã¾ã™ã€‚ã‚るホストã§ã‚¿ã‚¹ã‚¯ãŒå¤±æ•—ã—ãŸå ´åˆã€Ansible ã¯ãã®ãƒ›ã‚¹ãƒˆã‚’ Playbook ã®æ®‹ã‚Šã®éƒ¨åˆ†ã®ãƒãƒ¼ãƒ†ãƒ¼ã‚·ãƒ§ãƒ³ã‹ã‚‰å¤–ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_intro.rst:80 +#: ../../rst/user_guide/playbooks_intro.rst:82 msgid "When you run a playbook, Ansible returns information about connections, the ``name`` lines of all your plays and tasks, whether each task has succeeded or failed on each machine, and whether each task has made a change on each machine. At the bottom of the playbook execution, Ansible provides a summary of the nodes that were targeted and how they performed. General failures and fatal \"unreachable\" communication attempts are kept separate in the counts." msgstr "Playbook を実行ã™ã‚‹ã¨ã€Ansible ã¯æŽ¥ç¶šã«é–¢ã™ã‚‹æƒ…å ±ã€ã™ã¹ã¦ã®ãƒ—レイã¨ã‚¿ã‚¹ã‚¯ã® ``name`` è¡Œã€å„タスクãŒå„マシンã§æˆåŠŸã—ãŸã‹å¤±æ•—ã—ãŸã‹ã€ãŠã‚ˆã³å„タスクãŒå„マシンã§å¤‰æ›´ã‚’è¡Œã£ãŸã‹ã©ã†ã‹ã‚’è¿”ã—ã¾ã™ã€‚Playbook ã®å®Ÿè¡Œã®æœ€å¾Œã«ã€Ansible ã¯ã€å¯¾è±¡ã¨ãªã£ãŸãƒŽãƒ¼ãƒ‰ã¨ãã®ãƒ‘フォーマンスã®æ¦‚è¦ã‚’表示ã—ã¾ã™ã€‚一般的ãªå¤±æ•—ã¨è‡´å‘½çš„ãªã€Œåˆ°é”ä¸èƒ½ã€ã®é€šä¿¡è©¦è¡Œã¯ã€ã‚«ã‚¦ãƒ³ãƒˆã®ä¸ã§åˆ†ã‘ã¦è¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_intro.rst:85 +#: ../../rst/user_guide/playbooks_intro.rst:87 msgid "Desired state and 'idempotency'" msgstr "希望ã®çŠ¶æ…‹ãŠã‚ˆã³ã€Œå†ªç‰æ€§ã€" -#: ../../rst/user_guide/playbooks_intro.rst:87 +#: ../../rst/user_guide/playbooks_intro.rst:89 msgid "Most Ansible modules check whether the desired final state has already been achieved, and exit without performing any actions if that state has been achieved, so that repeating the task does not change the final state. Modules that behave this way are often called 'idempotent.' Whether you run a playbook once, or multiple times, the outcome should be the same. However, not all playbooks and not all modules behave this way. If you are unsure, test your playbooks in a sandbox environment before running them multiple times in production." msgstr "ã»ã¨ã‚“ã©ã® Ansible モジュールã¯ã€ç›®çš„ã®æœ€çµ‚状態ãŒã™ã§ã«é”æˆã•ã‚Œã¦ã„ã‚‹ã‹ã©ã†ã‹ã‚’確èªã—ã€ãã®çŠ¶æ…‹ãŒé”æˆã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ä½•ã‚‚実行ã›ãšã«çµ‚了ã™ã‚‹ãŸã‚ã€ã‚¿ã‚¹ã‚¯ã‚’ç¹°ã‚Šè¿”ã—ã¦ã‚‚最終状態ã¯å¤‰ã‚ã‚Šã¾ã›ã‚“。ã“ã®ã‚ˆã†ãªå‹•ä½œã‚’ã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ã€ã—ã°ã—ã°ã€Œå†ªç‰æ€§ã€ã¨å‘¼ã°ã‚Œã¾ã™ã€‚Playbook ã‚’ 1 回ã ã‘実行ã—ã¦ã‚‚ã€è¤‡æ•°å›žå®Ÿè¡Œã—ã¦ã‚‚ã€çµæžœã¯åŒã˜ã«ãªã‚‹ã¯ãšã§ã™ã€‚ã—ã‹ã—ã€ã™ã¹ã¦ã® Playbook ã‚„ã™ã¹ã¦ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãŒã“ã®ã‚ˆã†ã«å‹•ä½œã™ã‚‹ã‚ã‘ã§ã¯ã‚ã‚Šã¾ã›ã‚“。ä¸å®‰ãªå ´åˆã¯ã€å®Ÿç¨¼åƒç’°å¢ƒã§ Playbook を複数回実行ã™ã‚‹å‰ã«ã€ã‚µãƒ³ãƒ‰ãƒœãƒƒã‚¯ã‚¹ç’°å¢ƒã§ Playbook をテストã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_intro.rst:92 +#: ../../rst/user_guide/playbooks_intro.rst:94 msgid "Running playbooks" msgstr "Playbook ã®å®Ÿè¡Œ" -#: ../../rst/user_guide/playbooks_intro.rst:94 -msgid "To run your playbook, use the :ref:`ansible-playbook` command::" +#: ../../rst/user_guide/playbooks_intro.rst:96 +msgid "To run your playbook, use the :ref:`ansible-playbook` command." msgstr "Playbook を実行ã™ã‚‹ã«ã¯ã€:ref:`ansible-playbook` コマンドを使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_intro.rst:98 +#: ../../rst/user_guide/playbooks_intro.rst:102 msgid "Use the ``--verbose`` flag when running your playbook to see detailed output from successful modules as well as unsuccessful ones." msgstr "æˆåŠŸã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¨å¤±æ•—ã—ãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®è©³ç´°ãªå‡ºåŠ›ã‚’確èªã™ã‚‹ã«ã¯ã€Playbook ã®å®Ÿè¡Œæ™‚ã« ``--verbose`` フラグを使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_intro.rst:103 +#: ../../rst/user_guide/playbooks_intro.rst:107 msgid "Ansible-Pull" msgstr "ansible-pull" -#: ../../rst/user_guide/playbooks_intro.rst:105 +#: ../../rst/user_guide/playbooks_intro.rst:109 msgid "Should you want to invert the architecture of Ansible, so that nodes check in to a central location, instead of pushing configuration out to them, you can." msgstr "ノードã«è¨å®šã‚’プッシュã™ã‚‹ã®ã§ã¯ãªãã€Ansible ã®ã‚¢ãƒ¼ã‚テクãƒãƒ£ãƒ¼ã‚’逆ã«ã—ã¦ã€ãƒŽãƒ¼ãƒ‰ãŒä¸å¤®ã®å ´æ‰€ã«ãƒã‚§ãƒƒã‚¯ã‚¤ãƒ³ã™ã‚‹ã‚ˆã†ã«ã—ãŸã„å ´åˆã¯ã€ä»¥ä¸‹ã‚’è¡Œã†ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_intro.rst:108 +#: ../../rst/user_guide/playbooks_intro.rst:112 msgid "The ``ansible-pull`` is a small script that will checkout a repo of configuration instructions from git, and then run ``ansible-playbook`` against that content." msgstr "``ansible-pull`` ã¯å°ã•ãªã‚¹ã‚¯ãƒªãƒ—トã§ã€git ã‹ã‚‰è¨å®šæ–¹æ³•ã‚’ã¾ã¨ã‚ãŸãƒªãƒã‚¸ãƒˆãƒªãƒ¼ã‚’ãƒã‚§ãƒƒã‚¯ã‚¢ã‚¦ãƒˆã—ã€ãã®å†…容ã«å¯¾ã—㦠``ansible-playbook`` を実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_intro.rst:111 +#: ../../rst/user_guide/playbooks_intro.rst:115 msgid "Assuming you load balance your checkout location, ``ansible-pull`` scales essentially infinitely." msgstr "ãƒã‚§ãƒƒã‚¯ã‚¢ã‚¦ãƒˆã®å ´æ‰€ã‚’è² è·åˆ†æ•£ã™ã‚‹å ´åˆã€``ansible-pull`` ã¯åŸºæœ¬çš„ã«ç„¡é™ã«ã‚¹ã‚±ãƒ¼ãƒªãƒ³ã‚°ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_intro.rst:113 +#: ../../rst/user_guide/playbooks_intro.rst:117 msgid "Run ``ansible-pull --help`` for details." msgstr "詳細ã¯ã€ã€Œ``ansible-pull --help``ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_intro.rst:115 +#: ../../rst/user_guide/playbooks_intro.rst:119 msgid "There's also a `clever playbook <https://github.com/ansible/ansible-examples/blob/master/language_features/ansible_pull.yml>`_ available to configure ``ansible-pull`` via a crontab from push mode." msgstr "ã¾ãŸã€ãƒ—ッシュモードã‹ã‚‰ã® crontab 㧠``ansible-pull`` ã‚’è¨å®šã™ã‚‹éš›ã«åˆ©ç”¨å¯èƒ½ãª `優れ㟠Playbook <https://github.com/ansible/ansible-examples/blob/master/language_features/ansible_pull.yml>`_ ã‚‚ã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_intro.rst:118 +#: ../../rst/user_guide/playbooks_intro.rst:122 msgid "Verifying playbooks" msgstr "Playbook ã®æ¤œè¨¼" -#: ../../rst/user_guide/playbooks_intro.rst:120 +#: ../../rst/user_guide/playbooks_intro.rst:124 msgid "You may want to verify your playbooks to catch syntax errors and other problems before you run them. The :ref:`ansible-playbook` command offers several options for verification, including ``--check``, ``--diff``, ``--list-hosts``, ``--list-tasks``, and ``--syntax-check``. The :ref:`validate-playbook-tools` describes other tools for validating and testing playbooks." msgstr "Playbook を実行ã™ã‚‹å‰ã«ã€æ§‹æ–‡ã‚¨ãƒ©ãƒ¼ã‚„ãã®ä»–ã®å•é¡Œã‚’検出ã™ã‚‹ãŸã‚ã«ã€Playbook を検証ã—ãŸã„å ´åˆãŒã‚ã‚Šã¾ã™ã€‚:ref:`ansible-playbook` コマンドã«ã¯ã€``--check``ã€``--diff``ã€``--list-hosts``ã€``--list-tasks``ã€``--syntax-check`` ãªã©ã€æ¤œè¨¼ã®ãŸã‚ã®ã‚ªãƒ—ションãŒç”¨æ„ã•ã‚Œã¦ã„ã¾ã™ã€‚「:ref:`validate-playbook-tools`ã€ã§ã¯ã€Playbook ã®æ¤œè¨¼ã¨ãƒ†ã‚¹ãƒˆã®ãŸã‚ã®ä»–ã®ãƒ„ールã«ã¤ã„ã¦èª¬æ˜Žã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_intro.rst:125 +#: ../../rst/user_guide/playbooks_intro.rst:129 msgid "ansible-lint" msgstr "ansible-lint" -#: ../../rst/user_guide/playbooks_intro.rst:127 +#: ../../rst/user_guide/playbooks_intro.rst:131 msgid "You can use `ansible-lint <https://docs.ansible.com/ansible-lint/index.html>`_ for detailed, Ansible-specific feedback on your playbooks before you execute them. For example, if you run ``ansible-lint`` on the playbook called ``verify-apache.yml`` near the top of this page, you should get the following results:" msgstr "`ansible-lint <https://docs.ansible.com/ansible-lint/index.html>`_ を使用ã™ã‚‹ã¨ã€Playbook を実行ã™ã‚‹å‰ã«ã€Playbook ã«å¯¾ã™ã‚‹ Ansible 固有ã®è©³ç´°ãªãƒ•ã‚£ãƒ¼ãƒ‰ãƒãƒƒã‚¯ã‚’å¾—ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€ã“ã®ãƒšãƒ¼ã‚¸ã®ä¸Šä½ã«ã‚ã‚‹ ``verify-apache.yml`` ã¨ã„ㆠPlaybook ã«å¯¾ã—㦠``ansible-lint`` を実行ã™ã‚‹ã¨ã€ä»¥ä¸‹ã®ã‚ˆã†ãªçµæžœãŒå¾—られã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_intro.rst:136 +#: ../../rst/user_guide/playbooks_intro.rst:140 msgid "The `ansible-lint default rules <https://docs.ansible.com/ansible-lint/rules/default_rules.html>`_ page describes each error. For ``[403]``, the recommended fix is to change ``state: latest`` to ``state: present`` in the playbook." msgstr "`ansible-lint デフォルトルール <https://docs.ansible.com/ansible-lint/rules/default_rules.html>`_ ページã«ã¯ã€å„エラーã«ã¤ã„ã¦èª¬æ˜Žã—ã¦ã„ã¾ã™ã€‚``[403]`` ã«ã¤ã„ã¦ã¯ã€Playbook 㧠``state: latest`` ã‚’ ``state: present`` ã«å¤‰æ›´ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_intro.rst:140 +#: ../../rst/user_guide/playbooks_intro.rst:144 msgid "`ansible-lint <https://docs.ansible.com/ansible-lint/index.html>`_" msgstr "`ansible-lint <https://docs.ansible.com/ansible-lint/index.html>`_" -#: ../../rst/user_guide/playbooks_intro.rst:141 +#: ../../rst/user_guide/playbooks_intro.rst:145 msgid "Learn how to test Ansible Playbooks syntax" msgstr "Ansible Playbook 構文ã®ãƒ†ã‚¹ãƒˆæ–¹æ³•ã«ã¤ã„ã¦" -#: ../../rst/user_guide/playbooks_intro.rst:145 +#: ../../rst/user_guide/playbooks_intro.rst:149 msgid "Tips for managing playbooks in the real world" msgstr "実際㮠Playbook ã®ç®¡ç†ã«é–¢ã™ã‚‹ã•ã¾ã–ã¾ãªãƒ’ント" -#: ../../rst/user_guide/playbooks_intro.rst:149 +#: ../../rst/user_guide/playbooks_intro.rst:153 msgid "Learn to extend Ansible by writing your own modules" msgstr "独自ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’作æˆã—㦠Ansible ã‚’æ‹¡å¼µã™ã‚‹æ–¹æ³•ã«ã¤ã„ã¦" -#: ../../rst/user_guide/playbooks_intro.rst:153 +#: ../../rst/user_guide/playbooks_intro.rst:157 msgid "Complete end-to-end playbook examples" msgstr "完全ãªã‚¨ãƒ³ãƒ‰ãƒ„ーエンド Playbook ã®ä¾‹" @@ -7727,10 +7724,10 @@ msgid "Using lookups in variables" msgstr "変数ã§ã® lookup ã®ä½¿ç”¨" #: ../../rst/user_guide/playbooks_lookups.rst:14 -msgid "You can populate variables using lookups. Ansible evaluates the value each time it is executed in a task (or template)::" +msgid "You can populate variables using lookups. Ansible evaluates the value each time it is executed in a task (or template)." msgstr "lookup を使用ã—ã¦å¤‰æ•°ã‚’è¨å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚Ansible ã¯ã€ã‚¿ã‚¹ã‚¯ (ã¾ãŸã¯ãƒ†ãƒ³ãƒ—レート) ã§å®Ÿè¡Œã•ã‚Œã‚‹ãŸã³ã«å€¤ã‚’評価ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_lookups.rst:22 +#: ../../rst/user_guide/playbooks_lookups.rst:24 msgid "For more details and a list of lookup plugins in ansible-core, see :ref:`plugins_lookup`. You may also find lookup plugins in collections. You can review a list of lookup plugins installed on your control machine with the command ``ansible-doc -l -t lookup``." msgstr "ansible-core ã® lookup プラグインã®è©³ç´°ã¨ä¸€è¦§ã¯ã€ã€Œ:ref:`plugins_lookup`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。ã¾ãŸã€lookup プラグインã¯ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã«ã‚‚å«ã¾ã‚Œã¦ã„ã¾ã™ã€‚コントãƒãƒ¼ãƒ«ãƒžã‚·ãƒ³ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ lookup プラグインã®ãƒªã‚¹ãƒˆã¯ã€``ansible-doc -l -t lookup`` コマンドã§ç¢ºèªã§ãã¾ã™ã€‚" @@ -7779,322 +7776,322 @@ msgid "Be careful when changing ``with_items`` to ``loop``, as ``with_items`` pe msgstr "``with_items`` ã‚’ ``loop`` ã«å¤‰æ›´ã™ã‚‹éš›ã«ã¯ã€``with_items`` ãŒæš—é»™ã®å˜ä¸€ãƒ¬ãƒ™ãƒ«ã®ãƒ•ãƒ©ãƒƒãƒˆåŒ–ã‚’è¡Œã†ãŸã‚注æ„ãŒå¿…è¦ã§ã™ã€‚æ£ç¢ºãªçµæžœã‚’å¾—ã‚‹ãŸã‚ã«ã¯ã€``flatten(1)`` 㨠``loop`` ã®ä½µç”¨ãŒå¿…è¦ã«ãªã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€æ¬¡ã¨åŒã˜å‡ºåŠ›ã‚’å¾—ã‚‹ã«ã¯ã€" #: ../../rst/user_guide/playbooks_loops.rst:34 -msgid "you would need::" +msgid "you would need" msgstr "以下ãŒå¿…è¦ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:38 +#: ../../rst/user_guide/playbooks_loops.rst:40 msgid "Any ``with_*`` statement that requires using ``lookup`` within a loop should not be converted to use the ``loop`` keyword. For example, instead of doing:" msgstr "ループ内㧠``lookup`` を使用ã™ã‚‹å¿…è¦ã®ã‚ã‚‹ ``with_*`` æ–‡ã¯ã€``loop`` ã‚ーワードを使用ã™ã‚‹ã‚ˆã†ã«å¤‰æ›ã—ãªã„ã§ãã ã•ã„。ãŸã¨ãˆã°ã€ä»£ã‚ã‚Šã«ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:44 -msgid "it's cleaner to keep::" +#: ../../rst/user_guide/playbooks_loops.rst:46 +msgid "it's cleaner to keep" msgstr "ä¿æŒã™ã‚‹æ–¹ãŒè¦‹ãŸç›®ãŒã™ã£ãã‚Šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:51 +#: ../../rst/user_guide/playbooks_loops.rst:55 msgid "Standard loops" msgstr "標準ループ" -#: ../../rst/user_guide/playbooks_loops.rst:54 +#: ../../rst/user_guide/playbooks_loops.rst:58 msgid "Iterating over a simple list" msgstr "シンプルãªãƒªã‚¹ãƒˆã§ã®å復" -#: ../../rst/user_guide/playbooks_loops.rst:56 -msgid "Repeated tasks can be written as standard loops over a simple list of strings. You can define the list directly in the task::" +#: ../../rst/user_guide/playbooks_loops.rst:60 +msgid "Repeated tasks can be written as standard loops over a simple list of strings. You can define the list directly in the task." msgstr "ç¹°ã‚Šè¿”ã•ã‚Œã‚‹ã‚¿ã‚¹ã‚¯ã¯ã€æ–‡å—列ã®å˜ç´”ãªãƒªã‚¹ãƒˆã«å¯¾ã™ã‚‹æ¨™æº–çš„ãªãƒ«ãƒ¼ãƒ—ã¨ã—ã¦è¨˜è¿°ã§ãã¾ã™ã€‚ã“ã®ãƒªã‚¹ãƒˆã¯ã‚¿ã‚¹ã‚¯ã®ä¸ã§ç›´æŽ¥å®šç¾©ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:67 -msgid "You can define the list in a variables file, or in the 'vars' section of your play, then refer to the name of the list in the task::" +#: ../../rst/user_guide/playbooks_loops.rst:73 +msgid "You can define the list in a variables file, or in the 'vars' section of your play, then refer to the name of the list in the task." msgstr "変数ファイルã§ãƒªã‚¹ãƒˆã‚’定義ã™ã‚‹ã‹ã€ãƒ—レイã®ã€Œvarsã€ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã€ã‚¿ã‚¹ã‚¯å†…ã®ãƒªã‚¹ãƒˆã®åå‰ã‚’å‚ç…§ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:71 -msgid "Either of these examples would be the equivalent of::" +#: ../../rst/user_guide/playbooks_loops.rst:79 +msgid "Either of these examples would be the equivalent of" msgstr "ã“れらã®ä¾‹ã®ã„ãšã‚Œã‚‚ã€ä»¥ä¸‹ã¨åŒç‰ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:85 -msgid "You can pass a list directly to a parameter for some plugins. Most of the packaging modules, like :ref:`yum <yum_module>` and :ref:`apt <apt_module>`, have this capability. When available, passing the list to a parameter is better than looping over the task. For example::" +#: ../../rst/user_guide/playbooks_loops.rst:95 +msgid "You can pass a list directly to a parameter for some plugins. Most of the packaging modules, like :ref:`yum <yum_module>` and :ref:`apt <apt_module>`, have this capability. When available, passing the list to a parameter is better than looping over the task. For example" msgstr "ã„ãã¤ã‹ã®ãƒ—ラグインã§ã¯ã€ãƒ‘ラメーターã«ãƒªã‚¹ãƒˆã‚’直接渡ã™ã“ã¨ãŒã§ãã¾ã™ã€‚:ref:`yum <yum_module>` ã‚„ :ref:`apt <apt_module>` ãªã©ã€ã»ã¨ã‚“ã©ã®ãƒ‘ッケージングモジュールã«ã“ã®æ©Ÿèƒ½ãŒã‚ã‚Šã¾ã™ã€‚利用ã§ãã‚‹å ´åˆã¯ã€ãƒªã‚¹ãƒˆã‚’パラメーターã«æ¸¡ã™æ–¹ãŒã€ã‚¿ã‚¹ã‚¯ã‚’ループã•ã›ã‚‹ã‚ˆã‚Šã‚‚良ã„ã§ã—ょã†ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:98 +#: ../../rst/user_guide/playbooks_loops.rst:110 msgid "Check the :ref:`module documentation <modules_by_category>` to see if you can pass a list to any particular module's parameter(s)." msgstr ":ref:`モジュールã®ãƒ‰ã‚ュメント <modules_by_category>` ã§ã€ç‰¹å®šãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ‘ラメーターã«ãƒªã‚¹ãƒˆã‚’渡ã™ã“ã¨ãŒã§ãã‚‹ã‹ã©ã†ã‹ã‚’確èªã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:101 +#: ../../rst/user_guide/playbooks_loops.rst:113 msgid "Iterating over a list of hashes" msgstr "ãƒãƒƒã‚·ãƒ¥ãƒªã‚¹ãƒˆã§ã®å復" -#: ../../rst/user_guide/playbooks_loops.rst:103 -msgid "If you have a list of hashes, you can reference subkeys in a loop. For example::" +#: ../../rst/user_guide/playbooks_loops.rst:115 +msgid "If you have a list of hashes, you can reference subkeys in a loop. For example:" msgstr "ãƒãƒƒã‚·ãƒ¥ãƒªã‚¹ãƒˆãŒã‚ã‚‹å ´åˆã¯ã€ãƒ«ãƒ¼ãƒ—ã§ã‚µãƒ–ã‚ーをå‚ç…§ã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:114 +#: ../../rst/user_guide/playbooks_loops.rst:128 msgid "When combining :ref:`conditionals <playbooks_conditionals>` with a loop, the ``when:`` statement is processed separately for each item. See :ref:`the_when_statement` for examples." msgstr ":ref:`conditionals <playbooks_conditionals>` ã¨ãƒ«ãƒ¼ãƒ—を組ã¿åˆã‚ã›ã‚‹ã¨ã€``when:`` æ–‡ã¯å„é …ç›®ã«ã¤ã„ã¦å€‹åˆ¥ã«å‡¦ç†ã•ã‚Œã¾ã™ã€‚例ã¯ã€Œ:ref:`the_when_statement`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_loops.rst:118 +#: ../../rst/user_guide/playbooks_loops.rst:132 msgid "Iterating over a dictionary" msgstr "ディクショナリーã§ã®å復" -#: ../../rst/user_guide/playbooks_loops.rst:120 +#: ../../rst/user_guide/playbooks_loops.rst:134 msgid "To loop over a dict, use the :ref:`dict2items <dict_filter>`:" msgstr "ディクショナリーã§ãƒ«ãƒ¼ãƒ—ã™ã‚‹ã«ã¯ã€:ref:`dict2items <dict_filter>` を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:133 +#: ../../rst/user_guide/playbooks_loops.rst:147 msgid "Here, we are iterating over `tag_data` and printing the key and the value from it." msgstr "ã“ã“ã§ã¯ã€`tag_data` ã‚’ç¹°ã‚Šè¿”ã—処ç†ã—ã€ã‚ーã¨å€¤ã‚’出力ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:136 +#: ../../rst/user_guide/playbooks_loops.rst:150 msgid "Registering variables with a loop" msgstr "ループã«ã‚ˆã‚‹å¤‰æ•°ã®ç™»éŒ²" -#: ../../rst/user_guide/playbooks_loops.rst:138 -msgid "You can register the output of a loop as a variable. For example::" +#: ../../rst/user_guide/playbooks_loops.rst:152 +msgid "You can register the output of a loop as a variable. For example" msgstr "ループã®å‡ºåŠ›ã‚’変数ã¨ã—ã¦ç™»éŒ²ã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€æ¬¡ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:147 -msgid "When you use ``register`` with a loop, the data structure placed in the variable will contain a ``results`` attribute that is a list of all responses from the module. This differs from the data structure returned when using ``register`` without a loop::" +#: ../../rst/user_guide/playbooks_loops.rst:163 +msgid "When you use ``register`` with a loop, the data structure placed in the variable will contain a ``results`` attribute that is a list of all responses from the module. This differs from the data structure returned when using ``register`` without a loop." msgstr "``register`` をループã§ä½¿ç”¨ã™ã‚‹ã¨ã€å¤‰æ•°ã«é…ç½®ã•ã‚Œã‚‹ãƒ‡ãƒ¼ã‚¿æ§‹é€ ã«ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‹ã‚‰ã®ã™ã¹ã¦ã®å¿œç”ã®ãƒªã‚¹ãƒˆã§ã‚ã‚‹ ``results`` 属性ãŒå«ã¾ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ã€``register`` をループãªã—ã§ä½¿ç”¨ã—ãŸã¨ãã«è¿”ã•ã‚Œã‚‹ãƒ‡ãƒ¼ã‚¿æ§‹é€ ã¨ã¯ç•°ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:186 -msgid "Subsequent loops over the registered variable to inspect the results may look like::" +#: ../../rst/user_guide/playbooks_loops.rst:204 +msgid "Subsequent loops over the registered variable to inspect the results may look like" msgstr "登録済ã¿ã®å¤‰æ•°ã§å¾Œç¶šã®ãƒ«ãƒ¼ãƒ—を実行ã—ã¦çµæžœã‚’検査ã™ã‚‹ã¨ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:194 -msgid "During iteration, the result of the current item will be placed in the variable::" +#: ../../rst/user_guide/playbooks_loops.rst:214 +msgid "During iteration, the result of the current item will be placed in the variable." msgstr "å復時ã«ã€ç¾åœ¨ã®é …ç›®ã®çµæžœã¯å¤‰æ•°ã«é…ç½®ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:207 +#: ../../rst/user_guide/playbooks_loops.rst:229 msgid "Complex loops" msgstr "複雑ãªãƒ«ãƒ¼ãƒ—" -#: ../../rst/user_guide/playbooks_loops.rst:210 +#: ../../rst/user_guide/playbooks_loops.rst:232 msgid "Iterating over nested lists" msgstr "入れåã®ãƒªã‚¹ãƒˆã§ã®å復" -#: ../../rst/user_guide/playbooks_loops.rst:212 -msgid "You can use Jinja2 expressions to iterate over complex lists. For example, a loop can combine nested lists::" +#: ../../rst/user_guide/playbooks_loops.rst:234 +msgid "You can use Jinja2 expressions to iterate over complex lists. For example, a loop can combine nested lists." msgstr "Jinja2 ã®å¼ã‚’使用ã—ã¦ã€è¤‡é›‘ãªãƒªã‚¹ãƒˆã‚’ç¹°ã‚Šè¿”ã—処ç†ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€ãƒ«ãƒ¼ãƒ—ã¯å…¥ã‚Œåã«ãªã£ãŸãƒªã‚¹ãƒˆã‚’組ã¿åˆã‚ã›ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:226 +#: ../../rst/user_guide/playbooks_loops.rst:250 msgid "Retrying a task until a condition is met" msgstr "æ¡ä»¶ãŒæº€ãŸã•ã‚Œã‚‹ã¾ã§ã‚¿ã‚¹ã‚¯ã®å†è©¦è¡Œ" -#: ../../rst/user_guide/playbooks_loops.rst:230 -msgid "You can use the ``until`` keyword to retry a task until a certain condition is met. Here's an example::" +#: ../../rst/user_guide/playbooks_loops.rst:254 +msgid "You can use the ``until`` keyword to retry a task until a certain condition is met. Here's an example:" msgstr "``until`` ã‚ーワードを使用ã™ã‚‹ã¨ã€ã‚ã‚‹æ¡ä»¶ãŒæº€ãŸã•ã‚Œã‚‹ã¾ã§ã‚¿ã‚¹ã‚¯ã‚’å†è©¦è¡Œã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:239 +#: ../../rst/user_guide/playbooks_loops.rst:265 msgid "This task runs up to 5 times with a delay of 10 seconds between each attempt. If the result of any attempt has \"all systems go\" in its stdout, the task succeeds. The default value for \"retries\" is 3 and \"delay\" is 5." msgstr "ã“ã®ã‚¿ã‚¹ã‚¯ã¯ã€å„試行ã®é–“ã« 10 秒ã®é…延を置ã„ã¦æœ€å¤§ 5 回実行ã•ã‚Œã‚‹ã€‚試行ã®çµæžœã€æ¨™æº–出力ã«ã€Œall systems goã€ã¨è¡¨ç¤ºã•ã‚Œã¦ã„ã‚Œã°ã€ã‚¿ã‚¹ã‚¯ã¯æˆåŠŸã§ã™ã€‚「retries (å†è©¦è¡Œ)ã€ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã¯ 3ã€ã€Œdelay (é…延)ã€ã¯ 5 ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:241 +#: ../../rst/user_guide/playbooks_loops.rst:267 msgid "To see the results of individual retries, run the play with ``-vv``." msgstr "個別ã®å†è©¦è¡Œã®çµæžœã‚’表示ã™ã‚‹ã«ã¯ã€``-vv`` ã§ãƒ—レイを実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:243 +#: ../../rst/user_guide/playbooks_loops.rst:269 msgid "When you run a task with ``until`` and register the result as a variable, the registered variable will include a key called \"attempts\", which records the number of the retries for the task." msgstr "``until`` を使用ã—ã¦ã‚¿ã‚¹ã‚¯ã‚’実行ã—ã€çµæžœã‚’変数ã¨ã—ã¦ç™»éŒ²ã™ã‚‹å ´åˆã¯ã€ç™»éŒ²æ¸ˆã¿å¤‰æ•°ã«ã¯ã€Œattemptsã€ã¨å‘¼ã°ã‚Œã‚‹éµãŒå«ã¾ã‚Œã€ã‚¿ã‚¹ã‚¯ã®å†è©¦è¡Œå›žæ•°ã‚’記録ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:245 +#: ../../rst/user_guide/playbooks_loops.rst:271 msgid "You must set the ``until`` parameter if you want a task to retry. If ``until`` is not defined, the value for the ``retries`` parameter is forced to 1." msgstr "タスクãŒå†è©¦è¡Œã™ã‚‹ã«ã¯ã€``until`` パラメーターをè¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚``until`` ãŒå®šç¾©ã•ã‚Œã¦ã„ãªã„å ´åˆã¯ã€``retries`` パラメーターã®å€¤ãŒ 1 ã«å¼·åˆ¶ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:248 +#: ../../rst/user_guide/playbooks_loops.rst:274 msgid "Looping over inventory" msgstr "インベントリーã®ãƒ«ãƒ¼ãƒ—" -#: ../../rst/user_guide/playbooks_loops.rst:250 -msgid "To loop over your inventory, or just a subset of it, you can use a regular ``loop`` with the ``ansible_play_batch`` or ``groups`` variables::" +#: ../../rst/user_guide/playbooks_loops.rst:276 +msgid "To loop over your inventory, or just a subset of it, you can use a regular ``loop`` with the ``ansible_play_batch`` or ``groups`` variables." msgstr "インベントリーやãã®ä¸€éƒ¨ã ã‘をループã•ã›ã‚‹ã«ã¯ã€é€šå¸¸ã® ``loop`` ã« ``ansible_play_batch`` 変数や ``groups`` å¤‰æ•°ã‚’åŠ ãˆãŸã‚‚ã®ã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:262 -msgid "There is also a specific lookup plugin ``inventory_hostnames`` that can be used like this::" +#: ../../rst/user_guide/playbooks_loops.rst:290 +msgid "There is also a specific lookup plugin ``inventory_hostnames`` that can be used like this" msgstr "ã¾ãŸã€ä»¥ä¸‹ã®ã‚ˆã†ãªç‰¹å®šã® lookup プラグイン ``inventory_hostnames`` も使用ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:274 +#: ../../rst/user_guide/playbooks_loops.rst:304 msgid "More information on the patterns can be found in :ref:`intro_patterns`." msgstr "パターンã®è©³ç´°ã¯ã€ã€Œ:ref:`intro_patterns`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_loops.rst:279 +#: ../../rst/user_guide/playbooks_loops.rst:309 msgid "Ensuring list input for ``loop``: using ``query`` rather than ``lookup``" msgstr "``loop`` ã®ãƒªã‚¹ãƒˆå…¥åŠ›ã®ç¢ºä¿: ``lookup`` ã®ä»£ã‚ã‚Šã« ``query`` を使用" -#: ../../rst/user_guide/playbooks_loops.rst:281 +#: ../../rst/user_guide/playbooks_loops.rst:311 msgid "The ``loop`` keyword requires a list as input, but the ``lookup`` keyword returns a string of comma-separated values by default. Ansible 2.5 introduced a new Jinja2 function named :ref:`query <query>` that always returns a list, offering a simpler interface and more predictable output from lookup plugins when using the ``loop`` keyword." msgstr "``loop`` ã‚ーワードã¯å…¥åŠ›ã¨ã—ã¦ãƒªã‚¹ãƒˆã‚’å¿…è¦ã¨ã—ã¾ã™ãŒã€``lookup`` ã‚ーワードã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã‚³ãƒ³ãƒžã§åŒºåˆ‡ã‚‰ã‚ŒãŸå€¤ã®æ–‡å—列を返ã™ã‚ˆã†ã«ãªã£ã¦ã„ã¾ã™ã€‚Ansible 2.5 ã§ã¯ã€:ref:`query <query>` ã¨ã„ã†åå‰ã®æ–°ã—ã„ Jinja2 関数ãŒå°Žå…¥ã•ã‚Œã€å¸¸ã«ãƒªã‚¹ãƒˆã‚’è¿”ã™ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ãŒã‚·ãƒ³ãƒ—ルã«ãªã‚Šã€``loop`` ã‚ーワードを使用ã—ãŸå ´åˆã® lookup プラグインã®å‡ºåŠ›ãŒã‚ˆã‚Šäºˆæ¸¬ã—ã‚„ã™ããªã‚Šã¾ã—ãŸã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:283 +#: ../../rst/user_guide/playbooks_loops.rst:313 msgid "You can force ``lookup`` to return a list to ``loop`` by using ``wantlist=True``, or you can use ``query`` instead." msgstr "``wantlist=True`` を使用ã™ã‚Œã°ã€``lookup`` ãŒãƒªã‚¹ãƒˆã‚’ ``loop`` ã«è¿”ã™ã‚ˆã†ã«å¼·åˆ¶ã—ãŸã‚Šã€ä»£ã‚ã‚Šã« ``query`` を使用ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:285 -msgid "These examples do the same thing::" -msgstr "ã“れらã®ä¾‹ã§ã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" +#: ../../rst/user_guide/playbooks_loops.rst:315 +msgid "The following two examples do the same thing." +msgstr "以下ã®2ã¤ã®ä¾‹ã¯ã€åŒã˜ã“ã¨ã‚’ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:295 +#: ../../rst/user_guide/playbooks_loops.rst:327 msgid "Adding controls to loops" msgstr "ループã¸ã®ã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ«ã®è¿½åŠ " -#: ../../rst/user_guide/playbooks_loops.rst:298 +#: ../../rst/user_guide/playbooks_loops.rst:330 msgid "The ``loop_control`` keyword lets you manage your loops in useful ways." msgstr "``loop_control`` ã‚ーワードを使用ã™ã‚‹ã¨ã€ãƒ«ãƒ¼ãƒ—を便利ãªæ–¹æ³•ã§ç®¡ç†ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:301 +#: ../../rst/user_guide/playbooks_loops.rst:333 msgid "Limiting loop output with ``label``" msgstr "``label`` を使用ã—ãŸãƒ«ãƒ¼ãƒ—出力ã®åˆ¶é™" -#: ../../rst/user_guide/playbooks_loops.rst:304 -msgid "When looping over complex data structures, the console output of your task can be enormous. To limit the displayed output, use the ``label`` directive with ``loop_control``::" +#: ../../rst/user_guide/playbooks_loops.rst:336 +msgid "When looping over complex data structures, the console output of your task can be enormous. To limit the displayed output, use the ``label`` directive with ``loop_control``." msgstr "複雑ãªãƒ‡ãƒ¼ã‚¿æ§‹é€ をループã—ã¦ã„ã‚‹ã¨ã€ã‚¿ã‚¹ã‚¯ã®ã‚³ãƒ³ã‚½ãƒ¼ãƒ«å‡ºåŠ›ãŒè†¨å¤§ã«ãªã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚表示ã•ã‚Œã‚‹å‡ºåŠ›ã‚’制é™ã™ã‚‹ã«ã¯ã€``label`` ディレクティブ㨠``loop_control`` を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:321 +#: ../../rst/user_guide/playbooks_loops.rst:355 msgid "The output of this task will display just the ``name`` field for each ``item`` instead of the entire contents of the multi-line ``{{ item }}`` variable." msgstr "ã“ã®ã‚¿ã‚¹ã‚¯ã®å‡ºåŠ›ã«ã¯ã€è¤‡æ•°è¡Œã® ``{{ item }}`` 変数ã®å†…容全体ã§ã¯ãªãã€å„ ``item`` ã® ``name`` フィールドã®ã¿ãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:323 +#: ../../rst/user_guide/playbooks_loops.rst:357 msgid "This is for making console output more readable, not protecting sensitive data. If there is sensitive data in ``loop``, set ``no_log: yes`` on the task to prevent disclosure." msgstr "ã“ã‚Œã¯ã‚³ãƒ³ã‚½ãƒ¼ãƒ«å‡ºåŠ›ã‚’èªã¿ã‚„ã™ãã™ã‚‹ãŸã‚ã®ã‚‚ã®ã§ã€æ©Ÿå¯†ãƒ‡ãƒ¼ã‚¿ã‚’ä¿è·ã™ã‚‹ã‚‚ã®ã§ã¯ã‚ã‚Šã¾ã›ã‚“。``loop`` ã«æ©Ÿå¯†ãƒ‡ãƒ¼ã‚¿ãŒã‚ã‚‹å ´åˆã¯ã€``no_log: yes`` をタスクã«è¨å®šã—ã¦æ¼æ´©ã‚’防ãŽã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:326 +#: ../../rst/user_guide/playbooks_loops.rst:360 msgid "Pausing within a loop" msgstr "ループ内ã§ã®ä¸€æ™‚åœæ¢" -#: ../../rst/user_guide/playbooks_loops.rst:329 -msgid "To control the time (in seconds) between the execution of each item in a task loop, use the ``pause`` directive with ``loop_control``::" +#: ../../rst/user_guide/playbooks_loops.rst:363 +msgid "To control the time (in seconds) between the execution of each item in a task loop, use the ``pause`` directive with ``loop_control``." msgstr "タスクループã®å„é …ç›®ã®å®Ÿè¡Œé–“隔を (秒å˜ä½) ã§åˆ¶å¾¡ã™ã‚‹ã«ã¯ã€``pause`` 㧠``loop_control`` ディレクティブを使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:343 +#: ../../rst/user_guide/playbooks_loops.rst:379 msgid "Tracking progress through a loop with ``index_var``" msgstr "``index_var`` ã®ã‚るループã§ã®é€²æ—ã®è¿½è·¡" -#: ../../rst/user_guide/playbooks_loops.rst:346 -msgid "To keep track of where you are in a loop, use the ``index_var`` directive with ``loop_control``. This directive specifies a variable name to contain the current loop index::" +#: ../../rst/user_guide/playbooks_loops.rst:382 +msgid "To keep track of where you are in a loop, use the ``index_var`` directive with ``loop_control``. This directive specifies a variable name to contain the current loop index." msgstr "ループ内ã®ã©ã“ã«ã„ã‚‹ã‹ã‚’把æ¡ã™ã‚‹ã«ã¯ã€``loop_control`` ã¨ã¨ã‚‚ã« ``index_var`` ディレクティブを使用ã—ã¾ã™ã€‚ã“ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒ†ã‚£ãƒ–ã¯ã€ç¾åœ¨ã®ãƒ«ãƒ¼ãƒ—ã®ã‚¤ãƒ³ãƒ‡ãƒƒã‚¯ã‚¹ã‚’æ ¼ç´ã™ã‚‹å¤‰æ•°åを指定ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:358 +#: ../../rst/user_guide/playbooks_loops.rst:396 msgid "`index_var` is 0 indexed." msgstr "`index_var` ã¯ã€0 インデックスã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:361 +#: ../../rst/user_guide/playbooks_loops.rst:399 msgid "Defining inner and outer variable names with ``loop_var``" msgstr "``loop_var`` を使用ã—ãŸå†…部変数åãŠã‚ˆã³å¤–部変数åã®å®šç¾©" -#: ../../rst/user_guide/playbooks_loops.rst:364 -msgid "You can nest two looping tasks using ``include_tasks``. However, by default Ansible sets the loop variable ``item`` for each loop. This means the inner, nested loop will overwrite the value of ``item`` from the outer loop. You can specify the name of the variable for each loop using ``loop_var`` with ``loop_control``::" +#: ../../rst/user_guide/playbooks_loops.rst:402 +msgid "You can nest two looping tasks using ``include_tasks``. However, by default Ansible sets the loop variable ``item`` for each loop. This means the inner, nested loop will overwrite the value of ``item`` from the outer loop. You can specify the name of the variable for each loop using ``loop_var`` with ``loop_control``." msgstr "``include_tasks`` を使用ã™ã‚‹ã¨ã€2 ã¤ã®ãƒ«ãƒ¼ãƒ—タスクを入れåã«ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãŸã ã—ã€Ansible ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã¯ã€ãƒ«ãƒ¼ãƒ—ã”ã¨ã«ãƒ«ãƒ¼ãƒ—変数 ``item`` ãŒè¨å®šã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ã€å…¥ã‚Œåã«ãªã£ãŸå†…å´ã®ãƒ«ãƒ¼ãƒ—ãŒã€å¤–å´ã®ãƒ«ãƒ¼ãƒ—ã® ``item`` ã®å€¤ã‚’上書ãã™ã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚``loop_var`` 㨠``loop_control`` を使用ã—ã¦ã€å„ループã®å¤‰æ•°åを指定ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:385 +#: ../../rst/user_guide/playbooks_loops.rst:425 msgid "If Ansible detects that the current loop is using a variable which has already been defined, it will raise an error to fail the task." msgstr "定義ã•ã‚Œã¦ã„る変数をç¾åœ¨ã®ãƒ«ãƒ¼ãƒ—ãŒä½¿ç”¨ã—ã¦ã„ã‚‹ã“ã¨ã‚’ Ansible ãŒæ¤œå‡ºã™ã‚‹ã¨ã€ã‚¿ã‚¹ã‚¯ãŒå¤±æ•—ã™ã‚‹ãŸã‚ã«ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:388 +#: ../../rst/user_guide/playbooks_loops.rst:428 msgid "Extended loop variables" msgstr "拡張ループ変数" -#: ../../rst/user_guide/playbooks_loops.rst:391 +#: ../../rst/user_guide/playbooks_loops.rst:431 msgid "As of Ansible 2.8 you can get extended loop information using the ``extended`` option to loop control. This option will expose the following information." msgstr "Ansible 2.8 ã§ã¯ã€ãƒ«ãƒ¼ãƒ—制御㫠``extended`` オプションを使用ã™ã‚‹ã“ã¨ã§ã€æ‹¡å¼µã•ã‚ŒãŸãƒ«ãƒ¼ãƒ—æƒ…å ±ã‚’å¾—ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã®ã‚ªãƒ—ションã¯ã€ä»¥ä¸‹ã®æƒ…å ±ã‚’å…¬é–‹ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:394 +#: ../../rst/user_guide/playbooks_loops.rst:434 msgid "Variable" msgstr "変数" -#: ../../rst/user_guide/playbooks_loops.rst:396 +#: ../../rst/user_guide/playbooks_loops.rst:436 msgid "``ansible_loop.allitems``" msgstr "``ansible_loop.allitems``" -#: ../../rst/user_guide/playbooks_loops.rst:396 +#: ../../rst/user_guide/playbooks_loops.rst:436 msgid "The list of all items in the loop" msgstr "ループ内ã®ã™ã¹ã¦ã®é …ç›®ã®ãƒªã‚¹ãƒˆ" -#: ../../rst/user_guide/playbooks_loops.rst:397 +#: ../../rst/user_guide/playbooks_loops.rst:437 msgid "``ansible_loop.index``" msgstr "``ansible_loop.index``" -#: ../../rst/user_guide/playbooks_loops.rst:397 +#: ../../rst/user_guide/playbooks_loops.rst:437 msgid "The current iteration of the loop. (1 indexed)" msgstr "ループã®ç¾åœ¨ã®å復 (1 インデックス化)" -#: ../../rst/user_guide/playbooks_loops.rst:398 +#: ../../rst/user_guide/playbooks_loops.rst:438 msgid "``ansible_loop.index0``" msgstr "``ansible_loop.index0``" -#: ../../rst/user_guide/playbooks_loops.rst:398 +#: ../../rst/user_guide/playbooks_loops.rst:438 msgid "The current iteration of the loop. (0 indexed)" msgstr "ループã®ç¾åœ¨ã®å復 (0 インデックス化)" -#: ../../rst/user_guide/playbooks_loops.rst:399 +#: ../../rst/user_guide/playbooks_loops.rst:439 msgid "``ansible_loop.revindex``" msgstr "``ansible_loop.revindex``" -#: ../../rst/user_guide/playbooks_loops.rst:399 +#: ../../rst/user_guide/playbooks_loops.rst:439 msgid "The number of iterations from the end of the loop (1 indexed)" msgstr "ループã®æœ€å¾Œã‹ã‚‰ã®å復回数 (1 インデックス化)" -#: ../../rst/user_guide/playbooks_loops.rst:400 +#: ../../rst/user_guide/playbooks_loops.rst:440 msgid "``ansible_loop.revindex0``" msgstr "``ansible_loop.revindex0``" -#: ../../rst/user_guide/playbooks_loops.rst:400 +#: ../../rst/user_guide/playbooks_loops.rst:440 msgid "The number of iterations from the end of the loop (0 indexed)" msgstr "ループã®æœ€å¾Œã‹ã‚‰ã®å復回数 (0 インデックス化)" -#: ../../rst/user_guide/playbooks_loops.rst:401 +#: ../../rst/user_guide/playbooks_loops.rst:441 msgid "``ansible_loop.first``" msgstr "``ansible_loop.first``" -#: ../../rst/user_guide/playbooks_loops.rst:401 +#: ../../rst/user_guide/playbooks_loops.rst:441 msgid "``True`` if first iteration" msgstr "最åˆã®å復ã®å ´åˆã¯ ``True``" -#: ../../rst/user_guide/playbooks_loops.rst:402 +#: ../../rst/user_guide/playbooks_loops.rst:442 msgid "``ansible_loop.last``" msgstr "``ansible_loop.last``" -#: ../../rst/user_guide/playbooks_loops.rst:402 +#: ../../rst/user_guide/playbooks_loops.rst:442 msgid "``True`` if last iteration" msgstr "最後ã®å復ã®å ´åˆã¯ ``True``" -#: ../../rst/user_guide/playbooks_loops.rst:403 +#: ../../rst/user_guide/playbooks_loops.rst:443 msgid "``ansible_loop.length``" msgstr "``ansible_loop.length``" -#: ../../rst/user_guide/playbooks_loops.rst:403 +#: ../../rst/user_guide/playbooks_loops.rst:443 msgid "The number of items in the loop" msgstr "ループ内ã®é …目数" -#: ../../rst/user_guide/playbooks_loops.rst:404 +#: ../../rst/user_guide/playbooks_loops.rst:444 msgid "``ansible_loop.previtem``" msgstr "``ansible_loop.previtem``" -#: ../../rst/user_guide/playbooks_loops.rst:404 +#: ../../rst/user_guide/playbooks_loops.rst:444 msgid "The item from the previous iteration of the loop. Undefined during the first iteration." msgstr "ループã®å‰ã®å復ã®é …目。最åˆã®å復ã§ã¯æœªå®šç¾©ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:405 +#: ../../rst/user_guide/playbooks_loops.rst:445 msgid "``ansible_loop.nextitem``" msgstr "``ansible_loop.nextitem``" -#: ../../rst/user_guide/playbooks_loops.rst:405 +#: ../../rst/user_guide/playbooks_loops.rst:445 msgid "The item from the following iteration of the loop. Undefined during the last iteration." msgstr "ループã®æ¬¡ã®å復ã®é …目。最åˆã®å復ã§ã¯æœªå®šç¾©ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:413 +#: ../../rst/user_guide/playbooks_loops.rst:453 msgid "When using ``loop_control.extended`` more memory will be utilized on the control node. This is a result of ``ansible_loop.allitems`` containing a reference to the full loop data for every loop. When serializing the results for display in callback plugins within the main ansible process, these references may be dereferenced causing memory usage to increase." msgstr "``loop_control.extended`` を使用ã™ã‚‹ã¨ã€åˆ¶å¾¡ãƒŽãƒ¼ãƒ‰ã§ã‚ˆã‚Šå¤šãã®ãƒ¡ãƒ¢ãƒªãƒ¼ãŒä½¿ç”¨ã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ã€ã™ã¹ã¦ã®ãƒ«ãƒ¼ãƒ—ã®å®Œå…¨ãªãƒ«ãƒ¼ãƒ—データã¸ã®å‚ç…§ãŒå«ã¾ã‚Œã‚‹ ``ansible_loop.allitems`` ã®çµæžœã§ã™ã€‚メインã®Ansibleプãƒã‚»ã‚¹å†…ã®ã‚³ãƒ¼ãƒ«ãƒãƒƒã‚¯ãƒ—ラグインã«è¡¨ç¤ºã™ã‚‹ãŸã‚ã«çµæžœã‚’シリアル化ã™ã‚‹ã¨ã€ã“れらã®å‚ç…§ãŒé€†å‚ç…§ã•ã‚Œã€ãƒ¡ãƒ¢ãƒªãƒ¼ä½¿ç”¨é‡ãŒå¢—åŠ ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:416 +#: ../../rst/user_guide/playbooks_loops.rst:456 msgid "Accessing the name of your loop_var" msgstr "loop_var ã®åå‰ã¸ã®ã‚¢ã‚¯ã‚»ã‚¹" -#: ../../rst/user_guide/playbooks_loops.rst:419 +#: ../../rst/user_guide/playbooks_loops.rst:459 msgid "As of Ansible 2.8 you can get the name of the value provided to ``loop_control.loop_var`` using the ``ansible_loop_var`` variable" msgstr "Ansible 2.8 ã§ã¯ã€``ansible_loop_var`` 変数を使用ã—㦠``loop_control.loop_var`` ã«æä¾›ã•ã‚ŒãŸå€¤ã®åå‰ã‚’å–å¾—ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:421 -msgid "For role authors, writing roles that allow loops, instead of dictating the required ``loop_var`` value, you can gather the value via::" +#: ../../rst/user_guide/playbooks_loops.rst:461 +msgid "For role authors, writing roles that allow loops, instead of dictating the required ``loop_var`` value, you can gather the value via the following" msgstr "ãƒãƒ¼ãƒ«ã®ä½œæˆè€…ã¯ã€å¿…è¦ãª ``loop_var`` 値を指定ã™ã‚‹ä»£ã‚ã‚Šã«ã€ãƒ«ãƒ¼ãƒ—を許å¯ã™ã‚‹ãƒãƒ¼ãƒ«ã‚’作æˆã™ã‚‹ã“ã¨ã§ã€æ¬¡ã®æ–¹æ³•ã§å€¤ã‚’åŽé›†ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_loops.rst:428 +#: ../../rst/user_guide/playbooks_loops.rst:470 msgid "Migrating from with_X to loop" msgstr "with_X ã‹ã‚‰ loop ã¸ã®ç§»è¡Œ" @@ -8199,160 +8196,160 @@ msgid "If you frequently call the same module with the same arguments, it can be msgstr "åŒã˜å¼•æ•°ã§åŒã˜ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’é »ç¹ã«å‘¼ã³å‡ºã™å ´åˆã¯ã€``module_defaults`` ã‚ーワードを使用ã—ã¦ã€ãã®ç‰¹å®šã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå¼•æ•°ã‚’定義ã™ã‚‹ã¨ä¾¿åˆ©ã§ã™ã€‚" #: ../../rst/user_guide/playbooks_module_defaults.rst:8 -msgid "Here is a basic example::" +msgid "Here is a basic example:" msgstr "以下ã«åŸºæœ¬çš„ãªä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_module_defaults.rst:32 -msgid "The ``module_defaults`` keyword can be used at the play, block, and task level. Any module arguments explicitly specified in a task will override any established default for that module argument::" +#: ../../rst/user_guide/playbooks_module_defaults.rst:34 +msgid "The ``module_defaults`` keyword can be used at the play, block, and task level. Any module arguments explicitly specified in a task will override any established default for that module argument." msgstr "``module_defaults`` ã‚ーワードã¯ã€ãƒ—レイã€ãƒ–ãƒãƒƒã‚¯ã€ãŠã‚ˆã³ã‚¿ã‚¹ã‚¯ãƒ¬ãƒ™ãƒ«ã§ä½¿ç”¨ã§ãã¾ã™ã€‚タスクã§æ˜Žç¤ºçš„ã«æŒ‡å®šã•ã‚ŒãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«å¼•æ•°ã¯ã€ãã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«å¼•æ•°ã«å¯¾ã—ã¦ç¢ºç«‹ã•ã‚ŒãŸãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã‚’上書ãã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_module_defaults.rst:42 -msgid "You can remove any previously established defaults for a module by specifying an empty dict::" +#: ../../rst/user_guide/playbooks_module_defaults.rst:46 +msgid "You can remove any previously established defaults for a module by specifying an empty dict." msgstr "空ã®ãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼ã‚’指定ã™ã‚‹ã“ã¨ã§ã€ãã‚Œã¾ã§ã«è¨å®šã•ã‚ŒãŸãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã‚’削除ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_module_defaults.rst:52 +#: ../../rst/user_guide/playbooks_module_defaults.rst:58 msgid "Any module defaults set at the play level (and block/task level when using ``include_role`` or ``import_role``) will apply to any roles used, which may cause unexpected behavior in the role." msgstr "プレイレベルã§è¨å®šã•ã‚Œã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆ (``include_role`` ã¾ãŸã¯ ``import_role`` を使用ã™ã‚‹éš›ã®ãƒ–ãƒãƒƒã‚¯ã¾ãŸã¯ã‚¿ã‚¹ã‚¯ã®ãƒ¬ãƒ™ãƒ«) ã¯ã€ä½¿ç”¨ã•ã‚Œã‚‹ãƒãƒ¼ãƒ«ã«é©ç”¨ã•ã‚Œã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ãƒãƒ¼ãƒ«ã§äºˆæœŸã—ãªã„動作ãŒç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_module_defaults.rst:54 +#: ../../rst/user_guide/playbooks_module_defaults.rst:60 msgid "Here are some more realistic use cases for this feature." msgstr "ã“ã®æ©Ÿèƒ½ã®ã‚ˆã‚Šå®Ÿç”¨çš„ãªãƒ¦ãƒ¼ã‚¹ã‚±ãƒ¼ã‚¹ã‚’以下ã«ç¤ºã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_module_defaults.rst:56 -msgid "Interacting with an API that requires auth::" +#: ../../rst/user_guide/playbooks_module_defaults.rst:62 +msgid "Interacting with an API that requires auth." msgstr "èªè¨¼ã‚’ã‚’å¿…è¦ã¨ã™ã‚‹ API ã¨ã®å¯¾è©±:" -#: ../../rst/user_guide/playbooks_module_defaults.rst:77 -msgid "Setting a default AWS region for specific EC2-related modules::" +#: ../../rst/user_guide/playbooks_module_defaults.rst:85 +msgid "Setting a default AWS region for specific EC2-related modules." msgstr "特定㮠EC2 関連ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã® AWS リージョンをè¨å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_module_defaults.rst:93 +#: ../../rst/user_guide/playbooks_module_defaults.rst:103 msgid "Module defaults groups" msgstr "モジュールã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã‚°ãƒ«ãƒ¼ãƒ—" -#: ../../rst/user_guide/playbooks_module_defaults.rst:97 +#: ../../rst/user_guide/playbooks_module_defaults.rst:107 msgid "Ansible 2.7 adds a preview-status feature to group together modules that share common sets of parameters. This makes it easier to author playbooks making heavy use of API-based modules such as cloud modules." msgstr "Ansible 2.7 ã§ã¯ã€å…±é€šã®ãƒ‘ラメーターセットをæŒã¤ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’ã¾ã¨ã‚ã¦è¡¨ç¤ºã™ã‚‹ãƒ—レビューステータス機能ãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ã‚¯ãƒ©ã‚¦ãƒ‰ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãªã©ã® API ベースã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’多用ã™ã‚‹ Playbook ã®ä½œæˆãŒå®¹æ˜“ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_module_defaults.rst:100 +#: ../../rst/user_guide/playbooks_module_defaults.rst:110 msgid "Group" msgstr "グループ" -#: ../../rst/user_guide/playbooks_module_defaults.rst:100 +#: ../../rst/user_guide/playbooks_module_defaults.rst:110 msgid "Purpose" msgstr "目的" -#: ../../rst/user_guide/playbooks_module_defaults.rst:100 +#: ../../rst/user_guide/playbooks_module_defaults.rst:110 msgid "Ansible Version" msgstr "Ansible ãƒãƒ¼ã‚¸ãƒ§ãƒ³" -#: ../../rst/user_guide/playbooks_module_defaults.rst:102 +#: ../../rst/user_guide/playbooks_module_defaults.rst:112 msgid "aws" msgstr "aws" -#: ../../rst/user_guide/playbooks_module_defaults.rst:102 +#: ../../rst/user_guide/playbooks_module_defaults.rst:112 msgid "Amazon Web Services" msgstr "Amazon Web Services" -#: ../../rst/user_guide/playbooks_module_defaults.rst:102 -#: ../../rst/user_guide/playbooks_module_defaults.rst:104 -#: ../../rst/user_guide/playbooks_module_defaults.rst:106 +#: ../../rst/user_guide/playbooks_module_defaults.rst:112 +#: ../../rst/user_guide/playbooks_module_defaults.rst:114 +#: ../../rst/user_guide/playbooks_module_defaults.rst:116 msgid "2.7" msgstr "2.7" -#: ../../rst/user_guide/playbooks_module_defaults.rst:104 +#: ../../rst/user_guide/playbooks_module_defaults.rst:114 msgid "azure" msgstr "azure" -#: ../../rst/user_guide/playbooks_module_defaults.rst:104 +#: ../../rst/user_guide/playbooks_module_defaults.rst:114 msgid "Azure" msgstr "Azure" -#: ../../rst/user_guide/playbooks_module_defaults.rst:106 +#: ../../rst/user_guide/playbooks_module_defaults.rst:116 msgid "gcp" msgstr "gcp" -#: ../../rst/user_guide/playbooks_module_defaults.rst:106 +#: ../../rst/user_guide/playbooks_module_defaults.rst:116 msgid "Google Cloud Platform" msgstr "Google Cloud Platform" -#: ../../rst/user_guide/playbooks_module_defaults.rst:108 +#: ../../rst/user_guide/playbooks_module_defaults.rst:118 msgid "k8s" msgstr "k8s" -#: ../../rst/user_guide/playbooks_module_defaults.rst:108 +#: ../../rst/user_guide/playbooks_module_defaults.rst:118 msgid "Kubernetes" msgstr "Kubernetes" -#: ../../rst/user_guide/playbooks_module_defaults.rst:108 -#: ../../rst/user_guide/playbooks_module_defaults.rst:110 +#: ../../rst/user_guide/playbooks_module_defaults.rst:118 +#: ../../rst/user_guide/playbooks_module_defaults.rst:120 msgid "2.8" msgstr "2.8" -#: ../../rst/user_guide/playbooks_module_defaults.rst:110 +#: ../../rst/user_guide/playbooks_module_defaults.rst:120 msgid "os" msgstr "os" -#: ../../rst/user_guide/playbooks_module_defaults.rst:110 +#: ../../rst/user_guide/playbooks_module_defaults.rst:120 msgid "OpenStack" msgstr "OpenStack" -#: ../../rst/user_guide/playbooks_module_defaults.rst:112 +#: ../../rst/user_guide/playbooks_module_defaults.rst:122 msgid "acme" msgstr "acme" -#: ../../rst/user_guide/playbooks_module_defaults.rst:112 +#: ../../rst/user_guide/playbooks_module_defaults.rst:122 msgid "ACME" msgstr "ACME" -#: ../../rst/user_guide/playbooks_module_defaults.rst:112 -#: ../../rst/user_guide/playbooks_module_defaults.rst:114 -#: ../../rst/user_guide/playbooks_module_defaults.rst:116 -#: ../../rst/user_guide/playbooks_module_defaults.rst:118 +#: ../../rst/user_guide/playbooks_module_defaults.rst:122 +#: ../../rst/user_guide/playbooks_module_defaults.rst:124 +#: ../../rst/user_guide/playbooks_module_defaults.rst:126 +#: ../../rst/user_guide/playbooks_module_defaults.rst:128 msgid "2.10" msgstr "2.10" -#: ../../rst/user_guide/playbooks_module_defaults.rst:114 +#: ../../rst/user_guide/playbooks_module_defaults.rst:124 msgid "docker*" msgstr "docker*" -#: ../../rst/user_guide/playbooks_module_defaults.rst:114 +#: ../../rst/user_guide/playbooks_module_defaults.rst:124 msgid "Docker" msgstr "Docker" -#: ../../rst/user_guide/playbooks_module_defaults.rst:116 +#: ../../rst/user_guide/playbooks_module_defaults.rst:126 msgid "ovirt" msgstr "ovirt" -#: ../../rst/user_guide/playbooks_module_defaults.rst:116 +#: ../../rst/user_guide/playbooks_module_defaults.rst:126 msgid "oVirt" msgstr "oVirt" -#: ../../rst/user_guide/playbooks_module_defaults.rst:118 +#: ../../rst/user_guide/playbooks_module_defaults.rst:128 msgid "vmware" msgstr "vmware" -#: ../../rst/user_guide/playbooks_module_defaults.rst:118 +#: ../../rst/user_guide/playbooks_module_defaults.rst:128 msgid "VMware" msgstr "VMware" -#: ../../rst/user_guide/playbooks_module_defaults.rst:121 +#: ../../rst/user_guide/playbooks_module_defaults.rst:131 msgid "The `docker_stack <docker_stack_module>`_ module is not included in the ``docker`` defaults group." msgstr "`docker_stack <docker_stack_module>`_ モジュールã¯ã€``docker`` デフォルトグループã«ã¯å«ã¾ã‚Œã¾ã›ã‚“。" -#: ../../rst/user_guide/playbooks_module_defaults.rst:123 +#: ../../rst/user_guide/playbooks_module_defaults.rst:133 msgid "Use the groups with ``module_defaults`` by prefixing the group name with ``group/`` - for example ``group/aws``." msgstr "グループåã®å‰ã« ``group/`` ã‚’è¿½åŠ ã—㦠(例: ``group/aws``)ã€``module_defaults`` ã§ã‚°ãƒ«ãƒ¼ãƒ—を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_module_defaults.rst:125 +#: ../../rst/user_guide/playbooks_module_defaults.rst:135 msgid "In a playbook, you can set module defaults for whole groups of modules, such as setting a common AWS region." msgstr "Playbook ã§ã¯ã€ä¸€èˆ¬çš„㪠AWS リージョンã®è¨å®šãªã©ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ã‚°ãƒ«ãƒ¼ãƒ—全体ã«ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã‚’è¨å®šã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_module_defaults.rst:145 +#: ../../rst/user_guide/playbooks_module_defaults.rst:155 msgid "In ansible-core 2.12, collections can define their own groups in the ``meta/runtime.yml`` file. ``module_defaults`` does not take the ``collections`` keyword into account, so the fully qualified group name must be used for new groups in ``module_defaults``." msgstr "ansible-core 2.12 ã§ã¯ã€ã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ã¯ ``meta/runtime.yml`` ファイルã§ç‹¬è‡ªã®ã‚°ãƒ«ãƒ¼ãƒ—を定義ã§ãã¾ã™ã€‚``module_defaults`` 㯠``collections`` ã‚ーワードを考慮ã«å…¥ã‚Œãªã„ãŸã‚ã€å®Œå…¨ä¿®é£¾ã‚°ãƒ«ãƒ¼ãƒ—åã‚’ ``module_defaults`` ã®æ–°è¦ã‚°ãƒ«ãƒ¼ãƒ—ã«ä½¿ç”¨ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_module_defaults.rst:147 +#: ../../rst/user_guide/playbooks_module_defaults.rst:157 msgid "Here is an example ``runtime.yml`` file for a collection and a sample playbook using the group." msgstr "以下ã¯ã€ã‚°ãƒ«ãƒ¼ãƒ—を使用ã—ãŸã‚³ãƒ¬ã‚¯ã‚·ãƒ§ãƒ³ãŠã‚ˆã³ã‚µãƒ³ãƒ—ル Playbook ã® ``runtime.yml`` ファイルã®ä¾‹ã§ã™ã€‚" @@ -8365,119 +8362,119 @@ msgid "If you want your playbook to prompt the user for certain input, add a 'va msgstr "Playbook ã§ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«ç‰¹å®šã®å…¥åŠ›ã‚’促ã—ãŸã„å ´åˆã¯ã€ã€Œvars_promptã€ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã‚’è¿½åŠ ã—ã¾ã™ã€‚ユーザーã«å¤‰æ•°ã®å…¥åŠ›ã‚’促ã™ã“ã¨ã§ã€ãƒ‘スワードã®ã‚ˆã†ãªæ©Ÿå¯†ãƒ‡ãƒ¼ã‚¿ã®è¨˜éŒ²ã‚’回é¿ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã‚»ã‚ュリティーã®ã»ã‹ã«ã€ãƒ—ãƒãƒ³ãƒ—トã¯æŸ”軟性をサãƒãƒ¼ãƒˆã—ã¾ã™ã€‚ãŸã¨ãˆã°ã€1 ã¤ã® Playbook を複数ã®ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ãƒªãƒªãƒ¼ã‚¹ã§ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€ç‰¹å®šã®ãƒªãƒªãƒ¼ã‚¹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®å…¥åŠ›ã‚’促ã™ã“ã¨ãŒã§ãã¾ã™ã€‚" #: ../../rst/user_guide/playbooks_prompts.rst:12 -msgid "Here is a most basic example::" +msgid "Here is a most basic example:" msgstr "以下ã¯æœ€ã‚‚基本的ãªä¾‹ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_prompts.rst:31 +#: ../../rst/user_guide/playbooks_prompts.rst:33 msgid "The user input is hidden by default but it can be made visible by setting ``private: no``." msgstr "ユーザー入力ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã¯è¡¨ç¤ºã•ã‚Œã¾ã›ã‚“ãŒã€``private: no`` ã‚’è¨å®šã™ã‚‹ã“ã¨ã§è¡¨ç¤ºã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_prompts.rst:34 +#: ../../rst/user_guide/playbooks_prompts.rst:36 msgid "Prompts for individual ``vars_prompt`` variables will be skipped for any variable that is already defined through the command line ``--extra-vars`` option, or when running from a non-interactive session (such as cron or Ansible AWX). See :ref:`passing_variables_on_the_command_line`." msgstr "個別㮠``vars_prompt`` 変数ã®å…¥åŠ›ã‚’求ã‚るプãƒãƒ³ãƒ—トã¯ã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã® ``--extra-vars`` オプションã§ã™ã§ã«å®šç¾©ã•ã‚Œã¦ã„る変数やã€éžå¯¾è©±çš„ãªã‚»ãƒƒã‚·ãƒ§ãƒ³ (cron ã‚„ Ansible AWX ãªã©) ã‹ã‚‰å®Ÿè¡Œã™ã‚‹å ´åˆã«çœç•¥ã•ã‚Œã¾ã™ã€‚「:ref:`passing_variables_on_the_command_line`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_prompts.rst:36 -msgid "If you have a variable that changes infrequently, you can provide a default value that can be overridden::" +#: ../../rst/user_guide/playbooks_prompts.rst:38 +msgid "If you have a variable that changes infrequently, you can provide a default value that can be overridden." msgstr "ã¾ã‚Œã«å¤‰æ›´ã™ã‚‹å¤‰æ•°ãŒã‚ã‚‹å ´åˆã¯ã€ä¸Šæ›¸ãã§ãるデフォルト値を指定ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_prompts.rst:45 +#: ../../rst/user_guide/playbooks_prompts.rst:49 msgid "Encrypting values supplied by ``vars_prompt``" msgstr "``vars_prompt`` ã«ã‚ˆã‚Šæä¾›ã•ã‚Œã‚‹å€¤ã®æš—å·åŒ–" -#: ../../rst/user_guide/playbooks_prompts.rst:47 -msgid "You can encrypt the entered value so you can use it, for instance, with the user module to define a password::" +#: ../../rst/user_guide/playbooks_prompts.rst:51 +msgid "You can encrypt the entered value so you can use it, for instance, with the user module to define a password:" msgstr "入力値を暗å·åŒ–ã—ã¦ã€ãŸã¨ãˆã°ãƒ¦ãƒ¼ã‚¶ãƒ¼ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦ãƒ‘スワードを定義ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_prompts.rst:58 +#: ../../rst/user_guide/playbooks_prompts.rst:64 msgid "If you have `Passlib <https://passlib.readthedocs.io/en/stable/>`_ installed, you can use any crypt scheme the library supports:" msgstr "`Passlib <https://passlib.readthedocs.io/en/stable/>`_ をインストールã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒ©ã‚¤ãƒ–ラリーãŒã‚µãƒãƒ¼ãƒˆã™ã‚‹ä»»æ„ã® crypt スã‚ームを使用ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_prompts.rst:60 +#: ../../rst/user_guide/playbooks_prompts.rst:66 msgid "*des_crypt* - DES Crypt" msgstr "*des_crypt* - DES Crypt" -#: ../../rst/user_guide/playbooks_prompts.rst:61 +#: ../../rst/user_guide/playbooks_prompts.rst:67 msgid "*bsdi_crypt* - BSDi Crypt" msgstr "*bsdi_crypt* - BSDi Crypt" -#: ../../rst/user_guide/playbooks_prompts.rst:62 +#: ../../rst/user_guide/playbooks_prompts.rst:68 msgid "*bigcrypt* - BigCrypt" msgstr "*bigcrypt* - BigCrypt" -#: ../../rst/user_guide/playbooks_prompts.rst:63 +#: ../../rst/user_guide/playbooks_prompts.rst:69 msgid "*crypt16* - Crypt16" msgstr "*crypt16* - Crypt16" -#: ../../rst/user_guide/playbooks_prompts.rst:64 -#: ../../rst/user_guide/playbooks_prompts.rst:87 +#: ../../rst/user_guide/playbooks_prompts.rst:70 +#: ../../rst/user_guide/playbooks_prompts.rst:93 msgid "*md5_crypt* - MD5 Crypt" msgstr "*md5_crypt* - MD5 Crypt" -#: ../../rst/user_guide/playbooks_prompts.rst:65 -#: ../../rst/user_guide/playbooks_prompts.rst:86 +#: ../../rst/user_guide/playbooks_prompts.rst:71 +#: ../../rst/user_guide/playbooks_prompts.rst:92 msgid "*bcrypt* - BCrypt" msgstr "*bcrypt* - BCrypt" -#: ../../rst/user_guide/playbooks_prompts.rst:66 +#: ../../rst/user_guide/playbooks_prompts.rst:72 msgid "*sha1_crypt* - SHA-1 Crypt" msgstr "*sha1_crypt* - SHA-1 Crypt" -#: ../../rst/user_guide/playbooks_prompts.rst:67 +#: ../../rst/user_guide/playbooks_prompts.rst:73 msgid "*sun_md5_crypt* - Sun MD5 Crypt" msgstr "*sun_md5_crypt* - Sun MD5 Crypt" -#: ../../rst/user_guide/playbooks_prompts.rst:68 -#: ../../rst/user_guide/playbooks_prompts.rst:88 +#: ../../rst/user_guide/playbooks_prompts.rst:74 +#: ../../rst/user_guide/playbooks_prompts.rst:94 msgid "*sha256_crypt* - SHA-256 Crypt" msgstr "*sha256_crypt* - SHA-256 Crypt" -#: ../../rst/user_guide/playbooks_prompts.rst:69 -#: ../../rst/user_guide/playbooks_prompts.rst:89 +#: ../../rst/user_guide/playbooks_prompts.rst:75 +#: ../../rst/user_guide/playbooks_prompts.rst:95 msgid "*sha512_crypt* - SHA-512 Crypt" msgstr "*sha512_crypt* - SHA-512 Crypt" -#: ../../rst/user_guide/playbooks_prompts.rst:70 +#: ../../rst/user_guide/playbooks_prompts.rst:76 msgid "*apr_md5_crypt* - Apache's MD5-Crypt variant" msgstr "*apr_md5_crypt* - Apache's MD5-Crypt variant" -#: ../../rst/user_guide/playbooks_prompts.rst:71 +#: ../../rst/user_guide/playbooks_prompts.rst:77 msgid "*phpass* - PHPass' Portable Hash" msgstr "*phpass* - PHPass' Portable Hash" -#: ../../rst/user_guide/playbooks_prompts.rst:72 +#: ../../rst/user_guide/playbooks_prompts.rst:78 msgid "*pbkdf2_digest* - Generic PBKDF2 Hashes" msgstr "*pbkdf2_digest* - Generic PBKDF2 Hashes" -#: ../../rst/user_guide/playbooks_prompts.rst:73 +#: ../../rst/user_guide/playbooks_prompts.rst:79 msgid "*cta_pbkdf2_sha1* - Cryptacular's PBKDF2 hash" msgstr "*cta_pbkdf2_sha1* - Cryptacular's PBKDF2 hash" -#: ../../rst/user_guide/playbooks_prompts.rst:74 +#: ../../rst/user_guide/playbooks_prompts.rst:80 msgid "*dlitz_pbkdf2_sha1* - Dwayne Litzenberger's PBKDF2 hash" msgstr "*dlitz_pbkdf2_sha1* - Dwayne Litzenberger's PBKDF2 hash" -#: ../../rst/user_guide/playbooks_prompts.rst:75 +#: ../../rst/user_guide/playbooks_prompts.rst:81 msgid "*scram* - SCRAM Hash" msgstr "*scram* - SCRAM Hash" -#: ../../rst/user_guide/playbooks_prompts.rst:76 +#: ../../rst/user_guide/playbooks_prompts.rst:82 msgid "*bsd_nthash* - FreeBSD's MCF-compatible nthash encoding" msgstr "*bsd_nthash* - FreeBSD's MCF 互æ›ã® nthash エンコーディング" -#: ../../rst/user_guide/playbooks_prompts.rst:78 +#: ../../rst/user_guide/playbooks_prompts.rst:84 msgid "The only parameters accepted are 'salt' or 'salt_size'. You can use your own salt by defining 'salt', or have one generated automatically using 'salt_size'. By default Ansible generates a salt of size 8." msgstr "使用ã§ãるパラメーターã¯ã€Œsaltã€ã¾ãŸã¯ã€Œsalt_sizeã€ã®ã¿ã§ã™ã€‚「saltã€ã‚’定義ã—ã¦ç‹¬è‡ªã®ã‚½ãƒ«ãƒˆã‚’使用ã™ã‚‹ã“ã¨ã‚‚ã€ã€Œsalt_sizeã€ã‚’使用ã—ã¦è‡ªå‹•çš„ã«ç”Ÿæˆã•ã‚Œã‚‹ã‚½ãƒ«ãƒˆã‚’使用ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚デフォルトã§ã¯ã€Ansible ã¯ã‚µã‚¤ã‚º 8 ã® salt を生æˆã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_prompts.rst:84 +#: ../../rst/user_guide/playbooks_prompts.rst:90 msgid "If you do not have Passlib installed, Ansible uses the `crypt <https://docs.python.org/3/library/crypt.html>`_ library as a fallback. Ansible supports at most four crypt schemes, depending on your platform at most the following crypt schemes are supported:" msgstr "Passlib ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„å ´åˆã€Ansible ã¯ãƒ•ã‚©ãƒ¼ãƒ«ãƒãƒƒã‚¯ã¨ã—㦠`crypt <https://docs.python.org/3/library/crypt.html>`_ ライブラリーを使用ã—ã¾ã™ã€‚Ansible ã¯æœ€å¤§ã§ 4 ã¤ã®æš—å·æ–¹å¼ã‚’サãƒãƒ¼ãƒˆã—ã¦ã„ã¾ã™ãŒã€ãƒ—ラットフォームã«ã‚ˆã£ã¦ã¯æœ€å¤§ã§ä»¥ä¸‹ã®æš—å·æ–¹å¼ã‚’サãƒãƒ¼ãƒˆã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_prompts.rst:95 +#: ../../rst/user_guide/playbooks_prompts.rst:101 msgid "Allowing special characters in ``vars_prompt`` values" msgstr "``vars_prompt`` 値ã§ã®ç‰¹æ®Šæ–‡å—ã®è¨±å¯" -#: ../../rst/user_guide/playbooks_prompts.rst:97 -msgid "Some special characters, such as ``{`` and ``%`` can create templating errors. If you need to accept special characters, use the ``unsafe`` option::" +#: ../../rst/user_guide/playbooks_prompts.rst:103 +msgid "Some special characters, such as ``{`` and ``%`` can create templating errors. If you need to accept special characters, use the ``unsafe`` option:" msgstr "``{`` ã‚„ ``%`` ãªã©ã®ç‰¹æ®Šæ–‡å—ã¯ã€ãƒ†ãƒ³ãƒ—レートエラーã®ä½œæˆãŒå¯èƒ½ã§ã™ã€‚特殊文å—ã‚’å—ã‘入れる必è¦ãŒã‚ã‚‹å ´åˆã¯ã€``unsafe`` オプションを使用ã—ã¾ã™ã€‚" #: ../../rst/user_guide/playbooks_python_version.rst:5 @@ -8501,22 +8498,22 @@ msgid "In Python2, the :meth:`dict.keys`, :meth:`dict.values`, and :meth:`dict.i msgstr "Python2 ã§ã¯ã€:meth:`dict.keys`ã€:meth:`dict.values`ã€ãŠã‚ˆã³ :meth:`dict.items` メソッドã¯ãƒªã‚¹ãƒˆã‚’è¿”ã—ã¾ã™ã€‚Jinja2 ã¯ã€Ansible ãŒãƒªã‚¹ãƒˆã«æˆ»ã£ã¦ããŸæ–‡å—列表ç¾ã§ Ansible ã«è¿”ã—ã¾ã™ã€‚" #: ../../rst/user_guide/playbooks_python_version.rst:22 -msgid "In Python3, those methods return a :ref:`dictionary view <python3:dict-views>` object. The string representation that Jinja2 returns for dictionary views cannot be parsed back into a list by Ansible. It is, however, easy to make this portable by using the :func:`list <jinja2:jinja-filters.list>` filter whenever using :meth:`dict.keys`, :meth:`dict.values`, or :meth:`dict.items`::" -msgstr "Python3 ã§ã¯ã€ã“れらã®ãƒ¡ã‚½ãƒƒãƒ‰ã¯ :ref:`dictionary view <python3:dict-views>` オブジェクトを返ã—ã¾ã™ã€‚Jinja2 ãŒãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼ãƒ“ューã«è¿”ã™æ–‡å—列表ç¾ã¯ã€Ansible ã§ã¯ãƒªã‚¹ãƒˆã«è§£æžã—ç›´ã™ã“ã¨ãŒã§ãã¾ã›ã‚“。ã—ã‹ã—ã€:meth:`dict.keys`ã€:meth:`dict.values`ã€ã¾ãŸã¯ :meth:`dict.items` を使用ã™ã‚‹éš›ã«ã¯å¿…ãš :func:`list <jinja2:jinja-filters.list>` フィルターを使用ã™ã‚‹ã“ã¨ã§ã€ç°¡å˜ã«ç§»æ¤ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" +msgid "In Python3, those methods return a :ref:`dictionary view <python3:dict-views>` object. The string representation that Jinja2 returns for dictionary views cannot be parsed back into a list by Ansible. It is, however, easy to make this portable by using the :func:`list <jinja2:jinja-filters.list>` filter whenever using :meth:`dict.keys`, :meth:`dict.values`, or :meth:`dict.items`." +msgstr "Python3 ã§ã¯ã€ã“れらã®ãƒ¡ã‚½ãƒƒãƒ‰ã¯ :ref:`ディクショナリービュー <python3:dict-views>` オブジェクトを返ã—ã¾ã™ã€‚Jinja2 ãŒãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼ãƒ“ューã«è¿”ã™æ–‡å—列表ç¾ã¯ã€Ansible ã§ã¯ãƒªã‚¹ãƒˆã«è§£æžã—ç›´ã™ã“ã¨ãŒã§ãã¾ã›ã‚“。ã—ã‹ã—ã€:meth:`dict.keys`ã€:meth:`dict.values`ã€ã¾ãŸã¯ :meth:`dict.items` を使用ã™ã‚‹éš›ã«ã¯å¿…ãš :func:`list <jinja2:jinja-filters.list>` フィルターを使用ã™ã‚‹ã“ã¨ã§ã€ç°¡å˜ã«ç§»æ¤ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_python_version.rst:43 +#: ../../rst/user_guide/playbooks_python_version.rst:45 msgid "dict.iteritems()" msgstr "dict.iteritems()" -#: ../../rst/user_guide/playbooks_python_version.rst:45 +#: ../../rst/user_guide/playbooks_python_version.rst:47 msgid "Python2 dictionaries have :meth:`~dict.iterkeys`, :meth:`~dict.itervalues`, and :meth:`~dict.iteritems` methods." msgstr "Python2 ディクショナリーã«ã¯ã€:meth:`~dict.iterkeys` メソッドã€:meth:`~dict.itervalues` メソッドã€ãŠã‚ˆã³ :meth:`~dict.iteritems` メソッドãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_python_version.rst:47 -msgid "Python3 dictionaries do not have these methods. Use :meth:`dict.keys`, :meth:`dict.values`, and :meth:`dict.items` to make your playbooks and templates compatible with both Python2 and Python3::" +#: ../../rst/user_guide/playbooks_python_version.rst:49 +msgid "Python3 dictionaries do not have these methods. Use :meth:`dict.keys`, :meth:`dict.values`, and :meth:`dict.items` to make your playbooks and templates compatible with both Python2 and Python3." msgstr "Python3 ディクショナリーã«ã¯ã“れらã®ãƒ¡ã‚½ãƒƒãƒ‰ãŒã‚ã‚Šã¾ã›ã‚“。:meth:`dict.keys`ã€:meth:`dict.values`ã€ãŠã‚ˆã³ :meth:`dict.items` を使用ã—ã¦ã€Playbook ãŠã‚ˆã³ãƒ†ãƒ³ãƒ—レートを Python2 㨠Python3 ã®ä¸¡æ–¹ã«å¯¾å¿œã•ã›ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_python_version.rst:62 +#: ../../rst/user_guide/playbooks_python_version.rst:66 msgid "The :ref:`pb-py-compat-dict-views` entry for information on why the :func:`list filter <jinja2:jinja-filters.list>` is necessary here." msgstr "ã“ã“㧠:func:`list filter <jinja2:jinja-filters.list>` ãŒå¿…è¦ãªç†ç”±ã¯ã€:ref:`pb-py-compat-dict-views` エントリーをå‚ç…§ã—ã¦ãã ã•ã„。" @@ -9524,34 +9521,34 @@ msgid "start-at-task" msgstr "start-at-task" #: ../../rst/user_guide/playbooks_startnstep.rst:14 -msgid "To start executing your playbook at a particular task (usually the task that failed on the previous run), use the ``--start-at-task`` option::" +msgid "To start executing your playbook at a particular task (usually the task that failed on the previous run), use the ``--start-at-task`` option." msgstr "特定ã®ã‚¿ã‚¹ã‚¯ (通常ã¯ç›´å‰ã®å®Ÿè¡Œã§å¤±æ•—ã—ãŸã‚¿ã‚¹ã‚¯) 㧠Playbook ã®å®Ÿè¡Œã‚’開始ã™ã‚‹ã«ã¯ã€``--start-at-task`` オプションを使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_startnstep.rst:18 +#: ../../rst/user_guide/playbooks_startnstep.rst:20 msgid "In this example, Ansible starts executing your playbook at a task named \"install packages\". This feature does not work with tasks inside dynamically re-used roles or tasks (``include_*``), see :ref:`dynamic_vs_static`." msgstr "ã“ã®ä¾‹ã§ã¯ã€Ansible ã¯ã€Œinstall packagesã€ã¨ã„ã†åå‰ã®ã‚¿ã‚¹ã‚¯ã§ Playbook ã®å®Ÿè¡Œã‚’開始ã—ã¾ã™ã€‚ã“ã®æ©Ÿèƒ½ã¯ã€å‹•çš„ã«å†åˆ©ç”¨ã•ã‚Œã‚‹ãƒãƒ¼ãƒ«ã‚„タスク内ã®ã‚¿ã‚¹ã‚¯ (``include_*``) ã§ã¯å‹•ä½œã—ã¾ã›ã‚“。「:ref:`dynamic_vs_static`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_startnstep.rst:23 +#: ../../rst/user_guide/playbooks_startnstep.rst:25 msgid "Step mode" msgstr "step モード" -#: ../../rst/user_guide/playbooks_startnstep.rst:25 -msgid "To execute a playbook interactively, use ``--step``::" +#: ../../rst/user_guide/playbooks_startnstep.rst:27 +msgid "To execute a playbook interactively, use ``--step``." msgstr "Playbook を対話的ã«å®Ÿè¡Œã™ã‚‹ã«ã¯ã€``--step`` を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_startnstep.rst:29 -msgid "With this option, Ansible stops on each task, and asks if it should execute that task. For example, if you have a task called \"configure ssh\", the playbook run will stop and ask::" +#: ../../rst/user_guide/playbooks_startnstep.rst:33 +msgid "With this option, Ansible stops on each task, and asks if it should execute that task. For example, if you have a task called \"configure ssh\", the playbook run will stop and ask." msgstr "ã“ã®ã‚ªãƒ—ションを使用ã™ã‚‹ã¨ã€Ansible ã¯å„タスクã§åœæ¢ã—ã€ãã®ã‚¿ã‚¹ã‚¯ã‚’実行ã™ã¹ãã‹ã©ã†ã‹ã‚’å°‹ãã¾ã™ã€‚ãŸã¨ãˆã°ã€ã€Œconfigure sshã€ã¨ã„ã†åå‰ã®ã‚¿ã‚¹ã‚¯ãŒã‚ã£ãŸå ´åˆã€Playbook ã®å®Ÿè¡Œã¯åœæ¢ã—ã€æ¬¡ã®ã‚ˆã†ã«å°‹ãã¦ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_startnstep.rst:33 +#: ../../rst/user_guide/playbooks_startnstep.rst:39 msgid "Answer \"y\" to execute the task, answer \"n\" to skip the task, and answer \"c\" to exit step mode, executing all remaining tasks without asking." msgstr "「yã€ã¨ç”ãˆã¦ã‚¿ã‚¹ã‚¯ã‚’実行ã—ã€ã€Œnã€ã¨ç”ãˆã¦ã‚¿ã‚¹ã‚¯ã‚’スã‚ップã—ã€ã€Œcã€ã¨å¿œãˆã¦ step モードを終了ã—ã€æ®‹ã‚Šã®ã‚¿ã‚¹ã‚¯ã‚’ã™ã¹ã¦å®Ÿè¡Œã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_startnstep.rst:39 +#: ../../rst/user_guide/playbooks_startnstep.rst:45 msgid ":ref:`playbook_debugger`" msgstr ":ref:`playbook_debugger`" -#: ../../rst/user_guide/playbooks_startnstep.rst:40 +#: ../../rst/user_guide/playbooks_startnstep.rst:46 msgid "Using the Ansible debugger" msgstr "Ansible デãƒãƒƒã‚¬ãƒ¼ã®ä½¿ç”¨" @@ -9568,182 +9565,182 @@ msgid "Selecting a strategy" msgstr "ストラテジーã®é¸æŠž" #: ../../rst/user_guide/playbooks_strategies.rst:13 -msgid "The default behavior described above is the :ref:`linear strategy<linear_strategy>`. Ansible offers other strategies, including the :ref:`debug strategy<debug_strategy>` (see also :ref:`playbook_debugger`) and the :ref:`free strategy<free_strategy>`, which allows each host to run until the end of the play as fast as it can::" -msgstr "上述ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã®å‹•ä½œã¯ :ref:`線形ストラテジー<linear_strategy>` ã§ã™ã€‚Ansible ã«ã¯ã€:ref:`デãƒãƒƒã‚°ã‚¹ãƒˆãƒ©ãƒ†ã‚¸ãƒ¼<debug_strategy>` (:ref:`playbook_debugger` ã‚‚å‚ç…§) ã‚„ :ref:`フリーストラテジー<free_strategy>` ãªã©ã€ä»–ã®ã‚¹ãƒˆãƒ©ãƒ†ã‚¸ãƒ¼ã‚‚用æ„ã•ã‚Œã¦ã„ã¾ã™ã€‚フリーストラテジーã§ã¯ã€å„ホストãŒãƒ—レイãŒçµ‚了ã™ã‚‹ã¾ã§ã§ãã‚‹ã ã‘速ã実行ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" +msgid "The default behavior described above is the :ref:`linear strategy<linear_strategy>`. Ansible offers other strategies, including the :ref:`debug strategy<debug_strategy>` (see also :ref:`playbook_debugger`) and the :ref:`free strategy<free_strategy>`, which allows each host to run until the end of the play as fast as it can:" +msgstr "上述ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã®å‹•ä½œã¯ :ref:`linear strategy<linear_strategy>` ã§ã™ã€‚Ansible ã«ã¯ã€:ref:`debug strategy<debug_strategy>` (:ref:`playbook_debugger` ã‚‚å‚ç…§) ã‚„ :ref:`free strategy<free_strategy>` ãªã©ã€ä»–ã®ã‚¹ãƒˆãƒ©ãƒ†ã‚¸ãƒ¼ã‚‚用æ„ã•ã‚Œã¦ã„ã¾ã™ã€‚フリーストラテジーã§ã¯ã€å„ホストãŒãƒ—レイãŒçµ‚了ã™ã‚‹ã¾ã§ã§ãã‚‹ã ã‘速ã実行ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:20 -msgid "You can select a different strategy for each play as shown above, or set your preferred strategy globally in ``ansible.cfg``, under the ``defaults`` stanza::" +#: ../../rst/user_guide/playbooks_strategies.rst:22 +msgid "You can select a different strategy for each play as shown above, or set your preferred strategy globally in ``ansible.cfg``, under the ``defaults`` stanza:" msgstr "上記ã®ã‚ˆã†ã«å„プレイã«ç•°ãªã‚‹ã‚¹ãƒˆãƒ©ãƒ†ã‚¸ãƒ¼ã‚’é¸æŠžã™ã‚‹ã‹ã€``defaults`` stanza ã® ``ansible.cfg`` ã§å„ªå…ˆã•ã‚Œã‚‹ã‚¹ãƒˆãƒ©ãƒ†ã‚¸ãƒ¼ã‚’ã‚°ãƒãƒ¼ãƒãƒ«ã«è¨å®šã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:25 +#: ../../rst/user_guide/playbooks_strategies.rst:29 msgid "All strategies are implemented as :ref:`strategy plugins<strategy_plugins>`. Please review the documentation for each strategy plugin for details on how it works." msgstr "ã™ã¹ã¦ã®ã‚¹ãƒˆãƒ©ãƒ†ã‚¸ãƒ¼ã¯ :ref:`strategy プラグイン<strategy_plugins>` ã¨ã—ã¦å®Ÿè£…ã•ã‚Œã¾ã™ã€‚ãã®ä»•çµ„ã¿ã®è©³ç´°ã¯ã€å„ strategy プラグインã®ãƒ‰ã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_strategies.rst:28 +#: ../../rst/user_guide/playbooks_strategies.rst:32 msgid "Setting the number of forks" msgstr "フォークã®æ•°ã®è¨å®š" -#: ../../rst/user_guide/playbooks_strategies.rst:29 -msgid "If you have the processing power available and want to use more forks, you can set the number in ``ansible.cfg``::" +#: ../../rst/user_guide/playbooks_strategies.rst:33 +msgid "If you have the processing power available and want to use more forks, you can set the number in ``ansible.cfg``:" msgstr "利用å¯èƒ½ãªå‡¦ç†èƒ½åŠ›ãŒã‚ã‚Šã€ã•ã‚‰ã«å¤šãã®ãƒ•ã‚©ãƒ¼ã‚¯ã‚’使用ã™ã‚‹å ´åˆã¯ã€``ansible.cfg`` ã§æ•°å€¤ã‚’è¨å®šã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:34 +#: ../../rst/user_guide/playbooks_strategies.rst:40 msgid "or pass it on the command line: `ansible-playbook -f 30 my_playbook.yml`." msgstr "ã¾ãŸã¯ã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã§æ¸¡ã—ã¾ã™ (`ansible-playbook -f 30 my_playbook.yml`)。" -#: ../../rst/user_guide/playbooks_strategies.rst:37 +#: ../../rst/user_guide/playbooks_strategies.rst:43 msgid "Using keywords to control execution" msgstr "ã‚ーワードを使用ã—ãŸå®Ÿè¡Œã®åˆ¶å¾¡" -#: ../../rst/user_guide/playbooks_strategies.rst:39 +#: ../../rst/user_guide/playbooks_strategies.rst:45 msgid "In addition to strategies, several :ref:`keywords<playbook_keywords>` also affect play execution. You can set a number, a percentage, or a list of numbers of hosts you want to manage at a time with ``serial``. Ansible completes the play on the specified number or percentage of hosts before starting the next batch of hosts. You can restrict the number of workers allotted to a block or task with ``throttle``. You can control how Ansible selects the next host in a group to execute against with ``order``. You can run a task on a single host with ``run_once``. These keywords are not strategies. They are directives or options applied to a play, block, or task." msgstr "ストラテジーã ã‘ã§ãªãã€ã„ãã¤ã‹ã® :ref:`ã‚ーワード<playbook_keywords>` もプレイã®å®Ÿè¡Œã«å½±éŸ¿ã‚’与ãˆã¾ã™ã€‚``serial`` ã§ã¯ã€ä¸€åº¦ã«ç®¡ç†ã—ãŸã„ホストã®æ•°ã€å‰²åˆã€ã¾ãŸã¯ãƒªã‚¹ãƒˆã‚’è¨å®šã§ãã¾ã™ã€‚Ansible ã¯ã€æŒ‡å®šã—ãŸæ•°ã¾ãŸã¯å‰²åˆã®ãƒ›ã‚¹ãƒˆã§ãƒ—レイを完了ã—ã¦ã‹ã‚‰ã€æ¬¡ã®ãƒ›ã‚¹ãƒˆã®ãƒãƒƒãƒã‚’開始ã—ã¾ã™ã€‚``throttle`` ã§ã€ãƒ–ãƒãƒƒã‚¯ã‚„タスクã«å‰²ã‚Šå½“ã¦ã‚‰ã‚Œã‚‹ãƒ¯ãƒ¼ã‚«ãƒ¼ã®æ•°ã‚’制é™ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚``order`` ã§ã€Ansible ãŒã‚°ãƒ«ãƒ¼ãƒ—内ã®æ¬¡ã®ãƒ›ã‚¹ãƒˆã‚’é¸æŠžã—ã¦å®Ÿè¡Œã™ã‚‹æ–¹æ³•ã‚’制御ã§ãã¾ã™ã€‚``run_once`` を使用ã—ã¦ã€1 ã¤ã®ã‚¿ã‚¹ã‚¯ã‚’ 1 ã¤ã®ãƒ›ã‚¹ãƒˆã§å®Ÿè¡Œã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“れらã®ã‚ーワードã¯ã‚¹ãƒˆãƒ©ãƒ†ã‚¸ãƒ¼ã§ã¯ãªãã€ãƒ—レイã€ãƒ–ãƒãƒƒã‚¯ã€ã¾ãŸã¯ã‚¿ã‚¹ã‚¯ã«é©ç”¨ã•ã‚Œã‚‹ãƒ‡ã‚£ãƒ¬ã‚¯ãƒ†ã‚£ãƒ–やオプションã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:41 +#: ../../rst/user_guide/playbooks_strategies.rst:47 msgid "Other keywords that affect play execution include ``ignore_errors``, ``ignore_unreachable``, and ``any_errors_fatal``. These options are documented in :ref:`playbooks_error_handling`." msgstr "プレイã®å®Ÿè¡Œã«å½±éŸ¿ã™ã‚‹ä»–ã®ã‚ーワードã«ã¯ã€``ignore_errors``ã€``ignore_unreachable``ã€ãŠã‚ˆã³ ``any_errors_fatal`` ãŒå«ã¾ã‚Œã¾ã™ã€‚ã“れらã®ã‚ªãƒ—ションã¯ã€ã€Œ:ref:`playbooks_error_handling`ã€ã«è¨˜è¼‰ã•ã‚Œã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:46 +#: ../../rst/user_guide/playbooks_strategies.rst:52 msgid "Setting the batch size with ``serial``" msgstr "``serial`` を使用ã—ã¦ãƒãƒƒãƒã‚µã‚¤ã‚ºã®è¨å®š" -#: ../../rst/user_guide/playbooks_strategies.rst:48 -msgid "By default, Ansible runs in parallel against all the hosts in the :ref:`pattern <intro_patterns>` you set in the ``hosts:`` field of each play. If you want to manage only a few machines at a time, for example during a rolling update, you can define how many hosts Ansible should manage at a single time using the ``serial`` keyword::" +#: ../../rst/user_guide/playbooks_strategies.rst:54 +msgid "By default, Ansible runs in parallel against all the hosts in the :ref:`pattern <intro_patterns>` you set in the ``hosts:`` field of each play. If you want to manage only a few machines at a time, for example during a rolling update, you can define how many hosts Ansible should manage at a single time using the ``serial`` keyword:" msgstr "デフォルトã§ã¯ã€Ansible ã¯ã€å„プレイ㮠``hosts:`` フィールドã§è¨å®šã—㟠:ref:`pattern <intro_patterns>` ã®ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã«å¯¾ã—ã¦ä¸¦è¡Œã—ã¦å®Ÿè¡Œã—ã¾ã™ã€‚ãƒãƒ¼ãƒªãƒ³ã‚°ã‚¢ãƒƒãƒ—デートä¸ãªã©ã€ä¸€åº¦ã«æ•°å°ã®ãƒžã‚·ãƒ³ã®ã¿ã‚’管ç†ã™ã‚‹å ´åˆã¯ã€``serial`` ã‚ーワードを使用ã—ã¦ã€Ansible ãŒä¸€åº¦ã«ç®¡ç†ã™ã‚‹ãƒ›ã‚¹ãƒˆã®æ•°ã‚’定義ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:62 -msgid "In the above example, if we had 6 hosts in the group 'webservers', Ansible would execute the play completely (both tasks) on 3 of the hosts before moving on to the next 3 hosts::" +#: ../../rst/user_guide/playbooks_strategies.rst:71 +msgid "In the above example, if we had 6 hosts in the group 'webservers', Ansible would execute the play completely (both tasks) on 3 of the hosts before moving on to the next 3 hosts:" msgstr "上ã®ä¾‹ã§ã¯ã€ã€Œwebserversã€ã¨ã„ã†ã‚°ãƒ«ãƒ¼ãƒ—ã« 6 å°ã®ãƒ›ã‚¹ãƒˆãŒã‚ã£ãŸå ´åˆã€Ansible ã¯ãã®ã†ã¡ã® 3 å°ã®ãƒ›ã‚¹ãƒˆã§ãƒ—レイを完全㫠(両方ã®ã‚¿ã‚¹ã‚¯ã‚’) 実行ã—ã¦ã‹ã‚‰ã€æ¬¡ã® 3 å°ã®ãƒ›ã‚¹ãƒˆã«ç§»ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:98 -msgid "You can also specify a percentage with the ``serial`` keyword. Ansible applies the percentage to the total number of hosts in a play to determine the number of hosts per pass::" +#: ../../rst/user_guide/playbooks_strategies.rst:108 +msgid "You can also specify a percentage with the ``serial`` keyword. Ansible applies the percentage to the total number of hosts in a play to determine the number of hosts per pass:" msgstr "``serial`` ã‚ーワードã§ãƒ‘ーセンテージを指定ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚Ansible ã¯ã€ãƒ—レイ内ã®ãƒ›ã‚¹ãƒˆã®åˆè¨ˆæ•°ã«ãƒ‘ーセンテージをé©ç”¨ã—ã¦ã€ãƒ‘スã”ã¨ã®ãƒ›ã‚¹ãƒˆæ•°ã‚’決定ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:105 +#: ../../rst/user_guide/playbooks_strategies.rst:117 msgid "If the number of hosts does not divide equally into the number of passes, the final pass contains the remainder. In this example, if you had 20 hosts in the webservers group, the first batch would contain 6 hosts, the second batch would contain 6 hosts, the third batch would contain 6 hosts, and the last batch would contain 2 hosts." msgstr "ホストã®æ•°ãŒãƒ‘スã®æ•°ã«ç‰ã—ã分é…ã•ã‚Œãªã„å ´åˆã¯ã€æœ€å¾Œã®ãƒ‘スã«ã¯æ®‹ã‚Šã®æ•°ãŒå«ã¾ã‚Œã¾ã™ã€‚ã“ã®ä¾‹ã§ã¯ã€webservers グループ㫠20 å°ã®ãƒ›ã‚¹ãƒˆãŒã‚ã‚‹å ´åˆã€æœ€åˆã®ãƒãƒƒãƒã«ã¯ 6 å°ã®ãƒ›ã‚¹ãƒˆãŒã€2 番目ã®ãƒãƒƒãƒã«ã¯ 6 å°ã®ãƒ›ã‚¹ãƒˆãŒã€3 番目ã®ãƒãƒƒãƒã«ã¯ 6 å°ã®ãƒ›ã‚¹ãƒˆãŒã€ãã—ã¦æœ€å¾Œã®ãƒãƒƒãƒã«ã¯ 2 å°ã®ãƒ›ã‚¹ãƒˆãŒå«ã¾ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:107 -msgid "You can also specify batch sizes as a list. For example::" +#: ../../rst/user_guide/playbooks_strategies.rst:119 +msgid "You can also specify batch sizes as a list. For example:" msgstr "ã¾ãŸã€ãƒãƒƒãƒã‚µã‚¤ã‚ºã‚’リストã¨ã—ã¦æŒ‡å®šã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:117 +#: ../../rst/user_guide/playbooks_strategies.rst:131 msgid "In the above example, the first batch would contain a single host, the next would contain 5 hosts, and (if there are any hosts left), every following batch would contain either 10 hosts or all the remaining hosts, if fewer than 10 hosts remained." msgstr "上記ã®ä¾‹ã§ã¯ã€æœ€åˆã®ãƒãƒƒãƒã«ã¯ 1 å°ã®ãƒ›ã‚¹ãƒˆãŒå«ã¾ã‚Œã€æ¬¡ã®ãƒãƒƒãƒã«ã¯ 5 å°ã®ãƒ›ã‚¹ãƒˆãŒå«ã¾ã‚Œã€(ホストãŒæ®‹ã£ã¦ã„ã‚Œã°) ãã®å¾Œã®ã™ã¹ã¦ã®ãƒãƒƒãƒã«ã¯ 10 å°ã®ãƒ›ã‚¹ãƒˆãŒå«ã¾ã‚Œã‚‹ã‹ã€ã¾ãŸã¯ 10 å°æœªæº€ã®ãƒ›ã‚¹ãƒˆãŒæ®‹ã£ã¦ã„ã‚Œã°ã€æ®‹ã‚Šã®ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆãŒå«ã¾ã‚Œã‚‹ã“ã¨ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:119 -msgid "You can list multiple batch sizes as percentages::" +#: ../../rst/user_guide/playbooks_strategies.rst:133 +msgid "You can list multiple batch sizes as percentages:" msgstr "複数ã®ãƒãƒƒãƒã‚µã‚¤ã‚ºã‚’パーセンテージã¨ã—ã¦ä¸€è¦§è¡¨ç¤ºã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:129 -msgid "You can also mix and match the values::" +#: ../../rst/user_guide/playbooks_strategies.rst:145 +msgid "You can also mix and match the values:" msgstr "値を混在ã•ã›ãŸã‚Šã€ä¸€è‡´ã•ã›ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:140 +#: ../../rst/user_guide/playbooks_strategies.rst:158 msgid "No matter how small the percentage, the number of hosts per pass will always be 1 or greater." msgstr "パーセンテージをå°ã•ãã—ã¦ã‚‚ã€å„パスã®ãƒ›ã‚¹ãƒˆæ•°ã¯å¸¸ã« 1 以上ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:143 +#: ../../rst/user_guide/playbooks_strategies.rst:161 msgid "Restricting execution with ``throttle``" msgstr "``throttle`` ã§å®Ÿè¡Œã‚’制é™" -#: ../../rst/user_guide/playbooks_strategies.rst:145 -msgid "The ``throttle`` keyword limits the number of workers for a particular task. It can be set at the block and task level. Use ``throttle`` to restrict tasks that may be CPU-intensive or interact with a rate-limiting API::" +#: ../../rst/user_guide/playbooks_strategies.rst:163 +msgid "The ``throttle`` keyword limits the number of workers for a particular task. It can be set at the block and task level. Use ``throttle`` to restrict tasks that may be CPU-intensive or interact with a rate-limiting API:" msgstr "``throttle`` ã‚ーワードã¯ã€ç‰¹å®šã®ã‚¿ã‚¹ã‚¯ã«å¯¾ã™ã‚‹ãƒ¯ãƒ¼ã‚«ãƒ¼ã®æ•°ã‚’制é™ã—ã¾ã™ã€‚ã“ã‚Œã¯ã€ãƒ–ãƒãƒƒã‚¯ãŠã‚ˆã³ã‚¿ã‚¹ã‚¯ã®ãƒ¬ãƒ™ãƒ«ã§è¨å®šã§ãã¾ã™ã€‚``throttle`` を使用ã—ã¦ã€CPU ã«è² è·ãŒã‹ã‹ã‚‹å¯èƒ½æ€§ã®ã‚るタスクやã€ãƒ¬ãƒ¼ãƒˆåˆ¶é™ API ã¨ç›¸äº’作用ã™ã‚‹ã‚¿ã‚¹ã‚¯ã‚’制é™ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:151 +#: ../../rst/user_guide/playbooks_strategies.rst:171 msgid "If you have already restricted the number of forks or the number of machines to execute against in parallel, you can reduce the number of workers with ``throttle``, but you cannot increase it. In other words, to have an effect, your ``throttle`` setting must be lower than your ``forks`` or ``serial`` setting if you are using them together." msgstr "ã™ã§ã«ãƒ•ã‚©ãƒ¼ã‚¯ã®æ•°ã‚„並列実行ã™ã‚‹ãƒžã‚·ãƒ³ã®æ•°ã‚’制é™ã—ã¦ã„ã‚‹å ´åˆã¯ã€``throttle`` ã§ãƒ¯ãƒ¼ã‚«ãƒ¼ã®æ•°ã‚’減らã™ã“ã¨ã¯ã§ãã¾ã™ãŒã€å¢—ã‚„ã™ã“ã¨ã¯ã§ãã¾ã›ã‚“。ã¤ã¾ã‚Šã€ãれをåˆã‚ã›ã¦ä½¿ç”¨ã™ã‚‹å ´åˆã«åŠ¹æžœã‚’å¾—ã‚‹ãŸã‚ã«ã¯ã€``throttle`` ã®è¨å®šãŒ ``forks`` ã‚„ ``serial`` ã®è¨å®šã‚ˆã‚Šã‚‚低ããªã‘ã‚Œã°ãªã‚Šã¾ã›ã‚“。" -#: ../../rst/user_guide/playbooks_strategies.rst:154 +#: ../../rst/user_guide/playbooks_strategies.rst:174 msgid "Ordering execution based on inventory" msgstr "インベントリーã«åŸºã¥ã実行ã®é †åºä»˜ã‘" -#: ../../rst/user_guide/playbooks_strategies.rst:156 +#: ../../rst/user_guide/playbooks_strategies.rst:176 msgid "The ``order`` keyword controls the order in which hosts are run. Possible values for order are:" msgstr "``order`` ã‚ーワードã¯ã€ãƒ›ã‚¹ãƒˆãŒå®Ÿè¡Œã™ã‚‹é †åºã‚’制御ã—ã¾ã™ã€‚order ã«æŒ‡å®šã§ãる値ã¯æ¬¡ã®ã¨ãŠã‚Šã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:158 +#: ../../rst/user_guide/playbooks_strategies.rst:178 msgid "inventory:" msgstr "inventory:" -#: ../../rst/user_guide/playbooks_strategies.rst:159 +#: ../../rst/user_guide/playbooks_strategies.rst:179 msgid "(default) The order provided by the inventory for the selection requested (see note below)" msgstr "（デフォルト）è¦æ±‚ã•ã‚ŒãŸé¸æŠžã«å¯¾ã—ã¦ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã«ã‚ˆã£ã¦æä¾›ã•ã‚Œã‚‹é †åºï¼ˆä»¥ä¸‹ã®æ³¨è¨˜ã‚’å‚照）" -#: ../../rst/user_guide/playbooks_strategies.rst:160 +#: ../../rst/user_guide/playbooks_strategies.rst:180 msgid "reverse_inventory:" msgstr "reverse_inventory:" -#: ../../rst/user_guide/playbooks_strategies.rst:161 +#: ../../rst/user_guide/playbooks_strategies.rst:181 msgid "The same as above, but reversing the returned list" msgstr "上記ã¨åŒã˜ã§ã™ãŒã€è¿”ã•ã‚ŒãŸãƒªã‚¹ãƒˆã®å†æ¤œè¨¼" -#: ../../rst/user_guide/playbooks_strategies.rst:162 +#: ../../rst/user_guide/playbooks_strategies.rst:182 msgid "sorted:" msgstr "sorted:" -#: ../../rst/user_guide/playbooks_strategies.rst:163 +#: ../../rst/user_guide/playbooks_strategies.rst:183 msgid "Sorted alphabetically sorted by name" msgstr "åå‰ã‚’ã‚¢ãƒ«ãƒ•ã‚¡ãƒ™ãƒƒãƒˆé †ã§ä¸¦ã¹æ›¿ãˆã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:164 +#: ../../rst/user_guide/playbooks_strategies.rst:184 msgid "reverse_sorted:" msgstr "reverse_sorted:" -#: ../../rst/user_guide/playbooks_strategies.rst:165 +#: ../../rst/user_guide/playbooks_strategies.rst:185 msgid "Sorted by name in reverse alphabetical order" msgstr "アルファベットã®é€†é †ã§åå‰ãŒã‚½ãƒ¼ãƒˆã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:167 +#: ../../rst/user_guide/playbooks_strategies.rst:187 msgid "shuffle:" msgstr "shuffle:" -#: ../../rst/user_guide/playbooks_strategies.rst:167 +#: ../../rst/user_guide/playbooks_strategies.rst:187 msgid "Randomly ordered on each run" msgstr "実行ã”ã¨ã«ãƒ©ãƒ³ãƒ€ãƒ ã«é †åºä»˜ã‘られã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:170 +#: ../../rst/user_guide/playbooks_strategies.rst:190 msgid "the 'inventory' order does not equate to the order in which hosts/groups are defined in the inventory source file, but the 'order in which a selection is returned from the compiled inventory'. This is a backwards compatible option and while reproducible it is not normally predictable. Due to the nature of inventory, host patterns, limits, inventory plugins and the ability to allow multiple sources it is almost impossible to return such an order. For simple cases this might happen to match the file definition order, but that is not guaranteed." msgstr "'インベントリー' ã®é †åºã¯ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚½ãƒ¼ã‚¹ãƒ•ã‚¡ã‚¤ãƒ«å†…ã§ãƒ›ã‚¹ãƒˆ/グループãŒå®šç¾©ã™ã‚‹é †åºã¨åŒã˜ã§ã¯ã‚ã‚Šã¾ã›ã‚“ãŒã€'コンパイルã•ã‚ŒãŸã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‹ã‚‰é¸æŠžãŒè¿”ã•ã‚Œã‚‹é †åº' ã¨åŒã˜ã§ã™ã€‚ã“ã‚Œã¯ä¸‹ä½äº’æ›æ€§ã®ã‚るオプションã§ã‚ã‚Šã€å†ç¾å¯èƒ½ã§ã™ãŒã€é€šå¸¸ã¯äºˆæ¸¬ã§ãã¾ã›ã‚“。インベントリーã®æ€§è³ªã€ãƒ›ã‚¹ãƒˆãƒ‘ターンã€åˆ¶é™ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ—ラグインã€ãŠã‚ˆã³è¤‡æ•°ã®ã‚½ãƒ¼ã‚¹ã‚’許å¯ã™ã‚‹æ©Ÿèƒ½ã«ã‚ˆã‚Šã€ãã®ã‚ˆã†ãªé †åºã‚’è¿”ã™ã“ã¨ã¯ã»ã¨ã‚“ã©ä¸å¯èƒ½ã§ã™ã€‚å˜ç´”ãªã‚±ãƒ¼ã‚¹ã§ã¯ã€ã“ã‚Œã¯ãƒ•ã‚¡ã‚¤ãƒ«å®šç¾©ã®é †åºã¨ä¸€è‡´ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ãŒã€ãã‚Œã¯ä¿è¨¼ã•ã‚Œã¦ã„ã¾ã›ã‚“。" -#: ../../rst/user_guide/playbooks_strategies.rst:175 +#: ../../rst/user_guide/playbooks_strategies.rst:195 msgid "Running on a single machine with ``run_once``" msgstr "シングルマシンã§ã€``run_once`` ã§å‹•ä½œã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:177 -msgid "If you want a task to run only on the first host in your batch of hosts, set ``run_once`` to true on that task::" +#: ../../rst/user_guide/playbooks_strategies.rst:197 +msgid "If you want a task to run only on the first host in your batch of hosts, set ``run_once`` to true on that task:" msgstr "ホストã®ãƒãƒƒãƒã®æœ€åˆã®ãƒ›ã‚¹ãƒˆã§ã‚¿ã‚¹ã‚¯ã‚’実行ã™ã‚‹å ´åˆã¯ã€ãã®ã‚¿ã‚¹ã‚¯ã§ ``run_once`` ã‚’ true ã«è¨å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:191 -msgid "Ansible executes this task on the first host in the current batch and applies all results and facts to all the hosts in the same batch. This approach is similar to applying a conditional to a task such as::" +#: ../../rst/user_guide/playbooks_strategies.rst:213 +msgid "Ansible executes this task on the first host in the current batch and applies all results and facts to all the hosts in the same batch. This approach is similar to applying a conditional to a task such as:" msgstr "Ansible ã¯ã€ç¾åœ¨ã®ãƒãƒƒãƒã®æœ€åˆã®ãƒ›ã‚¹ãƒˆã§ã“ã®ã‚¿ã‚¹ã‚¯ã‚’実行ã—ã€ã™ã¹ã¦ã®çµæžœã¨ãƒ•ã‚¡ã‚¯ãƒˆã‚’åŒã˜ãƒãƒƒãƒã®ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã«é©ç”¨ã—ã¾ã™ã€‚ã“ã®æ–¹æ³•ã¯ã€æ¬¡ã®ã‚ˆã†ãªæ¡ä»¶ã‚’タスクã«é©ç”¨ã™ã‚‹ã“ã¨ã«ä¼¼ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:196 -msgid "However, with ``run_once``, the results are applied to all the hosts. To run the task on a specific host, instead of the first host in the batch, delegate the task::" +#: ../../rst/user_guide/playbooks_strategies.rst:220 +msgid "However, with ``run_once``, the results are applied to all the hosts. To run the task on a specific host, instead of the first host in the batch, delegate the task:" msgstr "ãŸã ã—ã€``run_once`` ã§ã¯ã€çµæžœã¯ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã«é©ç”¨ã•ã‚Œã¾ã™ã€‚ãƒãƒƒãƒã®æœ€åˆã®ãƒ›ã‚¹ãƒˆã§ã¯ãªãã€ç‰¹å®šã®ãƒ›ã‚¹ãƒˆã§ã‚¿ã‚¹ã‚¯ã‚’実行ã™ã‚‹ã«ã¯ã€ã‚¿ã‚¹ã‚¯ã‚’次ã®ã‚ˆã†ã«å§”è²ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:202 +#: ../../rst/user_guide/playbooks_strategies.rst:228 msgid "As always with :ref:`delegation <playbooks_delegation>`, the action will be executed on the delegated host, but the information is still that of the original host in the task." msgstr ":ref:`å§”è² <playbooks_delegation>` ã®å ´åˆã¨åŒæ§˜ã€ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ã¯å§”è²ã•ã‚ŒãŸãƒ›ã‚¹ãƒˆã§å®Ÿè¡Œã•ã‚Œã¾ã™ãŒã€æƒ…å ±ã¯ã‚¿ã‚¹ã‚¯ã®å…ƒã®ãƒ›ã‚¹ãƒˆã®æƒ…å ±ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:205 +#: ../../rst/user_guide/playbooks_strategies.rst:231 msgid "When used together with ``serial``, tasks marked as ``run_once`` will be run on one host in *each* serial batch. If the task must run only once regardless of ``serial`` mode, use :code:`when: inventory_hostname == ansible_play_hosts_all[0]` construct." msgstr "``serial`` ã¨ä½µç”¨ã™ã‚‹ã¨ã€``run_once`` ã¨ãƒžãƒ¼ã‚¯ã•ã‚ŒãŸã‚¿ã‚¹ã‚¯ã¯ã€*å„* シリアルãƒãƒƒãƒã®ä¸ã® 1 å°ã®ãƒ›ã‚¹ãƒˆã§å®Ÿè¡Œã—ã¾ã™ã€‚タスク㌠``serial`` モードã«é–¢ä¿‚ãªã 1 回ã ã‘実行ã™ã‚‹å¿…è¦ãŒã‚ã‚‹å ´åˆã¯ã€:code:`when: inventory_hostname == ansible_play_hosts_all[0]` コンストラクトを使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:209 +#: ../../rst/user_guide/playbooks_strategies.rst:235 msgid "Any conditional (in other words, `when:`) will use the variables of the 'first host' to decide if the task runs or not, no other hosts will be tested." msgstr "æ¡ä»¶ (ã¤ã¾ã‚Š `when:`) ã¯ã€ã€Œfirst hostã€ã®å¤‰æ•°ã‚’使用ã—ã¦ã€ã‚¿ã‚¹ã‚¯ãŒå®Ÿè¡Œã•ã‚Œã‚‹ã‹ã©ã†ã‹ã‚’判æ–ã—ã€ä»–ã®ãƒ›ã‚¹ãƒˆã¯ãƒ†ã‚¹ãƒˆã•ã‚Œã¾ã›ã‚“。" -#: ../../rst/user_guide/playbooks_strategies.rst:212 +#: ../../rst/user_guide/playbooks_strategies.rst:238 msgid "If you want to avoid the default behavior of setting the fact for all hosts, set ``delegate_facts: True`` for the specific task or block." msgstr "ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã«ãƒ•ã‚¡ã‚¯ãƒˆã‚’è¨å®šã™ã‚‹ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã®å‹•ä½œã‚’回é¿ã™ã‚‹å ´åˆã¯ã€ç‰¹å®šã®ã‚¿ã‚¹ã‚¯ã¾ãŸã¯ãƒ–ãƒãƒƒã‚¯ã« ``delegate_facts: True`` ã‚’è¨å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_strategies.rst:218 +#: ../../rst/user_guide/playbooks_strategies.rst:244 msgid ":ref:`playbooks_delegation`" msgstr ":ref:`playbooks_delegation`" -#: ../../rst/user_guide/playbooks_strategies.rst:219 +#: ../../rst/user_guide/playbooks_strategies.rst:245 msgid "Running tasks on or assigning facts to specific machines" msgstr "特定マシンã§ã®ã‚¿ã‚¹ã‚¯ã®å®Ÿè¡Œã€ã¾ãŸã¯ç‰¹å®šãƒžã‚·ãƒ³ã¸ã®ãƒ•ã‚¡ã‚¯ãƒˆã®å‰²ã‚Šå½“ã¦" @@ -10084,162 +10081,172 @@ msgid "As of Ansible 2.5, using a jinja test as a filter will generate a warning msgstr "Ansible 2.5 ã®æ™‚点ã§ã¯ã€jinja テストをフィルターã¨ã—ã¦ä½¿ç”¨ã™ã‚‹ã¨è¦å‘ŠãŒç”Ÿæˆã•ã‚Œã¾ã™ã€‚" #: ../../rst/user_guide/playbooks_tests.rst:27 -msgid "The syntax for using a jinja test is as follows::" +msgid "The syntax for using a jinja test is as follows" msgstr "jinja テストを使用ã™ã‚‹ãŸã‚ã®æ§‹æ–‡ã¯ã€ä»¥ä¸‹ã®ã¨ãŠã‚Šã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:31 -msgid "Such as::" -msgstr "例::" +#: ../../rst/user_guide/playbooks_tests.rst:33 +msgid "Such as" +msgstr "例:" -#: ../../rst/user_guide/playbooks_tests.rst:38 +#: ../../rst/user_guide/playbooks_tests.rst:42 msgid "Testing strings" msgstr "æ–‡å—列ã®ãƒ†ã‚¹ãƒˆ" -#: ../../rst/user_guide/playbooks_tests.rst:40 -msgid "To match strings against a substring or a regular expression, use the ``match``, ``search`` or ``regex`` tests::" +#: ../../rst/user_guide/playbooks_tests.rst:44 +msgid "To match strings against a substring or a regular expression, use the ``match``, ``search`` or ``regex`` tests" msgstr "サブ文å—列ã¾ãŸã¯æ£è¦è¡¨ç¾ã«å¯¾ã—ã¦æ–‡å—列ã¨ä¸€è‡´ã•ã›ã‚‹ã«ã¯ã€ã€Œ``match``ã€ã€ã€Œ``search``ã€ã€ã¾ãŸã¯ã€Œ``regex``ã€ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:62 +#: ../../rst/user_guide/playbooks_tests.rst:68 msgid "``match`` succeeds if it finds the pattern at the beginning of the string, while ``search`` succeeds if it finds the pattern anywhere within string. By default, ``regex`` works like ``search``, but ``regex`` can be configured to perform other tests as well, by passing the ``match_type`` keyword argument. In particular, ``match_type`` determines the ``re`` method that gets used to perform the search. The full list can be found in the relevant Python documentation `here <https://docs.python.org/3/library/re.html#regular-expression-objects>`_." msgstr "``match`` ã¯ã€æ–‡å—列ã®å…ˆé ã§ãƒ‘ターンを見ã¤ã‘ãŸå ´åˆã«æˆåŠŸã—ã€``search`` ã¯ã€æ–‡å—列内ã®ä»»æ„ã®å ´æ‰€ã§ãƒ‘ターンを見ã¤ã‘ãŸå ´åˆã«æˆåŠŸã—ã¾ã™ã€‚デフォルトã§ã¯ã€``regex`` 㯠``search`` ã®ã‚ˆã†ã«å‹•ä½œã—ã¾ã™ãŒã€``regex`` 㯠``match_type`` ã‚ーワード引数を渡ã™ã“ã¨ã§ã€ä»–ã®ãƒ†ã‚¹ãƒˆã‚‚実行ã™ã‚‹ã‚ˆã†ã«æ§‹æˆã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚特ã«ã€``match_type`` ã¯ã€æ¤œç´¢ã‚’実行ã™ã‚‹éš›ã«ä½¿ç”¨ã•ã‚Œã‚‹ ``re`` メソッドを決定ã—ã¾ã™ã€‚完全ãªãƒªã‚¹ãƒˆã¯ã€`ã“ã¡ã‚‰ <https://docs.python.org/3/library/re.html#regular-expression-objects>`_ ã«ã‚る関連 Python ドã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_tests.rst:64 +#: ../../rst/user_guide/playbooks_tests.rst:70 msgid "All of the string tests also take optional ``ignorecase`` and ``multiline`` arguments. These correspond to ``re.I`` and ``re.M`` from Python's ``re`` library, respectively." msgstr "ã™ã¹ã¦ã®æ–‡å—列テストã¯ã€ä»»æ„ã® ``ignorecase`` 引数ãŠã‚ˆã³ ``multiline`` 引数をå–ã‚Šã¾ã™ã€‚ã“れらã¯ã€Python ã® ``re`` ライブラリーã‹ã‚‰ãã‚Œãžã‚Œ ``re.I`` ãŠã‚ˆã³ ``re.M`` ã«å¯¾å¿œã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:69 +#: ../../rst/user_guide/playbooks_tests.rst:75 msgid "Vault" msgstr "Vault" -#: ../../rst/user_guide/playbooks_tests.rst:73 +#: ../../rst/user_guide/playbooks_tests.rst:79 msgid "You can test whether a variable is an inline single vault encrypted value using the ``vault_encrypted`` test." msgstr "変数ãŒã‚¤ãƒ³ãƒ©ã‚¤ãƒ³ã® 1 ã¤ã® vault ã§æš—å·åŒ–ã•ã‚ŒãŸå€¤ã§ã‚ã‚‹ã‹ã©ã†ã‹ã¯ã€``vault_encrypted`` テストã§ãƒ†ã‚¹ãƒˆã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:93 +#: ../../rst/user_guide/playbooks_tests.rst:99 msgid "Testing truthiness" msgstr "真å½ã®æ¤œè¨¼" -#: ../../rst/user_guide/playbooks_tests.rst:97 +#: ../../rst/user_guide/playbooks_tests.rst:103 msgid "As of Ansible 2.10, you can now perform Python like truthy and falsy checks." msgstr "Ansible 2.10 以é™ã§ã¯ã€Python を真å½ãƒã‚§ãƒƒã‚¯ã®ã‚ˆã†ã«å®Ÿè¡Œã§ãるよã†ã«ãªã‚Šã¾ã—ãŸã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:113 +#: ../../rst/user_guide/playbooks_tests.rst:119 msgid "Additionally, the ``truthy`` and ``falsy`` tests accept an optional parameter called ``convert_bool`` that will attempt to convert boolean indicators to actual booleans." msgstr "ã¾ãŸã€``truthy`` テストãŠã‚ˆã³ ``falsy`` テストã¯ã€ãƒ–ール値インジケーターを実際ã®ãƒ–ール値ã«å¤‰æ›ã—よã†ã¨ã™ã‚‹ ``convert_bool`` ã¨å‘¼ã°ã‚Œã‚‹ä»»æ„ã®ãƒ‘ラメーターをå—ã‘入れã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:133 +#: ../../rst/user_guide/playbooks_tests.rst:139 msgid "Comparing versions" msgstr "ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®æ¯”較" -#: ../../rst/user_guide/playbooks_tests.rst:137 +#: ../../rst/user_guide/playbooks_tests.rst:143 msgid "In 2.5 ``version_compare`` was renamed to ``version``" msgstr "2.5 ã§ã¯ã€``version_compare`` ã®åå‰ãŒ ``version`` ã«å¤‰æ›´ã•ã‚Œã¾ã—ãŸã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:139 +#: ../../rst/user_guide/playbooks_tests.rst:145 msgid "To compare a version number, such as checking if the ``ansible_facts['distribution_version']`` version is greater than or equal to '12.04', you can use the ``version`` test." msgstr "``ansible_facts['distribution_version']`` ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒã€Œ12.04ã€ä»¥ä¸Šã‹ã©ã†ã‹ã‚’確èªã™ã‚‹ãªã©ã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ç•ªå·ã‚’比較ã™ã‚‹ã«ã¯ã€``version`` テストを使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:142 -msgid "The ``version`` test can also be used to evaluate the ``ansible_facts['distribution_version']``::" +#: ../../rst/user_guide/playbooks_tests.rst:148 +msgid "The ``version`` test can also be used to evaluate the ``ansible_facts['distribution_version']``" msgstr "``version`` テストを使用ã—㦠``ansible_facts['distribution_version']`` を評価ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:146 +#: ../../rst/user_guide/playbooks_tests.rst:154 msgid "If ``ansible_facts['distribution_version']`` is greater than or equal to 12.04, this test returns True, otherwise False." msgstr "``ansible_facts['distribution_version']`` ㌠12.04 以上ã®å ´åˆã¯ã€ã“ã®ãƒ†ã‚¹ãƒˆã§ True ãŒè¿”ã‚Šã€ãれ以外ã®å ´åˆã¯ False ãŒè¿”ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:148 -msgid "The ``version`` test accepts the following operators::" +#: ../../rst/user_guide/playbooks_tests.rst:156 +msgid "The ``version`` test accepts the following operators" msgstr "``version`` テストã§ã¯ã€ä»¥ä¸‹ã®æ¼”ç®—åã‚’å—ã‘入れã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:152 -msgid "This test also accepts a 3rd parameter, ``strict`` which defines if strict version parsing as defined by ``distutils.version.StrictVersion`` should be used. The default is ``False`` (using ``distutils.version.LooseVersion``), ``True`` enables strict version parsing::" +#: ../../rst/user_guide/playbooks_tests.rst:162 +msgid "This test also accepts a 3rd parameter, ``strict`` which defines if strict version parsing as defined by ``distutils.version.StrictVersion`` should be used. The default is ``False`` (using ``distutils.version.LooseVersion``), ``True`` enables strict version parsing" msgstr "ã“ã®ãƒ†ã‚¹ãƒˆã¯ã€3 番目ã®ãƒ‘ラメーター ``strict`` ã‚‚å—ã‘入れã¾ã™ã€‚ã“ã‚Œã¯ã€``distutils.version.StrictVersion`` ã§å®šç¾©ã•ã‚ŒãŸåŽ³æ ¼ãªãƒãƒ¼ã‚¸ãƒ§ãƒ³è§£æžæ©Ÿèƒ½ã‚’使用ã§ãã¾ã™ã€‚デフォルト㯠``False`` (``distutils.version.LooseVersion`` を使用) ã§ã€``True`` ã¯ã€åŽ³æ ¼ãªãƒãƒ¼ã‚¸ãƒ§ãƒ³è§£æžã‚’有効ã«ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:156 -msgid "As of Ansible 2.11 the ``version`` test accepts a ``version_type`` parameter which is mutually exclusive with ``strict``, and accepts the following values::" +#: ../../rst/user_guide/playbooks_tests.rst:168 +msgid "As of Ansible 2.11 the ``version`` test accepts a ``version_type`` parameter which is mutually exclusive with ``strict``, and accepts the following values" msgstr "Ansible 2.11 ã®æ™‚点ã§ã€``version`` テスト㯠``strict`` ã¨ç›¸äº’ã«æŽ’他的㪠``version_type`` パラメーターをå—ã‘入れã€ä»¥ä¸‹ã®å€¤ã‚’å—ã‘入れã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:160 -msgid "Using ``version_type`` to compare a semantic version would be achieved like the following::" +#: ../../rst/user_guide/playbooks_tests.rst:174 +msgid "Using ``version_type`` to compare a semantic version would be achieved like the following" msgstr "``version_type`` を使用ã—ã¦ã‚»ãƒžãƒ³ãƒ†ã‚£ãƒƒã‚¯ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’比較ã™ã‚‹ã¨ã€ä»¥ä¸‹ã®ã‚ˆã†ã«å®Ÿè¡Œã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:164 -msgid "When using ``version`` in a playbook or role, don't use ``{{ }}`` as described in the `FAQ <https://docs.ansible.com/ansible/latest/reference_appendices/faq.html#when-should-i-use-also-how-to-interpolate-variables-or-dynamic-variable-names>`_::" +#: ../../rst/user_guide/playbooks_tests.rst:180 +msgid "When using ``version`` in a playbook or role, don't use ``{{ }}`` as described in the `FAQ <https://docs.ansible.com/ansible/latest/reference_appendices/faq.html#when-should-i-use-also-how-to-interpolate-variables-or-dynamic-variable-names>`_" msgstr "Playbook ã¾ãŸã¯ãƒãƒ¼ãƒ«ã§ ``version`` を使用ã™ã‚‹å ´åˆã¯ã€`FAQ <https://docs.ansible.com/ansible/latest/reference_appendices/faq.html#when-should-i-use-also-how-to-interpolate-variables-or-dynamic-variable-names>`_ ã§èª¬æ˜Žã•ã‚Œã¦ã„るよã†ã« ``{{ }}`` を使用ã—ãªã„ã§ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_tests.rst:177 +#: ../../rst/user_guide/playbooks_tests.rst:195 msgid "Set theory tests" msgstr "セットç†è«–テスト" -#: ../../rst/user_guide/playbooks_tests.rst:181 +#: ../../rst/user_guide/playbooks_tests.rst:199 msgid "In 2.5 ``issubset`` and ``issuperset`` were renamed to ``subset`` and ``superset``" msgstr "2.5 ã§ã¯ã€``issubset`` ãŠã‚ˆã³ ``issuperset`` ã®åå‰ãŒ ``subset`` ãŠã‚ˆã³ ``superset`` ã«å¤‰æ›´ã•ã‚Œã¾ã—ãŸã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:183 -msgid "To see if a list includes or is included by another list, you can use 'subset' and 'superset'::" +#: ../../rst/user_guide/playbooks_tests.rst:201 +msgid "To see if a list includes or is included by another list, you can use 'subset' and 'superset'" msgstr "リストã«åˆ¥ã®ãƒªã‚¹ãƒˆãŒå«ã¾ã‚Œã¦ã„ã‚‹ã‹ã€ã¾ãŸã¯ãƒªã‚¹ãƒˆãŒåˆ¥ã®ãƒªã‚¹ãƒˆã«å«ã¾ã‚Œã¦ã„ã‚‹ã‹ã‚’確èªã™ã‚‹ã«ã¯ã€ã€Œsubsetã€ãŠã‚ˆã³ã€Œsupersetã€ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:200 +#: ../../rst/user_guide/playbooks_tests.rst:220 msgid "Testing if a list contains a value" msgstr "リストã«å€¤ãŒå«ã¾ã‚Œã‚‹ã‹ã©ã†ã‹ã®ãƒ†ã‚¹ãƒˆ" -#: ../../rst/user_guide/playbooks_tests.rst:204 -msgid "Ansible includes a ``contains`` test which operates similarly, but in reverse of the Jinja2 provided ``in`` test. The ``contains`` test is designed to work with the ``select``, ``reject``, ``selectattr``, and ``rejectattr`` filters::" +#: ../../rst/user_guide/playbooks_tests.rst:224 +msgid "Ansible includes a ``contains`` test which operates similarly, but in reverse of the Jinja2 provided ``in`` test. The ``contains`` test is designed to work with the ``select``, ``reject``, ``selectattr``, and ``rejectattr`` filters" msgstr "Ansible ã«ã¯ã€Jinja2 ãŒæä¾›ã™ã‚‹ ``in`` テストã¨ã¯é€†ã«ã€åŒæ§˜ã®å‹•ä½œã‚’ã™ã‚‹ ``contains`` テストãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚``contains`` テストã¯ã€ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã® ``select``ã€``reject``ã€``selectattr``ã€ãŠã‚ˆã³ ``rejectattr`` ã§å‹•ä½œã™ã‚‹ã‚ˆã†ã«è¨è¨ˆã•ã‚Œã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:236 +#: ../../rst/user_guide/playbooks_tests.rst:258 msgid "Testing if a list value is True" msgstr "リスト値㌠True ã®å ´åˆã®ãƒ†ã‚¹ãƒˆ" -#: ../../rst/user_guide/playbooks_tests.rst:238 -msgid "You can use `any` and `all` to check if any or all elements in a list are true or not::" +#: ../../rst/user_guide/playbooks_tests.rst:260 +msgid "You can use `any` and `all` to check if any or all elements in a list are true or not" msgstr "`any` ãŠã‚ˆã³ `all` を使用ã—ã¦ã€ãƒªã‚¹ãƒˆå†…ã®ä¸€éƒ¨ã¾ãŸã¯ã™ã¹ã¦ã®è¦ç´ ㌠true ã‹ã©ã†ã‹ã‚’確èªã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:261 +#: ../../rst/user_guide/playbooks_tests.rst:285 msgid "Testing paths" msgstr "パスã®ãƒ†ã‚¹ãƒˆ" -#: ../../rst/user_guide/playbooks_tests.rst:263 +#: ../../rst/user_guide/playbooks_tests.rst:287 msgid "In 2.5 the following tests were renamed to remove the ``is_`` prefix" msgstr "2.5 ã§ã¯ã€ä»¥ä¸‹ã®ãƒ†ã‚¹ãƒˆã®åå‰ãŒå¤‰æ›´ã«ãªã‚Šã€``is_`` プレフィックスãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:265 -msgid "The following tests can provide information about a path on the controller::" +#: ../../rst/user_guide/playbooks_tests.rst:289 +msgid "The following tests can provide information about a path on the controller" msgstr "以下ã®ãƒ†ã‚¹ãƒˆã¯ã€ã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©ãƒ¼ä¸Šã®ãƒ‘スã«é–¢ã™ã‚‹æƒ…å ±ã‚’æä¾›ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:296 +#: ../../rst/user_guide/playbooks_tests.rst:322 msgid "Testing size formats" msgstr "サイズ形å¼ã®ãƒ†ã‚¹ãƒˆ" -#: ../../rst/user_guide/playbooks_tests.rst:298 +#: ../../rst/user_guide/playbooks_tests.rst:324 msgid "The ``human_readable`` and ``human_to_bytes`` functions let you test your playbooks to make sure you are using the right size format in your tasks, and that you provide Byte format to computers and human-readable format to people." msgstr "``human_readable`` 関数ãŠã‚ˆã³ ``human_to_bytes`` 関数を使用ã™ã‚‹ã¨ã€Playbook をテストã—ã¦ã€ã‚¿ã‚¹ã‚¯ã§é©åˆ‡ãªã‚µã‚¤ã‚ºã®å½¢å¼ã‚’使用ã—ã¦ã„ã‚‹ã‹ã©ã†ã‹ã€ã¾ãŸã€ã‚³ãƒ³ãƒ”ューターã«ã¯ãƒã‚¤ãƒˆå½¢å¼ã€ãŠã‚ˆã³ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«ã¯äººé–“ãŒåˆ¤èªå¯èƒ½ãªå½¢å¼ã‚’æä¾›ã—ã¦ã„ã‚‹ã‹ã©ã†ã‹ã‚’確èªã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:303 +#: ../../rst/user_guide/playbooks_tests.rst:329 msgid "Human readable" msgstr "人間ãŒèªã¿å–ã‚Šå¯èƒ½" -#: ../../rst/user_guide/playbooks_tests.rst:305 +#: ../../rst/user_guide/playbooks_tests.rst:331 msgid "Asserts whether the given string is human readable or not." msgstr "指定ã®æ–‡å—列ãŒäººãŒåˆ¤èªã§ãã‚‹ã‹ã©ã†ã‹ã‚’アサートã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:324 +#: ../../rst/user_guide/playbooks_tests.rst:333 +#: ../../rst/user_guide/playbooks_tests.rst:358 +msgid "For example" +msgstr "ãŸã¨ãˆã°ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" + +#: ../../rst/user_guide/playbooks_tests.rst:347 +#: ../../rst/user_guide/playbooks_tests.rst:374 +msgid "This would result in" +msgstr "ã“ã‚Œã«ã‚ˆã‚Šã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" + +#: ../../rst/user_guide/playbooks_tests.rst:354 msgid "Human to bytes" msgstr "人間ã‹ã‚‰ãƒã‚¤ãƒˆ" -#: ../../rst/user_guide/playbooks_tests.rst:326 +#: ../../rst/user_guide/playbooks_tests.rst:356 msgid "Returns the given string in the Bytes format." msgstr "指定ã—ãŸæ–‡å—列をãƒã‚¤ãƒˆå½¢å¼ã§è¿”ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:350 +#: ../../rst/user_guide/playbooks_tests.rst:384 msgid "Testing task results" msgstr "タスクçµæžœã®ãƒ†ã‚¹ãƒˆ" -#: ../../rst/user_guide/playbooks_tests.rst:352 -msgid "The following tasks are illustrative of the tests meant to check the status of tasks::" +#: ../../rst/user_guide/playbooks_tests.rst:386 +msgid "The following tasks are illustrative of the tests meant to check the status of tasks" msgstr "以下ã®ã‚¿ã‚¹ã‚¯ã¯ã€ã‚¿ã‚¹ã‚¯ã®ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã‚’確èªã™ã‚‹ãŸã‚ã®ãƒ†ã‚¹ãƒˆã‚’示ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_tests.rst:381 +#: ../../rst/user_guide/playbooks_tests.rst:417 msgid "From 2.1, you can also use success, failure, change, and skip so that the grammar matches, for those who need to be strict about it." msgstr "2.1 以é™ã€æ–‡æ³•ã‚’厳密ã«ã™ã‚‹å¿…è¦ãŒã‚ã‚‹å ´åˆã«ã€successã€failureã€changeã€ãŠã‚ˆã³ skip を使用ã—ã¦ã€æ–‡æ³•ãŒä¸€è‡´ã™ã‚‹ã‚ˆã†ã«ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" @@ -10328,467 +10335,467 @@ msgid "Defining simple variables" msgstr "ç°¡å˜ãªå¤‰æ•°ã®å®šç¾©" #: ../../rst/user_guide/playbooks_variables.rst:52 -msgid "You can define a simple variable using standard YAML syntax. For example::" +msgid "You can define a simple variable using standard YAML syntax. For example:" msgstr "標準㮠YAML 構文を使用ã—ã¦å˜ç´”ãªå¤‰æ•°ã‚’定義ã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:57 +#: ../../rst/user_guide/playbooks_variables.rst:59 msgid "Referencing simple variables" msgstr "å˜ç´”ãªå¤‰æ•°ã®å‚ç…§" -#: ../../rst/user_guide/playbooks_variables.rst:59 -msgid "After you define a variable, use Jinja2 syntax to reference it. Jinja2 variables use double curly braces. For example, the expression ``My amp goes to {{ max_amp_value }}`` demonstrates the most basic form of variable substitution. You can use Jinja2 syntax in playbooks. For example::" +#: ../../rst/user_guide/playbooks_variables.rst:61 +msgid "After you define a variable, use Jinja2 syntax to reference it. Jinja2 variables use double curly braces. For example, the expression ``My amp goes to {{ max_amp_value }}`` demonstrates the most basic form of variable substitution. You can use Jinja2 syntax in playbooks. For example:" msgstr "変数を定義ã—ãŸå¾Œã¯ã€Jinja2 ã®æ§‹æ–‡ã‚’使用ã—ã¦å¤‰æ•°ã‚’å‚ç…§ã—ã¾ã™ã€‚Jinja2 ã®å¤‰æ•°ã«ã¯äºŒé‡ã®ä¸æ‹¬å¼§ãŒä½¿ç”¨ã•ã‚Œã¾ã™ã€‚ãŸã¨ãˆã°ã€``My amp goes to {{ max_amp_value }}`` ã¨ã„ã†å¼ã¯ã€æœ€ã‚‚基本的ãªå½¢ã®å¤‰æ•°ç½®æ›ã‚’示ã—ã¦ã„ã¾ã™ã€‚Playbook ã§ã¯ã€Jinja2 構文を使用ã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:65 +#: ../../rst/user_guide/playbooks_variables.rst:69 msgid "In this example, the variable defines the location of a file, which can vary from one system to another." msgstr "ã“ã®ä¾‹ã§ã¯ã€å¤‰æ•°ãŒãƒ•ã‚¡ã‚¤ãƒ«ã®å ´æ‰€ã‚’定義ã—ã¦ã„ã¾ã™ãŒã€ã“ã‚Œã¯ã‚·ã‚¹ãƒ†ãƒ ã”ã¨ã«ç•°ãªã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:69 +#: ../../rst/user_guide/playbooks_variables.rst:73 msgid "Ansible allows Jinja2 loops and conditionals in :ref:`templates <playbooks_templating>` but not in playbooks. You cannot create a loop of tasks. Ansible playbooks are pure machine-parseable YAML." msgstr "Ansible ã§ã¯ã€:ref:`テンプレート <playbooks_templating>` 㧠Jinja2 ã®ãƒ«ãƒ¼ãƒ—ã‚„æ¡ä»¶åˆ†å²ã‚’使用ã§ãã¾ã™ãŒã€Playbook ã§ã¯ä½¿ç”¨ã§ãã¾ã›ã‚“。タスクã®ãƒ«ãƒ¼ãƒ—を作æˆã™ã‚‹ã“ã¨ã¯ã§ãã¾ã›ã‚“。Ansible ã® Playbook ã¯ç´”粋ã«æ©Ÿæ¢°ã§è§£æžå¯èƒ½ãª YAML ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:74 +#: ../../rst/user_guide/playbooks_variables.rst:78 msgid "When to quote variables (a YAML gotcha)" msgstr "変数を引用ã™ã‚‹ã‚¿ã‚¤ãƒŸãƒ³ã‚° (YAML ã«é–¢ã™ã‚‹æ³¨æ„点)" -#: ../../rst/user_guide/playbooks_variables.rst:76 +#: ../../rst/user_guide/playbooks_variables.rst:80 msgid "If you start a value with ``{{ foo }}``, you must quote the whole expression to create valid YAML syntax. If you do not quote the whole expression, the YAML parser cannot interpret the syntax - it might be a variable or it might be the start of a YAML dictionary. For guidance on writing YAML, see the :ref:`yaml_syntax` documentation." msgstr "値を ``{{ foo }}`` ã§å§‹ã‚ãŸå ´åˆã€æœ‰åŠ¹ãª YAML 構文を作æˆã™ã‚‹ãŸã‚ã«ã¯å¼å…¨ä½“を引用ã—ãªã‘ã‚Œã°ãªã‚Šã¾ã›ã‚“。å¼å…¨ä½“を引用符ã§å›²ã¾ãªã„ã¨ã€YAML パーサーã¯ãã®æ§‹æ–‡ã‚’解釈ã§ãã¾ã›ã‚“。ãã‚Œã¯å¤‰æ•°ã‹ã‚‚ã—ã‚Œãªã„ã—ã€YAML ディレクトリーã®å§‹ã¾ã‚Šã‹ã‚‚ã—ã‚Œã¾ã›ã‚“。YAML ã®è¨˜è¿°æ–¹æ³•ã«ã¤ã„ã¦ã¯ã€ã€Œ:ref:`yaml_syntax`ã€ã®ãƒ‰ã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_variables.rst:78 -msgid "If you use a variable without quotes like this::" +#: ../../rst/user_guide/playbooks_variables.rst:82 +msgid "If you use a variable without quotes like this:" msgstr "引用符ãªã—ã®å¤‰æ•°ã‚’使用ã™ã‚‹å ´åˆã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:84 -msgid "You will see: ``ERROR! Syntax Error while loading YAML.`` If you add quotes, Ansible works correctly::" +#: ../../rst/user_guide/playbooks_variables.rst:90 +msgid "You will see: ``ERROR! Syntax Error while loading YAML.`` If you add quotes, Ansible works correctly:" msgstr "``ERROR! Syntax Error while loading YAML.`` ã‚’å‚ç…§ã—ã¦ãã ã•ã„ã€‚å¼•ç”¨ç¬¦ã‚’è¿½åŠ ã™ã‚‹ã¨ã€Ansible ãŒæ£å¸¸ã«æ©Ÿèƒ½ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:93 +#: ../../rst/user_guide/playbooks_variables.rst:101 msgid "List variables" msgstr "リスト変数" -#: ../../rst/user_guide/playbooks_variables.rst:95 +#: ../../rst/user_guide/playbooks_variables.rst:103 msgid "A list variable combines a variable name with multiple values. The multiple values can be stored as an itemized list or in square brackets ``[]``, separated with commas." msgstr "リスト変数ã¯ã€å¤‰æ•°åã¨è¤‡æ•°ã®å€¤ã‚’組ã¿åˆã‚ã›ãŸã‚‚ã®ã§ã™ã€‚複数ã®å€¤ã¯ã€é …目別ã®ãƒªã‚¹ãƒˆã¨ã—ã¦ã€ã¾ãŸã¯è§’括弧 ``[]`` ã®ä¸ã«ã‚³ãƒ³ãƒžã§åŒºåˆ‡ã£ã¦æ ¼ç´ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:98 +#: ../../rst/user_guide/playbooks_variables.rst:106 msgid "Defining variables as lists" msgstr "変数をリストã¨ã—ã¦å®šç¾©" -#: ../../rst/user_guide/playbooks_variables.rst:100 -msgid "You can define variables with multiple values using YAML lists. For example::" +#: ../../rst/user_guide/playbooks_variables.rst:108 +msgid "You can define variables with multiple values using YAML lists. For example:" msgstr "YAML リストを使用ã—ã¦ã€è¤‡æ•°ã®å€¤ã§å¤‰æ•°ã‚’定義ã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:108 +#: ../../rst/user_guide/playbooks_variables.rst:118 msgid "Referencing list variables" msgstr "リスト変数ã®å‚ç…§" -#: ../../rst/user_guide/playbooks_variables.rst:110 -msgid "When you use variables defined as a list (also called an array), you can use individual, specific fields from that list. The first item in a list is item 0, the second item is item 1. For example::" +#: ../../rst/user_guide/playbooks_variables.rst:120 +msgid "When you use variables defined as a list (also called an array), you can use individual, specific fields from that list. The first item in a list is item 0, the second item is item 1. For example:" msgstr "リスト (é…列ã¨ã‚‚呼ã°ã‚Œã‚‹) ã¨ã—ã¦å®šç¾©ã•ã‚ŒãŸå¤‰æ•°ã‚’使用ã™ã‚‹å ´åˆã¯ã€ãã®ãƒªã‚¹ãƒˆã‹ã‚‰å€‹ã€…ã®ç‰¹å®šã®ãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ã‚’使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚リストã®æœ€åˆã®é …ç›®ã¯é …ç›® 0ã€2 番目ã®é …ç›®ã¯é …ç›® 1 ã§ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:114 +#: ../../rst/user_guide/playbooks_variables.rst:126 msgid "The value of this expression would be \"northeast\"." msgstr "ã“ã®å¼ã®å€¤ã¯ã€Œnortheastã€ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:119 +#: ../../rst/user_guide/playbooks_variables.rst:131 msgid "Dictionary variables" msgstr "ディクショナリー変数" -#: ../../rst/user_guide/playbooks_variables.rst:121 +#: ../../rst/user_guide/playbooks_variables.rst:133 msgid "A dictionary stores the data in key-value pairs. Usually, dictionaries are used to store related data, such as the information contained in an ID or a user profile." msgstr "ディクショナリーã¯ã€ãƒ‡ãƒ¼ã‚¿ã‚’ã‚ーã¨å€¤ã®ãƒšã‚¢ã«ä¿å˜ã—ã¾ã™ã€‚通常ã€ãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼ã¯ ID ã¾ãŸã¯ãƒ¦ãƒ¼ã‚¶ãƒ¼ãƒ—ãƒãƒ•ã‚¡ã‚¤ãƒ«ã«å«ã¾ã‚Œã‚‹æƒ…å ±ãªã©ã®é–¢é€£ãƒ‡ãƒ¼ã‚¿ã‚’ä¿å˜ã™ã‚‹ãŸã‚ã«ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:124 +#: ../../rst/user_guide/playbooks_variables.rst:136 msgid "Defining variables as key:value dictionaries" msgstr "変数を key:value ディクショナリーã¨ã—ã¦å®šç¾©" -#: ../../rst/user_guide/playbooks_variables.rst:126 -msgid "You can define more complex variables using YAML dictionaries. A YAML dictionary maps keys to values. For example::" +#: ../../rst/user_guide/playbooks_variables.rst:138 +msgid "You can define more complex variables using YAML dictionaries. A YAML dictionary maps keys to values. For example:" msgstr "YAML ディクショナリーを使用ã—ã¦ã‚ˆã‚Šè¤‡é›‘ãªå¤‰æ•°ã‚’定義ã§ãã¾ã™ã€‚YAML ディクショナリーã¯ã‚ーを値ã«ãƒžãƒƒãƒ”ングã—ã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:133 +#: ../../rst/user_guide/playbooks_variables.rst:147 msgid "Referencing key:value dictionary variables" msgstr "key:value ディクショナリー変数ã®å‚ç…§" -#: ../../rst/user_guide/playbooks_variables.rst:135 -msgid "When you use variables defined as a key:value dictionary (also called a hash), you can use individual, specific fields from that dictionary using either bracket notation or dot notation::" +#: ../../rst/user_guide/playbooks_variables.rst:149 +msgid "When you use variables defined as a key:value dictionary (also called a hash), you can use individual, specific fields from that dictionary using either bracket notation or dot notation:" msgstr "key:value ディクショナリー (ãƒãƒƒã‚·ãƒ¥ã¨ã‚‚呼ã°ã‚Œã¾ã™) ã¨ã—ã¦å®šç¾©ã•ã‚ŒãŸå¤‰æ•°ã‚’使用ã™ã‚‹å ´åˆã¯ã€æ‹¬å¼§è¡¨è¨˜ã¾ãŸã¯ãƒ‰ãƒƒãƒˆè¡¨è¨˜ã®ã„ãšã‚Œã‹ã‚’使用ã—ã¦ã€ãã®ãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼ã®å€‹ã€…ã®ç‰¹å®šã®ãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ã‚’使用ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:140 +#: ../../rst/user_guide/playbooks_variables.rst:156 msgid "Both of these examples reference the same value (\"one\"). Bracket notation always works. Dot notation can cause problems because some keys collide with attributes and methods of python dictionaries. Use bracket notation if you use keys which start and end with two underscores (which are reserved for special meanings in python) or are any of the known public attributes:" msgstr "ã“れらã®ä¾‹ã§ã¯ã€ã©ã¡ã‚‰ã‚‚åŒã˜å€¤ (「oneã€) ã‚’å‚ç…§ã—ã¦ã„ã¾ã™ã€‚括弧表記ã¯å¸¸ã«æœ‰åŠ¹ã§ã™ã€‚ドット表記ã§ã¯ã€ä¸€éƒ¨ã®ã‚ー㌠python ディクショナリーã®å±žæ€§ã‚„メソッドã¨è¡çªã™ã‚‹ãŸã‚ã€å•é¡ŒãŒç”Ÿã˜ã¾ã™ã€‚2 ã¤ã®ã‚¢ãƒ³ãƒ€ãƒ¼ã‚¹ã‚³ã‚¢ã§å§‹ã¾ã£ã¦çµ‚ã‚ã‚‹ã‚ー (python ã§ã¯ç‰¹åˆ¥ãªæ„味をæŒã¤ã‚‚ã®ã¨ã—ã¦äºˆç´„ã•ã‚Œã¦ã„ã¾ã™) ã‚„ã€æ—¢çŸ¥ã®å…¬é–‹å±žæ€§ã‚’使用ã™ã‚‹å ´åˆã¯ã€æ‹¬å¼§è¡¨è¨˜ã‚’使用ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_variables.rst:142 +#: ../../rst/user_guide/playbooks_variables.rst:158 msgid "``add``, ``append``, ``as_integer_ratio``, ``bit_length``, ``capitalize``, ``center``, ``clear``, ``conjugate``, ``copy``, ``count``, ``decode``, ``denominator``, ``difference``, ``difference_update``, ``discard``, ``encode``, ``endswith``, ``expandtabs``, ``extend``, ``find``, ``format``, ``fromhex``, ``fromkeys``, ``get``, ``has_key``, ``hex``, ``imag``, ``index``, ``insert``, ``intersection``, ``intersection_update``, ``isalnum``, ``isalpha``, ``isdecimal``, ``isdigit``, ``isdisjoint``, ``is_integer``, ``islower``, ``isnumeric``, ``isspace``, ``issubset``, ``issuperset``, ``istitle``, ``isupper``, ``items``, ``iteritems``, ``iterkeys``, ``itervalues``, ``join``, ``keys``, ``ljust``, ``lower``, ``lstrip``, ``numerator``, ``partition``, ``pop``, ``popitem``, ``real``, ``remove``, ``replace``, ``reverse``, ``rfind``, ``rindex``, ``rjust``, ``rpartition``, ``rsplit``, ``rstrip``, ``setdefault``, ``sort``, ``split``, ``splitlines``, ``startswith``, ``strip``, ``swapcase``, ``symmetric_difference``, ``symmetric_difference_update``, ``title``, ``translate``, ``union``, ``update``, ``upper``, ``values``, ``viewitems``, ``viewkeys``, ``viewvalues``, ``zfill``." msgstr "``add``ã€``append``ã€``as_integer_ratio``ã€``bit_length``ã€``capitalize``ã€``center``ã€``clear``ã€``conjugate``ã€``copy``ã€``count``ã€``decode``ã€``denominator``ã€``difference``ã€``difference_update``ã€``discard``ã€``encode``ã€``endswith``ã€``expandtabs``ã€``extend``ã€``find``ã€``format``ã€``fromhex``ã€``fromkeys``ã€``get``ã€``has_key``ã€``hex``ã€``imag``ã€``index``ã€``insert``ã€``intersection``ã€``intersection_update``ã€``isalnum``ã€``isalpha``ã€``isdecimal``ã€``isdigit``ã€``isdisjoint``ã€``is_integer``ã€``islower``ã€``isnumeric``ã€``isspace``ã€``issubset``ã€``issuperset``ã€``istitle``ã€``isupper``ã€``items``ã€``iteritems``ã€``iterkeys``ã€``itervalues``ã€``join``ã€``keys``ã€``ljust``ã€``lower``ã€``lstrip``ã€``numerator``ã€``partition``ã€``pop``ã€``popitem``ã€``real``ã€``remove``ã€``replace``ã€``reverse``ã€``rfind``ã€``rindex``ã€``rjust``ã€``rpartition``ã€``rsplit``ã€``rstrip``ã€``setdefault``ã€``sort``ã€``split``ã€``splitlines``ã€``startswith``ã€``strip``ã€``swapcase``ã€``symmetric_difference``ã€``symmetric_difference_update``ã€``title``ã€``translate``ã€``union``ã€``update``ã€``upper``ã€``values``ã€``viewitems``ã€``viewkeys``ã€``viewvalues``ã€``zfill``" -#: ../../rst/user_guide/playbooks_variables.rst:147 +#: ../../rst/user_guide/playbooks_variables.rst:163 msgid "Registering variables" msgstr "変数ã®ç™»éŒ²" -#: ../../rst/user_guide/playbooks_variables.rst:149 -msgid "You can create variables from the output of an Ansible task with the task keyword ``register``. You can use registered variables in any later tasks in your play. For example::" +#: ../../rst/user_guide/playbooks_variables.rst:165 +msgid "You can create variables from the output of an Ansible task with the task keyword ``register``. You can use registered variables in any later tasks in your play. For example:" msgstr "タスクã‚ーワード ``register`` を使用ã—ã¦ã€Ansible タスクã®å‡ºåŠ›ã‹ã‚‰å¤‰æ•°ã‚’作æˆã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚登録ã—ãŸå¤‰æ•°ã¯ã€ãƒ—レイä¸ã®å¾Œç¶šã®ã‚¿ã‚¹ã‚¯ã§ä½¿ç”¨ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:164 +#: ../../rst/user_guide/playbooks_variables.rst:182 msgid "For more examples of using registered variables in conditions on later tasks, see :ref:`playbooks_conditionals`. Registered variables may be simple variables, list variables, dictionary variables, or complex nested data structures. The documentation for each module includes a ``RETURN`` section describing the return values for that module. To see the values for a particular task, run your playbook with ``-v``." msgstr "登録ã•ã‚ŒãŸå¤‰æ•°ã‚’後ã®ã‚¿ã‚¹ã‚¯ã®æ¡ä»¶ã§ä½¿ç”¨ã™ã‚‹ä¾‹ã¯ã€ã€Œ:ref:`playbooks_conditionals`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。登録ã—ãŸå¤‰æ•°ã«ã¯ã€å˜ç´”ãªå¤‰æ•°ã€ãƒªã‚¹ãƒˆå¤‰æ•°ã€ãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªãƒ¼å¤‰æ•°ã€è¤‡é›‘ã«ãƒã‚¹ãƒˆã—ãŸãƒ‡ãƒ¼ã‚¿æ§‹é€ ãªã©ãŒã‚ã‚Šã¾ã™ã€‚å„モジュールã®ãƒ‰ã‚ュメントã«ã¯ã€ãã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®æˆ»ã‚Šå€¤ã‚’説明ã—㟠``RETURN`` セクションãŒã‚ã‚Šã¾ã™ã€‚特定ã®ã‚¿ã‚¹ã‚¯ã®å€¤ã‚’確èªã™ã‚‹ã«ã¯ã€``-v`` 㧠Playbook を実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:166 +#: ../../rst/user_guide/playbooks_variables.rst:184 msgid "Registered variables are stored in memory. You cannot cache registered variables for use in future plays. Registered variables are only valid on the host for the rest of the current playbook run." msgstr "登録ã•ã‚ŒãŸå¤‰æ•°ã¯ãƒ¡ãƒ¢ãƒªãƒ¼ã«ä¿å˜ã•ã‚Œã¾ã™ã€‚登録ã•ã‚ŒãŸå¤‰æ•°ã‚’å°†æ¥ã®ãƒ—レイã§ä½¿ç”¨ã™ã‚‹ãŸã‚ã«ã‚ャッシュã™ã‚‹ã“ã¨ã¯ã§ãã¾ã›ã‚“。登録ã•ã‚ŒãŸå¤‰æ•°ã¯ã€ç¾åœ¨ã® Playbook ã®æ®‹ã‚Šã®å®Ÿè¡Œä¸ã€ãƒ›ã‚¹ãƒˆä¸Šã§ã®ã¿æœ‰åŠ¹ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:168 +#: ../../rst/user_guide/playbooks_variables.rst:186 msgid "Registered variables are host-level variables. When you register a variable in a task with a loop, the registered variable contains a value for each item in the loop. The data structure placed in the variable during the loop will contain a ``results`` attribute, that is a list of all responses from the module. For a more in-depth example of how this works, see the :ref:`playbooks_loops` section on using register with a loop." msgstr "登録ã•ã‚ŒãŸå¤‰æ•°ã¯ã€ãƒ›ã‚¹ãƒˆãƒ¬ãƒ™ãƒ«ã®å¤‰æ•°ã§ã™ã€‚ループã®ã‚るタスクã§å¤‰æ•°ã‚’登録ã™ã‚‹ã¨ã€ç™»éŒ²ã•ã‚ŒãŸå¤‰æ•°ã«ã¯ãƒ«ãƒ¼ãƒ—内ã®å„é …ç›®ã®å€¤ãŒå…¥ã‚Šã¾ã™ã€‚ループä¸ã«å¤‰æ•°ã«ç½®ã‹ã‚ŒãŸãƒ‡ãƒ¼ã‚¿æ§‹é€ ã«ã¯ã€``results`` 属性ã€ã¤ã¾ã‚Šãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‹ã‚‰ã®å…¨å¿œç”ã®ãƒªã‚¹ãƒˆãŒå«ã¾ã‚Œã¾ã™ã€‚ã“ã®å‹•ä½œã®è©³ç´°ãªä¾‹ã«ã¤ã„ã¦ã¯ã€ãƒ«ãƒ¼ãƒ—ã§ç™»éŒ²ã®ä½¿ç”¨ã«é–¢ã™ã‚‹ã€Œ:ref:`playbooks_loops`ã€ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_variables.rst:170 +#: ../../rst/user_guide/playbooks_variables.rst:188 msgid "If a task fails or is skipped, Ansible still registers a variable with a failure or skipped status, unless the task is skipped based on tags. See :ref:`tags` for information on adding and using tags." msgstr "タスクãŒå¤±æ•—ã¾ãŸã¯ã‚¹ã‚ップã—ã¦ã‚‚ã€ã‚¿ã‚°ã«åŸºã¥ã„ã¦ã‚¿ã‚¹ã‚¯ãŒã‚¹ã‚ップã•ã‚Œã¦ã„ãªã„é™ã‚Šã€Ansible ã¯å¤±æ•—ã¾ãŸã¯ã‚¹ã‚ップã®ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã§å¤‰æ•°ã‚’登録ã—ã¾ã™ã€‚ã‚¿ã‚°ã®è¿½åŠ ãŠã‚ˆã³ä½¿ç”¨ã«é–¢ã™ã‚‹æƒ…å ±ã¯ã€ã€Œ:ref:`tags`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_variables.rst:175 +#: ../../rst/user_guide/playbooks_variables.rst:193 msgid "Referencing nested variables" msgstr "ãƒã‚¹ãƒˆã•ã‚ŒãŸå¤‰æ•°ã®å‚ç…§" -#: ../../rst/user_guide/playbooks_variables.rst:177 -msgid "Many registered variables (and :ref:`facts <vars_and_facts>`) are nested YAML or JSON data structures. You cannot access values from these nested data structures with the simple ``{{ foo }}`` syntax. You must use either bracket notation or dot notation. For example, to reference an IP address from your facts using the bracket notation::" +#: ../../rst/user_guide/playbooks_variables.rst:195 +msgid "Many registered variables (and :ref:`facts <vars_and_facts>`) are nested YAML or JSON data structures. You cannot access values from these nested data structures with the simple ``{{ foo }}`` syntax. You must use either bracket notation or dot notation. For example, to reference an IP address from your facts using the bracket notation:" msgstr "多ãã®ç™»éŒ²ã•ã‚ŒãŸå¤‰æ•° (ãŠã‚ˆã³ :ref:`ファクト <vars_and_facts>`) ã¯ã€ãƒã‚¹ãƒˆã•ã‚ŒãŸ YAML ã¾ãŸã¯ JSON ãƒ‡ãƒ¼ã‚¿æ§‹é€ ã§ã™ã€‚ã“れらã®ãƒã‚¹ãƒˆã—ãŸãƒ‡ãƒ¼ã‚¿æ§‹é€ ã®å€¤ã«ã¯ã€å˜ç´”㪠``{{ foo }}`` ã®æ§‹æ–‡ã§ã¯ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã›ã‚“。括弧表記ã¾ãŸã¯ãƒ‰ãƒƒãƒˆè¡¨è¨˜ã®ã„ãšã‚Œã‹ã‚’使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€æ‹¬å¼§è¡¨è¨˜ã‚’使用ã—ã¦ãƒ•ã‚¡ã‚¯ãƒˆã‹ã‚‰ IP アドレスをå‚ç…§ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:181 -msgid "To reference an IP address from your facts using the dot notation::" +#: ../../rst/user_guide/playbooks_variables.rst:201 +msgid "To reference an IP address from your facts using the dot notation:" msgstr "ドット表記を使用ã—ã¦ãƒ•ã‚¡ã‚¯ãƒˆã‹ã‚‰ IP アドレスをå‚ç…§ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:189 +#: ../../rst/user_guide/playbooks_variables.rst:211 msgid "Transforming variables with Jinja2 filters" msgstr "Jinja2 フィルターを使用ã—ãŸå¤‰æ•°ã®å¤‰æ›" -#: ../../rst/user_guide/playbooks_variables.rst:191 +#: ../../rst/user_guide/playbooks_variables.rst:213 msgid "Jinja2 filters let you transform the value of a variable within a template expression. For example, the ``capitalize`` filter capitalizes any value passed to it; the ``to_yaml`` and ``to_json`` filters change the format of your variable values. Jinja2 includes many `built-in filters <https://jinja.palletsprojects.com/templates/#builtin-filters>`_ and Ansible supplies many more filters. To find more examples of filters, see :ref:`playbooks_filters`." msgstr "Jinja2 ã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ã¯ã€ãƒ†ãƒ³ãƒ—レートå¼å†…ã®å¤‰æ•°ã®å€¤ã‚’変æ›ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€``capitalize`` フィルターã¯ã€æ¸¡ã•ã‚ŒãŸå€¤ã‚’ã™ã¹ã¦å¤§æ–‡å—ã«ã—ã¾ã™ã€‚``to_yaml`` フィルターãŠã‚ˆã³ ``to_json`` フィルターã¯ã€å¤‰æ•°ã®å€¤ã®å½¢å¼ã‚’変更ã—ã¾ã™ã€‚Jinja2 ã«ã¯å¤šãã® `built-in フィルター <https://jinja.palletsprojects.com/templates/#builtin-filters>`_ ãŒã‚ã‚Šã€Ansible ã«ã¯ã•ã‚‰ã«å¤šãã®ãƒ•ã‚£ãƒ«ã‚¿ãƒ¼ãŒç”¨æ„ã•ã‚Œã¦ã„ã¾ã™ã€‚フィルターã®ãã®ä»–ã®ä¾‹ã«ã¤ã„ã¦ã¯ã€ã€Œ:ref:`playbooks_filters`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_variables.rst:196 +#: ../../rst/user_guide/playbooks_variables.rst:218 msgid "Where to set variables" msgstr "変数をè¨å®šã™ã‚‹å ´æ‰€" -#: ../../rst/user_guide/playbooks_variables.rst:198 +#: ../../rst/user_guide/playbooks_variables.rst:220 msgid "You can define variables in a variety of places, such as in inventory, in playbooks, in reusable files, in roles, and at the command line. Ansible loads every possible variable it finds, then chooses the variable to apply based on :ref:`variable precedence rules <ansible_variable_precedence>`." msgstr "変数ã¯ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã€Playbookã€å†åˆ©ç”¨å¯èƒ½ãƒ•ã‚¡ã‚¤ãƒ«ã€ãƒãƒ¼ãƒ«ã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ãªã©ã€ã•ã¾ã–ã¾ãªå ´æ‰€ã§å®šç¾©ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚Ansible ã¯ã€æ¤œå‡ºå¯èƒ½ãªã™ã¹ã¦ã®å¤‰æ•°ã‚’èªã¿è¾¼ã¿ã€:ref:`変数ã®å„ªå…ˆé †ä½ãƒ«ãƒ¼ãƒ« <ansible_variable_precedence>` ã«åŸºã¥ã„ã¦é©ç”¨ã™ã‚‹å¤‰æ•°ã‚’é¸æŠžã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:203 +#: ../../rst/user_guide/playbooks_variables.rst:225 msgid "Defining variables in inventory" msgstr "インベントリーã§ã®å¤‰æ•°ã®å®šç¾©" -#: ../../rst/user_guide/playbooks_variables.rst:205 +#: ../../rst/user_guide/playbooks_variables.rst:227 msgid "You can define different variables for each individual host, or set shared variables for a group of hosts in your inventory. For example, if all machines in the ``[Boston]`` group use 'boston.ntp.example.com' as an NTP server, you can set a group variable. The :ref:`intro_inventory` page has details on setting :ref:`host variables <host_variables>` and :ref:`group variables <group_variables>` in inventory." msgstr "個々ã®ãƒ›ã‚¹ãƒˆã”ã¨ã«ç•°ãªã‚‹å¤‰æ•°ã‚’定義ã—ãŸã‚Šã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼å†…ã®ãƒ›ã‚¹ãƒˆã‚°ãƒ«ãƒ¼ãƒ—ã«å…±æœ‰å¤‰æ•°ã‚’è¨å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€``[Boston]`` グループã®ã™ã¹ã¦ã®ãƒžã‚·ãƒ³ãŒ NTP サーãƒãƒ¼ã¨ã—ã¦ã€Œboston.ntp.example.comã€ã‚’使用ã™ã‚‹å ´åˆã¯ã€ã‚°ãƒ«ãƒ¼ãƒ—変数をè¨å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚「:ref:`intro_inventory`〠ページã«ã¯ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã§ :ref:`host 変数 <host_variables>` ãŠã‚ˆã³ :ref:`group 変数 <group_variables>` ã‚’è¨å®šã™ã‚‹ãŸã‚ã®è©³ç´°ãŒè¨˜è¼‰ã•ã‚Œã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:210 +#: ../../rst/user_guide/playbooks_variables.rst:232 msgid "Defining variables in a play" msgstr "プレイã§ã®å¤‰æ•°ã®å®šç¾©" -#: ../../rst/user_guide/playbooks_variables.rst:212 -msgid "You can define variables directly in a playbook play::" +#: ../../rst/user_guide/playbooks_variables.rst:234 +msgid "You can define variables directly in a playbook play:" msgstr "変数㯠Playbook プレイã§ç›´æŽ¥å®šç¾©ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:218 +#: ../../rst/user_guide/playbooks_variables.rst:242 msgid "When you define variables in a play, they are only visible to tasks executed in that play." msgstr "プレイã§å¤‰æ•°ã‚’定義ã™ã‚‹ã¨ã€ãã®ãƒ—レイã§å®Ÿè¡Œã—ã¦ã„るタスクã§ã®ã¿è¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:224 +#: ../../rst/user_guide/playbooks_variables.rst:248 msgid "Defining variables in included files and roles" msgstr "インクルードファイルãŠã‚ˆã³ãƒãƒ¼ãƒ«ã§ã®å¤‰æ•°ã®å®šç¾©" -#: ../../rst/user_guide/playbooks_variables.rst:226 +#: ../../rst/user_guide/playbooks_variables.rst:250 msgid "You can define variables in reusable variables files and/or in reusable roles. When you define variables in reusable variable files, the sensitive variables are separated from playbooks. This separation enables you to store your playbooks in a source control software and even share the playbooks, without the risk of exposing passwords or other sensitive and personal data. For information about creating reusable files and roles, see :ref:`playbooks_reuse`." msgstr "変数ã¯ã€å†åˆ©ç”¨å¯èƒ½ãªå¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«ã‚„å†åˆ©ç”¨å¯èƒ½ãªãƒãƒ¼ãƒ«ã«å®šç¾©ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚å†åˆ©ç”¨å¯èƒ½ãªå¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«ã«å¤‰æ•°ã‚’定義ã™ã‚‹ã¨ã€æ©Ÿå¯†æ€§ã®é«˜ã„変数㌠Playbook ã‹ã‚‰åˆ†é›¢ã•ã‚Œã¾ã™ã€‚ã“ã®åˆ†é›¢ã«ã‚ˆã‚Šã€ãƒ‘スワードãªã©ã®æ©Ÿå¯†æƒ…å ±ã‚„å€‹äººæƒ…å ±ã‚’æµå‡ºã•ã›ã‚‹ã“ã¨ãªãã€ã‚½ãƒ¼ã‚¹ã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ«ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ã« Playbook ã‚’ä¿å˜ã—ãŸã‚Šã€Playbook を共有ã—ãŸã‚Šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚å†åˆ©ç”¨å¯èƒ½ãªãƒ•ã‚¡ã‚¤ãƒ«ã‚„ãƒãƒ¼ãƒ«ã®ä½œæˆã¯ã€ã€Œ:ref:`playbooks_reuse`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_variables.rst:228 -msgid "This example shows how you can include variables defined in an external file::" +#: ../../rst/user_guide/playbooks_variables.rst:252 +msgid "This example shows how you can include variables defined in an external file:" msgstr "ã“ã®ä¾‹ã¯ã€å¤–部ファイルã§å®šç¾©ã•ã‚ŒãŸå¤‰æ•°ã‚’è¿½åŠ ã™ã‚‹æ–¹æ³•ã‚’示ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:244 -msgid "The contents of each variables file is a simple YAML dictionary. For example::" +#: ../../rst/user_guide/playbooks_variables.rst:270 +msgid "The contents of each variables file is a simple YAML dictionary. For example:" msgstr "å„変数ファイルã®å†…容ã¯ã€å˜ç´”㪠YAML ディクショナリーã§ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:252 +#: ../../rst/user_guide/playbooks_variables.rst:280 msgid "You can keep per-host and per-group variables in similar files. To learn about organizing your variables, see :ref:`splitting_out_vars`." msgstr "ホスト別ãŠã‚ˆã³ã‚°ãƒ«ãƒ¼ãƒ—別ã®å¤‰æ•°ã‚’åŒæ§˜ã®ãƒ•ã‚¡ã‚¤ãƒ«ã«ç¶æŒã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚変数を整ç†ã™ã‚‹æ–¹æ³•ã¯ã€ã€Œ:ref:`splitting_out_vars`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_variables.rst:257 +#: ../../rst/user_guide/playbooks_variables.rst:285 msgid "Defining variables at runtime" msgstr "ランタイム時ã®å¤‰æ•°ã®å®šç¾©" -#: ../../rst/user_guide/playbooks_variables.rst:259 +#: ../../rst/user_guide/playbooks_variables.rst:287 msgid "You can define variables when you run your playbook by passing variables at the command line using the ``--extra-vars`` (or ``-e``) argument. You can also request user input with a ``vars_prompt`` (see :ref:`playbooks_prompts`). When you pass variables at the command line, use a single quoted string, that contains one or more variables, in one of the formats below." msgstr "Playbook ã®å®Ÿè¡Œæ™‚ã«å¤‰æ•°ã‚’定義ã™ã‚‹ã«ã¯ã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã§ ``--extra-vars`` (ã¾ãŸã¯ ``-e``) 引数を使用ã—ã¦å¤‰æ•°ã‚’渡ã—ã¾ã™ã€‚ã¾ãŸã€``vars_prompt`` (:ref:`playbooks_prompts` å‚ç…§) ã§ãƒ¦ãƒ¼ã‚¶ãƒ¼ã®å…¥åŠ›ã‚’è¦æ±‚ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚コマンドラインã§å¤‰æ•°ã‚’渡ã™ã¨ãã¯ã€ä»¥ä¸‹ã®ã„ãšã‚Œã‹ã®å½¢å¼ã§ã€1 ã¤ã¾ãŸã¯è¤‡æ•°ã®å¤‰æ•°ã‚’å«ã‚€ä¸€é‡å¼•ç”¨ç¬¦ã§å›²ã¾ã‚ŒãŸæ–‡å—列を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:262 +#: ../../rst/user_guide/playbooks_variables.rst:290 msgid "key=value format" msgstr "key=value å½¢å¼" -#: ../../rst/user_guide/playbooks_variables.rst:264 +#: ../../rst/user_guide/playbooks_variables.rst:292 msgid "Values passed in using the ``key=value`` syntax are interpreted as strings. Use the JSON format if you need to pass non-string values such as Booleans, integers, floats, lists, and so on." msgstr "``key=value`` 構文を使用ã—ã¦æ¸¡ã•ã‚Œã‚‹å€¤ã¯æ–‡å—列ã¨ã—ã¦è§£é‡ˆã•ã‚Œã¾ã™ã€‚ブール値ã€æ•´æ•°ã€æµ®å‹•å°æ•°ç‚¹ã€ãƒªã‚¹ãƒˆãªã©ã€æ–‡å—列以外ã®å€¤ã‚’渡ã™å¿…è¦ãŒã‚ã‚‹å ´åˆã¯ã€JSON å½¢å¼ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:271 +#: ../../rst/user_guide/playbooks_variables.rst:299 msgid "JSON string format" msgstr "JSON æ–‡å—列ã®å½¢å¼" -#: ../../rst/user_guide/playbooks_variables.rst:278 -msgid "When passing variables with ``--extra-vars``, you must escape quotes and other special characters appropriately for both your markup (for example, JSON), and for your shell::" +#: ../../rst/user_guide/playbooks_variables.rst:306 +msgid "When passing variables with ``--extra-vars``, you must escape quotes and other special characters appropriately for both your markup (for example, JSON), and for your shell:" msgstr "``--extra-vars`` ã§å¤‰æ•°ã‚’渡ã™å ´åˆã«ã¯ã€ãƒžãƒ¼ã‚¯ã‚¢ãƒƒãƒ— (JSON ãªã©) ã¨ã‚·ã‚§ãƒ«ã®ä¸¡æ–¹ã§ã€å¼•ç”¨ç¬¦ã‚„ãã®ä»–ã®ç‰¹æ®Šæ–‡å—ã‚’é©åˆ‡ã«ã‚¨ã‚¹ã‚±ãƒ¼ãƒ—ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:284 +#: ../../rst/user_guide/playbooks_variables.rst:314 msgid "If you have a lot of special characters, use a JSON or YAML file containing the variable definitions." msgstr "特殊文å—ãŒå¤šæ•°ã‚ã‚‹å ´åˆã¯ã€å¤‰æ•°å®šç¾©ã‚’å«ã‚€ JSON ファイルã¾ãŸã¯ YAML ファイルを使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:287 +#: ../../rst/user_guide/playbooks_variables.rst:317 msgid "vars from a JSON or YAML file" msgstr "JSON ファイルã¾ãŸã¯ YAML ファイルã®å¤‰æ•°" -#: ../../rst/user_guide/playbooks_variables.rst:297 +#: ../../rst/user_guide/playbooks_variables.rst:327 msgid "Variable precedence: Where should I put a variable?" msgstr "変数ã®å„ªå…ˆé †ä½: 変数をã©ã“ã«ç½®ãã¹ãã‹" -#: ../../rst/user_guide/playbooks_variables.rst:299 +#: ../../rst/user_guide/playbooks_variables.rst:329 msgid "You can set multiple variables with the same name in many different places. When you do this, Ansible loads every possible variable it finds, then chooses the variable to apply based on variable precedence. In other words, the different variables will override each other in a certain order." msgstr "åŒã˜åå‰ã®è¤‡æ•°ã®å¤‰æ•°ã‚’ã•ã¾ã–ã¾ãªå ´æ‰€ã«è¨å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“れを行ã†ã¨ã€Ansible ã¯æ¤œå‡ºå¯èƒ½ãªã™ã¹ã¦ã®å¤‰æ•°ã‚’èªã¿è¾¼ã¿ã€æ¬¡ã«å¤‰æ•°ã®å„ªå…ˆé †ä½ã«åŸºã¥ã„ã¦é©ç”¨ã™ã‚‹å¤‰æ•°ã‚’é¸æŠžã—ã¾ã™ã€‚ã¤ã¾ã‚Šã€ç•°ãªã‚‹å¤‰æ•°ãŒä¸€å®šã®é †åºã§äº’ã„ã«ä¸Šæ›¸ãã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:301 +#: ../../rst/user_guide/playbooks_variables.rst:331 msgid "Teams and projects that agree on guidelines for defining variables (where to define certain types of variables) usually avoid variable precedence concerns. We suggest that you define each variable in one place: figure out where to define a variable, and keep it simple. For examples, see :ref:`variable_examples`." msgstr "変数ã®å®šç¾©ã«é–¢ã™ã‚‹ã‚¬ã‚¤ãƒ‰ãƒ©ã‚¤ãƒ³ (特定ã®ã‚¿ã‚¤ãƒ—ã®å¤‰æ•°ã‚’ã©ã“ã§å®šç¾©ã™ã‚‹ã‹) ã«åˆæ„ã—ãŸãƒãƒ¼ãƒ やプãƒã‚¸ã‚§ã‚¯ãƒˆã¯ã€é€šå¸¸ã€å¤‰æ•°ã®å„ªå…ˆé †ä½ã«é–¢ã™ã‚‹æ‡¸å¿µã‚’回é¿ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚å„変数ã¯ã€ä¸€ç®‡æ‰€ã§å®šç¾©ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚ã©ã“ã§å¤‰æ•°ã‚’定義ã™ã‚‹ã‹ã‚’把æ¡ã—ã€ç°¡æ½”ã•ã‚’ä¿ã£ã¦ãã ã•ã„。例ã«ã¤ã„ã¦ã¯ã€ã€Œ:ref:`variable_examples`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_variables.rst:303 +#: ../../rst/user_guide/playbooks_variables.rst:333 msgid "Some behavioral parameters that you can set in variables you can also set in Ansible configuration, as command-line options, and using playbook keywords. For example, you can define the user Ansible uses to connect to remote devices as a variable with ``ansible_user``, in a configuration file with ``DEFAULT_REMOTE_USER``, as a command-line option with ``-u``, and with the playbook keyword ``remote_user``. If you define the same parameter in a variable and by another method, the variable overrides the other setting. This approach allows host-specific settings to override more general settings. For examples and more details on the precedence of these various settings, see :ref:`general_precedence_rules`." msgstr "変数ã§è¨å®šã§ãる動作パラメーターã®ä¸ã«ã¯ã€Ansible ã®æ§‹æˆã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã‚ªãƒ—ションã€ãŠã‚ˆã³ Playbook ã‚ーワードã§è¨å®šã§ãã‚‹ã‚‚ã®ãŒã‚ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€Ansible ãŒãƒªãƒ¢ãƒ¼ãƒˆãƒ‡ãƒã‚¤ã‚¹ã¸ã®æŽ¥ç¶šã«ä½¿ç”¨ã™ã‚‹ãƒ¦ãƒ¼ã‚¶ãƒ¼ã¯ã€å¤‰æ•°ã§ã¯ ``ansible_user``ã€æ§‹æˆãƒ•ã‚¡ã‚¤ãƒ«ã§ã¯ ``DEFAULT_REMOTE_USER``ã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã‚ªãƒ—ションã§ã¯ ``-u`` ã€Playbook ã‚ーワードã§ã¯ ``remote_user`` ã§å®šç¾©ã§ãã¾ã™ã€‚変数ã¨åˆ¥ã®æ–¹æ³•ã§åŒã˜ãƒ‘ラメーターを定義ã—ãŸå ´åˆã¯ã€å¤‰æ•°ãŒåˆ¥ã®è¨å®šã‚’上書ãã—ã¾ã™ã€‚ã“ã®æ–¹æ³•ã§ã¯ã€ãƒ›ã‚¹ãƒˆå›ºæœ‰ã®è¨å®šãŒã‚ˆã‚Šä¸€èˆ¬çš„ãªè¨å®šã‚’上書ãã—ã¾ã™ã€‚ã“れらã®ã•ã¾ã–ã¾ãªè¨å®šã®å„ªå…ˆé †ä½ã®ä¾‹ã‚„詳細ã¯ã€ã€Œ:ref:`general_precedence_rules`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_variables.rst:306 +#: ../../rst/user_guide/playbooks_variables.rst:336 msgid "Understanding variable precedence" msgstr "変数ã®å„ªå…ˆé †ä½ã«ã¤ã„ã¦" -#: ../../rst/user_guide/playbooks_variables.rst:308 +#: ../../rst/user_guide/playbooks_variables.rst:338 msgid "Ansible does apply variable precedence, and you might have a use for it. Here is the order of precedence from least to greatest (the last listed variables override all other variables):" msgstr "Ansible ã§ã¯å¤‰æ•°ã®å„ªå…ˆé †ä½ã‚’é©ç”¨ã—ã¦ãŠã‚Šã€ãれを利用ã§ãã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚ã“ã“ã§ã¯ã€å„ªå…ˆé †ä½ã®ä½Žã„ã‚‚ã®ã‹ã‚‰é«˜ã„ã‚‚ã®ã¾ã§ã‚’紹介ã—ã¾ã™ (最後ã«æŒ™ã’ãŸå¤‰æ•°ãŒä»–ã®ã™ã¹ã¦ã®å¤‰æ•°ã‚’上書ãã—ã¾ã™)。" -#: ../../rst/user_guide/playbooks_variables.rst:310 +#: ../../rst/user_guide/playbooks_variables.rst:340 msgid "command line values (for example, ``-u my_user``, these are not variables)" msgstr "コマンドラインã®å€¤ (例: ``-u my_user`` (ã“れらã¯å¤‰æ•°ã§ã¯ã‚ã‚Šã¾ã›ã‚“))" -#: ../../rst/user_guide/playbooks_variables.rst:311 +#: ../../rst/user_guide/playbooks_variables.rst:341 msgid "role defaults (defined in role/defaults/main.yml) [1]_" msgstr "ãƒãƒ¼ãƒ«ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆ(role/defaults/main.yml ã§å®šç¾©) [1]_" -#: ../../rst/user_guide/playbooks_variables.rst:312 +#: ../../rst/user_guide/playbooks_variables.rst:342 msgid "inventory file or script group vars [2]_" msgstr "インベントリーファイルã¾ãŸã¯ã‚¹ã‚¯ãƒªãƒ—トã®ã‚°ãƒ«ãƒ¼ãƒ—変数 [2]_" -#: ../../rst/user_guide/playbooks_variables.rst:313 +#: ../../rst/user_guide/playbooks_variables.rst:343 msgid "inventory group_vars/all [3]_" msgstr "インベントリー group_vars/all [3]_" -#: ../../rst/user_guide/playbooks_variables.rst:314 +#: ../../rst/user_guide/playbooks_variables.rst:344 msgid "playbook group_vars/all [3]_" msgstr "playbook group_vars/all [3]_" -#: ../../rst/user_guide/playbooks_variables.rst:315 +#: ../../rst/user_guide/playbooks_variables.rst:345 msgid "inventory group_vars/* [3]_" msgstr "インベントリー group_vars/* [3]_" -#: ../../rst/user_guide/playbooks_variables.rst:316 +#: ../../rst/user_guide/playbooks_variables.rst:346 msgid "playbook group_vars/* [3]_" msgstr "playbook group_vars/* [3]_" -#: ../../rst/user_guide/playbooks_variables.rst:317 +#: ../../rst/user_guide/playbooks_variables.rst:347 msgid "inventory file or script host vars [2]_" msgstr "インベントリーファイルã¾ãŸã¯ã‚¹ã‚¯ãƒªãƒ—トホスト変数 [2]_" -#: ../../rst/user_guide/playbooks_variables.rst:318 +#: ../../rst/user_guide/playbooks_variables.rst:348 msgid "inventory host_vars/* [3]_" msgstr "インベントリー host_vars/* [3]_" -#: ../../rst/user_guide/playbooks_variables.rst:319 +#: ../../rst/user_guide/playbooks_variables.rst:349 msgid "playbook host_vars/* [3]_" msgstr "playbook host_vars/* [3]_" -#: ../../rst/user_guide/playbooks_variables.rst:320 +#: ../../rst/user_guide/playbooks_variables.rst:350 msgid "host facts / cached set_facts [4]_" msgstr "ホストファクト / ã‚ャッシュ済㿠set_facts [4]_" -#: ../../rst/user_guide/playbooks_variables.rst:321 +#: ../../rst/user_guide/playbooks_variables.rst:351 msgid "play vars" msgstr "プレイ変数" -#: ../../rst/user_guide/playbooks_variables.rst:322 +#: ../../rst/user_guide/playbooks_variables.rst:352 msgid "play vars_prompt" msgstr "play vars_prompt" -#: ../../rst/user_guide/playbooks_variables.rst:323 +#: ../../rst/user_guide/playbooks_variables.rst:353 msgid "play vars_files" msgstr "play vars_files" -#: ../../rst/user_guide/playbooks_variables.rst:324 +#: ../../rst/user_guide/playbooks_variables.rst:354 msgid "role vars (defined in role/vars/main.yml)" msgstr "role 変数 (role/vars/main.yml ã§å®šç¾©)" -#: ../../rst/user_guide/playbooks_variables.rst:325 +#: ../../rst/user_guide/playbooks_variables.rst:355 msgid "block vars (only for tasks in block)" msgstr "ブãƒãƒƒã‚¯å¤‰æ•° (ブãƒãƒƒã‚¯ã®ã‚¿ã‚¹ã‚¯ã«ã®ã¿é©ç”¨)" -#: ../../rst/user_guide/playbooks_variables.rst:326 +#: ../../rst/user_guide/playbooks_variables.rst:356 msgid "task vars (only for the task)" msgstr "タスク変数 (タスク専用)" -#: ../../rst/user_guide/playbooks_variables.rst:327 -#: ../../rst/user_guide/windows_faq.rst:166 +#: ../../rst/user_guide/playbooks_variables.rst:357 +#: ../../rst/user_guide/windows_faq.rst:168 msgid "include_vars" msgstr "include_vars" -#: ../../rst/user_guide/playbooks_variables.rst:328 +#: ../../rst/user_guide/playbooks_variables.rst:358 msgid "set_facts / registered vars" msgstr "set_facts / 登録変数" -#: ../../rst/user_guide/playbooks_variables.rst:329 +#: ../../rst/user_guide/playbooks_variables.rst:359 msgid "role (and include_role) params" msgstr "role (ãŠã‚ˆã³ include_role) パラメーター" -#: ../../rst/user_guide/playbooks_variables.rst:330 +#: ../../rst/user_guide/playbooks_variables.rst:360 msgid "include params" msgstr "include パラメーター" -#: ../../rst/user_guide/playbooks_variables.rst:331 +#: ../../rst/user_guide/playbooks_variables.rst:361 msgid "extra vars (for example, ``-e \"user=my_user\"``)(always win precedence)" msgstr "è¿½åŠ ã®å¤‰æ•° (例: ``-e \"user=my_user\"``)(常ã«å„ªå…ˆã•ã‚Œã¾ã™)" -#: ../../rst/user_guide/playbooks_variables.rst:333 +#: ../../rst/user_guide/playbooks_variables.rst:363 msgid "In general, Ansible gives precedence to variables that were defined more recently, more actively, and with more explicit scope. Variables in the defaults folder inside a role are easily overridden. Anything in the vars directory of the role overrides previous versions of that variable in the namespace. Host and/or inventory variables override role defaults, but explicit includes such as the vars directory or an ``include_vars`` task override inventory variables." msgstr "一般的ã«ã€Ansible ã¯ã€ã‚ˆã‚Šæ–°ã—ãã€ã‚ˆã‚Šç©æ¥µçš„ã«ã€ã‚ˆã‚Šæ˜Žç¢ºãªã‚¹ã‚³ãƒ¼ãƒ—ã§å®šç¾©ã•ã‚ŒãŸå¤‰æ•°ã‚’優先ã—ã¾ã™ã€‚ãƒãƒ¼ãƒ«å†…ã® defaults フォルダーã«ã‚る変数ã¯ç°¡å˜ã«ä¸Šæ›¸ãã•ã‚Œã¾ã™ã€‚ãƒãƒ¼ãƒ«ã® vars ディレクトリーã«ã‚ã‚‹ã‚‚ã®ã¯ã€åå‰ç©ºé–“内ã®ãã®å¤‰æ•°ã®ä»¥å‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’上書ãã—ã¾ã™ã€‚ホストãŠã‚ˆã³/ã¾ãŸã¯ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼å¤‰æ•°ã¯ãƒãƒ¼ãƒ«ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã‚’上書ãã—ã¾ã™ãŒã€vars ディレクトリーや ``include_vars`` タスクãªã©ã®æ˜Žç¤ºçš„ãªã‚¤ãƒ³ã‚¯ãƒ«ãƒ¼ãƒ‰ã¯ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼å¤‰æ•°ã‚’上書ãã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:335 +#: ../../rst/user_guide/playbooks_variables.rst:365 msgid "Ansible merges different variables set in inventory so that more specific settings override more generic settings. For example, ``ansible_ssh_user`` specified as a group_var is overridden by ``ansible_user`` specified as a host_var. For details about the precedence of variables set in inventory, see :ref:`how_we_merge`." msgstr "Ansible ã¯ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã«è¨å®šã—ãŸç•°ãªã‚‹å¤‰æ•°ã‚’マージã—ã¦ã€ã‚ˆã‚Šç‰¹å®šã®è¨å®šãŒã‚ˆã‚Šä¸€èˆ¬çš„ãªè¨å®šã‚’上書ãã™ã‚‹ã‚ˆã†ã«ã—ã¾ã™ã€‚ãŸã¨ãˆã°ã€group_var ã¨ã—ã¦æŒ‡å®šã—㟠``ansible_ssh_user`` ã¯ã€host_var ã¨ã—ã¦æŒ‡å®šã—㟠``ansible_user`` ã«ã‚ˆã‚Šä¸Šæ›¸ãã•ã‚Œã¾ã™ã€‚インベントリーã§è¨å®šã•ã‚ŒãŸå¤‰æ•°ã®å„ªå…ˆé †ä½ã®è©³ç´°ã«ã¤ã„ã¦ã¯ã€ã€Œ:ref:`how_we_merge`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_variables.rst:338 +#: ../../rst/user_guide/playbooks_variables.rst:368 msgid "Footnotes" msgstr "注記" -#: ../../rst/user_guide/playbooks_variables.rst:339 +#: ../../rst/user_guide/playbooks_variables.rst:369 msgid "Tasks in each role see their own role's defaults. Tasks defined outside of a role see the last role's defaults." msgstr "å„ãƒãƒ¼ãƒ«ã®ã‚¿ã‚¹ã‚¯ã«ã¯ã€ãã‚Œãžã‚Œã®ãƒãƒ¼ãƒ«ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚ãƒãƒ¼ãƒ«ã®å¤–ã§å®šç¾©ã•ã‚ŒãŸã‚¿ã‚¹ã‚¯ã«ã¯ã€æœ€å¾Œã®ãƒãƒ¼ãƒ«ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:340 +#: ../../rst/user_guide/playbooks_variables.rst:370 msgid "Variables defined in inventory file or provided by dynamic inventory." msgstr "インベントリーファイルã§å®šç¾©ã•ã‚Œã‚‹å¤‰æ•°ã€ã¾ãŸã¯å‹•çš„インベントリーã§æŒ‡å®šã•ã‚Œã‚‹å¤‰æ•°ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:341 +#: ../../rst/user_guide/playbooks_variables.rst:371 msgid "Includes vars added by 'vars plugins' as well as host_vars and group_vars which are added by the default vars plugin shipped with Ansible." msgstr "「vars プラグインã€ã¨ã€Ansible ã«åŒæ¢±ã•ã‚Œã‚‹ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã® vars プラグインã«ã‚ˆã‚Šè¿½åŠ ã•ã‚Œã‚‹ host_vars ãŠã‚ˆã³ group_vars ãŒå«ã¾ã‚Œã‚‹ã‚¤ãƒ³ã‚¯ãƒ«ãƒ¼ãƒ‰å¤‰æ•°ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:342 +#: ../../rst/user_guide/playbooks_variables.rst:372 msgid "When created with set_facts's cacheable option, variables have the high precedence in the play, but are the same as a host facts precedence when they come from the cache." msgstr "set_facts ã®ã‚ャッシュå¯èƒ½ãªã‚ªãƒ—ションを使用ã—ã¦ä½œæˆã™ã‚‹ã¨ã€å¤‰æ•°ãŒãƒ—レイã«å„ªå…ˆã•ã‚Œã¾ã™ãŒã€ã‚ャッシュã‹ã‚‰ã®ãƒ›ã‚¹ãƒˆã®ãƒ•ã‚¡ã‚¯ãƒˆã¨åŒæ§˜ã«å„ªå…ˆã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:345 +#: ../../rst/user_guide/playbooks_variables.rst:375 msgid "Within any section, redefining a var overrides the previous instance. If multiple groups have the same variable, the last one loaded wins. If you define a variable twice in a play's ``vars:`` section, the second one wins." msgstr "ã©ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã‚‚ã€å¤‰æ•°ã‚’å†å®šç¾©ã™ã‚‹ã¨å‰ã®ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ãŒä¸Šæ›¸ãã•ã‚Œã¾ã™ã€‚複数ã®ã‚°ãƒ«ãƒ¼ãƒ—ãŒåŒã˜å¤‰æ•°ã‚’æŒã£ã¦ã„ã‚‹å ´åˆã¯ã€æœ€å¾Œã«èªã¿è¾¼ã¾ã‚ŒãŸã‚‚ã®ãŒå„ªå…ˆã•ã‚Œã¾ã™ã€‚プレイä¸ã® ``vars:`` ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§å¤‰æ•°ã‚’ 2 回定義ã—ãŸå ´åˆã¯ã€2 回目ã®å¤‰æ•°ãŒå„ªå…ˆã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:348 +#: ../../rst/user_guide/playbooks_variables.rst:378 msgid "The previous describes the default config ``hash_behaviour=replace``, switch to ``merge`` to only partially overwrite." msgstr "以å‰ã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã®è¨å®š ``hash_behaviour=replace`` を説明ã—ã€``merge`` ã«åˆ‡ã‚Šæ›¿ãˆã¦ã‚’部分的ã«ä¸Šæ›¸ãã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:353 +#: ../../rst/user_guide/playbooks_variables.rst:383 msgid "Scoping variables" msgstr "変数ã®ã‚¹ã‚³ãƒ¼ãƒ—è¨å®š" -#: ../../rst/user_guide/playbooks_variables.rst:355 +#: ../../rst/user_guide/playbooks_variables.rst:385 msgid "You can decide where to set a variable based on the scope you want that value to have. Ansible has three main scopes:" msgstr "変数をã©ã“ã«è¨å®šã™ã‚‹ã‹ã¯ã€ãã®å€¤ãŒæŒã¤ã¹ãスコープã«åŸºã¥ã„ã¦æ±ºã‚ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚Ansible ã«ã¯å¤§ãã分ã‘㦠3 ã¤ã®ã‚¹ã‚³ãƒ¼ãƒ—ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:357 +#: ../../rst/user_guide/playbooks_variables.rst:387 msgid "Global: this is set by config, environment variables and the command line" msgstr "ã‚°ãƒãƒ¼ãƒãƒ«: ã“ã‚Œã¯ã€è¨å®šã€ç’°å¢ƒå¤‰æ•°ã€ãŠã‚ˆã³ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã§è¨å®šã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:358 +#: ../../rst/user_guide/playbooks_variables.rst:388 msgid "Play: each play and contained structures, vars entries (vars; vars_files; vars_prompt), role defaults and vars." msgstr "プレイ: å„プレイãŠã‚ˆã³å«ã¾ã‚Œã‚‹æ§‹é€ ã€å¤‰æ•°ã‚¨ãƒ³ãƒˆãƒªãƒ¼ (varsã€vars_filesã€vars_prompt)ã€ãƒãƒ¼ãƒ«ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã€ãŠã‚ˆã³å¤‰æ•°" -#: ../../rst/user_guide/playbooks_variables.rst:359 +#: ../../rst/user_guide/playbooks_variables.rst:389 msgid "Host: variables directly associated to a host, like inventory, include_vars, facts or registered task outputs" msgstr "ホスト: インベントリーã€include_varsã€ãƒ•ã‚¡ã‚¯ãƒˆã€ã¾ãŸã¯ç™»éŒ²ã•ã‚ŒãŸã‚¿ã‚¹ã‚¯ã®å‡ºåŠ›ãªã©ã®ãƒ›ã‚¹ãƒˆã«ç›´æŽ¥é–¢é€£ä»˜ã‘られる変数" -#: ../../rst/user_guide/playbooks_variables.rst:361 +#: ../../rst/user_guide/playbooks_variables.rst:391 msgid "Inside a template, you automatically have access to all variables that are in scope for a host, plus any registered variables, facts, and magic variables." msgstr "テンプレート内ã§ã¯ã€ãƒ›ã‚¹ãƒˆã®ã‚¹ã‚³ãƒ¼ãƒ—内ã«ã‚ã‚‹ã™ã¹ã¦ã®å¤‰æ•°ã¨ã€ç™»éŒ²æ¸ˆã¿ã®å¤‰æ•°ã€ãƒ•ã‚¡ã‚¯ãƒˆã€ãŠã‚ˆã³ãƒžã‚¸ãƒƒã‚¯å¤‰æ•°ã«è‡ªå‹•çš„ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:366 +#: ../../rst/user_guide/playbooks_variables.rst:396 msgid "Tips on where to set variables" msgstr "変数をè¨å®šã™ã‚‹å ´æ‰€ã«é–¢ã™ã‚‹ãƒ’ント" -#: ../../rst/user_guide/playbooks_variables.rst:368 +#: ../../rst/user_guide/playbooks_variables.rst:398 msgid "You should choose where to define a variable based on the kind of control you might want over values." msgstr "変数を定義ã™ã‚‹å ´æ‰€ã¯ã€å€¤ã‚’ã©ã®ã‚ˆã†ã«åˆ¶å¾¡ã™ã‚‹ã‹ã«ã‚ˆã£ã¦é¸æŠžã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:370 +#: ../../rst/user_guide/playbooks_variables.rst:400 msgid "Set variables in inventory that deal with geography or behavior. Since groups are frequently the entity that maps roles onto hosts, you can often set variables on the group instead of defining them on a role. Remember: child groups override parent groups, and host variables override group variables. See :ref:`define_variables_in_inventory` for details on setting host and group variables." msgstr "地ç†ã‚„動作を扱ã†ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã«å¤‰æ•°ã‚’è¨å®šã—ã¾ã™ã€‚グループã¯ã€ãƒ›ã‚¹ãƒˆã«ãƒãƒ¼ãƒ«ã‚’マッピングã™ã‚‹ã‚¨ãƒ³ãƒ†ã‚£ãƒ†ã‚£ãƒ¼ã§ã‚ã‚‹ã“ã¨ãŒå¤šã„ãŸã‚ã€ãƒãƒ¼ãƒ«ã«å¤‰æ•°ã‚’定義ã™ã‚‹ä»£ã‚ã‚Šã«ã€ã‚°ãƒ«ãƒ¼ãƒ—ã«å¤‰æ•°ã‚’è¨å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚åグループãŒè¦ªã‚°ãƒ«ãƒ¼ãƒ—を上書ãã—ã€ãƒ›ã‚¹ãƒˆå¤‰æ•°ãŒã‚°ãƒ«ãƒ¼ãƒ—変数を上書ãã™ã‚‹ã“ã¨ã‚’忘れãªã„ã§ãã ã•ã„。ホスト変数ã¨ã‚°ãƒ«ãƒ¼ãƒ—変数ã®è¨å®šã®è©³ç´°ã¯ã€ã€Œ:ref:`define_variables_in_inventory`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_variables.rst:372 -msgid "Set common defaults in a ``group_vars/all`` file. See :ref:`splitting_out_vars` for details on how to organize host and group variables in your inventory. Group variables are generally placed alongside your inventory file, but they can also be returned by dynamic inventory (see :ref:`intro_dynamic_inventory`) or defined in AWX or on :ref:`ansible_platform` from the UI or API::" +#: ../../rst/user_guide/playbooks_variables.rst:402 +msgid "Set common defaults in a ``group_vars/all`` file. See :ref:`splitting_out_vars` for details on how to organize host and group variables in your inventory. Group variables are generally placed alongside your inventory file, but they can also be returned by dynamic inventory (see :ref:`intro_dynamic_inventory`) or defined in AWX or on :ref:`ansible_platform` from the UI or API:" msgstr "``group_vars/all`` ファイルã§å…±é€šã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã‚’è¨å®šã—ã¾ã™ã€‚インベントリーã§ãƒ›ã‚¹ãƒˆå¤‰æ•°ã¨ã‚°ãƒ«ãƒ¼ãƒ—変数を整ç†ã™ã‚‹æ–¹æ³•ã®è©³ç´°ã«ã¤ã„ã¦ã¯ã€ã€Œ:ref:`splitting_out_vars`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。グループ変数ã¯é€šå¸¸ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ•ã‚¡ã‚¤ãƒ«ã¨ä¸€ç·’ã«ç½®ã‹ã‚Œã¾ã™ãŒã€å‹•çš„インベントリー (:ref:`intro_dynamic_inventory` ã‚’å‚ç…§) ã§è¿”ã•ã‚ŒãŸã‚Šã€AWXã€ã¾ãŸã¯ UI ã‚„ API ã‹ã‚‰ :ref:`ansible_platform` ã§å®šç¾©ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:379 -msgid "Set location-specific variables in ``group_vars/my_location`` files. All groups are children of the ``all`` group, so variables set here override those set in ``group_vars/all``::" +#: ../../rst/user_guide/playbooks_variables.rst:411 +msgid "Set location-specific variables in ``group_vars/my_location`` files. All groups are children of the ``all`` group, so variables set here override those set in ``group_vars/all``:" msgstr "``group_vars/my_location`` ファイルã«ãƒã‚±ãƒ¼ã‚·ãƒ§ãƒ³å›ºæœ‰ã®å¤‰æ•°ã‚’è¨å®šã—ã¾ã™ã€‚ã™ã¹ã¦ã®ã‚°ãƒ«ãƒ¼ãƒ—㯠``all`` グループã®åã§ã‚ã‚‹ãŸã‚ã€ã“ã“ã«è¨å®šã•ã‚Œã‚‹å¤‰æ•°ã¯ ``group_vars/all`` ã§è¨å®šã—ãŸå¤‰æ•°ã‚’上書ãã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:385 -msgid "If one host used a different NTP server, you could set that in a host_vars file, which would override the group variable::" +#: ../../rst/user_guide/playbooks_variables.rst:419 +msgid "If one host used a different NTP server, you could set that in a host_vars file, which would override the group variable:" msgstr "1 ã¤ã®ãƒ›ã‚¹ãƒˆãŒåˆ¥ã® NTP サーãƒãƒ¼ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€host_vars ファイルã«ãã®ãƒ›ã‚¹ãƒˆã‚’è¨å®šã§ãã¾ã™ã€‚ã“ã‚Œã«ã‚ˆã‚Šã€ã‚°ãƒ«ãƒ¼ãƒ—変数ãŒä¸Šæ›¸ãã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:391 -msgid "Set defaults in roles to avoid undefined-variable errors. If you share your roles, other users can rely on the reasonable defaults you added in the ``roles/x/defaults/main.yml`` file, or they can easily override those values in inventory or at the command line. See :ref:`playbooks_reuse_roles` for more info. For example::" +#: ../../rst/user_guide/playbooks_variables.rst:427 +msgid "Set defaults in roles to avoid undefined-variable errors. If you share your roles, other users can rely on the reasonable defaults you added in the ``roles/x/defaults/main.yml`` file, or they can easily override those values in inventory or at the command line. See :ref:`playbooks_reuse_roles` for more info. For example:" msgstr "未定義ãªå¤‰æ•°ã‚¨ãƒ©ãƒ¼ã‚’防ããŸã‚ã«ã€ãƒãƒ¼ãƒ«ã«ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã‚’è¨å®šã—ã¾ã™ã€‚ãƒãƒ¼ãƒ«ã‚’共有ã—ã¦ã„ã‚‹å ´åˆã€ä»–ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã¯ã€``roles/x/defaults/main.yml`` ファイルã§è¿½åŠ ã—ãŸå¦¥å½“ãªãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã‚’ä¿¡é ¼ã™ã‚‹ã‹ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‚„コマンドラインã§ç°¡å˜ã«ãã®å€¤ã‚’上書ãã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚詳細ã¯ã€ã€Œ:ref:`playbooks_reuse_roles`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:398 -msgid "Set variables in roles to ensure a value is used in that role, and is not overridden by inventory variables. If you are not sharing your role with others, you can define app-specific behaviors like ports this way, in ``roles/x/vars/main.yml``. If you are sharing roles with others, putting variables here makes them harder to override, although they still can by passing a parameter to the role or setting a variable with ``-e``::" +#: ../../rst/user_guide/playbooks_variables.rst:436 +msgid "Set variables in roles to ensure a value is used in that role, and is not overridden by inventory variables. If you are not sharing your role with others, you can define app-specific behaviors like ports this way, in ``roles/x/vars/main.yml``. If you are sharing roles with others, putting variables here makes them harder to override, although they still can by passing a parameter to the role or setting a variable with ``-e``:" msgstr "ãƒãƒ¼ãƒ«ã«å¤‰æ•°ã‚’è¨å®šã™ã‚‹ã“ã¨ã§ã€å€¤ãŒãã®ãƒãƒ¼ãƒ«ã§ä½¿ç”¨ã•ã‚Œã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼å¤‰æ•°ã§ä¸Šæ›¸ãã•ã‚Œãªã„よã†ã«ã—ã¾ã™ã€‚ãƒãƒ¼ãƒ«ã‚’ä»–ã®äººã¨å…±æœ‰ã—ã¦ã„ãªã„å ´åˆã¯ã€ãƒãƒ¼ãƒˆãªã©ã®ã‚¢ãƒ—リ固有ã®å‹•ä½œã‚’ã€ã“ã®ã‚ˆã†ã« ``roles/x/vars/main.yml`` ã§å®šç¾©ã§ãã¾ã™ã€‚ä»–ã®äººã¨ãƒãƒ¼ãƒ«ã‚’共有ã—ã¦ã„ã‚‹å ´åˆã¯ã€ã“ã“ã«å¤‰æ•°ã‚’ç½®ãã“ã¨ã§ä¸Šæ›¸ãã•ã‚Œã«ãããªã‚Šã¾ã™ã€‚ãŸã ã—ã€ãƒãƒ¼ãƒ«ã«ãƒ‘ラメーターを渡ã—ãŸã‚Šã€``-e`` ã§å¤‰æ•°ã‚’è¨å®šã—ãŸã‚Šã™ã‚Œã°ã€ä¸Šæ›¸ãã•ã‚Œã‚‹å¯èƒ½æ€§ã¯ã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:405 -msgid "Pass variables as parameters when you call roles for maximum clarity, flexibility, and visibility. This approach overrides any defaults that exist for a role. For example::" +#: ../../rst/user_guide/playbooks_variables.rst:445 +msgid "Pass variables as parameters when you call roles for maximum clarity, flexibility, and visibility. This approach overrides any defaults that exist for a role. For example:" msgstr "明確ã•ã€æŸ”軟性ã€ãŠã‚ˆã³å¯è¦–性を最大化ã™ã‚‹ãŸã‚ã«ãƒãƒ¼ãƒ«ã‚’呼ã³å‡ºã™å ´åˆã¯ã€ãƒ‘ラメーターã¨ã—ã¦å¤‰æ•°ã‚’渡ã—ã¾ã™ã€‚ã“ã®æ–¹æ³•ã§ã¯ã€ãƒãƒ¼ãƒ«ã«å˜åœ¨ã™ã‚‹ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã‚’上書ãã—ã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:412 -msgid "When you read this playbook it is clear that you have chosen to set a variable or override a default. You can also pass multiple values, which allows you to run the same role multiple times. See :ref:`run_role_twice` for more details. For example::" +#: ../../rst/user_guide/playbooks_variables.rst:454 +msgid "When you read this playbook it is clear that you have chosen to set a variable or override a default. You can also pass multiple values, which allows you to run the same role multiple times. See :ref:`run_role_twice` for more details. For example:" msgstr "ã“ã® Playbook ã‚’èªã‚€ã¨ã€å¤‰æ•°ã®è¨å®šã‚„デフォルトã®ä¸Šæ›¸ãã‚’é¸æŠžã—ãŸã“ã¨ãŒã‚ã‹ã‚Šã¾ã™ã€‚ã¾ãŸã€è¤‡æ•°ã®å€¤ã‚’渡ã™ã“ã¨ãŒã§ãã‚‹ãŸã‚ã€åŒã˜ãƒãƒ¼ãƒ«ã‚’複数回実行ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚詳細ã¯ã€Œ:ref:`run_role_twice`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:428 -msgid "Variables set in one role are available to later roles. You can set variables in a ``roles/common_settings/vars/main.yml`` file and use them in other roles and elsewhere in your playbook::" +#: ../../rst/user_guide/playbooks_variables.rst:472 +msgid "Variables set in one role are available to later roles. You can set variables in a ``roles/common_settings/vars/main.yml`` file and use them in other roles and elsewhere in your playbook:" msgstr "1 ã¤ã®ãƒãƒ¼ãƒ«ã«è¨å®šã•ã‚ŒãŸå¤‰æ•°ã¯ã€å¾Œã®ãƒãƒ¼ãƒ«ã§ä½¿ç”¨ã§ãã¾ã™ã€‚変数ã¯ã€``roles/common_settings/vars/main.yml`` ファイルã«è¨å®šã—ã¦ã€ä»–ã®ãƒãƒ¼ãƒ«ã‚„ Playbook ã®ä»–ã®å ´æ‰€ã§ä½¿ç”¨ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:437 +#: ../../rst/user_guide/playbooks_variables.rst:483 msgid "There are some protections in place to avoid the need to namespace variables. In this example, variables defined in 'common_settings' are available to 'something' and 'something_else' tasks, but tasks in 'something' have foo set at 12, even if 'common_settings' sets foo to 20." msgstr "変数ã®åå‰ç©ºé–“化ã®å¿…è¦æ€§ã‚’回é¿ã™ã‚‹ãŸã‚ã«ã€ã„ãã¤ã‹ã®ä¿è·æ©Ÿèƒ½ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®ä¾‹ã§ã¯ã€ã€Œcommon_settingsã€ã§å®šç¾©ã•ã‚ŒãŸå¤‰æ•°ã¯ã€Œsomethingã€ã¨ã€Œsomething_elseã€ã®ã‚¿ã‚¹ã‚¯ã§ä½¿ç”¨ã§ãã¾ã™ãŒã€ã€Œcommon_settingsã€ã§ foo ㌠20 ã«è¨å®šã•ã‚Œã¦ã„ã¦ã‚‚ã€ã€Œsomethingã€ã®ã‚¿ã‚¹ã‚¯ã§ã¯ foo ㌠12 ã«è¨å®šã•ã‚Œã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:440 +#: ../../rst/user_guide/playbooks_variables.rst:486 msgid "Instead of worrying about variable precedence, we encourage you to think about how easily or how often you want to override a variable when deciding where to set it. If you are not sure what other variables are defined, and you need a particular value, use ``--extra-vars`` (``-e``) to override all other variables." msgstr "変数ã®å„ªå…ˆé †ä½ã‚’æ°—ã«ã™ã‚‹ã®ã§ã¯ãªãã€å¤‰æ•°ã‚’ã©ã“ã«è¨å®šã™ã‚‹ã‹ã‚’決ã‚ã‚‹éš›ã«ã¯ã€ã©ã‚Œã ã‘ç°¡å˜ã«ã€ã‚ã‚‹ã„ã¯ã©ã‚Œã ã‘é »ç¹ã«å¤‰æ•°ã‚’上書ãã—ãŸã„ã‹ã‚’考ãˆã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚ä»–ã®å¤‰æ•°ãŒã©ã®ã‚ˆã†ã«å®šç¾©ã•ã‚Œã¦ã„ã‚‹ã‹ã‚ã‹ã‚‰ãšã€ç‰¹å®šã®å€¤ãŒå¿…è¦ãªå ´åˆã¯ã€``--extra-vars`` (``-e``) を使用ã—ã¦ã€ä»–ã®ã™ã¹ã¦ã®å¤‰æ•°ã‚’上書ãã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_variables.rst:443 +#: ../../rst/user_guide/playbooks_variables.rst:489 msgid "Using advanced variable syntax" msgstr "高度ãªå¤‰æ•°æ§‹æ–‡ã®ä½¿ç”¨" -#: ../../rst/user_guide/playbooks_variables.rst:445 +#: ../../rst/user_guide/playbooks_variables.rst:491 msgid "For information about advanced YAML syntax used to declare variables and have more control over the data placed in YAML files used by Ansible, see :ref:`playbooks_advanced_syntax`." msgstr "変数を宣言ã™ã‚‹ã®ã«ä½¿ç”¨ã•ã‚Œã‚‹é«˜åº¦ãª YAML 構文ã€ãŠã‚ˆã³ Ansible ã«ã‚ˆã‚Šä½¿ç”¨ã•ã‚Œã‚‹ YAML ファイルã«ã‚るデータã«å¯¾ã™ã‚‹åˆ¶å¾¡ã®è©³ç´°ã¯ã€ã€Œ:ref:`playbooks_advanced_syntax`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_variables.rst:454 +#: ../../rst/user_guide/playbooks_variables.rst:500 msgid "Jinja2 filters and their uses" msgstr "Jinja2 フィルターãŠã‚ˆã³ãã®ä½¿ç”¨" -#: ../../rst/user_guide/playbooks_variables.rst:461 +#: ../../rst/user_guide/playbooks_variables.rst:507 msgid ":ref:`special_variables`" msgstr ":ref:`special_variables`" -#: ../../rst/user_guide/playbooks_variables.rst:462 +#: ../../rst/user_guide/playbooks_variables.rst:508 msgid "List of special variables" msgstr "特殊ãªå¤‰æ•°ã®ãƒªã‚¹ãƒˆ" @@ -10805,228 +10812,228 @@ msgid "Ansible facts" msgstr "Ansible ファクト" #: ../../rst/user_guide/playbooks_vars_facts.rst:15 -msgid "Ansible facts are data related to your remote systems, including operating systems, IP addresses, attached filesystems, and more. You can access this data in the ``ansible_facts`` variable. By default, you can also access some Ansible facts as top-level variables with the ``ansible_`` prefix. You can disable this behavior using the :ref:`INJECT_FACTS_AS_VARS` setting. To see all available facts, add this task to a play::" +msgid "Ansible facts are data related to your remote systems, including operating systems, IP addresses, attached filesystems, and more. You can access this data in the ``ansible_facts`` variable. By default, you can also access some Ansible facts as top-level variables with the ``ansible_`` prefix. You can disable this behavior using the :ref:`INJECT_FACTS_AS_VARS` setting. To see all available facts, add this task to a play:" msgstr "Ansible ã®ãƒ•ã‚¡ã‚¯ãƒˆã¯ã€ã‚ªãƒšãƒ¬ãƒ¼ãƒ†ã‚£ãƒ³ã‚°ã‚·ã‚¹ãƒ†ãƒ ã€IP アドレスã€æ·»ä»˜ã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚·ã‚¹ãƒ†ãƒ ãªã©ã€ãƒªãƒ¢ãƒ¼ãƒˆã‚·ã‚¹ãƒ†ãƒ ã«é–¢é€£ã™ã‚‹ãƒ‡ãƒ¼ã‚¿ã§ã™ã€‚ã“ã®ãƒ‡ãƒ¼ã‚¿ã«ã¯ã€``ansible_facts`` ã¨ã„ã†å¤‰æ•°ã§ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã™ã€‚デフォルトã§ã¯ã€ä¸€éƒ¨ã® Ansible ファクトã¯ã€``ansible_`` ã¨ã„ã†ãƒ—レフィックスをæŒã¤ãƒˆãƒƒãƒ—レベルã®å¤‰æ•°ã¨ã—ã¦ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚ã“ã®å‹•ä½œã¯ã€:ref:`INJECT_FACTS_AS_VARS` ã®è¨å®šã§ç„¡åŠ¹ã«ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚利用å¯èƒ½ãªã™ã¹ã¦ã®ãƒ•ã‚¡ã‚¯ãƒˆã‚’表示ã™ã‚‹ã«ã¯ã€ã“ã®ã‚¿ã‚¹ã‚¯ã‚’プレイã«è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:21 -msgid "To see the 'raw' information as gathered, run this command at the command line::" +#: ../../rst/user_guide/playbooks_vars_facts.rst:23 +msgid "To see the 'raw' information as gathered, run this command at the command line:" msgstr "åŽé›†ã•ã‚ŒãŸã€Œç”Ÿã€ã®æƒ…å ±ã‚’è¦‹ã‚‹ã«ã¯ã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã§æ¬¡ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:25 +#: ../../rst/user_guide/playbooks_vars_facts.rst:29 msgid "Facts include a large amount of variable data, which may look like this:" msgstr "ファクトã«ã¯å¤§é‡ã®å¤‰æ•°ãƒ‡ãƒ¼ã‚¿ãŒå«ã¾ã‚Œã¦ãŠã‚Šã€ãã‚Œã¯æ¬¡ã®ã‚ˆã†ãªã‚‚ã®ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:486 -msgid "You can reference the model of the first disk in the facts shown above in a template or playbook as::" +#: ../../rst/user_guide/playbooks_vars_facts.rst:490 +msgid "You can reference the model of the first disk in the facts shown above in a template or playbook as:" msgstr "上記ã®ãƒ•ã‚¡ã‚¯ãƒˆã®æœ€åˆã®ãƒ‡ã‚£ã‚¹ã‚¯ã®ãƒ¢ãƒ‡ãƒ«ã‚’テンプレートã¾ãŸã¯ Playbook ã§å‚ç…§ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:490 -msgid "To reference the system hostname::" +#: ../../rst/user_guide/playbooks_vars_facts.rst:496 +msgid "To reference the system hostname:" msgstr "システムã®ãƒ›ã‚¹ãƒˆåã‚’å‚ç…§ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:494 +#: ../../rst/user_guide/playbooks_vars_facts.rst:502 msgid "You can use facts in conditionals (see :ref:`playbooks_conditionals`) and also in templates. You can also use facts to create dynamic groups of hosts that match particular criteria, see the :ref:`group_by module <group_by_module>` documentation for details." msgstr "ファクトã¯ã€æ¡ä»¶å¼ (:ref:`playbooks_conditionals` ã‚’å‚ç…§) やテンプレートã§ã‚‚使用ã§ãã¾ã™ã€‚ã¾ãŸã€ãƒ•ã‚¡ã‚¯ãƒˆã‚’使用ã—ã¦ã€ç‰¹å®šã®æ¡ä»¶ã«ä¸€è‡´ã™ã‚‹ãƒ›ã‚¹ãƒˆã®å‹•çš„ãªã‚°ãƒ«ãƒ¼ãƒ—を作æˆã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚詳細ã¯ã€:ref:`group_by モジュール <group_by_module>` ã®ãƒ‰ã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_vars_facts.rst:496 +#: ../../rst/user_guide/playbooks_vars_facts.rst:504 #, python-format msgid "Because ``ansible_date_time`` is created and cached when Ansible gathers facts before each playbook run, it can get stale with long-running playbooks. If your playbook takes a long time to run, use the ``pipe`` filter (for example, ``lookup('pipe', 'date +%Y-%m-%d.%H:%M:%S')``) or :ref:`now() <templating_now>` with a Jinja 2 template instead of ``ansible_date_time``." msgstr "``ansible_date_time`` ã¯ã€Ansible ãŒå„ Playbook ã®å®Ÿè¡Œå‰ã«ãƒ•ã‚¡ã‚¯ãƒˆã‚’åŽé›†ã—ãŸã¨ãã«ã‚ャッシュã•ã‚Œã‚‹ãŸã‚ã€é•·æ™‚間実行ã•ã‚Œã‚‹ Playbook ã§å¤ããªã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚Playbook ã®å®Ÿè¡Œã«é•·ã„時間ãŒã‹ã‹ã‚‹å ´åˆã¯ã€``ansible_date_time`` ã§ã¯ãªã Jinja 2 テンプレート㧠``pipe`` フィルター（例: ``lookup('pipe', 'date +%Y-%m-%d.%H:%M:%S')``）ã¾ãŸã¯ :ref:`now() <templating_now>` を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:501 +#: ../../rst/user_guide/playbooks_vars_facts.rst:509 msgid "Package requirements for fact gathering" msgstr "ファクトåŽé›†ã®ãƒ‘ッケージè¦ä»¶" -#: ../../rst/user_guide/playbooks_vars_facts.rst:503 +#: ../../rst/user_guide/playbooks_vars_facts.rst:511 msgid "On some distros, you may see missing fact values or facts set to default values because the packages that support gathering those facts are not installed by default. You can install the necessary packages on your remote hosts using the OS package manager. Known dependencies include:" msgstr "一部ã®ãƒ‡ã‚£ã‚¹ãƒˆãƒªãƒ“ューションã§ã¯ã€ãƒ•ã‚¡ã‚¯ãƒˆã®åŽé›†ã‚’サãƒãƒ¼ãƒˆã™ã‚‹ãƒ‘ッケージãŒãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ãŸã‚ã€ãƒ•ã‚¡ã‚¯ãƒˆã®å€¤ãŒè¦‹ã¤ã‹ã‚‰ãªã‹ã£ãŸã‚Šã€ãƒ•ã‚¡ã‚¯ãƒˆãŒãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã«è¨å®šã•ã‚ŒãŸã‚Šã™ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚OS ã®ãƒ‘ッケージマãƒãƒ¼ã‚¸ãƒ£ãƒ¼ã‚’使用ã—ã¦ã€ãƒªãƒ¢ãƒ¼ãƒˆãƒ›ã‚¹ãƒˆã«å¿…è¦ãªãƒ‘ッケージをインストールã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚既知ã®ä¾å˜é–¢ä¿‚ã«ã¯ä»¥ä¸‹ã®ã‚‚ã®ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:505 +#: ../../rst/user_guide/playbooks_vars_facts.rst:513 msgid "Linux Network fact gathering - Depends on the ``ip`` binary, commonly included in the ``iproute2`` package." msgstr "Linux ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ•ã‚¡ã‚¯ãƒˆåŽé›† - 一般的㫠``iproute2`` パッケージã«å«ã¾ã‚Œã‚‹ ``ip`` ãƒã‚¤ãƒŠãƒªãƒ¼ã«ã‚ˆã£ã¦ç•°ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:510 +#: ../../rst/user_guide/playbooks_vars_facts.rst:518 msgid "Caching facts" msgstr "ファクトã®ã‚ャッシュ" -#: ../../rst/user_guide/playbooks_vars_facts.rst:512 -msgid "Like registered variables, facts are stored in memory by default. However, unlike registered variables, facts can be gathered independently and cached for repeated use. With cached facts, you can refer to facts from one system when configuring a second system, even if Ansible executes the current play on the second system first. For example::" +#: ../../rst/user_guide/playbooks_vars_facts.rst:520 +msgid "Like registered variables, facts are stored in memory by default. However, unlike registered variables, facts can be gathered independently and cached for repeated use. With cached facts, you can refer to facts from one system when configuring a second system, even if Ansible executes the current play on the second system first. For example:" msgstr "登録ã•ã‚ŒãŸå¤‰æ•°ã¨åŒæ§˜ã«ã€ãƒ•ã‚¡ã‚¯ãƒˆã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ãƒ¡ãƒ¢ãƒªãƒ¼ã«ä¿å˜ã•ã‚Œã¾ã™ã€‚ãŸã ã—ã€ç™»éŒ²ã•ã‚ŒãŸå¤‰æ•°ã¨ã¯ç•°ãªã‚Šã€ãƒ•ã‚¡ã‚¯ãƒˆã¯ç‹¬ç«‹ã—ã¦åŽé›†ã—ã€ç¹°ã‚Šè¿”ã—使用ã™ã‚‹ãŸã‚ã«ã‚ャッシュã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã‚ャッシュã•ã‚ŒãŸãƒ•ã‚¡ã‚¯ãƒˆã‚’使用ã™ã‚‹ã¨ã€Ansible ㌠2 ã¤ç›®ã®ã‚·ã‚¹ãƒ†ãƒ ã§ç¾åœ¨ã®ãƒ—レイを最åˆã«å®Ÿè¡Œã—ãŸå ´åˆã§ã‚‚ã€1 ã¤ã®ã‚·ã‚¹ãƒ†ãƒ ã®ãƒ•ã‚¡ã‚¯ãƒˆã‚’å‚ç…§ã—㦠2 ã¤ç›®ã®ã‚·ã‚¹ãƒ†ãƒ ã‚’è¨å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:516 +#: ../../rst/user_guide/playbooks_vars_facts.rst:526 msgid "Caching is controlled by the cache plugins. By default, Ansible uses the memory cache plugin, which stores facts in memory for the duration of the current playbook run. To retain Ansible facts for repeated use, select a different cache plugin. See :ref:`cache_plugins` for details." msgstr "ã‚ャッシュ処ç†ã¯ã€ã‚ャッシュプラグインã«ã‚ˆã£ã¦åˆ¶å¾¡ã•ã‚Œã¾ã™ã€‚デフォルトã§ã¯ã€Ansible ã¯ãƒ¡ãƒ¢ãƒªãƒ¼ã‚ャッシュプラグインを使用ã—ã€ç¾åœ¨ã® Playbook ã®å®Ÿè¡ŒæœŸé–“ä¸ã€ãƒ¡ãƒ¢ãƒªãƒ¼ã«ãƒ•ã‚¡ã‚¯ãƒˆã‚’ä¿å˜ã—ã¾ã™ã€‚Ansible ã®ãƒ•ã‚¡ã‚¯ãƒˆã‚’ç¹°ã‚Šè¿”ã—使用ã™ã‚‹ãŸã‚ã«ä¿æŒã™ã‚‹ã«ã¯ã€åˆ¥ã®ã‚ャッシュプラグインをé¸æŠžã—ã¾ã™ã€‚詳細ã¯ã€Œ:ref:`cache_plugins`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_vars_facts.rst:518 +#: ../../rst/user_guide/playbooks_vars_facts.rst:528 msgid "Fact caching can improve performance. If you manage thousands of hosts, you can configure fact caching to run nightly, then manage configuration on a smaller set of servers periodically throughout the day. With cached facts, you have access to variables and information about all hosts even when you are only managing a small number of servers." msgstr "ファクトã‚ャッシュ処ç†ã¯ãƒ‘フォーマンスをå‘上ã•ã›ã¾ã™ã€‚何åƒå°ã‚‚ã®ãƒ›ã‚¹ãƒˆã‚’管ç†ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒ•ã‚¡ã‚¯ãƒˆã‚ャッシュ処ç†ã‚’毎晩実行ã™ã‚‹ã‚ˆã†ã«è¨å®šã—ã€å°è¦æ¨¡ãªã‚µãƒ¼ãƒç¾¤ã®è¨å®šã‚’ 1 æ—¥ä¸å®šæœŸçš„ã«ç®¡ç†ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã‚ャッシュã•ã‚ŒãŸãƒ•ã‚¡ã‚¯ãƒˆãŒã‚ã‚Œã°ã€å°‘æ•°ã®ã‚µãƒ¼ãƒãƒ¼ã—ã‹ç®¡ç†ã—ã¦ã„ãªãã¦ã‚‚ã€ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã«é–¢ã™ã‚‹å¤‰æ•°ãŠã‚ˆã³æƒ…å ±ã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:523 +#: ../../rst/user_guide/playbooks_vars_facts.rst:533 msgid "Disabling facts" msgstr "ファクトã®ç„¡åŠ¹åŒ–" -#: ../../rst/user_guide/playbooks_vars_facts.rst:525 -msgid "By default, Ansible gathers facts at the beginning of each play. If you do not need to gather facts (for example, if you know everything about your systems centrally), you can turn off fact gathering at the play level to improve scalability. Disabling facts may particularly improve performance in push mode with very large numbers of systems, or if you are using Ansible on experimental platforms. To disable fact gathering::" +#: ../../rst/user_guide/playbooks_vars_facts.rst:535 +msgid "By default, Ansible gathers facts at the beginning of each play. If you do not need to gather facts (for example, if you know everything about your systems centrally), you can turn off fact gathering at the play level to improve scalability. Disabling facts may particularly improve performance in push mode with very large numbers of systems, or if you are using Ansible on experimental platforms. To disable fact gathering:" msgstr "デフォルトã§ã¯ã€Ansible ã¯å„プレイã®é–‹å§‹æ™‚ã«ãƒ•ã‚¡ã‚¯ãƒˆã‚’åŽé›†ã—ã¾ã™ã€‚ファクトをåŽé›†ã™ã‚‹å¿…è¦ãŒãªã„å ´åˆ (ãŸã¨ãˆã°ã€ã‚·ã‚¹ãƒ†ãƒ ã«é–¢ã™ã‚‹æƒ…å ±ã‚’ã™ã¹ã¦ä¸€å…ƒçš„ã«æŠŠæ¡ã—ã¦ã„ã‚‹å ´åˆ) ã¯ã€ãƒ—レイレベルã§ã®ãƒ•ã‚¡ã‚¯ãƒˆåŽé›†ã‚’オフã«ã™ã‚‹ã“ã¨ã§ã€ã‚¹ã‚±ãƒ¼ãƒ©ãƒ“リティーをå‘上ã•ã›ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ファクトを無効ã«ã™ã‚‹ã¨ã€éžå¸¸ã«å¤šæ•°ã®ã‚·ã‚¹ãƒ†ãƒ を使用ã™ã‚‹ãƒ—ッシュモードやã€å®Ÿé¨“çš„ãªãƒ—ラットフォーム㧠Ansible を使用ã—ã¦ã„ã‚‹å ´åˆã«ã€ç‰¹ã«ãƒ‘フォーマンスãŒå‘上ã™ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ファクトã®åŽé›†ã‚’無効ã«ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:531 +#: ../../rst/user_guide/playbooks_vars_facts.rst:543 msgid "Adding custom facts" msgstr "カスタムファクトã®è¿½åŠ " -#: ../../rst/user_guide/playbooks_vars_facts.rst:533 +#: ../../rst/user_guide/playbooks_vars_facts.rst:545 msgid "The setup module in Ansible automatically discovers a standard set of facts about each host. If you want to add custom values to your facts, you can write a custom facts module, set temporary facts with a ``ansible.builtin.set_fact`` task, or provide permanent custom facts using the facts.d directory." msgstr "Ansible ã®ã‚»ãƒƒãƒˆã‚¢ãƒƒãƒ—モジュールã¯ã€å„ホストã«é–¢ã™ã‚‹æ¨™æº–çš„ãªãƒ•ã‚¡ã‚¯ãƒˆã®ã‚»ãƒƒãƒˆã‚’自動的ã«æ¤œå‡ºã—ã¾ã™ã€‚ファクトã«ã‚«ã‚¹ã‚¿ãƒ å€¤ã‚’è¿½åŠ ã—ãŸã„å ´åˆã¯ã€ã‚«ã‚¹ã‚¿ãƒ ファクトモジュールを記述ã—ãŸã‚Šã€``ansible.builtin.set_fact`` タスクã§ä¸€æ™‚çš„ãªãƒ•ã‚¡ã‚¯ãƒˆã‚’è¨å®šã—ãŸã‚Šã€facts.d ディレクトリーを使用ã—ã¦æ’ä¹…çš„ãªã‚«ã‚¹ã‚¿ãƒ ファクトをæä¾›ã—ãŸã‚Šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:538 +#: ../../rst/user_guide/playbooks_vars_facts.rst:550 msgid "facts.d or local facts" msgstr "facts.d ã¾ãŸã¯ãƒãƒ¼ã‚«ãƒ«ãƒ•ã‚¡ã‚¯ãƒˆ" -#: ../../rst/user_guide/playbooks_vars_facts.rst:542 +#: ../../rst/user_guide/playbooks_vars_facts.rst:554 msgid "You can add static custom facts by adding static files to facts.d, or add dynamic facts by adding executable scripts to facts.d. For example, you can add a list of all users on a host to your facts by creating and running a script in facts.d." msgstr "é™çš„ãªã‚«ã‚¹ã‚¿ãƒ ファクトã¯ã€é™çš„ファイルを facts.d ã«è¿½åŠ ã™ã‚‹ã“ã¨ã§è¿½åŠ ã§ãã€å‹•çš„ãªãƒ•ã‚¡ã‚¯ãƒˆã¯å®Ÿè¡Œå¯èƒ½ãªã‚¹ã‚¯ãƒªãƒ—トを facts.d ã«è¿½åŠ ã™ã‚‹ã“ã¨ã§è¿½åŠ ã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€facts.d ã§ã‚¹ã‚¯ãƒªãƒ—トを作æˆã—ã¦å®Ÿè¡Œã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã€ãƒ›ã‚¹ãƒˆä¸Šã®ã™ã¹ã¦ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã®ãƒªã‚¹ãƒˆã‚’ファクトã«è¿½åŠ ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:544 +#: ../../rst/user_guide/playbooks_vars_facts.rst:556 msgid "To use facts.d, create an ``/etc/ansible/facts.d`` directory on the remote host or hosts. If you prefer a different directory, create it and specify it using the ``fact_path`` play keyword. Add files to the directory to supply your custom facts. All file names must end with ``.fact``. The files can be JSON, INI, or executable files returning JSON." msgstr "facts.d を使用ã™ã‚‹ã«ã¯ã€ãƒªãƒ¢ãƒ¼ãƒˆãƒ›ã‚¹ãƒˆã¾ãŸã¯ãƒ›ã‚¹ãƒˆä¸Šã« ``/etc/ansible/facts.d`` ディレクトリーを作æˆã—ã¾ã™ã€‚別ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã‚’使用ã™ã‚‹å ´åˆã¯ã€ãã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã‚’作æˆã—ã€ãƒ—レイã‚ーワード ``fact_path`` を使用ã—ã¦æŒ‡å®šã—ã¾ã™ã€‚ã“ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ãƒ•ã‚¡ã‚¤ãƒ«ã‚’è¿½åŠ ã—ã¦ã€ã‚«ã‚¹ã‚¿ãƒ ファクトをæä¾›ã—ã¾ã™ã€‚ã™ã¹ã¦ã®ãƒ•ã‚¡ã‚¤ãƒ«åã¯ã€``.fact`` ã§çµ‚ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ファイルã«ã¯ã€JSONã€INIã€ã¾ãŸã¯ JSON ã‚’è¿”ã™å®Ÿè¡Œå¯èƒ½ãƒ•ã‚¡ã‚¤ãƒ«ã‚’使用ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:546 -msgid "To add static facts, simply add a file with the ``.fact`` extension. For example, create ``/etc/ansible/facts.d/preferences.fact`` with this content::" +#: ../../rst/user_guide/playbooks_vars_facts.rst:558 +msgid "To add static facts, simply add a file with the ``.fact`` extension. For example, create ``/etc/ansible/facts.d/preferences.fact`` with this content:" msgstr "é™çš„ãƒ•ã‚¡ã‚¯ãƒˆã‚’è¿½åŠ ã™ã‚‹ã«ã¯ã€``.fact`` æ‹¡å¼µåã‚’æŒã¤ãƒ•ã‚¡ã‚¤ãƒ«ã‚’è¿½åŠ ã™ã‚‹ã ã‘ã§ã™ã€‚ãŸã¨ãˆã°ã€ä»¥ä¸‹ã®å†…容㧠``/etc/ansible/facts.d/preferences.fact`` を作æˆã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:552 +#: ../../rst/user_guide/playbooks_vars_facts.rst:566 msgid "Make sure the file is not executable as this will break the ``ansible.builtin.setup`` module." msgstr "``ansible.builtin.setup`` モジュールãŒå£Šã‚Œã‚‹ãŸã‚ã€ã“ã®ãƒ•ã‚¡ã‚¤ãƒ«ãŒå®Ÿè¡Œãƒ•ã‚¡ã‚¤ãƒ«ã§ã¯ãªã„ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/playbooks_vars_facts.rst:554 -msgid "The next time fact gathering runs, your facts will include a hash variable fact named ``general`` with ``asdf`` and ``bar`` as members. To validate this, run the following::" +#: ../../rst/user_guide/playbooks_vars_facts.rst:568 +msgid "The next time fact gathering runs, your facts will include a hash variable fact named ``general`` with ``asdf`` and ``bar`` as members. To validate this, run the following:" msgstr "次回ã€ãƒ•ã‚¡ã‚¯ãƒˆåŽé›†ãŒå®Ÿè¡Œã•ã‚Œã‚‹ã¨ã€ãƒ•ã‚¡ã‚¯ãƒˆã«ã¯ã€``asdf`` 㨠``bar`` をメンãƒãƒ¼ã¨ã™ã‚‹ ``general`` ã¨ã„ã†åå‰ã®ãƒãƒƒã‚·ãƒ¥å¤‰æ•°ãƒ•ã‚¡ã‚¯ãƒˆãŒå«ã¾ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚ã“れを検証ã™ã‚‹ã«ã¯ã€æ¬¡ã®ã‚ˆã†ã«å®Ÿè¡Œã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:558 -msgid "And you will see your custom fact added::" +#: ../../rst/user_guide/playbooks_vars_facts.rst:574 +msgid "And you will see your custom fact added:" msgstr "ã“ã‚Œã«ã‚ˆã‚Šã€ã‚«ã‚¹ã‚¿ãƒ ファクトãŒè¿½åŠ ã•ã‚Œã¦ã„ã‚‹ã®ãŒç¢ºèªã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:569 -msgid "The ansible_local namespace separates custom facts created by facts.d from system facts or variables defined elsewhere in the playbook, so variables will not override each other. You can access this custom fact in a template or playbook as::" +#: ../../rst/user_guide/playbooks_vars_facts.rst:589 +msgid "The ansible_local namespace separates custom facts created by facts.d from system facts or variables defined elsewhere in the playbook, so variables will not override each other. You can access this custom fact in a template or playbook as:" msgstr "ansible_local åå‰ç©ºé–“ã¯ã€facts.d ã§ä½œæˆã•ã‚ŒãŸã‚«ã‚¹ã‚¿ãƒ ファクトã¨ã€ã‚·ã‚¹ãƒ†ãƒ ファクトや Playbook 内ã®ä»–ã®å ´æ‰€ã§å®šç¾©ã•ã‚ŒãŸå¤‰æ•°ã‚’分離ã—ã€å¤‰æ•°ãŒäº’ã„ã«ä¸Šæ›¸ãã•ã‚Œãªã„よã†ã«ã—ã¾ã™ã€‚ã“ã®ã‚«ã‚¹ã‚¿ãƒ ファクトã«ã¯ã€ãƒ†ãƒ³ãƒ—レートや Playbook ã§æ¬¡ã®ã‚ˆã†ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:573 +#: ../../rst/user_guide/playbooks_vars_facts.rst:595 msgid "The key part in the key=value pairs will be converted into lowercase inside the ansible_local variable. Using the example above, if the ini file contained ``XYZ=3`` in the ``[general]`` section, then you should expect to access it as: ``{{ ansible_local['preferences']['general']['xyz'] }}`` and not ``{{ ansible_local['preferences']['general']['XYZ'] }}``. This is because Ansible uses Python's `ConfigParser`_ which passes all option names through the `optionxform`_ method and this method's default implementation converts option names to lower case." msgstr "éµã¨å€¤ã®ãƒšã‚¢ã®éµã®éƒ¨åˆ†ã¯ã€ansible_local 変数内ã§å°æ–‡å—ã«å¤‰æ›ã•ã‚Œã¾ã™ã€‚上記ã®ä¾‹ã§ã¯ã€ini ファイル㮠``[general]`` セクション㫠``XYZ=3`` ãŒå«ã¾ã‚Œã¦ã„ãŸå ´åˆã¯ã€``{{ ansible_local['preferences']['general']['XYZ'] }}`` ã§ã¯ãªãã€``{{ ansible_local['preferences']['general']['xyz'] }}`` ã¨ã—ã¦ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ã“ã¨ã«ãªã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€Ansible ㌠Python ã® `ConfigParser`_ を使用ã—ã¦ã€ã™ã¹ã¦ã®ã‚ªãƒ—ションåã‚’ `optionxform`_ メソッドã«æ¸¡ã—ã¦ãŠã‚Šã€ã“ã®ãƒ¡ã‚½ãƒƒãƒ‰ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã®å®Ÿè£…ã§ã¯ã€ã‚ªãƒ—ションåãŒå°æ–‡å—ã«å¤‰æ›ã•ã‚Œã‚‹ãŸã‚ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:578 +#: ../../rst/user_guide/playbooks_vars_facts.rst:600 msgid "You can also use facts.d to execute a script on the remote host, generating dynamic custom facts to the ansible_local namespace. For example, you can generate a list of all users that exist on a remote host as a fact about that host. To generate dynamic custom facts using facts.d:" msgstr "facts.d を使用ã—ã¦ã€ãƒªãƒ¢ãƒ¼ãƒˆãƒ›ã‚¹ãƒˆä¸Šã§ã‚¹ã‚¯ãƒªãƒ—トを実行ã—ã€ansible_local åå‰ç©ºé–“ã«å‹•çš„ãªã‚«ã‚¹ã‚¿ãƒ ファクトを生æˆã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€ãƒªãƒ¢ãƒ¼ãƒˆãƒ›ã‚¹ãƒˆã«å˜åœ¨ã™ã‚‹ã™ã¹ã¦ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã®ãƒªã‚¹ãƒˆã‚’ã€ãã®ãƒ›ã‚¹ãƒˆã«é–¢ã™ã‚‹ãƒ•ã‚¡ã‚¯ãƒˆã¨ã—ã¦ç”Ÿæˆã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚facts.d を使用ã—ã¦å‹•çš„ãªã‚«ã‚¹ã‚¿ãƒ ファクトを生æˆã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®æ‰‹é †ã«å¾“ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:580 +#: ../../rst/user_guide/playbooks_vars_facts.rst:602 msgid "Write and test a script to generate the JSON data you want." msgstr "スクリプトを作æˆã—ã¦ãƒ†ã‚¹ãƒˆã—ã¦ã€å¿…è¦ãª JSON データを生æˆã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:581 +#: ../../rst/user_guide/playbooks_vars_facts.rst:603 msgid "Save the script in your facts.d directory." msgstr "スクリプトを facts.d ディレクトリーã«ä¿å˜ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:582 +#: ../../rst/user_guide/playbooks_vars_facts.rst:604 msgid "Make sure your script has the ``.fact`` file extension." msgstr "スクリプト㫠``.fact`` ファイル拡張åãŒã‚ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:583 +#: ../../rst/user_guide/playbooks_vars_facts.rst:605 msgid "Make sure your script is executable by the Ansible connection user." msgstr "スクリプト㌠Ansible 接続ユーザーã«ã‚ˆã£ã¦å®Ÿè¡Œå¯èƒ½ã§ã‚ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:584 +#: ../../rst/user_guide/playbooks_vars_facts.rst:606 msgid "Gather facts to execute the script and add the JSON output to ansible_local." msgstr "スクリプトを実行ã™ã‚‹ãƒ•ã‚¡ã‚¯ãƒˆã‚’åŽé›†ã—ã€JSON 出力を ansible_local ã«è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:586 -msgid "By default, fact gathering runs once at the beginning of each play. If you create a custom fact using facts.d in a playbook, it will be available in the next play that gathers facts. If you want to use it in the same play where you created it, you must explicitly re-run the setup module. For example::" +#: ../../rst/user_guide/playbooks_vars_facts.rst:608 +msgid "By default, fact gathering runs once at the beginning of each play. If you create a custom fact using facts.d in a playbook, it will be available in the next play that gathers facts. If you want to use it in the same play where you created it, you must explicitly re-run the setup module. For example:" msgstr "デフォルトã§ã¯ã€ãƒ•ã‚¡ã‚¯ãƒˆã®åŽé›†ã¯å„プレイã®é–‹å§‹æ™‚ã«ä¸€åº¦ã ã‘実行ã—ã¾ã™ã€‚Playbook 㧠facts.d を使用ã—ã¦ã‚«ã‚¹ã‚¿ãƒ ファクトを作æˆã™ã‚‹ã¨ã€ãƒ•ã‚¡ã‚¯ãƒˆã‚’åŽé›†ã™ã‚‹æ¬¡ã®ãƒ—レイã§ä½¿ç”¨ã§ãるよã†ã«ãªã‚Šã¾ã™ã€‚作æˆã—ãŸã®ã¨åŒã˜ãƒ—レイã§ä½¿ç”¨ã—ãŸã„å ´åˆã¯ã€ã‚»ãƒƒãƒˆã‚¢ãƒƒãƒ—モジュールを明示的ã«å†å®Ÿè¡Œã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:606 +#: ../../rst/user_guide/playbooks_vars_facts.rst:630 msgid "If you use this pattern frequently, a custom facts module would be more efficient than facts.d." msgstr "ã“ã®ãƒ‘ã‚¿ãƒ¼ãƒ³ã‚’é »ç¹ã«ä½¿ç”¨ã™ã‚‹ã¨ã€ã‚«ã‚¹ã‚¿ãƒ ファクトモジュール㯠facts.d よりも効率ãŒä¸ŠãŒã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:611 +#: ../../rst/user_guide/playbooks_vars_facts.rst:635 msgid "Information about Ansible: magic variables" msgstr "Ansible ã«é–¢ã™ã‚‹æƒ…å ±: マジック変数" -#: ../../rst/user_guide/playbooks_vars_facts.rst:613 +#: ../../rst/user_guide/playbooks_vars_facts.rst:637 msgid "You can access information about Ansible operations, including the python version being used, the hosts and groups in inventory, and the directories for playbooks and roles, using \"magic\" variables. Like connection variables, magic variables are :ref:`special_variables`. Magic variable names are reserved - do not set variables with these names. The variable ``environment`` is also reserved." msgstr "使用ã—ã¦ã„ã‚‹ Python ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼å†…ã®ãƒ›ã‚¹ãƒˆã‚„グループã€Playbook ã‚„ãƒãƒ¼ãƒ«ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ãªã©ã€Ansible ã®æ“作ã«é–¢ã™ã‚‹æƒ…å ±ã¯ã€ã€Œãƒžã‚¸ãƒƒã‚¯ã€å¤‰æ•°ã‚’使用ã—ã¦ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚接続変数ã¨åŒæ§˜ã«ã€ãƒžã‚¸ãƒƒã‚¯å¤‰æ•°ã¯ :ref:`special_variables` ã§ã™ã€‚マジック変数ã®åå‰ã¯äºˆç´„済ã¿ã§ã™ã€‚ã“れらã®åå‰ã§å¤‰æ•°ã‚’è¨å®šã—ãªã„ã§ãã ã•ã„。変数 ``environment`` も予約済ã¿ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:615 +#: ../../rst/user_guide/playbooks_vars_facts.rst:639 msgid "The most commonly used magic variables are ``hostvars``, ``groups``, ``group_names``, and ``inventory_hostname``. With ``hostvars``, you can access variables defined for any host in the play, at any point in a playbook. You can access Ansible facts using the ``hostvars`` variable too, but only after you have gathered (or cached) facts." msgstr "最も一般的ã«ä½¿ç”¨ã•ã‚Œã‚‹ãƒžã‚¸ãƒƒã‚¯å¤‰æ•°ã¯ã€``hostvars``ã€``groups``ã€``group_names``ã€ãŠã‚ˆã³ ``inventory_hostname`` ã§ã™ã€‚``hostvars`` を使用ã™ã‚‹ã¨ã€Playbook 内ã®ä»»æ„ã®æ™‚点ã§ã€ãƒ—レイ内ã®ä»»æ„ã®ãƒ›ã‚¹ãƒˆã«å¯¾ã—ã¦å®šç¾©ã•ã‚ŒãŸå¤‰æ•°ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãã¾ã™ã€‚``hostvars`` 変数を使用ã—㦠Ansible ã®ãƒ•ã‚¡ã‚¯ãƒˆã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ãŒã€ãƒ•ã‚¡ã‚¯ãƒˆã‚’åŽé›† (ã¾ãŸã¯ã‚ャッシュ) ã—ãŸå¾Œã§ãªã‘ã‚Œã°ãªã‚Šã¾ã›ã‚“。" -#: ../../rst/user_guide/playbooks_vars_facts.rst:617 -msgid "If you want to configure your database server using the value of a 'fact' from another node, or the value of an inventory variable assigned to another node, you can use ``hostvars`` in a template or on an action line::" +#: ../../rst/user_guide/playbooks_vars_facts.rst:641 +msgid "If you want to configure your database server using the value of a 'fact' from another node, or the value of an inventory variable assigned to another node, you can use ``hostvars`` in a template or on an action line:" msgstr "ä»–ã®ãƒŽãƒ¼ãƒ‰ã®ã€Œãƒ•ã‚¡ã‚¯ãƒˆã€ã®å€¤ã‚„ã€ä»–ã®ãƒŽãƒ¼ãƒ‰ã«å‰²ã‚Šå½“ã¦ã‚‰ã‚ŒãŸã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼å¤‰æ•°ã®å€¤ã‚’使用ã—ã¦ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã‚µãƒ¼ãƒãƒ¼ã‚’è¨å®šã™ã‚‹å ´åˆã¯ã€ãƒ†ãƒ³ãƒ—レートやアクション行㧠``hostvars`` を使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:621 +#: ../../rst/user_guide/playbooks_vars_facts.rst:647 msgid "With ``groups``, a list of all the groups (and hosts) in the inventory, you can enumerate all hosts within a group. For example:" msgstr "``groups`` ã§ã¯ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼å†…ã®ã™ã¹ã¦ã®ã‚°ãƒ«ãƒ¼ãƒ— (ãŠã‚ˆã³ãƒ›ã‚¹ãƒˆ) ã®ãƒªã‚¹ãƒˆã§ã€ã‚°ãƒ«ãƒ¼ãƒ—内ã®ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã‚’列挙ã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:629 +#: ../../rst/user_guide/playbooks_vars_facts.rst:655 msgid "You can use ``groups`` and ``hostvars`` together to find all the IP addresses in a group." msgstr "``groups`` 㨠``hostvars`` を一緒ã«ä½¿ç”¨ã—ã¦ã€ã‚°ãƒ«ãƒ¼ãƒ—内ã®ã™ã¹ã¦ã® IP アドレスを探ã™ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:637 +#: ../../rst/user_guide/playbooks_vars_facts.rst:663 msgid "You can use this approach to point a frontend proxy server to all the hosts in your app servers group, to set up the correct firewall rules between servers, and so on. You must either cache facts or gather facts for those hosts before the task that fills out the template." msgstr "ã“ã®æ–¹æ³•ã‚’使用ã—ã¦ã€ãƒ•ãƒãƒ³ãƒˆã‚¨ãƒ³ãƒ‰ãƒ—ãƒã‚シーサーãƒãƒ¼ãŒã‚¢ãƒ—リサーãƒãƒ¼ã‚°ãƒ«ãƒ¼ãƒ—内ã®ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã‚’指ã™ã‚ˆã†ã«ã—ãŸã‚Šã€ã‚µãƒ¼ãƒãƒ¼é–“ã«æ£ã—ã„ファイアウォールルールをè¨å®šã—ãŸã‚Šã§ãã¾ã™ã€‚テンプレートã«å…¥åŠ›ã™ã‚‹ã‚¿ã‚¹ã‚¯ã®å‰ã«ã€ãƒ•ã‚¡ã‚¯ãƒˆã‚’ã‚ャッシュã™ã‚‹ã‹ã€ãれらã®ãƒ›ã‚¹ãƒˆã®ãƒ•ã‚¡ã‚¯ãƒˆã‚’åŽé›†ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:639 +#: ../../rst/user_guide/playbooks_vars_facts.rst:665 msgid "With ``group_names``, a list (array) of all the groups the current host is in, you can create templated files that vary based on the group membership (or role) of the host:" msgstr "``group_names`` ã§ã¯ã€ç¾åœ¨ã®ãƒ›ã‚¹ãƒˆãŒç½®ã‹ã‚Œã¦ã„ã‚‹ã™ã¹ã¦ã®ã‚°ãƒ«ãƒ¼ãƒ—ã®ãƒªã‚¹ãƒˆ (é…列) ã¯ã€ãƒ›ã‚¹ãƒˆã®ã‚°ãƒ«ãƒ¼ãƒ—メンãƒãƒ¼ã‚·ãƒƒãƒ— (ã¾ãŸã¯ãƒãƒ¼ãƒ«) ã«åŸºã¥ã„ã¦ç•°ãªã‚‹ãƒ†ãƒ³ãƒ—レートファイルを作æˆã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:647 +#: ../../rst/user_guide/playbooks_vars_facts.rst:673 msgid "You can use the magic variable ``inventory_hostname``, the name of the host as configured in your inventory, as an alternative to ``ansible_hostname`` when fact-gathering is disabled. If you have a long FQDN, you can use ``inventory_hostname_short``, which contains the part up to the first period, without the rest of the domain." msgstr "ファクトåŽé›†ãŒç„¡åŠ¹ã«ãªã£ã¦ã„ã‚‹ã¨ãã«ã¯ã€``ansible_hostname`` ã®ä»£ã‚ã‚Šã«ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã§è¨å®šã•ã‚ŒãŸãƒ›ã‚¹ãƒˆã®åå‰ã§ã‚るマジック変数 ``inventory_hostname`` を使用ã§ãã¾ã™ã€‚é•·ã„ FQDN ãŒã‚ã‚‹å ´åˆã«ã¯ã€æœ€åˆã®ãƒ”リオドã¾ã§ã®éƒ¨åˆ†ã‚’å«ã¿ã€ãƒ‰ãƒ¡ã‚¤ãƒ³ã®æ®‹ã‚Šã®éƒ¨åˆ†ã‚’å«ã¾ãªã„ ``inventory_hostname_short`` を使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:649 +#: ../../rst/user_guide/playbooks_vars_facts.rst:675 msgid "Other useful magic variables refer to the current play or playbook. These vars may be useful for filling out templates with multiple hostnames or for injecting the list into the rules for a load balancer." msgstr "ãã®ä»–ã®æœ‰ç”¨ãªãƒžã‚¸ãƒƒã‚¯å¤‰æ•°ã¯ã€ç¾åœ¨ã®ãƒ—レイや Playbook ã‚’å‚ç…§ã—ã¾ã™ã€‚ã“れらã®å¤‰æ•°ã¯ã€è¤‡æ•°ã®ãƒ›ã‚¹ãƒˆåã§ãƒ†ãƒ³ãƒ—レートを埋ã‚ã‚‹ã¨ãã‚„ã€ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚µãƒ¼ã®ãƒ«ãƒ¼ãƒ«ã«ãƒªã‚¹ãƒˆã‚’注入ã™ã‚‹ã¨ãã«ä¾¿åˆ©ã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:651 +#: ../../rst/user_guide/playbooks_vars_facts.rst:677 msgid "``ansible_play_hosts`` is the list of all hosts still active in the current play." msgstr "``ansible_play_hosts`` ã¯ã€ç¾åœ¨ã®ãƒ—レイã§ã‚¢ã‚¯ãƒ†ã‚£ãƒ–ãªã¾ã¾ã«ãªã£ã¦ã„ã‚‹ã™ã¹ã¦ã®ãƒ›ã‚¹ãƒˆã®å®Œå…¨ãªãƒªã‚¹ãƒˆã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:653 +#: ../../rst/user_guide/playbooks_vars_facts.rst:679 msgid "``ansible_play_batch`` is a list of hostnames that are in scope for the current 'batch' of the play." msgstr "``ansible_play_batch`` ã¯ã€ç¾åœ¨ã®ãƒ—レイã®ã€Œãƒãƒƒãƒã€ã®ç¯„囲内ã«ã‚るホストåã®ãƒªã‚¹ãƒˆã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:655 +#: ../../rst/user_guide/playbooks_vars_facts.rst:681 msgid "The batch size is defined by ``serial``, when not set it is equivalent to the whole play (making it the same as ``ansible_play_hosts``)." msgstr "ãƒãƒƒãƒã‚µã‚¤ã‚ºã¯ ``serial`` ã§å®šç¾©ã•ã‚Œã¾ã™ã€‚è¨å®šã•ã‚Œã¦ã„ãªã„å ´åˆã¯ã€ãƒ—レイ全体ã«ç›¸å½“ã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã™ (``ansible_play_hosts`` ã¨åŒã˜ã«ãªã‚Šã¾ã™)。" -#: ../../rst/user_guide/playbooks_vars_facts.rst:657 +#: ../../rst/user_guide/playbooks_vars_facts.rst:683 msgid "``ansible_playbook_python`` is the path to the python executable used to invoke the Ansible command line tool." msgstr "``ansible_playbook_python`` ã¯ã€Ansible コマンドラインツールを起動ã™ã‚‹ã®ã«ä½¿ç”¨ã•ã‚Œã‚‹ Python 実行ファイルã¸ã®ãƒ‘スã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:659 +#: ../../rst/user_guide/playbooks_vars_facts.rst:685 msgid "``inventory_dir`` is the pathname of the directory holding Ansible's inventory host file." msgstr "``inventory_dir`` ã¯ã€Ansible ã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ›ã‚¹ãƒˆãƒ•ã‚¡ã‚¤ãƒ«ã‚’ä¿æŒã™ã‚‹ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã®ãƒ‘スåã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:661 +#: ../../rst/user_guide/playbooks_vars_facts.rst:687 msgid "``inventory_file`` is the pathname and the filename pointing to the Ansible's inventory host file." msgstr "``inventory_file`` ã¯ã€Ansible ã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ›ã‚¹ãƒˆãƒ•ã‚¡ã‚¤ãƒ«ã‚’å‚ç…§ã™ã‚‹ãƒ‘スåã¨ãƒ•ã‚¡ã‚¤ãƒ«åã§ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:663 +#: ../../rst/user_guide/playbooks_vars_facts.rst:689 msgid "``playbook_dir`` contains the playbook base directory." msgstr "``playbook_dir`` ã«ã¯ Playbook ã®ãƒ™ãƒ¼ã‚¹ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ãŒå«ã¾ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:665 +#: ../../rst/user_guide/playbooks_vars_facts.rst:691 msgid "``role_path`` contains the current role's pathname and only works inside a role." msgstr "``role_path`` ã«ã¯ç¾åœ¨ã®ãƒãƒ¼ãƒ«ã®ãƒ‘スåãŒå«ã¾ã‚Œã€ãƒãƒ¼ãƒ«å†…ã§ã®ã¿å‹•ä½œã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:667 +#: ../../rst/user_guide/playbooks_vars_facts.rst:693 msgid "``ansible_check_mode`` is a boolean, set to ``True`` if you run Ansible with ``--check``." msgstr "``ansible_check_mode`` ㌠``--check`` 㧠Ansible を実行ã™ã‚‹å ´åˆã¯ ``True`` ã«è¨å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/playbooks_vars_facts.rst:672 +#: ../../rst/user_guide/playbooks_vars_facts.rst:698 msgid "Ansible version" msgstr "Ansible version" -#: ../../rst/user_guide/playbooks_vars_facts.rst:676 -msgid "To adapt playbook behavior to different versions of Ansible, you can use the variable ``ansible_version``, which has the following structure::" +#: ../../rst/user_guide/playbooks_vars_facts.rst:702 +msgid "To adapt playbook behavior to different versions of Ansible, you can use the variable ``ansible_version``, which has the following structure:" msgstr "Playbook ã®å‹•ä½œã‚’ã•ã¾ã–ã¾ãªãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Ansible ã«é©ç”¨ã™ã‚‹ã«ã¯ã€``ansible_version`` 変数を使用ã§ãã¾ã™ã€‚ã“ã®å¤‰æ•°ã«ã¯ã€ä»¥ä¸‹ã®æ§‹é€ ãŒã‚ã‚Šã¾ã™ã€‚" #: ../../rst/user_guide/playbooks_vault.rst:4 @@ -11118,134 +11125,134 @@ msgid "Sample directory layout" msgstr "ディレクトリーレイアウトã®ä¾‹" #: ../../rst/user_guide/sample_setup.rst:17 -msgid "This layout organizes most tasks in roles, with a single inventory file for each environment and a few playbooks in the top-level directory::" +msgid "This layout organizes most tasks in roles, with a single inventory file for each environment and a few playbooks in the top-level directory:" msgstr "ã“ã®ãƒ¬ã‚¤ã‚¢ã‚¦ãƒˆã§ã¯ã€ã»ã¨ã‚“ã©ã®ã‚¿ã‚¹ã‚¯ãŒãƒãƒ¼ãƒ«ã”ã¨ã«æ•´ç†ã•ã‚Œã¦ãŠã‚Šã€ç’°å¢ƒã”ã¨ã« 1 ã¤ã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ãƒ•ã‚¡ã‚¤ãƒ«ã‚’作æˆã—ã€ãƒˆãƒƒãƒ—レベルã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ã„ãã¤ã‹ã® Playbook ã‚’ç½®ã„ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:64 +#: ../../rst/user_guide/sample_setup.rst:66 msgid "By default, Ansible assumes your playbooks are stored in one directory with roles stored in a sub-directory called ``roles/``. As you use Ansible to automate more tasks, you may want to move your playbooks into a sub-directory called ``playbooks/``. If you do this, you must configure the path to your ``roles/`` directory using the ``roles_path`` setting in ansible.cfg." msgstr "デフォルトã§ã¯ã€Ansible ã¯ã€Playbook ㌠``roles/`` ã¨ã„ã†åå‰ã®ã‚µãƒ–ディレクトリーã«ä¿å˜ã•ã‚Œã¦ã„ã‚‹ãƒãƒ¼ãƒ«ã‚’æŒã¤ 1 ã¤ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ä¿å˜ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’å‰æã¨ã—ã¾ã™ã€‚Ansible を使用ã—ã¦ã‚ˆã‚Šå¤šãã®ã‚¿ã‚¹ã‚¯ã‚’自動化ã™ã‚‹å ´åˆã¯ã€Playbook ã‚’ ``playbooks/`` ã¨å‘¼ã°ã‚Œã‚‹ã‚µãƒ–ディレクトリーã«ç§»å‹•ã—ãŸã„å ´åˆãŒã‚ã‚Šã¾ã™ã€‚ã“れを行ã†å ´åˆã¯ã€ansible.cfg ã® ``roles_path`` ã®è¨å®šã‚’使用ã—ã¦ã€``roles/`` ディレクトリーã¸ã®ãƒ‘スをè¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:67 +#: ../../rst/user_guide/sample_setup.rst:69 msgid "Alternative directory layout" msgstr "代替ディレクトリーレイアウト" -#: ../../rst/user_guide/sample_setup.rst:69 -msgid "Alternatively you can put each inventory file with its ``group_vars``/``host_vars`` in a separate directory. This is particularly useful if your ``group_vars``/``host_vars`` don't have that much in common in different environments. The layout could look something like this::" +#: ../../rst/user_guide/sample_setup.rst:71 +msgid "Alternatively you can put each inventory file with its ``group_vars``/``host_vars`` in a separate directory. This is particularly useful if your ``group_vars``/``host_vars`` don't have that much in common in different environments. The layout could look something like this:" msgstr "ã¾ãŸã€``group_vars``/``host_vars`` ã‚’å«ã‚€å„インベントリーファイルを別ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ç½®ãã“ã¨ã‚‚ã§ãã¾ã™ã€‚ã“ã‚Œã¯ã€``group_vars``/``host_vars`` ãŒç•°ãªã‚‹ç’°å¢ƒã§ã‚ã¾ã‚Šå…±é€šã—ã¦ã„ãªã„å ´åˆã«ç‰¹ã«æœ‰åŠ¹ã§ã™ã€‚レイアウトã¯ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:104 +#: ../../rst/user_guide/sample_setup.rst:108 msgid "This layout gives you more flexibility for larger environments, as well as a total separation of inventory variables between different environments. However, this approach is harder to maintain, because there are more files. For more information on organizing group and host variables, see :ref:`splitting_out_vars`." msgstr "ã“ã®ãƒ¬ã‚¤ã‚¢ã‚¦ãƒˆã«ã‚ˆã‚Šã€å¤§è¦æ¨¡ãªç’°å¢ƒã«ã‚‚柔軟ã«å¯¾å¿œã™ã‚‹ã“ã¨ãŒã§ãã€ç•°ãªã‚‹ç’°å¢ƒé–“ã§ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼å¤‰æ•°ã‚’完全ã«åˆ†é›¢ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã—ã‹ã—ã€ã“ã®æ–¹æ³•ã§ã¯ã€ãƒ•ã‚¡ã‚¤ãƒ«æ•°ãŒå¤šããªã‚‹ãŸã‚ã€ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ãŒé›£ã—ããªã‚Šã¾ã™ã€‚グループ変数ã¨ãƒ›ã‚¹ãƒˆå¤‰æ•°ã®æ•´ç†ã®è©³ç´°ã¯ã€ã€Œ:ref:`splitting_out_vars`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/sample_setup.rst:109 +#: ../../rst/user_guide/sample_setup.rst:113 msgid "Sample group and host variables" msgstr "グループ変数ãŠã‚ˆã³ãƒ›ã‚¹ãƒˆå¤‰æ•°ã®ä¾‹" -#: ../../rst/user_guide/sample_setup.rst:111 -msgid "These sample group and host variables files record the variable values that apply to each machine or group of machines. For instance, the data center in Atlanta has its own NTP servers, so when setting up ntp.conf, we should use them::" +#: ../../rst/user_guide/sample_setup.rst:115 +msgid "These sample group and host variables files record the variable values that apply to each machine or group of machines. For instance, the data center in Atlanta has its own NTP servers, so when setting up ntp.conf, we should use them:" msgstr "ã“れらã®ã‚°ãƒ«ãƒ¼ãƒ—変数ã¨ãƒ›ã‚¹ãƒˆå¤‰æ•°ã®ã‚µãƒ³ãƒ—ルファイルã«ã¯ã€å„マシンやマシングループã«é©ç”¨ã•ã‚Œã‚‹å¤‰æ•°ã®å€¤ãŒè¨˜éŒ²ã•ã‚Œã¦ã„ã¾ã™ã€‚ãŸã¨ãˆã°ã€ã‚¢ãƒˆãƒ©ãƒ³ã‚¿ã®ãƒ‡ãƒ¼ã‚¿ã‚»ãƒ³ã‚¿ãƒ¼ã«ã¯ç‹¬è‡ªã® NTP サーãƒãƒ¼ãŒã‚ã‚‹ãŸã‚ã€ntp.conf ã‚’è¨å®šã™ã‚‹éš›ã«ã¯ã€ãれらを使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:118 -msgid "Similarly, the webservers have some configuration that does not apply to the database servers::" +#: ../../rst/user_guide/sample_setup.rst:124 +msgid "Similarly, the webservers have some configuration that does not apply to the database servers:" msgstr "åŒæ§˜ã«ã€Web サーãƒãƒ¼ã«ã¯ã€ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã‚µãƒ¼ãƒãƒ¼ã«ã¯é©ç”¨ã•ã‚Œãªã„以下ã®ã‚ˆã†ãªè¨å®šãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:125 -msgid "Default values, or values that are universally true, belong in a file called group_vars/all::" +#: ../../rst/user_guide/sample_setup.rst:133 +msgid "Default values, or values that are universally true, belong in a file called group_vars/all:" msgstr "デフォルト値ã¾ãŸã¯æ±Žç”¨çš„ã« true ã§ã‚る値ãŒã‚ã‚‹å ´åˆã¯ã€ãれらを group_vars/all ã¨ã„ã†ãƒ•ã‚¡ã‚¤ãƒ«ã«é…ç½®ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:132 -msgid "If necessary, you can define specific hardware variance in systems in a host_vars file::" +#: ../../rst/user_guide/sample_setup.rst:142 +msgid "If necessary, you can define specific hardware variance in systems in a host_vars file:" msgstr "å¿…è¦ã«å¿œã˜ã¦ã€ã‚·ã‚¹ãƒ†ãƒ ã®ç‰¹å®šã®ãƒãƒ¼ãƒ‰ã‚¦ã‚§ã‚¢ã®å·®ç•°ã‚’ host_vars ファイルã«å®šç¾©ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:139 +#: ../../rst/user_guide/sample_setup.rst:151 msgid "Again, if you are using :ref:`dynamic inventory <dynamic_inventory>`, Ansible creates many dynamic groups automatically. So a tag like \"class:webserver\" would load in variables from the file \"group_vars/ec2_tag_class_webserver\" automatically." msgstr "ç¹°ã‚Šè¿”ã—ã«ãªã‚Šã¾ã™ãŒã€:ref:`動的インベントリー <dynamic_inventory>` を使用ã—ã¦ã„ã‚‹å ´åˆã€Ansible ã¯å¤šãã®å‹•çš„グループを自動的ã«ä½œæˆã—ã¾ã™ã€‚ã¤ã¾ã‚Šã€ã€Œclass:webserverã€ã®ã‚ˆã†ãªã‚¿ã‚°ã¯ã€ã€Œgroup_vars/ec2_tag_class_webserverã€ãƒ•ã‚¡ã‚¤ãƒ«ã‹ã‚‰å¤‰æ•°ã‚’自動的ã«èªã¿è¾¼ã‚€ã“ã¨ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:144 +#: ../../rst/user_guide/sample_setup.rst:156 msgid "Sample playbooks organized by function" msgstr "関数別ã«æ•´ç†ã•ã‚ŒãŸ Playbook ã®ã‚µãƒ³ãƒ—ル" -#: ../../rst/user_guide/sample_setup.rst:146 -msgid "With this setup, a single playbook can define all the infrastructure. The site.yml playbook imports two other playbooks, one for the webservers and one for the database servers::" +#: ../../rst/user_guide/sample_setup.rst:158 +msgid "With this setup, a single playbook can define all the infrastructure. The site.yml playbook imports two other playbooks, one for the webservers and one for the database servers:" msgstr "ã“ã®è¨å®šã§ã¯ã€1 ã¤ã® Playbook ã§ã™ã¹ã¦ã®ã‚¤ãƒ³ãƒ•ãƒ©ã‚¹ãƒˆãƒ©ã‚¯ãƒãƒ£ãƒ¼ã‚’定義ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚Playbook site.yml ã¯ã€Web サーãƒãƒ¼ç”¨ã¨ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã‚µãƒ¼ãƒãƒ¼ç”¨ã® 2 ã¤ã® Playbook をインãƒãƒ¼ãƒˆã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:153 -msgid "The webservers.yml file, also at the top level, maps the configuration of the webservers group to the roles related to the webservers group::" +#: ../../rst/user_guide/sample_setup.rst:167 +msgid "The webservers.yml file, also at the top level, maps the configuration of the webservers group to the roles related to the webservers group:" msgstr "åŒã˜ãトップレベルã«ã‚ã‚‹ webservers.yml ファイルã¯ã€webservers グループã®è¨å®šã‚’ã€webservers グループã«é–¢é€£ã™ã‚‹ãƒãƒ¼ãƒ«ã«ãƒžãƒƒãƒ”ングã—ã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:162 -msgid "With this setup, you can configure your whole infrastructure by \"running\" site.yml, or run a subset by running webservers.yml. This is analogous to the Ansible \"--limit\" parameter but a little more explicit::" +#: ../../rst/user_guide/sample_setup.rst:178 +msgid "With this setup, you can configure your whole infrastructure by \"running\" site.yml, or run a subset by running webservers.yml. This is analogous to the Ansible \"--limit\" parameter but a little more explicit:" msgstr "ã“ã®è¨å®šã«ã‚ˆã‚Šã€site.yml を「実行ã€ã—ã¦ã‚¤ãƒ³ãƒ•ãƒ©ã‚¹ãƒˆãƒ©ã‚¯ãƒãƒ£ãƒ¼å…¨ä½“ã‚’è¨å®šã—ãŸã‚Šã€webservers.yml を実行ã—ã¦ã‚µãƒ–セットをè¨å®šã—ãŸã‚Šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã‚Œã¯ã€Ansible ã®ã€Œ--limitã€ãƒ‘ラメーターã«ä¼¼ã¦ã„ã¾ã™ãŒã€ã‚‚ã†å°‘ã—明確ã«ãªã£ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:170 +#: ../../rst/user_guide/sample_setup.rst:188 msgid "Sample task and handler files in a function-based role" msgstr "関数ベースã®ãƒãƒ¼ãƒ«å†…ã®ã‚¿ã‚¹ã‚¯ãŠã‚ˆã³ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã®ã‚µãƒ³ãƒ—ルファイル" -#: ../../rst/user_guide/sample_setup.rst:172 -msgid "Ansible loads any file called ``main.yml`` in a role sub-directory. This sample ``tasks/main.yml`` file is simple - it sets up NTP, but it could do more if we wanted::" +#: ../../rst/user_guide/sample_setup.rst:190 +msgid "Ansible loads any file called ``main.yml`` in a role sub-directory. This sample ``tasks/main.yml`` file is simple - it sets up NTP, but it could do more if we wanted:" msgstr "Ansible ã¯ã€ãƒãƒ¼ãƒ«ã®ã‚µãƒ–ディレクトリーã«ã‚ã‚‹ ``main.yml`` ファイルをèªã¿è¾¼ã¿ã¾ã™ã€‚ã“ã®ã‚µãƒ³ãƒ—ル㮠``tasks/main.yml`` ファイルã¯ã€NTP ã‚’è¨å®šã™ã‚‹ã¨ã„ã†ã‚·ãƒ³ãƒ—ルãªã‚‚ã®ã§ã™ãŒã€å¿…è¦ã«å¿œã˜ã¦ã‚‚ã£ã¨å¤šãã®ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:198 -msgid "Here is an example handlers file. As a review, handlers are only fired when certain tasks report changes, and are run at the end of each play::" +#: ../../rst/user_guide/sample_setup.rst:218 +msgid "Here is an example handlers file. As a review, handlers are only fired when certain tasks report changes, and are run at the end of each play:" msgstr "ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ãƒ•ã‚¡ã‚¤ãƒ«ã®ä¾‹ã‚’紹介ã—ã¾ã™ã€‚レビューã¨ã—ã¦ã€ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ã¯ç‰¹å®šã®ã‚¿ã‚¹ã‚¯ãŒå¤‰æ›´ã‚’å ±å‘Šã—ãŸã¨ãã«ã®ã¿èµ·å‹•ã—ã€å„プレイã®æœ€å¾Œã«å®Ÿè¡Œã—ã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:208 +#: ../../rst/user_guide/sample_setup.rst:230 msgid "See :ref:`playbooks_reuse_roles` for more information." msgstr "詳細ã¯ã€ã€Œ:ref:`playbooks_reuse_roles`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/sample_setup.rst:214 +#: ../../rst/user_guide/sample_setup.rst:236 msgid "What the sample setup enables" msgstr "è¨å®šä¾‹ã®æœ‰åŠ¹åŒ–" -#: ../../rst/user_guide/sample_setup.rst:216 -msgid "The basic organizational structure described above enables a lot of different automation options. To reconfigure your entire infrastructure::" +#: ../../rst/user_guide/sample_setup.rst:238 +msgid "The basic organizational structure described above enables a lot of different automation options. To reconfigure your entire infrastructure:" msgstr "上記ã®åŸºæœ¬çš„ãªçµ„ç¹”æ§‹é€ ã«ã‚ˆã‚Šã€å¤šãã®ç•°ãªã‚‹è‡ªå‹•åŒ–オプションãŒå¯èƒ½ã«ãªã‚Šã¾ã™ã€‚インフラストラクãƒãƒ£ãƒ¼å…¨ä½“ã‚’å†æ§‹æˆã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:220 -msgid "To reconfigure NTP on everything::" +#: ../../rst/user_guide/sample_setup.rst:244 +msgid "To reconfigure NTP on everything:" msgstr "å…¨é¢çš„ã« NTP ã‚’å†è¨å®šã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:224 -msgid "To reconfigure only the webservers::" +#: ../../rst/user_guide/sample_setup.rst:250 +msgid "To reconfigure only the webservers:" msgstr "webservers ã®ã¿ã‚’å†è¨å®šã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:228 -msgid "To reconfigure only the webservers in Boston::" +#: ../../rst/user_guide/sample_setup.rst:256 +msgid "To reconfigure only the webservers in Boston:" msgstr "Boston 㧠webservers ã®ã¿ã‚’å†è¨å®šã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:232 -msgid "To reconfigure only the first 10 webservers in Boston, and then the next 10::" +#: ../../rst/user_guide/sample_setup.rst:262 +msgid "To reconfigure only the first 10 webservers in Boston, and then the next 10:" msgstr "Boston ã§æœ€åˆã® 10 å°ã® webservers ã ã‘ã‚’å†è¨å®šã—ã€æ¬¡ã® 10 å°ã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:237 -msgid "The sample setup also supports basic ad hoc commands::" +#: ../../rst/user_guide/sample_setup.rst:269 +msgid "The sample setup also supports basic ad hoc commands:" msgstr "è¨å®šä¾‹ã§ã¯ã€åŸºæœ¬çš„ãªã‚¢ãƒ‰ãƒ›ãƒƒã‚¯ã‚³ãƒžãƒ³ãƒ‰ã‚‚サãƒãƒ¼ãƒˆã—ã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:242 -msgid "To discover what tasks would run or what hostnames would be affected by a particular Ansible command::" +#: ../../rst/user_guide/sample_setup.rst:276 +msgid "To discover what tasks would run or what hostnames would be affected by a particular Ansible command:" msgstr "実行ã™ã‚‹ã‚¿ã‚¹ã‚¯ã¾ãŸã¯ç‰¹å®šã® Ansible コマンドã®å½±éŸ¿ã‚’å—ã‘るホストåを検出ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:253 +#: ../../rst/user_guide/sample_setup.rst:289 msgid "Organizing for deployment or configuration" msgstr "デプãƒã‚¤ãƒ¡ãƒ³ãƒˆã¾ãŸã¯è¨å®šã®æ•´ç†" -#: ../../rst/user_guide/sample_setup.rst:255 +#: ../../rst/user_guide/sample_setup.rst:291 msgid "The sample setup models a typical configuration topology. When doing multi-tier deployments, there are going to be some additional playbooks that hop between tiers to roll out an application. In this case, 'site.yml' may be augmented by playbooks like 'deploy_exampledotcom.yml' but the general concepts still apply. Ansible allows you to deploy and configure using the same tool, so you would likely reuse groups and keep the OS configuration in separate playbooks or roles from the app deployment." msgstr "ã“ã®ã‚µãƒ³ãƒ—ルã§ã¯ã€å…¸åž‹çš„ãªè¨å®šãƒˆãƒãƒã‚¸ãƒ¼ã‚’モデル化ã—ã¦ã„ã¾ã™ã€‚複数階層ã®ãƒ‡ãƒ—ãƒã‚¤ãƒ¡ãƒ³ãƒˆã‚’è¡Œã†å ´åˆã¯ã€ã‚¢ãƒ—リケーションを展開ã™ã‚‹ãŸã‚ã«éšŽå±¤é–“ã‚’è¡Œãæ¥ã™ã‚‹ Playbook ãŒè¿½åŠ ã•ã‚Œã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®å ´åˆã€ã€Œsite.ymlã€ã«ã¯ã€Œdeploy_exampledotcom.ymlã€ãªã©ã® Playbook ãŒè¿½åŠ ã•ã‚Œã¾ã™ãŒã€ä¸€èˆ¬çš„ãªæ¦‚念ã¯å¤‰ã‚ã‚Šã¾ã›ã‚“。Ansible ã§ã¯ã€ãƒ‡ãƒ—ãƒã‚¤ã¨è¨å®šã‚’åŒã˜ãƒ„ールã§è¡Œã†ã“ã¨ãŒã§ãã‚‹ãŸã‚ã€ã‚°ãƒ«ãƒ¼ãƒ—ã‚’å†åˆ©ç”¨ã—ãŸã‚Šã€OS ã®è¨å®šã‚’アプリã®ãƒ‡ãƒ—ãƒã‚¤ã¨ã¯åˆ¥ã® Playbook ã‚„ãƒãƒ¼ãƒ«ã«ã¾ã¨ã‚ãŸã‚Šã™ã‚‹ã“ã¨ãŒè€ƒãˆã‚‰ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:259 +#: ../../rst/user_guide/sample_setup.rst:295 msgid "Consider \"playbooks\" as a sports metaphor -- you can have one set of plays to use against all your infrastructure and situational plays that you use at different times and for different purposes." msgstr "「Playbookã€ã‚’スãƒãƒ¼ãƒ„ã«ä¾‹ãˆã¦è€ƒãˆã¦ã¿ã¾ã—ょã†ã€‚ã™ã¹ã¦ã®ã‚¤ãƒ³ãƒ•ãƒ©ã‚¹ãƒˆãƒ©ã‚¯ãƒãƒ£ãƒ¼ã«å¯¾ã—ã¦ä½¿ç”¨ã™ã‚‹ 1 セットã®ãƒ—レイã¨ã€æ™‚ã¨å ´åˆã«å¿œã˜ã¦ä½¿ç”¨ã™ã‚‹çŠ¶æ³ã«å¿œã˜ãŸãƒ—レイãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/sample_setup.rst:264 +#: ../../rst/user_guide/sample_setup.rst:300 msgid "Using local Ansible modules" msgstr "ãƒãƒ¼ã‚«ãƒ« Ansible モジュールã®ä½¿ç”¨" -#: ../../rst/user_guide/sample_setup.rst:266 +#: ../../rst/user_guide/sample_setup.rst:302 msgid "If a playbook has a :file:`./library` directory relative to its YAML file, this directory can be used to add Ansible modules that will automatically be in the Ansible module path. This is a great way to keep modules that go with a playbook together. This is shown in the directory structure example at the start of this section." msgstr "Playbook ã«ã€YAML ファイルã«ç›¸å¯¾ã™ã‚‹ :file:`./library` ディレクトリーãŒã‚ã‚‹å ´åˆã¯ã€ã“ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã‚’使用ã—ã¦ã€è‡ªå‹•çš„ã« Ansible モジュールパスã«å«ã¾ã‚Œã‚‹ Ansible ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’è¿½åŠ ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã‚Œã¯ã€Playbook ã«ä»˜éšã™ã‚‹ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’ã¾ã¨ã‚ã¦ãŠãã®ã«æœ€é©ãªæ–¹æ³•ã§ã™ã€‚ã“ã‚Œã¯ã€ã“ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã®æœ€åˆã«ã‚ã‚‹ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼æ§‹é€ ã®ä¾‹ã§ç¤ºã•ã‚Œã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:5 ../../rst/user_guide/vault.rst:119 +#: ../../rst/user_guide/vault.rst:5 ../../rst/user_guide/vault.rst:121 msgid "Encrypting content with Ansible Vault" msgstr "Ansible Vault を使用ã—ãŸã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã®æš—å·åŒ–" @@ -11310,682 +11317,682 @@ msgid "Pass it with :option:`--vault-id <ansible-playbook --vault-id>` to the :r msgstr "Vault ID ã§æš—å·åŒ–ã•ã‚ŒãŸã‚³ãƒ³ãƒ†ãƒ³ãƒ„を使用ã™ã‚‹ Playbook を実行ã™ã‚‹éš›ã«ã€ã“れを :option:`--vault-id <ansible-playbook --vault-id>` 㧠:ref:`ansible-playbook` コマンドã«æ¸¡ã—ã¾ã™ã€‚" #: ../../rst/user_guide/vault.rst:43 -msgid "When you pass a vault ID as an option to the :ref:`ansible-vault` command, you add a label (a hint or nickname) to the encrypted content. This label documents which password you used to encrypt it. The encrypted variable or file includes the vault ID label in plain text in the header. The vault ID is the last element before the encrypted content. For example::" +msgid "When you pass a vault ID as an option to the :ref:`ansible-vault` command, you add a label (a hint or nickname) to the encrypted content. This label documents which password you used to encrypt it. The encrypted variable or file includes the vault ID label in plain text in the header. The vault ID is the last element before the encrypted content. For example:" msgstr ":ref:`ansible-vault` コマンドã®ã‚ªãƒ—ションã¨ã—㦠Vault ID を渡ã™ã¨ã€æš—å·åŒ–ã•ã‚ŒãŸã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã«ãƒ©ãƒ™ãƒ« (ヒントやニックãƒãƒ¼ãƒ ) ãŒè¿½åŠ ã•ã‚Œã¾ã™ã€‚ã“ã®ãƒ©ãƒ™ãƒ«ã¯ã€ã©ã®ãƒ‘スワードを使用ã—ã¦æš—å·åŒ–ã—ãŸã‹ã‚’記録ã—ã¾ã™ã€‚æš—å·åŒ–ã•ã‚ŒãŸå¤‰æ•°ã‚„ファイルã¯ã€ãƒ˜ãƒƒãƒ€ãƒ¼ã«å¹³æ–‡ã§ Vault ID ラベルをå«ã¿ã¾ã™ã€‚Vault ID ã¯æš—å·åŒ–ã•ã‚ŒãŸã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã®å‰ã®æœ€å¾Œã®è¦ç´ ã§ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:53 +#: ../../rst/user_guide/vault.rst:55 msgid "In addition to the label, you must provide a source for the related password. The source can be a prompt, a file, or a script, depending on how you are storing your vault passwords. The pattern looks like this:" msgstr "ラベルã«åŠ ãˆã¦ã€é–¢é€£ã™ã‚‹ãƒ‘スワードã®ã‚½ãƒ¼ã‚¹ã‚’æä¾›ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ソースã¯ã€Vault パスワードをã©ã®ã‚ˆã†ã«ä¿å˜ã™ã‚‹ã‹ã«ã‚ˆã£ã¦ã€ãƒ—ãƒãƒ³ãƒ—トã€ãƒ•ã‚¡ã‚¤ãƒ«ã€ã¾ãŸã¯ã‚¹ã‚¯ãƒªãƒ—トã«ãªã‚Šã¾ã™ã€‚パターンã¯æ¬¡ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:59 +#: ../../rst/user_guide/vault.rst:61 msgid "If your playbook uses multiple encrypted variables or files that you encrypted with different passwords, you must pass the vault IDs when you run that playbook. You can use :option:`--vault-id <ansible-playbook --vault-id>` by itself, with :option:`--vault-password-file <ansible-playbook --vault-password-file>`, or with :option:`--ask-vault-pass <ansible-playbook --ask-vault-pass>`. The pattern is the same as when you create encrypted content: include the label and the source for the matching password." msgstr "Playbook ãŒè¤‡æ•°ã®æš—å·åŒ–ã•ã‚ŒãŸå¤‰æ•°ã‚„ã€ç•°ãªã‚‹ãƒ‘スワードã§æš—å·åŒ–ã—ãŸãƒ•ã‚¡ã‚¤ãƒ«ã‚’使用ã™ã‚‹å ´åˆã¯ã€ãã® Playbook を実行ã™ã‚‹éš›ã« Vault ID を渡ã™å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚:option:`--vault-id <ansible-playbook --vault-id>` ã‚’å˜ç‹¬ã§ã€ã‚‚ã—ã㯠:option:`--vault-password-file <ansible-playbook --vault-password-file>` ã¾ãŸã¯ :option:`--ask-vault-pass <ansible-playbook --ask-vault-pass>` ã¨ä¸€ç·’ã«ä½¿ç”¨ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚パターンã¯ã€æš—å·åŒ–ã•ã‚ŒãŸã‚³ãƒ³ãƒ†ãƒ³ãƒ„を作æˆã™ã‚‹ã¨ãã¨åŒã˜ã§ã€ä¸€è‡´ã™ã‚‹ãƒ‘スワードã®ãƒ©ãƒ™ãƒ«ã¨ã‚½ãƒ¼ã‚¹ã‚’å«ã‚ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:61 +#: ../../rst/user_guide/vault.rst:63 msgid "See below for examples of encrypting content with vault IDs and using content encrypted with vault IDs. The :option:`--vault-id <ansible-playbook --vault-id>` option works with any Ansible command that interacts with vaults, including :ref:`ansible-vault`, :ref:`ansible-playbook`, and so on." msgstr "Vault ID ã§ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã‚’æš—å·åŒ–ã™ã‚‹ä¾‹ã¨ã€Vault ID ã§æš—å·åŒ–ã•ã‚ŒãŸã‚³ãƒ³ãƒ†ãƒ³ãƒ„を使用ã™ã‚‹ä¾‹ã«ã¤ã„ã¦ã¯ã€ä»¥ä¸‹ã‚’å‚ç…§ã—ã¦ãã ã•ã„。:option:`--vault-id <ansible-playbook --vault-id>` オプションã¯ã€:ref:`ansible-vault`ã€:ref:`ansible-playbook` ãªã©ã€Vault ã¨ç›¸äº’作用ã™ã‚‹ã™ã¹ã¦ã® Ansible コマンドã§å‹•ä½œã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:64 +#: ../../rst/user_guide/vault.rst:66 msgid "Limitations of vault IDs" msgstr "Vault ID ã®åˆ¶é™" -#: ../../rst/user_guide/vault.rst:66 +#: ../../rst/user_guide/vault.rst:68 msgid "Ansible does not enforce using the same password every time you use a particular vault ID label. You can encrypt different variables or files with the same vault ID label but different passwords. This usually happens when you type the password at a prompt and make a mistake. It is possible to use different passwords with the same vault ID label on purpose. For example, you could use each label as a reference to a class of passwords, rather than a single password. In this scenario, you must always know which specific password or file to use in context. However, you are more likely to encrypt two files with the same vault ID label and different passwords by mistake. If you encrypt two files with the same label but different passwords by accident, you can :ref:`rekey <rekeying_files>` one file to fix the issue." msgstr "Ansible ã¯ã€ç‰¹å®šã® Vault ID ラベルを使用ã™ã‚‹ãŸã³ã«åŒã˜ãƒ‘スワードを使用ã™ã‚‹ã“ã¨ã‚’強制ã—ã¾ã›ã‚“。異ãªã‚‹å¤‰æ•°ã‚„ファイルをã€åŒã˜ Vault ID ラベルã§ç•°ãªã‚‹ãƒ‘スワードを使用ã—ã¦æš—å·åŒ–ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã‚Œã¯é€šå¸¸ã€ãƒ—ãƒãƒ³ãƒ—トã§ãƒ‘スワードを入力ã—ã¦é–“é•ãˆãŸå ´åˆã«èµ·ã“ã‚Šã¾ã™ã€‚æ„図的ã«ã€åŒã˜ Vault ID ラベルã§ç•°ãªã‚‹ãƒ‘スワードを使用ã™ã‚‹ã“ã¨ã¯å¯èƒ½ã§ã™ã€‚ãŸã¨ãˆã°ã€å„ラベルをã€å˜ä¸€ã®ãƒ‘スワードã§ã¯ãªãã€ãƒ‘スワードã®ã‚¯ãƒ©ã‚¹ã¸ã®å‚ç…§ã¨ã—ã¦ä½¿ç”¨ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã®ã‚·ãƒŠãƒªã‚ªã§ã¯ã€ã©ã®ç‰¹å®šã®ãƒ‘スワードã¾ãŸã¯ãƒ•ã‚¡ã‚¤ãƒ«ã‚’使用ã™ã‚‹ã‹ã‚’常ã«ã‚³ãƒ³ãƒ†ã‚ストã§çŸ¥ã£ã¦ãŠãå¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã—ã‹ã—ã€èª¤ã£ã¦åŒã˜ Vault ID ラベルã¨ç•°ãªã‚‹ãƒ‘スワードを使用ã™ã‚‹ 2 ã¤ã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’æš—å·åŒ–ã—ã¦ã—ã¾ã†å¯èƒ½æ€§ãŒé«˜ããªã‚Šã¾ã™ã€‚誤ã£ã¦åŒã˜ãƒ©ãƒ™ãƒ«ã§ç•°ãªã‚‹ãƒ‘スワード㮠2 ã¤ã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’æš—å·åŒ–ã—ã¦ã—ã¾ã£ãŸå ´åˆã¯ã€1ã¤ã®ãƒ•ã‚¡ã‚¤ãƒ«ã§ :ref:`rekey <rekeying_files>` ã‚’è¡Œã£ã¦å•é¡Œã‚’解決ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:69 +#: ../../rst/user_guide/vault.rst:71 msgid "Enforcing vault ID matching" msgstr "Vault ID 一致ã®å¼·åˆ¶" -#: ../../rst/user_guide/vault.rst:71 +#: ../../rst/user_guide/vault.rst:73 msgid "By default the vault ID label is only a hint to remind you which password you used to encrypt a variable or file. Ansible does not check that the vault ID in the header of the encrypted content matches the vault ID you provide when you use the content. Ansible decrypts all files and variables called by your command or playbook that are encrypted with the password you provide. To check the encrypted content and decrypt it only when the vault ID it contains matches the one you provide with ``--vault-id``, set the config option :ref:`DEFAULT_VAULT_ID_MATCH`. When you set :ref:`DEFAULT_VAULT_ID_MATCH`, each password is only used to decrypt data that was encrypted with the same label. This is efficient, predictable, and can reduce errors when different values are encrypted with different passwords." msgstr "デフォルトã§ã¯ã€Vault ID ラベルã¯ã€å¤‰æ•°ã‚„ファイルã®æš—å·åŒ–ã«ã©ã®ãƒ‘スワードを使用ã—ãŸã‹ã‚’æ€ã„出ã•ã›ã‚‹ãŸã‚ã®ãƒ’ントã«éŽãŽã¾ã›ã‚“。Ansible ã¯ã€æš—å·åŒ–ã•ã‚ŒãŸã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã®ãƒ˜ãƒƒãƒ€ãƒ¼ã«ã‚ã‚‹ Vault ID ãŒã€ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã®ä½¿ç”¨æ™‚ã«æŒ‡å®šã—㟠Vault ID ã¨ä¸€è‡´ã™ã‚‹ã‹ã©ã†ã‹ã¯ãƒã‚§ãƒƒã‚¯ã—ã¾ã›ã‚“。Ansible ã¯ã€æŒ‡å®šã—ãŸãƒ‘スワードã§æš—å·åŒ–ã•ã‚ŒãŸã‚³ãƒžãƒ³ãƒ‰ã¾ãŸã¯ Playbook ã«ã‚ˆã£ã¦å‘¼ã³å‡ºã•ã‚ŒãŸã™ã¹ã¦ã®ãƒ•ã‚¡ã‚¤ãƒ«ãŠã‚ˆã³å¤‰æ•°ã‚’復å·ã—ã¾ã™ã€‚æš—å·åŒ–ã•ã‚ŒãŸã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã‚’ãƒã‚§ãƒƒã‚¯ã—ã€ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã«å«ã¾ã‚Œã‚‹ Vault ID ㌠``--vault-id`` ã§æŒ‡å®šã—ãŸã‚‚ã®ã¨ä¸€è‡´ã—ãŸå ´åˆã«ã®ã¿æš—å·åŒ–を解除ã™ã‚‹ã«ã¯ã€è¨å®šã‚ªãƒ—ション :ref:`DEFAULT_VAULT_ID_MATCH` ã‚’è¨å®šã—ã¾ã™ã€‚:ref:`DEFAULT_VAULT_ID_MATCH` ã‚’è¨å®šã™ã‚‹ã¨ã€å„パスワードã¯åŒã˜ãƒ©ãƒ™ãƒ«ã§æš—å·åŒ–ã—ãŸãƒ‡ãƒ¼ã‚¿ã‚’復å·ã™ã‚‹ãŸã‚ã«ã®ã¿ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯åŠ¹çŽ‡çš„ã§äºˆæ¸¬å¯èƒ½ã§ã‚ã‚Šã€ç•°ãªã‚‹å€¤ãŒç•°ãªã‚‹ãƒ‘スワードã§æš—å·åŒ–ã•ã‚ŒãŸå ´åˆã®ã‚¨ãƒ©ãƒ¼ã‚’減らã™ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:74 +#: ../../rst/user_guide/vault.rst:76 msgid "Even with the :ref:`DEFAULT_VAULT_ID_MATCH` setting enabled, Ansible does not enforce using the same password every time you use a particular vault ID label." msgstr ":ref:`DEFAULT_VAULT_ID_MATCH` ã®è¨å®šãŒæœ‰åŠ¹ã«ãªã£ã¦ã„ã‚‹å ´åˆã§ã‚‚ã€ç‰¹å®šã® Vault ID ラベルを使用ã™ã‚‹ãŸã³ã«ã€Ansible ã¯åŒã˜ãƒ‘スワードã®ä½¿ç”¨ã‚’強制ã—ã¾ã›ã‚“。" -#: ../../rst/user_guide/vault.rst:79 +#: ../../rst/user_guide/vault.rst:81 msgid "Storing and accessing vault passwords" msgstr "Vault パスワードã®ä¿å˜ãŠã‚ˆã³ã‚¢ã‚¯ã‚»ã‚¹" -#: ../../rst/user_guide/vault.rst:81 +#: ../../rst/user_guide/vault.rst:83 msgid "You can memorize your vault password, or manually copy vault passwords from any source and paste them at a command-line prompt, but most users store them securely and access them as needed from within Ansible. You have two options for storing vault passwords that work from within Ansible: in files, or in a third-party tool such as the system keyring or a secret manager. If you store your passwords in a third-party tool, you need a vault password client script to retrieve them from within Ansible." msgstr "Valut パスワードを記憶ã—ãŸã‚Šã€Valut パスワードを任æ„ã®ã‚½ãƒ¼ã‚¹ã‹ã‚‰æ‰‹å‹•ã§ã‚³ãƒ”ーã—ã¦ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ãƒ—ãƒãƒ³ãƒ—トã«è²¼ã‚Šä»˜ã‘ãŸã‚Šã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ãŒã€ã»ã¨ã‚“ã©ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã¯å®‰å…¨ã«ä¿ç®¡ã—ã€å¿…è¦ã«å¿œã˜ã¦ Ansible 内ã‹ã‚‰ã‚¢ã‚¯ã‚»ã‚¹ã—ã¾ã™ã€‚Ansible 内ã§æ©Ÿèƒ½ã™ã‚‹ Valut パスワードã®ä¿ç®¡æ–¹æ³•ã«ã¯ã€ãƒ•ã‚¡ã‚¤ãƒ«ã«ä¿ç®¡ã™ã‚‹æ–¹æ³•ã¨ã€ã‚·ã‚¹ãƒ†ãƒ ã‚ーリングやシークレットマãƒãƒ¼ã‚¸ãƒ£ãƒ¼ãªã©ã®ã‚µãƒ¼ãƒ‰ãƒ‘ーティーツールã«ä¿ç®¡ã™ã‚‹æ–¹æ³•ãŒã‚ã‚Šã¾ã™ã€‚サードパーティーã®ãƒ„ールã«ãƒ‘スワードをä¿å˜ã™ã‚‹å ´åˆã€Ansible 内ã‹ã‚‰ãƒ‘スワードをå–å¾—ã™ã‚‹ã«ã¯ã€Vault パスワードクライアントスクリプトãŒå¿…è¦ã§ã™ã€‚" -#: ../../rst/user_guide/vault.rst:84 +#: ../../rst/user_guide/vault.rst:86 msgid "Storing passwords in files" msgstr "パスワードã®ãƒ•ã‚¡ã‚¤ãƒ«ã¸ã®ä¿å˜" -#: ../../rst/user_guide/vault.rst:86 +#: ../../rst/user_guide/vault.rst:88 msgid "To store a vault password in a file, enter the password as a string on a single line in the file. Make sure the permissions on the file are appropriate. Do not add password files to source control." msgstr "Vault ã®ãƒ‘スワードをファイルã«ä¿å˜ã™ã‚‹ã«ã¯ã€ãƒ•ã‚¡ã‚¤ãƒ«ã® 1 è¡Œã«ãƒ‘スワードを文å—列ã§å…¥åŠ›ã—ã¾ã™ã€‚ファイルã®ãƒ‘ーミッションãŒé©åˆ‡ã§ã‚ã‚‹ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。パスワードファイルをソースコントãƒãƒ¼ãƒ«ã«è¿½åŠ ã—ãªã„ã§ãã ã•ã„。" -#: ../../rst/user_guide/vault.rst:91 +#: ../../rst/user_guide/vault.rst:93 msgid "Storing passwords in third-party tools with vault password client scripts" msgstr "Vault パスワードクライアントスクリプトを使用ã—ãŸã‚µãƒ¼ãƒ‰ãƒ‘ーティーツールã¸ã®ãƒ‘スワードã®ä¿å˜" -#: ../../rst/user_guide/vault.rst:93 +#: ../../rst/user_guide/vault.rst:95 msgid "You can store your vault passwords on the system keyring, in a database, or in a secret manager and retrieve them from within Ansible using a vault password client script. Enter the password as a string on a single line. If your password has a vault ID, store it in a way that works with your password storage tool." msgstr "Valut パスワードã¯ã€ã‚·ã‚¹ãƒ†ãƒ ã‚ーリングã€ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã€ã¾ãŸã¯ã‚·ãƒ¼ã‚¯ãƒ¬ãƒƒãƒˆãƒžãƒãƒ¼ã‚¸ãƒ£ãƒ¼ã«ä¿å˜ã—ã€Valut パスワードクライアントスクリプトを使用ã—㦠Ansible 内ã‹ã‚‰å–り出ã™ã“ã¨ãŒã§ãã¾ã™ã€‚パスワード㯠1 è¡Œã®æ–‡å—列ã¨ã—ã¦å…¥åŠ›ã—ã¾ã™ã€‚パスワード㫠Vault ID ãŒã‚ã‚‹å ´åˆã¯ã€ãƒ‘スワードä¿å˜ãƒ„ールã¨é€£æºã™ã‚‹æ–¹æ³•ã§ä¿å˜ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:95 +#: ../../rst/user_guide/vault.rst:97 msgid "To create a vault password client script:" msgstr "Vault パスワードクライアントスクリプトを作æˆã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:97 +#: ../../rst/user_guide/vault.rst:99 msgid "Create a file with a name ending in either ``-client`` or ``-client.EXTENSION``" msgstr "``-client`` ã¾ãŸã¯ ``-client.EXTENSION`` ã§çµ‚ã‚ã‚‹åå‰ã§ãƒ•ã‚¡ã‚¤ãƒ«ã‚’作æˆã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:98 +#: ../../rst/user_guide/vault.rst:100 msgid "Make the file executable" msgstr "ファイルを実行å¯èƒ½ãªçŠ¶æ…‹ã«ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:102 +#: ../../rst/user_guide/vault.rst:104 msgid "Within the script itself:" msgstr "スクリプト自体:" -#: ../../rst/user_guide/vault.rst:100 +#: ../../rst/user_guide/vault.rst:102 msgid "Print the passwords to standard output" msgstr "標準出力ã«ãƒ‘スワードを出力ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:101 +#: ../../rst/user_guide/vault.rst:103 msgid "Accept a ``--vault-id`` option" msgstr "``--vault-id`` オプションを許å¯ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:102 +#: ../../rst/user_guide/vault.rst:104 msgid "If the script prompts for data (for example, a database password), send the prompts to standard error" msgstr "スクリプトãŒãƒ‡ãƒ¼ã‚¿ã‚’è¦æ±‚ã™ã‚‹å ´åˆ (例: データベースパスワード) ã«ã¯ã€ãƒ—ãƒãƒ³ãƒ—トを標準エラーã«é€ä¿¡ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:104 +#: ../../rst/user_guide/vault.rst:106 msgid "When you run a playbook that uses vault passwords stored in a third-party tool, specify the script as the source within the ``--vault-id`` flag. For example:" msgstr "サードパーティーã®ãƒ„ールã«ä¿å˜ã•ã‚Œã¦ã„ã‚‹ Vault パスワードを使用ã™ã‚‹ Playbook を実行ã™ã‚‹å ´åˆã¯ã€``--vault-id`` フラグ内ã§ã‚¹ã‚¯ãƒªãƒ—トをソースã¨ã—ã¦æŒ‡å®šã—ã¾ã™ã€‚以下を例ã«ç¤ºã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:110 +#: ../../rst/user_guide/vault.rst:112 msgid "Ansible executes the client script with a ``--vault-id`` option so the script knows which vault ID label you specified. For example a script loading passwords from a secret manager can use the vault ID label to pick either the 'dev' or 'prod' password. The example command above results in the following execution of the client script:" msgstr "Ansible ã¯ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã‚¹ã‚¯ãƒªãƒ—トを ``--vault-id`` オプション付ãã§å®Ÿè¡Œã™ã‚‹ãŸã‚ã€ã‚¹ã‚¯ãƒªãƒ—トã¯æŒ‡å®šã•ã‚ŒãŸ Vault ID ラベルを知るã“ã¨ãŒã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€ã‚·ãƒ¼ã‚¯ãƒ¬ãƒƒãƒˆãƒžãƒãƒ¼ã‚¸ãƒ£ãƒ¼ã‹ã‚‰ãƒ‘スワードをèªã¿è¾¼ã‚€ã‚¹ã‚¯ãƒªãƒ—トã¯ã€Vault ID ラベルを使用ã—ã¦ã€ã€Œdevã€ã¾ãŸã¯ã€Œprodã€ã®ã„ãšã‚Œã‹ã®ãƒ‘スワードをé¸æŠžã§ãã¾ã™ã€‚上記ã®ã‚³ãƒžãƒ³ãƒ‰ã®ä¾‹ã§ã¯ã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã‚¹ã‚¯ãƒªãƒ—トã®å®Ÿè¡Œçµæžœã¯æ¬¡ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:116 +#: ../../rst/user_guide/vault.rst:118 msgid "For an example of a client script that loads passwords from the system keyring, see the `vault-keyring-client script <https://github.com/ansible-community/contrib-scripts/blob/main/vault/vault-keyring-client.py>`_." msgstr "システムã‚ーリングã‹ã‚‰ãƒ‘スワードをèªã¿è¾¼ã‚€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã‚¹ã‚¯ãƒªãƒ—トã®ä¾‹ã¯ã€:file:`vault-keyring-client script <https://github.com/ansible-community/contrib-scripts/blob/main/vault/vault-keyring-client.py>` ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/vault.rst:121 +#: ../../rst/user_guide/vault.rst:123 msgid "Once you have a strategy for managing and storing vault passwords, you can start encrypting content. You can encrypt two types of content with Ansible Vault: variables and files. Encrypted content always includes the ``!vault`` tag, which tells Ansible and YAML that the content needs to be decrypted, and a ``|`` character, which allows multi-line strings. Encrypted content created with ``--vault-id`` also contains the vault ID label. For more details about the encryption process and the format of content encrypted with Ansible Vault, see :ref:`vault_format`. This table shows the main differences between encrypted variables and encrypted files:" msgstr "Vault ã®ãƒ‘スワードを管ç†ãŠã‚ˆã³ä¿ç®¡ã™ã‚‹ãŸã‚ã®ã‚¹ãƒˆãƒ©ãƒ†ã‚¸ãƒ¼ãŒã§ããŸã‚‰ã€ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã®æš—å·åŒ–を開始ã§ãã¾ã™ã€‚Ansible Vault ã§ã¯ã€å¤‰æ•°ã¨ãƒ•ã‚¡ã‚¤ãƒ«ã® 2 種類ã®ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã‚’æš—å·åŒ–ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚æš—å·åŒ–ã•ã‚ŒãŸã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã«ã¯ã€å¿…ãš ``!vault`` ã‚¿ã‚°ãŒå«ã¾ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ã€ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã®å¾©å·ãŒå¿…è¦ã§ã‚ã‚‹ã“ã¨ã‚’ Ansible 㨠YAML ã«ä¼ãˆã‚‹ã‚‚ã®ã§ã€è¤‡æ•°è¡Œã®æ–‡å—列をå¯èƒ½ã«ã™ã‚‹ ``|`` æ–‡å—ã‚‚å«ã¾ã‚Œã¦ã„ã¾ã™ã€‚``--vault-id`` ã§ä½œæˆã•ã‚ŒãŸæš—å·åŒ–コンテンツã«ã¯ã€Vault ID ラベルもå«ã¾ã‚Œã¾ã™ã€‚Ansible Vault ã«ãŠã‘ã‚‹æš—å·åŒ–プãƒã‚»ã‚¹ã¨å½¢å¼ã®è©³ç´°ã¯ã€ã€Œ:ref:`vault_format`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。ã“ã®è¡¨ã¯ã€æš—å·åŒ–ã•ã‚ŒãŸå¤‰æ•°ã¨æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã®ä¸»ãªé•ã„を示ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:127 +#: ../../rst/user_guide/vault.rst:129 msgid "Encrypted variables" msgstr "æš—å·åŒ–ã•ã‚ŒãŸå¤‰æ•°" -#: ../../rst/user_guide/vault.rst:127 +#: ../../rst/user_guide/vault.rst:129 msgid "Encrypted files" msgstr "æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«" -#: ../../rst/user_guide/vault.rst:129 +#: ../../rst/user_guide/vault.rst:131 msgid "How much is encrypted?" msgstr "ã©ã®ãらã„æš—å·åŒ–ã•ã‚Œã¦ã„ã‚‹ã®ã‹" -#: ../../rst/user_guide/vault.rst:129 +#: ../../rst/user_guide/vault.rst:131 msgid "Variables within a plaintext file" msgstr "平文ファイル内ã®å¤‰æ•°" -#: ../../rst/user_guide/vault.rst:129 +#: ../../rst/user_guide/vault.rst:131 msgid "The entire file" msgstr "ファイル全体" -#: ../../rst/user_guide/vault.rst:131 +#: ../../rst/user_guide/vault.rst:133 msgid "When is it decrypted?" msgstr "復å·ã™ã‚‹ã‚¿ã‚¤ãƒŸãƒ³ã‚°" -#: ../../rst/user_guide/vault.rst:131 +#: ../../rst/user_guide/vault.rst:133 msgid "On demand, only when needed" msgstr "オンデマンド㧠(å¿…è¦ãªå ´åˆã«ã®ã¿)" -#: ../../rst/user_guide/vault.rst:131 +#: ../../rst/user_guide/vault.rst:133 msgid "Whenever loaded or referenced [#f1]_" msgstr "èªã¿è¾¼ã¿ã¾ãŸã¯å‚ç…§ã™ã‚‹å ´åˆ [#f1]_" -#: ../../rst/user_guide/vault.rst:133 +#: ../../rst/user_guide/vault.rst:135 msgid "What can be encrypted?" msgstr "æš—å·åŒ–ã§ãã‚‹ã‚‚ã®" -#: ../../rst/user_guide/vault.rst:133 +#: ../../rst/user_guide/vault.rst:135 msgid "Only variables" msgstr "変数ã®ã¿" -#: ../../rst/user_guide/vault.rst:133 +#: ../../rst/user_guide/vault.rst:135 msgid "Any structured data file" msgstr "æ§‹é€ åŒ–ãƒ‡ãƒ¼ã‚¿ãƒ•ã‚¡ã‚¤ãƒ«" -#: ../../rst/user_guide/vault.rst:137 +#: ../../rst/user_guide/vault.rst:139 msgid "Ansible cannot know if it needs content from an encrypted file unless it decrypts the file, so it decrypts all encrypted files referenced in your playbooks and roles." msgstr "Ansible ã¯ã€ãƒ•ã‚¡ã‚¤ãƒ«ã‚’復å·ã—ãªã„é™ã‚Šã€æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã‹ã‚‰ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã‚’å¿…è¦ã¨ã™ã‚‹ã‹ã©ã†ã‹ã‚’èªè˜ã§ããªã„ãŸã‚ã€Playbook ãŠã‚ˆã³ãƒãƒ¼ãƒ«ã§å‚ç…§ã•ã‚Œã‚‹æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã‚’ã™ã¹ã¦å¾©å·ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:143 +#: ../../rst/user_guide/vault.rst:145 msgid "Encrypting individual variables with Ansible Vault" msgstr "Ansible Vault ã«ã‚ˆã‚‹å€‹ã€…ã®å¤‰æ•°ã®æš—å·åŒ–" -#: ../../rst/user_guide/vault.rst:145 +#: ../../rst/user_guide/vault.rst:147 msgid "You can encrypt single values inside a YAML file using the :ref:`ansible-vault encrypt_string <ansible_vault_encrypt_string>` command. For one way to keep your vaulted variables safely visible, see :ref:`tip_for_variables_and_vaults`." msgstr ":ref:`ansible-vault encrypt_string <ansible_vault_encrypt_string>` コマンドを使用ã—ã¦ã€YAML ファイル内㧠1 ã¤ã®å€¤ã‚’æš—å·åŒ–ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚Vault を使用ã—ãŸå¤‰æ•°ã‚’安全ã«è¡¨ç¤ºã§ãる方法ã¯ã€ã€Œ:ref:`tip_for_variables_and_vaults`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/vault.rst:148 +#: ../../rst/user_guide/vault.rst:150 msgid "Advantages and disadvantages of encrypting variables" msgstr "変数を暗å·åŒ–ã™ã‚‹ã“ã¨ã®åˆ©ç‚¹ãŠã‚ˆã³æ¬ 点" -#: ../../rst/user_guide/vault.rst:150 +#: ../../rst/user_guide/vault.rst:152 msgid "With variable-level encryption, your files are still easily legible. You can mix plaintext and encrypted variables, even inline in a play or role. However, password rotation is not as simple as with file-level encryption. You cannot :ref:`rekey <rekeying_files>` encrypted variables. Also, variable-level encryption only works on variables. If you want to encrypt tasks or other content, you must encrypt the entire file." msgstr "変数レベルã®æš—å·åŒ–ã§ã¯ã€ãƒ•ã‚¡ã‚¤ãƒ«ã‚’ç°¡å˜ã«èªã¿å–ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚平文ã®å¤‰æ•°ã¨æš—å·åŒ–ã•ã‚ŒãŸå¤‰æ•°ã‚’混在ã•ã›ã‚‹ã“ã¨ãŒã§ãã€ãƒ—レイやãƒãƒ¼ãƒ«ã®ä¸ã§ã‚¤ãƒ³ãƒ©ã‚¤ãƒ³ã§ã‚‚使用ã§ãã¾ã™ã€‚ã—ã‹ã—ã€ãƒ‘スワードã®ãƒãƒ¼ãƒ†ãƒ¼ã‚·ãƒ§ãƒ³ã¯ãƒ•ã‚¡ã‚¤ãƒ«ãƒ¬ãƒ™ãƒ«ã®æš—å·åŒ–ã®ã‚ˆã†ã«ç°¡å˜ã§ã¯ã‚ã‚Šã¾ã›ã‚“。暗å·åŒ–ã•ã‚ŒãŸå¤‰æ•°ã« :ref:`éµã®å†è¨å®š <rekeying_files>` ã¯ä½¿ç”¨ã§ãã¾ã›ã‚“。ã¾ãŸã€å¤‰æ•°ãƒ¬ãƒ™ãƒ«ã®æš—å·åŒ–ã¯å¤‰æ•°ã«å¯¾ã—ã¦ã®ã¿æ©Ÿèƒ½ã—ã¾ã™ã€‚タスクやãã®ä»–ã®ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã‚’æš—å·åŒ–ã™ã‚‹å ´åˆã¯ã€ãƒ•ã‚¡ã‚¤ãƒ«å…¨ä½“ã‚’æš—å·åŒ–ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:155 +#: ../../rst/user_guide/vault.rst:157 msgid "Creating encrypted variables" msgstr "æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã®ä½œæˆ" -#: ../../rst/user_guide/vault.rst:157 +#: ../../rst/user_guide/vault.rst:159 msgid "The :ref:`ansible-vault encrypt_string <ansible_vault_encrypt_string>` command encrypts and formats any string you type (or copy or generate) into a format that can be included in a playbook, role, or variables file. To create a basic encrypted variable, pass three options to the :ref:`ansible-vault encrypt_string <ansible_vault_encrypt_string>` command:" msgstr ":ref:`ansible-vault encrypt_string <ansible_vault_encrypt_string>` コマンドã¯ã€å…¥åŠ› (ã‚‚ã—ãã¯ã‚³ãƒ”ーã¾ãŸã¯ç”Ÿæˆ) ã—ãŸæ–‡å—列を暗å·åŒ–ã—ã¦ã€Playbookã€ãƒãƒ¼ãƒ«ã€å¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«ã«å«ã‚ã‚‹ã“ã¨ãŒã§ãã‚‹å½¢å¼ã«ã—ã¾ã™ã€‚基本的ãªæš—å·åŒ–変数を作æˆã™ã‚‹ã«ã¯ã€:ref:`ansible-vault encrypt_string <ansible_vault_encrypt_string>` コマンド㫠3 ã¤ã®ã‚ªãƒ—ションを渡ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:159 +#: ../../rst/user_guide/vault.rst:161 msgid "a source for the vault password (prompt, file, or script, with or without a vault ID)" msgstr "Vault パスワードã®ã‚½ãƒ¼ã‚¹ (プãƒãƒ³ãƒ—トã€ãƒ•ã‚¡ã‚¤ãƒ«ã€ã¾ãŸã¯ã‚¹ã‚¯ãƒªãƒ—トã€Vault ID ã‚ã‚Š/ãªã—)" -#: ../../rst/user_guide/vault.rst:160 +#: ../../rst/user_guide/vault.rst:162 msgid "the string to encrypt" msgstr "æš—å·åŒ–ã™ã‚‹æ–‡å—列" -#: ../../rst/user_guide/vault.rst:161 +#: ../../rst/user_guide/vault.rst:163 msgid "the string name (the name of the variable)" msgstr "æ–‡å—列å (変数ã®åå‰)" -#: ../../rst/user_guide/vault.rst:163 +#: ../../rst/user_guide/vault.rst:165 msgid "The pattern looks like this:" msgstr "パターンã¯ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:169 +#: ../../rst/user_guide/vault.rst:171 msgid "For example, to encrypt the string 'foobar' using the only password stored in 'a_password_file' and name the variable 'the_secret':" msgstr "ãŸã¨ãˆã°ã€ã€Œa_password_fileã€ã«ä¿å˜ã•ã‚ŒãŸãƒ‘スワードã®ã¿ã‚’使用ã—ã¦æ–‡å—列を「foobarã€ã‚’æš—å·åŒ–ã™ã‚‹éš›ã«ã€å¤‰æ•°ã€Œthe_secretã€ã«åå‰ã‚’付ã‘ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:175 ../../rst/user_guide/vault.rst:191 -msgid "The command above creates this content::" +#: ../../rst/user_guide/vault.rst:177 ../../rst/user_guide/vault.rst:195 +msgid "The command above creates this content:" msgstr "上記ã®ã‚³ãƒžãƒ³ãƒ‰ã«ã‚ˆã‚Šã€ä»¥ä¸‹ã®ã‚ˆã†ãªå†…容ãŒä½œæˆã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:185 +#: ../../rst/user_guide/vault.rst:189 msgid "To encrypt the string 'foooodev', add the vault ID label 'dev' with the 'dev' vault password stored in 'a_password_file', and call the encrypted variable 'the_dev_secret':" msgstr "æ–‡å—列「foooodevã€ã‚’æš—å·åŒ–ã™ã‚‹ã«ã¯ã€Vault ID ラベル「devã€ã«ã€Œa_password_fileã€ã«æ ¼ç´ã•ã‚Œã¦ã„る「devã€ã® Vault ãƒ‘ã‚¹ãƒ¯ãƒ¼ãƒ‰ã‚’è¿½åŠ ã—ã€æš—å·åŒ–ã•ã‚ŒãŸå¤‰æ•°ã€Œthe_dev_secretã€ã‚’呼ã³å‡ºã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:201 +#: ../../rst/user_guide/vault.rst:207 msgid "To encrypt the string 'letmein' read from stdin, add the vault ID 'dev' using the 'dev' vault password stored in `a_password_file`, and name the variable 'db_password':" msgstr "標準入力ã‹ã‚‰èªã¿è¾¼ã‚“ã æ–‡å—列「letmeinã€ã‚’æš—å·åŒ–ã™ã‚‹ãŸã‚ã«ã€`a_password_file` ã«ä¿å˜ã•ã‚Œã¦ã„る「devã€ã® Vault ã®ãƒ‘スワードを使用ã—㦠Vault ID「devã€ã‚’è¿½åŠ ã—ã€å¤‰æ•°ã«ã€Œdb_passwordã€ã¨ã„ã†åå‰ã‚’付ã‘ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:209 +#: ../../rst/user_guide/vault.rst:215 msgid "Typing secret content directly at the command line (without a prompt) leaves the secret string in your shell history. Do not do this outside of testing." msgstr "秘密ã®å†…容をコマンドラインã§ç›´æŽ¥å…¥åŠ›ã™ã‚‹ã¨ (プãƒãƒ³ãƒ—トãªã—)ã€ã‚·ã‚§ãƒ«ã®å±¥æ´ã«ç§˜å¯†ã®æ–‡å—列ãŒæ®‹ã‚Šã¾ã™ã€‚テスト時以外ã¯ã“ã®ã‚ˆã†ãªã“ã¨ã‚’ã—ãªã„ã§ãã ã•ã„。" -#: ../../rst/user_guide/vault.rst:211 -msgid "The command above creates this output::" +#: ../../rst/user_guide/vault.rst:217 +msgid "The command above creates this output:" msgstr "上記ã®ã‚³ãƒžãƒ³ãƒ‰ã«ã‚ˆã‚Šã€ä»¥ä¸‹ãŒå‡ºåŠ›ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:222 +#: ../../rst/user_guide/vault.rst:230 msgid "To be prompted for a string to encrypt, encrypt it with the 'dev' vault password from 'a_password_file', name the variable 'new_user_password' and give it the vault ID label 'dev':" msgstr "æš—å·åŒ–ã™ã‚‹æ–‡å—列ã®å…¥åŠ›ã‚’求ã‚られるãŸã‚ã€ã€Œa_password_fileã€ã®ã€Œdevã€ã® Vault パスワードã§æš—å·åŒ–ã—ã€å¤‰æ•°åを「new_user_passwordã€ã¨ã—ã€Vault ID ラベル「devã€ã‚’付与ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:228 +#: ../../rst/user_guide/vault.rst:236 msgid "The command above triggers this prompt:" msgstr "上記ã®ã‚³ãƒžãƒ³ãƒ‰ã«ã‚ˆã‚Šã€ä»¥ä¸‹ã®ãƒ—ãƒãƒ³ãƒ—トãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:234 +#: ../../rst/user_guide/vault.rst:242 msgid "Type the string to encrypt (for example, 'hunter2'), hit ctrl-d, and wait." msgstr "æš—å·åŒ–ã™ã‚‹æ–‡å—列 (「hunter2ã€ãªã©) を入力ã—ã€ctrl-d を押ã—ã¦ãŠå¾…ã¡ãã ã•ã„。" -#: ../../rst/user_guide/vault.rst:238 +#: ../../rst/user_guide/vault.rst:246 msgid "Do not press ``Enter`` after supplying the string to encrypt. That will add a newline to the encrypted value." msgstr "æš—å·åŒ–ã™ã‚‹æ–‡å—列を指定ã—ãŸå¾Œã« ``Enter`` を押ã•ãªã„ã§ãã ã•ã„。暗å·åŒ–ã•ã‚ŒãŸå€¤ã«æ”¹è¡Œã‚’è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:240 -msgid "The sequence above creates this output::" +#: ../../rst/user_guide/vault.rst:248 +msgid "The sequence above creates this output:" msgstr "上記ã®ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ã«ã‚ˆã‚Šã€ä»¥ä¸‹ã®ã‚ˆã†ãªå‡ºåŠ›ãŒä½œæˆã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:250 +#: ../../rst/user_guide/vault.rst:260 msgid "You can add the output from any of the examples above to any playbook, variables file, or role for future use. Encrypted variables are larger than plain-text variables, but they protect your sensitive content while leaving the rest of the playbook, variables file, or role in plain text so you can easily read it." msgstr "上記ã®ä¾‹ã®å‡ºåŠ›ã‚’å°†æ¥ä½¿ç”¨ã™ã‚‹ãŸã‚ã«ã€ä»»æ„ã® Playbookã€å¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«ã€ã¾ãŸã¯ãƒãƒ¼ãƒ«ã«è¿½åŠ ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚æš—å·åŒ–ã•ã‚ŒãŸå¤‰æ•°ã¯ã€å¹³æ–‡ã®å¤‰æ•°ã‚ˆã‚Šã‚‚サイズãŒå¤§ãããªã‚Šã¾ã™ãŒã€æ©Ÿå¯†æ€§ã®é«˜ã„コンテンツをä¿è·ã™ã‚‹ä¸€æ–¹ã§ã€Playbookã€å¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«ã€ã¾ãŸã¯ãƒãƒ¼ãƒ«ã®æ®‹ã‚Šã®éƒ¨åˆ†ã¯å¹³æ–‡ã®ã¾ã¾ãªã¨ãªã‚‹ãŸã‚ã€ç°¡å˜ã«èªã¿å–ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:253 +#: ../../rst/user_guide/vault.rst:263 msgid "Viewing encrypted variables" msgstr "æš—å·åŒ–ã•ã‚ŒãŸå¤‰æ•°ã®è¡¨ç¤º" -#: ../../rst/user_guide/vault.rst:255 +#: ../../rst/user_guide/vault.rst:265 msgid "You can view the original value of an encrypted variable using the debug module. You must pass the password that was used to encrypt the variable. For example, if you stored the variable created by the last example above in a file called 'vars.yml', you could view the unencrypted value of that variable like this:" msgstr "æš—å·åŒ–ã•ã‚ŒãŸå¤‰æ•°ã®å…ƒã®å€¤ã¯ã€ãƒ‡ãƒãƒƒã‚°ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使用ã—ã¦è¦‹ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãã®éš›ã«ã¯ã€å¤‰æ•°ã®æš—å·åŒ–ã«ä½¿ç”¨ã—ãŸãƒ‘スワードを渡ã™å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€ä¸Šè¨˜ã®æœ€å¾Œã®ä¾‹ã§ä½œæˆã—ãŸå¤‰æ•°ã‚’「vars.ymlã€ã¨ã„ã†ãƒ•ã‚¡ã‚¤ãƒ«ã«ä¿å˜ã—ãŸå ´åˆã«ã€ãã®å¤‰æ•°ã®æš—å·åŒ–ã•ã‚Œã¦ã„ãªã„値を見るã«ã¯æ¬¡ã®ã‚ˆã†ã«ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:267 +#: ../../rst/user_guide/vault.rst:277 msgid "Encrypting files with Ansible Vault" msgstr "Ansible Vault ã«ã‚ˆã‚‹ãƒ•ã‚¡ã‚¤ãƒ«ã®æš—å·åŒ–" -#: ../../rst/user_guide/vault.rst:269 +#: ../../rst/user_guide/vault.rst:279 msgid "Ansible Vault can encrypt any structured data file used by Ansible, including:" msgstr "Ansible Vault ã¯ã€Ansible ãŒä½¿ç”¨ã™ã‚‹ã‚ã‚‰ã‚†ã‚‹æ§‹é€ åŒ–ãƒ‡ãƒ¼ã‚¿ãƒ•ã‚¡ã‚¤ãƒ«ã‚’æš—å·åŒ–ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:271 +#: ../../rst/user_guide/vault.rst:281 msgid "group variables files from inventory" msgstr "インベントリーã‹ã‚‰ã®ã‚°ãƒ«ãƒ¼ãƒ—変数ファイル" -#: ../../rst/user_guide/vault.rst:272 +#: ../../rst/user_guide/vault.rst:282 msgid "host variables files from inventory" msgstr "インベントリーã‹ã‚‰ã®ãƒ›ã‚¹ãƒˆå¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«" -#: ../../rst/user_guide/vault.rst:273 +#: ../../rst/user_guide/vault.rst:283 msgid "variables files passed to ansible-playbook with ``-e @file.yml`` or ``-e @file.json``" msgstr "``-e @file.yml`` ã¾ãŸã¯ ``-e @file.json`` 㧠ansible-playbook ã«æ¸¡ã•ã‚Œã‚‹å¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«" -#: ../../rst/user_guide/vault.rst:274 +#: ../../rst/user_guide/vault.rst:284 msgid "variables files loaded by ``include_vars`` or ``vars_files``" msgstr "``include_vars`` ã¾ãŸã¯ ``vars_files`` ã«ã‚ˆã‚Šèªã¿è¾¼ã¾ã‚ŒãŸå¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«" -#: ../../rst/user_guide/vault.rst:275 +#: ../../rst/user_guide/vault.rst:285 msgid "variables files in roles" msgstr "ãƒãƒ¼ãƒ«ã®å¤‰æ•°ãƒ•ã‚¡ã‚¤ãƒ«" -#: ../../rst/user_guide/vault.rst:276 +#: ../../rst/user_guide/vault.rst:286 msgid "defaults files in roles" msgstr "ãƒãƒ¼ãƒ«å†…ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆãƒ•ã‚¡ã‚¤ãƒ«" -#: ../../rst/user_guide/vault.rst:277 +#: ../../rst/user_guide/vault.rst:287 msgid "tasks files" msgstr "タスクファイル" -#: ../../rst/user_guide/vault.rst:278 +#: ../../rst/user_guide/vault.rst:288 msgid "handlers files" msgstr "ãƒãƒ³ãƒ‰ãƒ©ãƒ¼ãƒ•ã‚¡ã‚¤ãƒ«" -#: ../../rst/user_guide/vault.rst:279 +#: ../../rst/user_guide/vault.rst:289 msgid "binary files or other arbitrary files" msgstr "ãƒã‚¤ãƒŠãƒªãƒ¼ãƒ•ã‚¡ã‚¤ãƒ«ã¾ãŸã¯ãã®ä»–ã®ä»»æ„ã®ãƒ•ã‚¡ã‚¤ãƒ«" -#: ../../rst/user_guide/vault.rst:281 +#: ../../rst/user_guide/vault.rst:291 msgid "The full file is encrypted in the vault." msgstr "完全ãªãƒ•ã‚¡ã‚¤ãƒ«ã¯ Vault ã§æš—å·åŒ–ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:285 +#: ../../rst/user_guide/vault.rst:295 msgid "Ansible Vault uses an editor to create or modify encrypted files. See :ref:`vault_securing_editor` for some guidance on securing the editor." msgstr "Ansible Vault ã¯ã‚¨ãƒ‡ã‚£ã‚¿ãƒ¼ã‚’使用ã—ã¦æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã®ä½œæˆã¾ãŸã¯å¤‰æ›´ã—ã¾ã™ã€‚エディターã®ã‚»ã‚ュリティーä¿è·ã«é–¢ã™ã‚‹ã„ãã¤ã‹ã®ã‚¬ã‚¤ãƒ€ãƒ³ã‚¹ã¯ã€ã€Œ:ref:`vault_securing_editor`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/vault.rst:289 +#: ../../rst/user_guide/vault.rst:299 msgid "Advantages and disadvantages of encrypting files" msgstr "ファイルを暗å·åŒ–ã™ã‚‹ã“ã¨ã®åˆ©ç‚¹ãŠã‚ˆã³æ¬ 点" -#: ../../rst/user_guide/vault.rst:291 +#: ../../rst/user_guide/vault.rst:301 msgid "File-level encryption is easy to use. Password rotation for encrypted files is straightforward with the :ref:`rekey <rekeying_files>` command. Encrypting files can hide not only sensitive values, but the names of the variables you use. However, with file-level encryption the contents of files are no longer easy to access and read. This may be a problem with encrypted tasks files. When encrypting a variables file, see :ref:`tip_for_variables_and_vaults` for one way to keep references to these variables in a non-encrypted file. Ansible always decrypts the entire encrypted file when it is when loaded or referenced, because Ansible cannot know if it needs the content unless it decrypts it." msgstr "ファイルレベルã®æš—å·åŒ–ã¯ç°¡å˜ã«ä½¿ç”¨ã§ãã¾ã™ã€‚æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã®ãƒ‘スワードãƒãƒ¼ãƒ†ãƒ¼ã‚·ãƒ§ãƒ³ã¯ã€:ref:`rekey <rekeying_files>` コマンドã§ç°¡å˜ã«è¡Œã†ã“ã¨ãŒã§ãã¾ã™ã€‚ファイルを暗å·åŒ–ã™ã‚‹ã¨ã€æ…Žé‡ã«æ‰±ã†ã¹ã値ã ã‘ã§ãªãã€ä½¿ç”¨ã™ã‚‹å¤‰æ•°ã®åå‰ã‚‚éš ã™ã“ã¨ãŒã§ãã¾ã™ã€‚ã—ã‹ã—ã€ãƒ•ã‚¡ã‚¤ãƒ«ãƒ¬ãƒ™ãƒ«ã®æš—å·åŒ–ã§ã¯ã€ãƒ•ã‚¡ã‚¤ãƒ«ã®å†…容ã«ç°¡å˜ã«ã‚¢ã‚¯ã‚»ã‚¹ã—ã¦èªã‚€ã“ã¨ãŒã§ããªããªã‚Šã¾ã™ã€‚ã“ã‚Œã¯æš—å·åŒ–ã•ã‚ŒãŸã‚¿ã‚¹ã‚¯ãƒ•ã‚¡ã‚¤ãƒ«ã§ã¯å•é¡Œã«ãªã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“。変数ファイルを暗å·åŒ–ã™ã‚‹å ´åˆã€ã“れらã®å¤‰æ•°ã¸ã®å‚照を暗å·åŒ–ã•ã‚Œã¦ã„ãªã„ファイルã«ä¿æŒã™ã‚‹ 1 ã¤ã®æ–¹æ³•ã€ã€Œ:ref:`tip_for_variables_and_vaults`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。Ansible ã¯ã€æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã‚’èªã¿è¾¼ã‚“ã ã‚Šå‚ç…§ã—ãŸã‚Šã™ã‚‹éš›ã«ã¯ã€å¸¸ã«æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«å…¨ä½“を復å·ã—ã¾ã™ã€‚ã“ã‚Œã¯ã€Ansible ã¯å¾©å·ã—ãªã„é™ã‚Šã‚³ãƒ³ãƒ†ãƒ³ãƒ„ãŒå¿…è¦ã‹ã©ã†ã‹ã‚’知るã“ã¨ãŒã§ããªã„ã‹ã‚‰ã§ã™ã€‚" -#: ../../rst/user_guide/vault.rst:296 +#: ../../rst/user_guide/vault.rst:306 msgid "Creating encrypted files" msgstr "æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã®ä½œæˆ" -#: ../../rst/user_guide/vault.rst:298 +#: ../../rst/user_guide/vault.rst:308 msgid "To create a new encrypted data file called 'foo.yml' with the 'test' vault password from 'multi_password_file':" msgstr "「multi_password_fileã€ã® Vault パスワード「testã€ã‚’使用ã—ã¦ã€ã€Œfoo.ymlã€ã¨ã„ã†åå‰ã®æ–°ã—ã„æš—å·åŒ–データファイルを作æˆã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:304 +#: ../../rst/user_guide/vault.rst:314 msgid "The tool launches an editor (whatever editor you have defined with $EDITOR, default editor is vi). Add the content. When you close the editor session, the file is saved as encrypted data. The file header reflects the vault ID used to create it:" msgstr "ã“ã®ãƒ„ールã¯ã€ã‚¨ãƒ‡ã‚£ã‚¿ãƒ¼ ($EDITOR ã§å®šç¾©ã—ãŸã‚¨ãƒ‡ã‚£ã‚¿ãƒ¼ãŒãªã‚“ã§ã‚ã‚Œã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã¯ vi) ã‚’èµ·å‹•ã—ã¾ã™ã€‚ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã‚’è¿½åŠ ã—ã¾ã™ã€‚エディターセッションを終了ã™ã‚‹ã¨ã€ãƒ•ã‚¡ã‚¤ãƒ«ã¯æš—å·åŒ–ã•ã‚ŒãŸãƒ‡ãƒ¼ã‚¿ã¨ã—ã¦ä¿å˜ã•ã‚Œã¾ã™ã€‚ファイルã®ãƒ˜ãƒƒãƒ€ãƒ¼ã«ã¯ã€ä½œæˆæ™‚ã«ä½¿ç”¨ã—㟠Vault ID ãŒåæ˜ ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:310 +#: ../../rst/user_guide/vault.rst:320 msgid "To create a new encrypted data file with the vault ID 'my_new_password' assigned to it and be prompted for the password:" msgstr "Vault ID「my_new_passwordã€ãŒå‰²ã‚Šå½“ã¦ã‚‰ã‚ŒãŸæ–°ã—ã„æš—å·åŒ–データファイルを作æˆã—ã€ãƒ‘スワードã®å…¥åŠ›ã‚’求ã‚られるよã†ã«ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:316 +#: ../../rst/user_guide/vault.rst:326 msgid "Again, add content to the file in the editor and save. Be sure to store the new password you created at the prompt, so you can find it when you want to decrypt that file." msgstr "ã“ã“ã§ã‚‚ã€ã‚¨ãƒ‡ã‚£ã‚¿ãƒ¼ã®ãƒ•ã‚¡ã‚¤ãƒ«ã«ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã‚’è¿½åŠ ã—ã¦ä¿å˜ã—ã¾ã™ã€‚プãƒãƒ³ãƒ—トã§ä½œæˆã—ãŸæ–°ã—ã„パスワードを必ãšä¿å˜ã—ã€ãã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’復å·ã™ã‚‹ã¨ãã«è¦‹ã¤ã‘られるよã†ã«ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/vault.rst:321 +#: ../../rst/user_guide/vault.rst:331 msgid "Encrypting existing files" msgstr "æ—¢å˜ãƒ•ã‚¡ã‚¤ãƒ«ã®æš—å·åŒ–" -#: ../../rst/user_guide/vault.rst:323 +#: ../../rst/user_guide/vault.rst:333 msgid "To encrypt an existing file, use the :ref:`ansible-vault encrypt <ansible_vault_encrypt>` command. This command can operate on multiple files at once. For example:" msgstr "æ—¢å˜ãƒ•ã‚¡ã‚¤ãƒ«ã‚’æš—å·åŒ–ã™ã‚‹ã«ã¯ã€:ref:`ansible-vault encrypt <ansible_vault_encrypt>` コマンドを使用ã—ã¾ã™ã€‚ã“ã®ã‚³ãƒžãƒ³ãƒ‰ã¯ã€ä¸€åº¦ã«è¤‡æ•°ã®ãƒ•ã‚¡ã‚¤ãƒ«ã§å‹•ä½œã—ã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:329 +#: ../../rst/user_guide/vault.rst:339 msgid "To encrypt existing files with the 'project' ID and be prompted for the password:" msgstr "「プãƒã‚¸ã‚§ã‚¯ãƒˆã€IDã§æ—¢å˜ã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’æš—å·åŒ–ã—ã€ãƒ‘スワードã®å…¥åŠ›ã‚’求ã‚るプãƒãƒ³ãƒ—トを表示ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:339 +#: ../../rst/user_guide/vault.rst:349 msgid "Viewing encrypted files" msgstr "æš—å·åŒ–ã—ãŸãƒ•ã‚¡ã‚¤ãƒ«ã®è¡¨ç¤º" -#: ../../rst/user_guide/vault.rst:341 +#: ../../rst/user_guide/vault.rst:351 msgid "To view the contents of an encrypted file without editing it, you can use the :ref:`ansible-vault view <ansible_vault_view>` command:" msgstr "æš—å·åŒ–ã—ãŸãƒ•ã‚¡ã‚¤ãƒ«ã®å†…容を編集ã›ãšã«è¡¨ç¤ºã™ã‚‹å ´åˆã¯ã€:ref:`ansible-vault view <ansible_vault_view>` コマンドを使用ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:351 +#: ../../rst/user_guide/vault.rst:361 msgid "Editing encrypted files" msgstr "æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã®ç·¨é›†" -#: ../../rst/user_guide/vault.rst:353 +#: ../../rst/user_guide/vault.rst:363 msgid "To edit an encrypted file in place, use the :ref:`ansible-vault edit <ansible_vault_edit>` command. This command decrypts the file to a temporary file, allows you to edit the content, then saves and re-encrypts the content and removes the temporary file when you close the editor. For example:" msgstr "æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã‚’ãã®å ´ã§ç·¨é›†ã™ã‚‹ã«ã¯ã€:ref:`ansible-vault edit <ansible_vault_edit>` コマンドを使用ã—ã¾ã™ã€‚ã“ã®ã‚³ãƒžãƒ³ãƒ‰ã¯ã€ãƒ•ã‚¡ã‚¤ãƒ«ã‚’一時的ãªãƒ•ã‚¡ã‚¤ãƒ«ã«å¾©å·ã—ã€å†…容を編集ã§ãるよã†ã«ã—ãŸå¾Œã€å†…容をä¿å˜ã—ã¦å†åº¦æš—å·åŒ–ã—ã€ã‚¨ãƒ‡ã‚£ã‚¿ãƒ¼ã‚’é–‰ã˜ã‚‹ã¨ãã«ä¸€æ™‚çš„ãªãƒ•ã‚¡ã‚¤ãƒ«ã‚’削除ã—ã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:359 +#: ../../rst/user_guide/vault.rst:369 msgid "To edit a file encrypted with the ``vault2`` password file and assigned the vault ID ``pass2``:" msgstr "「``vault2``ã€ãƒ‘スワードファイルã§æš—å·åŒ–ã•ã‚Œã€Vault ID「``pass2``ã€ã‚’割り当ã¦ãŸãƒ•ã‚¡ã‚¤ãƒ«ã‚’編集ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:369 +#: ../../rst/user_guide/vault.rst:379 msgid "Changing the password and/or vault ID on encrypted files" msgstr "æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã®ãƒ‘スワードã¾ãŸã¯ Vault ID ã®å¤‰æ›´" -#: ../../rst/user_guide/vault.rst:371 +#: ../../rst/user_guide/vault.rst:381 msgid "To change the password on an encrypted file or files, use the :ref:`rekey <ansible_vault_rekey>` command:" msgstr "æš—å·åŒ–ã•ã‚ŒãŸ 1 ã¤ã¾ãŸã¯è¤‡æ•°ã®ãƒ•ã‚¡ã‚¤ãƒ«ã®ãƒ‘スワードを変更ã™ã‚‹ã«ã¯ã€:ref:`rekey <ansible_vault_rekey>` コマンドを使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:377 +#: ../../rst/user_guide/vault.rst:387 msgid "This command can rekey multiple data files at once and will ask for the original password and also the new password. To set a different ID for the rekeyed files, pass the new ID to ``--new-vault-id``. For example, to rekey a list of files encrypted with the 'preprod1' vault ID from the 'ppold' file to the 'preprod2' vault ID and be prompted for the new password:" msgstr "ã“ã®ã‚³ãƒžãƒ³ãƒ‰ã¯ã€è¤‡æ•°ã®ãƒ‡ãƒ¼ã‚¿ãƒ•ã‚¡ã‚¤ãƒ«ã®éµã‚’一度ã«å†è¨å®šã™ã‚‹ã“ã¨ãŒã§ãã€å…ƒã®ãƒ‘スワードã¨æ–°ã—ã„パスワードをè¦æ±‚ã—ã¾ã™ã€‚éµã‚’一度ã«å†è¨å®šã—ãŸãƒ•ã‚¡ã‚¤ãƒ«ã«åˆ¥ã® ID ã‚’è¨å®šã™ã‚‹ã«ã¯ã€æ–°ã—ã„ ID ã‚’ ``--new-vault-id`` ã«æ¸¡ã—ã¾ã™ã€‚ãŸã¨ãˆã°ã€ã€Œppoldã€ãƒ•ã‚¡ã‚¤ãƒ«ã‹ã‚‰ã€Œpreprod1ã€ã® Vault ID ã§æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã®ãƒªã‚¹ãƒˆã§ Vault ID「preprod2ã€ã«éµã‚’å†è¨å®šã—ã€æ–°ã—ã„パスワードã®å…¥åŠ›ã‚’求ã‚ã‚‹å ´åˆã§ã™ã€‚" -#: ../../rst/user_guide/vault.rst:387 +#: ../../rst/user_guide/vault.rst:397 msgid "Decrypting encrypted files" msgstr "æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã®å¾©å·åŒ–" -#: ../../rst/user_guide/vault.rst:389 +#: ../../rst/user_guide/vault.rst:399 msgid "If you have an encrypted file that you no longer want to keep encrypted, you can permanently decrypt it by running the :ref:`ansible-vault decrypt <ansible_vault_decrypt>` command. This command will save the file unencrypted to the disk, so be sure you do not want to :ref:`edit <ansible_vault_edit>` it instead." msgstr "æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ãŒã‚ã‚Šã€ãã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’æš—å·åŒ–ã—ãŸã¾ã¾ã«ã—ã¦ãŠããŸããªã„å ´åˆã¯ã€:ref:`ansible-vault decrypt <ansible_vault_decrypt>` コマンドを実行ã™ã‚‹ã“ã¨ã§æ°¸ä¹…ã«æš—å·åŒ–を解除ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã®ã‚³ãƒžãƒ³ãƒ‰ã¯æš—å·åŒ–ã•ã‚Œã¦ã„ãªã„ファイルをディスクã«ä¿å˜ã™ã‚‹ãŸã‚ã€ä»£ã‚ã‚Šã« :ref:`edit <ansible_vault_edit>` を使用ã—ãªã„よã†ã«ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/vault.rst:399 +#: ../../rst/user_guide/vault.rst:409 msgid "Steps to secure your editor" msgstr "エディターを確ä¿ã™ã‚‹ãŸã‚ã®æ‰‹é †" -#: ../../rst/user_guide/vault.rst:401 +#: ../../rst/user_guide/vault.rst:411 msgid "Ansible Vault relies on your configured editor, which can be a source of disclosures. Most editors have ways to prevent loss of data, but these normally rely on extra plain text files that can have a clear text copy of your secrets. Consult your editor documentation to configure the editor to avoid disclosing secure data. The following sections provide some guidance on common editors but should not be taken as a complete guide to securing your editor." msgstr "Ansible Vault ã¯ã€è¨å®šã•ã‚ŒãŸã‚¨ãƒ‡ã‚£ã‚¿ãƒ¼ã«ä¾å˜ã—ã¦ãŠã‚Šã€ã“ã‚ŒãŒæƒ…å ±æ¼ãˆã„ã®åŽŸå› ã¨ãªã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ã»ã¨ã‚“ã©ã®ã‚¨ãƒ‡ã‚£ã‚¿ãƒ¼ã«ã¯ã€ãƒ‡ãƒ¼ã‚¿ã®æ失を防ã方法ãŒã‚ã‚Šã¾ã™ãŒã€é€šå¸¸ã¯ã€ç§˜å¯†ã®ã‚³ãƒ”ーãŒå¹³æ–‡ã§ä¿å˜ã•ã‚Œã¦ã„ã‚‹å¯èƒ½æ€§ã®ã‚ã‚‹è¿½åŠ ã®å¹³æ–‡ãƒ•ã‚¡ã‚¤ãƒ«ã«ä¾å˜ã—ã¦ã„ã¾ã™ã€‚エディターã®ãƒ‰ã‚ュメントをå‚ç…§ã—ã¦ã€ã‚»ã‚ュアãªãƒ‡ãƒ¼ã‚¿ã®é–‹ç¤ºã‚’回é¿ã™ã‚‹ã‚ˆã†ã«ã‚¨ãƒ‡ã‚£ã‚¿ãƒ¼ã‚’è¨å®šã—ã¦ãã ã•ã„。以下ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã¯ã€ä¸€èˆ¬çš„ãªã‚¨ãƒ‡ã‚£ã‚¿ãƒ¼ã«é–¢ã™ã‚‹ã‚¬ã‚¤ãƒ€ãƒ³ã‚¹ã‚’æä¾›ã—ã¦ã„ã¾ã™ãŒã€ã‚¨ãƒ‡ã‚£ã‚¿ãƒ¼ã®ã‚»ã‚ュリティーを確ä¿ã™ã‚‹ãŸã‚ã®å®Œå…¨ãªã‚¬ã‚¤ãƒ‰ã¨è€ƒãˆã‚‹ã¹ãã§ã¯ã‚ã‚Šã¾ã›ã‚“。" -#: ../../rst/user_guide/vault.rst:405 +#: ../../rst/user_guide/vault.rst:415 msgid "vim" msgstr "vim" -#: ../../rst/user_guide/vault.rst:407 +#: ../../rst/user_guide/vault.rst:417 msgid "You can set the following ``vim`` options in command mode to avoid cases of disclosure. There may be more settings you need to modify to ensure security, especially when using plugins, so consult the ``vim`` documentation." msgstr "以下㮠``vim`` オプションをコマンドモードã§è¨å®šã™ã‚‹ã“ã¨ã§ã€æƒ…å ±æ¼ãˆã„ã®ã‚±ãƒ¼ã‚¹ã‚’回é¿ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚特ã«ãƒ—ラグインを使用ã—ã¦ã„ã‚‹å ´åˆãªã©ã€ã‚»ã‚ュリティーを確ä¿ã™ã‚‹ãŸã‚ã«å¤‰æ›´ã—ãªã‘ã‚Œã°ãªã‚‰ãªã„è¨å®šãŒä»–ã«ã‚‚ã‚ã‚‹ã‹ã‚‚ã—ã‚Œãªã„ãŸã‚ã€``vim`` ã®ãƒ‰ã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/vault.rst:410 +#: ../../rst/user_guide/vault.rst:420 msgid "Disable swapfiles that act like an autosave in case of crash or interruption." msgstr "クラッシュã¾ãŸã¯ä¸æ–ãŒç™ºç”Ÿã—ãŸå ´åˆã«è‡ªå‹•ä¿å˜ã¨ã—ã¦æ©Ÿèƒ½ã™ã‚‹ swapfiles を無効ã«ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:416 ../../rst/user_guide/vault.rst:450 +#: ../../rst/user_guide/vault.rst:426 ../../rst/user_guide/vault.rst:460 msgid "Disable creation of backup files." msgstr "ãƒãƒƒã‚¯ã‚¢ãƒƒãƒ—ファイルã®ä½œæˆã‚’無効ã«ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:423 +#: ../../rst/user_guide/vault.rst:433 msgid "Disable the viminfo file from copying data from your current session." msgstr "viminfo ファイルを無効ã«ã—ã¦ã€ç¾åœ¨ã®ã‚»ãƒƒã‚·ãƒ§ãƒ³ã‹ã‚‰ãƒ‡ãƒ¼ã‚¿ã‚’コピーã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:429 +#: ../../rst/user_guide/vault.rst:439 msgid "Disable copying to the system clipboard." msgstr "システムクリップボードã¸ã®ã‚³ãƒ”ーを無効ã«ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:436 +#: ../../rst/user_guide/vault.rst:446 msgid "You can optionally add these settings in ``.vimrc`` for all files, or just specific paths or extensions. See the ``vim`` manual for details." msgstr "å¿…è¦ã«å¿œã˜ã¦ã€ã™ã¹ã¦ã®ãƒ•ã‚¡ã‚¤ãƒ«ã¾ãŸã¯ç‰¹å®šã®ãƒ‘スã¾ãŸã¯æ‹¡å¼µã® ``.vimrc`` ã«ã“れらã®è¨å®šã‚’è¿½åŠ ã§ãã¾ã™ã€‚詳細ã¯ã€``vim`` マニュアルをå‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/vault.rst:440 +#: ../../rst/user_guide/vault.rst:450 msgid "Emacs" msgstr "Emacs" -#: ../../rst/user_guide/vault.rst:442 +#: ../../rst/user_guide/vault.rst:452 msgid "You can set the following Emacs options to avoid cases of disclosure. There may be more settings you need to modify to ensure security, especially when using plugins, so consult the Emacs documentation." msgstr "以下㮠Emacs オプションをè¨å®šã™ã‚‹ã“ã¨ã§ã€æƒ…å ±æ¼ãˆã„を回é¿ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚特ã«ãƒ—ラグインを使用ã™ã‚‹å ´åˆã¯ã€ã‚»ã‚ュリティーを確ä¿ã™ã‚‹ãŸã‚ã«å¤‰æ›´ã™ã‚‹å¿…è¦ãŒã‚ã‚‹è¨å®šãŒä»–ã«ã‚‚ã‚ã‚‹ã‹ã‚‚ã—ã‚Œãªã„ãŸã‚ã€Emacs ã®ãƒ‰ã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/vault.rst:444 +#: ../../rst/user_guide/vault.rst:454 msgid "Do not copy data to the system clipboard." msgstr "データをシステムクリップボードã«ã‚³ãƒ”ーã—ãªã„ã§ãã ã•ã„。" -#: ../../rst/user_guide/vault.rst:456 +#: ../../rst/user_guide/vault.rst:466 msgid "Disable autosave files." msgstr "自動ä¿å˜ãƒ•ã‚¡ã‚¤ãƒ«ã‚’無効ã«ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:467 +#: ../../rst/user_guide/vault.rst:477 msgid "Using encrypted variables and files" msgstr "æš—å·åŒ–ã•ã‚ŒãŸå¤‰æ•°ã¨ãƒ•ã‚¡ã‚¤ãƒ«ã®ä½¿ç”¨" -#: ../../rst/user_guide/vault.rst:469 +#: ../../rst/user_guide/vault.rst:479 msgid "When you run a task or playbook that uses encrypted variables or files, you must provide the passwords to decrypt the variables or files. You can do this at the command line or in the playbook itself." msgstr "æš—å·åŒ–ã•ã‚ŒãŸå¤‰æ•°ã‚„ファイルを使用ã™ã‚‹ã‚¿ã‚¹ã‚¯ã‚„ Playbook を実行ã™ã‚‹éš›ã¯ã€å¤‰æ•°ã‚„ファイルを復å·ã™ã‚‹ãŸã‚ã®ãƒ‘スワードをæä¾›ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã¾ãŸã¯ Playbook ã®ä¸ã§è¡Œã†ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:472 +#: ../../rst/user_guide/vault.rst:482 msgid "Passing a single password" msgstr "å˜ä¸€ã®ãƒ‘スワードを渡ã™" -#: ../../rst/user_guide/vault.rst:474 +#: ../../rst/user_guide/vault.rst:484 msgid "If all the encrypted variables and files your task or playbook needs use a single password, you can use the :option:`--ask-vault-pass <ansible-playbook --ask-vault-pass>` or :option:`--vault-password-file <ansible-playbook --vault-password-file>` cli options." msgstr "タスクや Playbook ãŒå¿…è¦ã¨ã™ã‚‹ã™ã¹ã¦ã®æš—å·åŒ–ã•ã‚ŒãŸå¤‰æ•°ã‚„ファイルãŒå˜ä¸€ã®ãƒ‘スワードを使用ã™ã‚‹å ´åˆã¯ã€CLI オプション :option:`--ask-vault-pass <ansible-playbook --ask-vault-pass>` ã¾ãŸã¯ :option:`--vault-password-file <ansible-playbook --vault-password-file>` を使用ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:476 ../../rst/user_guide/vault.rst:544 +#: ../../rst/user_guide/vault.rst:486 ../../rst/user_guide/vault.rst:554 msgid "To prompt for the password:" msgstr "パスワードをè¦æ±‚ã™ã‚‹å ´åˆã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:482 +#: ../../rst/user_guide/vault.rst:492 msgid "To retrieve the password from the :file:`/path/to/my/vault-password-file` file:" msgstr ":file:`/path/to/my/vault-password-file` ファイルã‹ã‚‰ãƒ‘スワードをå–å¾—ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:488 +#: ../../rst/user_guide/vault.rst:498 msgid "To get the password from the vault password client script :file:`my-vault-password-client.py`:" msgstr "Vault パスワードクライアントスクリプト :file:`my-vault-password-client.py` ã‹ã‚‰ Vault パスワードをå–å¾—ã™ã‚‹å ´åˆã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:498 +#: ../../rst/user_guide/vault.rst:508 msgid "Passing vault IDs" msgstr "Vault ID を渡ã™" -#: ../../rst/user_guide/vault.rst:500 +#: ../../rst/user_guide/vault.rst:510 msgid "You can also use the :option:`--vault-id <ansible-playbook --vault-id>` option to pass a single password with its vault label. This approach is clearer when multiple vaults are used within a single inventory." msgstr ":option:`--vault-id <ansible-playbook --vault-id>` オプションを使用ã—ã¦ã€Vault ラベルã§å˜ä¸€ã®ãƒ‘スワードを渡ã™ã“ã¨ã‚‚ã§ãã¾ã™ã€‚ã“ã®æ–¹æ³•ã¯ã€1 ã¤ã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼å†…ã§è¤‡æ•°ã® vault を使用ã—ã¦ã„ã‚‹å ´åˆã¯ã‚ˆã‚Šæ˜Žç¢ºã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:502 +#: ../../rst/user_guide/vault.rst:512 msgid "To prompt for the password for the 'dev' vault ID:" msgstr "Vault ID「devã€ã®ãƒ‘スワードをè¦æ±‚ã™ã‚‹å ´åˆã¯ã€æ¬¡ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:508 +#: ../../rst/user_guide/vault.rst:518 msgid "To retrieve the password for the 'dev' vault ID from the :file:`dev-password` file:" msgstr "「devã€ã® Vault ID ã®ãƒ‘スワードを :file:`dev-password` ã®ãƒ•ã‚¡ã‚¤ãƒ«ã‹ã‚‰å–å¾—ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:514 +#: ../../rst/user_guide/vault.rst:524 msgid "To get the password for the 'dev' vault ID from the vault password client script :file:`my-vault-password-client.py`:" msgstr "Vault パスワードクライアントスクリプト :file:`my-vault-password-client.py` ã‹ã‚‰ Vault ID 「devã€ã®ãƒ‘スワードをå–å¾—ã™ã‚‹å ´åˆã¯ã€ä»¥ä¸‹ã‚’è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:521 +#: ../../rst/user_guide/vault.rst:531 msgid "Passing multiple vault passwords" msgstr "複数㮠Vault パスワードを渡ã™" -#: ../../rst/user_guide/vault.rst:523 +#: ../../rst/user_guide/vault.rst:533 msgid "If your task or playbook requires multiple encrypted variables or files that you encrypted with different vault IDs, you must use the :option:`--vault-id <ansible-playbook --vault-id>` option, passing multiple ``--vault-id`` options to specify the vault IDs ('dev', 'prod', 'cloud', 'db') and sources for the passwords (prompt, file, script). . For example, to use a 'dev' password read from a file and to be prompted for the 'prod' password:" msgstr "タスクや Playbook ã§ã€ç•°ãªã‚‹ Vault ID ã§æš—å·åŒ–ã—ãŸè¤‡æ•°ã®æš—å·åŒ–変数やファイルãŒå¿…è¦ãªå ´åˆã¯ã€:option:`--vault-id <ansible-playbook --vault-id>` オプションを使用ã—ã€è¤‡æ•°ã® ``--vault-id`` オプションを渡ã—㦠Vault ID (「devã€ã€ã€Œprodã€ã€ã€Œcloudã€ã€ã€Œdbã€) ã¨ãƒ‘スワードã®ã‚½ãƒ¼ã‚¹ (プãƒãƒ³ãƒ—トã€ãƒ•ã‚¡ã‚¤ãƒ«ã€ã‚¹ã‚¯ãƒªãƒ—ト) を指定ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€ãƒ•ã‚¡ã‚¤ãƒ«ã‹ã‚‰èªã¿è¾¼ã‚“ã 「devã€ã®ãƒ‘スワードを使用ã—ã€ã€Œprodã€ã®ãƒ‘スワードを求ã‚るプãƒãƒ³ãƒ—トを表示ã™ã‚‹å ´åˆãªã©ã§ã™ã€‚" -#: ../../rst/user_guide/vault.rst:529 +#: ../../rst/user_guide/vault.rst:539 msgid "By default the vault ID labels (dev, prod and so on) are only hints. Ansible attempts to decrypt vault content with each password. The password with the same label as the encrypted data will be tried first, after that each vault secret will be tried in the order they were provided on the command line." msgstr "デフォルトã§ã¯ã€Vault ID ラベル (devã€prodãªã©) ã¯ãƒ’ントã§ã—ã‹ã‚ã‚Šã¾ã›ã‚“。Ansible ã¯ã€å„パスワード㧠Vault ã®ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã®å¾©å·ã‚’試ã¿ã¾ã™ã€‚æš—å·åŒ–ã•ã‚ŒãŸãƒ‡ãƒ¼ã‚¿ã¨åŒã˜ãƒ©ãƒ™ãƒ«ã®ãƒ‘スワードãŒæœ€åˆã«è©¦è¡Œã•ã‚Œã€ãã®å¾Œã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã§æŒ‡å®šã•ã‚ŒãŸé †ã«å„ Vault シークレットãŒè©¦è¡Œã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:531 +#: ../../rst/user_guide/vault.rst:541 msgid "Where the encrypted data has no label, or the label does not match any of the provided labels, the passwords will be tried in the order they are specified. In the example above, the 'dev' password will be tried first, then the 'prod' password for cases where Ansible doesn't know which vault ID is used to encrypt something." msgstr "æš—å·åŒ–ã•ã‚ŒãŸãƒ‡ãƒ¼ã‚¿ã«ãƒ©ãƒ™ãƒ«ãŒãªã„å ´åˆã€ã¾ãŸã¯ãƒ©ãƒ™ãƒ«ãŒã€æä¾›ã•ã‚ŒãŸãƒ©ãƒ™ãƒ«ã®ã©ã‚Œã¨ã‚‚一致ã—ãªã„å ´åˆã€ãƒ‘スワードã¯æŒ‡å®šã•ã‚ŒãŸé †ã«è©¦è¡Œã•ã‚Œã¾ã™ã€‚上ã®ä¾‹ã§ã¯ã€ã€Œdevã€ãƒ‘スワードãŒæœ€åˆã«è©¦è¡Œã•ã‚Œã€æ¬¡ã«ã€Œprodã€ãƒ‘スワードãŒè©¦è¡Œã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ã€Ansible ãŒã©ã® Vault ID ãŒä½•ã‹ã®æš—å·åŒ–ã«ä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹ã‹ã‚’知らãªã„å ´åˆã«è¡Œã‚ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:534 +#: ../../rst/user_guide/vault.rst:544 msgid "Using ``--vault-id`` without a vault ID" msgstr "Vault ID ãªã—㧠``--vault-id`` を使用" -#: ../../rst/user_guide/vault.rst:536 +#: ../../rst/user_guide/vault.rst:546 msgid "The :option:`--vault-id <ansible-playbook --vault-id>` option can also be used without specifying a vault-id. This behavior is equivalent to :option:`--ask-vault-pass <ansible-playbook --ask-vault-pass>` or :option:`--vault-password-file <ansible-playbook --vault-password-file>` so is rarely used." msgstr ":option:`--vault-id <ansible-playbook --vault-id>` オプションã¯ã€vault-id を指定ã›ãšã«ä½¿ç”¨ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚ã“ã®å‹•ä½œã¯ :option:`--ask-vault-pass <ansible-playbook --ask-vault-pass>` ã¾ãŸã¯ :option:`--vault-password-file <ansible-playbook --vault-password-file>` ã¨åŒç‰ã§ã‚ã‚‹ãŸã‚ã€ã»ã¨ã‚“ã©ä½¿ç”¨ã•ã‚Œã¾ã›ã‚“。" -#: ../../rst/user_guide/vault.rst:538 +#: ../../rst/user_guide/vault.rst:548 msgid "For example, to use a password file :file:`dev-password`:" msgstr "ãŸã¨ãˆã°ã€ãƒ‘スワードファイル :file:`dev-password` を使用ã™ã‚‹å ´åˆã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:550 +#: ../../rst/user_guide/vault.rst:560 msgid "To get the password from an executable script :file:`my-vault-password-client.py`:" msgstr "実行スクリプト :file:`my-vault-password-client.py` ã‹ã‚‰ãƒ‘スワードをå–å¾—ã™ã‚‹å ´åˆã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:558 +#: ../../rst/user_guide/vault.rst:568 msgid "Configuring defaults for using encrypted content" msgstr "æš—å·åŒ–ã•ã‚ŒãŸã‚³ãƒ³ãƒ†ãƒ³ãƒ„を使用ã™ã‚‹ãŸã‚ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã®è¨å®š" -#: ../../rst/user_guide/vault.rst:561 +#: ../../rst/user_guide/vault.rst:571 msgid "Setting a default vault ID" msgstr "デフォルト㮠Vault ID ã®è¨å®š" -#: ../../rst/user_guide/vault.rst:563 +#: ../../rst/user_guide/vault.rst:573 msgid "If you use one vault ID more frequently than any other, you can set the config option :ref:`DEFAULT_VAULT_IDENTITY_LIST` to specify a default vault ID and password source. Ansible will use the default vault ID and source any time you do not specify :option:`--vault-id <ansible-playbook --vault-id>`. You can set multiple values for this option. Setting multiple values is equivalent to passing multiple :option:`--vault-id <ansible-playbook --vault-id>` cli options." msgstr "ã‚ã‚‹ Vault ID ã‚’ä»–ã® Vault IDよ ã‚Šã‚‚é »ç¹ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€è¨å®šã‚ªãƒ—ション :ref:`DEFAULT_VAULT_IDENTITY_LIST` ã‚’è¨å®šã—ã¦ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã® Vault ID ã¨ãƒ‘スワードソースを指定ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚Ansible ã¯ã€:option:`--vault-id <ansible-playbook --vault-id>` を指定ã—ãªã„å ´åˆã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã® Vault ID ã¨ã‚½ãƒ¼ã‚¹ã‚’使用ã—ã¾ã™ã€‚ã“ã®ã‚ªãƒ—ションã«ã¯è¤‡æ•°ã®å€¤ã‚’è¨å®šã§ãã¾ã™ã€‚複数ã®å€¤ã‚’è¨å®šã™ã‚‹ã“ã¨ã¯ã€è¤‡æ•°ã® CLI オプション :option:`--vault-id <ansible-playbook --vault-id>` を渡ã™ã“ã¨ã¨åŒã˜ã§ã™ã€‚" -#: ../../rst/user_guide/vault.rst:566 +#: ../../rst/user_guide/vault.rst:576 msgid "Setting a default password source" msgstr "デフォルトã®ãƒ‘スワードソースã®è¨å®š" -#: ../../rst/user_guide/vault.rst:568 +#: ../../rst/user_guide/vault.rst:578 msgid "If you use one vault password file more frequently than any other, you can set the :ref:`DEFAULT_VAULT_PASSWORD_FILE` config option or the :envvar:`ANSIBLE_VAULT_PASSWORD_FILE` environment variable to specify that file. For example, if you set ``ANSIBLE_VAULT_PASSWORD_FILE=~/.vault_pass.txt``, Ansible will automatically search for the password in that file. This is useful if, for example, you use Ansible from a continuous integration system such as Jenkins." msgstr "ã‚ã‚‹ Vault パスワードファイルを他ã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚ˆã‚Šã‚‚é »ç¹ã«ä½¿ç”¨ã™ã‚‹å ´åˆã¯ã€:ref:`DEFAULT_VAULT_PASSWORD_FILE` è¨å®šã‚ªãƒ—ションã¾ãŸã¯ç’°å¢ƒå¤‰æ•° :envvar:`ANSIBLE_VAULT_PASSWORD_FILE` ã‚’è¨å®šã—ã¦ã€ãã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’指定ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãŸã¨ãˆã°ã€``ANSIBLE_VAULT_PASSWORD_FILE=~/.vault_pass.txt`` ã‚’è¨å®šã™ã‚‹ã¨ã€Ansible ã¯è‡ªå‹•çš„ã«ãã®ãƒ•ã‚¡ã‚¤ãƒ«å†…ã®ãƒ‘スワードを検索ã—ã¾ã™ã€‚ã“ã‚Œã¯ã€ãŸã¨ãˆã°ã€Jenkins ãªã©ã®ç¶™ç¶šçš„çµ±åˆã‚·ã‚¹ãƒ†ãƒ ã‹ã‚‰ Ansible を使用ã™ã‚‹å ´åˆã«ä¾¿åˆ©ã§ã™ã€‚" -#: ../../rst/user_guide/vault.rst:571 +#: ../../rst/user_guide/vault.rst:581 msgid "When are encrypted files made visible?" msgstr "æš—å·åŒ–ファイルをã„ã¤è¡¨ç¤ºã™ã‚‹ã‹ã€‚" -#: ../../rst/user_guide/vault.rst:573 +#: ../../rst/user_guide/vault.rst:583 msgid "In general, content you encrypt with Ansible Vault remains encrypted after execution. However, there is one exception. If you pass an encrypted file as the ``src`` argument to the :ref:`copy <copy_module>`, :ref:`template <template_module>`, :ref:`unarchive <unarchive_module>`, :ref:`script <script_module>` or :ref:`assemble <assemble_module>` module, the file will not be encrypted on the target host (assuming you supply the correct vault password when you run the play). This behavior is intended and useful. You can encrypt a configuration file or template to avoid sharing the details of your configuration, but when you copy that configuration to servers in your environment, you want it to be decrypted so local users and processes can access it." msgstr "一般的ã«ã€Ansible Vault ã§æš—å·åŒ–ã—ãŸã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã¯ã€å®Ÿè¡Œå¾Œã‚‚æš—å·åŒ–ã•ã‚ŒãŸã¾ã¾ã§ã™ã€‚ãŸã ã—ã€1 ã¤ã ã‘例外ãŒã‚ã‚Šã¾ã™ã€‚:ref:`copy <copy_module>` モジュールã€:ref:`template <template_module>` モジュールã€:ref:`unarchive <unarchive_module>` モジュールã€:ref:`script <script_module>` モジュールã€ã¾ãŸã¯ :ref:`assemble <assemble_module>` モジュールã¸ã® ``src`` 引数ã¨ã—ã¦æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã‚’渡ã—ãŸå ´åˆã€ãã®ãƒ•ã‚¡ã‚¤ãƒ«ã¯ã‚¿ãƒ¼ã‚²ãƒƒãƒˆãƒ›ã‚¹ãƒˆä¸Šã§ã¯æš—å·åŒ–ã•ã‚Œã¾ã›ã‚“ (プレイã®å®Ÿè¡Œæ™‚ã«æ£ã—ã„ Vault パスワードを供給ã—ã¦ã„ã‚‹ã“ã¨ãŒå‰æã§ã™)。ã“ã®å‹•ä½œã¯æ„図ã•ã‚ŒãŸã‚‚ã®ã§ã‚ã‚Šã€ä¾¿åˆ©ãªã‚‚ã®ã§ã™ã€‚è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã‚„テンプレートを暗å·åŒ–ã—ã¦ã€è¨å®šã®è©³ç´°ã‚’共有ã—ãªã„よã†ã«ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ãŒã€ãã®è¨å®šã‚’環境内ã®ã‚µãƒ¼ãƒãƒ¼ã«ã‚³ãƒ”ーã™ã‚‹ã¨ãã¯ã€ãƒãƒ¼ã‚«ãƒ«ã®ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚„プãƒã‚»ã‚¹ãŒã‚¢ã‚¯ã‚»ã‚¹ã§ãるよã†ã«ã€æš—å·åŒ–を解除ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:578 +#: ../../rst/user_guide/vault.rst:588 msgid "Format of files encrypted with Ansible Vault" msgstr "Ansible Vault ã§æš—å·åŒ–ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã®å½¢å¼" -#: ../../rst/user_guide/vault.rst:580 -msgid "Ansible Vault creates UTF-8 encoded txt files. The file format includes a newline terminated header. For example::" +#: ../../rst/user_guide/vault.rst:590 +msgid "Ansible Vault creates UTF-8 encoded txt files. The file format includes a newline terminated header. For example:" msgstr "Ansible Vault ã¯ã€UTF-8 ã§ã‚¨ãƒ³ã‚³ãƒ¼ãƒ‰ã•ã‚ŒãŸãƒ†ã‚ストファイルを作æˆã—ã¾ã™ã€‚ファイル形å¼ã«ã¯ã€æ”¹è¡Œã§çµ‚了ã™ã‚‹ãƒ˜ãƒƒãƒ€ãƒ¼ãŒå«ã¾ã‚Œã¾ã™ã€‚以下ã«ä¾‹ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:584 -msgid "or::" -msgstr "ã¾ãŸã¯::" +#: ../../rst/user_guide/vault.rst:596 +msgid "or" +msgstr "ã¾ãŸã¯" -#: ../../rst/user_guide/vault.rst:588 +#: ../../rst/user_guide/vault.rst:602 msgid "The header contains up to four elements, separated by semi-colons (``;``)." msgstr "ヘッダーã«ã¯ã€ã‚»ãƒŸã‚³ãƒãƒ³ (``;``) ã§åŒºåˆ‡ã‚‰ã‚ŒãŸæœ€å¤§ 4 ã¤ã®è¦ç´ ãŒå«ã¾ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:590 +#: ../../rst/user_guide/vault.rst:604 msgid "The format ID (``$ANSIBLE_VAULT``). Currently ``$ANSIBLE_VAULT`` is the only valid format ID. The format ID identifies content that is encrypted with Ansible Vault (via vault.is_encrypted_file())." msgstr "å½¢å¼ ID (``$ANSIBLE_VAULT``)。ç¾åœ¨ã€``$ANSIBLE_VAULT`` ã¯å”¯ä¸€ã®æœ‰åŠ¹ãªå½¢å¼ ID ã§ã™ã€‚フォーマット ID ã¯ã€(vault.is_encrypted_file() を介ã—ã¦) Ansible Vault ã§æš—å·åŒ–ã•ã‚Œã¦ã„るコンテンツをè˜åˆ¥ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:592 +#: ../../rst/user_guide/vault.rst:606 msgid "The vault format version (``1.X``). All supported versions of Ansible will currently default to '1.1' or '1.2' if a labeled vault ID is supplied. The '1.0' format is supported for reading only (and will be converted automatically to the '1.1' format on write). The format version is currently used as an exact string compare only (version numbers are not currently 'compared')." msgstr "Vault å½¢å¼ãƒãƒ¼ã‚¸ãƒ§ãƒ³ (``1.X``) ã§ã™ã€‚ç¾åœ¨ã€ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã‚‹ã™ã¹ã¦ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Ansible ã§ã¯ã€ãƒ©ãƒ™ãƒ«ä»˜ãã® Vault IDãŒæŒ‡å®šã•ã‚ŒãŸå ´åˆã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã€Œ1.1ã€ã¾ãŸã¯ã€Œ1.2ã€ã«ãªã‚Šã¾ã™ã€‚「1.0ã€å½¢å¼ã¯èªã¿è¾¼ã¿ã®ã¿ã‚µãƒãƒ¼ãƒˆã—ã¦ã„ã¾ã™ (書ãè¾¼ã¿æ™‚ã«ã¯è‡ªå‹•çš„ã«ã€Œ1.1ã€å½¢å¼ã«å¤‰æ›ã•ã‚Œã¾ã™)。形å¼ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯ã€ç¾åœ¨ã€æ£ç¢ºãªæ–‡å—列ã®æ¯”較ã¨ã—ã¦ã®ã¿ä½¿ç”¨ã•ã‚Œã¦ã„ã¾ã™ (ãƒãƒ¼ã‚¸ãƒ§ãƒ³ç•ªå·ã¯ç¾åœ¨ã€Œæ¯”較ã€ã•ã‚Œã¾ã›ã‚“)。" -#: ../../rst/user_guide/vault.rst:594 +#: ../../rst/user_guide/vault.rst:608 msgid "The cipher algorithm used to encrypt the data (``AES256``). Currently ``AES256`` is the only supported cipher algorithm. Vault format 1.0 used 'AES', but current code always uses 'AES256'." msgstr "データã®æš—å·åŒ–ã«ä½¿ç”¨ã•ã‚Œã‚‹æš—å·ã‚¢ãƒ«ã‚´ãƒªã‚ºãƒ (``AES256``)。ç¾åœ¨ã€``AES256`` ãŒå”¯ä¸€ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã‚‹æš—å·ã‚¢ãƒ«ã‚´ãƒªã‚ºãƒ ã§ã™ã€‚Vault å½¢å¼ 1.0 ã§ã¯ã€ŒAESã€ã‚’使用ã—ã¦ã„ã¾ã—ãŸãŒã€ç¾åœ¨ã®ã‚³ãƒ¼ãƒ‰ã§ã¯å¸¸ã«ã€ŒAES256ã€ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:596 +#: ../../rst/user_guide/vault.rst:610 msgid "The vault ID label used to encrypt the data (optional, ``vault-id-label``) For example, if you encrypt a file with ``--vault-id dev@prompt``, the vault-id-label is ``dev``." msgstr "データã®æš—å·åŒ–ã«ä½¿ç”¨ã•ã‚Œã‚‹ vault ID ラベル (ä»»æ„: ``vault-id-label``)。ãŸã¨ãˆã°ã€``--vault-id dev@prompt`` ã§ãƒ•ã‚¡ã‚¤ãƒ«ã‚’æš—å·åŒ–ã™ã‚‹å ´åˆã¯ã€vault-id-label ㌠``dev`` ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:598 +#: ../../rst/user_guide/vault.rst:612 msgid "Note: In the future, the header could change. Fields after the format ID and format version depend on the format version, and future vault format versions may add more cipher algorithm options and/or additional fields." msgstr "注: å°†æ¥çš„ã«ã¯ã€ãƒ˜ãƒƒãƒ€ãƒ¼ãŒå¤‰æ›´ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚å½¢å¼ ID ã¨å½¢å¼ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã®å¾Œã®ãƒ•ã‚£ãƒ¼ãƒ«ãƒ‰ã¯ã€å½¢å¼ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«ä¾å˜ã—ã¦ãŠã‚Šã€å°†æ¥ã® Vault å½¢å¼ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã¯ã€æš—å·ã‚¢ãƒ«ã‚´ãƒªã‚ºãƒ ã®ã‚ªãƒ—ションやフィールドãŒè¿½åŠ ã•ã‚Œã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:600 +#: ../../rst/user_guide/vault.rst:614 msgid "The rest of the content of the file is the 'vaulttext'. The vaulttext is a text armored version of the encrypted ciphertext. Each line is 80 characters wide, except for the last line which may be shorter." msgstr "ファイルã®æ®‹ã‚Šã®å†…容ã¯ã€Œvaulttextã€ã§ã™ã€‚vaulttext ã¯ã€æš—å·åŒ–ã•ã‚ŒãŸæš—å·æ–‡ã®ãƒ†ã‚スト版ã§ã™ã€‚å„è¡Œã®å¹…㯠80 æ–‡å—ã§ã™ã€‚ãŸã ã—ã€æœ€çµ‚è¡Œã¯çŸããªã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:604 +#: ../../rst/user_guide/vault.rst:618 msgid "Ansible Vault payload format 1.1 - 1.2" msgstr "Ansible Vault ペイãƒãƒ¼ãƒ‰å½¢å¼ 1.1 - 1.2" -#: ../../rst/user_guide/vault.rst:606 +#: ../../rst/user_guide/vault.rst:620 msgid "The vaulttext is a concatenation of the ciphertext and a SHA256 digest with the result 'hexlifyied'." msgstr "vaulttext ã¯ã€æš—å·åŒ–テã‚スト㨠SHA256 ダイジェストを連çµã—ãŸã‚‚ã®ã§ã€çµæžœã¯ã€Œhexlifyiedã€ã§ã™ã€‚" -#: ../../rst/user_guide/vault.rst:608 +#: ../../rst/user_guide/vault.rst:622 msgid "'hexlify' refers to the ``hexlify()`` method of the Python Standard Library's `binascii <https://docs.python.org/3/library/binascii.html>`_ module." msgstr "「hexlifyã€ã¯ã€Python 標準ライブラリー㮠`binascii <https://docs.python.org/3/library/binascii.html>`_ モジュール㮠``hexlify()`` メソッドを指ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:610 +#: ../../rst/user_guide/vault.rst:624 msgid "hexlify()'ed result of:" msgstr "hexlify() ãŒè¡Œã‚ã‚ŒãŸçµæžœ:" -#: ../../rst/user_guide/vault.rst:612 +#: ../../rst/user_guide/vault.rst:626 msgid "hexlify()'ed string of the salt, followed by a newline (``0x0a``)" msgstr "hexlify() ã§ç·¨é›†ã•ã‚ŒãŸã‚½ãƒ«ãƒˆã®æ–‡å—列ã¨ãã‚Œã«ç¶šã改行 (``0x0a``)。" -#: ../../rst/user_guide/vault.rst:613 +#: ../../rst/user_guide/vault.rst:627 msgid "hexlify()'ed string of the crypted HMAC, followed by a newline. The HMAC is:" msgstr "hexlify() ã§æš—å·åŒ–ã•ã‚ŒãŸ HMAC ã®æ–‡å—列ã®å¾Œã«ã€æ”¹è¡Œã‚’入れã¾ã™ã€‚ãã® HMAC ã¯ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:615 +#: ../../rst/user_guide/vault.rst:629 msgid "a `RFC2104 <https://www.ietf.org/rfc/rfc2104.txt>`_ style HMAC" msgstr "`RFC2104 <https://www.ietf.org/rfc/rfc2104.txt>`_ スタイル㮠HMAC" -#: ../../rst/user_guide/vault.rst:617 +#: ../../rst/user_guide/vault.rst:631 msgid "inputs are:" msgstr "入力ã¯æ¬¡ã®ã¨ãŠã‚Šã§ã™ã€‚" -#: ../../rst/user_guide/vault.rst:619 +#: ../../rst/user_guide/vault.rst:633 msgid "The AES256 encrypted ciphertext" msgstr "AES256 ã§æš—å·åŒ–ã—ãŸæš—å·æ–‡" -#: ../../rst/user_guide/vault.rst:620 +#: ../../rst/user_guide/vault.rst:634 msgid "A PBKDF2 key. This key, the cipher key, and the cipher IV are generated from:" msgstr "PBKDF2 ã‚ー。ã“ã®ã‚ーã€æš—å·ã‚ーã€ãŠã‚ˆã³æš—å· IV を生æˆã—ã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:622 +#: ../../rst/user_guide/vault.rst:636 msgid "the salt, in bytes" msgstr "ãƒã‚¤ãƒˆå˜ä½ã®ã‚½ãƒ«ãƒˆ" -#: ../../rst/user_guide/vault.rst:623 +#: ../../rst/user_guide/vault.rst:637 msgid "10000 iterations" msgstr "10000 回ã®ç¹°ã‚Šè¿”ã—" -#: ../../rst/user_guide/vault.rst:624 +#: ../../rst/user_guide/vault.rst:638 msgid "SHA256() algorithm" msgstr "SHA256() アルゴリズム" -#: ../../rst/user_guide/vault.rst:625 +#: ../../rst/user_guide/vault.rst:639 msgid "the first 32 bytes are the cipher key" msgstr "最åˆã® 32 ãƒã‚¤ãƒˆã¯æš—å·ã‚ーã§ã™ã€‚" -#: ../../rst/user_guide/vault.rst:626 +#: ../../rst/user_guide/vault.rst:640 msgid "the second 32 bytes are the HMAC key" msgstr "2 番目㮠32 ãƒã‚¤ãƒˆã¯ HMAC ã‚ーã§ã™ã€‚" -#: ../../rst/user_guide/vault.rst:627 +#: ../../rst/user_guide/vault.rst:641 msgid "remaining 16 bytes are the cipher IV" msgstr "残り㮠16 ãƒã‚¤ãƒˆã¯æš—å· IV ã§ã™ã€‚" -#: ../../rst/user_guide/vault.rst:629 +#: ../../rst/user_guide/vault.rst:643 msgid "hexlify()'ed string of the ciphertext. The ciphertext is:" msgstr "æš—å·æ–‡ã® hexlify() ãŒè¡Œã‚ã‚ŒãŸæ–‡å—列ã§ã™ã€‚æš—å·æ–‡ã¯ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:631 +#: ../../rst/user_guide/vault.rst:645 msgid "AES256 encrypted data. The data is encrypted using:" msgstr "AES256 ã§æš—å·åŒ–ã•ã‚ŒãŸãƒ‡ãƒ¼ã‚¿ã§ã™ã€‚データã¯æ¬¡ã‚’使用ã—ã¦æš—å·åŒ–ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/vault.rst:633 +#: ../../rst/user_guide/vault.rst:647 msgid "AES-CTR stream cipher" msgstr "AES-CTR ストリーム暗å·" -#: ../../rst/user_guide/vault.rst:634 +#: ../../rst/user_guide/vault.rst:648 msgid "cipher key" msgstr "æš—å·éµ" -#: ../../rst/user_guide/vault.rst:635 +#: ../../rst/user_guide/vault.rst:649 msgid "IV" msgstr "IV" -#: ../../rst/user_guide/vault.rst:636 +#: ../../rst/user_guide/vault.rst:650 msgid "a 128 bit counter block seeded from an integer IV" msgstr "æ•´æ•° IV ã‹ã‚‰ã‚·ãƒ¼ãƒ‰ã•ã‚ŒãŸ 128 ビットã®ã‚«ã‚¦ãƒ³ã‚¿ãƒ¼ãƒ–ãƒãƒƒã‚¯" -#: ../../rst/user_guide/vault.rst:637 +#: ../../rst/user_guide/vault.rst:651 msgid "the plaintext" msgstr "平文" -#: ../../rst/user_guide/vault.rst:639 +#: ../../rst/user_guide/vault.rst:653 msgid "the original plaintext" msgstr "å…ƒã®å¹³æ–‡" -#: ../../rst/user_guide/vault.rst:640 +#: ../../rst/user_guide/vault.rst:654 msgid "padding up to the AES256 blocksize. (The data used for padding is based on `RFC5652 <https://tools.ietf.org/html/rfc5652#section-6.3>`_)" msgstr "AES256 ブãƒãƒƒã‚¯ã‚µã‚¤ã‚ºã¾ã§ã®ãƒ‘ディング (パディングã«ä½¿ç”¨ã™ã‚‹ãƒ‡ãƒ¼ã‚¿ã¯ `RFC5652 <https://tools.ietf.org/html/rfc5652#section-6.3>`_ ã«åŸºã¥ã„ã¦ã„ã¾ã™)" @@ -12251,44 +12258,44 @@ msgid "Once installed, the win_dsc module will be able to use the resource by re msgstr "インストールã™ã‚‹ã¨ã€win_dsc モジュールã¯ã€``resource_name`` オプションã§ãƒªã‚½ãƒ¼ã‚¹ã‚’å‚ç…§ã™ã‚‹ã“ã¨ã§ã€ãƒªã‚½ãƒ¼ã‚¹ã‚’使用ã§ãるよã†ã«ãªã‚Šã¾ã™ã€‚" #: ../../rst/user_guide/windows_dsc.rst:365 -msgid "The first two methods above only work when the host has access to the internet. When a host does not have internet access, the module must first be installed using the methods above on another host with internet access and then copied across. To save a module to a local filepath, the following PowerShell cmdlet can be run::" +msgid "The first two methods above only work when the host has access to the internet. When a host does not have internet access, the module must first be installed using the methods above on another host with internet access and then copied across. To save a module to a local filepath, the following PowerShell cmdlet can be run:" msgstr "上記ã®æœ€åˆã® 2 ã¤ã®æ–¹æ³•ã¯ã€ãƒ›ã‚¹ãƒˆãŒã‚¤ãƒ³ã‚¿ãƒ¼ãƒãƒƒãƒˆã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãã‚‹å ´åˆã«ã®ã¿æ©Ÿèƒ½ã—ã¾ã™ã€‚ホストãŒã‚¤ãƒ³ã‚¿ãƒ¼ãƒãƒƒãƒˆã«ã‚¢ã‚¯ã‚»ã‚¹ã§ããªã„å ´åˆã¯ã€ã¾ãšã‚¤ãƒ³ã‚¿ãƒ¼ãƒãƒƒãƒˆã«ã‚¢ã‚¯ã‚»ã‚¹ã§ãる別ã®ãƒ›ã‚¹ãƒˆä¸Šã§ä¸Šè¨˜ã®æ–¹æ³•ã‚’使用ã—ã¦ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’インストールã—ã€ãれをコピーã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚モジュールをãƒãƒ¼ã‚«ãƒ«ã®ãƒ•ã‚¡ã‚¤ãƒ«ãƒ‘スã«ä¿å˜ã™ã‚‹ã«ã¯ã€æ¬¡ã® PowerShell コマンドレットを実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_dsc.rst:373 +#: ../../rst/user_guide/windows_dsc.rst:375 msgid "This will create a folder called ``xWebAdministration`` in ``C:\\temp`` which can be copied to any host. For PowerShell to see this offline resource, it must be copied to a directory set in the ``PSModulePath`` environment variable. In most cases the path ``C:\\Program Files\\WindowsPowerShell\\Module`` is set through this variable, but the ``win_path`` module can be used to add different paths." msgstr "ã“ã‚Œã«ã‚ˆã‚Šã€``C:\\temp`` ã®ä¸ã«``xWebAdministration`` フォルダーãŒä½œæˆã•ã‚Œã€ã“ã®ãƒ•ã‚£ãƒ«ãƒ€ãƒ¼ã¯ã©ã®ãƒ›ã‚¹ãƒˆã«ã‚‚コピーã§ãるよã†ã«ãªã‚Šã¾ã™ã€‚PowerShell ãŒã“ã®ã‚ªãƒ•ãƒ©ã‚¤ãƒ³ãƒªã‚½ãƒ¼ã‚¹ã‚’見るãŸã‚ã«ã¯ã€ç’°å¢ƒå¤‰æ•° ``PSModulePath`` ã§è¨å®šã•ã‚ŒãŸãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ã‚³ãƒ”ーã•ã‚Œã¦ã„ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã»ã¨ã‚“ã©ã®å ´åˆã¯ã€ã“ã®å¤‰æ•°ã‚’通ã˜ã¦ãƒ‘ス ``C:\\Program Files\\WindowsPowerShell\\Module`` ãŒè¨å®šã•ã‚Œã¾ã™ãŒã€``win_path`` モジュールを使用ã—ã¦ç•°ãªã‚‹ãƒ‘ã‚¹ã‚’è¿½åŠ ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_dsc.rst:381 +#: ../../rst/user_guide/windows_dsc.rst:383 msgid "Examples" msgstr "例" -#: ../../rst/user_guide/windows_dsc.rst:383 +#: ../../rst/user_guide/windows_dsc.rst:385 msgid "Extract a zip file" msgstr "zip ファイルã®å±•é–‹" -#: ../../rst/user_guide/windows_dsc.rst:395 +#: ../../rst/user_guide/windows_dsc.rst:397 msgid "Create a directory" msgstr "ディレクトリーã®ä½œæˆ" -#: ../../rst/user_guide/windows_dsc.rst:418 +#: ../../rst/user_guide/windows_dsc.rst:420 msgid "Interact with Azure" msgstr "Azure ã®æ“作" -#: ../../rst/user_guide/windows_dsc.rst:441 +#: ../../rst/user_guide/windows_dsc.rst:443 msgid "Setup IIS Website" msgstr "IIS Web サイトã®ã‚»ãƒƒãƒˆã‚¢ãƒƒãƒ—" -#: ../../rst/user_guide/windows_dsc.rst:500 -#: ../../rst/user_guide/windows_setup.rst:578 -#: ../../rst/user_guide/windows_usage.rst:508 -#: ../../rst/user_guide/windows_winrm.rst:909 +#: ../../rst/user_guide/windows_dsc.rst:502 +#: ../../rst/user_guide/windows_setup.rst:601 +#: ../../rst/user_guide/windows_usage.rst:512 +#: ../../rst/user_guide/windows_winrm.rst:931 msgid ":ref:`List of Windows Modules <windows_modules>`" msgstr ":ref:`List of Windows Modules <windows_modules>`" -#: ../../rst/user_guide/windows_dsc.rst:501 -#: ../../rst/user_guide/windows_setup.rst:579 -#: ../../rst/user_guide/windows_usage.rst:509 -#: ../../rst/user_guide/windows_winrm.rst:910 +#: ../../rst/user_guide/windows_dsc.rst:503 +#: ../../rst/user_guide/windows_setup.rst:602 +#: ../../rst/user_guide/windows_usage.rst:513 +#: ../../rst/user_guide/windows_winrm.rst:932 msgid "Windows specific module list, all implemented in PowerShell" msgstr "Windows 固有ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ãƒªã‚¹ãƒˆ (ã™ã¹ã¦ PowerShell ã«å®Ÿè£…)" @@ -12372,259 +12379,259 @@ msgstr "Ansible 㧠Windows Nano Server を管ç†ã§ãã¾ã™ã‹" msgid "Ansible does not currently work with Windows Nano Server, since it does not have access to the full .NET Framework that is used by the majority of the modules and internal components." msgstr "Ansible ã¯ç¾åœ¨ã€Windows Nano Server ã§ã¯å‹•ä½œã—ã¾ã›ã‚“。ã“ã‚Œã¯ã€å¤§éƒ¨åˆ†ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚„内部コンãƒãƒ¼ãƒãƒ³ãƒˆã§ä½¿ç”¨ã•ã‚Œã¦ã„る完全㪠.NET フレームワークã«ã‚¢ã‚¯ã‚»ã‚¹ã§ããªã„ãŸã‚ã§ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:45 +#: ../../rst/user_guide/windows_faq.rst:47 msgid "Can Ansible run on Windows?" msgstr "Ansible 㯠Windows ã§å®Ÿè¡Œã§ãã¾ã™ã‹" -#: ../../rst/user_guide/windows_faq.rst:46 +#: ../../rst/user_guide/windows_faq.rst:48 msgid "No, Ansible can only manage Windows hosts. Ansible cannot run on a Windows host natively, though it can run under the Windows Subsystem for Linux (WSL)." msgstr "ã„ã„ãˆã€Ansible 㯠Windows ホストã®ã¿ã‚’管ç†ã§ãã¾ã™ã€‚Ansible 㯠Windows ホスト上ã§ã¯ãƒã‚¤ãƒ†ã‚£ãƒ–ã«å®Ÿè¡Œã§ãã¾ã›ã‚“ãŒã€Windows Subsystem for Linux (WSL) ã®ä¸‹ã§å®Ÿè¡Œã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:49 +#: ../../rst/user_guide/windows_faq.rst:51 msgid "The Windows Subsystem for Linux is not supported by Ansible and should not be used for production systems." msgstr "Windows Subsystem for Linux 㯠Ansible ã§ã¯ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ãªã„ãŸã‚ã€å®Ÿç¨¼åƒã‚·ã‚¹ãƒ†ãƒ ã«ã¯ä½¿ç”¨ã—ãªã„ã§ãã ã•ã„。" -#: ../../rst/user_guide/windows_faq.rst:52 +#: ../../rst/user_guide/windows_faq.rst:54 msgid "To install Ansible on WSL, the following commands can be run in the bash terminal:" msgstr "WSL ã« Ansible をインストールã™ã‚‹ã«ã¯ã€bash ターミナルã§ä»¥ä¸‹ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:61 +#: ../../rst/user_guide/windows_faq.rst:63 msgid "To run Ansible from source instead of a release on the WSL, simply uninstall the pip installed version and then clone the git repo." msgstr "WSL ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ãªãソースã‹ã‚‰ Ansible を実行ã™ã‚‹ã«ã¯ã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—㟠pip をアンインストールã—ã€git リãƒã‚¸ãƒˆãƒªãƒ¼ã®ã‚¯ãƒãƒ¼ãƒ³ã‚’作æˆã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:73 +#: ../../rst/user_guide/windows_faq.rst:75 msgid "If you encounter timeout errors when running Ansible on the WSL, this may be due to an issue with ``sleep`` not returning correctly. The following workaround may resolve the issue:" msgstr "WSL 上㧠Ansible を実行ã—ãŸã¨ãã«ã‚¿ã‚¤ãƒ アウトエラーãŒç™ºç”Ÿã™ã‚‹å ´åˆã¯ã€``sleep`` ãŒæ£ã—ãè¿”ã•ã‚Œãªã„å•é¡ŒãŒåŽŸå› ã¨ãªã£ã¦ã„ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚以下ã®å›žé¿ç–ã«ã‚ˆã‚Šã€ã“ã®å•é¡ŒãŒè§£æ±ºã•ã‚Œã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:81 +#: ../../rst/user_guide/windows_faq.rst:83 msgid "Another option is to use WSL 2 if running Windows 10 later than build 2004." msgstr "別ã®ã‚ªãƒ—ションã¨ã—ã¦ã€ãƒ“ルド 2004 よりも Windows 10 以上を実行ã—ã¦ã„ã‚‹å ´åˆã¯ WSL 2 を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:89 +#: ../../rst/user_guide/windows_faq.rst:91 msgid "Can I use SSH keys to authenticate to Windows hosts?" msgstr "SSH ã‚ーを使用ã—㦠Windows ホストã¸ã®èªè¨¼ã‚’è¡Œã†ã“ã¨ã¯ã§ãã¾ã™ã‹" -#: ../../rst/user_guide/windows_faq.rst:90 +#: ../../rst/user_guide/windows_faq.rst:92 msgid "You cannot use SSH keys with the WinRM or PSRP connection plugins. These connection plugins use X509 certificates for authentication instead of the SSH key pairs that SSH uses." msgstr "WinRM ã¾ãŸã¯ PSRP connection プラグイン㧠SSH éµã‚’使用ã™ã‚‹ã“ã¨ã¯ã§ãã¾ã›ã‚“。ã“れら㮠connection プラグインã¯ã€èªè¨¼ã« SSH ãŒä½¿ç”¨ã™ã‚‹ SSH ã‚ーペアを使用ã™ã‚‹ä»£ã‚ã‚Šã«ã€X509 証明書を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:94 +#: ../../rst/user_guide/windows_faq.rst:96 msgid "The way X509 certificates are generated and mapped to a user is different from the SSH implementation; consult the :ref:`windows_winrm` documentation for more information." msgstr "X509 証明書ãŒç”Ÿæˆã•ã‚Œã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«ãƒžãƒƒãƒ”ングã•ã‚Œã‚‹æ–¹æ³•ã¯ã€SSH ã®å®Ÿè£…ã¨ã¯ç•°ãªã‚Šã¾ã™ã€‚詳細ã¯ã€:ref:`windows_winrm` ã®ãƒ‰ã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_faq.rst:98 +#: ../../rst/user_guide/windows_faq.rst:100 msgid "Ansible 2.8 has added an experimental option to use the SSH connection plugin, which uses SSH keys for authentication, for Windows servers. See :ref:`this question <windows_faq_ssh>` for more information." msgstr "Ansible 2.8 ã«ã¯ã€èªè¨¼ã« SSH éµã‚’使用ã™ã‚‹ SSH connection プラグインを Windows サーãƒãƒ¼ã§ä½¿ç”¨ã™ã‚‹å®Ÿé¨“çš„ãªã‚ªãƒ—ションãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸã€‚詳細ã¯ã€Œ:ref:`this question <windows_faq_ssh>`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_faq.rst:105 +#: ../../rst/user_guide/windows_faq.rst:107 msgid "Why can I run a command locally that does not work under Ansible?" msgstr "Ansible ã§æ©Ÿèƒ½ã—ãªã„コマンドをãƒãƒ¼ã‚«ãƒ«ã§å®Ÿè¡Œã§ãã‚‹ã®ã¯ãªãœã§ã™ã‹" -#: ../../rst/user_guide/windows_faq.rst:106 +#: ../../rst/user_guide/windows_faq.rst:108 msgid "Ansible executes commands through WinRM. These processes are different from running a command locally in these ways:" msgstr "Ansible ã¯ã€WinRM を介ã—ã¦ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚ã“れらã®ãƒ—ãƒã‚»ã‚¹ã¯ã€ä»¥ä¸‹ã®æ–¹æ³•ã§ãƒãƒ¼ã‚«ãƒ«ã§ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã™ã‚‹ã®ã¨ã¯ç•°ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:109 +#: ../../rst/user_guide/windows_faq.rst:111 msgid "Unless using an authentication option like CredSSP or Kerberos with credential delegation, the WinRM process does not have the ability to delegate the user's credentials to a network resource, causing ``Access is Denied`` errors." msgstr "CredSSP ã‚„ Kerberos ã®ã‚ˆã†ãªèªè¨¼ã‚ªãƒ—ションを使用ã—ã¦ã€èªè¨¼æƒ…å ±ã®å§”è²ã‚’è¡Œã£ã¦ã„ãªã„é™ã‚Šã€WinRM プãƒã‚»ã‚¹ã«ã¯ãƒ¦ãƒ¼ã‚¶ãƒ¼ã®èªè¨¼æƒ…å ±ã‚’ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒªã‚½ãƒ¼ã‚¹ã«å§”è²ã™ã‚‹æ©Ÿèƒ½ãŒãªãã€``Access is Denied`` エラーãŒç™ºç”Ÿã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:114 +#: ../../rst/user_guide/windows_faq.rst:116 msgid "All processes run under WinRM are in a non-interactive session. Applications that require an interactive session will not work." msgstr "WinRM ã§å®Ÿè¡Œã•ã‚Œã‚‹ã™ã¹ã¦ã®ãƒ—ãƒã‚»ã‚¹ã¯ã€éžå¯¾è©±åž‹ã‚»ãƒƒã‚·ãƒ§ãƒ³ã§ã™ã€‚対話型セッションを必è¦ã¨ã™ã‚‹ã‚¢ãƒ—リケーションã¯æ©Ÿèƒ½ã—ã¾ã›ã‚“。" -#: ../../rst/user_guide/windows_faq.rst:117 +#: ../../rst/user_guide/windows_faq.rst:119 msgid "When running through WinRM, Windows restricts access to internal Windows APIs like the Windows Update API and DPAPI, which some installers and programs rely on." msgstr "WinRM を介ã—ã¦å®Ÿè¡Œã™ã‚‹å ´åˆã€Windows ã¯ã€ä¸€éƒ¨ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ©ãƒ¼ã‚„プãƒã‚°ãƒ©ãƒ ãŒä¾å˜ã—ã¦ã„ã‚‹ Windows Update API ã‚„ DPAPI ãªã©ã® Windows 内部 API ã¸ã®ã‚¢ã‚¯ã‚»ã‚¹ã‚’制é™ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:121 +#: ../../rst/user_guide/windows_faq.rst:123 msgid "Some ways to bypass these restrictions are to:" msgstr "ã“れらã®åˆ¶é™ã‚’回é¿ã™ã‚‹æ–¹æ³•ã¯æ¬¡ã®ã¨ãŠã‚Šã§ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:123 +#: ../../rst/user_guide/windows_faq.rst:125 msgid "Use ``become``, which runs a command as it would when run locally. This will bypass most WinRM restrictions, as Windows is unaware the process is running under WinRM when ``become`` is used. See the :ref:`become` documentation for more information." msgstr "``become`` を使用ã™ã‚‹ã¨ã€ãƒãƒ¼ã‚«ãƒ«ã§å®Ÿè¡Œã™ã‚‹ã¨ãã¨åŒã˜ã‚ˆã†ã«ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã§ãã¾ã™ã€‚``become`` を使用ã™ã‚‹ã¨ã€Windows ã¯ãƒ—ãƒã‚»ã‚¹ãŒ WinRM ã®ä¸‹ã§å®Ÿè¡Œã—ã¦ã„ã‚‹ã“ã¨ã«æ°—ã¥ã‹ãªã„ãŸã‚ã€ã»ã¨ã‚“ã©ã® WinRM ã®åˆ¶é™ã‚’回é¿ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚詳細ã¯ã€:ref:`become` ã®ãƒ‰ã‚ュメントをå‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_faq.rst:128 +#: ../../rst/user_guide/windows_faq.rst:130 msgid "Use a scheduled task, which can be created with ``win_scheduled_task``. Like ``become``, it will bypass all WinRM restrictions, but it can only be used to run commands, not modules." msgstr "``win_scheduled_task`` ã§ä½œæˆã§ãã‚‹ã€ã‚¹ã‚±ã‚¸ãƒ¥ãƒ¼ãƒ«ã•ã‚ŒãŸã‚¿ã‚¹ã‚¯ã‚’使用ã—ã¾ã™ã€‚``become`` ã¨åŒæ§˜ã«ã€WinRM ã®åˆ¶é™ã‚’ã™ã¹ã¦å›žé¿ã§ãã¾ã™ãŒã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã§ã¯ãªãコマンドã®å®Ÿè¡Œã«ã®ã¿ä½¿ç”¨ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:132 +#: ../../rst/user_guide/windows_faq.rst:134 msgid "Use ``win_psexec`` to run a command on the host. PSExec does not use WinRM and so will bypass any of the restrictions." msgstr "``win_psexec`` を使用ã—ã¦ãƒ›ã‚¹ãƒˆã§ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚PSExec 㯠WinRM を使用ã—ãªã„ãŸã‚ã€ã‚らゆる制é™ã‚’回é¿ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:135 +#: ../../rst/user_guide/windows_faq.rst:137 msgid "To access network resources without any of these workarounds, you can use CredSSP or Kerberos with credential delegation enabled." msgstr "ã“れらã®å›žé¿ç–ã‚’å–らãšã«ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒªã‚½ãƒ¼ã‚¹ã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ã«ã¯ã€èªè¨¼æƒ…å ±ã®å§”è²ã‚’有効ã«ã—㟠CredSSP ã¾ãŸã¯ Kerberos を使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:138 +#: ../../rst/user_guide/windows_faq.rst:140 msgid "See :ref:`become` more info on how to use become. The limitations section at :ref:`windows_winrm` has more details around WinRM limitations." msgstr "become ã®ä½¿ç”¨æ–¹æ³•ã«é–¢ã™ã‚‹è©³ç´°ã¯ã€ã€Œ:ref:`become`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。:ref:`windows_winrm` ã®åˆ¶é™ã®ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã«ã¯ã€WinRM 制é™ã®è©³ç´°ãŒè¨˜è¼‰ã•ã‚Œã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:142 +#: ../../rst/user_guide/windows_faq.rst:144 msgid "This program won't install on Windows with Ansible" msgstr "ã“ã®ãƒ—ãƒã‚°ãƒ©ãƒ ãŒã€Ansible ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ Windows ã«ã¯ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¾ã›ã‚“" -#: ../../rst/user_guide/windows_faq.rst:143 +#: ../../rst/user_guide/windows_faq.rst:145 msgid "See :ref:`this question <windows_faq_winrm>` for more information about WinRM limitations." msgstr "WinRMã®åˆ¶é™ã®è©³ç´°ã¯ã€ã€Œ:ref:`ã“ã¡ã‚‰ã®è³ªå• <windows_faq_winrm>`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_faq.rst:146 +#: ../../rst/user_guide/windows_faq.rst:148 msgid "What Windows modules are available?" msgstr "ã©ã®ã‚ˆã†ãª Windows モジュールãŒåˆ©ç”¨ã§ãã¾ã™ã‹" -#: ../../rst/user_guide/windows_faq.rst:147 +#: ../../rst/user_guide/windows_faq.rst:149 msgid "Most of the Ansible modules in Ansible Core are written for a combination of Linux/Unix machines and arbitrary web services. These modules are written in Python and most of them do not work on Windows." msgstr "Ansible Core ã® Ansible モジュールã®å¤šãã¯ã€Linux/Unix マシンã¨ä»»æ„ã® Web サービスã®çµ„ã¿åˆã‚ã›ã‚’想定ã—ã¦è¨˜è¿°ã•ã‚Œã¾ã™ã€‚ã“れらã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯ Python ã§è¨˜è¿°ã•ã‚Œã¦ãŠã‚Šã€ãã®ã»ã¨ã‚“ã©ãŒ Windows ã§ã¯å‹•ä½œã—ã¾ã›ã‚“。" -#: ../../rst/user_guide/windows_faq.rst:151 +#: ../../rst/user_guide/windows_faq.rst:153 msgid "Because of this, there are dedicated Windows modules that are written in PowerShell and are meant to be run on Windows hosts. A list of these modules can be found :ref:`here <windows_modules>`." msgstr "ã“ã®ãŸã‚ã€PowerShell ã§è¨˜è¿°ã•ã‚Œã¦ãŠã‚Šã€Windows ホストã§å®Ÿè¡Œã™ã‚‹ã“ã¨ã‚’目的ã¨ã—ã¦ã„る専用㮠Windows モジュールãŒã‚ã‚Šã¾ã™ã€‚ã“れらã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®ä¸€è¦§ã¯ã€ã€Œ:ref:`here <windows_modules>`ã€ã«ã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:155 +#: ../../rst/user_guide/windows_faq.rst:157 msgid "In addition, the following Ansible Core modules/action-plugins work with Windows:" msgstr "次㮠Ansible Core モジュールãŠã‚ˆã³ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ãƒ—ラグインã¯ã€Windows ã§å‹•ä½œã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:157 +#: ../../rst/user_guide/windows_faq.rst:159 msgid "add_host" msgstr "add_host" -#: ../../rst/user_guide/windows_faq.rst:158 +#: ../../rst/user_guide/windows_faq.rst:160 msgid "assert" msgstr "assert" -#: ../../rst/user_guide/windows_faq.rst:159 +#: ../../rst/user_guide/windows_faq.rst:161 msgid "async_status" msgstr "async_status" -#: ../../rst/user_guide/windows_faq.rst:160 +#: ../../rst/user_guide/windows_faq.rst:162 msgid "debug" msgstr "debug" -#: ../../rst/user_guide/windows_faq.rst:161 +#: ../../rst/user_guide/windows_faq.rst:163 msgid "fail" msgstr "fail" -#: ../../rst/user_guide/windows_faq.rst:162 +#: ../../rst/user_guide/windows_faq.rst:164 msgid "fetch" msgstr "fetch" -#: ../../rst/user_guide/windows_faq.rst:163 +#: ../../rst/user_guide/windows_faq.rst:165 msgid "group_by" msgstr "group_by" -#: ../../rst/user_guide/windows_faq.rst:164 +#: ../../rst/user_guide/windows_faq.rst:166 msgid "include" msgstr "include" -#: ../../rst/user_guide/windows_faq.rst:165 +#: ../../rst/user_guide/windows_faq.rst:167 msgid "include_role" msgstr "include_role" -#: ../../rst/user_guide/windows_faq.rst:167 +#: ../../rst/user_guide/windows_faq.rst:169 msgid "meta" msgstr "meta" -#: ../../rst/user_guide/windows_faq.rst:168 +#: ../../rst/user_guide/windows_faq.rst:170 msgid "pause" msgstr "pause" -#: ../../rst/user_guide/windows_faq.rst:169 +#: ../../rst/user_guide/windows_faq.rst:171 msgid "raw" msgstr "raw" -#: ../../rst/user_guide/windows_faq.rst:170 +#: ../../rst/user_guide/windows_faq.rst:172 msgid "script" msgstr "script" -#: ../../rst/user_guide/windows_faq.rst:171 +#: ../../rst/user_guide/windows_faq.rst:173 msgid "set_fact" msgstr "set_fact" -#: ../../rst/user_guide/windows_faq.rst:172 +#: ../../rst/user_guide/windows_faq.rst:174 msgid "set_stats" msgstr "set_stats" -#: ../../rst/user_guide/windows_faq.rst:173 +#: ../../rst/user_guide/windows_faq.rst:175 msgid "setup" msgstr "setup" -#: ../../rst/user_guide/windows_faq.rst:174 +#: ../../rst/user_guide/windows_faq.rst:176 msgid "slurp" msgstr "slurp" -#: ../../rst/user_guide/windows_faq.rst:175 +#: ../../rst/user_guide/windows_faq.rst:177 msgid "template (also: win_template)" msgstr "template (win_template ã‚‚åŒæ§˜)" -#: ../../rst/user_guide/windows_faq.rst:176 +#: ../../rst/user_guide/windows_faq.rst:178 msgid "wait_for_connection" msgstr "wait_for_connection" -#: ../../rst/user_guide/windows_faq.rst:179 +#: ../../rst/user_guide/windows_faq.rst:181 msgid "Can I run Python modules on Windows hosts?" msgstr "Windows ホスト㧠Python モジュールを実行ã§ãã¾ã™ã‹" -#: ../../rst/user_guide/windows_faq.rst:180 +#: ../../rst/user_guide/windows_faq.rst:182 msgid "No, the WinRM connection protocol is set to use PowerShell modules, so Python modules will not work. A way to bypass this issue to use ``delegate_to: localhost`` to run a Python module on the Ansible controller. This is useful if during a playbook, an external service needs to be contacted and there is no equivalent Windows module available." msgstr "ã§ãã¾ã›ã‚“。WinRM 接続プãƒãƒˆã‚³ãƒ«ã¯ PowerShell モジュールを使用ã™ã‚‹ã‚ˆã†ã«è¨å®šã•ã‚Œã¦ã„ã‚‹ãŸã‚ã€Python モジュールã¯å‹•ä½œã—ã¾ã›ã‚“。ã“ã®å•é¡Œã‚’回é¿ã™ã‚‹ã«ã¯ã€``delegate_to: localhost`` を使用ã—㦠Ansible コントãƒãƒ¼ãƒ©ãƒ¼ä¸Šã§ Python モジュールを実行ã™ã‚‹æ–¹æ³•ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€Playbook ä¸ã«å¤–部サービスã«æŽ¥ç¶šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã€åŒç‰ã® Windows モジュールãŒãªã„å ´åˆã«ä¾¿åˆ©ã§ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:189 +#: ../../rst/user_guide/windows_faq.rst:191 msgid "Can I connect to Windows hosts over SSH?" msgstr "SSH 経由㧠Windows ホストã«æŽ¥ç¶šã§ãã¾ã™ã‹" -#: ../../rst/user_guide/windows_faq.rst:190 +#: ../../rst/user_guide/windows_faq.rst:192 msgid "Ansible 2.8 has added an experimental option to use the SSH connection plugin to manage Windows hosts. To connect to Windows hosts over SSH, you must install and configure the `Win32-OpenSSH <https://github.com/PowerShell/Win32-OpenSSH>`_ fork that is in development with Microsoft on the Windows host(s). While most of the basics should work with SSH, ``Win32-OpenSSH`` is rapidly changing, with new features added and bugs fixed in every release. It is highly recommend you `install <https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH>`_ the latest release of ``Win32-OpenSSH`` from the GitHub Releases page when using it with Ansible on Windows hosts." msgstr "Ansible 2.8 ã«ã¯ã€SSH connection プラグインを使用ã—㦠Windows ホストを管ç†ã™ã‚‹å®Ÿé¨“çš„ãªã‚ªãƒ—ションãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸã€‚Windows ホスト㫠SSH 接続ã™ã‚‹ã«ã¯ã€Microsoft ã¨å…±åŒã§é–‹ç™ºä¸ã® `Win32-OpenSSH <https://github.com/PowerShell/Win32-OpenSSH>`_ フォークを Windows ホストã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã¦è¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚基本的ãªæ©Ÿèƒ½ã®ã»ã¨ã‚“ã©ã¯ SSH ã§å‹•ä½œã™ã‚‹ã¯ãšã§ã™ãŒã€``Win32-OpenSSH`` ã¯ãƒªãƒªãƒ¼ã‚¹ã”ã¨ã«æ–°æ©Ÿèƒ½ãŒè¿½åŠ ã•ã‚ŒãŸã‚Šã€ãƒã‚°ãŒä¿®æ£ã•ã‚ŒãŸã‚Šã¨ã€æ€¥é€Ÿã«å¤‰åŒ–ã—ã¦ã„ã¾ã™ã€‚Windows ホスト㧠Ansible を使用ã™ã‚‹éš›ã«ã¯ã€GitHub Releases ページã‹ã‚‰ ``Win32-OpenSSH`` ã®æœ€æ–°ãƒªãƒªãƒ¼ã‚¹ã‚’ `インストール <https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH>`_ ã™ã‚‹ã“ã¨ãŒå¼·ã推奨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:199 -msgid "To use SSH as the connection to a Windows host, set the following variables in the inventory::" +#: ../../rst/user_guide/windows_faq.rst:201 +msgid "To use SSH as the connection to a Windows host, set the following variables in the inventory:" msgstr "Windows ホストã¸ã®æŽ¥ç¶šã« SSH を使用ã™ã‚‹ã«ã¯ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã«ä»¥ä¸‹ã®å¤‰æ•°ã‚’è¨å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:208 +#: ../../rst/user_guide/windows_faq.rst:212 msgid "The value for ``ansible_shell_type`` should either be ``cmd`` or ``powershell``. Use ``cmd`` if the ``DefaultShell`` has not been configured on the SSH service and ``powershell`` if that has been set as the ``DefaultShell``." msgstr "``ansible_shell_type`` ã®å€¤ã¯ã€``cmd`` ã¾ãŸã¯ ``powershell`` ã®ã„ãšã‚Œã‹ã§ãªã‘ã‚Œã°ãªã‚Šã¾ã›ã‚“。SSH サービス㧠``DefaultShell`` ãŒè¨å®šã•ã‚Œã¦ã„ãªã„å ´åˆã¯ ``cmd`` を使用ã—ã¦ã€``DefaultShell`` ã¨ã—ã¦è¨å®šã•ã‚Œã¦ã„ã‚‹å ´åˆã¯ ``powershell`` を使用ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_faq.rst:213 +#: ../../rst/user_guide/windows_faq.rst:217 msgid "Why is connecting to a Windows host via SSH failing?" msgstr "SSH 経由㧠Windows ホストã«æŽ¥ç¶šã§ããªã„ã®ã¯ãªãœã§ã™ã‹" -#: ../../rst/user_guide/windows_faq.rst:214 +#: ../../rst/user_guide/windows_faq.rst:218 msgid "Unless you are using ``Win32-OpenSSH`` as described above, you must connect to Windows hosts using :ref:`windows_winrm`. If your Ansible output indicates that SSH was used, either you did not set the connection vars properly or the host is not inheriting them correctly." msgstr "上記ã®ã‚ˆã†ã« ``Win32-OpenSSH`` を使用ã—ã¦ã„ã‚‹å ´åˆã‚’除ãã€Windows ホストã¸ã®æŽ¥ç¶šã«ã¯ :ref:`windows_winrm` を使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚Ansible ã®å‡ºåŠ›ã§ SSH ãŒä½¿ç”¨ã•ã‚ŒãŸã¨è¡¨ç¤ºã•ã‚ŒãŸå ´åˆã¯ã€æŽ¥ç¶šãƒãƒ¼ãŒæ£ã—ãè¨å®šã•ã‚Œã¦ã„ãªã„ã‹ã€ãƒ›ã‚¹ãƒˆã«æ£ã—ã継承ã•ã‚Œã¦ã„ã¾ã›ã‚“。" -#: ../../rst/user_guide/windows_faq.rst:218 +#: ../../rst/user_guide/windows_faq.rst:222 msgid "Make sure ``ansible_connection: winrm`` is set in the inventory for the Windows host(s)." msgstr "Windows ホストã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã« ``ansible_connection: winrm`` ãŒè¨å®šã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_faq.rst:222 +#: ../../rst/user_guide/windows_faq.rst:226 msgid "Why are my credentials being rejected?" msgstr "èªè¨¼æƒ…å ±ãŒæ‹’å¦ã•ã‚Œã‚‹ã®ã¯ãªãœã§ã™ã‹" -#: ../../rst/user_guide/windows_faq.rst:223 +#: ../../rst/user_guide/windows_faq.rst:227 msgid "This can be due to a myriad of reasons unrelated to incorrect credentials." msgstr "ã“ã‚Œã¯ã€èª¤ã£ãŸèªè¨¼æƒ…å ±ã¨ã¯ç„¡é–¢ä¿‚ã®ã€å¤šç¨®å¤šæ§˜ãªã‚‚ã®ãŒåŽŸå› ã§ã‚ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:225 +#: ../../rst/user_guide/windows_faq.rst:229 msgid "See HTTP 401/Credentials Rejected at :ref:`windows_setup` for a more detailed guide of this could mean." msgstr "ã“ã®ç¾è±¡ã®è©³ç´°ã«ã¤ã„ã¦ã¯ã€:ref:`windows_setup` ã®ã€ŒHTTP 401/èªè¨¼æƒ…å ±ã®æ‹’å¦ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_faq.rst:229 +#: ../../rst/user_guide/windows_faq.rst:233 msgid "Why am I getting an error SSL CERTIFICATE_VERIFY_FAILED?" msgstr "SSL CERTIFICATE_VERIFY_FAILED エラーãŒç™ºç”Ÿã™ã‚‹ã®ã¯ãªãœã§ã™ã‹" -#: ../../rst/user_guide/windows_faq.rst:230 +#: ../../rst/user_guide/windows_faq.rst:234 msgid "When the Ansible controller is running on Python 2.7.9+ or an older version of Python that has backported SSLContext (like Python 2.7.5 on RHEL 7), the controller will attempt to validate the certificate WinRM is using for an HTTPS connection. If the certificate cannot be validated (such as in the case of a self signed cert), it will fail the verification process." msgstr "Ansible コントãƒãƒ¼ãƒ©ãƒ¼ãŒ Python 2.7.9 以é™ã¾ãŸã¯ SSLContext ã‚’ãƒãƒƒã‚¯ãƒãƒ¼ãƒˆã—ãŸå¤ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Python (RHEL 7 ã® Python 2.7.5 ãªã©) ã§å‹•ä½œã—ã¦ã„ã‚‹å ´åˆã€ã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©ãƒ¼ã¯ WinRM ㌠HTTPS 接続ã«ä½¿ç”¨ã—ã¦ã„る証明書を検証ã—よã†ã¨ã—ã¾ã™ã€‚証明書を検証ã§ããªã„å ´åˆ (自己署å証明書ã®å ´åˆãªã©) ã¯ã€æ¤œè¨¼ãƒ—ãƒã‚»ã‚¹ã«å¤±æ•—ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_faq.rst:236 +#: ../../rst/user_guide/windows_faq.rst:240 msgid "To ignore certificate validation, add ``ansible_winrm_server_cert_validation: ignore`` to inventory for the Windows host." msgstr "証明書ã®æ¤œè¨¼ã‚’無視ã™ã‚‹ã«ã¯ã€Windows ホストã®ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã« ``ansible_winrm_server_cert_validation: ignore`` ã‚’è¿½åŠ ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_faq.rst:242 +#: ../../rst/user_guide/windows_faq.rst:246 msgid ":ref:`windows`" msgstr ":ref:`windows`" -#: ../../rst/user_guide/windows_faq.rst:243 +#: ../../rst/user_guide/windows_faq.rst:247 msgid "The Windows documentation index" msgstr "Windows ドã‚ュメントã®ç›®æ¬¡" @@ -12781,359 +12788,359 @@ msgid "To view the current listeners that are running on the WinRM service, run msgstr "WinRM サービスã§å®Ÿè¡Œã—ã¦ã„ã‚‹ç¾åœ¨ã®ãƒªã‚¹ãƒŠãƒ¼ã‚’表示ã™ã‚‹ã«ã¯ã€æ¬¡ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" #: ../../rst/user_guide/windows_setup.rst:154 -#: ../../rst/user_guide/windows_setup.rst:266 -msgid "This will output something like::" +#: ../../rst/user_guide/windows_setup.rst:272 +msgid "This will output something like:" msgstr "ã“ã‚Œã«ã‚ˆã‚Šã€ä»¥ä¸‹ã®ã‚ˆã†ãªã‚‚ã®ãŒå‡ºåŠ›ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:178 +#: ../../rst/user_guide/windows_setup.rst:180 msgid "In the example above there are two listeners activated; one is listening on port 5985 over HTTP and the other is listening on port 5986 over HTTPS. Some of the key options that are useful to understand are:" msgstr "上ã®ä¾‹ã§ã¯ã€2 ã¤ã®ãƒªã‚¹ãƒŠãƒ¼ãŒæœ‰åŠ¹ã«ãªã£ã¦ã„ã¾ã™ã€‚1 ã¤ã¯ HTTP ã§ãƒãƒ¼ãƒˆ 5985 をリッスンã—ã¦ãŠã‚Šã€ã‚‚ㆠ1 ã¤ã¯ HTTPS ã§ãƒãƒ¼ãƒˆ 5986 をリッスンã—ã¦ã„ã¾ã™ã€‚ç†è§£ã—ã¦ãŠãã¨ä¾¿åˆ©ãªã‚ªãƒ—ションをã„ãã¤ã‹ç´¹ä»‹ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:182 +#: ../../rst/user_guide/windows_setup.rst:184 msgid "``Transport``: Whether the listener is run over HTTP or HTTPS, it is recommended to use a listener over HTTPS as the data is encrypted without any further changes required." msgstr "``Transport``: リスナー㌠HTTP ã¾ãŸã¯ HTTPS ã®ã©ã¡ã‚‰ã§å®Ÿè¡Œã—ã¦ã„ã‚‹å ´åˆã§ã‚‚ã€ãƒ‡ãƒ¼ã‚¿ã¯ã•ã‚‰ãªã‚‹å¤‰æ›´ãªã—ã«æš—å·åŒ–ã•ã‚Œã‚‹ãŸã‚ã€HTTPS 経由ã§ãƒªã‚¹ãƒŠãƒ¼ã‚’使用ã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:186 +#: ../../rst/user_guide/windows_setup.rst:188 msgid "``Port``: The port the listener runs on, by default it is ``5985`` for HTTP and ``5986`` for HTTPS. This port can be changed to whatever is required and corresponds to the host var ``ansible_port``." msgstr "``Port``: リスナーãŒå®Ÿè¡Œã™ã‚‹ãƒãƒ¼ãƒˆã€‚デフォルトã¯ã€HTTP ã®å ´åˆã¯ ``5985``ã€HTTPS ã®å ´åˆã¯ ``5986`` ã§ã™ã€‚ã“ã®ãƒãƒ¼ãƒˆã¯ã€å¿…è¦ãªã‚‚ã®ã«ãã‚Œãžã‚Œå¤‰æ›´ã§ãã€ãƒ›ã‚¹ãƒˆå¤‰æ•° ``ansible_port`` ã«å¯¾å¿œã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:190 +#: ../../rst/user_guide/windows_setup.rst:192 msgid "``URLPrefix``: The URL prefix to listen on, by default it is ``wsman``. If this is changed, the host var ``ansible_winrm_path`` must be set to the same value." msgstr "``URLPrefix``: リッスンã™ã‚‹ URL プレフィックス。デフォルト㯠``wsman`` ã§ã™ã€‚ã“ã‚ŒãŒå¤‰æ›´ã•ã‚ŒãŸå ´åˆã€ãƒ›ã‚¹ãƒˆå¤‰æ•° ``ansible_winrm_path`` ã¯åŒã˜å€¤ã«è¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:194 -msgid "``CertificateThumbprint``: If running over an HTTPS listener, this is the thumbprint of the certificate in the Windows Certificate Store that is used in the connection. To get the details of the certificate itself, run this command with the relevant certificate thumbprint in PowerShell::" +#: ../../rst/user_guide/windows_setup.rst:196 +msgid "``CertificateThumbprint``: If running over an HTTPS listener, this is the thumbprint of the certificate in the Windows Certificate Store that is used in the connection. To get the details of the certificate itself, run this command with the relevant certificate thumbprint in PowerShell:" msgstr "``CertificateThumbprint``: HTTPS リスナーを介ã—ã¦å®Ÿè¡Œã™ã‚‹å ´åˆã€ã“ã‚Œã¯æŽ¥ç¶šã«ä½¿ç”¨ã•ã‚Œã‚‹ Windows 証明書ストアã®è¨¼æ˜Žæ›¸ã®ã‚µãƒ プリントã§ã™ã€‚証明書自体ã®è©³ç´°ã‚’å–å¾—ã™ã‚‹ã«ã¯ã€PowerShell ã§è©²å½“ã™ã‚‹è¨¼æ˜Žæ›¸ã®ã‚µãƒ プリントを指定ã—ã¦æ¬¡ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:203 +#: ../../rst/user_guide/windows_setup.rst:207 msgid "Setup WinRM Listener" msgstr "WinRM リスナーã®è¨å®š" -#: ../../rst/user_guide/windows_setup.rst:204 +#: ../../rst/user_guide/windows_setup.rst:208 msgid "There are three ways to set up a WinRM listener:" msgstr "WinRM リスナーをè¨å®šã™ã‚‹ã«ã¯ã€3 ã¤ã®æ–¹æ³•ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:206 +#: ../../rst/user_guide/windows_setup.rst:210 msgid "Using ``winrm quickconfig`` for HTTP or ``winrm quickconfig -transport:https`` for HTTPS. This is the easiest option to use when running outside of a domain environment and a simple listener is required. Unlike the other options, this process also has the added benefit of opening up the Firewall for the ports required and starts the WinRM service." msgstr "HTTP ã«ã¯ ``winrm quickconfig`` ã‚’ã€HTTPS ã«ã¯ ``winrm quickconfig -transport:https`` を使用ã—ã¾ã™ã€‚ã“ã‚Œã¯ã€ãƒ‰ãƒ¡ã‚¤ãƒ³ç’°å¢ƒå¤–ã§å‹•ä½œã—ã€ã‚·ãƒ³ãƒ—ルãªãƒªã‚¹ãƒŠãƒ¼ãŒå¿…è¦ãªå ´åˆã«ã€æœ€ã‚‚ç°¡å˜ã«ä½¿ç”¨ã§ãるオプションã§ã™ã€‚ä»–ã®ã‚ªãƒ—ションã¨ã¯ç•°ãªã‚Šã€ã“ã®ãƒ—ãƒã‚»ã‚¹ã«ã¯ã€å¿…è¦ãªãƒãƒ¼ãƒˆã®ãŸã‚ã«ãƒ•ã‚¡ã‚¤ã‚¢ã‚¦ã‚©ãƒ¼ãƒ«ã‚’é–‹ãã€WinRM サービスを開始ã™ã‚‹ã¨ã„ã†åˆ©ç‚¹ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:212 +#: ../../rst/user_guide/windows_setup.rst:216 msgid "Using Group Policy Objects. This is the best way to create a listener when the host is a member of a domain because the configuration is done automatically without any user input. For more information on group policy objects, see the `Group Policy Objects documentation <https://msdn.microsoft.com/en-us/library/aa374162(v=vs.85).aspx>`_." msgstr "グルーãƒ—ãƒãƒªã‚·ãƒ¼ã‚ªãƒ–ジェクトã®ä½¿ç”¨ã€‚è¨å®šã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒå…¥åŠ›ã›ãšã«è‡ªå‹•çš„ã«è¡Œã‚れるãŸã‚ã€ã“ã®æ–¹æ³•ã¯ã€ãƒ›ã‚¹ãƒˆãŒãƒ‰ãƒ¡ã‚¤ãƒ³ã®ãƒ¡ãƒ³ãƒãƒ¼ã§ã‚ã‚‹å ´åˆã«ãƒªã‚¹ãƒŠãƒ¼ã‚’作æˆã™ã‚‹ã®ã«æœ€é©ãªæ–¹æ³•ã§ã™ã€‚グループãƒãƒªã‚·ãƒ¼ã‚ªãƒ–ジェクトã®è©³ç´°ã¯ã€`Group Policy Objects ドã‚ュメント <https://msdn.microsoft.com/en-us/library/aa374162(v=vs.85).aspx>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_setup.rst:217 +#: ../../rst/user_guide/windows_setup.rst:221 msgid "Using PowerShell to create the listener with a specific configuration. This can be done by running the following PowerShell commands:" msgstr "PowerShell を使用ã—ã¦ã€ç‰¹å®šã®è¨å®šã§ãƒªã‚¹ãƒŠãƒ¼ã‚’作æˆã—ã¾ã™ã€‚ã“ã‚Œã¯ã€ä»¥ä¸‹ã® PowerShell コマンドを実行ã™ã‚‹ã“ã¨ã§å¯èƒ½ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:232 +#: ../../rst/user_guide/windows_setup.rst:236 msgid "To see the other options with this PowerShell cmdlet, see `New-WSManInstance <https://docs.microsoft.com/en-us/powershell/module/microsoft.wsman.management/new-wsmaninstance?view=powershell-5.1>`_." msgstr "ã“ã® PowerShell コマンドレッドを伴ã†ä»–ã®ã‚ªãƒ—ションを表示ã™ã‚‹ã«ã¯ã€ã€Œ`New-WSManInstance <https://docs.microsoft.com/en-us/powershell/module/microsoft.wsman.management/new-wsmaninstance?view=powershell-5.1>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_setup.rst:235 +#: ../../rst/user_guide/windows_setup.rst:239 msgid "When creating an HTTPS listener, an existing certificate needs to be created and stored in the ``LocalMachine\\My`` certificate store. Without a certificate being present in this store, most commands will fail." msgstr "HTTPS リスナーを作æˆã™ã‚‹éš›ã«ã¯ã€æ—¢å˜ã®è¨¼æ˜Žæ›¸ã‚’作æˆã—ã€``LocalMachine\\My`` ã®è¨¼æ˜Žæ›¸ã‚¹ãƒˆã‚¢ã«ä¿å˜ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®ã‚¹ãƒˆã‚¢ã«è¨¼æ˜Žæ›¸ãŒå˜åœ¨ã—ãªã„ã¨ã€ã»ã¨ã‚“ã©ã®ã‚³ãƒžãƒ³ãƒ‰ãŒå¤±æ•—ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:240 +#: ../../rst/user_guide/windows_setup.rst:244 msgid "Delete WinRM Listener" msgstr "WinRM リスナーã®å‰Šé™¤" -#: ../../rst/user_guide/windows_setup.rst:241 -msgid "To remove a WinRM listener::" +#: ../../rst/user_guide/windows_setup.rst:245 +msgid "To remove a WinRM listener:" msgstr "WinRM リスナーを削除ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:249 +#: ../../rst/user_guide/windows_setup.rst:255 msgid "The ``Keys`` object is an array of strings, so it can contain different values. By default it contains a key for ``Transport=`` and ``Address=`` which correspond to the values from winrm enumerate winrm/config/Listeners." msgstr "``Keys`` オブジェクトã¯æ–‡å—列ã®é…列ã§ã‚ã‚‹ãŸã‚ã€ç•°ãªã‚‹å€¤ã‚’å«ã‚€ã“ã¨ãŒã§ãã¾ã™ã€‚デフォルトã§ã¯ã€winrm enumerate winrm/config/Listeners ã®å€¤ã«å¯¾å¿œã™ã‚‹ ``Transport=`` ãŠã‚ˆã³ ``Address=`` ã®ã‚ーをå«ã‚“ã§ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:254 +#: ../../rst/user_guide/windows_setup.rst:260 msgid "WinRM Service Options" msgstr "WinRM サービスオプション" -#: ../../rst/user_guide/windows_setup.rst:255 +#: ../../rst/user_guide/windows_setup.rst:261 msgid "There are a number of options that can be set to control the behavior of the WinRM service component, including authentication options and memory settings." msgstr "WinRM サービスコンãƒãƒ¼ãƒãƒ³ãƒˆã®å‹•ä½œã‚’制御ã™ã‚‹ã‚ˆã†ã«è¨å®šã§ãã€èªè¨¼ã‚ªãƒ—ションやメモリーè¨å®šãªã©ã€è¤‡æ•°ã®ã‚ªãƒ—ションをè¨å®šã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:258 +#: ../../rst/user_guide/windows_setup.rst:264 msgid "To get an output of the current service configuration options, run the following command:" msgstr "ç¾åœ¨ã®ã‚µãƒ¼ãƒ“スè¨å®šã‚ªãƒ—ションã®å‡ºåŠ›ã‚’å¾—ã‚‹ã«ã¯ã€æ¬¡ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:302 +#: ../../rst/user_guide/windows_setup.rst:310 msgid "While many of these options should rarely be changed, a few can easily impact the operations over WinRM and are useful to understand. Some of the important options are:" msgstr "ã“れらã®ã‚ªãƒ—ションã®å¤šãã¯ã»ã¨ã‚“ã©å¤‰æ›´ã™ã‚‹å¿…è¦ã¯ã‚ã‚Šã¾ã›ã‚“ãŒã€ã„ãã¤ã‹ã®ã‚ªãƒ—ション㯠WinRM ã®æ“作ã«ç°¡å˜ã«å½±éŸ¿ã‚’与ãˆã‚‹ãŸã‚ã€ç†è§£ã—ã¦ãŠãã¨ä¾¿åˆ©ã§ã™ã€‚é‡è¦ãªã‚ªãƒ—ションã®ä¸€éƒ¨ã‚’紹介ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:306 +#: ../../rst/user_guide/windows_setup.rst:314 msgid "``Service\\AllowUnencrypted``: This option defines whether WinRM will allow traffic that is run over HTTP without message encryption. Message level encryption is only possible when ``ansible_winrm_transport`` is ``ntlm``, ``kerberos`` or ``credssp``. By default this is ``false`` and should only be set to ``true`` when debugging WinRM messages." msgstr "``Service\\AllowUnencrypted``: ã“ã®ã‚ªãƒ—ションã¯ã€ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã‚’æš—å·åŒ–ã›ãšã« HTTP ã§å®Ÿè¡Œã™ã‚‹ãƒˆãƒ©ãƒ•ã‚£ãƒƒã‚¯ã‚’ WinRM ã§è¨±å¯ã™ã‚‹ã‹ã©ã†ã‹ã‚’定義ã—ã¾ã™ã€‚メッセージレベルã®æš—å·åŒ–ã¯ã€``ansible_winrm_transport`` ㌠``ntlm``ã€``kerberos``ã€ã¾ãŸã¯ ``credssp`` ã®å ´åˆã«ã®ã¿å¯èƒ½ã§ã™ã€‚デフォルトã§ã¯ã€ã“れ㯠``false`` ã§ã‚ã‚Šã€WinRM メッセージをデãƒãƒƒã‚°ã™ã‚‹å ´åˆã«é™ã‚Š ``true`` ã«è¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:312 +#: ../../rst/user_guide/windows_setup.rst:320 msgid "``Service\\Auth\\*``: These flags define what authentication options are allowed with the WinRM service. By default, ``Negotiate (NTLM)`` and ``Kerberos`` are enabled." msgstr "``Service\\Auth\\*``: ã“れらã®ãƒ•ãƒ©ã‚°ã¯ã€WinRM サービスã§è¨±å¯ã•ã‚Œã‚‹èªè¨¼ã‚ªãƒ—ションを定義ã—ã¾ã™ã€‚デフォルトã§ã¯ã€``Negotiate (NTLM)`` ãŠã‚ˆã³ ``Kerberos`` ãŒæœ‰åŠ¹ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:316 +#: ../../rst/user_guide/windows_setup.rst:324 msgid "``Service\\Auth\\CbtHardeningLevel``: Specifies whether channel binding tokens are not verified (None), verified but not required (Relaxed), or verified and required (Strict). CBT is only used when connecting with NTLM or Kerberos over HTTPS." msgstr "``Service\\Auth\\CbtHardeningLevel``: ãƒãƒ£ãƒ³ãƒãƒ«ãƒã‚¤ãƒ³ãƒ‡ã‚£ãƒ³ã‚°ãƒˆãƒ¼ã‚¯ãƒ³ã‚’検証ã—ãªã„ (None)ã€æ¤œè¨¼æ¸ˆã¿ã ãŒå¿…è¦ãªã„ (Relaxed)ã€æ¤œè¨¼æ¸ˆã¿ã§å¿…è¦ (Strict) ã®ã„ãšã‚Œã‹ã‚’指定ã—ã¾ã™ã€‚CBT ã¯ã€HTTPS ã® NTLM ã¾ãŸã¯ Kerberos ã§ã®æŽ¥ç¶šæ™‚ã«ã®ã¿ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:321 +#: ../../rst/user_guide/windows_setup.rst:329 msgid "``Service\\CertificateThumbprint``: This is the thumbprint of the certificate used to encrypt the TLS channel used with CredSSP authentication. By default this is empty; a self-signed certificate is generated when the WinRM service starts and is used in the TLS process." msgstr "``Service\\CertificateThumbprint``: ã“ã‚Œã¯ã€CredSSP èªè¨¼ã§ä½¿ç”¨ã•ã‚Œã‚‹ TLS ãƒãƒ£ãƒ³ãƒãƒ«ã®æš—å·åŒ–ã«ä½¿ç”¨ã•ã‚Œã‚‹è¨¼æ˜Žæ›¸ã®ã‚µãƒ プリントã§ã™ã€‚デフォルトã§ã¯ã€ã“ã‚Œã¯ç©ºã§ã™ã€‚自己署å証明書ã¯ã€WinRM サービスã®èµ·å‹•æ™‚ã«ç”Ÿæˆã•ã‚Œã€TLS プãƒã‚»ã‚¹ã§ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:326 +#: ../../rst/user_guide/windows_setup.rst:334 msgid "``Winrs\\MaxShellRunTime``: This is the maximum time, in milliseconds, that a remote command is allowed to execute." msgstr "``Winrs\\MaxShellRunTime``: リモートコマンドã®å®Ÿè¡Œã‚’許å¯ã™ã‚‹æœ€å¤§æ™‚間をミリ秒å˜ä½ã§æŒ‡å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:329 +#: ../../rst/user_guide/windows_setup.rst:337 msgid "``Winrs\\MaxMemoryPerShellMB``: This is the maximum amount of memory allocated per shell, including the shell's child processes." msgstr "``Winrs\\MaxMemoryPerShellMB``: シェルã®åプãƒã‚»ã‚¹ã‚’å«ã‚ã€ã‚·ã‚§ãƒ«ã”ã¨ã«å‰²ã‚Šå½“ã¦ã‚‰ã‚Œã‚‹ãƒ¡ãƒ¢ãƒªãƒ¼ã®æœ€å¤§é‡ã§ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:332 -msgid "To modify a setting under the ``Service`` key in PowerShell::" +#: ../../rst/user_guide/windows_setup.rst:340 +msgid "To modify a setting under the ``Service`` key in PowerShell:" msgstr "PowerShell ã® ``Service`` ã‚ーã§è¨å®šã‚’変更ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:340 -msgid "To modify a setting under the ``Winrs`` key in PowerShell::" +#: ../../rst/user_guide/windows_setup.rst:350 +msgid "To modify a setting under the ``Winrs`` key in PowerShell:" msgstr "PowerShell ã® ``Winrs`` ã‚ーã§è¨å®šã‚’変更ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:348 +#: ../../rst/user_guide/windows_setup.rst:360 msgid "If running in a domain environment, some of these options are set by GPO and cannot be changed on the host itself. When a key has been configured with GPO, it contains the text ``[Source=\"GPO\"]`` next to the value." msgstr "ドメイン環境ã§å‹•ä½œã—ã¦ã„ã‚‹å ´åˆã€ã“れらã®ã‚ªãƒ—ションã®ä¸€éƒ¨ã¯ GPO ã«ã‚ˆã£ã¦è¨å®šã•ã‚Œã€ãƒ›ã‚¹ãƒˆè‡ªä½“ã§ã¯å¤‰æ›´ã§ãã¾ã›ã‚“。GPO ã§è¨å®šã•ã‚ŒãŸã‚ーã«ã¯ã€å€¤ã®æ¨ªã« ``[Source=\"GPO\"]`` ã¨ã„ã†ãƒ†ã‚ストãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:353 +#: ../../rst/user_guide/windows_setup.rst:365 msgid "Common WinRM Issues" msgstr "一般的㪠WinRM ã®å•é¡Œ" -#: ../../rst/user_guide/windows_setup.rst:354 +#: ../../rst/user_guide/windows_setup.rst:366 msgid "Because WinRM has a wide range of configuration options, it can be difficult to setup and configure. Because of this complexity, issues that are shown by Ansible could in fact be issues with the host setup instead." msgstr "WinRM ã«ã¯ã•ã¾ã–ã¾ãªè¨å®šã‚ªãƒ—ションãŒã‚ã‚‹ãŸã‚ã€ã‚»ãƒƒãƒˆã‚¢ãƒƒãƒ—ã‚„è¨å®šãŒé›£ã—ã„å ´åˆãŒã‚ã‚Šã¾ã™ã€‚ãã®ãŸã‚ã€Ansible ã§è¡¨ç¤ºã•ã‚Œã‚‹å•é¡ŒãŒã€å®Ÿéš›ã«ã¯ãƒ›ã‚¹ãƒˆã®è¨å®šã®å•é¡Œã§ã‚ã‚‹å¯èƒ½æ€§ã‚‚ã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:358 -msgid "One easy way to determine whether a problem is a host issue is to run the following command from another Windows host to connect to the target Windows host::" +#: ../../rst/user_guide/windows_setup.rst:370 +msgid "One easy way to determine whether a problem is a host issue is to run the following command from another Windows host to connect to the target Windows host:" msgstr "å•é¡ŒãŒãƒ›ã‚¹ãƒˆã®å•é¡Œã§ã‚ã‚‹ã‹ã©ã†ã‹ã‚’判æ–ã™ã‚‹ç°¡å˜ãªæ–¹æ³•ã¨ã—ã¦ã€åˆ¥ã® Windows ホストã‹ã‚‰æ¬¡ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¦ã€å¯¾è±¡ã® Windows ホストã«æŽ¥ç¶šã™ã‚‹æ–¹æ³•ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:376 +#: ../../rst/user_guide/windows_setup.rst:390 msgid "If this fails, the issue is probably related to the WinRM setup. If it works, the issue may not be related to the WinRM setup; please continue reading for more troubleshooting suggestions." msgstr "失敗ã—ãŸå ´åˆã¯ã€WinRM ã®è¨å®šã«å•é¡ŒãŒã‚ã‚‹ã¨æ€ã‚ã‚Œã¾ã™ã€‚æˆåŠŸã—ãŸå ´åˆã¯ã€å•é¡ŒãŒ WinRM ã®è¨å®šã«é–¢é€£ã—ã¦ã„ãªã„å¯èƒ½æ€§ãŒã‚ã‚‹ãŸã‚ã€ã•ã‚‰ã«è©³ã—ã„トラブルシューティングã®æ–¹æ³•ã‚’ã”確èªãã ã•ã„。" -#: ../../rst/user_guide/windows_setup.rst:379 +#: ../../rst/user_guide/windows_setup.rst:393 msgid "HTTP 401/Credentials Rejected" msgstr "HTTP 401/èªè¨¼æƒ…å ±ã®æ‹’å¦" -#: ../../rst/user_guide/windows_setup.rst:380 +#: ../../rst/user_guide/windows_setup.rst:394 msgid "A HTTP 401 error indicates the authentication process failed during the initial connection. Some things to check for this are:" msgstr "HTTP 401 エラーã¯ã€æœ€åˆã®æŽ¥ç¶šæ™‚ã«èªè¨¼ãƒ—ãƒã‚»ã‚¹ãŒå¤±æ•—ã—ãŸã“ã¨ã‚’示ã—ã¾ã™ã€‚ã“れを確èªã™ã‚‹ãŸã‚ã®ã„ãã¤ã‹ã®é …ç›®ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:383 +#: ../../rst/user_guide/windows_setup.rst:397 msgid "Verify that the credentials are correct and set properly in your inventory with ``ansible_user`` and ``ansible_password``" msgstr "``ansible_user`` ãŠã‚ˆã³ ``ansible_password`` を使用ã—ã¦ã€èªè¨¼æƒ…å ±ãŒæ£ã—ãã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã«é©åˆ‡ã«è¨å®šã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:386 +#: ../../rst/user_guide/windows_setup.rst:400 msgid "Ensure that the user is a member of the local Administrators group or has been explicitly granted access (a connection test with the ``winrs`` command can be used to rule this out)." msgstr "ユーザーãŒãƒãƒ¼ã‚«ãƒ«ã® Administrators グループã®ãƒ¡ãƒ³ãƒãƒ¼ã§ã‚ã‚‹ã‹ã€æ˜Žç¤ºçš„ã«ã‚¢ã‚¯ã‚»ã‚¹ã‚’許å¯ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„ (``winrs`` コマンドã«ã‚ˆã‚‹æŽ¥ç¶šãƒ†ã‚¹ãƒˆã§é™¤å¤–ã§ãã¾ã™)。" -#: ../../rst/user_guide/windows_setup.rst:390 +#: ../../rst/user_guide/windows_setup.rst:404 msgid "Make sure that the authentication option set by ``ansible_winrm_transport`` is enabled under ``Service\\Auth\\*``" msgstr "``ansible_winrm_transport`` ã§è¨å®šã—ãŸèªè¨¼ã‚ªãƒ—ションãŒã€``Service\\Auth\\*`` ã§æœ‰åŠ¹ã«ãªã£ã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_setup.rst:393 +#: ../../rst/user_guide/windows_setup.rst:407 msgid "If running over HTTP and not HTTPS, use ``ntlm``, ``kerberos`` or ``credssp`` with ``ansible_winrm_message_encryption: auto`` to enable message encryption. If using another authentication option or if the installed pywinrm version cannot be upgraded, the ``Service\\AllowUnencrypted`` can be set to ``true`` but this is only recommended for troubleshooting" msgstr "HTTPS ã§ã¯ãªã HTTP ã§å®Ÿè¡Œã™ã‚‹å ´åˆã¯ã€``ntlm``ã€``kerberos``ã€ã¾ãŸã¯ ``credssp`` 㨠``ansible_winrm_message_encryption: auto`` を使用ã—ã¦ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã®æš—å·åŒ–を有効ã«ã—ã¦ãã ã•ã„。他ã®èªè¨¼ã‚ªãƒ—ションを使用ã—ã¦ã„ã‚‹å ´åˆã‚„ã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ pywinrm ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’アップグレードã§ããªã„å ´åˆã¯ã€``Service\\AllowUnencrypted`` ã‚’``true`` ã«è¨å®šã§ãã¾ã™ãŒã€ã“ã‚Œã¯ãƒˆãƒ©ãƒ–ルシューティングã®ãŸã‚ã«ã®ã¿æŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:399 +#: ../../rst/user_guide/windows_setup.rst:413 msgid "Ensure the downstream packages ``pywinrm``, ``requests-ntlm``, ``requests-kerberos``, and/or ``requests-credssp`` are up to date using ``pip``." msgstr "ダウンストリームパッケージã§ã‚ã‚‹ ``pywinrm``ã€``requests-ntlm``ã€``requests-kerberos``ã€ã¾ãŸã¯ ``requests-credssp``ã€ã‚‚ã—ãã¯ãã®çµ„ã¿åˆã‚ã›ãŒ ``pip`` を使用ã—ã¦æœ€æ–°ã®çŠ¶æ…‹ã«ãªã£ã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:402 +#: ../../rst/user_guide/windows_setup.rst:416 msgid "If using Kerberos authentication, ensure that ``Service\\Auth\\CbtHardeningLevel`` is not set to ``Strict``." msgstr "Kerberos èªè¨¼ã‚’使用ã™ã‚‹å ´åˆã¯ã€``Service\\Auth\\CbtHardeningLevel`` ㌠``Strict`` ã«è¨å®šã•ã‚Œã¦ã„ãªã„ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_setup.rst:405 +#: ../../rst/user_guide/windows_setup.rst:419 msgid "When using Basic or Certificate authentication, make sure that the user is a local account and not a domain account. Domain accounts do not work with Basic and Certificate authentication." msgstr "Basic èªè¨¼ã‚„ Certificate èªè¨¼ã‚’使用ã™ã‚‹éš›ã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒãƒ‰ãƒ¡ã‚¤ãƒ³ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã§ã¯ãªãã€ãƒãƒ¼ã‚«ãƒ«ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã§ã‚ã‚‹ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。ドメインアカウントã¯ã€Basic èªè¨¼ã‚„ Certificate èªè¨¼ã§ã¯æ©Ÿèƒ½ã—ã¾ã›ã‚“。" -#: ../../rst/user_guide/windows_setup.rst:410 +#: ../../rst/user_guide/windows_setup.rst:424 msgid "HTTP 500 Error" msgstr "HTTP 500 Error" -#: ../../rst/user_guide/windows_setup.rst:411 +#: ../../rst/user_guide/windows_setup.rst:425 msgid "These indicate an error has occurred with the WinRM service. Some things to check for include:" msgstr "ã“れらã¯ã€WinRM サービスã§ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã—ãŸã“ã¨ã‚’示ã—ã¦ã„ã¾ã™ã€‚確èªã™ã¹ã点ã¯ä»¥ä¸‹ã®é€šã‚Šã§ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:414 +#: ../../rst/user_guide/windows_setup.rst:428 msgid "Verify that the number of current open shells has not exceeded either ``WinRsMaxShellsPerUser`` or any of the other Winrs quotas haven't been exceeded." msgstr "ç¾åœ¨ã®ã‚ªãƒ¼ãƒ—ンシェルã®æ•°ãŒ ``WinRsMaxShellsPerUser`` ã®ã©ã¡ã‚‰ã‹ã‚’超ãˆã¦ã„ãªã„ã‹ã€ã¾ãŸã¯ä»–ã® Winrs ã®ã‚¯ã‚©ãƒ¼ã‚¿ã‚’超ãˆã¦ã„ãªã„ã‹ã‚’確èªã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_setup.rst:419 +#: ../../rst/user_guide/windows_setup.rst:433 msgid "Timeout Errors" msgstr "タイムアウトエラー" -#: ../../rst/user_guide/windows_setup.rst:420 +#: ../../rst/user_guide/windows_setup.rst:434 msgid "These usually indicate an error with the network connection where Ansible is unable to reach the host. Some things to check for include:" msgstr "ã“れらã¯é€šå¸¸ã€Ansible ãŒãƒ›ã‚¹ãƒˆã«åˆ°é”ã§ããªã„ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯æŽ¥ç¶šã®ã‚¨ãƒ©ãƒ¼ã‚’示ã—ã¦ã„ã¾ã™ã€‚ãƒã‚§ãƒƒã‚¯é …ç›®ã«ã¯ä»¥ä¸‹ãŒå«ã¾ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:423 +#: ../../rst/user_guide/windows_setup.rst:437 msgid "Make sure the firewall is not set to block the configured WinRM listener ports" msgstr "ファイアウォールãŒã€è¨å®šã•ã‚ŒãŸ WinRM リスナーãƒãƒ¼ãƒˆã‚’ブãƒãƒƒã‚¯ã™ã‚‹ã‚ˆã†ã«è¨å®šã•ã‚Œã¦ã„ãªã„ã“ã¨ã‚’確èªã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:424 +#: ../../rst/user_guide/windows_setup.rst:438 msgid "Ensure that a WinRM listener is enabled on the port and path set by the host vars" msgstr "WinRM リスナーãŒã€ãƒ›ã‚¹ãƒˆå¤‰æ•°ã«ã‚ˆã£ã¦è¨å®šã•ã‚ŒãŸãƒãƒ¼ãƒˆãŠã‚ˆã³ãƒ‘スã§æœ‰åŠ¹ã«ãªã£ã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:425 +#: ../../rst/user_guide/windows_setup.rst:439 msgid "Ensure that the ``winrm`` service is running on the Windows host and configured for automatic start" msgstr "Windows ホスト上㧠``winrm`` サービスãŒç¨¼å‹•ã—ã¦ãŠã‚Šã€è‡ªå‹•èµ·å‹•ã™ã‚‹ã‚ˆã†ã«è¨å®šã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:429 +#: ../../rst/user_guide/windows_setup.rst:443 msgid "Connection Refused Errors" msgstr "接続拒å¦ã‚¨ãƒ©ãƒ¼" -#: ../../rst/user_guide/windows_setup.rst:430 +#: ../../rst/user_guide/windows_setup.rst:444 msgid "These usually indicate an error when trying to communicate with the WinRM service on the host. Some things to check for:" msgstr "ã“れらã¯é€šå¸¸ã€ãƒ›ã‚¹ãƒˆä¸Šã® WinRM サービスã¨é€šä¿¡ã—よã†ã¨ã™ã‚‹éš›ã«ã‚¨ãƒ©ãƒ¼ã‚’示ã—ã¾ã™ã€‚ã„ãã¤ã‹ã®ãƒã‚§ãƒƒã‚¯é …ç›®ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:433 +#: ../../rst/user_guide/windows_setup.rst:447 msgid "Ensure that the WinRM service is up and running on the host. Use ``(Get-Service -Name winrm).Status`` to get the status of the service." msgstr "ホスト上㧠WinRM サービスãŒç¨¼åƒã—ã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚``(Get-Service -Name winrm).Status`` を使用ã—ã¦ã€ã‚µãƒ¼ãƒ“スã®ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã‚’å–å¾—ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:435 +#: ../../rst/user_guide/windows_setup.rst:449 msgid "Check that the host firewall is allowing traffic over the WinRM port. By default this is ``5985`` for HTTP and ``5986`` for HTTPS." msgstr "ホストå´ã®ãƒ•ã‚¡ã‚¤ã‚¢ã‚¦ã‚©ãƒ¼ãƒ«ãŒã€WinRM ãƒãƒ¼ãƒˆã¸ã®ãƒˆãƒ©ãƒ•ã‚£ãƒƒã‚¯ã‚’許å¯ã—ã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚デフォルトã§ã¯ã€HTTP ã§ã¯ ``5985``ã€HTTPS ã§ã¯ ``5986`` ã¨ãªã£ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:438 +#: ../../rst/user_guide/windows_setup.rst:452 msgid "Sometimes an installer may restart the WinRM or HTTP service and cause this error. The best way to deal with this is to use ``win_psexec`` from another Windows host." msgstr "インストーラー㌠WinRM ã‚„ HTTP サービスをå†èµ·å‹•ã—ã¦ã—ã¾ã„ã€ã“ã®ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã™ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã«å¯¾å‡¦ã™ã‚‹æœ€è‰¯ã®æ–¹æ³•ã¯ã€åˆ¥ã® Windows ホストã‹ã‚‰ ``win_psexec`` を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:443 +#: ../../rst/user_guide/windows_setup.rst:457 msgid "Failure to Load Builtin Modules" msgstr "組ã¿è¾¼ã¿ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®èªã¿è¾¼ã¿ã«å¤±æ•—" -#: ../../rst/user_guide/windows_setup.rst:444 +#: ../../rst/user_guide/windows_setup.rst:458 msgid "If powershell fails with an error message similar to ``The 'Out-String' command was found in the module 'Microsoft.PowerShell.Utility', but the module could not be loaded.`` then there could be a problem trying to access all the paths specified by the ``PSModulePath`` environment variable. A common cause of this issue is that the ``PSModulePath`` environment variable contains a UNC path to a file share and because of the double hop/credential delegation issue the Ansible process cannot access these folders. The way around this problems is to either:" msgstr "``The 'Out-String' command was found in the module 'Microsoft.PowerShell.Utility', but the module could not be loaded.`` ã®ã‚ˆã†ãªã‚¨ãƒ©ãƒ¼ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã§ powershell ãŒå¤±æ•—ã™ã‚‹å ´åˆã¯ã€``PSModulePath`` 環境変数ã§æŒ‡å®šã•ã‚ŒãŸã™ã¹ã¦ã®ãƒ‘スã«ã‚¢ã‚¯ã‚»ã‚¹ã—よã†ã¨ã™ã‚‹ã¨å•é¡ŒãŒç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®å•é¡Œã®ä¸€èˆ¬çš„ãªåŽŸå› ã¯ã€``PSModulePath`` 環境変数ã«ãƒ•ã‚¡ã‚¤ãƒ«å…±æœ‰ã¸ã® UNC パスãŒå«ã¾ã‚Œã¦ãŠã‚Šã€ãƒ€ãƒ–ルホップ/èªè¨¼æƒ…å ±ã®å§”è²å•é¡Œã®ãŸã‚ã« Ansible プãƒã‚»ã‚¹ãŒã“れらã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ããªã„ã“ã¨ã§ã™ã€‚ã“ã®å•é¡Œã‚’回é¿ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®æ–¹æ³•ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:450 +#: ../../rst/user_guide/windows_setup.rst:464 msgid "Remove the UNC path from the ``PSModulePath`` environment variable, or" msgstr "``PSModulePath`` 環境変数ã‹ã‚‰ UNC パスを削除ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:451 +#: ../../rst/user_guide/windows_setup.rst:465 msgid "Use an authentication option that supports credential delegation like ``credssp`` or ``kerberos`` with credential delegation enabled" msgstr "èªè¨¼æƒ…å ±ã®å§”è²ã‚’有効ã«ã—㟠``credssp`` ã‚„ ``kerberos`` ã®ã‚ˆã†ãªã€èªè¨¼æƒ…å ±ã®å§”è²ã‚’サãƒãƒ¼ãƒˆã™ã‚‹èªè¨¼ã‚ªãƒ—ションを使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:453 +#: ../../rst/user_guide/windows_setup.rst:467 msgid "See `KB4076842 <https://support.microsoft.com/en-us/help/4076842>`_ for more information on this problem." msgstr "ã“ã®å•é¡Œã®è©³ç´°ã¯ã€ã€Œ`KB4076842 <https://support.microsoft.com/en-us/help/4076842>`_ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_setup.rst:457 +#: ../../rst/user_guide/windows_setup.rst:471 msgid "Windows SSH Setup" msgstr "Windows SSH ã®è¨å®š" -#: ../../rst/user_guide/windows_setup.rst:458 +#: ../../rst/user_guide/windows_setup.rst:472 msgid "Ansible 2.8 has added an experimental SSH connection for Windows managed nodes." msgstr "Ansible 2.8 ã§ã¯ã€Windows 管ç†ãƒŽãƒ¼ãƒ‰ã®å®Ÿé¨“的㪠SSH 接続ãŒè¿½åŠ ã•ã‚Œã¾ã—ãŸã€‚" -#: ../../rst/user_guide/windows_setup.rst:461 +#: ../../rst/user_guide/windows_setup.rst:475 msgid "Use this feature at your own risk! Using SSH with Windows is experimental, the implementation may make backwards incompatible changes in feature releases. The server side components can be unreliable depending on the version that is installed." msgstr "ã“ã®æ©Ÿèƒ½ã¯ã”自身ã®è²¬ä»»ã§ãŠä½¿ã„ãã ã•ã„。Windows ã§ã® SSH ã®ä½¿ç”¨ã¯å®Ÿé¨“çš„ãªã‚‚ã®ã§ã‚ã‚Šã€å®Ÿè£…ã¯æ©Ÿèƒ½ãƒªãƒªãƒ¼ã‚¹ã«ãŠã„ã¦å¾Œæ–¹äº’æ›æ€§ã®ãªã„変更を行ã†å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚ã¾ãŸã€ã‚µãƒ¼ãƒãƒ¼å´ã®ã‚³ãƒ³ãƒãƒ¼ãƒãƒ³ãƒˆã¯ã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«ã‚ˆã£ã¦ã¯ä¿¡é ¼æ€§ã«æ¬ ã‘ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:467 +#: ../../rst/user_guide/windows_setup.rst:481 msgid "Installing OpenSSH using Windows Settings" msgstr "Windows è¨å®šã‚’使用ã—㟠OpenSSH ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/user_guide/windows_setup.rst:468 +#: ../../rst/user_guide/windows_setup.rst:482 msgid "OpenSSH can be used to connect Window 10 clients to Windows Server 2019. OpenSSH Client is available to install on Windows 10 build 1809 and later, while OpenSSH Server is available to install on Windows Server 2019 and later." msgstr "OpenSSH ã¯ã€WinkW 10 クライアントを Windows Server 2019 ã«æŽ¥ç¶šã™ã‚‹ãŸã‚ã«ä½¿ç”¨ã§ãã¾ã™ã€‚OpenSSH クライアント㯠Windows 10 ビルド 1809 以é™ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ãã¾ã™ãŒã€OpenSSH Server 㯠Windows Server 2019 以é™ã«åˆ©ç”¨ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:471 +#: ../../rst/user_guide/windows_setup.rst:485 msgid "Please refer `this guide <https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse>`_." msgstr "`this guide <https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_setup.rst:474 +#: ../../rst/user_guide/windows_setup.rst:488 msgid "Installing Win32-OpenSSH" msgstr "Win32-OpenSSH ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/user_guide/windows_setup.rst:475 +#: ../../rst/user_guide/windows_setup.rst:489 msgid "The first step to using SSH with Windows is to install the `Win32-OpenSSH <https://github.com/PowerShell/Win32-OpenSSH>`_ service on the Windows host. Microsoft offers a way to install ``Win32-OpenSSH`` through a Windows capability but currently the version that is installed through this process is too old to work with Ansible. To install ``Win32-OpenSSH`` for use with Ansible, select one of these installation options:" msgstr "Windows 㧠SSH を利用ã™ã‚‹ãŸã‚ã®æœ€åˆã®ã‚¹ãƒ†ãƒƒãƒ—ã¯ã€Windows ホスト㫠`Win32-OpenSSH <https://github.com/PowerShell/Win32-OpenSSH>`_ サービスをインストールã™ã‚‹ã“ã¨ã§ã™ã€‚Microsoft 社ã§ã¯ã€Windows ã®æ©Ÿèƒ½ã‚’利用ã—㦠``Win32-OpenSSH`` をインストールã™ã‚‹æ–¹æ³•ã‚’æä¾›ã—ã¦ã„ã¾ã™ãŒã€ç¾åœ¨ã€ã“ã®æ–¹æ³•ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã‚‹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯ã€Ansible ã§å‹•ä½œã•ã›ã‚‹ã«ã¯å¤ã™ãŽã¾ã™ã€‚Ansible ã§ä½¿ç”¨ã™ã‚‹ãŸã‚ã« ``Win32-OpenSSH`` をインストールã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã‚ªãƒ—ションã®ã„ãšã‚Œã‹ã‚’é¸æŠžã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:481 +#: ../../rst/user_guide/windows_setup.rst:495 msgid "Manually install the service, following the `install instructions <https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH>`_ from Microsoft." msgstr "Microsoft 社ãŒæä¾›ã™ã‚‹ `ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«æ‰‹é † <https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH>`_ ã«å¾“ã£ã¦ã€ã‚µãƒ¼ãƒ“スを手動ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_setup.rst:484 -msgid "Install the `openssh <https://chocolatey.org/packages/openssh>`_ package using Chocolatey::" +#: ../../rst/user_guide/windows_setup.rst:498 +msgid "Install the `openssh <https://chocolatey.org/packages/openssh>`_ package using Chocolatey:" msgstr "Chocolatey を使用ã—㦠`openssh <https://chocolatey.org/packages/openssh>`_ パッケージをインストールã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:488 -msgid "Use ``win_chocolatey`` to install the service::" +#: ../../rst/user_guide/windows_setup.rst:504 +msgid "Use ``win_chocolatey`` to install the service" msgstr "``win_chocolatey`` を使用ã—ã¦ã‚µãƒ¼ãƒ“スをインストールã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:496 -msgid "Use an existing Ansible Galaxy role like `jborean93.win_openssh <https://galaxy.ansible.com/jborean93/win_openssh>`_::" +#: ../../rst/user_guide/windows_setup.rst:514 +msgid "Use an existing Ansible Galaxy role like `jborean93.win_openssh <https://galaxy.ansible.com/jborean93/win_openssh>`_:" msgstr "`jborean93.win_openssh <https://galaxy.ansible.com/jborean93/win_openssh>`_ ãªã©ã®æ—¢å˜ã® Ansible Galaxy ãƒãƒ¼ãƒ«ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:509 +#: ../../rst/user_guide/windows_setup.rst:531 msgid "``Win32-OpenSSH`` is still a beta product and is constantly being updated to include new features and bugfixes. If you are using SSH as a connection option for Windows, it is highly recommend you install the latest release from one of the 3 methods above." msgstr "``Win32-OpenSSH`` ã¯æœªã ベータ版ã®è£½å“ã§ã‚ã‚Šã€æ–°æ©Ÿèƒ½ã‚„ãƒã‚°ä¿®æ£ã‚’å«ã‚ã¦å¸¸ã«æ›´æ–°ã•ã‚Œã¦ã„ã¾ã™ã€‚Windows 㧠SSH 接続をã”利用ã®æ–¹ã¯ã€ä¸Šè¨˜ 3 ã¤ã®æ–¹æ³•ã‹ã‚‰æœ€æ–°ç‰ˆã‚’インストールã™ã‚‹ã“ã¨ãŒå¼·ã推奨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:515 +#: ../../rst/user_guide/windows_setup.rst:537 msgid "Configuring the Win32-OpenSSH shell" msgstr "Win32-OpenSSH シェルã®è¨å®š" -#: ../../rst/user_guide/windows_setup.rst:517 -msgid "By default ``Win32-OpenSSH`` will use ``cmd.exe`` as a shell. To configure a different shell, use an Ansible task to define the registry setting::" +#: ../../rst/user_guide/windows_setup.rst:539 +msgid "By default ``Win32-OpenSSH`` will use ``cmd.exe`` as a shell. To configure a different shell, use an Ansible task to define the registry setting:" msgstr "デフォルトã§ã¯ã€``Win32-OpenSSH`` 㯠``cmd.exe`` をシェルã¨ã—ã¦ä½¿ç”¨ã—ã¾ã™ã€‚別ã®ã‚·ã‚§ãƒ«ã‚’è¨å®šã™ã‚‹ã«ã¯ã€Ansible タスクを使用ã—ã¦ã€ãƒ¬ã‚¸ã‚¹ãƒˆãƒªãƒ¼è¨å®šã‚’定義ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:536 +#: ../../rst/user_guide/windows_setup.rst:560 msgid "Win32-OpenSSH Authentication" msgstr "Win32-OpenSSH èªè¨¼" -#: ../../rst/user_guide/windows_setup.rst:537 +#: ../../rst/user_guide/windows_setup.rst:561 msgid "Win32-OpenSSH authentication with Windows is similar to SSH authentication on Unix/Linux hosts. You can use a plaintext password or SSH public key authentication, add public keys to an ``authorized_key`` file in the ``.ssh`` folder of the user's profile directory, and configure the service using the ``sshd_config`` file used by the SSH service as you would on a Unix/Linux host." msgstr "Windows ã§ã® Win32-OpenSSH èªè¨¼ã¯ã€Unix/Linux ホストã§ã® SSH èªè¨¼ã«ä¼¼ã¦ã„ã¾ã™ã€‚平文ã®ãƒ‘スワードã¾ãŸã¯ SSH 公開éµèªè¨¼ã‚’使用ã—ã€å…¬é–‹éµã‚’ユーザーã®ãƒ—ãƒãƒ•ã‚¡ã‚¤ãƒ«ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªãƒ¼ã® ``.ssh`` ディレクトリーã«ã‚ã‚‹ ``authorized_key`` ファイルã«è¿½åŠ ã—ã€Unix/Linux ホストã¨åŒæ§˜ã« SSH サービスã§ä½¿ç”¨ã•ã‚Œã‚‹ ``sshd_config`` ファイルを使用ã—ã¦ã‚µãƒ¼ãƒ“スをè¨å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:544 +#: ../../rst/user_guide/windows_setup.rst:568 msgid "When using SSH key authentication with Ansible, the remote session won't have access to the user's credentials and will fail when attempting to access a network resource. This is also known as the double-hop or credential delegation issue. There are two ways to work around this issue:" msgstr "Ansible 㧠SSH ã‚ーèªè¨¼ã‚’使用ã™ã‚‹å ´åˆã¯ã€ãƒªãƒ¢ãƒ¼ãƒˆã‚»ãƒƒã‚·ãƒ§ãƒ³ãŒãƒ¦ãƒ¼ã‚¶ãƒ¼ã®èªè¨¼æƒ…å ±ã«ã‚¢ã‚¯ã‚»ã‚¹ã§ããšã€ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒªã‚½ãƒ¼ã‚¹ã«ã‚¢ã‚¯ã‚»ã‚¹ã—よã†ã¨ã™ã‚‹ã¨å¤±æ•—ã™ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€ãƒ€ãƒ–ルホップやèªè¨¼æƒ…å ±ã®å§”è²ã®å•é¡Œã¨ã—ã¦ã‚‚知られã¦ã„ã¾ã™ã€‚ã“ã®å•é¡Œã‚’回é¿ã™ã‚‹ã«ã¯ 2 ã¤ã®æ–¹æ³•ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:549 +#: ../../rst/user_guide/windows_setup.rst:573 msgid "Use plaintext password auth by setting ``ansible_password``" msgstr "``ansible_password`` ã‚’è¨å®šã—ã¦å¹³æ–‡ãƒ†ã‚ストã®ãƒ‘スワードèªè¨¼ã‚’使用ã™ã‚‹" -#: ../../rst/user_guide/windows_setup.rst:550 +#: ../../rst/user_guide/windows_setup.rst:574 msgid "Use ``become`` on the task with the credentials of the user that needs access to the remote resource" msgstr "リモートリソースã¸ã®ã‚¢ã‚¯ã‚»ã‚¹ã‚’å¿…è¦ã¨ã™ã‚‹ãƒ¦ãƒ¼ã‚¶ãƒ¼ã®èªè¨¼æƒ…å ±ã‚’ä½¿ç”¨ã—ã¦ã€ã‚¿ã‚¹ã‚¯ã§ ``become`` を使用ã™ã‚‹" -#: ../../rst/user_guide/windows_setup.rst:553 +#: ../../rst/user_guide/windows_setup.rst:577 msgid "Configuring Ansible for SSH on Windows" msgstr "Windows 㧠SSH 用㫠Ansible ã®è¨å®š" -#: ../../rst/user_guide/windows_setup.rst:554 +#: ../../rst/user_guide/windows_setup.rst:578 msgid "To configure Ansible to use SSH for Windows hosts, you must set two connection variables:" msgstr "Ansible ㌠Windows ホスト㫠SSH を使用ã™ã‚‹ã‚ˆã†ã«è¨å®šã™ã‚‹ã«ã¯ã€æŽ¥ç¶šå¤‰æ•°ã‚’ 2 ã¤è¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:556 +#: ../../rst/user_guide/windows_setup.rst:580 msgid "set ``ansible_connection`` to ``ssh``" msgstr "``ansible_connection`` ã‚’ ``ssh`` ã«è¨å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:557 +#: ../../rst/user_guide/windows_setup.rst:581 msgid "set ``ansible_shell_type`` to ``cmd`` or ``powershell``" msgstr "``ansible_shell_type`` ã‚’ ``cmd`` ã¾ãŸã¯ ``powershell`` ã«è¨å®šã™ã‚‹" -#: ../../rst/user_guide/windows_setup.rst:559 +#: ../../rst/user_guide/windows_setup.rst:583 msgid "The ``ansible_shell_type`` variable should reflect the ``DefaultShell`` configured on the Windows host. Set to ``cmd`` for the default shell or set to ``powershell`` if the ``DefaultShell`` has been changed to PowerShell." msgstr "``ansible_shell_type`` 変数ã«ã¯ã€Windows ホストã§è¨å®šã•ã‚Œã¦ã„ã‚‹``DefaultShell`` ã‚’åæ˜ ã•ã›ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚デフォルトシェルã®å ´åˆã¯ ``cmd`` ã«ã€``DefaultShell`` ㌠PowerShell ã«å¤‰æ›´ã—ã¦ã„ã‚‹å ´åˆã¯ ``powershell`` ã«è¨å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:564 +#: ../../rst/user_guide/windows_setup.rst:588 msgid "Known issues with SSH on Windows" msgstr "Windows ã§ã® SSH ã«é–¢ã™ã‚‹æ—¢çŸ¥ã®å•é¡Œ" -#: ../../rst/user_guide/windows_setup.rst:565 +#: ../../rst/user_guide/windows_setup.rst:589 msgid "Using SSH with Windows is experimental, and we expect to uncover more issues. Here are the known ones:" msgstr "Windows ã§ã® SSH ã®ä½¿ç”¨ã¯å®Ÿé¨“çš„ãªã‚‚ã®ã§ã‚ã‚Šã€ã‚ˆã‚Šå¤šãã®å•é¡ŒãŒæ˜Žã‚‰ã‹ã«ãªã‚‹ã“ã¨ã‚’期待ã—ã¦ã„ã¾ã™ã€‚ã“ã“ã§ã¯ã€æ—¢çŸ¥ã®ã‚‚ã®ã‚’紹介ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_setup.rst:568 +#: ../../rst/user_guide/windows_setup.rst:592 msgid "Win32-OpenSSH versions older than ``v7.9.0.0p1-Beta`` do not work when ``powershell`` is the shell type" msgstr "``powershell`` ãŒã‚·ã‚§ãƒ«ã‚¿ã‚¤ãƒ—ã®å ´åˆã¯ã€``v7.9.0.0p1-Beta`` よりもå¤ã„ Win32-OpenSSH ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯æ©Ÿèƒ½ã—ã¾ã›ã‚“。" -#: ../../rst/user_guide/windows_setup.rst:569 +#: ../../rst/user_guide/windows_setup.rst:593 msgid "While SCP should work, SFTP is the recommended SSH file transfer mechanism to use when copying or fetching a file" msgstr "SCP も有効ã§ã™ãŒã€SFTP ã¯ã€ãƒ•ã‚¡ã‚¤ãƒ«ã®ã‚³ãƒ”ーã¾ãŸã¯å–得時ã«ä½¿ç”¨ã™ã‚‹ã€æŽ¨å¥¨ã•ã‚Œã‚‹ SSH ファイル転é€ãƒ¡ã‚«ãƒ‹ã‚ºãƒ ã§ã™ã€‚" @@ -13387,91 +13394,91 @@ msgid "``<TAB>``, ``<SPACE>``, ``<NBSP>``, ``<LNSP>``, ``<PSP>`` -- Special char msgstr "``<TAB>``ã€``<SPACE>``ã€``<NBSP>``ã€``<LNSP>``ã€``<PSP>`` -- 特殊文å—" #: ../../rst/user_guide/windows_usage.rst:399 -#: ../../rst/user_guide/windows_usage.rst:449 +#: ../../rst/user_guide/windows_usage.rst:453 msgid "``\\x..`` -- 2-digit hex escape" msgstr "``\\x..`` -- 2 æ¡ã® 16 進エスケープ" #: ../../rst/user_guide/windows_usage.rst:401 -#: ../../rst/user_guide/windows_usage.rst:451 +#: ../../rst/user_guide/windows_usage.rst:455 msgid "``\\u....`` -- 4-digit hex escape" msgstr "``\\u....`` -- 4 æ¡ã® 16 進エスケープ" #: ../../rst/user_guide/windows_usage.rst:403 -#: ../../rst/user_guide/windows_usage.rst:453 +#: ../../rst/user_guide/windows_usage.rst:457 msgid "``\\U........`` -- 8-digit hex escape" msgstr "``\\U........`` -- 8 æ¡ã® 16 進エスケープ" #: ../../rst/user_guide/windows_usage.rst:405 -msgid "Here are some examples on how to write Windows paths::" +msgid "Here are some examples on how to write Windows paths:" msgstr "Windows パスã®è¨˜è¿°æ–¹æ³•ã®ä¾‹ã‚’次ã«ç¤ºã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_usage.rst:419 +#: ../../rst/user_guide/windows_usage.rst:421 msgid "This is an example which will fail:" msgstr "ã“ã‚Œã¯å¤±æ•—ã™ã‚‹ä¾‹ã§ã™ã€‚" -#: ../../rst/user_guide/windows_usage.rst:426 -msgid "This example shows the use of single quotes when they are required::" +#: ../../rst/user_guide/windows_usage.rst:428 +msgid "This example shows the use of single quotes when they are required:" msgstr "ã“ã®ä¾‹ã¯ã€å¿…è¦ãªå ´åˆã®ä¸€é‡å¼•ç”¨ç¬¦ã®ä½¿ç”¨ã‚’示ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_usage.rst:435 +#: ../../rst/user_guide/windows_usage.rst:439 msgid "Legacy key=value Style" msgstr "従æ¥ã® key=value スタイル" -#: ../../rst/user_guide/windows_usage.rst:436 +#: ../../rst/user_guide/windows_usage.rst:440 msgid "The legacy ``key=value`` syntax is used on the command line for ad hoc commands, or inside playbooks. The use of this style is discouraged within playbooks because backslash characters need to be escaped, making playbooks harder to read. The legacy syntax depends on the specific implementation in Ansible, and quoting (both single and double) does not have any effect on how it is parsed by Ansible." msgstr "従æ¥ã® ``key=value`` ã®æ§‹æ–‡ã¯ã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ã§ã®ã‚¢ãƒ‰ãƒ›ãƒƒã‚¯ãªã‚³ãƒžãƒ³ãƒ‰ã‚„ Playbook 内ã§ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚ãƒãƒƒã‚¯ã‚¹ãƒ©ãƒƒã‚·ãƒ¥æ–‡å—をエスケープã™ã‚‹å¿…è¦ãŒã‚ã‚Šã€Playbook ãŒèªã¿ã¥ã‚‰ããªã‚‹ãŸã‚ã€Playbook 内ã§ã¯ã“ã®ã‚¹ã‚¿ã‚¤ãƒ«ã®ä½¿ç”¨ã¯æŽ¨å¥¨ã•ã‚Œã¾ã›ã‚“。従æ¥ã®æ§‹æ–‡ã¯ã€Ansible ã®ç‰¹å®šã®å®Ÿè£…ã«ä¾å˜ã—ã¦ãŠã‚Šã€å¼•ç”¨ç¬¦ (å˜ä¸€ãŠã‚ˆã³äºŒé‡) ã¯ã€Ansible ã§ã®è§£æžæ–¹æ³•ã«ã¯å½±éŸ¿ã—ã¾ã›ã‚“。" -#: ../../rst/user_guide/windows_usage.rst:443 +#: ../../rst/user_guide/windows_usage.rst:447 msgid "The Ansible key=value parser parse_kv() considers the following escape sequences:" msgstr "Ansible ã® key=value パーサー parse_kv() ã¯ã€ä»¥ä¸‹ã®ã‚¨ã‚¹ã‚±ãƒ¼ãƒ—シーケンスを考慮ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_usage.rst:446 +#: ../../rst/user_guide/windows_usage.rst:450 msgid "``\\``, ``'``, ``\"``, ``\\a``, ``\\b``, ``\\f``, ``\\n``, ``\\r``, ``\\t`` and ``\\v`` -- Single character escape" msgstr "``\\``ã€``'``ã€``\"``ã€``\\a``ã€``\\b``ã€``\\f``ã€``\\n" "``ã€``\\r``ã€``\\t``ã€ãŠã‚ˆã³ ``\\v`` -- 一文å—ã®ã‚¨ã‚¹ã‚±ãƒ¼ãƒ—" -#: ../../rst/user_guide/windows_usage.rst:455 +#: ../../rst/user_guide/windows_usage.rst:459 msgid "``\\N{...}`` -- Unicode character by name" msgstr "``\\N{...}`` -- åå‰ã«ã‚ˆã‚‹ Unicode æ–‡å—" -#: ../../rst/user_guide/windows_usage.rst:457 +#: ../../rst/user_guide/windows_usage.rst:461 msgid "This means that the backslash is an escape character for some sequences, and it is usually safer to escape a backslash when in this form." msgstr "ã“ã‚Œã¯ã€ãƒãƒƒã‚¯ã‚¹ãƒ©ãƒƒã‚·ãƒ¥ãŒã„ãã¤ã‹ã®ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ã®ã‚¨ã‚¹ã‚±ãƒ¼ãƒ—æ–‡å—ã«ãªã£ã¦ã„ã‚‹ã“ã¨ã‚’æ„味ã—ã¦ãŠã‚Šã€é€šå¸¸ã€ã“ã®å½¢å¼ã®å ´åˆã¯ãƒãƒƒã‚¯ã‚¹ãƒ©ãƒƒã‚·ãƒ¥ã‚’エスケープã™ã‚‹æ–¹ãŒå®‰å…¨ã§ã™ã€‚" -#: ../../rst/user_guide/windows_usage.rst:460 +#: ../../rst/user_guide/windows_usage.rst:464 msgid "Here are some examples of using Windows paths with the key=value style:" msgstr "key=value スタイル㧠Windows パスを使用ã™ã‚‹ä¾‹ã‚’次ã«ç¤ºã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_usage.rst:482 +#: ../../rst/user_guide/windows_usage.rst:486 msgid "The failing examples don't fail outright but will substitute ``\\t`` with the ``<TAB>`` character resulting in ``tempdir`` being ``C:\\Windows<TAB>emp``." msgstr "失敗ã—ãŸä¾‹ã§ã¯ã€å®Œå…¨ã«å¤±æ•—ã™ã‚‹ã‚ã‘ã§ã¯ã‚ã‚Šã¾ã›ã‚“ãŒã€``\\t`` ã‚’ ``<TAB>`` ã®æ–‡å—ã§ç½®ãæ›ãˆã¦ã€``tempdir`` ã‚’ ``C:\\Windows<TAB>emp`` ã«ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_usage.rst:486 -#: ../../rst/user_guide/windows_winrm.rst:867 +#: ../../rst/user_guide/windows_usage.rst:490 +#: ../../rst/user_guide/windows_winrm.rst:889 msgid "Limitations" msgstr "制é™äº‹é …" -#: ../../rst/user_guide/windows_usage.rst:487 +#: ../../rst/user_guide/windows_usage.rst:491 msgid "Some things you cannot do with Ansible and Windows are:" msgstr "ã“ã“ã§ã¯ã€Ansible ãŠã‚ˆã³ Windows ã§ã§ããªã„ã“ã¨ã‚’説明ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_usage.rst:489 +#: ../../rst/user_guide/windows_usage.rst:493 msgid "Upgrade PowerShell" msgstr "PowerShell ã®ã‚¢ãƒƒãƒ—グレード" -#: ../../rst/user_guide/windows_usage.rst:491 +#: ../../rst/user_guide/windows_usage.rst:495 msgid "Interact with the WinRM listeners" msgstr "WinRM リスナーã¨ã®å¯¾è©±" -#: ../../rst/user_guide/windows_usage.rst:493 +#: ../../rst/user_guide/windows_usage.rst:497 msgid "Because WinRM is reliant on the services being online and running during normal operations, you cannot upgrade PowerShell or interact with WinRM listeners with Ansible. Both of these actions will cause the connection to fail. This can technically be avoided by using ``async`` or a scheduled task, but those methods are fragile if the process it runs breaks the underlying connection Ansible uses, and are best left to the bootstrapping process or before an image is created." msgstr "WinRM ã¯ã€é€šå¸¸ã®é‹ç”¨æ™‚ã«ã‚µãƒ¼ãƒ“スãŒã‚ªãƒ³ãƒ©ã‚¤ãƒ³ã§ç¨¼åƒã—ã¦ã„ã‚‹ã“ã¨ã«ä¾å˜ã—ã¦ã„ã‚‹ãŸã‚ã€PowerShell をアップグレードã—ãŸã‚Šã€Ansible 㧠WinRM リスナーã¨å¯¾è©±ã—ãŸã‚Šã™ã‚‹ã“ã¨ã¯ã§ãã¾ã›ã‚“。ã“れらã®ã‚¢ã‚¯ã‚·ãƒ§ãƒ³ã¯ã„ãšã‚Œã‚‚ã€æŽ¥ç¶šã®å¤±æ•—を引ãèµ·ã“ã—ã¾ã™ã€‚ã“ã‚Œã¯ã€æŠ€è¡“çš„ã«ã¯ ``async`` やスケジュールã•ã‚ŒãŸã‚¿ã‚¹ã‚¯ã‚’使用ã™ã‚‹ã“ã¨ã§å›žé¿ã§ãã¾ã™ãŒã€ã“れらã®æ–¹æ³•ã¯ã€å®Ÿè¡Œã™ã‚‹ãƒ—ãƒã‚»ã‚¹ã«ã‚ˆã£ã¦ Ansible ãŒä½¿ç”¨ã™ã‚‹åŸºç¤Žçš„ãªæŽ¥ç¶šãŒå£Šã‚Œã‚‹ã¨è„†å¼±ã«ãªã‚‹ãŸã‚ã€ãƒ–ートストラッププãƒã‚»ã‚¹ã‚„イメージãŒä½œæˆã•ã‚Œã‚‹å‰ã«ä»»ã›ã‚‹ã®ãŒæœ€é©ã§ã™ã€‚" -#: ../../rst/user_guide/windows_usage.rst:497 +#: ../../rst/user_guide/windows_usage.rst:501 msgid "Developing Windows Modules" msgstr "Windows モジュールã®é–‹ç™º" -#: ../../rst/user_guide/windows_usage.rst:498 +#: ../../rst/user_guide/windows_usage.rst:502 msgid "Because Ansible modules for Windows are written in PowerShell, the development guides for Windows modules differ substantially from those for standard standard modules. Please see :ref:`developing_modules_general_windows` for more information." msgstr "Windows 用㮠Ansible モジュール㯠PowerShell ã§æ›¸ã‹ã‚Œã¦ã„ã‚‹ãŸã‚ã€Windows モジュールã®é–‹ç™ºã‚¬ã‚¤ãƒ‰ã¯æ¨™æº–è¦æ ¼ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã®é–‹ç™ºã‚¬ã‚¤ãƒ‰ã¨ã¯å¤§ããç•°ãªã‚Šã¾ã™ã€‚詳細ã¯ã€ã€Œ:ref:`developing_modules_general_windows`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" @@ -13556,22 +13563,22 @@ msgid "No" msgstr "ä¸å¯" #: ../../rst/user_guide/windows_winrm.rst:51 -#: ../../rst/user_guide/windows_winrm.rst:82 +#: ../../rst/user_guide/windows_winrm.rst:84 msgid "Certificate" msgstr "証明書" #: ../../rst/user_guide/windows_winrm.rst:53 -#: ../../rst/user_guide/windows_winrm.rst:268 +#: ../../rst/user_guide/windows_winrm.rst:274 msgid "Kerberos" msgstr "Kerberos" #: ../../rst/user_guide/windows_winrm.rst:55 -#: ../../rst/user_guide/windows_winrm.rst:241 +#: ../../rst/user_guide/windows_winrm.rst:247 msgid "NTLM" msgstr "NTLM" #: ../../rst/user_guide/windows_winrm.rst:57 -#: ../../rst/user_guide/windows_winrm.rst:456 +#: ../../rst/user_guide/windows_winrm.rst:466 msgid "CredSSP" msgstr "CredSSP" @@ -13584,570 +13591,576 @@ msgid "The following example shows host vars configured for basic authentication msgstr "以下ã®ä¾‹ã¯ã€åŸºæœ¬èªè¨¼ã«è¨å®šã•ã‚Œã¦ã„るホスト変数を示ã—ã¦ã„ã¾ã™ã€‚" #: ../../rst/user_guide/windows_winrm.rst:76 -msgid "Basic authentication is not enabled by default on a Windows host but can be enabled by running the following in PowerShell::" +msgid "Basic authentication is not enabled by default on a Windows host but can be enabled by running the following in PowerShell:" msgstr "Basic èªè¨¼ã¯ã€Windows ホストã§ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã¯æœ‰åŠ¹ã«ãªã£ã¦ã„ã¾ã›ã‚“ãŒã€PowerShell ã§ä»¥ä¸‹ã‚’実行ã™ã‚‹ã“ã¨ã§æœ‰åŠ¹ã«ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:83 +#: ../../rst/user_guide/windows_winrm.rst:85 msgid "Certificate authentication uses certificates as keys similar to SSH key pairs, but the file format and key generation process is different." msgstr "証明書èªè¨¼ã¯ã€SSH ã‚ーペアã«ä¼¼ãŸéµã¨ã—ã¦è¨¼æ˜Žæ›¸ã‚’使用ã—ã¾ã™ãŒã€ãƒ•ã‚¡ã‚¤ãƒ«å½¢å¼ã¨éµã®ç”Ÿæˆãƒ—ãƒã‚»ã‚¹ã¯ç•°ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:86 +#: ../../rst/user_guide/windows_winrm.rst:88 msgid "The following example shows host vars configured for certificate authentication:" msgstr "以下ã®ä¾‹ã§ã¯ã€è¨¼æ˜Žæ›¸èªè¨¼ã«è¨å®šã•ã‚Œã¦ã„るホスト変数を示ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:95 -msgid "Certificate authentication is not enabled by default on a Windows host but can be enabled by running the following in PowerShell::" +#: ../../rst/user_guide/windows_winrm.rst:97 +msgid "Certificate authentication is not enabled by default on a Windows host but can be enabled by running the following in PowerShell:" msgstr "証明書èªè¨¼ã¯ã€Windows ホストã§ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã¯æœ‰åŠ¹ã«ãªã£ã¦ã„ã¾ã›ã‚“ãŒã€PowerShell ã§ä»¥ä¸‹ã‚’実行ã™ã‚‹ã“ã¨ã§æœ‰åŠ¹ã«ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:100 +#: ../../rst/user_guide/windows_winrm.rst:104 msgid "Encrypted private keys cannot be used as the urllib3 library that is used by Ansible for WinRM does not support this functionality." msgstr "WinRM å‘ã‘ã« Ansible ãŒä½¿ç”¨ã™ã‚‹ urllib3 ライブラリーãŒã“ã®æ©Ÿèƒ½ã‚’サãƒãƒ¼ãƒˆã—ã¦ã„ãªã„ãŸã‚ã€æš—å·åŒ–ã•ã‚ŒãŸç§˜å¯†éµã¯ä½¿ç”¨ã§ãã¾ã›ã‚“。" -#: ../../rst/user_guide/windows_winrm.rst:104 +#: ../../rst/user_guide/windows_winrm.rst:108 msgid "Generate a Certificate" msgstr "証明書ã®ç”Ÿæˆ" -#: ../../rst/user_guide/windows_winrm.rst:105 +#: ../../rst/user_guide/windows_winrm.rst:109 msgid "A certificate must be generated before it can be mapped to a local user. This can be done using one of the following methods:" msgstr "証明書をãƒãƒ¼ã‚«ãƒ«ãƒ¦ãƒ¼ã‚¶ãƒ¼ã«ãƒžãƒƒãƒ”ングã™ã‚‹å‰ã«ã€è¨¼æ˜Žæ›¸ã‚’生æˆã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€ä»¥ä¸‹ã®ã„ãšã‚Œã‹ã®æ–¹æ³•ã§è¡Œã†ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:108 +#: ../../rst/user_guide/windows_winrm.rst:112 msgid "OpenSSL" msgstr "OpenSSL" -#: ../../rst/user_guide/windows_winrm.rst:109 +#: ../../rst/user_guide/windows_winrm.rst:113 msgid "PowerShell, using the ``New-SelfSignedCertificate`` cmdlet" msgstr "``New-SelfSignedCertificate`` コマンドレットを使用ã—㟠PowerShell" -#: ../../rst/user_guide/windows_winrm.rst:110 +#: ../../rst/user_guide/windows_winrm.rst:114 msgid "Active Directory Certificate Services" msgstr "Active Directory 証明書サービス" -#: ../../rst/user_guide/windows_winrm.rst:112 +#: ../../rst/user_guide/windows_winrm.rst:116 msgid "Active Directory Certificate Services is beyond of scope in this documentation but may be the best option to use when running in a domain environment. For more information, see the `Active Directory Certificate Services documentation <https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732625(v=ws.11)>`_." msgstr "Active Directory Certificate Services ã¯ã€ã“ã®ãƒ‰ã‚ュメントã§ã¯å¯¾è±¡å¤–ã«ãªã‚Šã¾ã™ãŒã€ãƒ‰ãƒ¡ã‚¤ãƒ³ç’°å¢ƒã§å®Ÿè¡Œã™ã‚‹å ´åˆã«ã¯ã€æœ€é©ãªã‚ªãƒ—ションã«ãªã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“。詳細ã¯ã€`Active Directory Certificate Services ã®ãƒ‰ã‚ュメント <https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732625(v=ws.11)>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_winrm.rst:116 +#: ../../rst/user_guide/windows_winrm.rst:120 msgid "Using the PowerShell cmdlet ``New-SelfSignedCertificate`` to generate a certificate for authentication only works when being generated from a Windows 10 or Windows Server 2012 R2 host or later. OpenSSL is still required to extract the private key from the PFX certificate to a PEM file for Ansible to use." msgstr "PowerShell コマンドレット (``New-SelfSignedCertificate``) を使用ã—ã¦èªè¨¼ç”¨ã®è¨¼æ˜Žæ›¸ã‚’生æˆã™ã‚‹å ´åˆã¯ã€Windows 10 ã¾ãŸã¯ Windows Server 2012 R2 ホスト以é™ã‹ã‚‰ç”Ÿæˆã•ã‚ŒãŸå ´åˆã«ã®ã¿æ©Ÿèƒ½ã—ã¾ã™ã€‚PFX 証明書ã‹ã‚‰ Ansible ãŒä½¿ç”¨ã™ã‚‹ PEM ファイルã«ç§˜å¯†éµã‚’抽出ã™ã‚‹ã«ã¯ã€OpenSSL ãŒå¼•ã続ãå¿…è¦ã¨ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:122 +#: ../../rst/user_guide/windows_winrm.rst:126 msgid "To generate a certificate with ``OpenSSL``:" msgstr "``OpenSSL`` ã§è¨¼æ˜Žæ›¸ã‚’生æˆã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:142 +#: ../../rst/user_guide/windows_winrm.rst:146 msgid "To generate a certificate with ``New-SelfSignedCertificate``:" msgstr "``New-SelfSignedCertificate`` ã§è¨¼æ˜Žæ›¸ã‚’生æˆã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:170 +#: ../../rst/user_guide/windows_winrm.rst:174 msgid "To convert the PFX file to a private key that pywinrm can use, run the following command with OpenSSL ``openssl pkcs12 -in cert.pfx -nocerts -nodes -out cert_key.pem -passin pass: -passout pass:``" msgstr "PFX ファイルを pywinrm ãŒä½¿ç”¨ã§ãる秘密éµã«å¤‰æ›ã™ã‚‹ã«ã¯ã€OpenSSL 㧠``openssl pkcs12 -in cert.pfx -nocerts -nodes -out cert_key.pem -passin pass: -passout pass:`` コマンドを実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:175 +#: ../../rst/user_guide/windows_winrm.rst:179 msgid "Import a Certificate to the Certificate Store" msgstr "証明書ストアã¸ã®è¨¼æ˜Žæ›¸ã®ã‚¤ãƒ³ãƒãƒ¼ãƒˆ" -#: ../../rst/user_guide/windows_winrm.rst:176 +#: ../../rst/user_guide/windows_winrm.rst:180 msgid "Once a certificate has been generated, the issuing certificate needs to be imported into the ``Trusted Root Certificate Authorities`` of the ``LocalMachine`` store, and the client certificate public key must be present in the ``Trusted People`` folder of the ``LocalMachine`` store. For this example, both the issuing certificate and public key are the same." msgstr "証明書ãŒç”Ÿæˆã•ã‚ŒãŸã‚‰ã€ç™ºè¡Œã—ãŸè¨¼æ˜Žæ›¸ã‚’ ``LocalMachine`` ストア㮠``Trusted Root Certificate Authorities`` ã«ã‚¤ãƒ³ãƒãƒ¼ãƒˆã—ã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆè¨¼æ˜Žæ›¸ã®å…¬é–‹éµã‚’ ``LocalMachine`` ストア㮠``Trusted People`` ディレクトリーã«å˜åœ¨ã•ã›ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®ä¾‹ã§ã¯ã€ç™ºè¡Œã—ãŸè¨¼æ˜Žæ›¸ã¨å…¬é–‹éµã®ä¸¡æ–¹ãŒåŒã˜ã‚‚ã®ã§ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:182 +#: ../../rst/user_guide/windows_winrm.rst:186 msgid "Following example shows how to import the issuing certificate:" msgstr "以下ã®ä¾‹ã§ã¯ã€ç™ºè¡Œã—ãŸè¨¼æ˜Žæ›¸ã‚’インãƒãƒ¼ãƒˆã™ã‚‹æ–¹æ³•ã‚’示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:197 +#: ../../rst/user_guide/windows_winrm.rst:201 msgid "If using ADCS to generate the certificate, then the issuing certificate will already be imported and this step can be skipped." msgstr "ADCS を使用ã—ã¦è¨¼æ˜Žæ›¸ã‚’生æˆã™ã‚‹å ´åˆã¯ã€ç™ºè¡Œã™ã‚‹è¨¼æ˜Žæ›¸ãŒã™ã§ã«ã‚¤ãƒ³ãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã‚‹ãŸã‚ã€ã“ã®æ‰‹é †ã¯çœç•¥ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:200 +#: ../../rst/user_guide/windows_winrm.rst:204 msgid "The code to import the client certificate public key is:" msgstr "クライアント証明書ã®å…¬é–‹éµã‚’インãƒãƒ¼ãƒˆã™ã‚‹ã‚³ãƒ¼ãƒ‰ã¯ä»¥ä¸‹ã®ã¨ãŠã‚Šã§ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:216 +#: ../../rst/user_guide/windows_winrm.rst:220 msgid "Mapping a Certificate to an Account" msgstr "証明書ã®ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã¸ã®ãƒžãƒƒãƒ”ング" -#: ../../rst/user_guide/windows_winrm.rst:217 -msgid "Once the certificate has been imported, map it to the local user account::" +#: ../../rst/user_guide/windows_winrm.rst:221 +msgid "Once the certificate has been imported, map it to the local user account:" msgstr "証明書をインãƒãƒ¼ãƒˆã—ãŸã‚‰ã€ã“れをãƒãƒ¼ã‚«ãƒ«ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã«ãƒžãƒƒãƒ”ングã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:236 +#: ../../rst/user_guide/windows_winrm.rst:242 msgid "Once this is complete, the hostvar ``ansible_winrm_cert_pem`` should be set to the path of the public key and the ``ansible_winrm_cert_key_pem`` variable should be set to the path of the private key." msgstr "ã“ã‚ŒãŒå®Œäº†ã—ãŸã‚‰ã€ãƒ›ã‚¹ãƒˆå¤‰æ•° ``ansible_winrm_cert_pem`` ã«å…¬é–‹éµã®ãƒ‘スをè¨å®šã—ã€å¤‰æ•°``ansible_winrm_cert_key_pem`` ã«ç§˜å¯†éµã®ãƒ‘スをè¨å®šã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_winrm.rst:242 +#: ../../rst/user_guide/windows_winrm.rst:248 msgid "NTLM is an older authentication mechanism used by Microsoft that can support both local and domain accounts. NTLM is enabled by default on the WinRM service, so no setup is required before using it." msgstr "NTLM ã¯ã€Microsoft ãŒä½¿ç”¨ã—ã¦ã„ã‚‹å¤ã„èªè¨¼ãƒ¡ã‚«ãƒ‹ã‚ºãƒ ã§ã€ãƒãƒ¼ã‚«ãƒ«ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã¨ãƒ‰ãƒ¡ã‚¤ãƒ³ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã®ä¸¡æ–¹ã‚’サãƒãƒ¼ãƒˆã—ã¦ã„ã¾ã™ã€‚NTLM ã¯ã€WinRM サービスã§ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§æœ‰åŠ¹ã«ãªã£ã¦ã„ã‚‹ãŸã‚ã€ä½¿ç”¨ã™ã‚‹å‰ã«è¨å®šã™ã‚‹å¿…è¦ã¯ã‚ã‚Šã¾ã›ã‚“。" -#: ../../rst/user_guide/windows_winrm.rst:246 +#: ../../rst/user_guide/windows_winrm.rst:252 msgid "NTLM is the easiest authentication protocol to use and is more secure than ``Basic`` authentication. If running in a domain environment, ``Kerberos`` should be used instead of NTLM." msgstr "NTLM ã¯æœ€ã‚‚ç°¡å˜ã«ä½¿ç”¨ã§ãã‚‹èªè¨¼ãƒ—ãƒãƒˆã‚³ãƒ«ã§ã‚ã‚Šã€``Basic`` èªè¨¼ã‚ˆã‚Šã‚‚安全ã§ã™ã€‚ドメイン環境ã§ç¨¼åƒã—ã¦ã„ã‚‹å ´åˆã¯ã€NTLM ã®ä»£ã‚ã‚Šã« ``Kerberos`` を使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:250 +#: ../../rst/user_guide/windows_winrm.rst:256 msgid "Kerberos has several advantages over using NTLM:" msgstr "Kerberos 㯠NTLM ã®ä½¿ç”¨ã¨æ¯”較ã—ã¦ã€ä»¥ä¸‹ã®ã‚ˆã†ãªåˆ©ç‚¹ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:252 +#: ../../rst/user_guide/windows_winrm.rst:258 msgid "NTLM is an older protocol and does not support newer encryption protocols." msgstr "NTLM ã¯å¤ã„プãƒãƒˆã‚³ãƒ«ã§ã‚ã‚Šã€æ–°ã—ã„æš—å·åŒ–プãƒãƒˆã‚³ãƒ«ã‚’サãƒãƒ¼ãƒˆã—ã¾ã›ã‚“。" -#: ../../rst/user_guide/windows_winrm.rst:254 +#: ../../rst/user_guide/windows_winrm.rst:260 msgid "NTLM is slower to authenticate because it requires more round trips to the host in the authentication stage." msgstr "NTLM ã¯ã€èªè¨¼ã®æ®µéšŽã§ãƒ›ã‚¹ãƒˆã¸ã®ãƒ©ã‚¦ãƒ³ãƒ‰ãƒˆãƒªãƒƒãƒ—ãŒå¤šããªã‚‹ãŸã‚ã€èªè¨¼ã«æ™‚é–“ãŒã‹ã‹ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:256 +#: ../../rst/user_guide/windows_winrm.rst:262 msgid "Unlike Kerberos, NTLM does not allow credential delegation." msgstr "Kerberos ã¨ã¯ç•°ãªã‚Šã€NTLM ã¯èªè¨¼æƒ…å ±ã®å§”è²ã‚’許å¯ã—ã¦ã„ã¾ã›ã‚“。" -#: ../../rst/user_guide/windows_winrm.rst:258 +#: ../../rst/user_guide/windows_winrm.rst:264 msgid "This example shows host variables configured to use NTLM authentication:" msgstr "以下ã®ä¾‹ã§ã¯ã€NTLM èªè¨¼ã‚’使用ã™ã‚‹ã‚ˆã†ã«è¨å®šã•ã‚Œã¦ã„るホスト変数を示ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:269 +#: ../../rst/user_guide/windows_winrm.rst:275 msgid "Kerberos is the recommended authentication option to use when running in a domain environment. Kerberos supports features like credential delegation and message encryption over HTTP and is one of the more secure options that is available through WinRM." msgstr "Kerberos ã¯ã€ãƒ‰ãƒ¡ã‚¤ãƒ³ç’°å¢ƒã§å®Ÿè¡Œã™ã‚‹å ´åˆã«ä½¿ç”¨ã™ã‚‹æŽ¨å¥¨ã®èªè¨¼ã‚ªãƒ—ションã§ã™ã€‚Kerberos ã¯ã€èªè¨¼æƒ…å ±ã®å§”è²ã‚„ HTTP ã§ã®ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸æš—å·åŒ–ãªã©ã®æ©Ÿèƒ½ã‚’サãƒãƒ¼ãƒˆã—ã¦ãŠã‚Šã€WinRM ã§åˆ©ç”¨ã§ãるより安全ãªã‚ªãƒ—ション㮠1 ã¤ã§ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:274 +#: ../../rst/user_guide/windows_winrm.rst:280 msgid "Kerberos requires some additional setup work on the Ansible host before it can be used properly." msgstr "Kerberos ã‚’æ£ã—ã使用ã™ã‚‹ã«ã¯ã€Ansible ホスト上ã§ã„ãã¤ã‹ã®è¿½åŠ è¨å®šä½œæ¥ãŒå¿…è¦ã§ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:277 +#: ../../rst/user_guide/windows_winrm.rst:283 msgid "The following example shows host vars configured for Kerberos authentication:" msgstr "以下ã®ä¾‹ã¯ã€Kerberos èªè¨¼ã«è¨å®šã•ã‚ŒãŸãƒ›ã‚¹ãƒˆå¤‰æ•°ã‚’示ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:287 +#: ../../rst/user_guide/windows_winrm.rst:293 msgid "As of Ansible version 2.3, the Kerberos ticket will be created based on ``ansible_user`` and ``ansible_password``. If running on an older version of Ansible or when ``ansible_winrm_kinit_mode`` is ``manual``, a Kerberos ticket must already be obtained. See below for more details." msgstr "Ansible ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.3 以é™ã§ã¯ã€``ansible_user`` 㨠``ansible_password`` ã«åŸºã¥ã„㦠Kerberos ãƒã‚±ãƒƒãƒˆãŒä½œæˆã•ã‚Œã¾ã™ã€‚å¤ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Ansible ã§å®Ÿè¡Œã—ã¦ã„ã‚‹å ´åˆã‚„ã€``ansible_winrm_kinit_mode`` ㌠``manual`` ã®å ´åˆã¯ã€ã™ã§ã« Kerberos ãƒã‚±ãƒƒãƒˆã‚’å–å¾—ã—ã¦ã„ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚詳細ã¯ä»¥ä¸‹ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_winrm.rst:292 -msgid "There are some extra host variables that can be set::" +#: ../../rst/user_guide/windows_winrm.rst:298 +msgid "There are some extra host variables that can be set:" msgstr "è¨å®šå¯èƒ½ãªè¿½åŠ ã®ãƒ›ã‚¹ãƒˆå¤‰æ•°ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:301 +#: ../../rst/user_guide/windows_winrm.rst:309 msgid "Installing the Kerberos Library" msgstr "Kerberos ライブラリーã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/user_guide/windows_winrm.rst:302 +#: ../../rst/user_guide/windows_winrm.rst:310 msgid "Some system dependencies that must be installed prior to using Kerberos. The script below lists the dependencies based on the distro:" msgstr "Kerberos を使用ã™ã‚‹å‰ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã™ã‚‹å¿…è¦ãŒã‚るシステムä¾å˜é–¢ä¿‚ãŒã‚ã‚Šã¾ã™ã€‚以下ã®ã‚¹ã‚¯ãƒªãƒ—トã¯ã€ãƒ‡ã‚£ã‚¹ãƒˆãƒªãƒ“ューションã«åŸºã¥ãä¾å˜é–¢ä¿‚を一覧表示ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:328 +#: ../../rst/user_guide/windows_winrm.rst:336 msgid "Once the dependencies have been installed, the ``python-kerberos`` wrapper can be install using ``pip``:" msgstr "ä¾å˜é–¢ä¿‚ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚ŒãŸã‚‰ã€``pip`` を使用ã—㦠``python-kerberos`` ラッパーをインストールã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:337 +#: ../../rst/user_guide/windows_winrm.rst:345 msgid "While Ansible has supported Kerberos auth through ``pywinrm`` for some time, optional features or more secure options may only be available in newer versions of the ``pywinrm`` and/or ``pykerberos`` libraries. It is recommended you upgrade each version to the latest available to resolve any warnings or errors. This can be done through tools like ``pip`` or a system package manager like ``dnf``, ``yum``, ``apt`` but the package names and versions available may differ between tools." msgstr "Ansible ã¯ã“ã‚Œã¾ã§ã€``pywinrm`` を通ã˜ã¦ Kerberos èªè¨¼ã‚’サãƒãƒ¼ãƒˆã—ã¦ãã¾ã—ãŸãŒã€ã‚ªãƒ—ション機能やより安全ãªã‚ªãƒ—ションã¯ã€``pywinrm`` ライブラリーã¾ãŸã¯ ``pykerberos`` ライブラリーã®æ–°ã—ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã®ã¿åˆ©ç”¨ã§ãã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚è¦å‘Šã‚„エラーãŒç™ºç”Ÿã—ãŸå ´åˆã¯ã€å„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’最新ã®ã‚‚ã®ã«ã‚¢ãƒƒãƒ—グレードã™ã‚‹ã“ã¨ãŒæŽ¨å¥¨ã•ã‚Œã¾ã™ã€‚ã“ã®ä½œæ¥ã¯ã€``pip`` ã®ã‚ˆã†ãªãƒ„ールやã€``dnf``ã€``yum``ã€``apt`` ã®ã‚ˆã†ãªã‚·ã‚¹ãƒ†ãƒ パッケージマãƒãƒ¼ã‚¸ãƒ£ãƒ¼ã§è¡Œã†ã“ã¨ãŒã§ãã¾ã™ãŒã€ãƒ‘ッケージåや利用å¯èƒ½ãªãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯ãƒ„ールã«ã‚ˆã£ã¦ç•°ãªã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:347 +#: ../../rst/user_guide/windows_winrm.rst:355 msgid "Configuring Host Kerberos" msgstr "ホスト Kerberos ã®è¨å®š" -#: ../../rst/user_guide/windows_winrm.rst:348 +#: ../../rst/user_guide/windows_winrm.rst:356 msgid "Once the dependencies have been installed, Kerberos needs to be configured so that it can communicate with a domain. This configuration is done through the ``/etc/krb5.conf`` file, which is installed with the packages in the script above." msgstr "ä¾å˜é–¢ä¿‚ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚ŒãŸã‚‰ã€Kerberos ãŒãƒ‰ãƒ¡ã‚¤ãƒ³ã¨é€šä¿¡ã§ãるよã†ã«è¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®è¨å®šã¯ã€ä¸Šã®ã‚¹ã‚¯ãƒªãƒ—トã§ãƒ‘ッケージã¨ä¸€ç·’ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚ŒãŸ ``/etc/krb5.conf`` ファイルを通ã˜ã¦è¡Œã‚ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:352 +#: ../../rst/user_guide/windows_winrm.rst:360 msgid "To configure Kerberos, in the section that starts with:" msgstr "Kerberos ã‚’è¨å®šã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã§å§‹ã¾ã‚‹ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§è¡Œã„ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:358 +#: ../../rst/user_guide/windows_winrm.rst:366 msgid "Add the full domain name and the fully qualified domain names of the primary and secondary Active Directory domain controllers. It should look something like this:" msgstr "プライマリーãŠã‚ˆã³ã‚»ã‚«ãƒ³ãƒ€ãƒªãƒ¼ã® Active Directory ドメインコントãƒãƒ¼ãƒ©ãƒ¼ã®å®Œå…¨ãƒ‰ãƒ¡ã‚¤ãƒ³åãŠã‚ˆã³å®Œå…¨ä¿®é£¾ãƒ‰ãƒ¡ã‚¤ãƒ³åã‚’è¿½åŠ ã—ã¾ã™ã€‚以下ã®ã‚ˆã†ã«ãªã‚‹ã¯ãšã§ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:370 +#: ../../rst/user_guide/windows_winrm.rst:378 msgid "In the section that starts with:" msgstr "以下ã§å§‹ã¾ã‚‹ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã§ã€" -#: ../../rst/user_guide/windows_winrm.rst:376 +#: ../../rst/user_guide/windows_winrm.rst:384 msgid "Add a line like the following for each domain that Ansible needs access for:" msgstr "Ansible ãŒã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹å¿…è¦ã®ã‚ã‚‹å„ドメインã«ä»¥ä¸‹ã®ã‚ˆã†ãªè¡Œã‚’è¿½åŠ ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:383 +#: ../../rst/user_guide/windows_winrm.rst:391 msgid "You can configure other settings in this file such as the default domain. See `krb5.conf <https://web.mit.edu/kerberos/krb5-1.12/doc/admin/conf_files/krb5_conf.html>`_ for more details." msgstr "ã“ã®ãƒ•ã‚¡ã‚¤ãƒ«ã§ã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã®ãƒ‰ãƒ¡ã‚¤ãƒ³ãªã©ã€ãã®ä»–ã®è¨å®šã‚’è¡Œã†ã“ã¨ãŒã§ãã¾ã™ã€‚詳細㯠`krb5.conf <https://web.mit.edu/kerberos/krb5-1.12/doc/admin/conf_files/krb5_conf.html>`_ ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_winrm.rst:388 +#: ../../rst/user_guide/windows_winrm.rst:396 msgid "Automatic Kerberos Ticket Management" msgstr "Kerberos ãƒã‚±ãƒƒãƒˆã®è‡ªå‹•ç®¡ç†" -#: ../../rst/user_guide/windows_winrm.rst:389 +#: ../../rst/user_guide/windows_winrm.rst:397 msgid "Ansible version 2.3 and later defaults to automatically managing Kerberos tickets when both ``ansible_user`` and ``ansible_password`` are specified for a host. In this process, a new ticket is created in a temporary credential cache for each host. This is done before each task executes to minimize the chance of ticket expiration. The temporary credential caches are deleted after each task completes and will not interfere with the default credential cache." msgstr "Ansible ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 2.3 以é™ã§ã¯ã€ãƒ›ã‚¹ãƒˆã« ``ansible_user`` ãŠã‚ˆã³ ``ansible_password`` ã®ä¸¡æ–¹ãŒæŒ‡å®šã•ã‚ŒãŸå ´åˆã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ Kerberos ãƒã‚±ãƒƒãƒˆã‚’自動的ã«ç®¡ç†ã—ã¾ã™ã€‚ã“ã®ãƒ—ãƒã‚»ã‚¹ã§ã¯ã€å„ホストã®ä¸€æ™‚çš„ãªèªè¨¼æƒ…å ±ã‚ャッシュã«æ–°ã—ã„ãƒã‚±ãƒƒãƒˆãŒä½œæˆã•ã‚Œã¾ã™ã€‚ã“ã‚Œã¯ã€ãƒã‚±ãƒƒãƒˆãŒå¤±åŠ¹ã™ã‚‹å¯èƒ½æ€§ã‚’最å°é™ã«ã™ã‚‹ãŸã‚ã«ã€å„タスクãŒå®Ÿè¡Œã•ã‚Œã‚‹å‰ã«è¡Œã‚ã‚Œã¾ã™ã€‚一時的ãªèªè¨¼æƒ…å ±ã‚ャッシュã¯ã€å„タスクãŒå®Œäº†ã™ã‚‹ã¨å‰Šé™¤ã•ã‚Œã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã®èªè¨¼æƒ…å ±ã‚ャッシュã«å¹²æ¸‰ã™ã‚‹ã“ã¨ã¯ã‚ã‚Šã¾ã›ã‚“。" -#: ../../rst/user_guide/windows_winrm.rst:396 +#: ../../rst/user_guide/windows_winrm.rst:404 msgid "To disable automatic ticket management, set ``ansible_winrm_kinit_mode=manual`` via the inventory." msgstr "ãƒã‚±ãƒƒãƒˆã®è‡ªå‹•ç®¡ç†ã‚’無効ã«ã™ã‚‹ã«ã¯ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã‹ã‚‰ ``ansible_winrm_kinit_mode=manual`` ã‚’è¨å®šã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_winrm.rst:399 +#: ../../rst/user_guide/windows_winrm.rst:407 msgid "Automatic ticket management requires a standard ``kinit`` binary on the control host system path. To specify a different location or binary name, set the ``ansible_winrm_kinit_cmd`` hostvar to the fully qualified path to a MIT krbv5 ``kinit``-compatible binary." msgstr "自動ãƒã‚±ãƒƒãƒˆç®¡ç†ã«ã¯ã€åˆ¶å¾¡ãƒ›ã‚¹ãƒˆã‚·ã‚¹ãƒ†ãƒ ã®ãƒ‘スã«æ¨™æº–ã® ``kinit`` ãƒã‚¤ãƒŠãƒªãƒ¼ãŒå¿…è¦ã§ã™ã€‚別ã®å ´æ‰€ã‚„ãƒã‚¤ãƒŠãƒªãƒ¼åを指定ã™ã‚‹ã«ã¯ã€ãƒ›ã‚¹ãƒˆå¤‰æ•° ``ansible_winrm_kinit_cmd`` ã« MIT krbv5 ``kinit`` 互æ›ãƒã‚¤ãƒŠãƒªãƒ¼ã¸ã®å®Œå…¨ä¿®é£¾ãƒ‘スをè¨å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:405 +#: ../../rst/user_guide/windows_winrm.rst:413 msgid "Manual Kerberos Ticket Management" msgstr "Kerberos ãƒã‚±ãƒƒãƒˆã®æ‰‹å‹•ç®¡ç†" -#: ../../rst/user_guide/windows_winrm.rst:406 +#: ../../rst/user_guide/windows_winrm.rst:414 msgid "To manually manage Kerberos tickets, the ``kinit`` binary is used. To obtain a new ticket the following command is used:" msgstr "Kerberos ãƒã‚±ãƒƒãƒˆã‚’手動ã§ç®¡ç†ã™ã‚‹ã«ã¯ã€``kinit`` ãƒã‚¤ãƒŠãƒªãƒ¼ã‚’使用ã—ã¾ã™ã€‚æ–°ã—ã„ãƒã‚±ãƒƒãƒˆã‚’å–å¾—ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:413 +#: ../../rst/user_guide/windows_winrm.rst:421 msgid "The domain must match the configured Kerberos realm exactly, and must be in upper case." msgstr "ドメインã¯è¨å®šã•ã‚ŒãŸ Kerberos レルムã«å®Œå…¨ã«ä¸€è‡´ã—ã€å¤§æ–‡å—ã§ã‚ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:415 +#: ../../rst/user_guide/windows_winrm.rst:423 msgid "To see what tickets (if any) have been acquired, use the following command:" msgstr "å–å¾—ã—ãŸãƒã‚±ãƒƒãƒˆ (å˜åœ¨ã™ã‚‹å ´åˆ) を確èªã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:421 +#: ../../rst/user_guide/windows_winrm.rst:429 msgid "To destroy all the tickets that have been acquired, use the following command:" msgstr "å–å¾—ã—ãŸã™ã¹ã¦ã®ãƒã‚±ãƒƒãƒˆã‚’ç ´æ£„ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:428 +#: ../../rst/user_guide/windows_winrm.rst:436 msgid "Troubleshooting Kerberos" msgstr "Kerberos ã®ãƒˆãƒ©ãƒ–ルシューティング" -#: ../../rst/user_guide/windows_winrm.rst:429 +#: ../../rst/user_guide/windows_winrm.rst:437 msgid "Kerberos is reliant on a properly-configured environment to work. To troubleshoot Kerberos issues, ensure that:" msgstr "Kerberos ã¯ã€é©åˆ‡ã«æ§‹æˆã•ã‚ŒãŸç’°å¢ƒã§ãªã‘ã‚Œã°å‹•ä½œã—ã¾ã›ã‚“。Kerberos ã®å•é¡Œã‚’トラブルシューティングã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’確èªã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_winrm.rst:432 +#: ../../rst/user_guide/windows_winrm.rst:440 msgid "The hostname set for the Windows host is the FQDN and not an IP address." msgstr "Windows ホストã®ãƒ›ã‚¹ãƒˆåã«ã¯ã€IP アドレスã§ã¯ãªã FQDN ã§ã‚ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:434 +#: ../../rst/user_guide/windows_winrm.rst:442 msgid "The forward and reverse DNS lookups are working properly in the domain. To test this, ping the windows host by name and then use the ip address returned with ``nslookup``. The same name should be returned when using ``nslookup`` on the IP address." msgstr "ã“ã®ãƒ‰ãƒ¡ã‚¤ãƒ³ã§ã¯ã€DNS ã®æ£å¼•ãã¨é€†å¼•ããŒæ£å¸¸ã«å‹•ä½œã—ã¦ã„ã¾ã™ã€‚ã“れをテストã™ã‚‹ã«ã¯ã€Windows ホストã«åå‰ã§ ping を打ã¡ã€``nslookup`` ã§è¿”ã•ã‚ŒãŸ IP アドレスを使用ã—ã¾ã™ã€‚IP アドレス㫠``nslookup`` を使用ã™ã‚‹ã¨ã€åŒã˜åå‰ãŒè¿”ã•ã‚Œã‚‹ã¯ãšã§ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:439 +#: ../../rst/user_guide/windows_winrm.rst:447 msgid "The Ansible host's clock is synchronized with the domain controller. Kerberos is time sensitive, and a little clock drift can cause the ticket generation process to fail." msgstr "Ansible ホストã®æ™‚計ã¯ãƒ‰ãƒ¡ã‚¤ãƒ³ã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©ãƒ¼ã¨åŒæœŸã—ã¾ã™ã€‚Kerberos ã¯æ™‚é–“ã«æ•æ„Ÿã§ã€ã‚ãšã‹ãªæ™‚計ã®ãšã‚Œã«ã‚ˆã‚Šã€ãƒã‚±ãƒƒãƒˆç”Ÿæˆãƒ—ãƒã‚»ã‚¹ãŒå¤±æ•—ã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:443 -msgid "Ensure that the fully qualified domain name for the domain is configured in the ``krb5.conf`` file. To check this, run::" +#: ../../rst/user_guide/windows_winrm.rst:451 +msgid "Ensure that the fully qualified domain name for the domain is configured in the ``krb5.conf`` file. To check this, run:" msgstr "ドメインã®å®Œå…¨ä¿®é£¾ãƒ‰ãƒ¡ã‚¤ãƒ³åãŒã€``krb5.conf`` ファイルã«è¨å®šã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。ã“れを確èªã™ã‚‹ã«ã¯ã€æ¬¡ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:449 +#: ../../rst/user_guide/windows_winrm.rst:459 msgid "If the domain name returned by ``klist`` is different from the one requested, an alias is being used. The ``krb5.conf`` file needs to be updated so that the fully qualified domain name is used and not an alias." msgstr "``klist`` ã§è¿”ã•ã‚ŒãŸãƒ‰ãƒ¡ã‚¤ãƒ³åãŒè¦æ±‚ã•ã‚ŒãŸã‚‚ã®ã¨ç•°ãªã‚‹å ´åˆã¯ã€ã‚¨ã‚¤ãƒªã‚¢ã‚¹ãŒä½¿ç”¨ã•ã‚Œã¦ã„ã¾ã™ã€‚``krb5.conf`` ファイルを更新ã—ã¦ã€ã‚¨ã‚¤ãƒªã‚¢ã‚¹ã§ã¯ãªã完全修飾ドメインåを使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:453 +#: ../../rst/user_guide/windows_winrm.rst:463 msgid "If the default kerberos tooling has been replaced or modified (some IdM solutions may do this), this may cause issues when installing or upgrading the Python Kerberos library. As of the time of this writing, this library is called ``pykerberos`` and is known to work with both MIT and Heimdal Kerberos libraries. To resolve ``pykerberos`` installation issues, ensure the system dependencies for Kerberos have been met (see: `Installing the Kerberos Library`_), remove any custom Kerberos tooling paths from the PATH environment variable, and retry the installation of Python Kerberos library package." msgstr "デフォルト㮠kerberos ツールãŒç½®ãæ›ãˆã‚‰ã‚ŒãŸã‚Šå¤‰æ›´ã—ãŸã‚Šã—ãŸå ´åˆ (ã„ãã¤ã‹ã® IdM ソリューションã§ã¯ãã†ãªã£ã¦ã„ã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“)ã€Python Kerberos ライブラリーをインストールã—ãŸã‚Šã‚¢ãƒƒãƒ—グレードã—ãŸã‚Šã™ã‚‹éš›ã«å•é¡ŒãŒç™ºç”Ÿã™ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚本ガイドã®ä½œæˆæ™‚点ã§ã€ã“ã®ãƒ©ã‚¤ãƒ–ラリー㯠``pykerberos`` ã¨å‘¼ã°ã‚Œã€MIT 㨠Heimdal Kerberos ライブラリーã®ä¸¡æ–¹ã§å‹•ä½œã™ã‚‹ã“ã¨ãŒçŸ¥ã‚‰ã‚Œã¦ã„ã¾ã™ã€‚``pykerberos`` ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«å•é¡Œã‚’解決ã™ã‚‹ã«ã¯ã€Kerberos ã®ã‚·ã‚¹ãƒ†ãƒ ä¾å˜æ€§ãŒæº€ãŸã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚’確èªã— (å‚ç…§: `Installing the Kerberos Library`_)ã€PATH 環境変数ã‹ã‚‰ã‚«ã‚¹ã‚¿ãƒ ã® Kerberos ツールパスを削除ã—ã€Python Kerberos ライブラリーパッケージã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã‚’å†è©¦è¡Œã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_winrm.rst:457 +#: ../../rst/user_guide/windows_winrm.rst:467 msgid "CredSSP authentication is a newer authentication protocol that allows credential delegation. This is achieved by encrypting the username and password after authentication has succeeded and sending that to the server using the CredSSP protocol." msgstr "CredSSP èªè¨¼ã¯ã€èªè¨¼æƒ…å ±ã®å§”è²ã‚’å¯èƒ½ã«ã™ã‚‹æ–°ã—ã„èªè¨¼ãƒ—ãƒãƒˆã‚³ãƒ«ã«ãªã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€èªè¨¼ãŒæˆåŠŸã—ãŸå¾Œã®ãƒ¦ãƒ¼ã‚¶ãƒ¼åã¨ãƒ‘スワードを暗å·åŒ–ã—ã€ãれを CredSSP プãƒãƒˆã‚³ãƒ«ã‚’使用ã—ã¦ã‚µãƒ¼ãƒãƒ¼ã«é€ä¿¡ã™ã‚‹ã“ã¨ã§å®Ÿç¾ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:462 +#: ../../rst/user_guide/windows_winrm.rst:472 msgid "Because the username and password are sent to the server to be used for double hop authentication, ensure that the hosts that the Windows host communicates with are not compromised and are trusted." msgstr "ユーザーåã¨ãƒ‘スワードをサーãƒãƒ¼ã«é€ä¿¡ã—ã¦ãƒ€ãƒ–ルホップèªè¨¼ã«ä½¿ç”¨ã™ã‚‹ãŸã‚ã€Windows ホストãŒé€šä¿¡ã™ã‚‹ãƒ›ã‚¹ãƒˆãŒæ¼æ´©ã—ã¦ãŠã‚‰ãšã€ä¿¡é ¼ã§ãã‚‹ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_winrm.rst:466 +#: ../../rst/user_guide/windows_winrm.rst:476 msgid "CredSSP can be used for both local and domain accounts and also supports message encryption over HTTP." msgstr "CredSSP ã¯ã€ãƒãƒ¼ã‚«ãƒ«ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã¨ãƒ‰ãƒ¡ã‚¤ãƒ³ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã®ä¸¡æ–¹ã«ä½¿ç”¨ã§ãã€HTTPã§ã®ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸æš—å·åŒ–ã«ã‚‚対応ã—ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:469 +#: ../../rst/user_guide/windows_winrm.rst:479 msgid "To use CredSSP authentication, the host vars are configured like so:" msgstr "CredSSP èªè¨¼ã‚’使用ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãƒ›ã‚¹ãƒˆå¤‰æ•°ã‚’è¨å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:478 -msgid "There are some extra host variables that can be set as shown below::" +#: ../../rst/user_guide/windows_winrm.rst:488 +msgid "There are some extra host variables that can be set as shown below:" msgstr "以下ã®ã‚ˆã†ã«è¨å®šã§ãã‚‹è¿½åŠ ã®ãƒ›ã‚¹ãƒˆå¤‰æ•°ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:482 +#: ../../rst/user_guide/windows_winrm.rst:494 msgid "CredSSP authentication is not enabled by default on a Windows host, but can be enabled by running the following in PowerShell:" msgstr "CredSSP èªè¨¼ã¯ã€Windows ホストã§ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã¯æœ‰åŠ¹ã«ãªã£ã¦ã„ã¾ã›ã‚“ãŒã€PowerShell ã§ä»¥ä¸‹ã‚’実行ã™ã‚‹ã“ã¨ã§æœ‰åŠ¹ã«ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:490 +#: ../../rst/user_guide/windows_winrm.rst:502 msgid "Installing CredSSP Library" msgstr "CredSSP ライブラリーã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«" -#: ../../rst/user_guide/windows_winrm.rst:492 +#: ../../rst/user_guide/windows_winrm.rst:504 msgid "The ``requests-credssp`` wrapper can be installed using ``pip``:" msgstr "``requests-credssp`` ラッパーã¯ã€``pip`` を使用ã—ã¦ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:499 +#: ../../rst/user_guide/windows_winrm.rst:511 msgid "CredSSP and TLS 1.2" msgstr "CredSSP ãŠã‚ˆã³ TLS 1.2" -#: ../../rst/user_guide/windows_winrm.rst:500 +#: ../../rst/user_guide/windows_winrm.rst:512 msgid "By default the ``requests-credssp`` library is configured to authenticate over the TLS 1.2 protocol. TLS 1.2 is installed and enabled by default for Windows Server 2012 and Windows 8 and more recent releases." msgstr "デフォルトã§ã¯ã€``requests-credssp`` ライブラリーã¯ã€TLS 1.2 プãƒãƒˆã‚³ãƒ«ã§èªè¨¼ã™ã‚‹ã‚ˆã†ã«è¨å®šã•ã‚Œã¦ã„ã¾ã™ã€‚TLS 1.2 ã¯ã€Windows Server 2012 ãŠã‚ˆã³ Windows 8 ã¨ã€ãれ以é™ã®ãƒªãƒªãƒ¼ã‚¹ã§ã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã€æœ‰åŠ¹ã«ãªã£ã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:504 +#: ../../rst/user_guide/windows_winrm.rst:516 msgid "There are two ways that older hosts can be used with CredSSP:" msgstr "å¤ã„ホストを CredSSP ã§ä½¿ç”¨ã§ãる方法㯠2 ã¤ã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:506 +#: ../../rst/user_guide/windows_winrm.rst:518 msgid "Install and enable a hotfix to enable TLS 1.2 support (recommended for Server 2008 R2 and Windows 7)." msgstr "TLS 1.2 ã®ã‚µãƒãƒ¼ãƒˆã‚’有効ã«ã™ã‚‹ Hotfix をインストールã—ã¦æœ‰åŠ¹ã«ã—ã¦ãã ã•ã„ (Server 2008 R2 ãŠã‚ˆã³ Windows 7 ã§æŽ¨å¥¨)。" -#: ../../rst/user_guide/windows_winrm.rst:509 +#: ../../rst/user_guide/windows_winrm.rst:521 msgid "Set ``ansible_winrm_credssp_disable_tlsv1_2=True`` in the inventory to run over TLS 1.0. This is the only option when connecting to Windows Server 2008, which has no way of supporting TLS 1.2" msgstr "インベントリー㫠``ansible_winrm_credssp_disable_tlsv1_2=True`` ã‚’è¨å®šã—ã¦ã€TLS 1.0 ã§å®Ÿè¡Œã™ã‚‹ã‚ˆã†ã«è¨å®šã—ã¾ã™ã€‚ã“ã‚Œã¯ã€TLS 1.2 ã«å¯¾å¿œã—ã¦ã„ãªã„ Windows Server 2008 ã«æŽ¥ç¶šã™ã‚‹éš›ã®å”¯ä¸€ã®é¸æŠžè‚¢ã§ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:513 +#: ../../rst/user_guide/windows_winrm.rst:525 msgid "See :ref:`winrm_tls12` for more information on how to enable TLS 1.2 on the Windows host." msgstr "Windows ホスト㧠TLS 1.2 を有効ã«ã™ã‚‹æ–¹æ³•ã¯ã€ã€Œ:ref:`winrm_tls12`ã€ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_winrm.rst:517 +#: ../../rst/user_guide/windows_winrm.rst:529 msgid "Set CredSSP Certificate" msgstr "CredSSP 証明書ã®è¨å®š" -#: ../../rst/user_guide/windows_winrm.rst:518 +#: ../../rst/user_guide/windows_winrm.rst:530 msgid "CredSSP works by encrypting the credentials through the TLS protocol and uses a self-signed certificate by default. The ``CertificateThumbprint`` option under the WinRM service configuration can be used to specify the thumbprint of another certificate." msgstr "CredSSP ã¯ã€TLS プãƒãƒˆã‚³ãƒ«ã§èªè¨¼æƒ…å ±ã‚’æš—å·åŒ–ã—ã¦å‹•ä½œã—ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã¯è‡ªå·±ç½²å証明書を使用ã—ã¾ã™ã€‚WinRM サービス構æˆã® ``CertificateThumbprint`` オプションを使用ã—ã¦ã€åˆ¥ã®è¨¼æ˜Žæ›¸ã®ã‚µãƒ プリントを指定ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:521 +#: ../../rst/user_guide/windows_winrm.rst:533 msgid "This certificate configuration is independent of the WinRM listener certificate. With CredSSP, message transport still occurs over the WinRM listener, but the TLS-encrypted messages inside the channel use the service-level certificate." msgstr "ã“ã®è¨¼æ˜Žæ›¸æ§‹æˆã¯ã€WinRM リスナーã®è¨¼æ˜Žæ›¸ã¨ã¯ç‹¬ç«‹ã—ã¦ã„ã¾ã™ã€‚CredSSP ã§ã¯ã€ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãƒˆãƒ©ãƒ³ã‚¹ãƒãƒ¼ãƒˆã¯å¼•ã続ã WinRM リスナーを介ã—ã¦è¡Œã‚ã‚Œã¾ã™ãŒã€ãƒãƒ£ãƒ³ãƒãƒ«å†…ã® TLS æš—å·åŒ–メッセージã«ã¯ã‚µãƒ¼ãƒ“スレベル証明書ãŒä½¿ç”¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:525 -msgid "To explicitly set the certificate to use for CredSSP::" +#: ../../rst/user_guide/windows_winrm.rst:537 +msgid "To explicitly set the certificate to use for CredSSP:" msgstr "CredSSP ã«ä½¿ç”¨ã™ã‚‹è¨¼æ˜Žæ›¸ã‚’明示的ã«è¨å®šã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:535 +#: ../../rst/user_guide/windows_winrm.rst:549 msgid "Non-Administrator Accounts" msgstr "管ç†è€…以外ã®ã‚¢ã‚«ã‚¦ãƒ³ãƒˆ" -#: ../../rst/user_guide/windows_winrm.rst:536 +#: ../../rst/user_guide/windows_winrm.rst:550 msgid "WinRM is configured by default to only allow connections from accounts in the local ``Administrators`` group. This can be changed by running:" msgstr "WinRM ã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã€ãƒãƒ¼ã‚«ãƒ«ã® ``Administrators`` グループã®ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã‹ã‚‰ã®æŽ¥ç¶šã®ã¿ã‚’許å¯ã™ã‚‹ã‚ˆã†ã«è¨å®šã•ã‚Œã¦ã„ã¾ã™ã€‚ã“ã‚Œã¯ã€ä»¥ä¸‹ã‚’実行ã—ã¦å¤‰æ›´ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:543 +#: ../../rst/user_guide/windows_winrm.rst:557 msgid "This will display an ACL editor, where new users or groups may be added. To run commands over WinRM, users and groups must have at least the ``Read`` and ``Execute`` permissions enabled." msgstr "ã“ã‚Œã«ã‚ˆã‚Šã€ACL エディターãŒè¡¨ç¤ºã•ã‚Œã€æ–°ã—ã„ユーザーã¾ãŸã¯ã‚°ãƒ«ãƒ¼ãƒ—ã‚’è¿½åŠ ã§ãã¾ã™ã€‚WinRM ã§ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã™ã‚‹ã«ã¯ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŠã‚ˆã³ã‚°ãƒ«ãƒ¼ãƒ—ã«å°‘ãªãã¨ã‚‚ ``Read`` ãŠã‚ˆã³ ``Execute`` パーミッションãŒæœ‰åŠ¹ã«ãªã£ã¦ã„ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:547 +#: ../../rst/user_guide/windows_winrm.rst:561 msgid "While non-administrative accounts can be used with WinRM, most typical server administration tasks require some level of administrative access, so the utility is usually limited." msgstr "WinRM ã§ã¯ã€ç®¡ç†è€…以外ã®ã‚¢ã‚«ã‚¦ãƒ³ãƒˆã‚’使用ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ãŒã€ä¸€èˆ¬çš„ãªã‚µãƒ¼ãƒãƒ¼ç®¡ç†ä½œæ¥ã§ã¯ã€ã‚る程度ã®ç®¡ç†è€…権é™ãŒå¿…è¦ã¨ãªã‚‹ãŸã‚ã€å®Ÿç”¨æ€§ã¯é™ã‚‰ã‚Œã¦ã—ã¾ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:551 +#: ../../rst/user_guide/windows_winrm.rst:565 msgid "WinRM Encryption" msgstr "WinRM æš—å·åŒ–" -#: ../../rst/user_guide/windows_winrm.rst:552 +#: ../../rst/user_guide/windows_winrm.rst:566 msgid "By default WinRM will fail to work when running over an unencrypted channel. The WinRM protocol considers the channel to be encrypted if using TLS over HTTP (HTTPS) or using message level encryption. Using WinRM with TLS is the recommended option as it works with all authentication options, but requires a certificate to be created and used on the WinRM listener." msgstr "デフォルトã§ã¯ã€WinRM ã¯ã€æš—å·åŒ–ã•ã‚Œã¦ã„ãªã„ãƒãƒ£ãƒ³ãƒãƒ«ä¸Šã§å®Ÿè¡Œã™ã‚‹ã¨ã€å‹•ä½œã«å¤±æ•—ã—ã¾ã™ã€‚WinRM プãƒãƒˆã‚³ãƒ«ã¯ã€TLS over HTTP (HTTPS) を使用ã—ã¦ã„ã‚‹å ´åˆã‚„ã€ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãƒ¬ãƒ™ãƒ«ã®æš—å·åŒ–を使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ãƒãƒ£ãƒ³ãƒãƒ«ãŒæš—å·åŒ–ã•ã‚Œã¦ã„ã‚‹ã¨ã¿ãªã—ã¾ã™ã€‚WinRM ã‚’ TLS ã§ä½¿ç”¨ã™ã‚‹ã“ã¨ã¯ã€ã™ã¹ã¦ã®èªè¨¼ã‚ªãƒ—ションã§å‹•ä½œã™ã‚‹ãŸã‚ã€æŽ¨å¥¨ã•ã‚Œã‚‹ã‚ªãƒ—ションã§ã™ãŒã€WinRM リスナーã§è¨¼æ˜Žæ›¸ã‚’作æˆã—ã¦ä½¿ç”¨ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:558 +#: ../../rst/user_guide/windows_winrm.rst:572 msgid "The ``ConfigureRemotingForAnsible.ps1`` creates a self-signed certificate and creates the listener with that certificate. If in a domain environment, ADCS can also create a certificate for the host that is issued by the domain itself." msgstr "``ConfigureRemotingForAnsible.ps1`` ã¯ã€è‡ªå·±ç½²å証明書を作æˆã—ã€ãã®è¨¼æ˜Žæ›¸ã§ãƒªã‚¹ãƒŠãƒ¼ã‚’作æˆã—ã¾ã™ã€‚ドメイン環境ã§ã‚ã‚Œã°ã€ADCS ã¯ãƒ‰ãƒ¡ã‚¤ãƒ³è‡ªä½“ãŒç™ºè¡Œã™ã‚‹ãƒ›ã‚¹ãƒˆç”¨ã®è¨¼æ˜Žæ›¸ã‚’作æˆã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:562 +#: ../../rst/user_guide/windows_winrm.rst:576 msgid "If using HTTPS is not an option, then HTTP can be used when the authentication option is ``NTLM``, ``Kerberos`` or ``CredSSP``. These protocols will encrypt the WinRM payload with their own encryption method before sending it to the server. The message-level encryption is not used when running over HTTPS because the encryption uses the more secure TLS protocol instead. If both transport and message encryption is required, set ``ansible_winrm_message_encryption=always`` in the host vars." msgstr "HTTPS を使用ã™ã‚‹ã“ã¨ãŒã§ããªã„å ´åˆã¯ã€èªè¨¼ã‚ªãƒ—ション㌠``NTLM``ã€``Kerberos``ã€ã¾ãŸã¯ ``CredSSP`` ã§ã‚ã‚Œã°ã€HTTP を使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“れらã®ãƒ—ãƒãƒˆã‚³ãƒ«ã¯ã€WinRM ペイãƒãƒ¼ãƒ‰ã‚’独自ã®æš—å·åŒ–æ–¹å¼ã§æš—å·åŒ–ã—ã¦ã‹ã‚‰ã‚µãƒ¼ãƒãƒ¼ã«é€ä¿¡ã—ã¾ã™ã€‚æš—å·åŒ–ã¯ã€ã‚ˆã‚Šå®‰å…¨ãª TLS プãƒãƒˆã‚³ãƒ«ã‚’代ã‚ã‚Šã«ä½¿ç”¨ã™ã‚‹ãŸã‚ã€HTTPS ã§å®Ÿè¡Œã™ã‚‹å ´åˆã«ã€ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãƒ¬ãƒ™ãƒ«ã®æš—å·åŒ–ã¯ä½¿ç”¨ã•ã‚Œã¾ã›ã‚“。トランスãƒãƒ¼ãƒˆã¨ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã®ä¸¡æ–¹ã®æš—å·åŒ–ãŒå¿…è¦ãªå ´åˆã¯ã€ãƒ›ã‚¹ãƒˆå¤‰æ•°ã« ``ansible_winrm_message_encryption=always`` ã‚’è¨å®šã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_winrm.rst:570 +#: ../../rst/user_guide/windows_winrm.rst:584 msgid "Message encryption over HTTP requires pywinrm>=0.3.0." msgstr "HTTPã§ã®ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸æš—å·åŒ–ã«ã¯ 0.3.0 以上㮠pywinrm ãŒå¿…è¦ã§ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:572 -msgid "A last resort is to disable the encryption requirement on the Windows host. This should only be used for development and debugging purposes, as anything sent from Ansible can be viewed, manipulated and also the remote session can completely be taken over by anyone on the same network. To disable the encryption requirement::" +#: ../../rst/user_guide/windows_winrm.rst:586 +msgid "A last resort is to disable the encryption requirement on the Windows host. This should only be used for development and debugging purposes, as anything sent from Ansible can be viewed, manipulated and also the remote session can completely be taken over by anyone on the same network. To disable the encryption requirement:" msgstr "最後ã®æ‰‹æ®µã¨ã—ã¦ã€Windows ホストã®æš—å·åŒ–è¦ä»¶ã‚’無効ã«ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã‚Œã¯ã€Ansible ã‹ã‚‰é€ä¿¡ã•ã‚ŒãŸã‚‚ã®ã¯ã™ã¹ã¦é–²è¦§ã€æ“作ã§ãã€ã¾ãŸåŒã˜ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ä¸Šã®èª°ã‚‚ãŒãƒªãƒ¢ãƒ¼ãƒˆã‚»ãƒƒã‚·ãƒ§ãƒ³ã‚’完全ã«ä¹—ã£å–ã‚‹ã“ã¨ãŒã§ãã‚‹ãŸã‚ã€é–‹ç™ºã‚„デãƒãƒƒã‚°ã®ç›®çš„ã§ã®ã¿ä½¿ç”¨ã—ã¦ãã ã•ã„。暗å·åŒ–を無効ã«ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®æ‰‹é †ã«å¾“ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:580 +#: ../../rst/user_guide/windows_winrm.rst:596 msgid "Do not disable the encryption check unless it is absolutely required. Doing so could allow sensitive information like credentials and files to be intercepted by others on the network." msgstr "ã©ã†ã—ã¦ã‚‚å¿…è¦ãªå ´åˆã‚’除ãã€æš—å·åŒ–ãƒã‚§ãƒƒã‚¯ã‚’無効ã«ã—ãªã„ã§ãã ã•ã„。暗å·åŒ–ãƒã‚§ãƒƒã‚¯ã‚’無効ã«ã™ã‚‹ã¨ã€èªè¨¼æƒ…å ±ã‚„ãƒ•ã‚¡ã‚¤ãƒ«ãªã©ã®æ©Ÿå¯†æƒ…å ±ãŒãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ä¸Šã®ä»–ã®äººã«å‚å—ã•ã‚Œã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:585 +#: ../../rst/user_guide/windows_winrm.rst:601 msgid "Inventory Options" msgstr "インベントリーオプション" -#: ../../rst/user_guide/windows_winrm.rst:586 +#: ../../rst/user_guide/windows_winrm.rst:602 msgid "Ansible's Windows support relies on a few standard variables to indicate the username, password, and connection type of the remote hosts. These variables are most easily set up in the inventory, but can be set on the ``host_vars``/ ``group_vars`` level." msgstr "Ansible ã® Windows サãƒãƒ¼ãƒˆã¯ã€ãƒªãƒ¢ãƒ¼ãƒˆãƒ›ã‚¹ãƒˆã®ãƒ¦ãƒ¼ã‚¶ãƒ¼åã€ãƒ‘スワードã€æŽ¥ç¶šã‚¿ã‚¤ãƒ—を示ã™ã„ãã¤ã‹ã®æ¨™æº–変数ã«ä¾å˜ã—ã¦ã„ã¾ã™ã€‚ã“れらã®å¤‰æ•°ã¯ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã§æœ€ã‚‚ç°¡å˜ã«è¨å®šã§ãã¾ã™ãŒã€``host_vars``/``group_vars`` レベルã§è¨å®šã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:591 +#: ../../rst/user_guide/windows_winrm.rst:607 msgid "When setting up the inventory, the following variables are required:" msgstr "インベントリーをè¨å®šã™ã‚‹éš›ã«ã€ä»¥ä¸‹ã®å¤‰æ•°ãŒå¿…è¦ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:606 +#: ../../rst/user_guide/windows_winrm.rst:622 msgid "Using the variables above, Ansible will connect to the Windows host with Basic authentication through HTTPS. If ``ansible_user`` has a UPN value like ``username@MY.DOMAIN.COM`` then the authentication option will automatically attempt to use Kerberos unless ``ansible_winrm_transport`` has been set to something other than ``kerberos``." msgstr "上記ã®å¤‰æ•°ã‚’使用ã™ã‚‹ã¨ã€Ansible 㯠HTTPS を通ã˜ã¦ Basic èªè¨¼ã§ Windows ホストã«æŽ¥ç¶šã—ã¾ã™ã€‚``ansible_user`` ã« ``username@MY.DOMAIN.COM`` ã®ã‚ˆã†ãª UPN 値ãŒã‚ã‚‹å ´åˆã¯ã€``ansible_winrm_transport`` ㌠``kerberos`` 以外ã«è¨å®šã•ã‚Œã¦ã„ãªã„é™ã‚Šã€èªè¨¼ã‚ªãƒ—ションã¯è‡ªå‹•çš„ã« Kerberos ã®ä½¿ç”¨ã‚’試ã¿ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:612 +#: ../../rst/user_guide/windows_winrm.rst:628 msgid "The following custom inventory variables are also supported for additional configuration of WinRM connections:" msgstr "以下ã®ã‚«ã‚¹ã‚¿ãƒ インベントリー変数もã€WinRM 接続ã®è¿½åŠ è¨å®šã®ãŸã‚ã«ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:615 +#: ../../rst/user_guide/windows_winrm.rst:631 msgid "``ansible_port``: The port WinRM will run over, HTTPS is ``5986`` which is the default while HTTP is ``5985``" msgstr "``ansible_port``: WinRM ãŒå®Ÿè¡Œã™ã‚‹ãƒãƒ¼ãƒˆã§ã™ã€‚HTTPS ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã¯ ``5986`` ã§ã€HTTP ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã¯ ``5985`` ã§ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:618 +#: ../../rst/user_guide/windows_winrm.rst:634 msgid "``ansible_winrm_scheme``: Specify the connection scheme (``http`` or ``https``) to use for the WinRM connection. Ansible uses ``https`` by default unless ``ansible_port`` is ``5985``" msgstr "``ansible_winrm_scheme``: WinRM 接続ã«ä½¿ç”¨ã™ã‚‹æŽ¥ç¶šã‚¹ã‚ーム(``http`` ã¾ãŸã¯ ``https``) を指定ã—ã¾ã™ã€‚Ansible ã¯ã€``ansible_port`` ㌠``5985`` ã«æŒ‡å®šã•ã‚Œã¦ã„ãªã„é™ã‚Šã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ ``https`` を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:622 +#: ../../rst/user_guide/windows_winrm.rst:638 msgid "``ansible_winrm_path``: Specify an alternate path to the WinRM endpoint, Ansible uses ``/wsman`` by default" msgstr "``ansible_winrm_path``: WinRMエンドãƒã‚¤ãƒ³ãƒˆã¸ã®åˆ¥ã®ãƒ‘スを指定ã—ã¾ã™ã€‚Ansible ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ ``/wsman`` を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:625 +#: ../../rst/user_guide/windows_winrm.rst:641 msgid "``ansible_winrm_realm``: Specify the realm to use for Kerberos authentication. If ``ansible_user`` contains ``@``, Ansible will use the part of the username after ``@`` by default" msgstr "``ansible_winrm_realm``: Kerberos èªè¨¼ã«ä½¿ç”¨ã™ã‚‹ãƒ¬ãƒ«ãƒ を指定ã—ã¾ã™ã€‚``ansible_user`` ã« ``@`` ãŒå«ã¾ã‚Œã‚‹å ´åˆã€Ansible ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ ``@`` ã®å¾Œã«ãƒ¦ãƒ¼ã‚¶ãƒ¼åã®ä¸€éƒ¨ã‚’使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:629 +#: ../../rst/user_guide/windows_winrm.rst:645 msgid "``ansible_winrm_transport``: Specify one or more authentication transport options as a comma-separated list. By default, Ansible will use ``kerberos, basic`` if the ``kerberos`` module is installed and a realm is defined, otherwise it will be ``plaintext``" msgstr "``ansible_winrm_transport``: 1 ã¤ä»¥ä¸Šã®èªè¨¼ãƒˆãƒ©ãƒ³ã‚¹ãƒãƒ¼ãƒˆã‚ªãƒ—ションをコンマ区切りã®ãƒªã‚¹ãƒˆã§æŒ‡å®šã—ã¾ã™ã€‚デフォルトã§ã¯ã€``kerberos`` モジュールãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã¦ãƒ¬ãƒ«ãƒ ãŒå®šç¾©ã•ã‚Œã¦ã„ã‚‹å ´åˆã€Ansible 㯠``kerberos, basic`` を使用ã—ã€ãれ以外ã®å ´åˆã¯ ``plaintext`` ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:634 +#: ../../rst/user_guide/windows_winrm.rst:650 msgid "``ansible_winrm_server_cert_validation``: Specify the server certificate validation mode (``ignore`` or ``validate``). Ansible defaults to ``validate`` on Python 2.7.9 and higher, which will result in certificate validation errors against the Windows self-signed certificates. Unless verifiable certificates have been configured on the WinRM listeners, this should be set to ``ignore``" msgstr "``ansible_winrm_server_cert_validation``: サーãƒãƒ¼è¨¼æ˜Žæ›¸ã®æ¤œè¨¼ãƒ¢ãƒ¼ãƒ‰ (``ignore`` ã¾ãŸã¯``validate``) を指定ã—ã¾ã™ã€‚Ansible ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã¯ã€Python 2.7.9 以é™ã§ã¯ ``validate`` ã§ã€ã“れ㯠Windows ã®è‡ªå·±ç½²å証明書ã«å¯¾ã—ã¦è¨¼æ˜Žæ›¸ã®æ¤œè¨¼ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã—ã¾ã™ã€‚WinRM リスナーã§æ¤œè¨¼å¯èƒ½ãªè¨¼æ˜Žæ›¸ãŒè¨å®šã•ã‚Œã¦ã„ãªã„å ´åˆã¯ã€ã“ã®è¨å®šã‚’ ``ignore`` ã«è¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:641 +#: ../../rst/user_guide/windows_winrm.rst:657 msgid "``ansible_winrm_operation_timeout_sec``: Increase the default timeout for WinRM operations, Ansible uses ``20`` by default" msgstr "``ansible_winrm_operation_timeout_sec``: WinRM æ“作ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã‚¿ã‚¤ãƒ アウトを増やã™ã¨ã€Ansible ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ ``20`` を使用ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:644 +#: ../../rst/user_guide/windows_winrm.rst:660 msgid "``ansible_winrm_read_timeout_sec``: Increase the WinRM read timeout, Ansible uses ``30`` by default. Useful if there are intermittent network issues and read timeout errors keep occurring" msgstr "``ansible_winrm_read_timeout_sec``: WinRM ã®èªã¿å–りタイムアウトを増やã—ã¾ã™ã€‚Ansible ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ ``30`` を使用ã—ã¾ã™ã€‚ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã®å•é¡ŒãŒæ–続的ã«ç™ºç”Ÿã—ã€èªã¿å–りタイムアウトã®ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã—続ã‘ã‚‹å ´åˆã«æœ‰åŠ¹ã§ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:648 +#: ../../rst/user_guide/windows_winrm.rst:664 msgid "``ansible_winrm_message_encryption``: Specify the message encryption operation (``auto``, ``always``, ``never``) to use, Ansible uses ``auto`` by default. ``auto`` means message encryption is only used when ``ansible_winrm_scheme`` is ``http`` and ``ansible_winrm_transport`` supports message encryption. ``always`` means message encryption will always be used and ``never`` means message encryption will never be used" msgstr "``ansible_winrm_message_encryption``: 使用ã™ã‚‹ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸æš—å·åŒ–æ“作 (``auto``ã€``always``ã€``never``) を指定ã—ã¾ã™ã€‚Ansible ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ ``auto`` を使用ã—ã¾ã™ã€‚``auto`` ã¯ã€``ansible_winrm_scheme`` ㌠``http`` ã§ã€``ansible_winrm_transport`` ãŒãƒ¡ãƒƒã‚»ãƒ¼ã‚¸æš—å·åŒ–をサãƒãƒ¼ãƒˆã—ã¦ã„ã‚‹å ´åˆã«é™ã‚Šã€ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸æš—å·åŒ–ãŒä½¿ç”¨ã•ã‚Œã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚``always`` ã¯ã€ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸æš—å·åŒ–ãŒå¸¸ã«ä½¿ç”¨ã•ã‚Œã‚‹ã“ã¨ã‚’æ„味ã—ã€``never`` ã¯ã€ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸æš—å·åŒ–ãŒæ±ºã—ã¦ä½¿ç”¨ã•ã‚Œãªã„ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:655 +#: ../../rst/user_guide/windows_winrm.rst:671 msgid "``ansible_winrm_ca_trust_path``: Used to specify a different cacert container than the one used in the ``certifi`` module. See the HTTPS Certificate Validation section for more details." msgstr "``ansible_winrm_ca_trust_path``: ``certifi`` モジュールã§ä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹ã‚‚ã®ã¨ã¯ç•°ãªã‚‹ cacert コンテナーを指定ã™ã‚‹ãŸã‚ã«ä½¿ç”¨ã—ã¾ã™ã€‚詳細ã¯ã€ã€ŒHTTPS 証明書ã®æ¤œè¨¼ã€ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_winrm.rst:659 +#: ../../rst/user_guide/windows_winrm.rst:675 msgid "``ansible_winrm_send_cbt``: When using ``ntlm`` or ``kerberos`` over HTTPS, the authentication library will try to send channel binding tokens to mitigate against man in the middle attacks. This flag controls whether these bindings will be sent or not (default: ``yes``)." msgstr "``ansible_winrm_send_cbt``: ``ntlm`` ã¾ãŸã¯ ``kerberos`` ã‚’ HTTPS ã§ä½¿ç”¨ã™ã‚‹å ´åˆã€èªè¨¼ãƒ©ã‚¤ãƒ–ラリーã¯ã€ä¸é–“者攻撃を緩和ã™ã‚‹ãŸã‚ã«ãƒãƒ£ãƒ³ãƒãƒ«ãƒã‚¤ãƒ³ãƒ‡ã‚£ãƒ³ã‚°ãƒˆãƒ¼ã‚¯ãƒ³ã®é€ä¿¡ã‚’試ã¿ã¾ã™ã€‚ã“ã®ãƒ•ãƒ©ã‚°ã¯ã€ã“れらã®ãƒã‚¤ãƒ³ãƒ‡ã‚£ãƒ³ã‚°ã‚’é€ä¿¡ã™ã‚‹ã‹ã©ã†ã‹ã‚’制御ã—ã¾ã™ (デフォルト: ``yes``)。" -#: ../../rst/user_guide/windows_winrm.rst:664 +#: ../../rst/user_guide/windows_winrm.rst:680 msgid "``ansible_winrm_*``: Any additional keyword arguments supported by ``winrm.Protocol`` may be provided in place of ``*``" msgstr "``ansible_winrm_*``: ``winrm.Protocol`` ã§ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¦ã„ã‚‹ä»»æ„ã®è¿½åŠ ã‚ーワード引数ã¯ã€ä»£ã‚ã‚Šã« ``*`` ã§æŒ‡å®šã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:667 +#: ../../rst/user_guide/windows_winrm.rst:683 msgid "In addition, there are also specific variables that need to be set for each authentication option. See the section on authentication above for more information." msgstr "ã•ã‚‰ã«ã€å„èªè¨¼ã‚ªãƒ—ションã§è¨å®šã™ã‚‹å¿…è¦ãŒã‚る特定ã®å¤‰æ•°ã‚‚ã‚ã‚Šã¾ã™ã€‚詳細ã¯ã€ä¸Šè¨˜ã®èªè¨¼ã«é–¢ã™ã‚‹ã‚»ã‚¯ã‚·ãƒ§ãƒ³ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_winrm.rst:670 +#: ../../rst/user_guide/windows_winrm.rst:686 msgid "Ansible 2.0 has deprecated the \"ssh\" from ``ansible_ssh_user``, ``ansible_ssh_pass``, ``ansible_ssh_host``, and ``ansible_ssh_port`` to become ``ansible_user``, ``ansible_password``, ``ansible_host``, and ``ansible_port``. If using a version of Ansible prior to 2.0, the older style (``ansible_ssh_*``) should be used instead. The shorter variables are ignored, without warning, in older versions of Ansible." msgstr "Ansible 2.0 ã§ã¯ã€``ansible_ssh_user``ã€``ansible_ssh_pass``ã€``ansible_ssh_host``ã€ãŠã‚ˆã³ ``ansible_ssh_port`` ã®ã€Œsshã€ãŒéžæŽ¨å¥¨ã¨ãªã‚Šã€``ansible_user``ã€``ansible_password``ã€``ansible_host``ã€ãŠã‚ˆã³ ``ansible_port`` ã¨ãªã‚Šã¾ã—ãŸã€‚Ansible 2.0 よりå‰ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã¯ã€ä»£ã‚ã‚Šã«å¤ã„スタイル (``ansible_ssh_*``) を使用ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚çŸã„æ–¹ã®å¤‰æ•°ã¯ã€å¤ã„ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã® Ansible ã§ã¯è¦å‘Šãªã—ã«ç„¡è¦–ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:677 +#: ../../rst/user_guide/windows_winrm.rst:693 msgid "``ansible_winrm_message_encryption`` is different from transport encryption done over TLS. The WinRM payload is still encrypted with TLS when run over HTTPS, even if ``ansible_winrm_message_encryption=never``." msgstr "``ansible_winrm_message_encryption`` ã¯ã€TLS 上ã§è¡Œã‚れるトランスãƒãƒ¼ãƒˆæš—å·åŒ–ã¨ã¯ç•°ãªã‚Šã¾ã™ã€‚WinRM ペイãƒãƒ¼ãƒ‰ã¯ã€``ansible_winrm_message_encryption=never`` ã§ã‚ã£ã¦ã‚‚ã€HTTPS ã§å®Ÿè¡Œã•ã‚ŒãŸå ´åˆã§ã‚‚ TLS ã§æš—å·åŒ–ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:682 +#: ../../rst/user_guide/windows_winrm.rst:698 msgid "IPv6 Addresses" msgstr "IPv6 アドレス" -#: ../../rst/user_guide/windows_winrm.rst:683 +#: ../../rst/user_guide/windows_winrm.rst:699 msgid "IPv6 addresses can be used instead of IPv4 addresses or hostnames. This option is normally set in an inventory. Ansible will attempt to parse the address using the `ipaddress <https://docs.python.org/3/library/ipaddress.html>`_ package and pass to pywinrm correctly." msgstr "IPv4 アドレスやホストåã®ä»£ã‚ã‚Šã«ã€IPv6 アドレスを使用ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã®ã‚ªãƒ—ションã¯é€šå¸¸ã€ã‚¤ãƒ³ãƒ™ãƒ³ãƒˆãƒªãƒ¼ã§è¨å®šã—ã¾ã™ã€‚Ansible ã¯ã€`ipaddress <https://docs.python.org/3/library/ipaddress.html>`_ パッケージを使用ã—ã¦ã‚¢ãƒ‰ãƒ¬ã‚¹ã®è§£æžã‚’試ã¿ã€pywinrm ã«æ£ã—ã渡ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:688 +#: ../../rst/user_guide/windows_winrm.rst:704 msgid "When defining a host using an IPv6 address, just add the IPv6 address as you would an IPv4 address or hostname:" msgstr "IPv6 アドレスを使用ã—ã¦ãƒ›ã‚¹ãƒˆã‚’定義ã™ã‚‹å ´åˆã¯ã€IPv4 アドレスやホストåã¨åŒã˜ã‚ˆã†ã« IPv6 ã‚¢ãƒ‰ãƒ¬ã‚¹ã‚’è¿½åŠ ã™ã‚‹ã ã‘ã§ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:702 +#: ../../rst/user_guide/windows_winrm.rst:718 msgid "The ipaddress library is only included by default in Python 3.x. To use IPv6 addresses in Python 2.7, make sure to run ``pip install ipaddress`` which installs a backported package." msgstr "ipaddress ライブラリー㯠Python 3.x ã«ã®ã¿ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§å«ã¾ã‚Œã¦ã„ã¾ã™ã€‚Python 2.7 㧠IPv6 アドレスを使用ã™ã‚‹ã«ã¯ã€ãƒãƒƒã‚¯ãƒãƒ¼ãƒˆã•ã‚ŒãŸãƒ‘ッケージをインストールã™ã‚‹ ``pip install ipaddress`` ã‚’å¿…ãšå®Ÿè¡Œã—ã¦ãã ã•ã„。" -#: ../../rst/user_guide/windows_winrm.rst:707 +#: ../../rst/user_guide/windows_winrm.rst:723 msgid "HTTPS Certificate Validation" msgstr "HTTPS 証明書ã®æ¤œè¨¼" -#: ../../rst/user_guide/windows_winrm.rst:708 +#: ../../rst/user_guide/windows_winrm.rst:724 msgid "As part of the TLS protocol, the certificate is validated to ensure the host matches the subject and the client trusts the issuer of the server certificate. When using a self-signed certificate or setting ``ansible_winrm_server_cert_validation: ignore`` these security mechanisms are bypassed. While self signed certificates will always need the ``ignore`` flag, certificates that have been issued from a certificate authority can still be validated." msgstr "TLS プãƒãƒˆã‚³ãƒ«ã®ä¸€ç’°ã¨ã—ã¦ã€è¨¼æ˜Žæ›¸ãŒæ¤œè¨¼ã•ã‚Œã€ãƒ›ã‚¹ãƒˆãŒã‚µãƒ–ジェクトã¨ä¸€è‡´ã—ã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆãŒã‚µãƒ¼ãƒãƒ¼è¨¼æ˜Žæ›¸ã®ç™ºè¡Œè€…ã‚’ä¿¡é ¼ã—ã¦ã„ã‚‹ã“ã¨ãŒç¢ºèªã•ã‚Œã¾ã™ã€‚自己署å証明書を使用ã—ãŸã‚Šã€``ansible_winrm_server_cert_validation: ignore`` ã‚’è¨å®šã—ãŸã‚Šã™ã‚‹ã¨ã€ã“れらã®ã‚»ã‚ュリティーメカニズムãŒå›žé¿ã•ã‚Œã¾ã™ã€‚自己署å証明書ã«ã¯å¸¸ã« ``ignore`` フラグãŒå¿…è¦ã§ã™ãŒã€èªè¨¼å±€ã‹ã‚‰ç™ºè¡Œã•ã‚ŒãŸè¨¼æ˜Žæ›¸ã¯æ¤œè¨¼ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:716 +#: ../../rst/user_guide/windows_winrm.rst:732 msgid "One of the more common ways of setting up a HTTPS listener in a domain environment is to use Active Directory Certificate Service (AD CS). AD CS is used to generate signed certificates from a Certificate Signing Request (CSR). If the WinRM HTTPS listener is using a certificate that has been signed by another authority, like AD CS, then Ansible can be set up to trust that issuer as part of the TLS handshake." msgstr "ドメイン環境㧠HTTPS リスナーをセットアップã™ã‚‹ä¸€èˆ¬çš„ãªæ–¹æ³•ã® 1 ã¤ã«ã€Active Directory Certificate Service (AD CS) を使用ã™ã‚‹æ–¹æ³•ãŒã‚ã‚Šã¾ã™ã€‚AD CS ã¯ã€CSR (Certificate Signing Request) ã‹ã‚‰ç½²å付ã証明書を生æˆã™ã‚‹ãŸã‚ã«ä½¿ç”¨ã•ã‚Œã¾ã™ã€‚WinRM HTTPS リスナー㌠AD CS ã®ã‚ˆã†ãªåˆ¥ã®æ©Ÿé–¢ã«ã‚ˆã£ã¦ç½²åã•ã‚ŒãŸè¨¼æ˜Žæ›¸ã‚’使用ã—ã¦ã„ã‚‹å ´åˆã€Ansible 㯠TLS ãƒãƒ³ãƒ‰ã‚·ã‚§ã‚¤ã‚¯ã®ä¸€éƒ¨ã¨ã—ã¦ãã®ç™ºè¡Œè€…ã‚’ä¿¡é ¼ã™ã‚‹ã‚ˆã†ã«è¨å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:723 +#: ../../rst/user_guide/windows_winrm.rst:739 msgid "To get Ansible to trust a Certificate Authority (CA) like AD CS, the issuer certificate of the CA can be exported as a PEM encoded certificate. This certificate can then be copied locally to the Ansible controller and used as a source of certificate validation, otherwise known as a CA chain." msgstr "AD CS ã®ã‚ˆã†ãªèªè¨¼å±€ (CA) ã‚’ Ansible ã«ä¿¡é ¼ã•ã›ã‚‹ã«ã¯ã€CA ã®ç™ºè¡Œè€…証明書を PEM エンコード証明書ã¨ã—ã¦ã‚¨ã‚¯ã‚¹ãƒãƒ¼ãƒˆã—ã¾ã™ã€‚ã“ã®è¨¼æ˜Žæ›¸ã¯ã€Ansible コントãƒãƒ¼ãƒ©ãƒ¼ã®ãƒãƒ¼ã‚«ãƒ«ã«ã‚³ãƒ”ーã—ã¦ã€è¨¼æ˜Žæ›¸æ¤œè¨¼ã®ã‚½ãƒ¼ã‚¹ã¨ã—ã¦ä½¿ç”¨ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ (CA ãƒã‚§ãƒ¼ãƒ³ã¨ã‚‚呼ã°ã‚Œã¾ã™)。" -#: ../../rst/user_guide/windows_winrm.rst:728 +#: ../../rst/user_guide/windows_winrm.rst:744 msgid "The CA chain can contain a single or multiple issuer certificates and each entry is contained on a new line. To then use the custom CA chain as part of the validation process, set ``ansible_winrm_ca_trust_path`` to the path of the file. If this variable is not set, the default CA chain is used instead which is located in the install path of the Python package `certifi <https://github.com/certifi/python-certifi>`_." msgstr "CA ãƒã‚§ãƒ¼ãƒ³ã«ã¯ã€å˜ä¸€ã¾ãŸã¯è¤‡æ•°ã®ç™ºè¡Œè€…証明書をå«ã‚ã‚‹ã“ã¨ãŒã§ãã€å„エントリーã¯æ–°ã—ã„è¡Œã«å«ã¾ã‚Œã¾ã™ã€‚èªè¨¼ãƒ—ãƒã‚»ã‚¹ã®ä¸€éƒ¨ã¨ã—ã¦ã‚«ã‚¹ã‚¿ãƒ CA ãƒã‚§ãƒ¼ãƒ³ã‚’使用ã™ã‚‹ã«ã¯ã€``ansible_winrm_ca_trust_path`` ã«ãƒ•ã‚¡ã‚¤ãƒ«ã®ãƒ‘スをè¨å®šã—ã¾ã™ã€‚ã“ã®å¤‰æ•°ãŒè¨å®šã•ã‚Œã¦ã„ãªã„å ´åˆã¯ã€Python パッケージ `certifi <https://github.com/certifi/python-certifi>`_ ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãƒ‘スã«ã‚るデフォルト㮠CAムェーンãŒä½¿ç”¨ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:735 +#: ../../rst/user_guide/windows_winrm.rst:751 msgid "Each HTTP call is done by the Python requests library which does not use the systems built-in certificate store as a trust authority. Certificate validation will fail if the server's certificate issuer is only added to the system's truststore." msgstr "HTTP 呼ã³å‡ºã—ã¯ãã‚Œãžã‚Œã€ã‚·ã‚¹ãƒ†ãƒ ã«çµ„ã¿è¾¼ã¾ã‚ŒãŸè¨¼æ˜Žæ›¸ã‚¹ãƒˆã‚¢ã‚’ä¿¡é ¼æ©Ÿé–¢ã¨ã—ã¦ä½¿ç”¨ã—ãªã„ Python リクエストライブラリーã«ã‚ˆã£ã¦è¡Œã‚ã‚Œã¾ã™ã€‚サーãƒãƒ¼ã®è¨¼æ˜Žæ›¸ç™ºè¡Œè€…ãŒã‚·ã‚¹ãƒ†ãƒ ã®ãƒˆãƒ©ã‚¹ãƒˆã‚¹ãƒˆã‚¢ã«è¿½åŠ ã•ã‚Œã¦ã„ãªã„å ´åˆã€è¨¼æ˜Žæ›¸ã®æ¤œè¨¼ã¯å¤±æ•—ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:743 +#: ../../rst/user_guide/windows_winrm.rst:759 msgid "TLS 1.2 Support" msgstr "TLS 1.2 ã®ã‚µãƒãƒ¼ãƒˆ" -#: ../../rst/user_guide/windows_winrm.rst:744 -msgid "As WinRM runs over the HTTP protocol, using HTTPS means that the TLS protocol is used to encrypt the WinRM messages. TLS will automatically attempt to negotiate the best protocol and cipher suite that is available to both the client and the server. If a match cannot be found then Ansible will error out with a message similar to::" +#: ../../rst/user_guide/windows_winrm.rst:760 +msgid "As WinRM runs over the HTTP protocol, using HTTPS means that the TLS protocol is used to encrypt the WinRM messages. TLS will automatically attempt to negotiate the best protocol and cipher suite that is available to both the client and the server. If a match cannot be found then Ansible will error out with a message similar to:" msgstr "WinRM 㯠HTTP プãƒãƒˆã‚³ãƒ«ä¸Šã§å‹•ä½œã™ã‚‹ãŸã‚ã€HTTPS を使用ã™ã‚‹ã¨ã„ã†ã“ã¨ã¯ã€WinRM メッセージã®æš—å·åŒ–ã« TLS プãƒãƒˆã‚³ãƒ«ãŒä½¿ç”¨ã•ã‚Œã‚‹ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚TLS ã¯ã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã¨ã‚µãƒ¼ãƒãƒ¼ã®ä¸¡æ–¹ã§åˆ©ç”¨å¯èƒ½ãªã€æœ€é©ãªãƒ—ãƒãƒˆã‚³ãƒ«ã¨æš—å·ã‚¹ã‚¤ãƒ¼ãƒˆã‚’自動的ã«å–り決ã‚よã†ã¨ã—ã¾ã™ã€‚一致ã™ã‚‹ã‚‚ã®ãŒè¦‹ã¤ã‹ã‚‰ãªã„å ´åˆã€Ansible ã¯æ¬¡ã®ã‚ˆã†ãªãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã§ã‚¨ãƒ©ãƒ¼ã«ãªã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:752 +#: ../../rst/user_guide/windows_winrm.rst:770 msgid "Commonly this is when the Windows host has not been configured to support TLS v1.2 but it could also mean the Ansible controller has an older OpenSSL version installed." msgstr "ã“ã‚Œã¯ã€Windows ホスト㌠TLS v1.2 をサãƒãƒ¼ãƒˆã™ã‚‹ã‚ˆã†ã«è¨å®šã•ã‚Œã¦ã„ãªã„å ´åˆã§ã™ãŒã€Ansible コントãƒãƒ¼ãƒ©ãƒ¼ã«å¤ã„ OpenSSL ãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ã‚‹ã“ã¨ã‚‚æ„味ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:756 +#: ../../rst/user_guide/windows_winrm.rst:774 msgid "Windows 8 and Windows Server 2012 come with TLS v1.2 installed and enabled by default but older hosts, like Server 2008 R2 and Windows 7, have to be enabled manually." msgstr "Windows 8 ãŠã‚ˆã³ Windows Server 2012 ã«ã¯ã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ TLS v1.2 ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã€æœ‰åŠ¹ã«ãªã£ã¦ã„ã¾ã™ãŒã€Server 2008 R2 ã‚„ Windows 7 ãªã©ã®å¤ã„ホストã¯æ‰‹å‹•ã§æœ‰åŠ¹ã«ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:760 +#: ../../rst/user_guide/windows_winrm.rst:778 msgid "There is a bug with the TLS 1.2 patch for Server 2008 which will stop Ansible from connecting to the Windows host. This means that Server 2008 cannot be configured to use TLS 1.2. Server 2008 R2 and Windows 7 are not affected by this issue and can use TLS 1.2." msgstr "Server 2008 ã® TLS 1.2 パッãƒã«ã¯ãƒã‚°ãŒã‚ã‚Šã€Ansible ã® Windows ホストã¸ã®æŽ¥ç¶šãŒåœæ¢ã—ã¦ã—ã¾ã„ã¾ã™ã€‚ã“ã‚Œã¯ã€Server 2008 ㌠TLS 1.2 を使用ã™ã‚‹ã‚ˆã†ã«è¨å®šã§ããªã„ã“ã¨ã‚’æ„味ã—ã¾ã™ã€‚Server 2008 R2 ã¨Windows 7 ã¯ã“ã®å•é¡Œã®å½±éŸ¿ã‚’å—ã‘ãšã€TLS 1.2 を使用ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:765 -msgid "To verify what protocol the Windows host supports, you can run the following command on the Ansible controller::" +#: ../../rst/user_guide/windows_winrm.rst:783 +msgid "To verify what protocol the Windows host supports, you can run the following command on the Ansible controller:" msgstr "Windows ホストãŒå¯¾å¿œã—ã¦ã„るプãƒãƒˆã‚³ãƒ«ã‚’確èªã™ã‚‹ã«ã¯ã€Ansible コントãƒãƒ¼ãƒ©ãƒ¼ã§ä»¥ä¸‹ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:770 -msgid "The output will contain information about the TLS session and the ``Protocol`` line will display the version that was negotiated::" +#: ../../rst/user_guide/windows_winrm.rst:790 +msgid "The output will contain information about the TLS session and the ``Protocol`` line will display the version that was negotiated:" msgstr "出力ã«ã¯ TLS セッションã«é–¢ã™ã‚‹æƒ…å ±ãŒå«ã¾ã‚Œã€``Protocol`` è¡Œã«ã¯ãƒã‚´ã‚·ã‚¨ãƒ¼ãƒˆã•ã‚ŒãŸãƒãƒ¼ã‚¸ãƒ§ãƒ³ãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:806 +#: ../../rst/user_guide/windows_winrm.rst:828 msgid "If the host is returning ``TLSv1`` then it should be configured so that TLS v1.2 is enable. You can do this by running the following PowerShell script:" msgstr "ホスト㌠``TLSv1`` ã‚’è¿”ã™å ´åˆã¯ã€TLS v1.2 ãŒæœ‰åŠ¹ã«ãªã‚‹ã‚ˆã†ã«è¨å®šã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã¯ã€æ¬¡ã® PowerShell スクリプトを実行ã™ã‚‹ã“ã¨ã§è¡Œã†ã“ã¨ãŒã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:831 +#: ../../rst/user_guide/windows_winrm.rst:853 msgid "The below Ansible tasks can also be used to enable TLS v1.2:" msgstr "以下㮠Ansible タスクを使用ã—㦠TLS v1.2 を有効ã«ã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:861 +#: ../../rst/user_guide/windows_winrm.rst:883 msgid "There are other ways to configure the TLS protocols as well as the cipher suites that are offered by the Windows host. One tool that can give you a GUI to manage these settings is `IIS Crypto <https://www.nartac.com/Products/IISCrypto/>`_ from Nartac Software." msgstr "TLS プãƒãƒˆã‚³ãƒ«ã‚„ã€Windows ホストãŒæä¾›ã™ã‚‹æš—å·ã‚¹ã‚¤ãƒ¼ãƒˆã‚’è¨å®šã™ã‚‹æ–¹æ³•ã¯ä»–ã«ã‚‚ã‚ã‚Šã¾ã™ã€‚ã“れらã®è¨å®šã‚’管ç†ã™ã‚‹ãŸã‚ã® GUI ã‚’æä¾›ã™ã‚‹ãƒ„ールã¨ã—ã¦ã€Nartac Software 社㮠`IIS Crypto <https://www.nartac.com/Products/IISCrypto/>`_ ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:868 +#: ../../rst/user_guide/windows_winrm.rst:890 msgid "Due to the design of the WinRM protocol , there are a few limitations when using WinRM that can cause issues when creating playbooks for Ansible. These include:" msgstr "WinRM プãƒãƒˆã‚³ãƒ«ã®è¨è¨ˆä¸Šã€WinRM を使用ã™ã‚‹éš›ã«ã¯ã„ãã¤ã‹ã®åˆ¶é™ãŒã‚ã‚Šã€Ansible ã® Playbook を作æˆã™ã‚‹éš›ã«å•é¡Œã¨ãªã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã«ã¯æ¬¡ã®ã‚ˆã†ãªã‚‚ã®ãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:872 +#: ../../rst/user_guide/windows_winrm.rst:894 msgid "Credentials are not delegated for most authentication types, which causes authentication errors when accessing network resources or installing certain programs." msgstr "ã»ã¨ã‚“ã©ã®èªè¨¼ã‚¿ã‚¤ãƒ—ã§èªè¨¼æƒ…å ±ãŒå§”è²ã•ã‚Œã¦ã„ãªã„ãŸã‚ã€ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒªã‚½ãƒ¼ã‚¹ã¸ã®ã‚¢ã‚¯ã‚»ã‚¹ã‚„特定ã®ãƒ—ãƒã‚°ãƒ©ãƒ ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«æ™‚ã«èªè¨¼ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿã™ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã—ãŸã€‚" -#: ../../rst/user_guide/windows_winrm.rst:876 +#: ../../rst/user_guide/windows_winrm.rst:898 msgid "Many calls to the Windows Update API are blocked when running over WinRM." msgstr "WinRM 経由ã§å®Ÿè¡Œã™ã‚‹ã¨ã€Windows Update API ã¸ã®å¤šãã®å‘¼ã³å‡ºã—ãŒãƒ–ãƒãƒƒã‚¯ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:878 +#: ../../rst/user_guide/windows_winrm.rst:900 msgid "Some programs fail to install with WinRM due to no credential delegation or because they access forbidden Windows API like WUA over WinRM." msgstr "èªè¨¼æƒ…å ±ã®å§”è²ã‚„ã€WUA over WinRM ãªã©ã®ç¦æ¢ã•ã‚Œã¦ã„ã‚‹ Windows API ã¸ã®ã‚¢ã‚¯ã‚»ã‚¹ã«ã‚ˆã‚Šã€ä¸€éƒ¨ã®ãƒ—ãƒã‚°ãƒ©ãƒ 㯠WinRM ã§ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ããªã„å ´åˆãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:881 +#: ../../rst/user_guide/windows_winrm.rst:903 msgid "Commands under WinRM are done under a non-interactive session, which can prevent certain commands or executables from running." msgstr "WinRM ã®ã‚³ãƒžãƒ³ãƒ‰ã¯éžå¯¾è©±åž‹ã‚»ãƒƒã‚·ãƒ§ãƒ³ã§å®Ÿè¡Œã•ã‚Œã‚‹ãŸã‚ã€ç‰¹å®šã®ã‚³ãƒžãƒ³ãƒ‰ã‚„実行ファイルãŒå®Ÿè¡Œã§ããªã„å ´åˆãŒã‚ã‚Šã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:884 +#: ../../rst/user_guide/windows_winrm.rst:906 msgid "You cannot run a process that interacts with ``DPAPI``, which is used by some installers (like Microsoft SQL Server)." msgstr "一部ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ©ãƒ¼ (Microsoft SQL Server ãªã©) ãŒä½¿ç”¨ã™ã‚‹ ``DPAPI`` ã¨å¯¾è©±ã™ã‚‹ãƒ—ãƒã‚»ã‚¹ã‚’実行ã™ã‚‹ã“ã¨ã¯ã§ãã¾ã›ã‚“。" -#: ../../rst/user_guide/windows_winrm.rst:887 +#: ../../rst/user_guide/windows_winrm.rst:909 msgid "Some of these limitations can be mitigated by doing one of the following:" msgstr "ã“ã®åˆ¶é™ã®ä¸€éƒ¨ã¯ã€ä»¥ä¸‹ã®ã„ãšã‚Œã‹ã‚’実行ã—ã¦è»½æ¸›ã§ãã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:889 +#: ../../rst/user_guide/windows_winrm.rst:911 msgid "Set ``ansible_winrm_transport`` to ``credssp`` or ``kerberos`` (with ``ansible_winrm_kerberos_delegation=true``) to bypass the double hop issue and access network resources" msgstr "ダブルホップå•é¡Œã‚’回é¿ã—ã¦ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒªã‚½ãƒ¼ã‚¹ã«ã‚¢ã‚¯ã‚»ã‚¹ã™ã‚‹ãŸã‚ã«ã€``ansible_winrm_transport`` ã‚’ ``credssp`` ã¾ãŸã¯ ``kerberos`` (``ansible_winrm_kerberos_delegation=true`` を使用) ã«è¨å®šã—ã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:893 +#: ../../rst/user_guide/windows_winrm.rst:915 msgid "Use ``become`` to bypass all WinRM restrictions and run a command as it would locally. Unlike using an authentication transport like ``credssp``, this will also remove the non-interactive restriction and API restrictions like WUA and DPAPI" msgstr "``become`` を使用ã™ã‚‹ã¨ã€ã™ã¹ã¦ã® WinRM 制é™ã‚’回é¿ã—ã¦ã€ãƒãƒ¼ã‚«ãƒ«ã¨åŒæ§˜ã«ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã§ãã¾ã™ã€‚``credssp`` ã®ã‚ˆã†ãªèªè¨¼ãƒˆãƒ©ãƒ³ã‚¹ãƒãƒ¼ãƒˆã‚’使用ã™ã‚‹å ´åˆã¨ã¯ç•°ãªã‚Šã€éžå¯¾è©±åž‹ã®åˆ¶é™ã‚„ã€WUA ã‚„ DPAPI ãªã©ã® API ã®åˆ¶é™ã‚‚解除ã•ã‚Œã¾ã™ã€‚" -#: ../../rst/user_guide/windows_winrm.rst:898 +#: ../../rst/user_guide/windows_winrm.rst:920 msgid "Use a scheduled task to run a command which can be created with the ``win_scheduled_task`` module. Like ``become``, this bypasses all WinRM restrictions but can only run a command and not modules." msgstr "``win_scheduled_task`` モジュールã§ä½œæˆã•ã‚Œã‚‹ã‚³ãƒžãƒ³ãƒ‰ã‚’実行ã™ã‚‹ãŸã‚ã«ã€ã‚¹ã‚±ã‚¸ãƒ¥ãƒ¼ãƒ«ã•ã‚ŒãŸã‚¿ã‚¹ã‚¯ã‚’使用ã—ã¾ã™ã€‚``become`` ã¨åŒæ§˜ã«ã€WinRM ã®åˆ¶é™ã‚’ã™ã¹ã¦å›žé¿ã—ã¾ã™ãŒã€å®Ÿè¡Œã§ãã‚‹ã®ã¯ã‚³ãƒžãƒ³ãƒ‰ã®ã¿ã§ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¯å®Ÿè¡Œã§ãã¾ã›ã‚“。" +#~ msgid "You can test the OpenStack dynamic inventory script manually to confirm it is working as expected::" +#~ msgstr "OpenStack ã®å‹•çš„インベントリースクリプトを手動ã§ãƒ†ã‚¹ãƒˆã—ã¦ã€æƒ³å®šã©ãŠã‚Šã«æ©Ÿèƒ½ã—ã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¾ã™ã€‚" + +#~ msgid "or::" +#~ msgstr "ã¾ãŸã¯::" + diff --git a/docs/docsite/rst/reference_appendices/automationhub.rst b/docs/docsite/rst/reference_appendices/automationhub.rst index dd70b98f..5ebedb5c 100644 --- a/docs/docsite/rst/reference_appendices/automationhub.rst +++ b/docs/docsite/rst/reference_appendices/automationhub.rst @@ -3,6 +3,10 @@ Ansible Automation Hub ====================== +.. important:: + + Red Hat Ansible Automation Platform will soon be available on Microsoft Azure. `Sign up to preview the experience <https://www.redhat.com/en/engage/ansible-microsoft-azure-e-202110220735>`_. + `Ansible Automation Hub <https://www.ansible.com/products/automation-hub>`_ is the official location to discover and download supported :ref:`collections <collections>`, included as part of an Ansible Automation Platform subscription. These content collections contain modules, plugins, roles, and playbooks in a downloadable package. Ansible Automation Hub gives you direct access to trusted content collections from Red Hat and Certified Partners. You can find content by topic or Ansible Partner organizations. diff --git a/docs/docsite/rst/reference_appendices/tower.rst b/docs/docsite/rst/reference_appendices/tower.rst index c92506b8..62c6afa3 100644 --- a/docs/docsite/rst/reference_appendices/tower.rst +++ b/docs/docsite/rst/reference_appendices/tower.rst @@ -3,6 +3,10 @@ Red Hat Ansible Automation Platform =================================== +.. important:: + + Red Hat Ansible Automation Platform will soon be available on Microsoft Azure. `Sign up to preview the experience <https://www.redhat.com/en/engage/ansible-microsoft-azure-e-202110220735>`_. + `Red Hat Ansible Automation Platform <https://www.ansible.com/products/automation-platform>`_ (RHAAP) is an integrated solution for operationalizing Ansible across your team, organization, and enterprise. The platform includes a controller with a web console and REST API, analytics, execution environments, and much more. RHAAP gives you role-based access control, including control over the use of securely stored credentials for SSH and other services. You can sync your inventory with a wide variety of cloud sources, and powerful multi-playbook workflows allow you to model complex processes. diff --git a/docs/docsite/rst/scenario_guides/guide_aci.rst b/docs/docsite/rst/scenario_guides/guide_aci.rst index 5b194174..99429bd9 100644 --- a/docs/docsite/rst/scenario_guides/guide_aci.rst +++ b/docs/docsite/rst/scenario_guides/guide_aci.rst @@ -599,7 +599,7 @@ The following error messages may occur and this section can help you understand APIC Error 801: property descr of uni/tn-TENANT/ap-AP failed validation for value 'A "legacy" network' - Some values in the APIC have strict format-rules to comply to, and the internal APIC validation check for the provided value failed. In the above case, the ``description`` parameter (internally known as ``descr``) only accepts values conforming to `Regex: [a-zA-Z0-9\\!#$%()*,-./:;@ _{|}~?&+]+ <https://pubhub-prod.s3.amazonaws.com/media/apic-mim-ref/docs/MO-fvAp.html#descr>`_, in general it must not include quotes or square brackets. + Some values in the APIC have strict format-rules to comply to, and the internal APIC validation check for the provided value failed. In the above case, the ``description`` parameter (internally known as ``descr``) only accepts values conforming to Regex: ``[a-zA-Z0-9\\!#$%()*,-./:;@ _{|}~?&+]+``, in general it must not include quotes or square brackets. .. _aci_guide_known_issues: diff --git a/docs/docsite/rst/scenario_guides/guide_azure.rst b/docs/docsite/rst/scenario_guides/guide_azure.rst index 2e730f7b..548ee36c 100644 --- a/docs/docsite/rst/scenario_guides/guide_azure.rst +++ b/docs/docsite/rst/scenario_guides/guide_azure.rst @@ -1,6 +1,10 @@ Microsoft Azure Guide ===================== +.. important:: + + Red Hat Ansible Automation Platform will soon be available on Microsoft Azure. `Sign up to preview the experience <https://www.redhat.com/en/engage/ansible-microsoft-azure-e-202110220735>`_. + Ansible includes a suite of modules for interacting with Azure Resource Manager, giving you the tools to easily create and orchestrate infrastructure on the Microsoft Azure Cloud. diff --git a/docs/docsite/rst/shared_snippets/installing_collections_file.rst b/docs/docsite/rst/shared_snippets/installing_collections_file.rst new file mode 100644 index 00000000..60eccab4 --- /dev/null +++ b/docs/docsite/rst/shared_snippets/installing_collections_file.rst @@ -0,0 +1,24 @@ +Ansible can also install from a source directory in several ways: + +.. code-block:: yaml + + collections: + # directory containing the collection + - source: ./my_namespace/my_collection/ + type: dir + + # directory containing a namespace, with collections as subdirectories + - source: ./my_namespace/ + type: subdirs + +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: + +.. code-block:: yaml + + collections: + - source: /tmp/my_namespace-my_collection-1.0.0.tar.gz + type: file + +.. note:: + + 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.
\ No newline at end of file diff --git a/docs/docsite/rst/shared_snippets/installing_multiple_collections.txt b/docs/docsite/rst/shared_snippets/installing_multiple_collections.txt index a1bf0265..db49aa92 100644 --- a/docs/docsite/rst/shared_snippets/installing_multiple_collections.txt +++ b/docs/docsite/rst/shared_snippets/installing_multiple_collections.txt @@ -22,7 +22,7 @@ You can specify four keys for each collection entry: The ``version`` key uses the same range identifier format documented in :ref:`collections_older_version`. -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. +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. 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: diff --git a/docs/docsite/rst/user_guide/collections_using.rst b/docs/docsite/rst/user_guide/collections_using.rst index c0450501..c6719b46 100644 --- a/docs/docsite/rst/user_guide/collections_using.rst +++ b/docs/docsite/rst/user_guide/collections_using.rst @@ -37,11 +37,6 @@ Installing an older version of a collection .. include:: ../shared_snippets/installing_older_collection.txt -Installing a collection from a git repository ---------------------------------------------- - -.. include:: ../shared_snippets/installing_collections_git_repo.txt - .. _collection_requirements_file: Install multiple collections with a requirements file @@ -56,6 +51,15 @@ Downloading a collection for offline use .. include:: ../shared_snippets/download_tarball_collections.txt +Installing a collection from source files +----------------------------------------- + +.. include:: ../shared_snippets/installing_collections_file.rst + +Installing a collection from a git repository +--------------------------------------------- + +.. include:: ../shared_snippets/installing_collections_git_repo.txt .. _galaxy_server_config: diff --git a/docs/docsite/rst/user_guide/playbooks_filters.rst b/docs/docsite/rst/user_guide/playbooks_filters.rst index 9116172b..80961d46 100644 --- a/docs/docsite/rst/user_guide/playbooks_filters.rst +++ b/docs/docsite/rst/user_guide/playbooks_filters.rst @@ -1294,8 +1294,8 @@ This allows for dynamic generation of VLAN lists on a Cisco IOS tagged interface .. _hash_filters: -Encrypting and checksumming strings and passwords -================================================= +Hashing and encrypting strings and passwords +============================================== .. versionadded:: 1.9 diff --git a/docs/docsite/rst/user_guide/playbooks_reuse_roles.rst b/docs/docsite/rst/user_guide/playbooks_reuse_roles.rst index 2422830b..bc74b210 100644 --- a/docs/docsite/rst/user_guide/playbooks_reuse_roles.rst +++ b/docs/docsite/rst/user_guide/playbooks_reuse_roles.rst @@ -320,7 +320,7 @@ role ``meta/argument_specs.yml`` file. All fields are lower-case. :type: - * The data type of the option. Default is ``str``. + * The data type of the option. See :ref:`Argument spec <argument_spec>` for allowed values for ``type``. Default is ``str``. * If an option is of type ``list``, ``elements`` should be specified. :required: diff --git a/docs/docsite/sphinx_conf/all_conf.py b/docs/docsite/sphinx_conf/all_conf.py index 2e0460a2..625e0c5f 100644 --- a/docs/docsite/sphinx_conf/all_conf.py +++ b/docs/docsite/sphinx_conf/all_conf.py @@ -287,6 +287,7 @@ autoclass_content = 'both' intersphinx_mapping = {'python': ('https://docs.python.org/2/', (None, '../python2.inv')), 'python3': ('https://docs.python.org/3/', (None, '../python3.inv')), 'jinja2': ('http://jinja.palletsprojects.com/', (None, '../jinja2.inv')), + 'ansible_5': ('https://docs.ansible.com/ansible/5/', (None, '../ansible_5.inv')), 'ansible_4': ('https://docs.ansible.com/ansible/4/', (None, '../ansible_4.inv')), 'ansible_3': ('https://docs.ansible.com/ansible/3/', (None, '../ansible_3.inv')), 'ansible_2_10': ('https://docs.ansible.com/ansible/2.10/', (None, '../ansible_2_10.inv')), diff --git a/docs/docsite/sphinx_conf/ansible_conf.py b/docs/docsite/sphinx_conf/ansible_conf.py index 0a9f9a9f..44102cc9 100644 --- a/docs/docsite/sphinx_conf/ansible_conf.py +++ b/docs/docsite/sphinx_conf/ansible_conf.py @@ -32,7 +32,7 @@ sys.path.insert(0, os.path.join('ansible', 'lib')) # the repository version needs to be the one that is loaded: sys.path.insert(0, os.path.abspath(os.path.join('..', '..', '..', 'lib'))) -VERSION = 'devel' +VERSION = '5' AUTHOR = 'Ansible, Inc' @@ -163,7 +163,7 @@ html_context = { 'github_root_dir': 'devel/lib/ansible', 'github_cli_version': 'devel/lib/ansible/cli/', 'current_version': version, - 'latest_version': '4', + 'latest_version': '5', # list specifically out of order to make latest work 'available_versions': ('latest', '2.9', 'devel'), } @@ -296,6 +296,7 @@ autoclass_content = 'both' intersphinx_mapping = {'python': ('https://docs.python.org/2/', (None, '../python2.inv')), 'python3': ('https://docs.python.org/3/', (None, '../python3.inv')), 'jinja2': ('http://jinja.palletsprojects.com/', (None, '../jinja2.inv')), + 'ansible_5': ('https://docs.ansible.com/ansible/5/', (None, '../ansible_5.inv')), 'ansible_4': ('https://docs.ansible.com/ansible/4/', (None, '../ansible_4.inv')), 'ansible_3': ('https://docs.ansible.com/ansible/3/', (None, '../ansible_3.inv')), 'ansible_2_10': ('https://docs.ansible.com/ansible/2.10/', (None, '../ansible_2_10.inv')), diff --git a/docs/docsite/sphinx_conf/core_conf.py b/docs/docsite/sphinx_conf/core_conf.py index be90f802..8597d4f5 100644 --- a/docs/docsite/sphinx_conf/core_conf.py +++ b/docs/docsite/sphinx_conf/core_conf.py @@ -32,7 +32,7 @@ sys.path.insert(0, os.path.join('ansible', 'lib')) # the repository version needs to be the one that is loaded: sys.path.insert(0, os.path.abspath(os.path.join('..', '..', '..', 'lib'))) -VERSION = 'devel' +VERSION = '2.12' AUTHOR = 'Ansible, Inc' @@ -173,9 +173,9 @@ html_context = { 'github_root_dir': 'devel/lib/ansible', 'github_cli_version': 'devel/lib/ansible/cli/', 'current_version': version, - 'latest_version': '2.11', + 'latest_version': '2.12', # list specifically out of order to make latest work - 'available_versions': ('2.11', '2.10', 'devel',), + 'available_versions': ('2.12', '2.11', '2.10', 'devel',), } # Add extra CSS styles to the resulting HTML pages @@ -308,6 +308,7 @@ autoclass_content = 'both' intersphinx_mapping = {'python': ('https://docs.python.org/2/', (None, '../python2.inv')), 'python3': ('https://docs.python.org/3/', (None, '../python3.inv')), 'jinja2': ('http://jinja.palletsprojects.com/', (None, '../jinja2.inv')), + 'ansible_5': ('https://docs.ansible.com/ansible/5/', (None, '../ansible_5.inv')), 'ansible_4': ('https://docs.ansible.com/ansible/4/', (None, '../ansible_4.inv')), 'ansible_3': ('https://docs.ansible.com/ansible/3/', (None, '../ansible_3.inv')), 'ansible_2_10': ('https://docs.ansible.com/ansible/2.10/', (None, '../ansible_2_10.inv')), diff --git a/docs/man/man1/ansible-config.1 b/docs/man/man1/ansible-config.1 index b9a2acbf..95a7fcfb 100644 --- a/docs/man/man1/ansible-config.1 +++ b/docs/man/man1/ansible-config.1 @@ -1,6 +1,6 @@ .\" Man page generated from reStructuredText. . -.TH ANSIBLE-CONFIG 1 "" "Ansible 2.12.0" "System administration commands" +.TH ANSIBLE-CONFIG 1 "" "Ansible 2.12.3" "System administration commands" .SH NAME ansible-config \- View ansible configuration. . diff --git a/docs/man/man1/ansible-console.1 b/docs/man/man1/ansible-console.1 index df8763fc..a66e8fa1 100644 --- a/docs/man/man1/ansible-console.1 +++ b/docs/man/man1/ansible-console.1 @@ -1,6 +1,6 @@ .\" Man page generated from reStructuredText. . -.TH ANSIBLE-CONSOLE 1 "" "Ansible 2.12.0" "System administration commands" +.TH ANSIBLE-CONSOLE 1 "" "Ansible 2.12.3" "System administration commands" .SH NAME ansible-console \- REPL console for executing Ansible tasks. . diff --git a/docs/man/man1/ansible-doc.1 b/docs/man/man1/ansible-doc.1 index 86d35a12..5142e598 100644 --- a/docs/man/man1/ansible-doc.1 +++ b/docs/man/man1/ansible-doc.1 @@ -1,6 +1,6 @@ .\" Man page generated from reStructuredText. . -.TH ANSIBLE-DOC 1 "" "Ansible 2.12.0" "System administration commands" +.TH ANSIBLE-DOC 1 "" "Ansible 2.12.3" "System administration commands" .SH NAME ansible-doc \- plugin documentation tool . diff --git a/docs/man/man1/ansible-galaxy.1 b/docs/man/man1/ansible-galaxy.1 index 1596a4c1..0b4c0f0e 100644 --- a/docs/man/man1/ansible-galaxy.1 +++ b/docs/man/man1/ansible-galaxy.1 @@ -1,6 +1,6 @@ .\" Man page generated from reStructuredText. . -.TH ANSIBLE-GALAXY 1 "" "Ansible 2.12.0" "System administration commands" +.TH ANSIBLE-GALAXY 1 "" "Ansible 2.12.3" "System administration commands" .SH NAME ansible-galaxy \- Perform various Role and Collection related operations. . diff --git a/docs/man/man1/ansible-inventory.1 b/docs/man/man1/ansible-inventory.1 index 8d91b617..a6724b4f 100644 --- a/docs/man/man1/ansible-inventory.1 +++ b/docs/man/man1/ansible-inventory.1 @@ -1,6 +1,6 @@ .\" Man page generated from reStructuredText. . -.TH ANSIBLE-INVENTORY 1 "" "Ansible 2.12.0" "System administration commands" +.TH ANSIBLE-INVENTORY 1 "" "Ansible 2.12.3" "System administration commands" .SH NAME ansible-inventory \- None . diff --git a/docs/man/man1/ansible-playbook.1 b/docs/man/man1/ansible-playbook.1 index d3457d31..1521cc43 100644 --- a/docs/man/man1/ansible-playbook.1 +++ b/docs/man/man1/ansible-playbook.1 @@ -1,6 +1,6 @@ .\" Man page generated from reStructuredText. . -.TH ANSIBLE-PLAYBOOK 1 "" "Ansible 2.12.0" "System administration commands" +.TH ANSIBLE-PLAYBOOK 1 "" "Ansible 2.12.3" "System administration commands" .SH NAME ansible-playbook \- Runs Ansible playbooks, executing the defined tasks on the targeted hosts. . diff --git a/docs/man/man1/ansible-pull.1 b/docs/man/man1/ansible-pull.1 index 63ec854e..5eb87f23 100644 --- a/docs/man/man1/ansible-pull.1 +++ b/docs/man/man1/ansible-pull.1 @@ -1,6 +1,6 @@ .\" Man page generated from reStructuredText. . -.TH ANSIBLE-PULL 1 "" "Ansible 2.12.0" "System administration commands" +.TH ANSIBLE-PULL 1 "" "Ansible 2.12.3" "System administration commands" .SH NAME ansible-pull \- pulls playbooks from a VCS repo and executes them for the local host . diff --git a/docs/man/man1/ansible-vault.1 b/docs/man/man1/ansible-vault.1 index ec72ea14..431b1516 100644 --- a/docs/man/man1/ansible-vault.1 +++ b/docs/man/man1/ansible-vault.1 @@ -1,6 +1,6 @@ .\" Man page generated from reStructuredText. . -.TH ANSIBLE-VAULT 1 "" "Ansible 2.12.0" "System administration commands" +.TH ANSIBLE-VAULT 1 "" "Ansible 2.12.3" "System administration commands" .SH NAME ansible-vault \- encryption/decryption utility for Ansible data files . diff --git a/docs/man/man1/ansible.1 b/docs/man/man1/ansible.1 index bb06ead0..6ee36c5a 100644 --- a/docs/man/man1/ansible.1 +++ b/docs/man/man1/ansible.1 @@ -1,6 +1,6 @@ .\" Man page generated from reStructuredText. . -.TH ANSIBLE 1 "" "Ansible 2.12.0" "System administration commands" +.TH ANSIBLE 1 "" "Ansible 2.12.3" "System administration commands" .SH NAME ansible \- Define and run a single task 'playbook' against a set of hosts . diff --git a/lib/ansible/cli/__init__.py b/lib/ansible/cli/__init__.py index 0ffafc5a..6075b0a1 100644 --- a/lib/ansible/cli/__init__.py +++ b/lib/ansible/cli/__init__.py @@ -21,6 +21,7 @@ from ansible.errors import AnsibleError from ansible.inventory.manager import InventoryManager from ansible.module_utils.six import with_metaclass, string_types, PY3 from ansible.module_utils._text import to_bytes, to_text +from ansible.module_utils.common.file import is_executable from ansible.parsing.dataloader import DataLoader from ansible.parsing.vault import PromptVaultSecret, get_file_vault_secret from ansible.plugins.loader import add_all_plugin_dirs @@ -513,7 +514,7 @@ class CLI(with_metaclass(ABCMeta, object)): elif not os.path.exists(b_pwd_file): raise AnsibleError("The password file %s was not found" % pwd_file) - elif os.path.is_executable(b_pwd_file): + elif is_executable(b_pwd_file): display.vvvv(u'The password file %s is a script.' % to_text(pwd_file)) cmd = [b_pwd_file] diff --git a/lib/ansible/cli/config.py b/lib/ansible/cli/config.py index 328b3c11..0fff3744 100644 --- a/lib/ansible/cli/config.py +++ b/lib/ansible/cli/config.py @@ -365,18 +365,23 @@ class ConfigCLI(CLI): text = [] for setting in sorted(config): + changed = False if isinstance(config[setting], Setting): + # proceed normally if config[setting].origin == 'default': color = 'green' elif config[setting].origin == 'REQUIRED': + # should include '_terms', '_input', etc color = 'red' else: color = 'yellow' + changed = True msg = "%s(%s) = %s" % (setting, config[setting].origin, config[setting].value) else: color = 'green' msg = "%s(%s) = %s" % (setting, 'default', config[setting].get('default')) - if not context.CLIARGS['only_changed'] or color == 'yellow': + + if not context.CLIARGS['only_changed'] or changed: text.append(stringc(msg, color)) return text @@ -440,6 +445,11 @@ class ConfigCLI(CLI): o = 'REQUIRED' else: raise e + + if v is None and o is None: + # not all cases will be error + o = 'REQUIRED' + config_entries[finalname][setting] = Setting(setting, v, o, None) # pretty please! diff --git a/lib/ansible/cli/galaxy.py b/lib/ansible/cli/galaxy.py index cc9a813e..5d9080e9 100644 --- a/lib/ansible/cli/galaxy.py +++ b/lib/ansible/cli/galaxy.py @@ -551,6 +551,7 @@ class GalaxyCLI(CLI): self.api_servers.append(GalaxyAPI( self.galaxy, 'cmd_arg', cmd_server, token=cmd_token, priority=len(config_servers) + 1, + validate_certs=validate_certs_fallback, **galaxy_options )) else: @@ -561,6 +562,7 @@ class GalaxyCLI(CLI): self.api_servers.append(GalaxyAPI( self.galaxy, 'default', C.GALAXY_SERVER, token=cmd_token, priority=0, + validate_certs=validate_certs_fallback, **galaxy_options )) diff --git a/lib/ansible/config/base.yml b/lib/ansible/config/base.yml index 35a6ad2f..984ff448 100644 --- a/lib/ansible/config/base.yml +++ b/lib/ansible/config/base.yml @@ -35,7 +35,7 @@ ANSIBLE_COW_SELECTION: ANSIBLE_COW_ACCEPTLIST: name: Cowsay filter acceptance list default: ['bud-frogs', 'bunny', 'cheese', 'daemon', 'default', 'dragon', 'elephant-in-snake', 'elephant', 'eyes', 'hellokitty', 'kitty', 'luke-koala', 'meow', 'milk', 'moofasa', 'moose', 'ren', 'sheep', 'small', 'stegosaurus', 'stimpy', 'supermilker', 'three-eyes', 'turkey', 'turtle', 'tux', 'udder', 'vader-koala', 'vader', 'www'] - description: White list of cowsay templates that are 'safe' to use, set to empty list if you want to enable all installed templates. + description: Accept list of cowsay templates that are 'safe' to use, set to empty list if you want to enable all installed templates. env: - name: ANSIBLE_COW_WHITELIST deprecated: @@ -1920,7 +1920,7 @@ USE_PERSISTENT_CONNECTIONS: VARIABLE_PLUGINS_ENABLED: name: Vars plugin enabled list default: ['host_group_vars'] - description: Whitelist for variable plugins that require it. + description: Accept list for variable plugins that require it. env: [{name: ANSIBLE_VARS_ENABLED}] ini: - {key: vars_plugins_enabled, section: defaults} diff --git a/lib/ansible/executor/playbook_executor.py b/lib/ansible/executor/playbook_executor.py index e0d3a645..e8b2a3dc 100644 --- a/lib/ansible/executor/playbook_executor.py +++ b/lib/ansible/executor/playbook_executor.py @@ -190,7 +190,6 @@ class PlaybookExecutor: result = self._tqm.run(play=play) except AnsibleEndPlay as e: result = e.result - break_play = True break # break the play if the result equals the special return code diff --git a/lib/ansible/executor/task_executor.py b/lib/ansible/executor/task_executor.py index 78cf09bb..34e04afb 100644 --- a/lib/ansible/executor/task_executor.py +++ b/lib/ansible/executor/task_executor.py @@ -480,8 +480,19 @@ class TaskExecutor: raise self._loop_eval_error # pylint: disable=raising-bad-type # if we ran into an error while setting up the PlayContext, raise it now, unless is known issue with delegation - if context_validation_error is not None and not (self._task.delegate_to and isinstance(context_validation_error, AnsibleUndefinedVariable)): - raise context_validation_error # pylint: disable=raising-bad-type + # and undefined vars (correct values are in cvars later on and connection plugins, if still error, blows up there) + if context_validation_error is not None: + raiseit = True + if self._task.delegate_to: + if isinstance(context_validation_error, AnsibleUndefinedVariable): + raiseit = False + elif isinstance(context_validation_error, AnsibleParserError): + # parser error, might be cause by undef too + orig_exc = getattr(context_validation_error, 'orig_exc', None) + if isinstance(orig_exc, AnsibleUndefinedVariable): + raiseit = False + if raiseit: + raise context_validation_error # pylint: disable=raising-bad-type # if this task is a TaskInclude, we just return now with a success code so the # main thread can expand the task list for the given host @@ -502,7 +513,7 @@ class TaskExecutor: # Now we do final validation on the task, which sets all fields to their final values. try: self._task.post_validate(templar=templar) - except AnsibleError: + except AnsibleError as e: raise except Exception: return dict(changed=False, failed=True, _ansible_no_log=self._play_context.no_log, exception=to_text(traceback.format_exc())) @@ -622,14 +633,14 @@ class TaskExecutor: self._final_q.send_callback( 'v2_runner_on_async_failed', TaskResult(self._host.name, - self._task, # We send the full task here, because the controller knows nothing about it, the TE created it + self._task._uuid, result, task_fields=self._task.dump_attrs())) else: self._final_q.send_callback( 'v2_runner_on_async_ok', TaskResult(self._host.name, - self._task, # We send the full task here, because the controller knows nothing about it, the TE created it + self._task._uuid, result, task_fields=self._task.dump_attrs())) @@ -655,7 +666,13 @@ class TaskExecutor: if 'ansible_facts' in result and self._task.action not in C._ACTION_DEBUG: if self._task.action in C._ACTION_WITH_CLEAN_FACTS: - vars_copy.update(result['ansible_facts']) + if self._task.delegate_to and self._task.delegate_facts: + if '_ansible_delegated_vars' in vars_copy: + vars_copy['_ansible_delegated_vars'].update(result['ansible_facts']) + else: + vars_copy['_ansible_delegated_vars'] = result['ansible_facts'] + else: + vars_copy.update(result['ansible_facts']) else: # TODO: cleaning of facts should eventually become part of taskresults instead of vars af = wrap_var(result['ansible_facts']) @@ -786,7 +803,7 @@ class TaskExecutor: # that (with a sleep for "poll" seconds between each retry) until the # async time limit is exceeded. - async_task = Task().load(dict(action='async_status jid=%s' % async_jid, environment=self._task.environment)) + async_task = Task.load(dict(action='async_status', args={'jid': async_jid}, environment=self._task.environment)) # FIXME: this is no longer the case, normal takes care of all, see if this can just be generalized # Because this is an async task, the action handler is async. However, @@ -838,9 +855,9 @@ class TaskExecutor: 'v2_runner_on_async_poll', TaskResult( self._host.name, - async_task, # We send the full task here, because the controller knows nothing about it, the TE created it + async_task._uuid, async_result, - task_fields=self._task.dump_attrs(), + task_fields=async_task.dump_attrs(), ), ) @@ -852,7 +869,7 @@ class TaskExecutor: else: # If the async task finished, automatically cleanup the temporary # status file left behind. - cleanup_task = Task().load( + cleanup_task = Task.load( { 'async_status': { 'jid': async_jid, diff --git a/lib/ansible/galaxy/collection/__init__.py b/lib/ansible/galaxy/collection/__init__.py index 9e3454e6..436436e6 100644 --- a/lib/ansible/galaxy/collection/__init__.py +++ b/lib/ansible/galaxy/collection/__init__.py @@ -791,6 +791,8 @@ def _build_files_manifest(b_collection_path, namespace, name, ignore_patterns): # We always ignore .pyc and .retry files as well as some well known version control directories. The ignore # patterns can be extended by the build_ignore key in galaxy.yml b_ignore_patterns = [ + b'MANIFEST.json', + b'FILES.json', b'galaxy.yml', b'galaxy.yaml', b'.git', diff --git a/lib/ansible/inventory/manager.py b/lib/ansible/inventory/manager.py index aabc75cc..53ddd98f 100644 --- a/lib/ansible/inventory/manager.py +++ b/lib/ansible/inventory/manager.py @@ -208,7 +208,7 @@ class InventoryManager(object): display.warning('Failed to load inventory plugin, skipping %s' % name) if not plugins: - raise AnsibleError("No inventory plugins available to generate inventory, make sure you have at least one whitelisted.") + raise AnsibleError("No inventory plugins available to generate inventory, make sure you have at least one enabled.") return plugins diff --git a/lib/ansible/keyword_desc.yml b/lib/ansible/keyword_desc.yml index f0e076c5..1e8d844a 100644 --- a/lib/ansible/keyword_desc.yml +++ b/lib/ansible/keyword_desc.yml @@ -41,7 +41,7 @@ ignore_errors: Boolean that allows you to ignore task failures and continue with ignore_unreachable: Boolean that allows you to ignore task failures due to an unreachable host and continue with the play. This does not affect other task errors (see :term:`ignore_errors`) but is useful for groups of volatile/ephemeral hosts. loop: "Takes a list for the task to iterate over, saving each list element into the ``item`` variable (configurable via loop_control)" loop_control: Several keys here allow you to modify/set loop behaviour in a task. See :ref:`loop_control`. -max_fail_percentage: can be used to abort the run after a given percentage of hosts in the current batch has failed. This only wokrs on linear or linear derived strategies. +max_fail_percentage: can be used to abort the run after a given percentage of hosts in the current batch has failed. This only works on linear or linear derived strategies. module_defaults: Specifies default parameter values for modules. name: "Identifier. Can be used for documentation, or in tasks/handlers." no_log: Boolean that controls information disclosure. diff --git a/lib/ansible/module_utils/common/parameters.py b/lib/ansible/module_utils/common/parameters.py index 2624bb50..8bba4d5f 100644 --- a/lib/ansible/module_utils/common/parameters.py +++ b/lib/ansible/module_utils/common/parameters.py @@ -724,14 +724,17 @@ def _validate_sub_spec(argument_spec, parameters, prefix='', options_context=Non options_context.append(param) # Make sure we can iterate over the elements - if isinstance(parameters[param], dict): + if not isinstance(parameters[param], Sequence) or isinstance(parameters[param], string_types): elements = [parameters[param]] else: elements = parameters[param] for idx, sub_parameters in enumerate(elements): + no_log_values.update(set_fallbacks(sub_spec, sub_parameters)) + if not isinstance(sub_parameters, dict): errors.append(SubParameterTypeError("value of '%s' must be of type dict or list of dicts" % param)) + continue # Set prefix for warning messages new_prefix = prefix + param @@ -739,8 +742,6 @@ def _validate_sub_spec(argument_spec, parameters, prefix='', options_context=Non new_prefix += '[%d]' % idx new_prefix += '.' - no_log_values.update(set_fallbacks(sub_spec, sub_parameters)) - alias_warnings = [] alias_deprecations = [] try: diff --git a/lib/ansible/module_utils/facts/virtual/linux.py b/lib/ansible/module_utils/facts/virtual/linux.py index 066cf5e1..31fa0617 100644 --- a/lib/ansible/module_utils/facts/virtual/linux.py +++ b/lib/ansible/module_utils/facts/virtual/linux.py @@ -110,6 +110,16 @@ class LinuxVirtual(Virtual): virtual_facts['virtualization_role'] = 'guest' found_virt = True + # If docker/containerd has a custom cgroup parent, checking /proc/1/cgroup (above) might fail. + # https://docs.docker.com/engine/reference/commandline/dockerd/#default-cgroup-parent + # Fallback to more rudimentary checks. + if os.path.exists('/.dockerenv') or os.path.exists('/.dockerinit'): + guest_tech.add('docker') + if not found_virt: + virtual_facts['virtualization_type'] = 'docker' + virtual_facts['virtualization_role'] = 'guest' + found_virt = True + # ensure 'container' guest_tech is appropriately set if guest_tech.intersection(set(['docker', 'lxc', 'podman', 'openvz', 'containerd'])) or systemd_container: guest_tech.add('container') diff --git a/lib/ansible/module_utils/powershell/Ansible.ModuleUtils.LinkUtil.psm1 b/lib/ansible/module_utils/powershell/Ansible.ModuleUtils.LinkUtil.psm1 index 78aa4eac..839dd028 100644 --- a/lib/ansible/module_utils/powershell/Ansible.ModuleUtils.LinkUtil.psm1 +++ b/lib/ansible/module_utils/powershell/Ansible.ModuleUtils.LinkUtil.psm1 @@ -394,6 +394,7 @@ namespace Ansible # FUTURE: find a better way to get the _ansible_remote_tmp variable $original_tmp = $env:TMP + $original_lib = $env:LIB $remote_tmp = $original_tmp $module_params = Get-Variable -Name complex_args -ErrorAction SilentlyContinue @@ -405,8 +406,10 @@ namespace Ansible } $env:TMP = $remote_tmp + $env:LIB = $null Add-Type -TypeDefinition $link_util $env:TMP = $original_tmp + $env:LIB = $original_lib # enable the SeBackupPrivilege if it is disabled $state = Get-AnsiblePrivilege -Name SeBackupPrivilege diff --git a/lib/ansible/modules/add_host.py b/lib/ansible/modules/add_host.py index c6d8a444..9acd0267 100644 --- a/lib/ansible/modules/add_host.py +++ b/lib/ansible/modules/add_host.py @@ -62,7 +62,7 @@ notes: - Since Ansible 2.4, the C(inventory_dir) variable is now set to C(None) instead of the 'global inventory source', because you can now have multiple sources. An example was added that shows how to partially restore the previous behaviour. - Though this module does not change the remote host, we do provide 'changed' status as it can be useful for those trying to track inventory changes. -- The hosts added will not bypass the ``--limit`` from the command line, so both of those need to be in agreement to make them available as play targets. +- The hosts added will not bypass the C(--limit) from the command line, so both of those need to be in agreement to make them available as play targets. They are still available from hostvars and for delegation as a normal part of the inventory. seealso: - module: ansible.builtin.group_by diff --git a/lib/ansible/modules/apt.py b/lib/ansible/modules/apt.py index 5a00a214..2d232e6a 100644 --- a/lib/ansible/modules/apt.py +++ b/lib/ansible/modules/apt.py @@ -170,7 +170,7 @@ options: version_added: "2.4" lock_timeout: description: - - How many seconds will this action wait to aquire a lock on the apt db. + - How many seconds will this action wait to acquire a lock on the apt db. - Sometimes there is a transitory lock and this will retry at least until timeout is hit. type: int default: 60 @@ -196,7 +196,7 @@ notes: - The apt-get commandline supports implicit regex matches here but we do not because it can let typos through easier (If you typo C(foo) as C(fo) apt-get would install packages that have "fo" in their name with a warning and a prompt for the user. Since we don't have warnings and prompts before installing we disallow this.Use an explicit fnmatch pattern if you want wildcarding) - - When used with a `loop:` each package will be processed individually, it is much more efficient to pass the list directly to the `name` option. + - When used with a C(loop:) each package will be processed individually, it is much more efficient to pass the list directly to the I(name) option. ''' EXAMPLES = ''' @@ -298,18 +298,6 @@ EXAMPLES = ''' - name: Remove dependencies that are no longer required apt: autoremove: yes - -# Sometimes apt tasks fail because apt is locked by an autoupdate or by a race condition on a thread. -# To check for a lock file before executing, and keep trying until the lock file is released: -- name: Install packages only when the apt process is not locked - apt: - name: foo - state: present - register: apt_action - retries: 100 - until: apt_action is success or ('Failed to lock apt for exclusive operation' not in apt_action.msg and '/var/lib/dpkg/lock' not in apt_action.msg) - - ''' RETURN = ''' diff --git a/lib/ansible/modules/dnf.py b/lib/ansible/modules/dnf.py index 943f2b2d..75b45183 100644 --- a/lib/ansible/modules/dnf.py +++ b/lib/ansible/modules/dnf.py @@ -132,14 +132,14 @@ options: security: description: - If set to C(yes), and C(state=latest) then only installs updates that have been marked security related. - - Note that, similar to ``dnf upgrade-minimal``, this filter applies to dependencies as well. + - Note that, similar to C(dnf upgrade-minimal), this filter applies to dependencies as well. type: bool default: "no" version_added: "2.7" bugfix: description: - If set to C(yes), and C(state=latest) then only installs updates that have been marked bugfix related. - - Note that, similar to ``dnf upgrade-minimal``, this filter applies to dependencies as well. + - Note that, similar to C(dnf upgrade-minimal), this filter applies to dependencies as well. default: "no" type: bool version_added: "2.7" @@ -255,7 +255,7 @@ attributes: platform: platforms: rhel notes: - - When used with a `loop:` each package will be processed individually, it is much more efficient to pass the list directly to the `name` option. + - When used with a C(loop:) each package will be processed individually, it is much more efficient to pass the list directly to the I(name) option. - Group removal doesn't work if the group was installed with Ansible because upstream dnf's API doesn't properly mark groups as installed, therefore upon removal the module is unable to detect that the group is installed diff --git a/lib/ansible/modules/git.py b/lib/ansible/modules/git.py index efe229f3..ed87088e 100644 --- a/lib/ansible/modules/git.py +++ b/lib/ansible/modules/git.py @@ -95,8 +95,8 @@ options: description: - If C(yes), any modified files in the working repository will be discarded. Prior to 0.7, this was always - 'yes' and could not be disabled. Prior to 1.9, the default was - `yes`. + C(yes) and could not be disabled. Prior to 1.9, the default was + C(yes). type: bool default: 'no' version_added: "0.7" diff --git a/lib/ansible/modules/hostname.py b/lib/ansible/modules/hostname.py index 6ec42eb7..fc908b50 100644 --- a/lib/ansible/modules/hostname.py +++ b/lib/ansible/modules/hostname.py @@ -161,7 +161,8 @@ class Hostname(object): if self.use is not None: strat = globals()['%sStrategy' % STRATS[self.use]] self.strategy = strat(module) - elif self.platform == 'Linux' and ServiceMgrFactCollector.is_systemd_managed(module): + elif platform.system() == 'Linux' and ServiceMgrFactCollector.is_systemd_managed(module): + # This is Linux and systemd is active self.strategy = SystemdStrategy(module) else: self.strategy = self.strategy_class(module) @@ -638,12 +639,6 @@ class DarwinStrategy(BaseStrategy): self.changed = True -class FedoraHostname(Hostname): - platform = 'Linux' - distribution = 'Fedora' - strategy_class = SystemdStrategy - - class SLESHostname(Hostname): platform = 'Linux' distribution = 'Sles' @@ -658,60 +653,6 @@ class SLESHostname(Hostname): strategy_class = UnimplementedStrategy -class OpenSUSEHostname(Hostname): - platform = 'Linux' - distribution = 'Opensuse' - strategy_class = SystemdStrategy - - -class OpenSUSELeapHostname(Hostname): - platform = 'Linux' - distribution = 'Opensuse-leap' - strategy_class = SystemdStrategy - - -class OpenSUSETumbleweedHostname(Hostname): - platform = 'Linux' - distribution = 'Opensuse-tumbleweed' - strategy_class = SystemdStrategy - - -class AsteraHostname(Hostname): - platform = 'Linux' - distribution = '"astralinuxce"' - strategy_class = SystemdStrategy - - -class ArchHostname(Hostname): - platform = 'Linux' - distribution = 'Arch' - strategy_class = SystemdStrategy - - -class ArchARMHostname(Hostname): - platform = 'Linux' - distribution = 'Archarm' - strategy_class = SystemdStrategy - - -class AlmaLinuxHostname(Hostname): - platform = 'Linux' - distribution = 'Almalinux' - strategy_class = SystemdStrategy - - -class ManjaroHostname(Hostname): - platform = 'Linux' - distribution = 'Manjaro' - strategy_class = SystemdStrategy - - -class ManjaroARMHostname(Hostname): - platform = 'Linux' - distribution = 'Manjaro-arm' - strategy_class = SystemdStrategy - - class RHELHostname(Hostname): platform = 'Linux' distribution = 'Redhat' @@ -730,12 +671,6 @@ class AnolisOSHostname(Hostname): strategy_class = RedHatStrategy -class ClearLinuxHostname(Hostname): - platform = 'Linux' - distribution = 'Clear-linux-os' - strategy_class = SystemdStrategy - - class CloudlinuxserverHostname(Hostname): platform = 'Linux' distribution = 'Cloudlinuxserver' @@ -754,18 +689,6 @@ class AlinuxHostname(Hostname): strategy_class = RedHatStrategy -class CoreosHostname(Hostname): - platform = 'Linux' - distribution = 'Coreos' - strategy_class = SystemdStrategy - - -class FlatcarHostname(Hostname): - platform = 'Linux' - distribution = 'Flatcar' - strategy_class = SystemdStrategy - - class ScientificHostname(Hostname): platform = 'Linux' distribution = 'Scientific' @@ -904,18 +827,6 @@ class DarwinHostname(Hostname): strategy_class = DarwinStrategy -class OsmcHostname(Hostname): - platform = 'Linux' - distribution = 'Osmc' - strategy_class = SystemdStrategy - - -class PardusHostname(Hostname): - platform = 'Linux' - distribution = 'Pardus' - strategy_class = SystemdStrategy - - class VoidLinuxHostname(Hostname): platform = 'Linux' distribution = 'Void' @@ -928,16 +839,10 @@ class PopHostname(Hostname): strategy_class = FileStrategy -class RockyHostname(Hostname): - platform = 'Linux' - distribution = 'Rocky' - strategy_class = SystemdStrategy - - -class RedosHostname(Hostname): +class EurolinuxHostname(Hostname): platform = 'Linux' - distribution = 'Redos' - strategy_class = SystemdStrategy + distribution = 'Eurolinux' + strategy_class = RedHatStrategy def main(): diff --git a/lib/ansible/modules/iptables.py b/lib/ansible/modules/iptables.py index a6067e2b..0530fdd6 100644 --- a/lib/ansible/modules/iptables.py +++ b/lib/ansible/modules/iptables.py @@ -33,7 +33,7 @@ attributes: platform: platforms: linux notes: - - This module just deals with individual rules.If you need advanced + - This module just deals with individual rules. If you need advanced chaining of rules the recommended way is to template the iptables restore file. options: @@ -317,9 +317,9 @@ options: limit: description: - Specifies the maximum average number of matches to allow per second. - - The number can specify units explicitly, using `/second', `/minute', - `/hour' or `/day', or parts of them (so `5/second' is the same as - `5/s'). + - The number can specify units explicitly, using C(/second), C(/minute), + C(/hour) or C(/day), or parts of them (so C(5/second) is the same as + C(5/s)). type: str limit_burst: description: diff --git a/lib/ansible/modules/known_hosts.py b/lib/ansible/modules/known_hosts.py index cb7ee2f8..df8a1dc1 100644 --- a/lib/ansible/modules/known_hosts.py +++ b/lib/ansible/modules/known_hosts.py @@ -34,7 +34,7 @@ options: - Specifically, the key should not match the format that is found in an SSH pubkey file, but should rather have the hostname prepended to a line that includes the pubkey, the same way that it would appear in the known_hosts file. The value prepended to the line must also match the value of the name parameter. - - Should be of format `<hostname[,IP]> ssh-rsa <pubkey>`. + - Should be of format C(<hostname[,IP]> ssh-rsa <pubkey>). - For custom SSH port, C(key) needs to specify port as well. See example section. type: str path: diff --git a/lib/ansible/modules/package.py b/lib/ansible/modules/package.py index 0db7821f..e9c177ff 100644 --- a/lib/ansible/modules/package.py +++ b/lib/ansible/modules/package.py @@ -19,8 +19,8 @@ short_description: Generic OS package manager description: - This modules manages packages on a target without specifying a package manager module (like M(ansible.builtin.yum), M(ansible.builtin.apt), ...). It is convenient to use in an heterogeneous environment of machines without having to create a specific task for - each package manager. `package` calls behind the module for the package manager used by the operating system - discovered by the module M(ansible.builtin.setup). If `setup` was not yet run, `package` will run it. + each package manager. C(package) calls behind the module for the package manager used by the operating system + discovered by the module M(ansible.builtin.setup). If C(setup) was not yet run, C(package) will run it. - This module acts as a proxy to the underlying package manager module. While all arguments will be passed to the underlying module, not all modules support the same arguments. This documentation only covers the minimum intersection of module arguments that all packaging modules support. @@ -39,7 +39,7 @@ options: required: true use: description: - - The required package manager module to use (`yum`, `apt`, and so on). The default 'auto' will use existing facts or try to autodetect it. + - The required package manager module to use (C(yum), C(apt), and so on). The default 'auto' will use existing facts or try to autodetect it. - You should only use this field if the automatic selection is not working for some reason. default: auto requirements: @@ -64,7 +64,7 @@ attributes: details: The support depends on the availability for the specific plugin for each platform and if fact gathering is able to detect it platforms: all notes: - - While `package` abstracts package managers to ease dealing with multiple distributions, package name often differs for the same software. + - While C(package) abstracts package managers to ease dealing with multiple distributions, package name often differs for the same software. ''' EXAMPLES = ''' diff --git a/lib/ansible/modules/pip.py b/lib/ansible/modules/pip.py index ce0ea419..f2d9cc1e 100644 --- a/lib/ansible/modules/pip.py +++ b/lib/ansible/modules/pip.py @@ -129,7 +129,7 @@ notes: run the actual pip command, so it can use any pip version you specify with I(executable). By default, it uses the pip version for the Ansible Python interpreter. For example, pip3 on python 3, and pip2 or pip on python 2. - The interpreter used by Ansible - (see :ref:`ansible_python_interpreter<ansible_python_interpreter>`) + (see R(ansible_python_interpreter, ansible_python_interpreter)) requires the setuptools package, regardless of the version of pip set with the I(executable) option. requirements: diff --git a/lib/ansible/modules/service.py b/lib/ansible/modules/service.py index bd105ec1..d13a6f11 100644 --- a/lib/ansible/modules/service.py +++ b/lib/ansible/modules/service.py @@ -23,7 +23,7 @@ description: (such as M(ansible.builtin.systemd) and M(ansible.builtin.sysvinit)). This allows management of a heterogeneous environment of machines without creating a specific task for each service manager. The module to be executed is determined by the I(use) option, which defaults to the - service manager discovered by M(ansible.builtin.setup). If `setup` was not yet run, this module may run it. + service manager discovered by M(ansible.builtin.setup). If C(setup) was not yet run, this module may run it. - For Windows targets, use the M(ansible.windows.win_service) module instead. options: name: diff --git a/lib/ansible/modules/set_fact.py b/lib/ansible/modules/set_fact.py index 8fa73896..f4a0317a 100644 --- a/lib/ansible/modules/set_fact.py +++ b/lib/ansible/modules/set_fact.py @@ -22,7 +22,7 @@ description: options: key_value: description: - - "The C(set_fact) module takes ``key=value`` pairs or ``key: value``(YAML notation) as variables to set in the playbook scope. + - "The C(set_fact) module takes C(key=value) pairs or C(key: value) (YAML notation) as variables to set in the playbook scope. The 'key' is the resulting variable name and the value is, of course, the value of said variable." - You can create multiple variables at once, by supplying multiple pairs, but do NOT mix notations. required: true diff --git a/lib/ansible/modules/stat.py b/lib/ansible/modules/stat.py index 70b8041c..bb242ea8 100644 --- a/lib/ansible/modules/stat.py +++ b/lib/ansible/modules/stat.py @@ -48,8 +48,8 @@ options: description: - Use file magic and return data about the nature of the file. this uses the 'file' utility found on most Linux/Unix systems. - - This will add both `mime_type` and 'charset' fields to the return, if possible. - - In Ansible 2.3 this option changed from 'mime' to 'get_mime' and the default changed to 'Yes'. + - This will add both C(mime_type) and C(charset) fields to the return, if possible. + - In Ansible 2.3 this option changed from I(mime) to I(get_mime) and the default changed to C(yes). type: bool default: yes aliases: [ mime, mime_type, mime-type ] @@ -334,15 +334,15 @@ stat: mimetype: description: file magic data or mime-type returned: success, path exists and user can read stats and - installed python supports it and the `mime` option was true, will - return 'unknown' on error. + installed python supports it and the I(mime) option was true, will + return C(unknown) on error. type: str sample: application/pdf; charset=binary charset: description: file character set or encoding returned: success, path exists and user can read stats and - installed python supports it and the `mime` option was true, will - return 'unknown' on error. + installed python supports it and the I(mime) option was true, will + return C(unknown) on error. type: str sample: us-ascii readable: diff --git a/lib/ansible/modules/systemd.py b/lib/ansible/modules/systemd.py index d679e9a9..e94fc660 100644 --- a/lib/ansible/modules/systemd.py +++ b/lib/ansible/modules/systemd.py @@ -64,7 +64,7 @@ options: - "For systemd to work with 'user', the executing user must have its own instance of dbus started and accessible (systemd requirement)." - "The user dbus process is normally started during normal login, but not during the run of Ansible tasks. Otherwise you will probably get a 'Failed to connect to bus: no such file or directory' error." - - The user must have access, normally given via setting the ``XDG_RUNTIME_DIR`` variable, see example below. + - The user must have access, normally given via setting the C(XDG_RUNTIME_DIR) variable, see example below. type: str choices: [ system, user, global ] @@ -89,7 +89,7 @@ notes: - Since 2.4, one of the following options is required C(state), C(enabled), C(masked), C(daemon_reload), (C(daemon_reexec) since 2.8), and all except C(daemon_reload) and (C(daemon_reexec) since 2.8) also require C(name). - Before 2.4 you always required C(name). - - Globs are not supported in name, i.e ``postgres*.service``. + - Globs are not supported in name, i.e C(postgres*.service). - The service names might vary by specific OS/distribution requirements: - A system managed by systemd. @@ -148,7 +148,7 @@ EXAMPLES = ''' RETURN = ''' status: - description: A dictionary with the key=value pairs returned from `systemctl show`. + description: A dictionary with the key=value pairs returned from C(systemctl show). returned: success type: complex sample: { diff --git a/lib/ansible/modules/unarchive.py b/lib/ansible/modules/unarchive.py index e4c40a93..0b265943 100644 --- a/lib/ansible/modules/unarchive.py +++ b/lib/ansible/modules/unarchive.py @@ -386,7 +386,7 @@ class ZipArchive(object): exclude_flag = False if self.excludes: for exclude in self.excludes: - if not fnmatch.fnmatch(member, exclude): + if fnmatch.fnmatch(member, exclude): exclude_flag = True break if not exclude_flag: @@ -786,7 +786,7 @@ class TgzArchive(object): cmd.extend(self.include_files) locale = get_best_parsable_locale(self.module) - rc, out, err = self.module.run_command(cmd, cwd=self.b_dest, environ_update=dict(LANG=locale, LC_ALL=locale, LC_MESSAGES=locale)) + rc, out, err = self.module.run_command(cmd, cwd=self.b_dest, environ_update=dict(LANG=locale, LC_ALL=locale, LC_MESSAGES=locale, LANGUAGE=locale)) if rc != 0: raise UnarchiveError('Unable to list files in the archive') @@ -831,7 +831,7 @@ class TgzArchive(object): if self.include_files: cmd.extend(self.include_files) locale = get_best_parsable_locale(self.module) - rc, out, err = self.module.run_command(cmd, cwd=self.b_dest, environ_update=dict(LANG=locale, LC_ALL=locale, LC_MESSAGES=locale)) + rc, out, err = self.module.run_command(cmd, cwd=self.b_dest, environ_update=dict(LANG=locale, LC_ALL=locale, LC_MESSAGES=locale, LANGUAGE=locale)) # Check whether the differences are in something that we're # setting anyway @@ -885,7 +885,7 @@ class TgzArchive(object): if self.include_files: cmd.extend(self.include_files) locale = get_best_parsable_locale(self.module) - rc, out, err = self.module.run_command(cmd, cwd=self.b_dest, environ_update=dict(LANG=locale, LC_ALL=locale, LC_MESSAGES=locale)) + rc, out, err = self.module.run_command(cmd, cwd=self.b_dest, environ_update=dict(LANG=locale, LC_ALL=locale, LC_MESSAGES=locale, LANGUAGE=locale)) return dict(cmd=cmd, rc=rc, out=out, err=err) def can_handle_archive(self): diff --git a/lib/ansible/modules/uri.py b/lib/ansible/modules/uri.py index b75c1bff..c095395d 100644 --- a/lib/ansible/modules/uri.py +++ b/lib/ansible/modules/uri.py @@ -52,7 +52,7 @@ options: description: - The serialization format of the body. When set to C(json), C(form-multipart), or C(form-urlencoded), encodes the body argument, if needed, and automatically sets the Content-Type header accordingly. - - As of C(2.3) it is possible to override the `Content-Type` header, when + - As of v2.3 it is possible to override the C(Content-Type) header, when set to C(json) or C(form-urlencoded) via the I(headers) option. - The 'Content-Type' header cannot be overridden when using C(form-multipart) - C(form-urlencoded) was added in v2.7. diff --git a/lib/ansible/modules/validate_argument_spec.py b/lib/ansible/modules/validate_argument_spec.py index 3e66a9b9..291890e3 100644 --- a/lib/ansible/modules/validate_argument_spec.py +++ b/lib/ansible/modules/validate_argument_spec.py @@ -78,7 +78,7 @@ EXAMPLES = r''' - validate_argument_spec: argument_spec: "{{lookup('file', 'nakedoptions.yml'}}" provided_arguments: - but: "that i can define on the include itself, like in it's `vars:` keyword" + but: "that i can define on the include itself, like in it's C(vars:) keyword" - name: the include itself vars: diff --git a/lib/ansible/modules/yum.py b/lib/ansible/modules/yum.py index 0b428e85..2a6caca5 100644 --- a/lib/ansible/modules/yum.py +++ b/lib/ansible/modules/yum.py @@ -50,9 +50,9 @@ options: version_added: "2.0" list: description: - - "Package name to run the equivalent of yum list --show-duplicates <package> against. In addition to listing packages, + - "Package name to run the equivalent of yum list C(--show-duplicates <package>) against. In addition to listing packages, use can also list the following: C(installed), C(updates), C(available) and C(repos)." - - This parameter is mutually exclusive with C(name). + - This parameter is mutually exclusive with I(name). type: str state: description: @@ -261,8 +261,8 @@ attributes: platform: platforms: rhel notes: - - When used with a `loop:` each package will be processed individually, - it is much more efficient to pass the list directly to the `name` option. + - When used with a C(loop:) each package will be processed individually, + it is much more efficient to pass the list directly to the I(name) option. - In versions prior to 1.9.2 this module installed and removed each package given to the yum module separately. This caused problems when packages specified by filename or url had to be installed or removed together. In @@ -737,13 +737,13 @@ class YumModule(YumDnf): # If a repo with `repo_gpgcheck=1` is added and the repo GPG # key was never accepted, querying this repo will throw an # error: 'repomd.xml signature could not be verified'. In that - # situation we need to run `yum -y makecache` which will accept + # situation we need to run `yum -y makecache fast` which will accept # the key and try again. if 'repomd.xml signature could not be verified' in to_native(e): if self.releasever: - self.module.run_command(self.yum_basecmd + ['makecache'] + ['--releasever=%s' % self.releasever]) + self.module.run_command(self.yum_basecmd + ['makecache', 'fast', '--releasever=%s' % self.releasever]) else: - self.module.run_command(self.yum_basecmd + ['makecache']) + self.module.run_command(self.yum_basecmd + ['makecache', 'fast']) pkgs = self.yum_base.returnPackagesByDep(req_spec) + \ self.yum_base.returnInstalledPackagesByDep(req_spec) else: diff --git a/lib/ansible/playbook/block.py b/lib/ansible/playbook/block.py index 3c8ecc76..a9b399f2 100644 --- a/lib/ansible/playbook/block.py +++ b/lib/ansible/playbook/block.py @@ -79,11 +79,13 @@ class Block(Base, Conditional, CollectionSearch, Taggable): of a role or task include which does, so return those if present. ''' - all_vars = self.vars.copy() + all_vars = {} if self._parent: all_vars.update(self._parent.get_vars()) + all_vars.update(self.vars.copy()) + return all_vars @staticmethod diff --git a/lib/ansible/playbook/conditional.py b/lib/ansible/playbook/conditional.py index 7afcb41c..53a03fb8 100644 --- a/lib/ansible/playbook/conditional.py +++ b/lib/ansible/playbook/conditional.py @@ -184,12 +184,7 @@ class Conditional: # NOTE The spaces around True and False are intentional to short-circuit safe_eval and avoid # its expensive calls. presented = "{%% if %s %%} True {%% else %%} False {%% endif %%}" % conditional - # NOTE Convert the result to text to account for both native and non-native jinja. - # NOTE The templated result of `presented` is string on native jinja as well prior to Python 3.10. - # ast.literal_eval on Python 3.10 removes leading whitespaces so " True " becomes bool True - # as opposed to Python 3.9 and lower where the same would result in IndentationError and - # string " True " would be returned by Templar. - val = to_text(templar.template(presented, disable_lookups=disable_lookups)).strip() + val = templar.template(presented, disable_lookups=disable_lookups).strip() if val == "True": return True elif val == "False": diff --git a/lib/ansible/plugins/action/gather_facts.py b/lib/ansible/plugins/action/gather_facts.py index 45802ea2..50e13b66 100644 --- a/lib/ansible/plugins/action/gather_facts.py +++ b/lib/ansible/plugins/action/gather_facts.py @@ -22,8 +22,13 @@ class ActionModule(ActionBase): # deal with 'setup specific arguments' if fact_module not in C._ACTION_SETUP: + # TODO: remove in favor of controller side argspec detecing valid arguments # network facts modules must support gather_subset - if self._connection._load_name not in ('network_cli', 'httpapi', 'netconf'): + try: + name = self._connection.redirected_names[-1].replace('ansible.netcommon.', '', 1) + except (IndexError, AttributeError): + name = self._connection._load_name.split('.')[-1] + if name not in ('network_cli', 'httpapi', 'netconf'): subset = mod_args.pop('gather_subset', None) if subset not in ('all', ['all']): self._display.warning('Ignoring subset(%s) for %s' % (subset, fact_module)) diff --git a/lib/ansible/plugins/action/include_vars.py b/lib/ansible/plugins/action/include_vars.py index aec0f004..3c3cb9e1 100644 --- a/lib/ansible/plugins/action/include_vars.py +++ b/lib/ansible/plugins/action/include_vars.py @@ -100,6 +100,7 @@ class ActionModule(ActionBase): self._set_args() results = dict() + failed = False if self.source_dir: self._set_dir_defaults() self._set_root_dir() @@ -172,13 +173,16 @@ class ActionModule(ActionBase): ) self.source_dir = path.join(current_dir, self.source_dir) + def _log_walk(self, error): + self._display.vvv('Issue with walking through "%s": %s' % (to_native(error.filename), to_native(error))) + def _traverse_dir_depth(self): """ Recursively iterate over a directory and sort the files in alphabetical order. Do not iterate pass the set depth. The default depth is unlimited. """ current_depth = 0 - sorted_walk = list(walk(self.source_dir)) + sorted_walk = list(walk(self.source_dir, onerror=self._log_walk)) sorted_walk.sort(key=lambda x: x[0]) for current_root, current_dir, current_files in sorted_walk: current_depth += 1 diff --git a/lib/ansible/plugins/become/sudo.py b/lib/ansible/plugins/become/sudo.py index a4093b85..9b6ded7d 100644 --- a/lib/ansible/plugins/become/sudo.py +++ b/lib/ansible/plugins/become/sudo.py @@ -69,6 +69,8 @@ DOCUMENTATION = """ key: password """ +import re +import shlex from ansible.plugins.become import BecomeBase @@ -94,7 +96,16 @@ class BecomeModule(BecomeBase): if self.get_option('become_pass'): self.prompt = '[sudo via ansible, key=%s] password:' % self._id if flags: # this could be simplified, but kept as is for now for backwards string matching - flags = flags.replace('-n', '') + reflag = [] + for flag in shlex.split(flags): + if flag in ('-n', '--non-interactive'): + continue + elif not flag.startswith('--'): + # handle -XnxxX flags only + flag = re.sub(r'^(-\w*)n(\w*.*)', r'\1\2', flag) + reflag.append(flag) + flags = shlex.join(reflag) + prompt = '-p "%s"' % (self.prompt) user = self.get_option('become_user') or '' diff --git a/lib/ansible/plugins/callback/default.py b/lib/ansible/plugins/callback/default.py index 56d65315..0e479703 100644 --- a/lib/ansible/plugins/callback/default.py +++ b/lib/ansible/plugins/callback/default.py @@ -24,6 +24,7 @@ from ansible import context from ansible.playbook.task_include import TaskInclude from ansible.plugins.callback import CallbackBase from ansible.utils.color import colorize, hostcolor +from ansible.utils.fqcn import add_internal_fqcns # These values use ansible.constants for historical reasons, mostly to allow # unmodified derivative plugins to work. However, newer options added to the @@ -176,7 +177,7 @@ class CallbackModule(CallbackBase): # Preserve task name, as all vars may not be available for templating # when we need it later - if self._play.strategy in ('free', 'host_pinned'): + if self._play.strategy in add_internal_fqcns(('free', 'host_pinned')): # Explicitly set to None for strategy free/host_pinned to account for any cached # task title from a previous non-free play self._last_task_name = None diff --git a/lib/ansible/plugins/callback/junit.py b/lib/ansible/plugins/callback/junit.py index 73284a33..09287063 100644 --- a/lib/ansible/plugins/callback/junit.py +++ b/lib/ansible/plugins/callback/junit.py @@ -40,6 +40,13 @@ DOCUMENTATION = ''' version_added: "2.8" env: - name: JUNIT_TASK_RELATIVE_PATH + replace_out_of_tree_path: + name: Replace out of tree path + default: none + description: Replace the directory portion of an out-of-tree relative task path with the given placeholder + version_added: "2.12.3" + env: + - name: JUNIT_REPLACE_OUT_OF_TREE_PATH fail_on_change: name: JUnit fail on change default: False @@ -141,6 +148,7 @@ class CallbackModule(CallbackBase): self._include_setup_tasks_in_report = os.getenv('JUNIT_INCLUDE_SETUP_TASKS_IN_REPORT', 'True').lower() self._hide_task_arguments = os.getenv('JUNIT_HIDE_TASK_ARGUMENTS', 'False').lower() self._test_case_prefix = os.getenv('JUNIT_TEST_CASE_PREFIX', '') + self._replace_out_of_tree_path = os.getenv('JUNIT_REPLACE_OUT_OF_TREE_PATH', None) self._playbook_path = None self._playbook_name = None self._play_name = None @@ -150,6 +158,9 @@ class CallbackModule(CallbackBase): self._task_data = {} + if self._replace_out_of_tree_path is not None: + self._replace_out_of_tree_path = to_text(self._replace_out_of_tree_path) + if not os.path.exists(self._output_dir): os.makedirs(self._output_dir) @@ -208,11 +219,14 @@ class CallbackModule(CallbackBase): name = '[%s] %s: %s' % (host_data.name, task_data.play, task_data.name) duration = host_data.finish - task_data.start - if self._task_relative_path: - junit_classname = os.path.relpath(task_data.path, self._task_relative_path) + if self._task_relative_path and task_data.path: + junit_classname = to_text(os.path.relpath(to_bytes(task_data.path), to_bytes(self._task_relative_path))) else: junit_classname = task_data.path + if self._replace_out_of_tree_path is not None and junit_classname.startswith('../'): + junit_classname = self._replace_out_of_tree_path + to_text(os.path.basename(to_bytes(junit_classname))) + if self._task_class == 'true': junit_classname = re.sub(r'\.yml:[0-9]+$', '', junit_classname) diff --git a/lib/ansible/plugins/callback/tree.py b/lib/ansible/plugins/callback/tree.py index e7682d5f..da9c767a 100644 --- a/lib/ansible/plugins/callback/tree.py +++ b/lib/ansible/plugins/callback/tree.py @@ -15,7 +15,7 @@ DOCUMENTATION = ''' options: directory: version_added: '2.11' - description: directory that will contain the per host JSON files. Also set by the ``--tree`` option when using adhoc. + description: directory that will contain the per host JSON files. Also set by the C(--tree) option when using adhoc. ini: - section: callback_tree key: directory @@ -24,7 +24,7 @@ DOCUMENTATION = ''' default: "~/.ansible/tree" type: path description: - - "This callback is used by the Ansible (adhoc) command line option `-t|--tree`" + - "This callback is used by the Ansible (adhoc) command line option C(-t|--tree)." - This produces a JSON dump of events in a directory, a file for each host, the directory used MUST be passed as a command line option. ''' diff --git a/lib/ansible/plugins/connection/ssh.py b/lib/ansible/plugins/connection/ssh.py index 08e90ce0..74ebbf9e 100644 --- a/lib/ansible/plugins/connection/ssh.py +++ b/lib/ansible/plugins/connection/ssh.py @@ -59,7 +59,7 @@ DOCUMENTATION = ''' sshpass_prompt: description: - Password prompt that sshpass should search for. Supported by sshpass 1.06 and up. - - Defaults to ``Enter PIN for`` when pkcs11_provider is set. + - Defaults to C(Enter PIN for) when pkcs11_provider is set. default: '' ini: - section: 'ssh_connection' @@ -131,7 +131,7 @@ DOCUMENTATION = ''' - name: ansible_scp_executable version_added: '2.7' scp_extra_args: - description: Extra exclusive to the ``scp`` CLI + description: Extra exclusive to the C(scp) CLI vars: - name: ansible_scp_extra_args env: @@ -145,7 +145,7 @@ DOCUMENTATION = ''' - name: scp_extra_args default: '' sftp_extra_args: - description: Extra exclusive to the ``sftp`` CLI + description: Extra exclusive to the C(sftp) CLI vars: - name: ansible_sftp_extra_args env: @@ -242,9 +242,9 @@ DOCUMENTATION = ''' control_path: description: - This is the location to save SSH's ControlPath sockets, it uses SSH's variable substitution. - - Since 2.3, if null (default), ansible will generate a unique hash. Use `%(directory)s` to indicate where to use the control dir path setting. - - Before 2.3 it defaulted to `control_path=%(directory)s/ansible-ssh-%%h-%%p-%%r`. - - Be aware that this setting is ignored if `-o ControlPath` is set in ssh args. + - Since 2.3, if null (default), ansible will generate a unique hash. Use ``%(directory)s`` to indicate where to use the control dir path setting. + - Before 2.3 it defaulted to ``control_path=%(directory)s/ansible-ssh-%%h-%%p-%%r``. + - Be aware that this setting is ignored if C(-o ControlPath) is set in ssh args. env: - name: ANSIBLE_SSH_CONTROL_PATH ini: @@ -257,7 +257,7 @@ DOCUMENTATION = ''' default: ~/.ansible/cp description: - This sets the directory to use for ssh control path if the control path setting is null. - - Also, provides the `%(directory)s` variable for the control path setting. + - Also, provides the ``%(directory)s`` variable for the control path setting. env: - name: ANSIBLE_SSH_CONTROL_PATH_DIR ini: @@ -280,7 +280,7 @@ DOCUMENTATION = ''' description: - "Preferred method to use when transferring files over ssh" - Setting to 'smart' (default) will try them in order, until one succeeds or they all fail - - Using 'piped' creates an ssh pipe with ``dd`` on either side to copy the data + - Using 'piped' creates an ssh pipe with C(dd) on either side to copy the data choices: ['sftp', 'scp', 'piped', 'smart'] env: [{name: ANSIBLE_SSH_TRANSFER_METHOD}] ini: @@ -356,7 +356,6 @@ import subprocess import time from functools import wraps -from ansible import constants as C from ansible.errors import ( AnsibleAuthenticationFailure, AnsibleConnectionFailure, @@ -383,6 +382,7 @@ b_NOT_SSH_ERRORS = (b'Traceback (most recent call last):', # Python-2.6 when th ) SSHPASS_AVAILABLE = None +SSH_DEBUG = re.compile(r'^debug\d+: .*') class AnsibleControlPersistBrokenPipeError(AnsibleError): @@ -771,7 +771,7 @@ class Connection(ConnectionBase): self.port, self.user ) - b_args = (b"-o", b"ControlPath=" + to_bytes(self.control_path % dict(directory=cpdir), errors='surrogate_or_strict')) + b_args = (b"-o", b'ControlPath="%s"' % to_bytes(self.control_path % dict(directory=cpdir), errors='surrogate_or_strict')) self._add_args(b_command, b_args, u"found only ControlPersist; added ControlPath") # Finally, we add any caller-supplied extras. @@ -832,7 +832,10 @@ class Connection(ConnectionBase): suppress_output = False # display.debug("Examining line (source=%s, state=%s): '%s'" % (source, state, display_line)) - if self.become.expect_prompt() and self.become.check_password_prompt(b_line): + if SSH_DEBUG.match(display_line): + # skip lines from ssh debug output to avoid false matches + pass + elif self.become.expect_prompt() and self.become.check_password_prompt(b_line): display.debug(u"become_prompt: (source=%s, state=%s): '%s'" % (source, state, display_line)) self._flags['become_prompt'] = True suppress_output = True @@ -1270,6 +1273,8 @@ class Connection(ConnectionBase): super(Connection, self).exec_command(cmd, in_data=in_data, sudoable=sudoable) + self.host = self.get_option('host') or self._play_context.remote_addr + display.vvv(u"ESTABLISH SSH CONNECTION FOR USER: {0}".format(self.user), host=self.host) if getattr(self._shell, "_IS_WINDOWS", False): @@ -1314,6 +1319,8 @@ class Connection(ConnectionBase): super(Connection, self).put_file(in_path, out_path) + self.host = self.get_option('host') or self._play_context.remote_addr + display.vvv(u"PUT {0} TO {1}".format(in_path, out_path), host=self.host) if not os.path.exists(to_bytes(in_path, errors='surrogate_or_strict')): raise AnsibleFileNotFound("file or module does not exist: {0}".format(to_native(in_path))) @@ -1328,6 +1335,8 @@ class Connection(ConnectionBase): super(Connection, self).fetch_file(in_path, out_path) + self.host = self.get_option('host') or self._play_context.remote_addr + display.vvv(u"FETCH {0} TO {1}".format(in_path, out_path), host=self.host) # need to add / if path is rooted @@ -1339,6 +1348,7 @@ class Connection(ConnectionBase): def reset(self): run_reset = False + self.host = self.get_option('host') or self._play_context.remote_addr # If we have a persistent ssh connection (ControlPersist), we can ask it to stop listening. # only run the reset if the ControlPath already exists or if it isn't configured and ControlPersist is set diff --git a/lib/ansible/plugins/connection/winrm.py b/lib/ansible/plugins/connection/winrm.py index b8d73536..827d9eae 100644 --- a/lib/ansible/plugins/connection/winrm.py +++ b/lib/ansible/plugins/connection/winrm.py @@ -12,7 +12,7 @@ DOCUMENTATION = """ description: - Run commands or put/fetch on a target via WinRM - This plugin allows extra arguments to be passed that are supported by the protocol but not explicitly defined here. - They should take the form of variables declared with the following pattern `ansible_winrm_<option>`. + They should take the form of variables declared with the following pattern C(ansible_winrm_<option>). version_added: "2.0" extends_documentation_fragment: - connection_pipelining diff --git a/lib/ansible/plugins/doc_fragments/default_callback.py b/lib/ansible/plugins/doc_fragments/default_callback.py index 4b10f207..f9d862c1 100644 --- a/lib/ansible/plugins/doc_fragments/default_callback.py +++ b/lib/ansible/plugins/doc_fragments/default_callback.py @@ -18,9 +18,9 @@ class ModuleDocFragment(object): env: - name: DISPLAY_SKIPPED_HOSTS deprecated: - why: environment variables without "ANSIBLE_" prefix are deprecated + why: environment variables without C(ANSIBLE_) prefix are deprecated version: "2.12" - alternatives: the "ANSIBLE_DISPLAY_SKIPPED_HOSTS" environment variable + alternatives: the C(ANSIBLE_DISPLAY_SKIPPED_HOSTS) environment variable - name: ANSIBLE_DISPLAY_SKIPPED_HOSTS ini: - key: display_skipped_hosts diff --git a/lib/ansible/plugins/doc_fragments/shell_common.py b/lib/ansible/plugins/doc_fragments/shell_common.py index 5b018000..628cc218 100644 --- a/lib/ansible/plugins/doc_fragments/shell_common.py +++ b/lib/ansible/plugins/doc_fragments/shell_common.py @@ -35,7 +35,7 @@ options: system_tmpdirs: description: - "List of valid system temporary directories on the managed machine for Ansible to choose - when it cannot use ``remote_tmp``, normally due to permission issues. These must be world + when it cannot use C(remote_tmp), normally due to permission issues. These must be world readable, writable, and executable. This list should only contain directories which the system administrator has pre-created with the proper ownership and permissions otherwise security issues can arise." diff --git a/lib/ansible/plugins/inventory/auto.py b/lib/ansible/plugins/inventory/auto.py index 82d96650..9d175ed8 100644 --- a/lib/ansible/plugins/inventory/auto.py +++ b/lib/ansible/plugins/inventory/auto.py @@ -11,14 +11,14 @@ DOCUMENTATION = ''' version_added: "2.5" short_description: Loads and executes an inventory plugin specified in a YAML config description: - - By whitelisting C(auto) inventory plugin, any YAML inventory config file with a + - By enabling the C(auto) inventory plugin, any YAML inventory config file with a C(plugin) key at its root will automatically cause the named plugin to be loaded and executed with that - config. This effectively provides automatic whitelisting of all installed/accessible inventory plugins. + config. This effectively provides automatic enabling of all installed/accessible inventory plugins. - To disable this behavior, remove C(auto) from the C(INVENTORY_ENABLED) config element. ''' EXAMPLES = ''' -# This plugin is not intended for direct use; it is a fallback mechanism for automatic whitelisting of +# This plugin is not intended for direct use; it is a fallback mechanism for automatic enabling of # all installed inventory plugins. ''' diff --git a/lib/ansible/plugins/inventory/ini.py b/lib/ansible/plugins/inventory/ini.py index 6518f8a3..f6375311 100644 --- a/lib/ansible/plugins/inventory/ini.py +++ b/lib/ansible/plugins/inventory/ini.py @@ -8,13 +8,13 @@ DOCUMENTATION = ''' version_added: "2.4" short_description: Uses an Ansible INI file as inventory source. description: - - INI file based inventory, sections are groups or group related with special `:modifiers`. + - INI file based inventory, sections are groups or group related with special C(:modifiers). - Entries in sections C([group_1]) are hosts, members of the group. - Hosts can have variables defined inline as key/value pairs separated by C(=). - The C(children) modifier indicates that the section contains groups. - The C(vars) modifier indicates that the section contains variables assigned to members of the group. - Anything found outside a section is considered an 'ungrouped' host. - - Values passed in the INI format using the ``key=value`` syntax are interpreted differently depending on where they are declared within your inventory. + - Values passed in the INI format using the C(key=value) syntax are interpreted differently depending on where they are declared within your inventory. - When declared inline with the host, INI values are processed by Python's ast.literal_eval function (U(https://docs.python.org/3/library/ast.html#ast.literal_eval)) and interpreted as Python literal structures (strings, numbers, tuples, lists, dicts, booleans, None). Host lines accept multiple C(key=value) parameters per line. @@ -24,7 +24,7 @@ DOCUMENTATION = ''' - Do not rely on types set during definition, always make sure you specify type with a filter when needed when consuming the variable. - See the Examples for proper quoting to prevent changes to variable type. notes: - - Whitelisted in configuration by default. + - Enabled in configuration by default. - Consider switching to YAML format for inventory sources to avoid confusion on the actual type of a variable. The YAML inventory plugin processes variable values consistently and correctly. ''' diff --git a/lib/ansible/plugins/inventory/script.py b/lib/ansible/plugins/inventory/script.py index 0c028c70..9d8aae55 100644 --- a/lib/ansible/plugins/inventory/script.py +++ b/lib/ansible/plugins/inventory/script.py @@ -26,7 +26,7 @@ DOCUMENTATION = ''' C(--host) will only be used if no C(_meta) key is present. This is a performance optimization as the script would be called per host otherwise. notes: - - Whitelisted in configuration by default. + - Enabled in configuration by default. - The plugin does not cache results because external inventory scripts are responsible for their own caching. ''' diff --git a/lib/ansible/plugins/inventory/yaml.py b/lib/ansible/plugins/inventory/yaml.py index f927e00b..d865d68f 100644 --- a/lib/ansible/plugins/inventory/yaml.py +++ b/lib/ansible/plugins/inventory/yaml.py @@ -16,7 +16,7 @@ DOCUMENTATION = ''' - File MUST have a valid extension, defined in configuration. notes: - If you want to set vars for the C(all) group inside the inventory file, the C(all) group must be the first entry in the file. - - Whitelisted in configuration by default. + - Enabled in configuration by default. options: yaml_extensions: description: list of 'valid' extensions for files containing YAML diff --git a/lib/ansible/plugins/loader.py b/lib/ansible/plugins/loader.py index a80aae7c..cd655814 100644 --- a/lib/ansible/plugins/loader.py +++ b/lib/ansible/plugins/loader.py @@ -1147,7 +1147,8 @@ def _does_collection_support_ansible_version(requirement_string, ansible_version def _configure_collection_loader(): if AnsibleCollectionConfig.collection_finder: - display.warning('AnsibleCollectionFinder has already been configured') + # this must be a Python warning so that it can be filtered out by the import sanity test + warnings.warn('AnsibleCollectionFinder has already been configured') return finder = _AnsibleCollectionFinder(C.config.get_config_value('COLLECTIONS_PATHS'), C.config.get_config_value('COLLECTIONS_SCAN_SYS_PATH')) diff --git a/lib/ansible/plugins/lookup/inventory_hostnames.py b/lib/ansible/plugins/lookup/inventory_hostnames.py index a3cff92e..f8432752 100644 --- a/lib/ansible/plugins/lookup/inventory_hostnames.py +++ b/lib/ansible/plugins/lookup/inventory_hostnames.py @@ -14,7 +14,7 @@ DOCUMENTATION = """ version_added: "1.3" short_description: list of inventory hosts matching a host pattern description: - - "This lookup understands 'host patterns' as used by the `hosts:` keyword in plays + - "This lookup understands 'host patterns' as used by the C(hosts:) keyword in plays and can return a list of matching hosts from inventory" notes: - this is only worth for 'hostname patterns' it is easier to loop over the group/group_names variables otherwise. diff --git a/lib/ansible/plugins/lookup/sequence.py b/lib/ansible/plugins/lookup/sequence.py index 7dac37bd..3a2f38ba 100644 --- a/lib/ansible/plugins/lookup/sequence.py +++ b/lib/ansible/plugins/lookup/sequence.py @@ -15,8 +15,8 @@ DOCUMENTATION = """ - 'Arguments can be specified as key=value pair strings or as a shortcut form of the arguments string is also accepted: [start-]end[/stride][:format].' - 'Numerical values can be specified in decimal, hexadecimal (0x3f8) or octal (0600).' - Starting at version 1.9.2, negative strides are allowed. - - Generated items are strings. Use Jinja2 filters to convert items to preferred type, e.g. ``{{ 1 + item|int }}``. - - See also Jinja2 ``range`` filter as an alternative. + - Generated items are strings. Use Jinja2 filters to convert items to preferred type, e.g. C({{ 1 + item|int }}). + - See also Jinja2 C(range) filter as an alternative. options: start: description: number at which to start the sequence diff --git a/lib/ansible/plugins/lookup/template.py b/lib/ansible/plugins/lookup/template.py index 5dc1b7c7..8f98861b 100644 --- a/lib/ansible/plugins/lookup/template.py +++ b/lib/ansible/plugins/lookup/template.py @@ -20,6 +20,7 @@ DOCUMENTATION = """ description: - Whether to convert YAML into data. If False, strings that are YAML will be left untouched. - Mutually exclusive with the jinja2_native option. + default: true variable_start_string: description: The string marking the beginning of a print statement. default: '{{' diff --git a/lib/ansible/plugins/strategy/__init__.py b/lib/ansible/plugins/strategy/__init__.py index f415709a..29de68ce 100644 --- a/lib/ansible/plugins/strategy/__init__.py +++ b/lib/ansible/plugins/strategy/__init__.py @@ -46,6 +46,7 @@ from ansible.playbook.conditional import Conditional from ansible.playbook.handler import Handler from ansible.playbook.helpers import load_list_of_blocks from ansible.playbook.included_file import IncludedFile +from ansible.playbook.task import Task from ansible.playbook.task_include import TaskInclude from ansible.plugins import loader as plugin_loader from ansible.template import Templar @@ -469,9 +470,18 @@ class StrategyBase: if isinstance(task_result._task, string_types): # If the value is a string, it is ``Task._uuid`` queue_cache_entry = (task_result._host.name, task_result._task) - found_task = self._queued_task_cache.get(queue_cache_entry)['task'] - original_task = found_task.copy(exclude_parent=True, exclude_tasks=True) - original_task._parent = found_task._parent + try: + found_task = self._queued_task_cache[queue_cache_entry]['task'] + except KeyError: + # This should only happen due to an implicit task created by the + # TaskExecutor, restrict this behavior to the explicit use case + # of an implicit async_status task + if task_result._task_fields.get('action') != 'async_status': + raise + original_task = Task() + else: + original_task = found_task.copy(exclude_parent=True, exclude_tasks=True) + original_task._parent = found_task._parent original_task.from_attrs(task_result._task_fields) task_result._task = original_task diff --git a/lib/ansible/plugins/vars/host_group_vars.py b/lib/ansible/plugins/vars/host_group_vars.py index dec18c86..58587d6e 100644 --- a/lib/ansible/plugins/vars/host_group_vars.py +++ b/lib/ansible/plugins/vars/host_group_vars.py @@ -23,13 +23,13 @@ DOCUMENTATION = ''' version_added: "2.4" short_description: In charge of loading group_vars and host_vars requirements: - - whitelist in configuration + - Enabled in configuration description: - Loads YAML vars into corresponding groups/hosts in group_vars/ and host_vars/ directories. - Files are restricted by extension to one of .yaml, .json, .yml or no extension. - Hidden (starting with '.') and backup (ending with '~') files and directories are ignored. - Only applies to inventory sources that are existing paths. - - Starting in 2.10, this plugin requires whitelisting and is whitelisted by default. + - Starting in 2.10, this plugin requires enabling and is enabled by default. options: stage: ini: diff --git a/lib/ansible/release.py b/lib/ansible/release.py index b73bdca9..078520dc 100644 --- a/lib/ansible/release.py +++ b/lib/ansible/release.py @@ -19,6 +19,6 @@ from __future__ import (absolute_import, division, print_function) __metaclass__ = type -__version__ = '2.12.0' +__version__ = '2.12.3' __author__ = 'Ansible, Inc.' __codename__ = 'Dazed and Confused' diff --git a/lib/ansible/template/__init__.py b/lib/ansible/template/__init__.py index 4bb42963..3c27587c 100644 --- a/lib/ansible/template/__init__.py +++ b/lib/ansible/template/__init__.py @@ -573,9 +573,8 @@ class JinjaPluginIntercept(MutableMapping): except Exception as e: raise TemplateSyntaxError(to_native(e), 0) - method_map = getattr(plugin_impl, self._method_map_name) - try: + method_map = getattr(plugin_impl, self._method_map_name) func_items = iteritems(method_map()) except Exception as e: display.warning( @@ -725,6 +724,7 @@ class Templar: new_templar = object.__new__(Templar) new_templar.__dict__.update(self.__dict__) new_templar.environment = new_env + new_templar.environment.finalize = new_templar._finalize mapping = { 'available_variables': new_templar, diff --git a/lib/ansible/template/native_helpers.py b/lib/ansible/template/native_helpers.py index 8886fc1b..94d0c3bb 100644 --- a/lib/ansible/template/native_helpers.py +++ b/lib/ansible/template/native_helpers.py @@ -6,9 +6,9 @@ from __future__ import (absolute_import, division, print_function) __metaclass__ = type -from ast import literal_eval -from itertools import islice, chain +import ast import types +from itertools import islice, chain from jinja2.runtime import StrictUndefined @@ -83,7 +83,11 @@ def ansible_native_concat(nodes): out = u''.join([to_text(_fail_on_undefined(v)) for v in nodes]) try: - out = literal_eval(out) - return out + return ast.literal_eval( + # In Python 3.10+ ast.literal_eval removes leading spaces/tabs + # from the given string. For backwards compatibility we need to + # parse the string ourselves without removing leading spaces/tabs. + ast.parse(out, mode='eval') + ) except (ValueError, SyntaxError, MemoryError): return out diff --git a/lib/ansible/utils/encrypt.py b/lib/ansible/utils/encrypt.py index ee30b322..4cb70b70 100644 --- a/lib/ansible/utils/encrypt.py +++ b/lib/ansible/utils/encrypt.py @@ -246,7 +246,7 @@ class PasslibHash(BaseHash): # Hashes from passlib.hash should be represented as ascii strings of hex # digits so this should not traceback. If it's not representable as such - # we need to traceback and then blacklist such algorithms because it may + # we need to traceback and then block such algorithms because it may # impact calling code. return to_text(result, errors='strict') diff --git a/lib/ansible/vars/clean.py b/lib/ansible/vars/clean.py index 334197ac..c7bac6b2 100644 --- a/lib/ansible/vars/clean.py +++ b/lib/ansible/vars/clean.py @@ -152,13 +152,7 @@ def clean_facts(facts): # then we remove them (except for ssh host keys) for r_key in remove_keys: if not r_key.startswith('ansible_ssh_host_key_'): - try: - r_val = to_text(data[r_key]) - if len(r_val) > 24: - r_val = '%s ... %s' % (r_val[:13], r_val[-6:]) - except Exception: - r_val = ' <failed to convert value to a string> ' - display.warning("Removed restricted key from module data: %s = %s" % (r_key, r_val)) + display.warning("Removed restricted key from module data: %s" % (r_key)) del data[r_key] return strip_internal_keys(data) diff --git a/lib/ansible/vars/plugins.py b/lib/ansible/vars/plugins.py index 1411129d..82beb3ad 100644 --- a/lib/ansible/vars/plugins.py +++ b/lib/ansible/vars/plugins.py @@ -55,7 +55,7 @@ def get_vars_from_path(loader, path, entities, stage): for plugin in vars_plugin_list: if plugin._load_name not in C.VARIABLE_PLUGINS_ENABLED and getattr(plugin, 'REQUIRES_WHITELIST', False): - # 2.x plugins shipped with ansible should require whitelisting, older or non shipped should load automatically + # 2.x plugins shipped with ansible should require enabling, older or non shipped should load automatically continue has_stage = hasattr(plugin, 'get_option') and plugin.has_option('stage') diff --git a/test/integration/targets/ansible-galaxy-collection-scm/tasks/download.yml b/test/integration/targets/ansible-galaxy-collection-scm/tasks/download.yml index b1017e78..6b52bd1d 100644 --- a/test/integration/targets/ansible-galaxy-collection-scm/tasks/download.yml +++ b/test/integration/targets/ansible-galaxy-collection-scm/tasks/download.yml @@ -8,6 +8,7 @@ ansible-galaxy collection download git+https://github.com/ansible-collections/amazon.aws.git,37875c5b4ba5bf3cc43e07edf29f3432fd76def5 git+https://github.com/AlanCoding/awx.git#awx_collection,750c22a150d04eef1cb625fd4f83cce57949416c + --no-deps args: chdir: '{{ galaxy_dir }}/download' register: download_collection @@ -30,7 +31,7 @@ - download_collection_awx_actual.stat.exists - name: test the downloaded repository can be installed - command: 'ansible-galaxy collection install -r requirements.yml' + command: 'ansible-galaxy collection install -r requirements.yml --no-deps' args: chdir: '{{ galaxy_dir }}/download/collections/' diff --git a/test/integration/targets/ansible-galaxy-collection-scm/tasks/individual_collection_repo.yml b/test/integration/targets/ansible-galaxy-collection-scm/tasks/individual_collection_repo.yml index 9ca7c8f0..e51c3a99 100644 --- a/test/integration/targets/ansible-galaxy-collection-scm/tasks/individual_collection_repo.yml +++ b/test/integration/targets/ansible-galaxy-collection-scm/tasks/individual_collection_repo.yml @@ -4,7 +4,7 @@ dest: '{{ scm_path }}/amazon.aws/' - name: install - command: 'ansible-galaxy collection install git+file://{{ scm_path }}/amazon.aws/.git' + command: 'ansible-galaxy collection install git+file://{{ scm_path }}/amazon.aws/.git --no-deps' - name: list installed collections command: 'ansible-galaxy collection list' diff --git a/test/integration/targets/ansible-galaxy-collection-scm/tasks/requirements.yml b/test/integration/targets/ansible-galaxy-collection-scm/tasks/requirements.yml index 235ed126..c7743426 100644 --- a/test/integration/targets/ansible-galaxy-collection-scm/tasks/requirements.yml +++ b/test/integration/targets/ansible-galaxy-collection-scm/tasks/requirements.yml @@ -66,7 +66,7 @@ appear to be a git repository") - name: test using name as a git repo without git+ prefix - command: 'ansible-galaxy collection install -r name_without_type.yml' + command: 'ansible-galaxy collection install -r name_without_type.yml --no-deps' register: result ignore_errors: true args: @@ -83,13 +83,13 @@ dest: '{{ scm_path }}/amazon.aws/' - name: test using name as a git repo - command: 'ansible-galaxy collection install -r git_prefix_name.yml' + command: 'ansible-galaxy collection install -r git_prefix_name.yml --no-deps' register: result args: chdir: '{{ galaxy_dir }}/requirements' - name: test using name plus type as a git repo - command: 'ansible-galaxy collection install -r name_and_type.yml --force' + command: 'ansible-galaxy collection install -r name_and_type.yml --force --no-deps' register: result args: chdir: '{{ galaxy_dir }}/requirements' diff --git a/test/integration/targets/ansible-test/aliases b/test/integration/targets/ansible-test/aliases index 13e01f0c..b98e7bb2 100644 --- a/test/integration/targets/ansible-test/aliases +++ b/test/integration/targets/ansible-test/aliases @@ -1,2 +1,4 @@ -shippable/posix/group1 +shippable/posix/group1 # runs in the distro test containers +shippable/generic/group1 # runs in the default test container context/controller +destructive # adds and then removes packages into lib/ansible/_vendor/ diff --git a/test/integration/targets/ansible-test/ansible_collections/ns/col/plugins/lookup/vendor1.py b/test/integration/targets/ansible-test/ansible_collections/ns/col/plugins/lookup/vendor1.py new file mode 100644 index 00000000..f59b9091 --- /dev/null +++ b/test/integration/targets/ansible-test/ansible_collections/ns/col/plugins/lookup/vendor1.py @@ -0,0 +1,33 @@ +# GNU General Public License v3.0+ (see COPYING or https://www.gnu.org/licenses/gpl-3.0.txt) + +from __future__ import absolute_import, division, print_function +__metaclass__ = type + +DOCUMENTATION = ''' +name: vendor1 +short_description: lookup +description: Lookup. +author: + - Ansible Core Team +''' + +EXAMPLES = '''#''' +RETURN = '''#''' + +from ansible.plugins.lookup import LookupBase +# noinspection PyUnresolvedReferences +from ansible.plugins import loader # import the loader to verify it works when the collection loader has already been loaded + +try: + import demo +except ImportError: + pass +else: + raise Exception('demo import found when it should not be') + + +class LookupModule(LookupBase): + def run(self, terms, variables, **kwargs): + self.set_options(var_options=variables, direct=kwargs) + + return terms diff --git a/test/integration/targets/ansible-test/ansible_collections/ns/col/plugins/lookup/vendor2.py b/test/integration/targets/ansible-test/ansible_collections/ns/col/plugins/lookup/vendor2.py new file mode 100644 index 00000000..22b4236a --- /dev/null +++ b/test/integration/targets/ansible-test/ansible_collections/ns/col/plugins/lookup/vendor2.py @@ -0,0 +1,33 @@ +# GNU General Public License v3.0+ (see COPYING or https://www.gnu.org/licenses/gpl-3.0.txt) + +from __future__ import absolute_import, division, print_function +__metaclass__ = type + +DOCUMENTATION = ''' +name: vendor2 +short_description: lookup +description: Lookup. +author: + - Ansible Core Team +''' + +EXAMPLES = '''#''' +RETURN = '''#''' + +from ansible.plugins.lookup import LookupBase +# noinspection PyUnresolvedReferences +from ansible.plugins import loader # import the loader to verify it works when the collection loader has already been loaded + +try: + import demo +except ImportError: + pass +else: + raise Exception('demo import found when it should not be') + + +class LookupModule(LookupBase): + def run(self, terms, variables, **kwargs): + self.set_options(var_options=variables, direct=kwargs) + + return terms diff --git a/test/integration/targets/ansible-test/ansible_collections/ns/col/plugins/modules/no_callable.py b/test/integration/targets/ansible-test/ansible_collections/ns/col/plugins/modules/no_callable.py new file mode 100644 index 00000000..176376ab --- /dev/null +++ b/test/integration/targets/ansible-test/ansible_collections/ns/col/plugins/modules/no_callable.py @@ -0,0 +1,23 @@ +#!/usr/bin/python +# GNU General Public License v3.0+ (see COPYING or https://www.gnu.org/licenses/gpl-3.0.txt) + +from __future__ import absolute_import, division, print_function +__metaclass__ = type + +DOCUMENTATION = ''' +module: no_callable +short_description: No callale test module +description: No callable test module. +author: + - Ansible Core Team +''' + +EXAMPLES = '''#''' +RETURN = '''''' + +from ansible.module_utils.basic import AnsibleModule + + +if __name__ == '__main__': + module = AnsibleModule(argument_spec=dict()) + module.exit_json() diff --git a/test/integration/targets/ansible-test/ansible_collections/ns/ps_only/meta/runtime.yml b/test/integration/targets/ansible-test/ansible_collections/ns/ps_only/meta/runtime.yml new file mode 100644 index 00000000..1602a255 --- /dev/null +++ b/test/integration/targets/ansible-test/ansible_collections/ns/ps_only/meta/runtime.yml @@ -0,0 +1 @@ +requires_ansible: '>=2.9' diff --git a/test/integration/targets/ansible-test/ansible_collections/ns/ps_only/plugins/module_utils/validate.psm1 b/test/integration/targets/ansible-test/ansible_collections/ns/ps_only/plugins/module_utils/validate.psm1 new file mode 100644 index 00000000..7072b311 --- /dev/null +++ b/test/integration/targets/ansible-test/ansible_collections/ns/ps_only/plugins/module_utils/validate.psm1 @@ -0,0 +1,8 @@ +function Validate { + <# + .SYNOPSIS + validate + #> +} + +Export-ModuleMember -Function "Validate" diff --git a/test/integration/targets/ansible-test/ansible_collections/ns/ps_only/plugins/modules/validate.ps1 b/test/integration/targets/ansible-test/ansible_collections/ns/ps_only/plugins/modules/validate.ps1 new file mode 100644 index 00000000..a587af80 --- /dev/null +++ b/test/integration/targets/ansible-test/ansible_collections/ns/ps_only/plugins/modules/validate.ps1 @@ -0,0 +1,8 @@ +#!powershell +# GNU General Public License v3.0+ (see COPYING or https://www.gnu.org/licenses/gpl-3.0.txt) + +#AnsibleRequires -CSharpUtil Ansible.Basic +#AnsibleRequires -PowerShell ..module_utils.validate + +$module = [Ansible.Basic.AnsibleModule]::Create($args, @{}) +$module.ExitJson() diff --git a/test/integration/targets/ansible-test/ansible_collections/ns/ps_only/plugins/modules/validate.py b/test/integration/targets/ansible-test/ansible_collections/ns/ps_only/plugins/modules/validate.py new file mode 100644 index 00000000..ee1fb138 --- /dev/null +++ b/test/integration/targets/ansible-test/ansible_collections/ns/ps_only/plugins/modules/validate.py @@ -0,0 +1,14 @@ +# GNU General Public License v3.0+ (see COPYING or https://www.gnu.org/licenses/gpl-3.0.txt) + +DOCUMENTATION = r''' +module: validate +short_description: validate +description: validate +author: "validate (@validate)" +''' + +EXAMPLES = r''' +''' + +RETURN = r''' +''' diff --git a/test/integration/targets/ansible-test/collection-tests/constraints.sh b/test/integration/targets/ansible-test/collection-tests/constraints.sh deleted file mode 100755 index d3bbc6ab..00000000 --- a/test/integration/targets/ansible-test/collection-tests/constraints.sh +++ /dev/null @@ -1,20 +0,0 @@ -#!/usr/bin/env bash - -set -eux -o pipefail - -cp -a "${TEST_DIR}/ansible_collections" "${WORK_DIR}" -cd "${WORK_DIR}/ansible_collections/ns/col_constraints" - -# common args for all tests -# each test will be run in a separate venv to verify that requirements have been properly specified -common=(--venv --python "${ANSIBLE_TEST_PYTHON_VERSION}" --color --truncate 0 "${@}") - -# unit tests - -rm -rf "tests/output" -ansible-test units "${common[@]}" - -# integration tests - -rm -rf "tests/output" -ansible-test integration "${common[@]}" diff --git a/test/integration/targets/ansible-test/collection-tests/coverage.sh b/test/integration/targets/ansible-test/collection-tests/coverage.sh index 221ae66a..c2336a32 100755 --- a/test/integration/targets/ansible-test/collection-tests/coverage.sh +++ b/test/integration/targets/ansible-test/collection-tests/coverage.sh @@ -5,22 +5,13 @@ set -eux -o pipefail cp -a "${TEST_DIR}/ansible_collections" "${WORK_DIR}" cd "${WORK_DIR}/ansible_collections/ns/col" -# rename the sanity ignore file to match the current ansible version and update import ignores with the python version -ansible_version="$(python -c 'import ansible.release; print(".".join(ansible.release.__version__.split(".")[:2]))')" -if [[ "${ANSIBLE_TEST_PYTHON_VERSION}" =~ ^2\. ]] || [[ "${ANSIBLE_TEST_PYTHON_VERSION}" =~ ^3\.[567] ]]; then - # Non-module/module_utils plugins are not checked on these remote-only Python versions - sed "s/ import$/ import-${ANSIBLE_TEST_PYTHON_VERSION}/;" < "tests/sanity/ignore.txt" | grep -v 'plugins/[^m].* import' > "tests/sanity/ignore-${ansible_version}.txt" -else - sed "s/ import$/ import-${ANSIBLE_TEST_PYTHON_VERSION}/;" < "tests/sanity/ignore.txt" > "tests/sanity/ignore-${ansible_version}.txt" -fi -cat "tests/sanity/ignore-${ansible_version}.txt" +"${TEST_DIR}/collection-tests/update-ignore.py" # common args for all tests common=(--venv --color --truncate 0 "${@}") -test_common=("${common[@]}" --python "${ANSIBLE_TEST_PYTHON_VERSION}") # run a lightweight test that generates code coverge output -ansible-test sanity --test import "${test_common[@]}" --coverage +ansible-test sanity --test import "${common[@]}" --coverage # report on code coverage in all supported formats ansible-test coverage report "${common[@]}" diff --git a/test/integration/targets/ansible-test/collection-tests/integration-constraints.sh b/test/integration/targets/ansible-test/collection-tests/integration-constraints.sh new file mode 100755 index 00000000..35e5a26b --- /dev/null +++ b/test/integration/targets/ansible-test/collection-tests/integration-constraints.sh @@ -0,0 +1,8 @@ +#!/usr/bin/env bash + +set -eux -o pipefail + +cp -a "${TEST_DIR}/ansible_collections" "${WORK_DIR}" +cd "${WORK_DIR}/ansible_collections/ns/col_constraints" + +ansible-test integration --venv --color --truncate 0 "${@}" diff --git a/test/integration/targets/ansible-test/collection-tests/integration.sh b/test/integration/targets/ansible-test/collection-tests/integration.sh new file mode 100755 index 00000000..b257093a --- /dev/null +++ b/test/integration/targets/ansible-test/collection-tests/integration.sh @@ -0,0 +1,8 @@ +#!/usr/bin/env bash + +set -eux -o pipefail + +cp -a "${TEST_DIR}/ansible_collections" "${WORK_DIR}" +cd "${WORK_DIR}/ansible_collections/ns/col" + +ansible-test integration --venv --color --truncate 0 "${@}" diff --git a/test/integration/targets/ansible-test/collection-tests/sanity-vendor.sh b/test/integration/targets/ansible-test/collection-tests/sanity-vendor.sh new file mode 100755 index 00000000..0fcd659b --- /dev/null +++ b/test/integration/targets/ansible-test/collection-tests/sanity-vendor.sh @@ -0,0 +1,25 @@ +#!/usr/bin/env bash + +set -eux -o pipefail + +cp -a "${TEST_DIR}/ansible_collections" "${WORK_DIR}" +cd "${WORK_DIR}/ansible_collections/ns/col" + +"${TEST_DIR}/collection-tests/update-ignore.py" + +vendor_dir="$(python -c 'import pathlib, ansible._vendor; print(pathlib.Path(ansible._vendor.__file__).parent)')" + +cleanup() { + rm -rf "${vendor_dir}/demo/" +} + +trap cleanup EXIT + +# Verify that packages installed in the vendor directory are not available to the import test. +# If they are, the vendor logic will generate a warning which will be turned into an error. +# Testing this requires at least two plugins (not modules) to be run through the import test. + +mkdir "${vendor_dir}/demo/" +touch "${vendor_dir}/demo/__init__.py" + +ansible-test sanity --test import --color --truncate 0 plugins/lookup/vendor1.py plugins/lookup/vendor2.py "${@}" diff --git a/test/integration/targets/ansible-test/collection-tests/sanity.sh b/test/integration/targets/ansible-test/collection-tests/sanity.sh new file mode 100755 index 00000000..21e8607b --- /dev/null +++ b/test/integration/targets/ansible-test/collection-tests/sanity.sh @@ -0,0 +1,10 @@ +#!/usr/bin/env bash + +set -eux -o pipefail + +cp -a "${TEST_DIR}/ansible_collections" "${WORK_DIR}" +cd "${WORK_DIR}/ansible_collections/ns/col" + +"${TEST_DIR}/collection-tests/update-ignore.py" + +ansible-test sanity --color --truncate 0 "${@}" diff --git a/test/integration/targets/ansible-test/collection-tests/units-constraints.sh b/test/integration/targets/ansible-test/collection-tests/units-constraints.sh new file mode 100755 index 00000000..3440eb12 --- /dev/null +++ b/test/integration/targets/ansible-test/collection-tests/units-constraints.sh @@ -0,0 +1,11 @@ +#!/usr/bin/env bash + +set -eux -o pipefail + +cp -a "${TEST_DIR}/ansible_collections" "${WORK_DIR}" +cd "${WORK_DIR}/ansible_collections/ns/col_constraints" + +options=$("${TEST_DIR}"/collection-tests/venv-pythons.py) +IFS=', ' read -r -a pythons <<< "${options}" + +ansible-test units --color --truncate 0 "${pythons[@]}" "${@}" diff --git a/test/integration/targets/ansible-test/collection-tests/units.sh b/test/integration/targets/ansible-test/collection-tests/units.sh new file mode 100755 index 00000000..ecb2e162 --- /dev/null +++ b/test/integration/targets/ansible-test/collection-tests/units.sh @@ -0,0 +1,11 @@ +#!/usr/bin/env bash + +set -eux -o pipefail + +cp -a "${TEST_DIR}/ansible_collections" "${WORK_DIR}" +cd "${WORK_DIR}/ansible_collections/ns/col" + +options=$("${TEST_DIR}"/collection-tests/venv-pythons.py) +IFS=', ' read -r -a pythons <<< "${options}" + +ansible-test units --color --truncate 0 "${pythons[@]}" "${@}" diff --git a/test/integration/targets/ansible-test/collection-tests/unsupported-directory.sh b/test/integration/targets/ansible-test/collection-tests/unsupported-directory.sh new file mode 100755 index 00000000..713bd5d6 --- /dev/null +++ b/test/integration/targets/ansible-test/collection-tests/unsupported-directory.sh @@ -0,0 +1,17 @@ +#!/usr/bin/env bash + +set -eux -o pipefail + +cd "${WORK_DIR}" + +if ansible-test --help 1>stdout 2>stderr; then + echo "ansible-test did not fail" + exit 1 +fi + +grep '^Current working directory: ' stderr + +if grep raise stderr; then + echo "ansible-test failed with a traceback instead of an error message" + exit 2 +fi diff --git a/test/integration/targets/ansible-test/collection-tests/update-ignore.py b/test/integration/targets/ansible-test/collection-tests/update-ignore.py new file mode 100755 index 00000000..51ddf9ac --- /dev/null +++ b/test/integration/targets/ansible-test/collection-tests/update-ignore.py @@ -0,0 +1,51 @@ +#!/usr/bin/env python +"""Rewrite a sanity ignore file to expand Python versions for import ignores and write the file out with the correct Ansible version in the name.""" + +import os +import sys + +from ansible import release + + +def main(): + ansible_root = os.path.dirname(os.path.dirname(os.path.dirname(os.path.abspath(release.__file__)))) + source_root = os.path.join(ansible_root, 'test', 'lib') + + sys.path.insert(0, source_root) + + from ansible_test._internal import constants + + src_path = 'tests/sanity/ignore.txt' + directory = os.path.dirname(src_path) + name, ext = os.path.splitext(os.path.basename(src_path)) + major_minor = '.'.join(release.__version__.split('.')[:2]) + dst_path = os.path.join(directory, f'{name}-{major_minor}{ext}') + + with open(src_path) as src_file: + src_lines = src_file.read().splitlines() + + dst_lines = [] + + for line in src_lines: + path, rule = line.split(' ') + + if rule != 'import': + dst_lines.append(line) + continue + + if path.startswith('plugins/module'): + python_versions = constants.SUPPORTED_PYTHON_VERSIONS + else: + python_versions = constants.CONTROLLER_PYTHON_VERSIONS + + for python_version in python_versions: + dst_lines.append(f'{line}-{python_version}') + + ignores = '\n'.join(dst_lines) + '\n' + + with open(dst_path, 'w') as dst_file: + dst_file.write(ignores) + + +if __name__ == '__main__': + main() diff --git a/test/integration/targets/ansible-test/collection-tests/validate-modules-collection-loader.sh b/test/integration/targets/ansible-test/collection-tests/validate-modules-collection-loader.sh new file mode 100755 index 00000000..3f77a6af --- /dev/null +++ b/test/integration/targets/ansible-test/collection-tests/validate-modules-collection-loader.sh @@ -0,0 +1,14 @@ +#!/usr/bin/env bash + +set -eux -o pipefail + +cp -a "${TEST_DIR}/ansible_collections" "${WORK_DIR}" +cd "${WORK_DIR}/ansible_collections/ns/ps_only" + +if ! command -V pwsh; then + echo "skipping test since pwsh is not available" + exit 0 +fi + +# Use a PowerShell-only collection to verify that validate-modules does not load the collection loader multiple times. +ansible-test sanity --test validate-modules --color --truncate 0 "${@}" diff --git a/test/integration/targets/ansible-test/collection-tests/venv-pythons.py b/test/integration/targets/ansible-test/collection-tests/venv-pythons.py new file mode 100755 index 00000000..ad41b1f5 --- /dev/null +++ b/test/integration/targets/ansible-test/collection-tests/venv-pythons.py @@ -0,0 +1,47 @@ +#!/usr/bin/env python +"""Return target Python options for use with ansible-test.""" + +import os +import shutil +import subprocess +import sys + +from ansible import release + + +def main(): + ansible_root = os.path.dirname(os.path.dirname(os.path.dirname(os.path.abspath(release.__file__)))) + source_root = os.path.join(ansible_root, 'test', 'lib') + + sys.path.insert(0, source_root) + + from ansible_test._internal import constants + + args = [] + + for python_version in constants.SUPPORTED_PYTHON_VERSIONS: + executable = shutil.which(f'python{python_version}') + + if executable: + if python_version == '2.6': + # skip Python 2.6 since it requires docker to provide a PyPI proxy container + print(f'{executable} - skip', file=sys.stderr) + continue + + if python_version.startswith('2.'): + cmd = [executable, '-m', 'virtualenv', '--version'] + else: + cmd = [executable, '-m', 'venv', '--help'] + + process = subprocess.run(cmd, capture_output=True, check=False) + + print(f'{executable} - {"fail" if process.returncode else "pass"}', file=sys.stderr) + + if not process.returncode: + args.extend(['--target-python', f'venv/{python_version}']) + + print(' '.join(args)) + + +if __name__ == '__main__': + main() diff --git a/test/integration/targets/ansible-test/collection-tests/venv.sh b/test/integration/targets/ansible-test/collection-tests/venv.sh deleted file mode 100755 index 42dbfde4..00000000 --- a/test/integration/targets/ansible-test/collection-tests/venv.sh +++ /dev/null @@ -1,49 +0,0 @@ -#!/usr/bin/env bash - -set -eux -o pipefail - -cp -a "${TEST_DIR}/ansible_collections" "${WORK_DIR}" -cd "${WORK_DIR}/ansible_collections/ns/col" - -# rename the sanity ignore file to match the current ansible version and update import ignores with the python version -ansible_version="$(python -c 'import ansible.release; print(".".join(ansible.release.__version__.split(".")[:2]))')" -if [[ "${ANSIBLE_TEST_PYTHON_VERSION}" =~ ^2\. ]] || [[ "${ANSIBLE_TEST_PYTHON_VERSION}" =~ ^3\.[567] ]]; then - # Non-module/module_utils plugins are not checked on these remote-only Python versions - sed "s/ import$/ import-${ANSIBLE_TEST_PYTHON_VERSION}/;" < "tests/sanity/ignore.txt" | grep -v 'plugins/[^m].* import' > "tests/sanity/ignore-${ansible_version}.txt" -else - sed "s/ import$/ import-${ANSIBLE_TEST_PYTHON_VERSION}/;" < "tests/sanity/ignore.txt" > "tests/sanity/ignore-${ansible_version}.txt" -fi -cat "tests/sanity/ignore-${ansible_version}.txt" - -# common args for all tests -# each test will be run in a separate venv to verify that requirements have been properly specified -common=(--venv --python "${ANSIBLE_TEST_PYTHON_VERSION}" --color --truncate 0 "${@}") - -# sanity tests - -tests=() - -set +x - -while IFS='' read -r line; do - tests+=("$line"); -done < <( - ansible-test sanity --list-tests -) - -set -x - -for test in "${tests[@]}"; do - rm -rf "tests/output" - ansible-test sanity "${common[@]}" --test "${test}" -done - -# unit tests - -rm -rf "tests/output" -ansible-test units "${common[@]}" - -# integration tests - -rm -rf "tests/output" -ansible-test integration "${common[@]}" diff --git a/test/integration/targets/blockinfile/meta/main.yml b/test/integration/targets/blockinfile/meta/main.yml index 07faa217..cb6005d0 100644 --- a/test/integration/targets/blockinfile/meta/main.yml +++ b/test/integration/targets/blockinfile/meta/main.yml @@ -1,2 +1,3 @@ dependencies: - prepare_tests + - setup_remote_tmp_dir diff --git a/test/integration/targets/blockinfile/tasks/add_block_to_existing_file.yml b/test/integration/targets/blockinfile/tasks/add_block_to_existing_file.yml index 7093ed2b..c610905c 100644 --- a/test/integration/targets/blockinfile/tasks/add_block_to_existing_file.yml +++ b/test/integration/targets/blockinfile/tasks/add_block_to_existing_file.yml @@ -1,11 +1,11 @@ - name: copy the sshd_config to the test dir copy: src: sshd_config - dest: "{{ output_dir_test }}" + dest: "{{ remote_tmp_dir_test }}" - name: insert/update "Match User" configuration block in sshd_config blockinfile: - path: "{{ output_dir_test }}/sshd_config" + path: "{{ remote_tmp_dir_test }}/sshd_config" block: | Match User ansible-agent PasswordAuthentication no @@ -18,7 +18,7 @@ - "'backup_file' in blockinfile_test0" - name: check content - shell: 'grep -c -e "Match User ansible-agent" -e "PasswordAuthentication no" {{ output_dir_test }}/sshd_config' + shell: 'grep -c -e "Match User ansible-agent" -e "PasswordAuthentication no" {{ remote_tmp_dir_test }}/sshd_config' register: blockinfile_test0_grep - debug: @@ -40,7 +40,7 @@ - name: check idemptotence blockinfile: - path: "{{ output_dir_test }}/sshd_config" + path: "{{ remote_tmp_dir_test }}/sshd_config" block: | Match User ansible-agent PasswordAuthentication no diff --git a/test/integration/targets/blockinfile/tasks/block_without_trailing_newline.yml b/test/integration/targets/blockinfile/tasks/block_without_trailing_newline.yml index 57dac60e..466e86c0 100644 --- a/test/integration/targets/blockinfile/tasks/block_without_trailing_newline.yml +++ b/test/integration/targets/blockinfile/tasks/block_without_trailing_newline.yml @@ -1,6 +1,6 @@ - name: Add block without trailing line separator blockinfile: - path: "{{ output_dir_test }}/chomped_block_test.txt" + path: "{{ remote_tmp_dir_test }}/chomped_block_test.txt" create: yes content: |- one @@ -10,7 +10,7 @@ - name: Add block without trailing line separator again blockinfile: - path: "{{ output_dir_test }}/chomped_block_test.txt" + path: "{{ remote_tmp_dir_test }}/chomped_block_test.txt" content: |- one two @@ -19,7 +19,7 @@ - name: Check output file stat: - path: "{{ output_dir_test }}/chomped_block_test.txt" + path: "{{ remote_tmp_dir_test }}/chomped_block_test.txt" register: chomptest_file - name: Ensure chomptest results are correct diff --git a/test/integration/targets/blockinfile/tasks/create_file.yml b/test/integration/targets/blockinfile/tasks/create_file.yml index 94e47203..c8ded300 100644 --- a/test/integration/targets/blockinfile/tasks/create_file.yml +++ b/test/integration/targets/blockinfile/tasks/create_file.yml @@ -1,6 +1,6 @@ - name: Create a file with blockinfile blockinfile: - path: "{{ output_dir_test }}/empty.txt" + path: "{{ remote_tmp_dir_test }}/empty.txt" block: | Hey there @@ -10,7 +10,7 @@ - name: Run a task that results in an empty file blockinfile: - path: "{{ output_dir_test }}/empty.txt" + path: "{{ remote_tmp_dir_test }}/empty.txt" block: | Hey there @@ -19,7 +19,7 @@ register: empty_test_2 - stat: - path: "{{ output_dir_test }}/empty.txt" + path: "{{ remote_tmp_dir_test }}/empty.txt" register: empty_test_stat - name: Ensure empty file was created diff --git a/test/integration/targets/blockinfile/tasks/diff.yml b/test/integration/targets/blockinfile/tasks/diff.yml index 4a2f9454..56ef08dc 100644 --- a/test/integration/targets/blockinfile/tasks/diff.yml +++ b/test/integration/targets/blockinfile/tasks/diff.yml @@ -1,11 +1,11 @@ - name: Create a test file copy: content: diff test - dest: "{{ output_dir_test }}/diff.txt" + dest: "{{ remote_tmp_dir_test }}/diff.txt" - name: Add block to file with diff blockinfile: - path: "{{ output_dir_test }}/diff.txt" + path: "{{ remote_tmp_dir_test }}/diff.txt" block: | line 1 line 2 diff --git a/test/integration/targets/blockinfile/tasks/file_without_trailing_newline.yml b/test/integration/targets/blockinfile/tasks/file_without_trailing_newline.yml index fe4e2abc..797ffc5b 100644 --- a/test/integration/targets/blockinfile/tasks/file_without_trailing_newline.yml +++ b/test/integration/targets/blockinfile/tasks/file_without_trailing_newline.yml @@ -1,13 +1,13 @@ - name: Create file without trailing newline copy: content: '# File with no newline' - dest: "{{ output_dir_test }}/no_newline_at_end.txt" + dest: "{{ remote_tmp_dir_test }}/no_newline_at_end.txt" register: no_newline - name: Add block to file that does not have a newline at the end blockinfile: - path: "{{ output_dir_test }}/no_newline_at_end.txt" + path: "{{ remote_tmp_dir_test }}/no_newline_at_end.txt" content: | one two @@ -16,7 +16,7 @@ - name: Add block to file that does not have a newline at the end again blockinfile: - path: "{{ output_dir_test }}/no_newline_at_end.txt" + path: "{{ remote_tmp_dir_test }}/no_newline_at_end.txt" content: | one two @@ -25,7 +25,7 @@ - name: Stat the file stat: - path: "{{ output_dir_test }}/no_newline_at_end.txt" + path: "{{ remote_tmp_dir_test }}/no_newline_at_end.txt" register: no_newline_file - name: Ensure block was correctly written to file with no newline at end diff --git a/test/integration/targets/blockinfile/tasks/insertafter.yml b/test/integration/targets/blockinfile/tasks/insertafter.yml index daf7bcf1..a4cdd5f6 100644 --- a/test/integration/targets/blockinfile/tasks/insertafter.yml +++ b/test/integration/targets/blockinfile/tasks/insertafter.yml @@ -1,6 +1,6 @@ - name: Create insertafter test file copy: - dest: "{{ output_dir }}/after.txt" + dest: "{{ remote_tmp_dir }}/after.txt" content: | line1 line2 @@ -8,7 +8,7 @@ - name: Add block using insertafter blockinfile: - path: "{{ output_dir }}/after.txt" + path: "{{ remote_tmp_dir }}/after.txt" insertafter: line2 block: | block1 @@ -17,7 +17,7 @@ - name: Add block using insertafter again blockinfile: - path: "{{ output_dir }}/after.txt" + path: "{{ remote_tmp_dir }}/after.txt" insertafter: line2 block: | block1 @@ -26,7 +26,7 @@ - name: Stat the after.txt file stat: - path: "{{ output_dir }}/after.txt" + path: "{{ remote_tmp_dir }}/after.txt" register: after_file - name: Ensure insertafter worked correctly diff --git a/test/integration/targets/blockinfile/tasks/insertbefore.yml b/test/integration/targets/blockinfile/tasks/insertbefore.yml index 6089af15..03e51c99 100644 --- a/test/integration/targets/blockinfile/tasks/insertbefore.yml +++ b/test/integration/targets/blockinfile/tasks/insertbefore.yml @@ -1,6 +1,6 @@ - name: Create insertbefore test file copy: - dest: "{{ output_dir }}/before.txt" + dest: "{{ remote_tmp_dir }}/before.txt" content: | line1 line2 @@ -8,7 +8,7 @@ - name: Add block using insertbefore blockinfile: - path: "{{ output_dir }}/before.txt" + path: "{{ remote_tmp_dir }}/before.txt" insertbefore: line2 block: | block1 @@ -17,7 +17,7 @@ - name: Add block using insertbefore again blockinfile: - path: "{{ output_dir }}/before.txt" + path: "{{ remote_tmp_dir }}/before.txt" insertbefore: line2 block: | block1 @@ -26,10 +26,10 @@ - name: Stat the before.txt file stat: - path: "{{ output_dir }}/before.txt" + path: "{{ remote_tmp_dir }}/before.txt" register: after_file -- command: cat {{ output_dir }}/before.txt +- command: cat {{ remote_tmp_dir }}/before.txt - name: Ensure insertbefore worked correctly assert: diff --git a/test/integration/targets/blockinfile/tasks/main.yml b/test/integration/targets/blockinfile/tasks/main.yml index 4bc0b8d1..03507684 100644 --- a/test/integration/targets/blockinfile/tasks/main.yml +++ b/test/integration/targets/blockinfile/tasks/main.yml @@ -17,16 +17,16 @@ # along with Ansible. If not, see <http://www.gnu.org/licenses/>. - set_fact: - output_dir_test: "{{ output_dir }}/test_blockinfile" + remote_tmp_dir_test: "{{ remote_tmp_dir }}/test_blockinfile" - name: make sure our testing sub-directory does not exist file: - path: "{{ output_dir_test }}" + path: "{{ remote_tmp_dir_test }}" state: absent - name: create our testing sub-directory file: - path: "{{ output_dir_test }}" + path: "{{ remote_tmp_dir_test }}" state: directory - import_tasks: add_block_to_existing_file.yml diff --git a/test/integration/targets/blockinfile/tasks/preserve_line_endings.yml b/test/integration/targets/blockinfile/tasks/preserve_line_endings.yml index bb2dee29..0528c3bf 100644 --- a/test/integration/targets/blockinfile/tasks/preserve_line_endings.yml +++ b/test/integration/targets/blockinfile/tasks/preserve_line_endings.yml @@ -1,19 +1,19 @@ - name: create line_endings_test.txt in the test dir copy: - dest: "{{ output_dir_test }}/line_endings_test.txt" + dest: "{{ remote_tmp_dir_test }}/line_endings_test.txt" # generating the content like this instead of copying a fixture file # prevents sanity checks from warning about mixed line endings content: "unix\nunix\nunix\n\ndos\r\ndos\r\ndos\r\n\nunix\nunix\n# BEGIN ANSIBLE MANAGED BLOCK\ndos\r\n# END ANSIBLE MANAGED BLOCK\nunix\nunix\nunix\nunix\n" - name: insert/update "dos" configuration block in line_endings_test.txt blockinfile: - path: "{{ output_dir_test }}/line_endings_test.txt" + path: "{{ remote_tmp_dir_test }}/line_endings_test.txt" block: "dos\r\ndos\r\ndos\r\n" register: blockinfile_test2 - name: check content # using the more precise `grep -Pc "^dos\\r$" ...` fails on BSD/macOS - shell: 'grep -c "^dos.$" {{ output_dir_test }}/line_endings_test.txt' + shell: 'grep -c "^dos.$" {{ remote_tmp_dir_test }}/line_endings_test.txt' register: blockinfile_test2_grep - name: validate line_endings_test.txt results diff --git a/test/integration/targets/blockinfile/tasks/validate.yml b/test/integration/targets/blockinfile/tasks/validate.yml index 105bca53..aa7aa636 100644 --- a/test/integration/targets/blockinfile/tasks/validate.yml +++ b/test/integration/targets/blockinfile/tasks/validate.yml @@ -1,6 +1,6 @@ - name: EXPECTED FAILURE test improper validate blockinfile: - path: "{{ output_dir }}/validate.txt" + path: "{{ remote_tmp_dir }}/validate.txt" block: | line1 line2 @@ -10,7 +10,7 @@ - name: EXPECTED FAILURE test failure to validate blockinfile: - path: "{{ output_dir }}/validate.txt" + path: "{{ remote_tmp_dir }}/validate.txt" block: | line1 line2 @@ -20,7 +20,7 @@ - name: Test proper validate blockinfile: - path: "{{ output_dir }}/validate.txt" + path: "{{ remote_tmp_dir }}/validate.txt" block: | line1 line2 diff --git a/test/integration/targets/callback_default/callback_default.out.fqcn_free.stdout b/test/integration/targets/callback_default/callback_default.out.fqcn_free.stdout new file mode 100644 index 00000000..0ec04479 --- /dev/null +++ b/test/integration/targets/callback_default/callback_default.out.fqcn_free.stdout @@ -0,0 +1,35 @@ + +PLAY [nonlockstep] ************************************************************* + +TASK [command] ***************************************************************** +changed: [testhost10] + +TASK [command] ***************************************************************** +changed: [testhost10] + +TASK [command] ***************************************************************** +changed: [testhost10] + +TASK [command] ***************************************************************** +changed: [testhost11] + +TASK [command] ***************************************************************** +changed: [testhost11] + +TASK [command] ***************************************************************** +changed: [testhost11] + +TASK [command] ***************************************************************** +changed: [testhost12] + +TASK [command] ***************************************************************** +changed: [testhost12] + +TASK [command] ***************************************************************** +changed: [testhost12] + +PLAY RECAP ********************************************************************* +testhost10 : ok=3 changed=3 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 +testhost11 : ok=3 changed=3 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 +testhost12 : ok=3 changed=3 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 + diff --git a/test/integration/targets/callback_default/runme.sh b/test/integration/targets/callback_default/runme.sh index f9b60b6b..50b4cf70 100755 --- a/test/integration/targets/callback_default/runme.sh +++ b/test/integration/targets/callback_default/runme.sh @@ -211,4 +211,5 @@ rm -f meta_test.out # Ensure free/host_pinned non-lockstep strategies display correctly diff -u callback_default.out.free.stdout <(ANSIBLE_STRATEGY=free ansible-playbook -i inventory test_non_lockstep.yml 2>/dev/null) +diff -u callback_default.out.fqcn_free.stdout <(ANSIBLE_STRATEGY=ansible.builtin.free ansible-playbook -i inventory test_non_lockstep.yml 2>/dev/null) diff -u callback_default.out.host_pinned.stdout <(ANSIBLE_STRATEGY=host_pinned ansible-playbook -i inventory test_non_lockstep.yml 2>/dev/null) diff --git a/test/integration/targets/collections/collection_root_user/ansible_collections/testns/testcoll/playbooks/roles/non_coll_role/tasks/main.yml b/test/integration/targets/collections/collection_root_user/ansible_collections/testns/testcoll/playbooks/roles/non_coll_role/tasks/main.yml index d41ae90e..3fab7fe9 100644 --- a/test/integration/targets/collections/collection_root_user/ansible_collections/testns/testcoll/playbooks/roles/non_coll_role/tasks/main.yml +++ b/test/integration/targets/collections/collection_root_user/ansible_collections/testns/testcoll/playbooks/roles/non_coll_role/tasks/main.yml @@ -26,4 +26,4 @@ - assert: that: - - test_role_output.msg == test_role_input + - non_coll_role_to_call_test_role_output.msg == test_role_input diff --git a/test/integration/targets/collections/collection_root_user/ansible_collections/testns/testcoll/playbooks/roles/non_coll_role_to_call/tasks/main.yml b/test/integration/targets/collections/collection_root_user/ansible_collections/testns/testcoll/playbooks/roles/non_coll_role_to_call/tasks/main.yml index 98445ce3..2b1c15f2 100644 --- a/test/integration/targets/collections/collection_root_user/ansible_collections/testns/testcoll/playbooks/roles/non_coll_role_to_call/tasks/main.yml +++ b/test/integration/targets/collections/collection_root_user/ansible_collections/testns/testcoll/playbooks/roles/non_coll_role_to_call/tasks/main.yml @@ -1,7 +1,7 @@ - debug: msg: '{{ test_role_input | default("(undefined)") }}' - register: test_role_output + register: non_coll_role_to_call_test_role_output - assert: that: - - test_role_input is not defined or test_role_input == test_role_output.msg + - 'non_coll_role_to_call_test_role_output.msg == "include another non-coll role"' diff --git a/test/integration/targets/connection_ssh/runme.sh b/test/integration/targets/connection_ssh/runme.sh index cbadf1d5..4d430263 100755 --- a/test/integration/targets/connection_ssh/runme.sh +++ b/test/integration/targets/connection_ssh/runme.sh @@ -71,3 +71,7 @@ ansible-playbook check_ssh_defaults.yml "$@" -i test_connection.inventory # ensure we can load from ini cfg ANSIBLE_CONFIG=./test_ssh_defaults.cfg ansible-playbook verify_config.yml "$@" + +# ensure we handle cp with spaces correctly, otherwise would fail with +# `"Failed to connect to the host via ssh: command-line line 0: keyword controlpath extra arguments at end of line"` +ANSIBLE_SSH_CONTROL_PATH='/tmp/ssh cp with spaces' ansible -m ping all -e ansible_connection=ssh -i test_connection.inventory "$@" diff --git a/test/integration/targets/delegate_to/delegate_facts_loop.yml b/test/integration/targets/delegate_to/delegate_facts_loop.yml new file mode 100644 index 00000000..28a1488d --- /dev/null +++ b/test/integration/targets/delegate_to/delegate_facts_loop.yml @@ -0,0 +1,40 @@ +- hosts: localhost + gather_facts: no + tasks: + - set_fact: + test: 123 + delegate_to: "{{ item }}" + delegate_facts: true + loop: "{{ groups['all'] | difference(['localhost']) }}" + + - name: ensure we didnt create it on current host + assert: + that: + - test is undefined + + - name: ensure facts get created + assert: + that: + - "'test' in hostvars[item]" + - hostvars[item]['test'] == 123 + loop: "{{ groups['all'] | difference(['localhost']) }}" + + +- name: test that we don't polute whole group with one value + hosts: localhost + gather_facts: no + vars: + cluster_name: bleh + tasks: + - name: construct different fact per host in loop + set_fact: + vm_name: "{{ cluster_name }}-{{item}}" + delegate_to: "{{ item }}" + delegate_facts: True + with_items: "{{ groups['all'] }}" + + - name: ensure the fact is personalized for each host + assert: + that: + - hostvars[item]['vm_name'].endswith(item) + loop: "{{ groups['all'] }}" diff --git a/test/integration/targets/delegate_to/inventory b/test/integration/targets/delegate_to/inventory index f7ad0a33..ebc33254 100644 --- a/test/integration/targets/delegate_to/inventory +++ b/test/integration/targets/delegate_to/inventory @@ -7,3 +7,11 @@ testhost5 ansible_connection=fakelocal [all:vars] ansible_python_interpreter="{{ ansible_playbook_python }}" + +[delegated_vars] +testhost6 myhost=127.0.0.3 +testhost7 myhost=127.0.0.4 + +[delegated_vars:vars] +ansible_host={{myhost}} +ansible_connection=ssh diff --git a/test/integration/targets/delegate_to/runme.sh b/test/integration/targets/delegate_to/runme.sh index af090cdf..1bdf27cf 100755 --- a/test/integration/targets/delegate_to/runme.sh +++ b/test/integration/targets/delegate_to/runme.sh @@ -48,7 +48,7 @@ ANSIBLE_SSH_ARGS='-C -o ControlMaster=auto -o ControlPersist=60s -o UserKnownHos # this test is not doing what it says it does, also relies on var that should not be available #ansible-playbook test_loop_control.yml -v "$@" -ansible-playbook test_delegate_to_loop_randomness.yml -v "$@" +ansible-playbook test_delegate_to_loop_randomness.yml -i inventory -v "$@" ansible-playbook delegate_and_nolog.yml -i inventory -v "$@" @@ -75,3 +75,4 @@ ansible-playbook resolve_vars.yml -i inventory -v "$@" ansible-playbook test_delegate_to_lookup_context.yml -i inventory -v "$@" ansible-playbook delegate_local_from_root.yml -i inventory -v "$@" -e 'ansible_user=root' ansible-playbook delegate_with_fact_from_delegate_host.yml "$@" +ansible-playbook delegate_facts_loop.yml -i inventory -v "$@" diff --git a/test/integration/targets/delegate_to/test_delegate_to.yml b/test/integration/targets/delegate_to/test_delegate_to.yml index 05b0536e..dcfa9d03 100644 --- a/test/integration/targets/delegate_to/test_delegate_to.yml +++ b/test/integration/targets/delegate_to/test_delegate_to.yml @@ -56,3 +56,27 @@ - name: remove test file file: path={{ output_dir }}/tmp.txt state=absent + + +- name: verify delegation with per host vars + hosts: testhost6 + gather_facts: yes + tasks: + - debug: msg={{ansible_facts['env']}} + + - name: ensure normal facts still work as expected + assert: + that: + - '"127.0.0.3" in ansible_facts["env"]["SSH_CONNECTION"]' + + - name: Test delegate_to with other host defined using same named var + setup: + register: setup_results + delegate_to: testhost7 + + - debug: msg={{setup_results.ansible_facts.ansible_env}} + + - name: verify ssh plugin resolves variable for ansible_host correctly + assert: + that: + - '"127.0.0.4" in setup_results.ansible_facts.ansible_env["SSH_CONNECTION"]' diff --git a/test/integration/targets/dnf/tasks/cacheonly.yml b/test/integration/targets/dnf/tasks/cacheonly.yml index a5c84a37..eb19156c 100644 --- a/test/integration/targets/dnf/tasks/cacheonly.yml +++ b/test/integration/targets/dnf/tasks/cacheonly.yml @@ -8,8 +8,9 @@ state: latest cacheonly: true register: dnf_result + ignore_errors: true -- name: Verify dnf has not changed +- name: Verify dnf failed or has not changed assert: that: - - "not dnf_result is changed" + - "dnf_result is failed or not dnf_result is changed" diff --git a/test/integration/targets/filter_mathstuff/runme.sh b/test/integration/targets/filter_mathstuff/runme.sh index 36503003..fad8443c 100755 --- a/test/integration/targets/filter_mathstuff/runme.sh +++ b/test/integration/targets/filter_mathstuff/runme.sh @@ -11,7 +11,7 @@ source virtualenv.sh # Install Jinja < 2.10 since we want to test the fallback to Ansible's custom # unique filter. Jinja < 2.10 does not have do_unique so we will trigger the # fallback. -pip install 'jinja2 < 2.10' +pip install 'jinja2 < 2.10' 'markupsafe < 2.1' # Run the playbook again in the venv with Jinja < 2.10 ansible-playbook runme.yml "$@" diff --git a/test/integration/targets/filter_urls/runme.sh b/test/integration/targets/filter_urls/runme.sh index f6460acb..2ed1cd84 100755 --- a/test/integration/targets/filter_urls/runme.sh +++ b/test/integration/targets/filter_urls/runme.sh @@ -16,7 +16,7 @@ pip install 'setuptools<45' # Install Jinja 2.6 since we want to test the fallback to Ansible's custom # urlencode functions. Jinja 2.6 does not have urlencode so we will trigger the # fallback. -pip install 'jinja2 >= 2.6, < 2.7' +pip install 'jinja2 >= 2.6, < 2.7' 'markupsafe < 2.1' # Run the playbook again in the venv with Jinja 2.6 ansible-playbook runme.yml "$@" diff --git a/test/integration/targets/git/meta/main.yml b/test/integration/targets/git/meta/main.yml index 34a77cb7..5e461383 100644 --- a/test/integration/targets/git/meta/main.yml +++ b/test/integration/targets/git/meta/main.yml @@ -1,3 +1,4 @@ dependencies: - prepare_tests - setup_gnutar + - setup_remote_tmp_dir diff --git a/test/integration/targets/git/tasks/missing_hostkey.yml b/test/integration/targets/git/tasks/missing_hostkey.yml index 6e4d53c3..136c5d5d 100644 --- a/test/integration/targets/git/tasks/missing_hostkey.yml +++ b/test/integration/targets/git/tasks/missing_hostkey.yml @@ -2,7 +2,7 @@ git: repo: '{{ repo_format2 }}' dest: '{{ checkout_dir }}' - ssh_opts: '-o UserKnownHostsFile={{ output_dir }}/known_hosts' + ssh_opts: '-o UserKnownHostsFile={{ remote_tmp_dir }}/known_hosts' register: git_result ignore_errors: true @@ -16,7 +16,7 @@ dest: '{{ checkout_dir }}' accept_hostkey: true key_file: '{{ github_ssh_private_key }}' - ssh_opts: '-o UserKnownHostsFile={{ output_dir }}/known_hosts' + ssh_opts: '-o UserKnownHostsFile={{ remote_tmp_dir }}/known_hosts' register: git_result when: github_ssh_private_key is defined @@ -38,7 +38,7 @@ version: 'master' accept_hostkey: false # should already have been accepted key_file: '{{ github_ssh_private_key }}' - ssh_opts: '-o UserKnownHostsFile={{ output_dir }}/known_hosts' + ssh_opts: '-o UserKnownHostsFile={{ remote_tmp_dir }}/known_hosts' register: git_result when: github_ssh_private_key is defined @@ -49,7 +49,7 @@ - name: MISSING-HOSTEKY | Remove github.com hostkey from known_hosts lineinfile: - dest: '{{ output_dir }}/known_hosts' + dest: '{{ remote_tmp_dir }}/known_hosts' regexp: "github.com" state: absent when: github_ssh_private_key is defined diff --git a/test/integration/targets/git/tasks/missing_hostkey_acceptnew.yml b/test/integration/targets/git/tasks/missing_hostkey_acceptnew.yml index fb8bb063..3fd19067 100644 --- a/test/integration/targets/git/tasks/missing_hostkey_acceptnew.yml +++ b/test/integration/targets/git/tasks/missing_hostkey_acceptnew.yml @@ -9,7 +9,7 @@ repo: '{{ repo_format2 }}' dest: '{{ checkout_dir }}' accept_newhostkey: true - ssh_opts: '-o UserKnownHostsFile={{ output_dir }}/known_hosts' + ssh_opts: '-o UserKnownHostsFile={{ remote_tmp_dir }}/known_hosts' register: git_result ignore_errors: true @@ -24,7 +24,7 @@ git: repo: '{{ repo_format2 }}' dest: '{{ checkout_dir }}' - ssh_opts: '-o UserKnownHostsFile={{ output_dir }}/known_hosts' + ssh_opts: '-o UserKnownHostsFile={{ remote_tmp_dir }}/known_hosts' register: git_result ignore_errors: true @@ -39,7 +39,7 @@ dest: '{{ checkout_dir }}' accept_newhostkey: true key_file: '{{ github_ssh_private_key }}' - ssh_opts: '-o UserKnownHostsFile={{ output_dir }}/known_hosts' + ssh_opts: '-o UserKnownHostsFile={{ remote_tmp_dir }}/known_hosts' register: git_result - assert: @@ -58,7 +58,7 @@ version: 'master' accept_newhostkey: false # should already have been accepted key_file: '{{ github_ssh_private_key }}' - ssh_opts: '-o UserKnownHostsFile={{ output_dir }}/known_hosts' + ssh_opts: '-o UserKnownHostsFile={{ remote_tmp_dir }}/known_hosts' register: git_result - assert: @@ -67,7 +67,7 @@ - name: MISSING-HOSTEKY | Remove github.com hostkey from known_hosts lineinfile: - dest: '{{ output_dir }}/known_hosts' + dest: '{{ remote_tmp_dir }}/known_hosts' regexp: "github.com" state: absent diff --git a/test/integration/targets/git/tasks/setup.yml b/test/integration/targets/git/tasks/setup.yml index 3158bf62..06511053 100644 --- a/test/integration/targets/git/tasks/setup.yml +++ b/test/integration/targets/git/tasks/setup.yml @@ -1,11 +1,11 @@ -- name: SETUP | clean out the output_dir +- name: SETUP | clean out the remote_tmp_dir file: - path: "{{ output_dir }}" + path: "{{ remote_tmp_dir }}" state: absent -- name: SETUP | create clean output_dir +- name: SETUP | create clean remote_tmp_dir file: - path: "{{ output_dir }}" + path: "{{ remote_tmp_dir }}" state: directory - name: SETUP | install git diff --git a/test/integration/targets/git/vars/main.yml b/test/integration/targets/git/vars/main.yml index a1bbfca9..b38531f3 100644 --- a/test/integration/targets/git/vars/main.yml +++ b/test/integration/targets/git/vars/main.yml @@ -27,9 +27,9 @@ git_list_commands: tgz: tar -tf zip: unzip -Z1 -checkout_dir: '{{ output_dir }}/git' -repo_dir: '{{ output_dir }}/local_repos' -separate_git_dir: '{{ output_dir }}/sep_git_dir' +checkout_dir: '{{ remote_tmp_dir }}/git' +repo_dir: '{{ remote_tmp_dir }}/local_repos' +separate_git_dir: '{{ remote_tmp_dir }}/sep_git_dir' repo_format1: 'https://github.com/jimi-c/test_role' repo_format2: 'git@github.com:jimi-c/test_role.git' repo_format3: 'ssh://git@github.com/jimi-c/test_role.git' diff --git a/test/integration/targets/groupby_filter/runme.sh b/test/integration/targets/groupby_filter/runme.sh index 09b47d55..9c9c6f03 100755 --- a/test/integration/targets/groupby_filter/runme.sh +++ b/test/integration/targets/groupby_filter/runme.sh @@ -7,10 +7,10 @@ source virtualenv.sh # Update pip in the venv to a version that supports constraints pip install --requirement requirements.txt -pip install -U jinja2==2.9.4 --constraint "../../../lib/ansible_test/_data/requirements/constraints.txt" +pip install -U jinja2==2.9.4 "markupsafe<2.1.0" --constraint "../../../lib/ansible_test/_data/requirements/constraints.txt" ansible-playbook -i ../../inventory test_jinja2_groupby.yml -v "$@" -pip install -U "jinja2<2.9.0" --constraint "../../../lib/ansible_test/_data/requirements/constraints.txt" +pip install -U "jinja2<2.9.0" "markupsafe<2.1.0" --constraint "../../../lib/ansible_test/_data/requirements/constraints.txt" ansible-playbook -i ../../inventory test_jinja2_groupby.yml -v "$@" diff --git a/test/integration/targets/incidental_setup_mongodb/defaults/main.yml b/test/integration/targets/incidental_setup_mongodb/defaults/main.yml index b205013c..de0b76d3 100644 --- a/test/integration/targets/incidental_setup_mongodb/defaults/main.yml +++ b/test/integration/targets/incidental_setup_mongodb/defaults/main.yml @@ -42,5 +42,5 @@ redhat_packages_py3: # Do not install requests[security] via pip. It will cause test failures. # See https://github.com/ansible/ansible/pull/66319 pip_packages: - - psutil - - pymongo + - psutil==5.8.0 + - pymongo==3.12.2 diff --git a/test/integration/targets/jinja_plugins/collections/ansible_collections/foo/bar/plugins/filter/bad_collection_filter2.py b/test/integration/targets/jinja_plugins/collections/ansible_collections/foo/bar/plugins/filter/bad_collection_filter2.py new file mode 100644 index 00000000..96e726ac --- /dev/null +++ b/test/integration/targets/jinja_plugins/collections/ansible_collections/foo/bar/plugins/filter/bad_collection_filter2.py @@ -0,0 +1,10 @@ +# Copyright (c) 2021 Matt Martz <matt@sivel.net> +# GNU General Public License v3.0+ (see COPYING or https://www.gnu.org/licenses/gpl-3.0.txt) + +# Make coding more python3-ish +from __future__ import (absolute_import, division, print_function) +__metaclass__ = type + + +class FilterModule: + pass diff --git a/test/integration/targets/jinja_plugins/tasks/main.yml b/test/integration/targets/jinja_plugins/tasks/main.yml index 012ec954..013baecb 100644 --- a/test/integration/targets/jinja_plugins/tasks/main.yml +++ b/test/integration/targets/jinja_plugins/tasks/main.yml @@ -17,6 +17,8 @@ - | result.stderr|regex_findall('bad_test')|length == 2 - | - result.stderr|regex_findall('bad_collection_filter')|length == 2 + result.stderr|regex_findall('bad_collection_filter')|length == 3 + - | + result.stderr|regex_findall('bad_collection_filter2')|length == 1 - | result.stderr|regex_findall('bad_collection_test')|length == 2 diff --git a/test/integration/targets/lookup_template/tasks/main.yml b/test/integration/targets/lookup_template/tasks/main.yml index 36a8ee31..9ebdf0c5 100644 --- a/test/integration/targets/lookup_template/tasks/main.yml +++ b/test/integration/targets/lookup_template/tasks/main.yml @@ -25,3 +25,10 @@ - assert: that: - "hello_world_comment|trim == 'Hello world!'" + +# 77004 +- assert: + that: + - lookup('template', 'dict.j2') is mapping + - lookup('template', 'dict.j2', convert_data=True) is mapping + - lookup('template', 'dict.j2', convert_data=False) is not mapping diff --git a/test/integration/targets/lookup_template/templates/dict.j2 b/test/integration/targets/lookup_template/templates/dict.j2 new file mode 100644 index 00000000..0439155b --- /dev/null +++ b/test/integration/targets/lookup_template/templates/dict.j2 @@ -0,0 +1 @@ +{"foo": "{{ 'bar' }}"} diff --git a/test/integration/targets/meta_tasks/runme.sh b/test/integration/targets/meta_tasks/runme.sh index f5916ec7..c29579bf 100755 --- a/test/integration/targets/meta_tasks/runme.sh +++ b/test/integration/targets/meta_tasks/runme.sh @@ -55,6 +55,13 @@ for test_strategy in linear free; do [ "$(grep -c "Testing end_play on host" <<< "$out" )" -eq 1 ] grep -q "META: ending play" <<< "$out" grep -qv 'Failed to end using end_play' <<< "$out" + + out="$(ansible-playbook test_end_play_multiple_plays.yml -i inventory.yml -e test_strategy=$test_strategy -vv "$@")" + + grep -q "META: ending play" <<< "$out" + grep -q "Play 1" <<< "$out" + grep -q "Play 2" <<< "$out" + grep -qv 'Failed to end using end_play' <<< "$out" done # test end_batch meta task diff --git a/test/integration/targets/meta_tasks/test_end_play_multiple_plays.yml b/test/integration/targets/meta_tasks/test_end_play_multiple_plays.yml new file mode 100644 index 00000000..2cc8d1e6 --- /dev/null +++ b/test/integration/targets/meta_tasks/test_end_play_multiple_plays.yml @@ -0,0 +1,18 @@ +- name: Testing end_play with multiple plays with strategy {{ test_strategy | default('linear') }} + hosts: testhost + gather_facts: no + strategy: "{{ test_strategy | default('linear') }}" + tasks: + - debug: + msg: "Play 1" + - meta: end_play + - fail: + msg: 'Failed to end using end_play' + +- name: Testing end_play with multiple plays with strategy {{ test_strategy | default('linear') }} + hosts: testhost + gather_facts: no + strategy: "{{ test_strategy | default('linear') }}" + tasks: + - debug: + msg: "Play 2" diff --git a/test/integration/targets/pip/tasks/pip.yml b/test/integration/targets/pip/tasks/pip.yml index 2b9ad561..2ffb3dfa 100644 --- a/test/integration/targets/pip/tasks/pip.yml +++ b/test/integration/targets/pip/tasks/pip.yml @@ -580,27 +580,24 @@ # https://github.com/ansible/ansible/issues/68592 # Handle pre-release version numbers in check_mode for already-installed # packages. -# TODO: Limiting to py3 test boxes for now so the example of 'black' installs, -# we should probably find another package to use with a similar versioning -# scheme or make a small one and enable this test for py2 as well. - block: - - name: Install a beta version of a package + - name: Install a pre-release version of a package pip: - name: black - version: 19.10b0 + name: fallible + version: 0.0.1a2 state: present - name: Use check_mode and ensure that the package is shown as installed check_mode: true pip: - name: black + name: fallible state: present register: pip_prereleases - - name: Uninstall the beta package if we need to + - name: Uninstall the pre-release package if we need to pip: - name: black - version: 19.10b0 + name: fallible + version: 0.0.1a2 state: absent when: pip_prereleases is changed @@ -608,6 +605,4 @@ that: - pip_prereleases is successful - pip_prereleases is not changed - - '"black==19.10b0" in pip_prereleases.stdout_lines' - - when: ansible_python.version.major == 3 + - '"fallible==0.0.1a2" in pip_prereleases.stdout_lines' diff --git a/test/integration/targets/roles_arg_spec/roles/test1/meta/argument_specs.yml b/test/integration/targets/roles_arg_spec/roles/test1/meta/argument_specs.yml index 02edac66..427946e5 100644 --- a/test/integration/targets/roles_arg_spec/roles/test1/meta/argument_specs.yml +++ b/test/integration/targets/roles_arg_spec/roles/test1/meta/argument_specs.yml @@ -73,6 +73,11 @@ argument_specs: some_second_level: type: "bool" default: true + some_more_dict_options: + type: "dict" + options: + some_second_level: + type: "str" some_str_removed_in: type: "str" removed_in: 2.10 diff --git a/test/integration/targets/roles_arg_spec/test_complex_role_fails.yml b/test/integration/targets/roles_arg_spec/test_complex_role_fails.yml index a04785fb..923e92f7 100644 --- a/test/integration/targets/roles_arg_spec/test_complex_role_fails.yml +++ b/test/integration/targets/roles_arg_spec/test_complex_role_fails.yml @@ -34,7 +34,10 @@ "value of test1_choices must be one of: this paddle game, the astray, this remote control, the chair, got: My dog", "value of some_choices must be one of: choice1, choice2, got: choice4", "argument 'some_second_level' is of type <class 'ansible.parsing.yaml.objects.AnsibleUnicode'> found in 'some_dict_options'. and we were unable to convert to bool: The value 'not-a-bool' is not a valid boolean. ", - "argument 'third_level' is of type <class 'ansible.parsing.yaml.objects.AnsibleUnicode'> found in 'multi_level_option -> second_level'. and we were unable to convert to int: <class 'ansible.parsing.yaml.objects.AnsibleUnicode'> cannot be converted to an int" + "argument 'third_level' is of type <class 'ansible.parsing.yaml.objects.AnsibleUnicode'> found in 'multi_level_option -> second_level'. and we were unable to convert to int: <class 'ansible.parsing.yaml.objects.AnsibleUnicode'> cannot be converted to an int", + "argument 'some_more_dict_options' is of type <class 'ansible.parsing.yaml.objects.AnsibleUnicode'> and we were unable to convert to dict: dictionary requested, could not parse JSON or key=value", + "value of 'some_more_dict_options' must be of type dict or list of dicts", + "dictionary requested, could not parse JSON or key=value", ] tasks: @@ -86,6 +89,7 @@ some_str_removed_in: "foo" some_dict_options: some_second_level: "not-a-bool" + some_more_dict_options: "not-a-dict" multi_level_option: second_level: third_level: "should_be_int" diff --git a/test/integration/targets/setup_paramiko/install-FreeBSD-python-3.yml b/test/integration/targets/setup_paramiko/install-FreeBSD-python-3.yml index 27daf3cf..f737fe30 100644 --- a/test/integration/targets/setup_paramiko/install-FreeBSD-python-3.yml +++ b/test/integration/targets/setup_paramiko/install-FreeBSD-python-3.yml @@ -4,3 +4,5 @@ pip: # no package in pkg, just use pip name: paramiko extra_args: "-c {{ remote_constraints }}" + environment: + SETUPTOOLS_USE_DISTUTILS: stdlib diff --git a/test/integration/targets/setup_paramiko/install-RedHat-8-python-3.yml b/test/integration/targets/setup_paramiko/install-RedHat-8-python-3.yml index 19fd3f63..55677f21 100644 --- a/test/integration/targets/setup_paramiko/install-RedHat-8-python-3.yml +++ b/test/integration/targets/setup_paramiko/install-RedHat-8-python-3.yml @@ -4,3 +4,5 @@ pip: # no python3-paramiko package exists for RHEL 8 name: paramiko extra_args: "-c {{ remote_constraints }}" + environment: + SETUPTOOLS_USE_DISTUTILS: stdlib diff --git a/test/integration/targets/template/tasks/main.yml b/test/integration/targets/template/tasks/main.yml index f8848ef5..14ef6180 100644 --- a/test/integration/targets/template/tasks/main.yml +++ b/test/integration/targets/template/tasks/main.yml @@ -250,11 +250,6 @@ # VERIFY CONTENTS -- name: check what python version ansible is running on - command: "{{ ansible_python.executable }} -c 'import distutils.sysconfig ; print(distutils.sysconfig.get_python_version())'" - register: pyver - delegate_to: localhost - - name: copy known good into place copy: src=foo.txt dest={{output_dir}}/foo.txt diff --git a/test/integration/targets/unarchive/tasks/main.yml b/test/integration/targets/unarchive/tasks/main.yml index 035a5561..baa2a8cf 100644 --- a/test/integration/targets/unarchive/tasks/main.yml +++ b/test/integration/targets/unarchive/tasks/main.yml @@ -17,3 +17,4 @@ - import_tasks: test_symlink.yml - import_tasks: test_download.yml - import_tasks: test_unprivileged_user.yml +- import_tasks: test_different_language_var.yml diff --git a/test/integration/targets/unarchive/tasks/test_different_language_var.yml b/test/integration/targets/unarchive/tasks/test_different_language_var.yml new file mode 100644 index 00000000..1d7d3f60 --- /dev/null +++ b/test/integration/targets/unarchive/tasks/test_different_language_var.yml @@ -0,0 +1,41 @@ +- name: test non-ascii with different LANGUAGE + when: ansible_os_family == 'Debian' + block: + - name: install de language pack + apt: + name: language-pack-de + state: present + + - name: create our unarchive destination + file: + path: "{{ remote_tmp_dir }}/test-unarchive-nonascii-ãらã¨ã¿-tar-gz" + state: directory + + - name: test that unarchive works with an archive that contains non-ascii filenames + unarchive: + # Both the filename of the tarball and the filename inside the tarball have + # nonascii chars + src: "test-unarchive-nonascii-ãらã¨ã¿.tar.gz" + dest: "{{ remote_tmp_dir }}/test-unarchive-nonascii-ãらã¨ã¿-tar-gz" + mode: "u+rwX,go+rX" + remote_src: no + register: nonascii_result0 + + - name: Check that file is really there + stat: + path: "{{ remote_tmp_dir }}/test-unarchive-nonascii-ãらã¨ã¿-tar-gz/storage/aÌ€âæçeÌeÌ€ïiÌ‚oÌ‚Å“(copy)!@#$%^&-().jpg" + register: nonascii_stat0 + + - name: Assert that nonascii tests succeeded + assert: + that: + - "nonascii_result0.changed == true" + - "nonascii_stat0.stat.exists == true" + + - name: remove nonascii test + file: + path: "{{ remote_tmp_dir }}/test-unarchive-nonascii-ãらã¨ã¿-tar-gz" + state: absent + + environment: + LANGUAGE: de_DE:en
\ No newline at end of file diff --git a/test/integration/targets/unarchive/tasks/test_exclude.yml b/test/integration/targets/unarchive/tasks/test_exclude.yml index bf9f14fb..8d3183c3 100644 --- a/test/integration/targets/unarchive/tasks/test_exclude.yml +++ b/test/integration/targets/unarchive/tasks/test_exclude.yml @@ -11,13 +11,28 @@ src: "{{ remote_tmp_dir }}/unarchive-00.{{item}}" dest: "{{ remote_tmp_dir }}/exclude-{{item}}" remote_src: yes + list_files: yes exclude: - "exclude/exclude-*.txt" - "other/exclude-1.ext" + register: result_of_unarchive with_items: - zip - tar +- name: Make sure unarchive module reported back extracted files + assert: + that: + - "'include/include-1.txt' in item.files" + - "'include/include-2.txt' in item.files" + - "'include/include-3.txt' in item.files" + - "'other/include-1.ext' in item.files" + - "'other/include-2.ext' in item.files" + - "'other/exclude-2.ext' in item.files" + - "'other/other-1.ext' in item.files" + - "'other/other-2.ext' in item.files" + loop: "{{ result_of_unarchive.results }}" + - name: verify that the file was unarchived shell: find {{ remote_tmp_dir }}/exclude-{{item}} chdir={{ remote_tmp_dir }} register: unarchive00 diff --git a/test/integration/targets/uri/tasks/main.yml b/test/integration/targets/uri/tasks/main.yml index 700e7f10..755cd432 100644 --- a/test/integration/targets/uri/tasks/main.yml +++ b/test/integration/targets/uri/tasks/main.yml @@ -19,8 +19,8 @@ - name: set role facts set_fact: http_port: 15260 - files_dir: '{{ output_dir|expanduser }}/files' - checkout_dir: '{{ output_dir }}/git' + files_dir: '{{ remote_tmp_dir|expanduser }}/files' + checkout_dir: '{{ remote_tmp_dir }}/git' - name: create a directory to serve files from file: @@ -39,10 +39,10 @@ - copy: src: "testserver.py" - dest: "{{ output_dir }}/testserver.py" + dest: "{{ remote_tmp_dir }}/testserver.py" - name: start SimpleHTTPServer - shell: cd {{ files_dir }} && {{ ansible_python.executable }} {{ output_dir}}/testserver.py {{ http_port }} + shell: cd {{ files_dir }} && {{ ansible_python.executable }} {{ remote_tmp_dir}}/testserver.py {{ http_port }} async: 120 # this test set can take ~1m to run on FreeBSD (via Shippable) poll: 0 @@ -91,12 +91,12 @@ - name: test https fetch to a site with mismatched hostname and certificate uri: url: "https://{{ badssl_host }}/" - dest: "{{ output_dir }}/shouldnotexist.html" + dest: "{{ remote_tmp_dir }}/shouldnotexist.html" ignore_errors: True register: result - stat: - path: "{{ output_dir }}/shouldnotexist.html" + path: "{{ remote_tmp_dir }}/shouldnotexist.html" register: stat_result - name: Assert that the file was not downloaded @@ -111,18 +111,18 @@ - name: Clean up any cruft from the results directory file: - name: "{{ output_dir }}/kreitz.html" + name: "{{ remote_tmp_dir }}/kreitz.html" state: absent - name: test https fetch to a site with mismatched hostname and certificate and validate_certs=no uri: url: "https://{{ badssl_host }}/" - dest: "{{ output_dir }}/kreitz.html" + dest: "{{ remote_tmp_dir }}/kreitz.html" validate_certs: no register: result - stat: - path: "{{ output_dir }}/kreitz.html" + path: "{{ remote_tmp_dir }}/kreitz.html" register: stat_result - name: Assert that the file was downloaded @@ -139,13 +139,13 @@ - name: test https fetch to a site with self signed certificate using ca_path uri: url: "https://{{ self_signed_host }}:444/" - dest: "{{ output_dir }}/self-signed_using_ca_path.html" + dest: "{{ remote_tmp_dir }}/self-signed_using_ca_path.html" ca_path: "{{ remote_tmp_dir }}/ca2cert.pem" validate_certs: yes register: result - stat: - path: "{{ output_dir }}/self-signed_using_ca_path.html" + path: "{{ remote_tmp_dir }}/self-signed_using_ca_path.html" register: stat_result - name: Assert that the file was downloaded @@ -157,13 +157,13 @@ - name: test https fetch to a site with self signed certificate without using ca_path uri: url: "https://{{ self_signed_host }}:444/" - dest: "{{ output_dir }}/self-signed-without_using_ca_path.html" + dest: "{{ remote_tmp_dir }}/self-signed-without_using_ca_path.html" validate_certs: yes register: result ignore_errors: true - stat: - path: "{{ output_dir }}/self-signed-without_using_ca_path.html" + path: "{{ remote_tmp_dir }}/self-signed-without_using_ca_path.html" register: stat_result - name: Assure that https access to a host with self-signed certificate without providing ca_path fails @@ -653,16 +653,16 @@ - name: Create a testing file copy: content: "content" - dest: "{{ output_dir }}/output" + dest: "{{ remote_tmp_dir }}/output" - name: Download a file from non existing location uri: url: http://does/not/exist - dest: "{{ output_dir }}/output" + dest: "{{ remote_tmp_dir }}/output" ignore_errors: yes - name: Save testing file's output - command: "cat {{ output_dir }}/output" + command: "cat {{ remote_tmp_dir }}/output" register: file_out - name: Test the testing file was not overwritten @@ -672,7 +672,7 @@ - name: Clean up file: - dest: "{{ output_dir }}/output" + dest: "{{ remote_tmp_dir }}/output" state: absent - name: Test follow_redirects=none diff --git a/test/integration/targets/uri/tasks/unexpected-failures.yml b/test/integration/targets/uri/tasks/unexpected-failures.yml index ac38871c..f00380ab 100644 --- a/test/integration/targets/uri/tasks/unexpected-failures.yml +++ b/test/integration/targets/uri/tasks/unexpected-failures.yml @@ -1,6 +1,6 @@ --- # same as expanduser & expandvars called on managed host -- command: 'echo {{ output_dir }}' +- command: 'echo {{ remote_tmp_dir }}' register: echo - set_fact: @@ -8,13 +8,13 @@ - name: ensure test directory doesn't exist file: - path: '{{ output_dir }}/non/existent/path' + path: '{{ remote_tmp_dir }}/non/existent/path' state: absent - name: destination doesn't exist uri: url: 'https://{{ httpbin_host }}/get' - dest: '{{ output_dir }}/non/existent/path' + dest: '{{ remote_tmp_dir }}/non/existent/path' ignore_errors: true register: ret diff --git a/test/integration/targets/user/tasks/test_ssh_key_passphrase.yml b/test/integration/targets/user/tasks/test_ssh_key_passphrase.yml index bb0486da..f0725ed6 100644 --- a/test/integration/targets/user/tasks/test_ssh_key_passphrase.yml +++ b/test/integration/targets/user/tasks/test_ssh_key_passphrase.yml @@ -10,11 +10,12 @@ state: present generate_ssh_key: yes force: yes - ssh_key_file: "{{ output_dir }}/test_id_rsa" + ssh_key_file: .ssh/test_id_rsa ssh_key_passphrase: secret_passphrase + register: ansibulluser_create_with_ssh_key - name: Unlock ssh key - command: "ssh-keygen -y -f {{ output_dir }}/test_id_rsa -P secret_passphrase" + command: "ssh-keygen -y -f {{ ansibulluser_create_with_ssh_key.ssh_key_file|quote }} -P secret_passphrase" register: result - name: Check that ssh key was unlocked successfully @@ -24,6 +25,6 @@ - name: Clean ssh key file: - path: "{{ output_dir }}/test_id_rsa" + path: "{{ ansibulluser_create_with_ssh_key.ssh_key_file }}" state: absent when: ansible_os_family == 'FreeBSD' diff --git a/test/integration/targets/var_inheritance/aliases b/test/integration/targets/var_inheritance/aliases new file mode 100644 index 00000000..498fedd5 --- /dev/null +++ b/test/integration/targets/var_inheritance/aliases @@ -0,0 +1,2 @@ +shippable/posix/group4 +context/controller diff --git a/test/integration/targets/var_inheritance/tasks/main.yml b/test/integration/targets/var_inheritance/tasks/main.yml new file mode 100644 index 00000000..48d7b3d3 --- /dev/null +++ b/test/integration/targets/var_inheritance/tasks/main.yml @@ -0,0 +1,16 @@ +- name: outer + vars: + myvar: abc + block: + - assert: + that: + - "myvar == 'abc'" + + - name: inner block + vars: + myvar: 123 + block: + + - assert: + that: + - myvar|int == 123 diff --git a/test/integration/targets/wait_for/tasks/main.yml b/test/integration/targets/wait_for/tasks/main.yml index 67e07786..1af08924 100644 --- a/test/integration/targets/wait_for/tasks/main.yml +++ b/test/integration/targets/wait_for/tasks/main.yml @@ -150,7 +150,7 @@ - name: install psutil using pip (non-Linux only) pip: - name: psutil + name: psutil==5.8.0 when: ansible_system != 'Linux' - name: Copy zombie.py diff --git a/test/lib/ansible_test/_data/completion/docker.txt b/test/lib/ansible_test/_data/completion/docker.txt index cbb4c362..05d173a6 100644 --- a/test/lib/ansible_test/_data/completion/docker.txt +++ b/test/lib/ansible_test/_data/completion/docker.txt @@ -1,7 +1,7 @@ base image=quay.io/ansible/base-test-container:1.1.0 python=3.9,2.6,2.7,3.5,3.6,3.7,3.8,3.10 seccomp=unconfined -default image=quay.io/ansible/default-test-container:4.1.0 python=3.9,2.6,2.7,3.5,3.6,3.7,3.8,3.10 seccomp=unconfined context=collection -default image=quay.io/ansible/ansible-core-test-container:4.1.0 python=3.9,2.6,2.7,3.5,3.6,3.7,3.8,3.10 seccomp=unconfined context=ansible-core -alpine3 image=quay.io/ansible/alpine3-test-container:3.1.0 python=3.9 +default image=quay.io/ansible/default-test-container:4.2.0 python=3.9,2.6,2.7,3.5,3.6,3.7,3.8,3.10 seccomp=unconfined context=collection +default image=quay.io/ansible/ansible-core-test-container:4.2.0 python=3.9,2.6,2.7,3.5,3.6,3.7,3.8,3.10 seccomp=unconfined context=ansible-core +alpine3 image=quay.io/ansible/alpine3-test-container:3.3.0 python=3.9 centos6 image=quay.io/ansible/centos6-test-container:3.1.0 python=2.6 seccomp=unconfined centos7 image=quay.io/ansible/centos7-test-container:3.1.0 python=2.7 seccomp=unconfined centos8 image=quay.io/ansible/centos8-test-container:3.1.0 python=3.6 seccomp=unconfined diff --git a/test/lib/ansible_test/_data/requirements/sanity.import.plugin.txt b/test/lib/ansible_test/_data/requirements/sanity.import.plugin.txt new file mode 100644 index 00000000..76d16725 --- /dev/null +++ b/test/lib/ansible_test/_data/requirements/sanity.import.plugin.txt @@ -0,0 +1,12 @@ +jinja2 == 3.0.1 +PyYAML == 5.4.1 +cryptography == 3.3.2 +packaging == 21.0 +resolvelib == 0.5.4 + +# dependencies +MarkupSafe == 2.0.1 +cffi == 1.15.0 +pycparser == 2.20 +pyparsing == 2.4.7 +six == 1.16.0 diff --git a/test/lib/ansible_test/_data/requirements/sanity.import.txt b/test/lib/ansible_test/_data/requirements/sanity.import.txt new file mode 100644 index 00000000..d77a09d7 --- /dev/null +++ b/test/lib/ansible_test/_data/requirements/sanity.import.txt @@ -0,0 +1 @@ +pyyaml == 5.4.1 # needed for yaml_to_json.py diff --git a/test/lib/ansible_test/_data/requirements/units.txt b/test/lib/ansible_test/_data/requirements/units.txt index d723a65f..d2f56d35 100644 --- a/test/lib/ansible_test/_data/requirements/units.txt +++ b/test/lib/ansible_test/_data/requirements/units.txt @@ -2,4 +2,5 @@ mock pytest pytest-mock pytest-xdist +pytest-forked pyyaml # required by the collection loader (only needed for collections) diff --git a/test/lib/ansible_test/_internal/cli/compat.py b/test/lib/ansible_test/_internal/cli/compat.py index cf6c01f1..2090aac7 100644 --- a/test/lib/ansible_test/_internal/cli/compat.py +++ b/test/lib/ansible_test/_internal/cli/compat.py @@ -26,8 +26,8 @@ from ..docker_util import ( ) from ..completion import ( - DOCKER_COMPLETION, - REMOTE_COMPLETION, + docker_completion, + remote_completion, filter_completion, ) @@ -68,7 +68,7 @@ def controller_python(version): # type: (t.Optional[str]) -> t.Optional[str] def get_fallback_remote_controller(): # type: () -> str """Return the remote fallback platform for the controller.""" platform = 'freebsd' # lower cost than RHEL and macOS - candidates = [item for item in filter_completion(REMOTE_COMPLETION).values() if item.controller_supported and item.platform == platform] + candidates = [item for item in filter_completion(remote_completion()).values() if item.controller_supported and item.platform == platform] fallback = sorted(candidates, key=lambda value: str_to_version(value.version), reverse=True)[0] return fallback.name @@ -316,7 +316,7 @@ def get_legacy_host_config( targets = [ControllerConfig(python=VirtualPythonConfig(version=options.python or 'default', system_site_packages=options.venv_system_site_packages))] elif options.docker: - docker_config = filter_completion(DOCKER_COMPLETION).get(options.docker) + docker_config = filter_completion(docker_completion()).get(options.docker) if docker_config: if options.python and options.python not in docker_config.supported_pythons: @@ -350,7 +350,7 @@ def get_legacy_host_config( targets = [DockerConfig(name=options.docker, python=native_python(options), privileged=options.docker_privileged, seccomp=options.docker_seccomp, memory=options.docker_memory)] elif options.remote: - remote_config = filter_completion(REMOTE_COMPLETION).get(options.remote) + remote_config = filter_completion(remote_completion()).get(options.remote) context, reason = None, None if remote_config: diff --git a/test/lib/ansible_test/_internal/cli/environments.py b/test/lib/ansible_test/_internal/cli/environments.py index 640ff56b..3c0230ca 100644 --- a/test/lib/ansible_test/_internal/cli/environments.py +++ b/test/lib/ansible_test/_internal/cli/environments.py @@ -14,10 +14,10 @@ from ..constants import ( ) from ..completion import ( - DOCKER_COMPLETION, - NETWORK_COMPLETION, - REMOTE_COMPLETION, - WINDOWS_COMPLETION, + docker_completion, + network_completion, + remote_completion, + windows_completion, filter_completion, ) @@ -425,9 +425,9 @@ def add_environment_docker( ): # type: (...) -> None """Add environment arguments for running in docker containers.""" if target_mode in (TargetMode.POSIX_INTEGRATION, TargetMode.SHELL): - docker_images = sorted(filter_completion(DOCKER_COMPLETION)) + docker_images = sorted(filter_completion(docker_completion())) else: - docker_images = sorted(filter_completion(DOCKER_COMPLETION, controller_only=True)) + docker_images = sorted(filter_completion(docker_completion(), controller_only=True)) exclusive_parser.add_argument( '--docker', @@ -538,7 +538,7 @@ def complete_windows(prefix, parsed_args, **_): # type: (str, argparse.Namespac def complete_network_platform(prefix, parsed_args, **_): # type: (str, argparse.Namespace, ...) -> t.List[str] """Return a list of supported network platforms matching the given prefix, excluding platforms already parsed from the command line.""" - images = sorted(filter_completion(NETWORK_COMPLETION)) + images = sorted(filter_completion(network_completion())) return [i for i in images if i.startswith(prefix) and (not parsed_args.platform or i not in parsed_args.platform)] @@ -546,7 +546,7 @@ def complete_network_platform(prefix, parsed_args, **_): # type: (str, argparse def complete_network_platform_collection(prefix, parsed_args, **_): # type: (str, argparse.Namespace, ...) -> t.List[str] """Return a list of supported network platforms matching the given prefix, excluding collection platforms already parsed from the command line.""" left = prefix.split('=')[0] - images = sorted(set(image.platform for image in filter_completion(NETWORK_COMPLETION).values())) + images = sorted(set(image.platform for image in filter_completion(network_completion()).values())) return [i + '=' for i in images if i.startswith(left) and (not parsed_args.platform_collection or i not in [x[0] for x in parsed_args.platform_collection])] @@ -554,21 +554,21 @@ def complete_network_platform_collection(prefix, parsed_args, **_): # type: (st def complete_network_platform_connection(prefix, parsed_args, **_): # type: (str, argparse.Namespace, ...) -> t.List[str] """Return a list of supported network platforms matching the given prefix, excluding connection platforms already parsed from the command line.""" left = prefix.split('=')[0] - images = sorted(set(image.platform for image in filter_completion(NETWORK_COMPLETION).values())) + images = sorted(set(image.platform for image in filter_completion(network_completion()).values())) return [i + '=' for i in images if i.startswith(left) and (not parsed_args.platform_connection or i not in [x[0] for x in parsed_args.platform_connection])] def get_remote_platform_choices(controller=False): # type: (bool) -> t.List[str] """Return a list of supported remote platforms matching the given prefix.""" - return sorted(filter_completion(REMOTE_COMPLETION, controller_only=controller)) + return sorted(filter_completion(remote_completion(), controller_only=controller)) def get_windows_platform_choices(): # type: () -> t.List[str] """Return a list of supported Windows versions matching the given prefix.""" - return sorted(f'windows/{windows.version}' for windows in filter_completion(WINDOWS_COMPLETION).values()) + return sorted(f'windows/{windows.version}' for windows in filter_completion(windows_completion()).values()) def get_windows_version_choices(): # type: () -> t.List[str] """Return a list of supported Windows versions.""" - return sorted(windows.version for windows in filter_completion(WINDOWS_COMPLETION).values()) + return sorted(windows.version for windows in filter_completion(windows_completion()).values()) diff --git a/test/lib/ansible_test/_internal/cli/parsers/helpers.py b/test/lib/ansible_test/_internal/cli/parsers/helpers.py index 0cf13f8d..8dc7a65c 100644 --- a/test/lib/ansible_test/_internal/cli/parsers/helpers.py +++ b/test/lib/ansible_test/_internal/cli/parsers/helpers.py @@ -9,8 +9,8 @@ from ...constants import ( ) from ...completion import ( - DOCKER_COMPLETION, - REMOTE_COMPLETION, + docker_completion, + remote_completion, filter_completion, ) @@ -23,7 +23,7 @@ from ...host_configs import ( def get_docker_pythons(name, controller, strict): # type: (str, bool, bool) -> t.List[str] """Return a list of docker instance Python versions supported by the specified host config.""" - image_config = filter_completion(DOCKER_COMPLETION).get(name) + image_config = filter_completion(docker_completion()).get(name) available_pythons = CONTROLLER_PYTHON_VERSIONS if controller else SUPPORTED_PYTHON_VERSIONS if not image_config: @@ -36,7 +36,7 @@ def get_docker_pythons(name, controller, strict): # type: (str, bool, bool) -> def get_remote_pythons(name, controller, strict): # type: (str, bool, bool) -> t.List[str] """Return a list of remote instance Python versions supported by the specified host config.""" - platform_config = filter_completion(REMOTE_COMPLETION).get(name) + platform_config = filter_completion(remote_completion()).get(name) available_pythons = CONTROLLER_PYTHON_VERSIONS if controller else SUPPORTED_PYTHON_VERSIONS if not platform_config: diff --git a/test/lib/ansible_test/_internal/cli/parsers/host_config_parsers.py b/test/lib/ansible_test/_internal/cli/parsers/host_config_parsers.py index 37322630..8a7e0ef9 100644 --- a/test/lib/ansible_test/_internal/cli/parsers/host_config_parsers.py +++ b/test/lib/ansible_test/_internal/cli/parsers/host_config_parsers.py @@ -4,10 +4,10 @@ from __future__ import annotations import typing as t from ...completion import ( - DOCKER_COMPLETION, - NETWORK_COMPLETION, - REMOTE_COMPLETION, - WINDOWS_COMPLETION, + docker_completion, + network_completion, + remote_completion, + windows_completion, filter_completion, ) @@ -108,7 +108,7 @@ class DockerParser(PairParser): def get_left_parser(self, state): # type: (ParserState) -> Parser """Return the parser for the left side.""" - return NamespaceWrappedParser('name', ChoicesParser(list(filter_completion(DOCKER_COMPLETION, controller_only=self.controller)), + return NamespaceWrappedParser('name', ChoicesParser(list(filter_completion(docker_completion(), controller_only=self.controller)), conditions=MatchConditions.CHOICE | MatchConditions.ANY)) def get_right_parser(self, choice): # type: (t.Any) -> Parser @@ -128,7 +128,7 @@ class DockerParser(PairParser): """Generate and return documentation for this parser.""" default = 'default' content = '\n'.join([f' {image} ({", ".join(get_docker_pythons(image, self.controller, False))})' - for image, item in filter_completion(DOCKER_COMPLETION, controller_only=self.controller).items()]) + for image, item in filter_completion(docker_completion(), controller_only=self.controller).items()]) content += '\n'.join([ '', @@ -151,7 +151,7 @@ class PosixRemoteParser(PairParser): def get_left_parser(self, state): # type: (ParserState) -> Parser """Return the parser for the left side.""" - return NamespaceWrappedParser('name', PlatformParser(list(filter_completion(REMOTE_COMPLETION, controller_only=self.controller)))) + return NamespaceWrappedParser('name', PlatformParser(list(filter_completion(remote_completion(), controller_only=self.controller)))) def get_right_parser(self, choice): # type: (t.Any) -> Parser """Return the parser for the right side.""" @@ -170,7 +170,7 @@ class PosixRemoteParser(PairParser): """Generate and return documentation for this parser.""" default = get_fallback_remote_controller() content = '\n'.join([f' {name} ({", ".join(get_remote_pythons(name, self.controller, False))})' - for name, item in filter_completion(REMOTE_COMPLETION, controller_only=self.controller).items()]) + for name, item in filter_completion(remote_completion(), controller_only=self.controller).items()]) content += '\n'.join([ '', @@ -190,7 +190,7 @@ class WindowsRemoteParser(PairParser): def get_left_parser(self, state): # type: (ParserState) -> Parser """Return the parser for the left side.""" - names = list(filter_completion(WINDOWS_COMPLETION)) + names = list(filter_completion(windows_completion())) for target in state.root_namespace.targets or []: # type: WindowsRemoteConfig names.remove(target.name) @@ -203,7 +203,7 @@ class WindowsRemoteParser(PairParser): def document(self, state): # type: (DocumentationState) -> t.Optional[str] """Generate and return documentation for this parser.""" - content = '\n'.join([f' {name}' for name, item in filter_completion(WINDOWS_COMPLETION).items()]) + content = '\n'.join([f' {name}' for name, item in filter_completion(windows_completion()).items()]) content += '\n'.join([ '', @@ -223,7 +223,7 @@ class NetworkRemoteParser(PairParser): def get_left_parser(self, state): # type: (ParserState) -> Parser """Return the parser for the left side.""" - names = list(filter_completion(NETWORK_COMPLETION)) + names = list(filter_completion(network_completion())) for target in state.root_namespace.targets or []: # type: NetworkRemoteConfig names.remove(target.name) @@ -236,7 +236,7 @@ class NetworkRemoteParser(PairParser): def document(self, state): # type: (DocumentationState) -> t.Optional[str] """Generate and return documentation for this parser.""" - content = '\n'.join([f' {name}' for name, item in filter_completion(NETWORK_COMPLETION).items()]) + content = '\n'.join([f' {name}' for name, item in filter_completion(network_completion()).items()]) content += '\n'.join([ '', diff --git a/test/lib/ansible_test/_internal/commands/integration/__init__.py b/test/lib/ansible_test/_internal/commands/integration/__init__.py index 09eb889c..839b24ae 100644 --- a/test/lib/ansible_test/_internal/commands/integration/__init__.py +++ b/test/lib/ansible_test/_internal/commands/integration/__init__.py @@ -242,7 +242,7 @@ def integration_test_environment( ansible_config = ansible_config_src vars_file = os.path.join(data_context().content.root, data_context().content.integration_vars_path) - yield IntegrationEnvironment(integration_dir, targets_dir, inventory_path, ansible_config, vars_file) + yield IntegrationEnvironment(data_context().content.root, integration_dir, targets_dir, inventory_path, ansible_config, vars_file) return # When testing a collection, the temporary directory must reside within the collection. @@ -320,7 +320,7 @@ def integration_test_environment( make_dirs(os.path.dirname(file_dst)) shutil.copy2(file_src, file_dst) - yield IntegrationEnvironment(integration_dir, targets_dir, inventory_path, ansible_config, vars_file) + yield IntegrationEnvironment(temp_dir, integration_dir, targets_dir, inventory_path, ansible_config, vars_file) finally: if not args.explain: remove_tree(temp_dir) @@ -440,9 +440,10 @@ def command_integration_filtered( if isinstance(target_profile, ControllerProfile): if host_state.controller_profile.python.path != target_profile.python.path: - install_requirements(args, target_python, command=True) # integration + install_requirements(args, target_python, command=True, controller=False) # integration elif isinstance(target_profile, SshTargetHostProfile): - install_requirements(args, target_python, command=True, connection=target_profile.get_controller_target_connections()[0]) # integration + connection = target_profile.get_controller_target_connections()[0] + install_requirements(args, target_python, command=True, controller=False, connection=connection) # integration coverage_manager = CoverageManager(args, host_state, inventory_path) coverage_manager.setup() @@ -589,7 +590,7 @@ def command_integration_script( if args.verbosity: cmd.append('-' + ('v' * args.verbosity)) - env = integration_environment(args, target, test_dir, test_env.inventory_path, test_env.ansible_config, env_config) + env = integration_environment(args, target, test_dir, test_env.inventory_path, test_env.ansible_config, env_config, test_env) cwd = os.path.join(test_env.targets_dir, target.relative_path) env.update(dict( @@ -710,7 +711,7 @@ def command_integration_role( if args.verbosity: cmd.append('-' + ('v' * args.verbosity)) - env = integration_environment(args, target, test_dir, test_env.inventory_path, test_env.ansible_config, env_config) + env = integration_environment(args, target, test_dir, test_env.inventory_path, test_env.ansible_config, env_config, test_env) cwd = test_env.integration_dir env.update(dict( @@ -765,6 +766,7 @@ def integration_environment( inventory_path, # type: str ansible_config, # type: t.Optional[str] env_config, # type: t.Optional[CloudEnvironmentConfig] + test_env, # type: IntegrationEnvironment ): # type: (...) -> t.Dict[str, str] """Return a dictionary of environment variables to use when running the given integration test target.""" env = ansible_environment(args, ansible_config=ansible_config) @@ -773,6 +775,8 @@ def integration_environment( integration = dict( JUNIT_OUTPUT_DIR=ResultType.JUNIT.path, + JUNIT_TASK_RELATIVE_PATH=test_env.test_dir, + JUNIT_REPLACE_OUT_OF_TREE_PATH='out-of-tree:', ANSIBLE_CALLBACKS_ENABLED=','.join(sorted(set(callback_plugins))), ANSIBLE_TEST_CI=args.metadata.ci_provider or get_ci_provider().code, ANSIBLE_TEST_COVERAGE='check' if args.coverage_check else ('yes' if args.coverage else ''), @@ -796,7 +800,8 @@ def integration_environment( class IntegrationEnvironment: """Details about the integration environment.""" - def __init__(self, integration_dir, targets_dir, inventory_path, ansible_config, vars_file): + def __init__(self, test_dir, integration_dir, targets_dir, inventory_path, ansible_config, vars_file): + self.test_dir = test_dir self.integration_dir = integration_dir self.targets_dir = targets_dir self.inventory_path = inventory_path diff --git a/test/lib/ansible_test/_internal/commands/integration/cloud/aws.py b/test/lib/ansible_test/_internal/commands/integration/cloud/aws.py index f4493933..a34d714d 100644 --- a/test/lib/ansible_test/_internal/commands/integration/cloud/aws.py +++ b/test/lib/ansible_test/_internal/commands/integration/cloud/aws.py @@ -127,5 +127,5 @@ class AwsCloudEnvironment(CloudEnvironment): """Callback to run when an integration target fails.""" if not tries and self.managed: display.notice('If %s failed due to permissions, the IAM test policy may need to be updated. ' - 'https://docs.ansible.com/ansible/devel/dev_guide/platforms/aws_guidelines.html#aws-permissions-for-integration-tests.' + 'https://docs.ansible.com/ansible-core/devel/dev_guide/platforms/aws_guidelines.html#aws-permissions-for-integration-tests.' % target.name) diff --git a/test/lib/ansible_test/_internal/commands/integration/cloud/galaxy.py b/test/lib/ansible_test/_internal/commands/integration/cloud/galaxy.py index 9c900071..de58cbf5 100644 --- a/test/lib/ansible_test/_internal/commands/integration/cloud/galaxy.py +++ b/test/lib/ansible_test/_internal/commands/integration/cloud/galaxy.py @@ -86,7 +86,7 @@ class GalaxyProvider(CloudProvider): # the newer update is available. self.pulp = os.environ.get( 'ANSIBLE_PULP_CONTAINER', - 'docker.io/pulp/pulp-galaxy-ng@sha256:b79a7be64eff86d8f58db9ca83ed4967bd8b4e45c99addb17a91d11926480cf1' + 'quay.io/ansible/pulp-galaxy-ng:b79a7be64eff' ) self.uses_docker = True diff --git a/test/lib/ansible_test/_internal/commands/integration/cloud/openshift.py b/test/lib/ansible_test/_internal/commands/integration/cloud/openshift.py index c30785af..10f63ac0 100644 --- a/test/lib/ansible_test/_internal/commands/integration/cloud/openshift.py +++ b/test/lib/ansible_test/_internal/commands/integration/cloud/openshift.py @@ -36,7 +36,7 @@ class OpenShiftCloudProvider(CloudProvider): super().__init__(args, config_extension='.kubeconfig') # The image must be pinned to a specific version to guarantee CI passes with the version used. - self.image = 'openshift/origin:v3.9.0' + self.image = 'quay.io/ansible/openshift-origin:v3.9.0' self.uses_docker = True self.uses_config = True diff --git a/test/lib/ansible_test/_internal/commands/sanity/__init__.py b/test/lib/ansible_test/_internal/commands/sanity/__init__.py index 542e078a..8c1340f2 100644 --- a/test/lib/ansible_test/_internal/commands/sanity/__init__.py +++ b/test/lib/ansible_test/_internal/commands/sanity/__init__.py @@ -242,7 +242,7 @@ def command_sanity(args): # type: (SanityConfig) -> None elif isinstance(test, SanitySingleVersion): # single version sanity tests use the controller python test_profile = host_state.controller_profile - virtualenv_python = create_sanity_virtualenv(args, test_profile.python, test.name, context=test.name) + virtualenv_python = create_sanity_virtualenv(args, test_profile.python, test.name) if virtualenv_python: virtualenv_yaml = check_sanity_virtualenv_yaml(virtualenv_python) @@ -1077,10 +1077,8 @@ def create_sanity_virtualenv( args, # type: SanityConfig python, # type: PythonConfig name, # type: str - ansible=False, # type: bool coverage=False, # type: bool minimize=False, # type: bool - context=None, # type: t.Optional[str] ): # type: (...) -> t.Optional[VirtualPythonConfig] """Return an existing sanity virtual environment matching the requested parameters or create a new one.""" commands = collect_requirements( # create_sanity_virtualenv() @@ -1088,13 +1086,11 @@ def create_sanity_virtualenv( controller=True, virtualenv=False, command=None, - # used by import tests - ansible=ansible, - cryptography=ansible, + ansible=False, + cryptography=False, coverage=coverage, minimize=minimize, - # used by non-import tests - sanity=context, + sanity=name, ) if commands: @@ -1129,6 +1125,7 @@ def create_sanity_virtualenv( write_text_file(meta_install, virtualenv_install) + # false positive: pylint: disable=no-member if any(isinstance(command, PipInstall) and command.has_package('pyyaml') for command in commands): virtualenv_yaml = yamlcheck(virtualenv_python) else: diff --git a/test/lib/ansible_test/_internal/commands/sanity/import.py b/test/lib/ansible_test/_internal/commands/sanity/import.py index 9a961015..aa0239d5 100644 --- a/test/lib/ansible_test/_internal/commands/sanity/import.py +++ b/test/lib/ansible_test/_internal/commands/sanity/import.py @@ -2,7 +2,6 @@ from __future__ import annotations import os -import tempfile import typing as t from . import ( @@ -18,9 +17,14 @@ from . import ( ) from ...constants import ( + CONTROLLER_MIN_PYTHON_VERSION, REMOTE_ONLY_PYTHON_VERSIONS, ) +from ...io import ( + write_text_file, +) + from ...test import ( TestResult, ) @@ -30,14 +34,18 @@ from ...target import ( ) from ...util import ( + cache, SubprocessError, display, parse_to_list_of_dict, is_subdir, + ANSIBLE_TEST_TOOLS_ROOT, + ANSIBLE_TEST_TARGET_ROOT, ) from ...util_common import ( ResultType, + create_temp_dir, ) from ...ansible_util import ( @@ -45,6 +53,7 @@ from ...ansible_util import ( ) from ...python_requirements import ( + PipUnavailableError, install_requirements, ) @@ -64,6 +73,10 @@ from ...host_configs import ( PythonConfig, ) +from ...venv import ( + get_virtualenv_version, +) + def _get_module_test(module_restrictions): # type: (bool) -> t.Callable[[str], bool] """Create a predicate which tests whether a path can be used by modules or not.""" @@ -91,18 +104,22 @@ class ImportTest(SanityMultipleVersion): paths = [target.path for target in targets.include] - if python.version.startswith('2.'): + if python.version.startswith('2.') and (get_virtualenv_version(args, python.path) or (0,)) < (13,): # hack to make sure that virtualenv is available under Python 2.x # on Python 3.x we can use the built-in venv - install_requirements(args, python, virtualenv=True) # sanity (import) + # version 13+ is required to use the `--no-wheel` option + try: + install_requirements(args, python, virtualenv=True, controller=False) # sanity (import) + except PipUnavailableError as ex: + display.warning(ex) temp_root = os.path.join(ResultType.TMP.path, 'sanity', 'import') messages = [] - for import_type, test, controller in ( - ('module', _get_module_test(True), False), - ('plugin', _get_module_test(False), True), + for import_type, test in ( + ('module', _get_module_test(True)), + ('plugin', _get_module_test(False)), ): if import_type == 'plugin' and python.version in REMOTE_ONLY_PYTHON_VERSIONS: continue @@ -112,7 +129,7 @@ class ImportTest(SanityMultipleVersion): if not data and not args.prime_venvs: continue - virtualenv_python = create_sanity_virtualenv(args, python, f'{self.name}.{import_type}', ansible=controller, coverage=args.coverage, minimize=True) + virtualenv_python = create_sanity_virtualenv(args, python, f'{self.name}.{import_type}', coverage=args.coverage, minimize=True) if not virtualenv_python: display.warning(f'Skipping sanity test "{self.name}" on Python {python.version} due to missing virtual environment support.') @@ -123,9 +140,6 @@ class ImportTest(SanityMultipleVersion): if virtualenv_yaml is False: display.warning(f'Sanity test "{self.name}" ({import_type}) on Python {python.version} may be slow due to missing libyaml support in PyYAML.') - if args.prime_venvs: - continue - env = ansible_environment(args, color=False) env.update( @@ -134,25 +148,30 @@ class ImportTest(SanityMultipleVersion): ) if data_context().content.collection: + external_python = create_sanity_virtualenv(args, args.controller_python, self.name) + env.update( SANITY_COLLECTION_FULL_NAME=data_context().content.collection.full_name, - SANITY_EXTERNAL_PYTHON=python.path, + SANITY_EXTERNAL_PYTHON=external_python.path, + SANITY_YAML_TO_JSON=os.path.join(ANSIBLE_TEST_TOOLS_ROOT, 'yaml_to_json.py'), + ANSIBLE_CONTROLLER_MIN_PYTHON_VERSION=CONTROLLER_MIN_PYTHON_VERSION, + PYTHONPATH=':'.join((get_ansible_test_python_path(), env["PYTHONPATH"])), ) + if args.prime_venvs: + continue + display.info(import_type + ': ' + data, verbosity=4) cmd = ['importer.py'] - try: - with tempfile.TemporaryDirectory(prefix='ansible-test', suffix='-import') as temp_dir: - # make the importer available in the temporary directory - os.symlink(os.path.abspath(os.path.join(TARGET_SANITY_ROOT, 'import', 'importer.py')), os.path.join(temp_dir, 'importer.py')) - os.symlink(os.path.abspath(os.path.join(TARGET_SANITY_ROOT, 'import', 'yaml_to_json.py')), os.path.join(temp_dir, 'yaml_to_json.py')) - - # add the importer to the path so it can be accessed through the coverage injector - env['PATH'] = os.pathsep.join([temp_dir, env['PATH']]) + # add the importer to the path so it can be accessed through the coverage injector + env.update( + PATH=os.pathsep.join([os.path.join(TARGET_SANITY_ROOT, 'import'), env['PATH']]), + ) - stdout, stderr = cover_python(args, virtualenv_python, cmd, self.name, env, capture=True, data=data) + try: + stdout, stderr = cover_python(args, virtualenv_python, cmd, self.name, env, capture=True, data=data) if stdout or stderr: raise SubprocessError(cmd, stdout=stdout, stderr=stderr) @@ -182,3 +201,20 @@ class ImportTest(SanityMultipleVersion): return SanityFailure(self.name, messages=results, python_version=python.version) return SanitySuccess(self.name, python_version=python.version) + + +@cache +def get_ansible_test_python_path(): # type: () -> str + """ + Return a directory usable for PYTHONPATH, containing only the ansible-test collection loader. + The temporary directory created will be cached for the lifetime of the process and cleaned up at exit. + """ + python_path = create_temp_dir(prefix='ansible-test-') + ansible_test_path = os.path.join(python_path, 'ansible_test') + + # legacy collection loader required by all python versions not supported by the controller + write_text_file(os.path.join(ansible_test_path, '__init__.py'), '', True) + write_text_file(os.path.join(ansible_test_path, '_internal', '__init__.py'), '', True) + os.symlink(os.path.join(ANSIBLE_TEST_TARGET_ROOT, 'legacy_collection_loader'), os.path.join(ansible_test_path, '_internal', 'legacy_collection_loader')) + + return python_path diff --git a/test/lib/ansible_test/_internal/commands/sanity/integration_aliases.py b/test/lib/ansible_test/_internal/commands/sanity/integration_aliases.py index bc3ebc0d..6d29968b 100644 --- a/test/lib/ansible_test/_internal/commands/sanity/integration_aliases.py +++ b/test/lib/ansible_test/_internal/commands/sanity/integration_aliases.py @@ -64,7 +64,7 @@ class IntegrationAliasesTest(SanitySingleVersion): UNSTABLE = 'unstable/' UNSUPPORTED = 'unsupported/' - EXPLAIN_URL = 'https://docs.ansible.com/ansible/devel/dev_guide/testing/sanity/integration-aliases.html' + EXPLAIN_URL = 'https://docs.ansible.com/ansible-core/devel/dev_guide/testing/sanity/integration-aliases.html' TEMPLATE_DISABLED = """ The following integration tests are **disabled** [[explain]({explain_url}#disabled)]: diff --git a/test/lib/ansible_test/_internal/commands/units/__init__.py b/test/lib/ansible_test/_internal/commands/units/__init__.py index d23d36fc..9a2b1827 100644 --- a/test/lib/ansible_test/_internal/commands/units/__init__.py +++ b/test/lib/ansible_test/_internal/commands/units/__init__.py @@ -227,7 +227,7 @@ def command_units(args): # type: (UnitsConfig) -> None controller = any(test_context == TestContext.controller for test_context, python, paths, env in final_candidates) if args.requirements_mode != 'skip': - install_requirements(args, target_profile.python, ansible=controller, command=True) # units + install_requirements(args, target_profile.python, ansible=controller, command=True, controller=False) # units test_sets.extend(final_candidates) @@ -237,7 +237,7 @@ def command_units(args): # type: (UnitsConfig) -> None for test_context, python, paths, env in test_sets: cmd = [ 'pytest', - '--boxed', + '--forked', '-r', 'a', '-n', str(args.num_workers) if args.num_workers else 'auto', '--color', diff --git a/test/lib/ansible_test/_internal/completion.py b/test/lib/ansible_test/_internal/completion.py index 25cc6367..86674cb2 100644 --- a/test/lib/ansible_test/_internal/completion.py +++ b/test/lib/ansible_test/_internal/completion.py @@ -13,6 +13,7 @@ from .constants import ( from .util import ( ANSIBLE_TEST_DATA_ROOT, + cache, read_lines_without_comments, ) @@ -220,7 +221,25 @@ def filter_completion( return completion -DOCKER_COMPLETION = load_completion('docker', DockerCompletionConfig) -REMOTE_COMPLETION = load_completion('remote', PosixRemoteCompletionConfig) -WINDOWS_COMPLETION = load_completion('windows', WindowsRemoteCompletionConfig) -NETWORK_COMPLETION = load_completion('network', NetworkRemoteCompletionConfig) +@cache +def docker_completion(): # type: () -> t.Dict[str, DockerCompletionConfig] + """Return docker completion entries.""" + return load_completion('docker', DockerCompletionConfig) + + +@cache +def remote_completion(): # type: () -> t.Dict[str, PosixRemoteCompletionConfig] + """Return remote completion entries.""" + return load_completion('remote', PosixRemoteCompletionConfig) + + +@cache +def windows_completion(): # type: () -> t.Dict[str, WindowsRemoteCompletionConfig] + """Return windows completion entries.""" + return load_completion('windows', WindowsRemoteCompletionConfig) + + +@cache +def network_completion(): # type: () -> t.Dict[str, NetworkRemoteCompletionConfig] + """Return network completion entries.""" + return load_completion('network', NetworkRemoteCompletionConfig) diff --git a/test/lib/ansible_test/_internal/constants.py b/test/lib/ansible_test/_internal/constants.py index 07455d8e..cac72408 120000..100644 --- a/test/lib/ansible_test/_internal/constants.py +++ b/test/lib/ansible_test/_internal/constants.py @@ -1 +1,49 @@ -../_util/target/common/constants.py
\ No newline at end of file +"""Constants used by ansible-test. Imports should not be used in this file (other than to import the target common constants).""" +from __future__ import annotations + +from .._util.target.common.constants import ( + CONTROLLER_PYTHON_VERSIONS, + REMOTE_ONLY_PYTHON_VERSIONS, +) + +# Setting a low soft RLIMIT_NOFILE value will improve the performance of subprocess.Popen on Python 2.x when close_fds=True. +# This will affect all Python subprocesses. It will also affect the current Python process if set before subprocess is imported for the first time. +SOFT_RLIMIT_NOFILE = 1024 + +# File used to track the ansible-test test execution timeout. +TIMEOUT_PATH = '.ansible-test-timeout.json' + +CONTROLLER_MIN_PYTHON_VERSION = CONTROLLER_PYTHON_VERSIONS[0] +SUPPORTED_PYTHON_VERSIONS = REMOTE_ONLY_PYTHON_VERSIONS + CONTROLLER_PYTHON_VERSIONS + +COVERAGE_REQUIRED_VERSION = '4.5.4' + +REMOTE_PROVIDERS = [ + 'default', + 'aws', + 'azure', + 'ibmps', + 'parallels', +] + +SECCOMP_CHOICES = [ + 'default', + 'unconfined', +] + +# This bin symlink map must exactly match the contents of the bin directory. +# It is necessary for payload creation to reconstruct the bin directory when running ansible-test from an installed version of ansible. +# It is also used to construct the injector directory at runtime. +ANSIBLE_BIN_SYMLINK_MAP = { + 'ansible': '../lib/ansible/cli/scripts/ansible_cli_stub.py', + 'ansible-config': 'ansible', + 'ansible-connection': '../lib/ansible/cli/scripts/ansible_connection_cli_stub.py', + 'ansible-console': 'ansible', + 'ansible-doc': 'ansible', + 'ansible-galaxy': 'ansible', + 'ansible-inventory': 'ansible', + 'ansible-playbook': 'ansible', + 'ansible-pull': 'ansible', + 'ansible-test': '../test/lib/ansible_test/_util/target/cli/ansible_test_cli_stub.py', + 'ansible-vault': 'ansible', +} diff --git a/test/lib/ansible_test/_internal/containers.py b/test/lib/ansible_test/_internal/containers.py index 97e84880..7ffbfb4c 100644 --- a/test/lib/ansible_test/_internal/containers.py +++ b/test/lib/ansible_test/_internal/containers.py @@ -829,7 +829,7 @@ def cleanup_ssh_ports( for process in ssh_processes: process.terminate() - display.info('Waiting for the %s host SSH port forwarding processs(es) to terminate.' % host_type, verbosity=1) + display.info('Waiting for the %s host SSH port forwarding process(es) to terminate.' % host_type, verbosity=1) for process in ssh_processes: process.wait() diff --git a/test/lib/ansible_test/_internal/delegation.py b/test/lib/ansible_test/_internal/delegation.py index aaee0dfa..83ff24c0 100644 --- a/test/lib/ansible_test/_internal/delegation.py +++ b/test/lib/ansible_test/_internal/delegation.py @@ -53,7 +53,6 @@ from .ci import ( from .host_configs import ( OriginConfig, PythonConfig, - VirtualPythonConfig, ) from .connections import ( @@ -254,9 +253,9 @@ def generate_command( ANSIBLE_TEST_CONTENT_ROOT=content_root, ) - if isinstance(args.controller.python, VirtualPythonConfig): - # Expose the ansible and ansible_test library directories to the virtual environment. - # This is only required when running from an install. + if isinstance(args.controller, OriginConfig): + # Expose the ansible and ansible_test library directories to the Python environment. + # This is only required when delegation is used on the origin host. library_path = process_scoped_temporary_directory(args) os.symlink(ANSIBLE_LIB_ROOT, os.path.join(library_path, 'ansible')) diff --git a/test/lib/ansible_test/_internal/host_configs.py b/test/lib/ansible_test/_internal/host_configs.py index a819652e..87030ae0 100644 --- a/test/lib/ansible_test/_internal/host_configs.py +++ b/test/lib/ansible_test/_internal/host_configs.py @@ -19,17 +19,17 @@ from .io import ( from .completion import ( CompletionConfig, - DOCKER_COMPLETION, + docker_completion, DockerCompletionConfig, InventoryCompletionConfig, - NETWORK_COMPLETION, + network_completion, NetworkRemoteCompletionConfig, PosixCompletionConfig, PosixRemoteCompletionConfig, PosixSshCompletionConfig, - REMOTE_COMPLETION, + remote_completion, RemoteCompletionConfig, - WINDOWS_COMPLETION, + windows_completion, WindowsRemoteCompletionConfig, filter_completion, ) @@ -277,7 +277,7 @@ class DockerConfig(ControllerHostConfig, PosixConfig): def get_defaults(self, context): # type: (HostContext) -> DockerCompletionConfig """Return the default settings.""" - return filter_completion(DOCKER_COMPLETION).get(self.name) or DockerCompletionConfig( + return filter_completion(docker_completion()).get(self.name) or DockerCompletionConfig( name=self.name, image=self.name, placeholder=True, @@ -285,7 +285,7 @@ class DockerConfig(ControllerHostConfig, PosixConfig): def get_default_targets(self, context): # type: (HostContext) -> t.List[ControllerConfig] """Return the default targets for this host config.""" - if self.name in filter_completion(DOCKER_COMPLETION): + if self.name in filter_completion(docker_completion()): defaults = self.get_defaults(context) pythons = {version: defaults.get_python_path(version) for version in defaults.supported_pythons} else: @@ -327,14 +327,14 @@ class PosixRemoteConfig(RemoteConfig, ControllerHostConfig, PosixConfig): def get_defaults(self, context): # type: (HostContext) -> PosixRemoteCompletionConfig """Return the default settings.""" - return filter_completion(REMOTE_COMPLETION).get(self.name) or REMOTE_COMPLETION.get(self.platform) or PosixRemoteCompletionConfig( + return filter_completion(remote_completion()).get(self.name) or remote_completion().get(self.platform) or PosixRemoteCompletionConfig( name=self.name, placeholder=True, ) def get_default_targets(self, context): # type: (HostContext) -> t.List[ControllerConfig] """Return the default targets for this host config.""" - if self.name in filter_completion(REMOTE_COMPLETION): + if self.name in filter_completion(remote_completion()): defaults = self.get_defaults(context) pythons = {version: defaults.get_python_path(version) for version in defaults.supported_pythons} else: @@ -358,7 +358,7 @@ class WindowsRemoteConfig(RemoteConfig, WindowsConfig): """Configuration for a remoe Windows host.""" def get_defaults(self, context): # type: (HostContext) -> WindowsRemoteCompletionConfig """Return the default settings.""" - return filter_completion(WINDOWS_COMPLETION).get(self.name) or WindowsRemoteCompletionConfig( + return filter_completion(windows_completion()).get(self.name) or WindowsRemoteCompletionConfig( name=self.name, ) @@ -381,7 +381,7 @@ class NetworkRemoteConfig(RemoteConfig, NetworkConfig): def get_defaults(self, context): # type: (HostContext) -> NetworkRemoteCompletionConfig """Return the default settings.""" - return filter_completion(NETWORK_COMPLETION).get(self.name) or NetworkRemoteCompletionConfig( + return filter_completion(network_completion()).get(self.name) or NetworkRemoteCompletionConfig( name=self.name, ) diff --git a/test/lib/ansible_test/_internal/host_profiles.py b/test/lib/ansible_test/_internal/host_profiles.py index 0a08d68f..e3aeeeeb 100644 --- a/test/lib/ansible_test/_internal/host_profiles.py +++ b/test/lib/ansible_test/_internal/host_profiles.py @@ -209,11 +209,7 @@ class PosixProfile(HostProfile[TPosixConfig], metaclass=abc.ABCMeta): python = self.config.python if isinstance(python, VirtualPythonConfig): - python = VirtualPythonConfig( - version=python.version, - system_site_packages=python.system_site_packages, - path=os.path.join(get_virtual_python(self.args, python), 'bin', 'python'), - ) + python = get_virtual_python(self.args, python) self.state['python'] = python diff --git a/test/lib/ansible_test/_internal/python_requirements.py b/test/lib/ansible_test/_internal/python_requirements.py index 8fca7834..aaaf44b8 100644 --- a/test/lib/ansible_test/_internal/python_requirements.py +++ b/test/lib/ansible_test/_internal/python_requirements.py @@ -25,6 +25,7 @@ from .util import ( ANSIBLE_TEST_DATA_ROOT, ANSIBLE_TEST_TARGET_ROOT, ANSIBLE_TEST_TOOLS_ROOT, + ApplicationError, SubprocessError, display, find_executable, @@ -65,6 +66,12 @@ REQUIREMENTS_SCRIPT_PATH = os.path.join(ANSIBLE_TEST_TARGET_ROOT, 'setup', 'requ # Pip Abstraction +class PipUnavailableError(ApplicationError): + """Exception raised when pip is not available.""" + def __init__(self, python): # type: (PythonConfig) -> None + super().__init__(f'Python {python.version} at "{python.path}" does not have pip available.') + + @dataclasses.dataclass(frozen=True) class PipCommand: """Base class for pip commands.""""" @@ -97,6 +104,18 @@ class PipUninstall(PipCommand): ignore_errors: bool +@dataclasses.dataclass(frozen=True) +class PipVersion(PipCommand): + """Details required to get the pip version.""" + + +@dataclasses.dataclass(frozen=True) +class PipBootstrap(PipCommand): + """Details required to bootstrap pip.""" + pip_version: str + packages: t.List[str] + + # Entry Points @@ -107,13 +126,12 @@ def install_requirements( command=False, # type: bool coverage=False, # type: bool virtualenv=False, # type: bool + controller=True, # type: bool connection=None, # type: t.Optional[Connection] ): # type: (...) -> None """Install requirements for the given Python using the specified arguments.""" create_result_directories(args) - controller = not connection - if not requirements_allowed(args, controller): return @@ -157,10 +175,25 @@ def install_requirements( run_pip(args, python, commands, connection) + # false positive: pylint: disable=no-member if any(isinstance(command, PipInstall) and command.has_package('pyyaml') for command in commands): check_pyyaml(python) +def collect_bootstrap(python): # type: (PythonConfig) -> t.List[PipCommand] + """Return the details necessary to bootstrap pip into an empty virtual environment.""" + infrastructure_packages = get_venv_packages(python) + pip_version = infrastructure_packages['pip'] + packages = [f'{name}=={version}' for name, version in infrastructure_packages.items()] + + bootstrap = PipBootstrap( + pip_version=pip_version, + packages=packages, + ) + + return [bootstrap] + + def collect_requirements( python, # type: PythonConfig controller, # type: bool @@ -176,7 +209,10 @@ def collect_requirements( commands = [] # type: t.List[PipCommand] if virtualenv: - commands.extend(collect_package_install(packages=['virtualenv'])) + # sanity tests on Python 2.x install virtualenv when it is too old or is not already installed and the `--requirements` option is given + # the last version of virtualenv with no dependencies is used to minimize the changes made outside a virtual environment + virtualenv_version = '15.2.0' if python.version == '2.6' else '16.7.12' + commands.extend(collect_package_install(packages=[f'virtualenv=={virtualenv_version}'], constraints=False)) if coverage: commands.extend(collect_package_install(packages=[f'coverage=={COVERAGE_REQUIRED_VERSION}'], constraints=False)) @@ -196,15 +232,20 @@ def collect_requirements( if command in ('integration', 'windows-integration', 'network-integration'): commands.extend(collect_integration_install(command, controller)) - if minimize: - # In some environments pkg_resources is installed as a separate pip package which needs to be removed. - # For example, using Python 3.8 on Ubuntu 18.04 a virtualenv is created with only pip and setuptools. - # However, a venv is created with an additional pkg-resources package which is independent of setuptools. - # Making sure pkg-resources is removed preserves the import test consistency between venv and virtualenv. - # Additionally, in the above example, the pyparsing package vendored with pkg-resources is out-of-date and generates deprecation warnings. - # Thus it is important to remove pkg-resources to prevent system installed packages from generating deprecation warnings. - commands.extend(collect_uninstall(packages=['pkg-resources'], ignore_errors=True)) - commands.extend(collect_uninstall(packages=['setuptools', 'pip'])) + if (sanity or minimize) and any(isinstance(command, PipInstall) for command in commands): + # bootstrap the managed virtual environment, which will have been created without any installed packages + # sanity tests which install no packages skip this step + commands = collect_bootstrap(python) + commands + + # most infrastructure packages can be removed from sanity test virtual environments after they've been created + # removing them reduces the size of environments cached in containers + uninstall_packages = list(get_venv_packages(python)) + + if not minimize: + # installed packages may have run-time dependencies on setuptools + uninstall_packages.remove('setuptools') + + commands.extend(collect_uninstall(packages=uninstall_packages)) return commands @@ -220,7 +261,18 @@ def run_pip( script = prepare_pip_script(commands) if not args.explain: - connection.run([python.path], data=script) + try: + connection.run([python.path], data=script) + except SubprocessError: + script = prepare_pip_script([PipVersion()]) + + try: + connection.run([python.path], data=script, capture=True) + except SubprocessError as ex: + if 'pip is unavailable:' in ex.stdout + ex.stderr: + raise PipUnavailableError(python) + + raise # Collect @@ -355,6 +407,46 @@ def collect_uninstall(packages, ignore_errors=False): # type: (t.List[str], boo # Support +def get_venv_packages(python): # type: (PythonConfig) -> t.Dict[str, str] + """Return a dictionary of Python packages needed for a consistent virtual environment specific to the given Python version.""" + + # NOTE: This same information is needed for building the base-test-container image. + # See: https://github.com/ansible/base-test-container/blob/main/files/installer.py + + default_packages = dict( + pip='21.3.1', + setuptools='60.8.2', + wheel='0.37.1', + ) + + override_packages = { + '2.6': dict( + pip='9.0.3', # 10.0 requires Python 2.7+ + setuptools='36.8.0', # 37.0.0 requires Python 2.7+ + wheel='0.29.0', # 0.30.0 requires Python 2.7+ + ), + '2.7': dict( + pip='20.3.4', # 21.0 requires Python 3.6+ + setuptools='44.1.1', # 45.0.0 requires Python 3.5+ + wheel=None, + ), + '3.5': dict( + pip='20.3.4', # 21.0 requires Python 3.6+ + setuptools='50.3.2', # 51.0.0 requires Python 3.6+ + wheel=None, + ), + '3.6': dict( + pip='21.3.1', # 22.0 requires Python 3.7+ + setuptools='59.6.0', # 59.7.0 requires Python 3.7+ + wheel=None, + ), + } + + packages = {name: version or default_packages[name] for name, version in override_packages.get(python.version, default_packages).items()} + + return packages + + def requirements_allowed(args, controller): # type: (EnvironmentConfig, bool) -> bool """ Return True if requirements can be installed, otherwise return False. @@ -430,11 +522,11 @@ def get_cryptography_requirements(python): # type: (PythonConfig) -> t.List[str # pyopenssl 20.0.0 requires cryptography 3.2 or later pyopenssl = 'pyopenssl < 20.0.0' else: - # cryptography 3.4+ fails to install on many systems - # this is a temporary work-around until a more permanent solution is available - cryptography = 'cryptography < 3.4' - # no specific version of pyopenssl required, don't install it - pyopenssl = None + # cryptography 3.4+ builds require a working rust toolchain + # systems bootstrapped using ansible-core-ci can access additional wheels through the spare-tire package index + cryptography = 'cryptography' + # any future installation of pyopenssl is free to use any compatible version of cryptography + pyopenssl = '' requirements = [ cryptography, diff --git a/test/lib/ansible_test/_internal/test.py b/test/lib/ansible_test/_internal/test.py index af21cbd6..b67addc3 100644 --- a/test/lib/ansible_test/_internal/test.py +++ b/test/lib/ansible_test/_internal/test.py @@ -347,7 +347,7 @@ class TestFailure(TestResult): if re.search(r'^[0-9.]+$', ansible_version): url_version = '.'.join(ansible_version.split('.')[:2]) - testing_docs_url = 'https://docs.ansible.com/ansible/%s/dev_guide/testing' % url_version + testing_docs_url = 'https://docs.ansible.com/ansible-core/%s/dev_guide/testing' % url_version url = '%s/%s/' % (testing_docs_url, self.command) diff --git a/test/lib/ansible_test/_internal/venv.py b/test/lib/ansible_test/_internal/venv.py index 2cfd978d..cf436775 100644 --- a/test/lib/ansible_test/_internal/venv.py +++ b/test/lib/ansible_test/_internal/venv.py @@ -3,6 +3,7 @@ from __future__ import annotations import json import os +import pathlib import sys import typing as t @@ -31,11 +32,16 @@ from .host_configs import ( PythonConfig, ) +from .python_requirements import ( + collect_bootstrap, + run_pip, +) + def get_virtual_python( args, # type: EnvironmentConfig python, # type: VirtualPythonConfig -): +): # type: (...) -> VirtualPythonConfig """Create a virtual environment for the given Python and return the path to its root.""" if python.system_site_packages: suffix = '-ssp' @@ -43,24 +49,40 @@ def get_virtual_python( suffix = '' virtual_environment_path = os.path.join(ResultType.TMP.path, 'delegation', f'python{python.version}{suffix}') + virtual_environment_marker = os.path.join(virtual_environment_path, 'marker.txt') + + virtual_environment_python = VirtualPythonConfig( + version=python.version, + path=os.path.join(virtual_environment_path, 'bin', 'python'), + system_site_packages=python.system_site_packages, + ) + + if os.path.exists(virtual_environment_marker): + display.info('Using existing Python %s virtual environment: %s' % (python.version, virtual_environment_path), verbosity=1) + else: + # a virtualenv without a marker is assumed to have been partially created + remove_tree(virtual_environment_path) - if not create_virtual_environment(args, python, virtual_environment_path, python.system_site_packages): - raise ApplicationError(f'Python {python.version} does not provide virtual environment support.') + if not create_virtual_environment(args, python, virtual_environment_path, python.system_site_packages): + raise ApplicationError(f'Python {python.version} does not provide virtual environment support.') - return virtual_environment_path + commands = collect_bootstrap(virtual_environment_python) + + run_pip(args, virtual_environment_python, commands, None) # get_virtual_python() + + # touch the marker to keep track of when the virtualenv was last used + pathlib.Path(virtual_environment_marker).touch() + + return virtual_environment_python def create_virtual_environment(args, # type: EnvironmentConfig python, # type: PythonConfig path, # type: str system_site_packages=False, # type: bool - pip=True, # type: bool + pip=False, # type: bool ): # type: (...) -> bool """Create a virtual environment using venv or virtualenv for the requested Python version.""" - if os.path.isdir(path): - display.info('Using existing Python %s virtual environment: %s' % (python.version, path), verbosity=1) - return True - if not os.path.exists(python.path): # the requested python version could not be found return False @@ -207,6 +229,9 @@ def run_virtualenv(args, # type: EnvironmentConfig if not pip: cmd.append('--no-pip') + # these options provide consistency with venv, which does not install them without pip + cmd.append('--no-setuptools') + cmd.append('--no-wheel') cmd.append(path) diff --git a/test/lib/ansible_test/_util/controller/sanity/code-smell/runtime-metadata.py b/test/lib/ansible_test/_util/controller/sanity/code-smell/runtime-metadata.py index cad82a55..929f371f 100644 --- a/test/lib/ansible_test/_util/controller/sanity/code-smell/runtime-metadata.py +++ b/test/lib/ansible_test/_util/controller/sanity/code-smell/runtime-metadata.py @@ -141,7 +141,7 @@ def validate_metadata_file(path, is_ansible, check_deprecation_dates=False): current_version = get_collection_version() # Updates to schema MUST also be reflected in the documentation - # ~https://docs.ansible.com/ansible/devel/dev_guide/developing_collections.html + # ~https://docs.ansible.com/ansible-core/devel/dev_guide/developing_collections.html # plugin_routing schema diff --git a/test/lib/ansible_test/_util/controller/sanity/validate-modules/validate_modules/main.py b/test/lib/ansible_test/_util/controller/sanity/validate-modules/validate_modules/main.py index 9f4f5c47..f9eaa02a 100644 --- a/test/lib/ansible_test/_util/controller/sanity/validate-modules/validate_modules/main.py +++ b/test/lib/ansible_test/_util/controller/sanity/validate-modules/validate_modules/main.py @@ -30,20 +30,48 @@ import subprocess import sys import tempfile import traceback +import warnings from collections import OrderedDict from contextlib import contextmanager -from ansible.module_utils.compat.version import StrictVersion, LooseVersion from fnmatch import fnmatch import yaml +from voluptuous.humanize import humanize_error + + +def setup_collection_loader(): + """ + Configure the collection loader if a collection is being tested. + This must be done before the plugin loader is imported. + """ + if '--collection' not in sys.argv: + return + + # noinspection PyProtectedMember + from ansible.utils.collection_loader._collection_finder import _AnsibleCollectionFinder + + collections_paths = os.environ.get('ANSIBLE_COLLECTIONS_PATH', '').split(os.pathsep) + collection_loader = _AnsibleCollectionFinder(collections_paths) + # noinspection PyProtectedMember + collection_loader._install() # pylint: disable=protected-access + + warnings.filterwarnings( + "ignore", + "AnsibleCollectionFinder has already been configured") + + +setup_collection_loader() + from ansible import __version__ as ansible_version from ansible.executor.module_common import REPLACER_WINDOWS from ansible.module_utils.common._collections_compat import Mapping from ansible.module_utils.common.parameters import DEFAULT_TYPE_VALIDATORS +from ansible.module_utils.compat.version import StrictVersion, LooseVersion +from ansible.module_utils.basic import to_bytes +from ansible.module_utils.six import PY3, with_metaclass, string_types from ansible.plugins.loader import fragment_loader -from ansible.utils.collection_loader._collection_finder import _AnsibleCollectionFinder from ansible.utils.plugin_docs import REJECTLIST, add_collection_to_versions_and_dates, add_fragments, get_docstring from ansible.utils.version import SemanticVersion @@ -52,9 +80,7 @@ from .module_args import AnsibleModuleImportError, AnsibleModuleNotInitialized, from .schema import ansible_module_kwargs_schema, doc_schema, return_schema from .utils import CaptureStd, NoArgsAnsibleModule, compare_unordered_lists, is_empty, parse_yaml, parse_isodate -from voluptuous.humanize import humanize_error -from ansible.module_utils.six import PY3, with_metaclass, string_types if PY3: # Because there is no ast.TryExcept in Python 3 ast module @@ -487,7 +513,7 @@ class ModuleValidator(Validator): path=self.object_path, code='use-short-gplv3-license', msg='Found old style GPLv3 license header: ' - 'https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_documenting.html#copyright' + 'https://docs.ansible.com/ansible-core/devel/dev_guide/developing_modules_documenting.html#copyright' ) def _check_for_subprocess(self): @@ -606,7 +632,7 @@ class ModuleValidator(Validator): if isinstance(child, (ast.FunctionDef, ast.ClassDef)): linenos.append(child.lineno) - return min(linenos) + return min(linenos) if linenos else None def _find_has_import(self): for child in self.ast.body: @@ -2179,7 +2205,7 @@ class ModuleValidator(Validator): self._find_rejectlist_imports() self._find_module_utils() self._find_has_import() - first_callable = self._get_first_callable() + first_callable = self._get_first_callable() or 1000000 # use a bogus "high" line number if no callable exists self._ensure_imports_below_docs(doc_info, first_callable) self._check_for_subprocess() self._check_for_os_call() @@ -2238,11 +2264,6 @@ class PythonPackageValidator(Validator): ) -def setup_collection_loader(): - collections_paths = os.environ.get('ANSIBLE_COLLECTIONS_PATH', '').split(os.pathsep) - _AnsibleCollectionFinder(collections_paths) - - def re_compile(value): """ Argparse expects things to raise TypeError, re.compile raises an re.error @@ -2295,7 +2316,6 @@ def run(): routing = None if args.collection: - setup_collection_loader() routing_file = 'meta/runtime.yml' # Load meta/runtime.yml if it exists, as it may contain deprecation information if os.path.isfile(routing_file): diff --git a/test/lib/ansible_test/_util/controller/sanity/yamllint/yamllinter.py b/test/lib/ansible_test/_util/controller/sanity/yamllint/yamllinter.py index 42822111..7f9df40a 100644 --- a/test/lib/ansible_test/_util/controller/sanity/yamllint/yamllinter.py +++ b/test/lib/ansible_test/_util/controller/sanity/yamllint/yamllinter.py @@ -13,7 +13,7 @@ import yaml from yaml.resolver import Resolver from yaml.constructor import SafeConstructor from yaml.error import MarkedYAMLError -from _yaml import CParser # pylint: disable=no-name-in-module +from yaml.cyaml import CParser from yamllint import linter from yamllint.config import YamlLintConfig diff --git a/test/lib/ansible_test/_util/controller/tools/virtualenvcheck.py b/test/lib/ansible_test/_util/controller/tools/virtualenvcheck.py index 90dfa394..a38ad074 100644 --- a/test/lib/ansible_test/_util/controller/tools/virtualenvcheck.py +++ b/test/lib/ansible_test/_util/controller/tools/virtualenvcheck.py @@ -5,10 +5,17 @@ __metaclass__ = type import json try: + # virtualenv <20 from sys import real_prefix except ImportError: real_prefix = None +try: + # venv and virtualenv >= 20 + from sys import base_exec_prefix +except ImportError: + base_exec_prefix = None + print(json.dumps(dict( - real_prefix=real_prefix, + real_prefix=real_prefix or base_exec_prefix, ))) diff --git a/test/lib/ansible_test/_util/target/sanity/import/yaml_to_json.py b/test/lib/ansible_test/_util/controller/tools/yaml_to_json.py index 1164168e..1164168e 100644 --- a/test/lib/ansible_test/_util/target/sanity/import/yaml_to_json.py +++ b/test/lib/ansible_test/_util/controller/tools/yaml_to_json.py diff --git a/test/lib/ansible_test/_util/target/common/constants.py b/test/lib/ansible_test/_util/target/common/constants.py index 3c02eb2e..fdaa9e5f 100644 --- a/test/lib/ansible_test/_util/target/common/constants.py +++ b/test/lib/ansible_test/_util/target/common/constants.py @@ -1,17 +1,10 @@ -"""Constants used by ansible-test. Imports should not be used in this file.""" +"""Constants used by ansible-test's CLI entry point (as well as the rest of ansible-test). Imports should not be used in this file.""" # NOTE: This file resides in the _util/target directory to ensure compatibility with all supported Python versions. from __future__ import (absolute_import, division, print_function) __metaclass__ = type -# Setting a low soft RLIMIT_NOFILE value will improve the performance of subprocess.Popen on Python 2.x when close_fds=True. -# This will affect all Python subprocesses. It will also affect the current Python process if set before subprocess is imported for the first time. -SOFT_RLIMIT_NOFILE = 1024 - -# File used to track the ansible-test test execution timeout. -TIMEOUT_PATH = '.ansible-test-timeout.json' - REMOTE_ONLY_PYTHON_VERSIONS = ( '2.6', '2.7', @@ -25,38 +18,3 @@ CONTROLLER_PYTHON_VERSIONS = ( '3.9', '3.10', ) - -CONTROLLER_MIN_PYTHON_VERSION = CONTROLLER_PYTHON_VERSIONS[0] -SUPPORTED_PYTHON_VERSIONS = REMOTE_ONLY_PYTHON_VERSIONS + CONTROLLER_PYTHON_VERSIONS - -COVERAGE_REQUIRED_VERSION = '4.5.4' - -REMOTE_PROVIDERS = [ - 'default', - 'aws', - 'azure', - 'ibmps', - 'parallels', -] - -SECCOMP_CHOICES = [ - 'default', - 'unconfined', -] - -# This bin symlink map must exactly match the contents of the bin directory. -# It is necessary for payload creation to reconstruct the bin directory when running ansible-test from an installed version of ansible. -# It is also used to construct the injector directory at runtime. -ANSIBLE_BIN_SYMLINK_MAP = { - 'ansible': '../lib/ansible/cli/scripts/ansible_cli_stub.py', - 'ansible-config': 'ansible', - 'ansible-connection': '../lib/ansible/cli/scripts/ansible_connection_cli_stub.py', - 'ansible-console': 'ansible', - 'ansible-doc': 'ansible', - 'ansible-galaxy': 'ansible', - 'ansible-inventory': 'ansible', - 'ansible-playbook': 'ansible', - 'ansible-pull': 'ansible', - 'ansible-test': '../test/lib/ansible_test/_util/target/cli/ansible_test_cli_stub.py', - 'ansible-vault': 'ansible', -} diff --git a/test/lib/ansible_test/_util/target/sanity/import/importer.py b/test/lib/ansible_test/_util/target/sanity/import/importer.py index 778643bb..60255da6 100644 --- a/test/lib/ansible_test/_util/target/sanity/import/importer.py +++ b/test/lib/ansible_test/_util/target/sanity/import/importer.py @@ -8,25 +8,38 @@ def main(): Main program function used to isolate globals from imported code. Changes to globals in imported modules on Python 2.x will overwrite our own globals. """ + import os + import sys + import types + + # preload an empty ansible._vendor module to prevent use of any embedded modules during the import test + vendor_module_name = 'ansible._vendor' + + vendor_module = types.ModuleType(vendor_module_name) + vendor_module.__file__ = os.path.join(os.path.sep.join(os.path.abspath(__file__).split(os.path.sep)[:-8]), 'lib/ansible/_vendor/__init__.py') + vendor_module.__path__ = [] + vendor_module.__package__ = vendor_module_name + + sys.modules[vendor_module_name] = vendor_module + import ansible import contextlib import datetime import json - import os import re import runpy import subprocess - import sys import traceback - import types import warnings ansible_path = os.path.dirname(os.path.dirname(ansible.__file__)) temp_path = os.environ['SANITY_TEMP_PATH'] + os.path.sep - external_python = os.environ.get('SANITY_EXTERNAL_PYTHON') or sys.executable + external_python = os.environ.get('SANITY_EXTERNAL_PYTHON') + yaml_to_json_path = os.environ.get('SANITY_YAML_TO_JSON') collection_full_name = os.environ.get('SANITY_COLLECTION_FULL_NAME') collection_root = os.environ.get('ANSIBLE_COLLECTIONS_PATH') import_type = os.environ.get('SANITY_IMPORTER_TYPE') + ansible_controller_min_python_version = tuple(int(x) for x in os.environ.get('ANSIBLE_CONTROLLER_MIN_PYTHON_VERSION', '0').split('.')) try: # noinspection PyCompatibility @@ -45,10 +58,17 @@ def main(): if collection_full_name: # allow importing code from collections when testing a collection from ansible.module_utils.common.text.converters import to_bytes, to_text, to_native, text_type - from ansible.utils.collection_loader._collection_finder import _AnsibleCollectionFinder - from ansible.utils.collection_loader import _collection_finder - yaml_to_json_path = os.path.join(os.path.dirname(__file__), 'yaml_to_json.py') + if sys.version_info >= ansible_controller_min_python_version: + # noinspection PyProtectedMember + from ansible.utils.collection_loader._collection_finder import _AnsibleCollectionFinder + from ansible.utils.collection_loader import _collection_finder + else: + # noinspection PyProtectedMember + from ansible_test._internal.legacy_collection_loader._collection_finder import _AnsibleCollectionFinder + # noinspection PyProtectedMember + from ansible_test._internal.legacy_collection_loader import _collection_finder + yaml_to_dict_cache = {} # unique ISO date marker matching the one present in yaml_to_json.py @@ -101,8 +121,13 @@ def main(): # do not support collection loading when not testing a collection collection_loader = None - # remove all modules under the ansible package - list(map(sys.modules.pop, [m for m in sys.modules if m.partition('.')[0] == ansible.__name__])) + if collection_loader and import_type == 'plugin': + # do not unload ansible code for collection plugin (not module) tests + # doing so could result in the collection loader being initialized multiple times + pass + else: + # remove all modules under the ansible package, except the preloaded vendor module + list(map(sys.modules.pop, [m for m in sys.modules if m.partition('.')[0] == ansible.__name__ and m != vendor_module_name])) if import_type == 'module': # pre-load an empty ansible package to prevent unwanted code in __init__.py from loading @@ -424,7 +449,7 @@ def main(): try: yield finally: - if import_type == 'plugin': + if import_type == 'plugin' and not collection_loader: from ansible.utils.collection_loader._collection_finder import _AnsibleCollectionFinder _AnsibleCollectionFinder._remove() # pylint: disable=protected-access @@ -473,6 +498,11 @@ def main(): with warnings.catch_warnings(): warnings.simplefilter('error') + if collection_loader and import_type == 'plugin': + warnings.filterwarnings( + "ignore", + "AnsibleCollectionFinder has already been configured") + if sys.version_info[0] == 2: warnings.filterwarnings( "ignore", diff --git a/test/lib/ansible_test/_util/target/setup/bootstrap.sh b/test/lib/ansible_test/_util/target/setup/bootstrap.sh index 2d31945e..53e2ca71 100644 --- a/test/lib/ansible_test/_util/target/setup/bootstrap.sh +++ b/test/lib/ansible_test/_util/target/setup/bootstrap.sh @@ -49,8 +49,11 @@ customize_bashrc() install_pip() { if ! "${python_interpreter}" -m pip.__main__ --version --disable-pip-version-check 2>/dev/null; then case "${python_version}" in + "2.7") + pip_bootstrap_url="https://ci-files.testing.ansible.com/ansible-test/get-pip-20.3.4.py" + ;; *) - pip_bootstrap_url="https://ansible-ci-files.s3.amazonaws.com/ansible-test/get-pip-20.3.4.py" + pip_bootstrap_url="https://ci-files.testing.ansible.com/ansible-test/get-pip-21.3.1.py" ;; esac @@ -180,6 +183,13 @@ bootstrap_remote_freebsd() sed -i '' 's/^# *PermitRootLogin.*$/PermitRootLogin yes/;' /etc/ssh/sshd_config service sshd restart fi + + # make additional wheels available for packages which lack them for this platform + echo "# generated by ansible-test +[global] +extra-index-url = https://spare-tire.testing.ansible.com/simple/ +prefer-binary = yes +" > /etc/pip.conf } bootstrap_remote_macos() diff --git a/test/lib/ansible_test/_util/target/setup/quiet_pip.py b/test/lib/ansible_test/_util/target/setup/quiet_pip.py index 83d4576b..fc65c88b 100644 --- a/test/lib/ansible_test/_util/target/setup/quiet_pip.py +++ b/test/lib/ansible_test/_util/target/setup/quiet_pip.py @@ -3,8 +3,10 @@ from __future__ import (absolute_import, division, print_function) __metaclass__ = type import logging +import os import re import runpy +import sys import warnings BUILTIN_FILTERER_FILTER = logging.Filterer.filter @@ -69,7 +71,19 @@ def main(): # Python 2.7 cannot use the -W option to match warning text after a colon. This makes it impossible to match specific warning messages. warnings.filterwarnings('ignore', message_filter) - runpy.run_module('pip.__main__', run_name='__main__', alter_sys=True) + get_pip = os.environ.get('GET_PIP') + + try: + if get_pip: + directory, filename = os.path.split(get_pip) + module = os.path.splitext(filename)[0] + sys.path.insert(0, directory) + runpy.run_module(module, run_name='__main__', alter_sys=True) + else: + runpy.run_module('pip.__main__', run_name='__main__', alter_sys=True) + except ImportError as ex: + print('pip is unavailable: %s' % ex) + sys.exit(1) if __name__ == '__main__': diff --git a/test/lib/ansible_test/_util/target/setup/requirements.py b/test/lib/ansible_test/_util/target/setup/requirements.py index 0e3b1e63..f460c5c5 100644 --- a/test/lib/ansible_test/_util/target/setup/requirements.py +++ b/test/lib/ansible_test/_util/target/setup/requirements.py @@ -38,6 +38,11 @@ except ImportError: # noinspection PyProtectedMember from pipes import quote as cmd_quote +try: + from urllib.request import urlopen +except ImportError: + from urllib import urlopen + ENCODING = 'utf-8' PAYLOAD = b'{payload}' # base-64 encoded JSON payload which will be populated before this script is executed @@ -70,6 +75,38 @@ def main(): # type: () -> None sys.exit(1) +# noinspection PyUnusedLocal +def bootstrap(pip, options): # type: (str, t.Dict[str, t.Any]) -> None + """Bootstrap pip and related packages in an empty virtual environment.""" + pip_version = options['pip_version'] + packages = options['packages'] + + url = 'https://ansible-ci-files.s3.amazonaws.com/ansible-test/get-pip-%s.py' % pip_version + cache_path = os.path.expanduser('~/.ansible/test/cache/get_pip_%s.py' % pip_version.replace(".", "_")) + temp_path = cache_path + '.download' + + if os.path.exists(cache_path): + log('Using cached pip %s bootstrap script: %s' % (pip_version, cache_path)) + else: + log('Downloading pip %s bootstrap script: %s' % (pip_version, url)) + + make_dirs(os.path.dirname(cache_path)) + download_file(url, temp_path) + shutil.move(temp_path, cache_path) + + log('Cached pip %s bootstrap script: %s' % (pip_version, cache_path)) + + env = common_pip_environment() + env.update(GET_PIP=cache_path) + + options = common_pip_options() + options.extend(packages) + + command = [sys.executable, pip] + options + + execute_command(command, env=env) + + def install(pip, options): # type: (str, t.Dict[str, t.Any]) -> None """Perform a pip install.""" requirements = options['requirements'] @@ -92,7 +129,9 @@ def install(pip, options): # type: (str, t.Dict[str, t.Any]) -> None command = [sys.executable, pip, 'install'] + options - execute_command(command, tempdir) + env = common_pip_environment() + + execute_command(command, env=env, cwd=tempdir) finally: remove_tree(tempdir) @@ -107,13 +146,36 @@ def uninstall(pip, options): # type: (str, t.Dict[str, t.Any]) -> None command = [sys.executable, pip, 'uninstall', '-y'] + options + env = common_pip_environment() + try: - execute_command(command, capture=True) + execute_command(command, env=env, capture=True) except SubprocessError: if not ignore_errors: raise +# noinspection PyUnusedLocal +def version(pip, options): # type: (str, t.Dict[str, t.Any]) -> None + """Report the pip version.""" + del options + + options = common_pip_options() + + command = [sys.executable, pip, '-V'] + options + + env = common_pip_environment() + + execute_command(command, env=env, capture=True) + + +def common_pip_environment(): # type: () -> t.Dict[str, str] + """Return common environment variables used to run pip.""" + env = os.environ.copy() + + return env + + def common_pip_options(): # type: () -> t.List[str] """Return a list of common pip options.""" return [ @@ -131,6 +193,13 @@ def devnull(): # type: () -> t.IO[bytes] return devnull.file +def download_file(url, path): # type: (str, str) -> None + """Download the given URL to the specified file path.""" + with open(to_bytes(path), 'wb') as saved_file: + download = urlopen(url) + shutil.copyfileobj(download, saved_file) + + class ApplicationError(Exception): """Base class for application exceptions.""" @@ -158,7 +227,7 @@ def log(message, verbosity=0): # type: (str, int) -> None CONSOLE.flush() -def execute_command(cmd, cwd=None, capture=False): # type: (t.List[str], t.Optional[str], bool) -> None +def execute_command(cmd, cwd=None, capture=False, env=None): # type: (t.List[str], t.Optional[str], bool, t.Optional[t.Dict[str, str]]) -> None """Execute the specified command.""" log('Execute command: %s' % ' '.join(cmd_quote(c) for c in cmd), verbosity=1) @@ -171,7 +240,8 @@ def execute_command(cmd, cwd=None, capture=False): # type: (t.List[str], t.Opti stdout = None stderr = None - process = subprocess.Popen(cmd_bytes, cwd=to_optional_bytes(cwd), stdin=devnull(), stdout=stdout, stderr=stderr) # pylint: disable=consider-using-with + cwd_bytes = to_optional_bytes(cwd) + process = subprocess.Popen(cmd_bytes, cwd=cwd_bytes, stdin=devnull(), stdout=stdout, stderr=stderr, env=env) # pylint: disable=consider-using-with stdout_bytes, stderr_bytes = process.communicate() stdout_text = to_optional_text(stdout_bytes) or u'' stderr_text = to_optional_text(stderr_bytes) or u'' diff --git a/test/sanity/code-smell/package-data.py b/test/sanity/code-smell/package-data.py index 921cb197..06f3f916 100644 --- a/test/sanity/code-smell/package-data.py +++ b/test/sanity/code-smell/package-data.py @@ -223,8 +223,9 @@ def install_sdist(tmp_dir, sdist_dir): raise Exception('sdist install failed:\n%s' % stderr) # Determine the prefix for the installed files - match = re.search('^creating (%s/.*?/(?:site|dist)-packages)/ansible$' % + match = re.search('^copying .* -> (%s/.*?/(?:site|dist)-packages)/ansible$' % tmp_dir, stdout, flags=re.M) + return match.group(1) diff --git a/test/sanity/ignore.txt b/test/sanity/ignore.txt index 4a3bb620..058331e1 100644 --- a/test/sanity/ignore.txt +++ b/test/sanity/ignore.txt @@ -1,3 +1,4 @@ +.azure-pipelines/scripts/publish-codecov.py replace-urlopen docs/docsite/rst/dev_guide/testing/sanity/no-smart-quotes.rst no-smart-quotes docs/docsite/rst/locales/ja/LC_MESSAGES/dev_guide.po no-smart-quotes # Translation of the no-smart-quotes rule examples/play.yml shebang @@ -183,6 +184,7 @@ test/integration/targets/win_script/files/test_script_with_splatting.ps1 pslint: test/integration/targets/windows-minimal/library/win_ping_syntax_error.ps1 pslint!skip test/lib/ansible_test/_data/requirements/sanity.pslint.ps1 pslint:PSCustomUseLiteralPath # Uses wildcards on purpose test/lib/ansible_test/_util/target/setup/ConfigureRemotingForAnsible.ps1 pslint:PSCustomUseLiteralPath +test/lib/ansible_test/_util/target/setup/requirements.py replace-urlopen test/support/integration/plugins/inventory/aws_ec2.py pylint:use-a-generator test/support/integration/plugins/module_utils/network/common/utils.py pylint:use-a-generator test/support/integration/plugins/modules/ec2_group.py pylint:use-a-generator diff --git a/test/units/galaxy/test_collection.py b/test/units/galaxy/test_collection.py index 3de2e89a..65243df1 100644 --- a/test/units/galaxy/test_collection.py +++ b/test/units/galaxy/test_collection.py @@ -218,7 +218,49 @@ def server_config(monkeypatch): @pytest.mark.parametrize('global_ignore_certs', [True, False]) -def test_validate_certs(global_ignore_certs, server_config, monkeypatch): +def test_validate_certs(global_ignore_certs, monkeypatch): + cli_args = [ + 'ansible-galaxy', + 'collection', + 'install', + 'namespace.collection:1.0.0', + ] + if global_ignore_certs: + cli_args.append('--ignore-certs') + + galaxy_cli = GalaxyCLI(args=cli_args) + mock_execute_install = MagicMock() + monkeypatch.setattr(galaxy_cli, '_execute_install_collection', mock_execute_install) + galaxy_cli.run() + + assert len(galaxy_cli.api_servers) == 1 + assert galaxy_cli.api_servers[0].validate_certs is not global_ignore_certs + + +@pytest.mark.parametrize('global_ignore_certs', [True, False]) +def test_validate_certs_with_server_url(global_ignore_certs, monkeypatch): + cli_args = [ + 'ansible-galaxy', + 'collection', + 'install', + 'namespace.collection:1.0.0', + '-s', + 'https://galaxy.ansible.com' + ] + if global_ignore_certs: + cli_args.append('--ignore-certs') + + galaxy_cli = GalaxyCLI(args=cli_args) + mock_execute_install = MagicMock() + monkeypatch.setattr(galaxy_cli, '_execute_install_collection', mock_execute_install) + galaxy_cli.run() + + assert len(galaxy_cli.api_servers) == 1 + assert galaxy_cli.api_servers[0].validate_certs is not global_ignore_certs + + +@pytest.mark.parametrize('global_ignore_certs', [True, False]) +def test_validate_certs_with_server_config(global_ignore_certs, server_config, monkeypatch): get_plugin_options = MagicMock(side_effect=server_config) monkeypatch.setattr(C.config, 'get_plugin_options', get_plugin_options) @@ -289,6 +331,45 @@ def test_build_existing_output_with_force(collection_input): assert tarfile.is_tarfile(existing_output) +def test_build_with_existing_files_and_manifest(collection_input): + input_dir, output_dir = collection_input + + with open(os.path.join(input_dir, 'MANIFEST.json'), "wb") as fd: + fd.write(b'{"collection_info": {"version": "6.6.6"}, "version": 1}') + + with open(os.path.join(input_dir, 'FILES.json'), "wb") as fd: + fd.write(b'{"files": [], "format": 1}') + + with open(os.path.join(input_dir, "plugins", "MANIFEST.json"), "wb") as fd: + fd.write(b"test data that should be in build") + + collection.build_collection(to_text(input_dir, errors='surrogate_or_strict'), to_text(output_dir, errors='surrogate_or_strict'), False) + + output_artifact = os.path.join(output_dir, 'ansible_namespace-collection-0.1.0.tar.gz') + assert tarfile.is_tarfile(output_artifact) + + with tarfile.open(output_artifact, mode='r') as actual: + members = actual.getmembers() + + manifest_file = next(m for m in members if m.path == "MANIFEST.json") + manifest_file_obj = actual.extractfile(manifest_file.name) + manifest_file_text = manifest_file_obj.read() + manifest_file_obj.close() + assert manifest_file_text != b'{"collection_info": {"version": "6.6.6"}, "version": 1}' + + json_file = next(m for m in members if m.path == "MANIFEST.json") + json_file_obj = actual.extractfile(json_file.name) + json_file_text = json_file_obj.read() + json_file_obj.close() + assert json_file_text != b'{"files": [], "format": 1}' + + sub_manifest_file = next(m for m in members if m.path == "plugins/MANIFEST.json") + sub_manifest_file_obj = actual.extractfile(sub_manifest_file.name) + sub_manifest_file_text = sub_manifest_file_obj.read() + sub_manifest_file_obj.close() + assert sub_manifest_file_text == b"test data that should be in build" + + @pytest.mark.parametrize('galaxy_yml_dir', [b'namespace: value: broken'], indirect=True) def test_invalid_yaml_galaxy_file(galaxy_yml_dir): galaxy_file = os.path.join(galaxy_yml_dir, b'galaxy.yml') diff --git a/test/units/module_utils/facts/virtual/test_linux.py b/test/units/module_utils/facts/virtual/test_linux.py index 25503750..7c13299e 100644 --- a/test/units/module_utils/facts/virtual/test_linux.py +++ b/test/units/module_utils/facts/virtual/test_linux.py @@ -8,6 +8,30 @@ __metaclass__ = type from ansible.module_utils.facts.virtual import linux +def mock_os_path_is_file_docker(filename): + if filename in ('/.dockerenv', '/.dockerinit'): + return True + return False + + +def test_get_virtual_facts_docker(mocker): + mocker.patch('os.path.exists', mock_os_path_is_file_docker) + + module = mocker.Mock() + module.run_command.return_value = (0, '', '') + inst = linux.LinuxVirtual(module) + facts = inst.get_virtual_facts() + + expected = { + 'virtualization_role': 'guest', + 'virtualization_tech_host': set(), + 'virtualization_type': 'docker', + 'virtualization_tech_guest': set(['docker', 'container']), + } + + assert facts == expected + + def test_get_virtual_facts_bhyve(mocker): mocker.patch('os.path.exists', return_value=False) mocker.patch('ansible.module_utils.facts.virtual.linux.get_file_content', return_value='') diff --git a/test/units/parsing/yaml/test_loader.py b/test/units/parsing/yaml/test_loader.py index d6989f44..fbe69a97 100644 --- a/test/units/parsing/yaml/test_loader.py +++ b/test/units/parsing/yaml/test_loader.py @@ -35,12 +35,8 @@ from ansible.parsing.yaml.dumper import AnsibleDumper from units.mock.yaml_helper import YamlTestUtils from units.mock.vault_helper import TextVaultSecret -try: - from _yaml import ParserError - from _yaml import ScannerError -except ImportError: - from yaml.parser import ParserError - from yaml.scanner import ScannerError +from yaml.parser import ParserError +from yaml.scanner import ScannerError class NameStringIO(StringIO): diff --git a/test/units/plugins/become/test_sudo.py b/test/units/plugins/become/test_sudo.py index 8ccb2a12..67eb9a46 100644 --- a/test/units/plugins/become/test_sudo.py +++ b/test/units/plugins/become/test_sudo.py @@ -38,3 +38,30 @@ def test_sudo(mocker, parser, reset_cli_args): cmd = sudo.build_become_command('/bin/foo', sh) assert re.match(r"""sudo\s+-s\s-H\s+-p "\[sudo via ansible, key=.+?\] password:" -u foo /bin/bash -c 'echo BECOME-SUCCESS-.+? ; /bin/foo'""", cmd), cmd + + sudo.set_options(direct={ + 'become_user': 'foo', + 'become_flags': '-snH', + 'become_pass': 'testpass', + }) + + cmd = sudo.build_become_command('/bin/foo', sh) + assert re.match(r"""sudo\s+-sH\s+-p "\[sudo via ansible, key=.+?\] password:" -u foo /bin/bash -c 'echo BECOME-SUCCESS-.+? ; /bin/foo'""", cmd), cmd + + sudo.set_options(direct={ + 'become_user': 'foo', + 'become_flags': '--non-interactive -s -H', + 'become_pass': 'testpass', + }) + + cmd = sudo.build_become_command('/bin/foo', sh) + assert re.match(r"""sudo\s+-s\s-H\s+-p "\[sudo via ansible, key=.+?\] password:" -u foo /bin/bash -c 'echo BECOME-SUCCESS-.+? ; /bin/foo'""", cmd), cmd + + sudo.set_options(direct={ + 'become_user': 'foo', + 'become_flags': '--non-interactive -nC5 -s -H', + 'become_pass': 'testpass', + }) + + cmd = sudo.build_become_command('/bin/foo', sh) + assert re.match(r"""sudo\s+-C5\s-s\s-H\s+-p "\[sudo via ansible, key=.+?\] password:" -u foo /bin/bash -c 'echo BECOME-SUCCESS-.+? ; /bin/foo'""", cmd), cmd diff --git a/test/units/plugins/connection/test_ssh.py b/test/units/plugins/connection/test_ssh.py index d693313f..9b3e3c9d 100644 --- a/test/units/plugins/connection/test_ssh.py +++ b/test/units/plugins/connection/test_ssh.py @@ -102,6 +102,7 @@ class TestConnectionBaseClass(unittest.TestCase): def test_plugins_connection_ssh__examine_output(self): pc = PlayContext() new_stdin = StringIO() + become_success_token = b'BECOME-SUCCESS-abcdefghijklmnopqrstuvxyz' conn = connection_loader.get('ssh', pc, new_stdin) conn.set_become_plugin(become_loader.get('sudo')) @@ -112,24 +113,16 @@ class TestConnectionBaseClass(unittest.TestCase): conn.become.check_missing_password = MagicMock() def _check_password_prompt(line): - if b'foo' in line: - return True - return False + return b'foo' in line def _check_become_success(line): - if b'BECOME-SUCCESS-abcdefghijklmnopqrstuvxyz' in line: - return True - return False + return become_success_token in line def _check_incorrect_password(line): - if b'incorrect password' in line: - return True - return False + return b'incorrect password' in line def _check_missing_password(line): - if b'bad password' in line: - return True - return False + return b'bad password' in line # test examining output for prompt conn._flags = dict( @@ -172,9 +165,9 @@ class TestConnectionBaseClass(unittest.TestCase): pc.prompt = False conn.become.prompt = False - pc.success_key = u'BECOME-SUCCESS-abcdefghijklmnopqrstuvxyz' - conn.become.success = u'BECOME-SUCCESS-abcdefghijklmnopqrstuvxyz' - output, unprocessed = conn._examine_output(u'source', u'state', b'line 1\nline 2\nBECOME-SUCCESS-abcdefghijklmnopqrstuvxyz\nline 3\n', False) + pc.success_key = str(become_success_token) + conn.become.success = str(become_success_token) + output, unprocessed = conn._examine_output(u'source', u'state', b'line 1\nline 2\n%s\nline 3\n' % become_success_token, False) self.assertEqual(output, b'line 1\nline 2\nline 3\n') self.assertEqual(unprocessed, b'') self.assertFalse(conn._flags['become_prompt']) @@ -182,6 +175,23 @@ class TestConnectionBaseClass(unittest.TestCase): self.assertFalse(conn._flags['become_error']) self.assertFalse(conn._flags['become_nopasswd_error']) + # test we dont detect become success from ssh debug: lines + conn._flags = dict( + become_prompt=False, + become_success=False, + become_error=False, + become_nopasswd_error=False, + ) + + pc.prompt = False + conn.become.prompt = True + pc.success_key = str(become_success_token) + conn.become.success = str(become_success_token) + output, unprocessed = conn._examine_output(u'source', u'state', b'line 1\nline 2\ndebug1: %s\nline 3\n' % become_success_token, False) + self.assertEqual(output, b'line 1\nline 2\ndebug1: %s\nline 3\n' % become_success_token) + self.assertEqual(unprocessed, b'') + self.assertFalse(conn._flags['become_success']) + # test examining output for become failure conn._flags = dict( become_prompt=False, |