diff --git a/docs/docsite/rst/collections_guide/collections_installing.rst b/docs/docsite/rst/collections_guide/collections_installing.rst index 12f6e67f4b8..880f78de4a7 100644 --- a/docs/docsite/rst/collections_guide/collections_installing.rst +++ b/docs/docsite/rst/collections_guide/collections_installing.rst @@ -11,7 +11,7 @@ Installing collections in containers ------------------------------------ You can install collections with their dependencies in containers known as Execution Environments. -See `Getting started with Execution Environments `_ for details. +See :ref:`getting_started_ee_index` for details. Installing collections with ``ansible-galaxy`` ---------------------------------------------- diff --git a/docs/docsite/rst/command_guide/index.rst b/docs/docsite/rst/command_guide/index.rst index 4027e3493d7..ca5b41d0e88 100644 --- a/docs/docsite/rst/command_guide/index.rst +++ b/docs/docsite/rst/command_guide/index.rst @@ -25,5 +25,5 @@ Ansible provides ad hoc commands and several utilities for performing various op `Ansible Navigator `_ A command-line tool and a TUI that provides a convenient user interface for most of the native Ansible command-line utilities and allows to run Ansible automation content - inside containers (`Execution Environments `_) + inside containers (:ref:`Execution Environments`) diff --git a/docs/docsite/rst/community/collection_contributors/collection_requirements.rst b/docs/docsite/rst/community/collection_contributors/collection_requirements.rst index 92e140a19a0..acd549632bb 100644 --- a/docs/docsite/rst/community/collection_contributors/collection_requirements.rst +++ b/docs/docsite/rst/community/collection_contributors/collection_requirements.rst @@ -199,7 +199,7 @@ Example: `meta/runtime.yml `_ building, they SHOULD be listed in corresponding files under the ``meta`` directory, specified in ``meta/execution-environment.yml``, and `verified `_. +If a collection has controller-side Python package and/or system package requirements, to allow easy :ref:`execution environment` building, they SHOULD be listed in corresponding files under the ``meta`` directory, specified in ``meta/execution-environment.yml``, and `verified `_. See the `Collection-level dependencies guide `_ for more information and `collection_template/meta `_ directory content as an example. diff --git a/docs/docsite/rst/dev_guide/developing_collections_structure.rst b/docs/docsite/rst/dev_guide/developing_collections_structure.rst index 6a82af60b69..6c15c31973e 100644 --- a/docs/docsite/rst/dev_guide/developing_collections_structure.rst +++ b/docs/docsite/rst/dev_guide/developing_collections_structure.rst @@ -290,7 +290,7 @@ execution_environments.yml ^^^^^^^^^^^^^^^^^^^^^^^^^^ If your collection has requirements, you can specify them in the ``execution-environment.yml`` file in the ``meta`` directory. -This ensures users do not need to add these requirements manually when building `Execution Environments `_ containing your collection. +This ensures users do not need to add these requirements manually when building :ref:`Execution Environments` containing your collection. See the `collection-level metadata guide `_ for details. .. seealso:: diff --git a/docs/docsite/rst/installation_guide/intro_installation.rst b/docs/docsite/rst/installation_guide/intro_installation.rst index 0526359984c..87d77a87967 100644 --- a/docs/docsite/rst/installation_guide/intro_installation.rst +++ b/docs/docsite/rst/installation_guide/intro_installation.rst @@ -194,7 +194,7 @@ Installing Ansible to containers ================================ Instead of installing Ansible content manually, you can simply build an execution environment container image or use one of the available community images as your control node. -See the `Getting started with Execution Environments guide `_ for details. +See :ref:`getting_started_ee_index` for details. .. _development_install: diff --git a/docs/docsite/rst/shared_snippets/basic_concepts.txt b/docs/docsite/rst/shared_snippets/basic_concepts.txt index a4f7ce06130..2b2c3efeeb6 100644 --- a/docs/docsite/rst/shared_snippets/basic_concepts.txt +++ b/docs/docsite/rst/shared_snippets/basic_concepts.txt @@ -2,7 +2,7 @@ Control node ============ The machine from which you run the Ansible CLI tools (``ansible-playbook`` , ``ansible``, ``ansible-vault`` and others). You can use any computer that meets the software requirements as a control node - laptops, shared desktops, and servers can all run Ansible. -You can also run Ansible in containers known as `Execution Environments `_. +You can also run Ansible in containers known as :ref:`Execution Environments`. Multiple control nodes are possible, but Ansible itself does not coordinate across them, see ``AAP`` for such features. diff --git a/docs/docsite/rst/tips_tricks/ansible_tips_tricks.rst b/docs/docsite/rst/tips_tricks/ansible_tips_tricks.rst index ac8a370ff2c..88746d3d8be 100644 --- a/docs/docsite/rst/tips_tricks/ansible_tips_tricks.rst +++ b/docs/docsite/rst/tips_tricks/ansible_tips_tricks.rst @@ -132,7 +132,7 @@ These tips apply to using Ansible, rather than to Ansible artifacts. Use Execution Environments -------------------------- -Reduce complexity with portable container images known as `Execution Environments `_. +Reduce complexity with portable container images known as :ref:`Execution Environments`. Try it in staging first -----------------------