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

we would like an unauthenticated EE download (no podman login) from AH,

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • None
    • 2.2
    • hub
    • False
    • Hide

      None

      Show
      None
    • False
    • Team Discussion

      Feature Overview

      Allow for unauthenticated EE container image download

      Background, and strategic fit

      Allow for unauthenticated EE container image download from private automation hub. At the moment, there seems to be only 2 flags for unauthenticated collection download (GALAXY_ENABLE_UNAUTHENTICATED_COLLECTION_ACCESS and _DOWNLOAD), but nothing similar for EE ISSUE: Trying to pull an EE image from PAH results in $ podman pull <PAH>/bsc/ee-shared-docker:latest Trying to pull <PAH>/bsc/ee-shared-docker:latest... Error: initializing source docker://<PAH>/bsc/ee-shared-docker:latest: reading manifest latest in <PAH>/bsc/ee-shared-docker: errors: denied: requested access to the resource is denied unauthorized: Insufficient permissions

      (Optional) Use Cases

      using execution environments, we would like the same principle for ee container access so that we do not need to share tokens from 2 different PAH instances (we have setup AAP similar to the redhat reference architecture
      https://access.redhat.com/documentation/en-us/reference_architectures/2021/html-single/deploying_ansible_automation_platform_2.1/index
      , thus we have 2 AH instances)

      Assumptions

      we could specify "public" per container repository, but I do guess that a similar handling as is done with unauthenticated collection access would suffice.

      Out of Scope

       

       

              rhn-support-ebock Emily Bock
              rhn-support-gotiwari Goutam Tiwari
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: