Ansible Plugin

https://github.com/pulp/pulp_ansible/blob/master/pulp_ansible/app/serializers.py#L134-L148

Here's a sample requirements.yml that should work

collections:
  - name: amazon.aws
    source: https://galaxy.ansible.com
    version: 1.2.1
  - name: junipernetworks.junos
    source: https://galaxy.ansible.com
  - name: f5networks.f5_modules
    source: https://galaxy.ansible.com

Here's what I think needs to be done for this ticket:

From a high level we need to accept data just like the CLI does: https://docs.ansible.com/ansible/latest/user_guide/collections_using.html#configuring-the-ansible-galaxy-client

To do that effectively we need to accept remote.url and remote.requirements_file differently.

I think tests would make developing this easier, so I suggest make or update some tests:

1. One that uses the requirements file from comment #3 as the requirements file
2. One that uses a url like https://galaxy.ansible.com (the new style)
3. One that uses a url like we used to use https://galaxy.ansible.com/api/v2/collections/ and ensure it's rejected

In terms of migrations, maybe we need a migration? I don't think we should support the old-style data, but maybe refuse to sync with it if it's present and not ship a migration ... ?

I think the sync machinery is what needs to be updated. I think doing this only for CollectionRemote is ok, RoleRemote can continue to be whatever it is unless it's easier to also update that one.

We don't support requirements files for RoleRemote. That field is only on CollectionRemotes.

For the requirements file, we need to support two formats for collections: name.collection and a dict with name/version/source/etc

https://github.com/ansible/ansible/blob/c20329a0f635611eb5300d633300b621b5d1fbf8/lib/ansible/cli/galaxy.py#L539-L544

Noticed that the ansible-galaxy cli will try to append 'api' to the end of the URL as well:

https://github.com/ansible/ansible/blob/c20329a0f635611eb5300d633300b621b5d1fbf8/lib/ansible/galaxy/api.py#L51-L52