Uploaded image for project: 'Product Technical Learning'
  1. Product Technical Learning
  2. PTL-5189

RH294-235: 7.5 - Deploying Roles from External Content Sources

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Minor Minor
    • RH294 - RHEL9.0-en-2-20221117
    • RH294
    • None
    • 7
    • en-US (English)

      URL:
      Reporter RHNID:
      Section: -
      Language: en-US (English)||||||||
      Workaround:

      Description: The syntax of the ansible-galaxy command has changed slightly since support for collections has been added. We really should be using the 'role' subcommand consistently :

      $ ansible-galaxy role -h
      usage: ansible-galaxy role [-h] ROLE_ACTION ...
      
      positional arguments:
        ROLE_ACTION
          init       Initialize new role with the base structure of a role.
          remove     Delete roles from roles_path.
          delete     Removes the role from Galaxy. It does not remove or alter the actual GitHub repository.
          list       Show the name and version of each role installed in the roles_path.
          search     Search the Galaxy database by tags, platforms, author and multiple keywords.
          import     Import a role into a galaxy server
          setup      Manage the integration between Galaxy and the given source.
          info       View more details about a specific role.
          install    Install role(s) from file(s), URL(s) or Ansible Galaxy
      

      In this section specifically, we have several examples that should be updated to use the following:

      ansible-galaxy role install

      ansible-galaxy role search

      ansible-galaxy role info

      ansible-galaxy role list

      ansible-galaxy role remove

      The same goes for the upcoming exercise as well.

      The previous section should use 'ansible-galaxy role init' in its examples for consistency.
      It might be worth doing a full search in the PDF for ansible-galaxy and make sure the same style is used when it deals with roles.

      Under the last heading titled Managing Downloaded Roles, we should mention that these examples require the roles_path to be modified to include the roles subdirectory in the project folder. Or just add -p roles to these examples.

              shasingh01 Shashi Singh
              zoltanmolnar Zoltan Molnar
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: