Getting started with automation hub

Procedure

1. Navigate to Ansible Automation Platform on the Red Hat Hybrid Cloud Console.
2. From the navigation panel, select Automation Hub → Connect to Hub.
3. Under Offline token, click Load Token.
4. Click the Copy to clipboard icon to copy the API token.
5. Paste the API token into a file and store in a secure location.

Procedure

1. Log in to your private automation hub.
2. From the navigation panel, select Collections → API token.
3. Click Load Token.
4. To copy the API token, click the Copy to clipboard icon.
5. Paste the API token into a file and store in a secure location.

Procedure

1. Open the ansible.cfg file.
2. Add the server_list option under the [galaxy] section and include one or more server names.

3. Create a new section for each server name:

   [galaxy_server._<server_name>_]

4. Set the url option for each server name:

   https://<server_fully_qualified_domain_name>/api/galaxy/

5. Optional: Set the auth_url option. The community Ansible Galaxy does not require an auth_url.
6. Set the API token for the automation hub server.

Procedure

1. Navigate to your automation controller.

2. Create a new credential.

   1. Navigate to Resources → Credentials.
   2. Click Add.
   3. Enter the name for your new credential in the Name field.
   4. Optional: Enter a description and enter or select the name of the organization with which the credential is associated.
   5. Under Organization, select the organization that you want to use the credential for.
   6. Select Ansible Galaxy/Automation Hub API Token as the credential type.
   7. Under Type Details, enter the Galaxy Server URL, Authentication Server URL, and API Token previously created.
   8. Click Save.

3. Select the credential that you created from the Organization’s Galaxy Credentials field.

   1. Navigate to Access → Organizations.
   2. Select the organization where want to add your Galaxy credentials.
   3. Click Edit.
   4. Under Galaxy Credentials, click the Search icon.
   5. Select the credential that you created for automation hub, and place it at the beginning of the list.
   6. Optional: If you have a secondary source of content, such as Ansible Galaxy, place this credential after the credential that you created for automation hub.
   7. Click Select.
   8. Click Save.

1. Navigate to your project repository.
2. Select a project that uses a collections/requirements.yml file.
3. Update the project by clicking the Sync Project icon.

Procedure

1. Navigate to the installer.

   Bundled installer

   $ cd ansible-automation-platform-setup-bundle-<latest-version>

   Online installer

   $ cd ansible-automation-platform-setup-<latest-version>

2. Open the inventory file with a text editor.

3. Add the automationhub_enable_unauthenticated_collection_access and automationhub_enable_unauthenticated_collection_download parameters to the inventory file and set both to True, following the example below:

   [all:vars]
   
   automationhub_enable_unauthenticated_collection_access = True 1
   automationhub_enable_unauthenticated_collection_download = True 2

   1

   Allows unauthorized users to view collections

   2

   Allows unathorized users to download collections

4. Run the setup.sh script. The installer enables view-only access to your private automation hub.

1. Navigate to your private automation hub.
2. On the login screen, click View only mode.

1. From the navigation panel, select Collections → Namespaces.
2. On the My namespaces tab, locate the namespace to which you want to upload a collection.
3. Click View collections and click Upload collection.
4. In the New collection modal, click Select file. Locate the file on your system.
5. Click Upload.

Procedure

1. Log in to your private automation hub.
2. From the navigation panel, select Collections → Collections.

3. Before deleting the collection, check to see if it has collections that are dependent on it:

   • Click the Dependencies tab for that collection. If it is blank, you will be able to delete the collection. If the Dependencies tab is not blank, you must delete these dependencies before you can delete the collection.
4. Click the collection to delete.

5. Click the More Actions icon ⋮, and then select an option:

   1. Delete entire collection to delete all versions in this collection.

   2. Delete version [number] to delete the current version of this collection. You can change versions by using the Version drop-down menu.

      Note

      If the selected collection has any dependencies with other collections, these actions are disabled until you delete those dependencies. Click the Dependencies tab to see a list of dependencies to delete.

6. When the confirmation window opens, verify that the collection or version number is correct, and then select Delete.