Uploaded image for project: 'Ansible Automation Platform RFEs'
  1. Ansible Automation Platform RFEs
  2. AAPRFE-2372

[RFE] Display Execution Environment Container Tag and Hash in Automation Hub UI.

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Duplicate
    • Icon: Normal Normal
    • None
    • 2.5
    • hub
    • False
    • Hide

      None

      Show
      None
    • False

      1. What is the nature and description of the request?

      When a user builds a new Execution Environment (EE) using ansible-builder, they typically push it to their Automation Hub using podman login followed by podman push. However, in the Automation Hub GUI, it is difficult to verify whether the upload was successful. While a "last updated" date is displayed, it is small and easy to overlook. It would be beneficial if the container hash and tag were also visible—if not in the list of EEs, then at least within the detailed view of a specific EE. This would greatly improve usability and provide clearer confirmation that the upload was successful.

      2. Why does the customer need this? (List the business requirements here)

      If a user attempts to upload a new Execution Environment (EE) and a job fails due to the wrong EE being used, having a clear way to identify which container was actually used would significantly help speed up the debugging process.

      3. How would you like to achieve this? (List the functional requirements here)

      If the page displaying an Execution Environment (EE) included identifiers such as the container hash and tag, it would be easier for users to verify that a correct push had occurred. Alternatively, this information could be shown when clicking through to a specific EE container. Currently, only the container name is visible, which makes it difficult to confirm the exact version that was uploaded.

              Unassigned Unassigned
              rhn-support-snarveka Swati Narvekar
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: