Adding upstream version 2.14.3.upstream/2.14.3upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

2 files changed, 723 insertions, 0 deletions

diff --git a/docs/docsite/rst/galaxy/dev_guide.rst b/docs/docsite/rst/galaxy/dev_guide.rst
new file mode 100644
index 0000000..01a92d0
--- /dev/null
+++ b/docs/docsite/rst/galaxy/dev_guide.rst
@@ -0,0 +1,226 @@
+.. _developing_galaxy:
+
+**********************
+Galaxy Developer Guide
+**********************
+
+You can host collections and roles on Galaxy to share with the Ansible community. Galaxy content is formatted in pre-packaged units of work such as :ref:`roles <playbooks_reuse_roles>`, and new in Galaxy 3.2, :ref:`collections <collections>`.
+You can create roles for provisioning infrastructure, deploying applications, and all of the tasks you do everyday. Taking this a step further, you can create collections which provide a comprehensive package of automation that may include multiple playbooks, roles, modules, and plugins.
+
+.. contents::
+   :local:
+   :depth: 2
+
+.. _creating_collections_galaxy:
+
+Creating collections for Galaxy
+===============================
+
+Collections are a distribution format for Ansible content. You can use collections to package and distribute playbooks, roles, modules, and plugins.
+You can publish and use collections through `Ansible Galaxy <https://galaxy.ansible.com>`_.
+
+See :ref:`developing_collections` for details on how to create collections.
+
+.. _creating_roles_galaxy:
+
+
+Creating roles for Galaxy
+=========================
+
+Use the ``init`` command to initialize the base structure of a new role, saving time on creating the various directories and main.yml files a role requires
+
+.. code-block:: bash
+
+   $ ansible-galaxy init role_name
+
+The above will create the following directory structure in the current working directory:
+
+.. code-block:: text
+
+   role_name/
+       README.md
+       .travis.yml
+       defaults/
+           main.yml
+       files/
+       handlers/
+           main.yml
+       meta/
+           main.yml
+       templates/
+       tests/
+           inventory
+           test.yml
+       vars/
+           main.yml
+
+If you want to create a repository for the role, the repository root should be `role_name`.
+
+Force
+-----
+
+If a directory matching the name of the role already exists in the current working directory, the init command will result in an error. To ignore the error
+use the ``--force`` option. Force will create the above subdirectories and files, replacing anything that matches.
+
+Container enabled
+-----------------
+
+If you are creating a Container Enabled role, pass ``--type container`` to ``ansible-galaxy init``. This will create the same directory structure as above, but populate it
+with default files appropriate for a Container Enabled role. For instance, the README.md has a slightly different structure, the *.travis.yml* file tests
+the role using `Ansible Container <https://github.com/ansible/ansible-container>`_, and the meta directory includes a *container.yml* file.
+
+Using a custom role skeleton
+----------------------------
+
+A custom role skeleton directory can be supplied as follows:
+
+.. code-block:: bash
+
+   $ ansible-galaxy init --role-skeleton=/path/to/skeleton role_name
+
+When a skeleton is provided, init will:
+
+- copy all files and directories from the skeleton to the new role
+- any .j2 files found outside of a templates folder will be rendered as templates. The only useful variable at the moment is role_name
+- The .git folder and any .git_keep files will not be copied
+
+Alternatively, the role_skeleton and ignoring of files can be configured via ansible.cfg
+
+.. code-block:: text
+
+  [galaxy]
+  role_skeleton = /path/to/skeleton
+  role_skeleton_ignore = ^.git$,^.*/.git_keep$
+
+Authenticate with Galaxy
+------------------------
+
+Using the ``import``, ``delete`` and ``setup`` commands to manage your roles on the Galaxy website requires authentication in the form of an API key, you must create an account on the Galaxy website.
+
+#. Log in to the Galaxy website and open the `Preferences <https://galaxy.ansible.com/me/preferences>`_ view.
+#. Select **Show API key** and then copy it.
+
+#. Save your token in the path set in the :ref:`GALAXY_TOKEN_PATH`.
+
+
+Import a role
+-------------
+
+The ``import`` command requires that you first authenticate using the ``login`` command. Once authenticated you can import any GitHub repository that you own or have been granted access.
+
+Use the following to import to role:
+
+.. code-block:: bash
+
+  $ ansible-galaxy import github_user github_repo
+
+By default the command will wait for Galaxy to complete the import process, displaying the results as the import progresses:
+
+.. code-block:: text
+
+      Successfully submitted import request 41
+      Starting import 41: role_name=myrole repo=githubuser/ansible-role-repo ref=
+      Retrieving GitHub repo githubuser/ansible-role-repo
+      Accessing branch: devel
+      Parsing and validating meta/main.yml
+      Parsing galaxy_tags
+      Parsing platforms
+      Adding dependencies
+      Parsing and validating README.md
+      Adding repo tags as role versions
+      Import completed
+      Status SUCCESS : warnings=0 errors=0
+
+Branch
+^^^^^^
+
+Use the ``--branch`` option to import a specific branch. If not specified, the default branch for the repo will be used.
+
+Role name
+^^^^^^^^^
+
+By default the name given to the role will be derived from the GitHub repository name. However, you can use the ``--role-name`` option to override this and set the name.
+
+No wait
+^^^^^^^
+
+If the ``--no-wait`` option is present, the command will not wait for results. Results of the most recent import for any of your roles is available on the Galaxy web site by visiting *My Imports*.
+
+Delete a role
+-------------
+
+The ``delete`` command requires that you first authenticate using the ``login`` command. Once authenticated you can remove a role from the Galaxy web site. You are only allowed to remove roles where you have access to the repository in GitHub.
+
+Use the following to delete a role:
+
+.. code-block:: bash
+
+  $ ansible-galaxy delete github_user github_repo
+
+This only removes the role from Galaxy. It does not remove or alter the actual GitHub repository.
+
+
+Travis integrations
+-------------------
+
+You can create an integration or connection between a role in Galaxy and `Travis <https://travis-ci.org>`_. Once the connection is established, a build in Travis will
+automatically trigger an import in Galaxy, updating the search index with the latest information about the role.
+
+You create the integration using the ``setup`` command, but before an integration can be created, you must first authenticate using the ``login`` command; you will
+also need an account in Travis, and your Travis token. Once you're ready, use the following command to create the integration:
+
+.. code-block:: bash
+
+  $ ansible-galaxy setup travis github_user github_repo xxx-travis-token-xxx
+
+The setup command requires your Travis token, however the token is not stored in Galaxy. It is used along with the GitHub username and repo to create a hash as described
+in `the Travis documentation <https://docs.travis-ci.com/user/notifications/>`_. The hash is stored in Galaxy and used to verify notifications received from Travis.
+
+The setup command enables Galaxy to respond to notifications. To configure Travis to run a build on your repository and send a notification, follow the
+`Travis getting started guide <https://docs.travis-ci.com/user/getting-started/>`_.
+
+To instruct Travis to notify Galaxy when a build completes, add the following to your .travis.yml file:
+
+.. code-block:: text
+
+    notifications:
+        webhooks: https://galaxy.ansible.com/api/v1/notifications/
+
+
+List Travis integrations
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+Use the ``--list`` option to display your Travis integrations:
+
+.. code-block:: bash
+
+      $ ansible-galaxy setup --list
+
+
+      ID         Source     Repo
+      ---------- ---------- ----------
+      2          travis     github_user/github_repo
+      1          travis     github_user/github_repo
+
+
+Remove Travis integrations
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Use the ``--remove`` option to disable and remove a Travis integration:
+
+  .. code-block:: bash
+
+    $ ansible-galaxy setup --remove ID
+
+Provide the ID of the integration to be disabled. You can find the ID by using the ``--list`` option.
+
+
+.. seealso::
+  :ref:`collections`
+    Shareable collections of modules, playbooks and roles
+  :ref:`playbooks_reuse_roles`
+    All about ansible roles
+  `Mailing List <https://groups.google.com/group/ansible-project>`_
+    Questions? Help? Ideas?  Stop by the list on Google Groups
+  :ref:`communication_irc`
+    How to join Ansible chat channels
diff --git a/docs/docsite/rst/galaxy/user_guide.rst b/docs/docsite/rst/galaxy/user_guide.rst
new file mode 100644
index 0000000..c5a1e19
--- /dev/null
+++ b/docs/docsite/rst/galaxy/user_guide.rst
@@ -0,0 +1,497 @@
+.. _using_galaxy:
+.. _ansible_galaxy:
+
+*****************
+Galaxy User Guide
+*****************
+
+:dfn:`Ansible Galaxy` refers to the `Galaxy <https://galaxy.ansible.com>`_  website, a free site for finding, downloading, and sharing community developed roles.
+
+Use Galaxy to jump-start your automation project with great content from the Ansible community. Galaxy provides pre-packaged units of work such as :ref:`roles <playbooks_reuse_roles>`, and new in Galaxy 3.2, :ref:`collections <collections>`
+You can find roles for provisioning infrastructure, deploying applications, and all of the tasks you do everyday. The collection format provides a comprehensive package of automation that may include multiple playbooks, roles, modules, and plugins.
+
+.. contents::
+   :local:
+   :depth: 2
+.. _finding_galaxy_collections:
+
+Finding collections on Galaxy
+=============================
+
+To find collections on Galaxy:
+
+#. Click the :guilabel:`Search` icon in the left-hand navigation.
+#. Set the filter to *collection*.
+#. Set other filters and press :guilabel:`enter`.
+
+Galaxy presents a list of collections that match your search criteria.
+
+.. _installing_galaxy_collections:
+
+
+Installing collections
+======================
+
+
+Installing a collection from Galaxy
+-----------------------------------
+
+.. include:: ../shared_snippets/installing_collections.txt
+
+.. _installing_ah_collection:
+
+Downloading a collection from Automation Hub
+----------------------------------------------------
+
+You can download collections from Automation Hub at the command line. Automation Hub content is available to subscribers only, so you must download an API token and configure your local environment to provide it before you can you download collections. To download a collection from Automation Hub with the ``ansible-galaxy`` command:
+
+1. Get your Automation Hub API token. Go to https://cloud.redhat.com/ansible/automation-hub/token/ and click :guilabel:`Load token` from the version dropdown to copy your API token.
+2. Configure Red Hat Automation Hub server in the ``server_list``  option under the ``[galaxy]`` section in your :file:`ansible.cfg` file.
+
+  .. code-block:: ini
+
+      [galaxy]
+      server_list = automation_hub
+
+      [galaxy_server.automation_hub]
+      url=https://console.redhat.com/api/automation-hub/
+      auth_url=https://sso.redhat.com/auth/realms/redhat-external/protocol/openid-connect/token
+      token=my_ah_token
+
+3. Download the collection hosted in Automation Hub.
+
+  .. code-block:: bash
+
+     ansible-galaxy collection install my_namespace.my_collection
+
+.. seealso::
+  `Getting started with Automation Hub <https://www.ansible.com/blog/getting-started-with-ansible-hub>`_
+    An introduction to Automation Hub
+
+Installing an older version of a collection
+-------------------------------------------
+
+.. include:: ../shared_snippets/installing_older_collection.txt
+
+Install multiple collections with a requirements file
+-----------------------------------------------------
+
+.. include:: ../shared_snippets/installing_multiple_collections.txt
+
+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
+
+Listing installed collections
+-----------------------------
+
+To list installed collections, run ``ansible-galaxy collection list``. See :ref:`collections_listing` for more details.
+
+
+Configuring the ``ansible-galaxy`` client
+------------------------------------------
+
+.. include:: ../shared_snippets/galaxy_server_list.txt
+
+.. _finding_galaxy_roles:
+
+Finding roles on Galaxy
+=======================
+
+Search the Galaxy database by tags, platforms, author and multiple keywords. For example:
+
+.. code-block:: bash
+
+    $ ansible-galaxy search elasticsearch --author geerlingguy
+
+The search command will return a list of the first 1000 results matching your search:
+
+.. code-block:: text
+
+    Found 2 roles matching your search:
+
+    Name                              Description
+    ----                              -----------
+    geerlingguy.elasticsearch         Elasticsearch for Linux.
+    geerlingguy.elasticsearch-curator Elasticsearch curator for Linux.
+
+
+Get more information about a role
+---------------------------------
+
+Use the ``info`` command to view more detail about a specific role:
+
+.. code-block:: bash
+
+    $ ansible-galaxy info username.role_name
+
+This returns everything found in Galaxy for the role:
+
+.. code-block:: text
+
+    Role: username.role_name
+        description: Installs and configures a thing, a distributed, highly available NoSQL thing.
+        active: True
+        commit: c01947b7bc89ebc0b8a2e298b87ab416aed9dd57
+        commit_message: Adding travis
+        commit_url: https://github.com/username/repo_name/commit/c01947b7bc89ebc0b8a2e298b87ab
+        company: My Company, Inc.
+        created: 2015-12-08T14:17:52.773Z
+        download_count: 1
+        forks_count: 0
+        github_branch:
+        github_repo: repo_name
+        github_user: username
+        id: 6381
+        is_valid: True
+        issue_tracker_url:
+        license: Apache
+        min_ansible_version: 1.4
+        modified: 2015-12-08T18:43:49.085Z
+        namespace: username
+        open_issues_count: 0
+        path: /Users/username/projects/roles
+        scm: None
+        src: username.repo_name
+        stargazers_count: 0
+        travis_status_url: https://travis-ci.org/username/repo_name.svg?branch=main
+        version:
+        watchers_count: 1
+
+
+.. _installing_galaxy_roles:
+
+Installing roles from Galaxy
+============================
+
+The ``ansible-galaxy`` command comes bundled with Ansible, and you can use it to install roles from Galaxy or directly from a git based SCM. You can
+also use it to create a new role, remove roles, or perform tasks on the Galaxy website.
+
+The command line tool by default communicates with the Galaxy website API using the server address *https://galaxy.ansible.com*. If you run your own internal Galaxy server
+and want to use it instead of the default one, pass the ``--server`` option following the address of this galaxy server. You can set permanently this option by setting
+the Galaxy server value in your ``ansible.cfg`` file to use it . For information on setting the value in *ansible.cfg* see :ref:`galaxy_server`.
+
+
+Installing roles
+----------------
+
+Use the ``ansible-galaxy`` command to download roles from the `Galaxy website <https://galaxy.ansible.com>`_
+
+.. code-block:: bash
+
+  $ ansible-galaxy install namespace.role_name
+
+Setting where to install roles
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+By default, Ansible downloads roles to the first writable directory in the default list of paths ``~/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles``. This installs roles in the home directory of the user running ``ansible-galaxy``.
+
+You can override this with one of the following options:
+
+* Set the environment variable :envvar:`ANSIBLE_ROLES_PATH` in your session.
+* Use the ``--roles-path`` option for the ``ansible-galaxy`` command.
+* Define ``roles_path`` in an ``ansible.cfg`` file.
+
+The following provides an example of using ``--roles-path`` to install the role into the current working directory:
+
+.. code-block:: bash
+
+    $ ansible-galaxy install --roles-path . geerlingguy.apache
+
+.. seealso::
+
+   :ref:`intro_configuration`
+      All about configuration files
+
+Installing a specific version of a role
+---------------------------------------
+
+When the Galaxy server imports a role, it imports any git tags matching the `Semantic Version <https://semver.org/>`_ format as versions.
+In turn, you can download a specific version of a role by specifying one of the imported tags.
+
+To see the available versions for a role:
+
+#. Locate the role on the Galaxy search page.
+#. Click on the name to view more details, including the available versions.
+
+You can also navigate directly to the role using the /<namespace>/<role name>. For example, to view the role geerlingguy.apache, go to `<https://galaxy.ansible.com/geerlingguy/apache>`_.
+
+To install a specific version of a role from Galaxy, append a comma and the value of a GitHub release tag. For example:
+
+.. code-block:: bash
+
+   $ ansible-galaxy install geerlingguy.apache,1.0.0
+
+It is also possible to point directly to the git repository and specify a branch name or commit hash as the version. For example, the following will
+install a specific commit:
+
+.. code-block:: bash
+
+   $ ansible-galaxy install git+https://github.com/geerlingguy/ansible-role-apache.git,0b7cd353c0250e87a26e0499e59e7fd265cc2f25
+
+Installing multiple roles from a file
+-------------------------------------
+
+You can install multiple roles by including the roles in a :file:`requirements.yml` file. The format of the file is YAML, and the
+file extension must be either *.yml* or *.yaml*.
+
+Use the following command to install roles included in :file:`requirements.yml:`
+
+.. code-block:: bash
+
+    $ ansible-galaxy install -r requirements.yml
+
+Again, the extension is important. If the *.yml* extension is left off, the ``ansible-galaxy`` CLI assumes the file is in an older, now deprecated,
+"basic" format.
+
+Each role in the file will have one or more of the following attributes:
+
+   src
+     The source of the role. Use the format *namespace.role_name*, if downloading from Galaxy; otherwise, provide a URL pointing
+     to a repository within a git based SCM. See the examples below. This is a required attribute.
+   scm
+     Specify the SCM. As of this writing only *git* or *hg* are allowed. See the examples below. Defaults to *git*.
+   version:
+     The version of the role to download. Provide a release tag value, commit hash, or branch name. Defaults to the branch set as a default in the repository, otherwise defaults to the *master*.
+   name:
+     Download the role to a specific name. Defaults to the Galaxy name when downloading from Galaxy, otherwise it defaults
+     to the name of the repository.
+
+Use the following example as a guide for specifying roles in *requirements.yml*:
+
+.. code-block:: yaml
+
+    # from galaxy
+    - name: yatesr.timezone
+
+    # from locally cloned git repository (git+file:// requires full paths)
+    - src: git+file:///home/bennojoy/nginx
+
+    # from GitHub
+    - src: https://github.com/bennojoy/nginx
+
+    # from GitHub, overriding the name and specifying a specific tag
+    - name: nginx_role
+      src: https://github.com/bennojoy/nginx
+      version: main
+
+    # from GitHub, specifying a specific commit hash
+    - src: https://github.com/bennojoy/nginx
+      version: "ee8aa41"
+
+    # from a webserver, where the role is packaged in a tar.gz
+    - name: http-role-gz
+      src: https://some.webserver.example.com/files/main.tar.gz
+
+    # from a webserver, where the role is packaged in a tar.bz2
+    - name: http-role-bz2
+      src: https://some.webserver.example.com/files/main.tar.bz2
+
+    # from a webserver, where the role is packaged in a tar.xz (Python 3.x only)
+    - name: http-role-xz
+      src: https://some.webserver.example.com/files/main.tar.xz
+
+    # from Bitbucket
+    - src: git+https://bitbucket.org/willthames/git-ansible-galaxy
+      version: v1.4
+
+    # from Bitbucket, alternative syntax and caveats
+    - src: https://bitbucket.org/willthames/hg-ansible-galaxy
+      scm: hg
+
+    # from GitLab or other git-based scm, using git+ssh
+    - src: git@gitlab.company.com:mygroup/ansible-core.git
+      scm: git
+      version: "0.1"  # quoted, so YAML doesn't parse this as a floating-point value
+
+.. warning::
+
+   Embedding credentials into a SCM URL is not secure. Make sure to use safe auth options for security reasons. For example, use `SSH <https://help.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh>`_, `netrc <https://linux.die.net/man/5/netrc>`_ or `http.extraHeader <https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpextraHeader>`_/`url.<base>.pushInsteadOf <https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtpushInsteadOf>`_ in Git config to prevent your creds from being exposed in logs.
+
+Installing roles and collections from the same requirements.yml file
+---------------------------------------------------------------------
+
+You can install roles and collections from the same requirements files
+
+.. code-block:: yaml
+
+    ---
+    roles:
+      # Install a role from Ansible Galaxy.
+      - name: geerlingguy.java
+        version: "1.9.6" # note that ranges are not supported for roles
+
+    collections:
+      # Install a collection from Ansible Galaxy.
+      - name: geerlingguy.php_roles
+        version: ">=0.9.3"
+        source: https://galaxy.ansible.com
+
+Installing multiple roles from multiple files
+---------------------------------------------
+
+For large projects, the ``include`` directive in a :file:`requirements.yml` file provides the ability to split a large file into multiple smaller files.
+
+For example, a project may have a :file:`requirements.yml` file, and a :file:`webserver.yml` file.
+
+Below are the contents of the :file:`webserver.yml` file:
+
+.. code-block:: bash
+
+    # from github
+    - src: https://github.com/bennojoy/nginx
+
+    # from Bitbucket
+    - src: git+https://bitbucket.org/willthames/git-ansible-galaxy
+      version: v1.4
+
+The following shows the contents of the :file:`requirements.yml` file that now includes the :file:`webserver.yml` file:
+
+.. code-block:: bash
+
+  # from galaxy
+  - name: yatesr.timezone
+  - include: <path_to_requirements>/webserver.yml
+
+To install all the roles from both files, pass the root file, in this case :file:`requirements.yml` on the
+command line, as follows:
+
+.. code-block:: bash
+
+    $ ansible-galaxy install -r requirements.yml
+
+.. _galaxy_dependencies:
+
+Dependencies
+------------
+
+Roles can also be dependent on other roles, and when you install a role that has dependencies, those dependencies will automatically be installed to the ``roles_path``.
+
+There are two ways to define the dependencies of a role:
+
+* using ``meta/requirements.yml``
+* using ``meta/main.yml``
+
+Using ``meta/requirements.yml``
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. versionadded:: 2.10
+
+You can create the file ``meta/requirements.yml`` and define dependencies in the same format used for :file:`requirements.yml` described in the `Installing multiple roles from a file`_ section.
+
+From there, you can import or include the specified roles in your tasks.
+
+Using ``meta/main.yml``
+^^^^^^^^^^^^^^^^^^^^^^^
+
+Alternatively, you can specify role dependencies in the ``meta/main.yml`` file by providing a list of roles under the ``dependencies`` section. If the source of a role is Galaxy, you can simply specify the role in
+the format ``namespace.role_name``. You can also use the more complex format in :file:`requirements.yml`, allowing you to provide ``src``, ``scm``, ``version``, and ``name``.
+
+Dependencies installed that way, depending on other factors described below, will also be executed **before** this role is executed during play execution.
+To better understand how dependencies are handled during play execution, see :ref:`playbooks_reuse_roles`.
+
+The following shows an example ``meta/main.yml`` file with dependent roles:
+
+.. code-block:: yaml
+
+    ---
+    dependencies:
+      - geerlingguy.java
+
+    galaxy_info:
+      author: geerlingguy
+      description: Elasticsearch for Linux.
+      company: "Midwestern Mac, LLC"
+      license: "license (BSD, MIT)"
+      min_ansible_version: 2.4
+      platforms:
+      - name: EL
+        versions:
+        - all
+      - name: Debian
+        versions:
+        - all
+      - name: Ubuntu
+        versions:
+        - all
+      galaxy_tags:
+        - web
+        - system
+        - monitoring
+        - logging
+        - lucene
+        - elk
+        - elasticsearch
+
+Tags are inherited *down* the dependency chain. In order for tags to be applied to a role and all its dependencies, the tag should be applied to the role, not to all the tasks within a role.
+
+Roles listed as dependencies are subject to conditionals and tag filtering, and may not execute fully depending on
+what tags and conditionals are applied.
+
+If the source of a role is Galaxy, specify the role in the format *namespace.role_name*:
+
+.. code-block:: yaml
+
+    dependencies:
+      - geerlingguy.apache
+      - geerlingguy.ansible
+
+
+Alternately, you can specify the role dependencies in the complex form used in  :file:`requirements.yml` as follows:
+
+.. code-block:: yaml
+
+    dependencies:
+      - name: geerlingguy.ansible
+      - name: composer
+        src: git+https://github.com/geerlingguy/ansible-role-composer.git
+        version: 775396299f2da1f519f0d8885022ca2d6ee80ee8
+
+.. note::
+
+    Galaxy expects all role dependencies to exist in Galaxy, and therefore dependencies to be specified in the
+    ``namespace.role_name`` format. If you import a role with a dependency where the ``src`` value is a URL, the import process will fail.
+
+List installed roles
+--------------------
+
+Use ``list`` to show the name and version of each role installed in the *roles_path*.
+
+.. code-block:: bash
+
+    $ ansible-galaxy list
+      - ansible-network.network-engine, v2.7.2
+      - ansible-network.config_manager, v2.6.2
+      - ansible-network.cisco_nxos, v2.7.1
+      - ansible-network.vyos, v2.7.3
+      - ansible-network.cisco_ios, v2.7.0
+
+Remove an installed role
+------------------------
+
+Use ``remove`` to delete a role from *roles_path*:
+
+.. code-block:: bash
+
+    $ ansible-galaxy remove namespace.role_name
+
+
+.. seealso::
+  :ref:`collections`
+    Shareable collections of modules, playbooks and roles
+  :ref:`playbooks_reuse_roles`
+    Reusable tasks, handlers, and other files in a known directory structure
+  :ref:`command_line_tools`
+    Perform other related operations
+