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.
- relates to
-
AAH-1776 Collection Repository Management - P1 use cases [blocker]
-
- Closed
-
- mentioned on