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

Collection Signing: Creating & Exposing Signatures (summit, PAH + CRC)

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • Collection Signing: Creating & Exposing Signatures
    • False
    • False
    • Done
    • ANSTRAT-411 - Content Signing
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined
    • 4.5.0a Sprint 2

      Creating:

      Hub UI will allow users to select a specific set of collection versions to 

      perform on-demand signing.

       

      Hub will be able to sign content automatically during the approval process.

      Depends on: Pulp-Ansible to expose an API/Task to sign a content using the specified Signing Service.

       

      Exposing:

      Hub UI 

          visual indication to identify the signed content.

          filtering collections based on signatures.

          download the signatures along with collections.

      Depends on: Pulp Signing API & Hub API endpoints


       

      Hub API will expose signature metadata 

      along with collections.

      When syncing collections from a remote Hub, signatures will also be synced.

      *Hub will not perform any signature verification, this task is deferred to the ansible-galaxy CLI.

      Depends on: 

      Pulp Ansible to provide the Signature storage and its APIs.
      Pulp Ansible to sync signatures along with collections.

       

       

       

              rochacbruno@redhat.com Bruno Rocha
              awcrosby5 Andrew Crosby (Inactive)
              Archiver:
              ranumula@redhat.com Raju Anumula
              Clara Spealman Clara Spealman (Inactive)

                Created:
                Updated:
                Resolved:
                Archived: