You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
ansible/docs/docsite/rst/shared_snippets/installing_multiple_collect...

25 lines
1.0 KiB
Plaintext

Backport/2.9/docs2 (#63524) * Update sros_config.py (#63132) (cherry picked from commit b3deab4319fe1e793d36307093e1639a49c28175) * add note about collection links (#63346) (cherry picked from commit bdd0fac606265f92e6521540106accf19a1ae4d0) * Nosh module documentation update (#63303) * detail the 'status' dictionary * did not add individual descriptions, see nosh documentation for those * sample: False not being rendered unless 'False' is quoted (cherry picked from commit df283788e562470741ebed15dc4374190316c352) * Move galaxy appendix info to a new Galaxy section (#63356) * start galaxy docs restructure * shared snippets in txt files * moved all content to galaxy section (cherry picked from commit ae265bc5464a89935bfe1be6af050b94e09b6eb9) * Enter should be Italics as it is a menu option (#63441) (cherry picked from commit 7a8c9098763a2b6a30d54d69aa94b2ecf1ee516d) * ini_file: remove incorrect documentation (#63394) (cherry picked from commit ab249a469eaa9cb27c3f17813a60fe23ee2d7315) * Changed with_items to loop in VMware example (#63022) (cherry picked from commit 876a2d57be5683ab5cfa90268a4712187c092fdb) * ovirt update fetch_nested param doc (#63191) (cherry picked from commit 0beab6bf699fc014aeb7bb74af7a692b2e7d462f) * Update 'delete' parameter description in synchronize module (#63450) Co-Authored-By: Abhijeet Kasurde <akasurde@redhat.com> (cherry picked from commit da46800f1b0576a4a2cc5d6ca20b24efe58ea3d7) * Update unarchive.py - Further clarify extra_opts (#58102) Update the description in the options to help assist with what the module is looking for in the extra_opts. #31873 alone is not enough since if you are not familiar with the option given in the example it may not be obvious that both elements are part of the same option instead of being two different options. Co-Authored-By: Alicia Cozine <879121+acozine@users.noreply.github.com> (cherry picked from commit e967060b9f64dffdf4b7febb27f64dd3a411f59b) * ovirt_vm add warning about next run configuration (#63458) (cherry picked from commit 16e49fdd44134356323d10207715f7943ef0f44f) * Fix doc - porting_guide_2.8 value example (#63493) (cherry picked from commit e0f67b58ce85b3fbb5930e19ad76d27834cf6c34) * Fix warnings for ufw examples (#63505) (cherry picked from commit e4eea0510cd89124c3a20f4d9937e7c015a46597)
5 years ago
You can also setup a ``requirements.yml`` file to install multiple collections in one command. This file is a YAML file in the format:
.. code-block:: yaml+jinja
---
collections:
# With just the collection name
- my_namespace.my_collection
# With the collection name, version, and source options
- name: my_namespace.my_other_collection
version: 'version range identifiers (default: ``*``)'
source: 'The Galaxy URL to pull the collection from (default: ``--api-server`` from cmdline)'
The ``version`` key can take in the same range identifier format documented above.
Roles can also be specified and placed under the ``roles`` key. The values follow the same format as a requirements
file used in older Ansible releases.
.. note::
While both roles and collections can be specified in one requirements file, they need to be installed separately.
The ``ansible-galaxy role install -r requirements.yml`` will only install roles and
``ansible-galaxy collection install -r requirements.yml -p ./`` will only install collections.