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

Make requirements.yaml required for galaxy.ansible.com

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • 2.4
    • 2.4
    • Backend
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Release Note Not Required
    • Approved

      Description

      The v3 remote api requires a requirements.yaml file to create remotes to connect to galaxy.ansible.com in order to prevent customers from syncing everything in galaxy and DoSing the service. With repo management we're using the pulp apis, which don't have this check in place.

      We can use the access policy to add an extra validation step onto the sync actions for remotes that prevents users from syncing from galaxy.ansible.com without a requirements.yaml file.

            dnewswan David Newswanger
            dnewswan David Newswanger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: