Uploaded image for project: 'Automation Hub'
  1. Automation Hub
  2. AAH-2169

Collection approval workflow UI

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • crc-2023-06-27
    • None
    • UI
    • None

      Design document: https://docs.google.com/document/d/1xmRAm7QIc_If8TGPmEXKK6-5Wc2v1cfCHDnPt310XzA/edit#

      On the collection approval page:

      When the user clicks "Approve" query the ansible repository API for a list of all repositories with the "pipeline=approved" label (/api/galaxy/pulp/api/v3/repositories/ansible/ansible/?pulp_label_select=pipeline=approved).

      • If only one repository exists, the UI should do what it does now. Move the collection into the published repository
      • If more than one repository exists, the UI should prompt the user which repositories the want to move the collection into. From here the user can select as many repositories as they want. The easiest way to do this right now is move the collection into the first repository selected (using the existing move endpoint) and then call copy on all the subsequent repositories that the user selects. (This api functions the same as the current move api)

              mipospis@redhat.com Milan Pospisil
              dnewswan David Newswanger
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: