Actions
Issue #7412
closedCollection Remote sync breaks when requirements.yml is added.
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Sync breaks when requirements.yml is added. This appears to be happening because pulp_ansible tries to append api/v2/collections/<namespace>/<name>
on to the end of the URL, which throws a 404.
- On API version 2 (galaxy), the sync process tries to look up
https://galaxy.ansible.com/api/v2/collections/api/v2/collections/newswangerd/collection_demo
- On API verson 3 (hub) the sync process looks up
https://cloud.redhat.com/api/automation-hub/v3/collections/api/v2/collections/frr/frr
I haven't tested sync on galaxy.ansible.com without a requirements.yml because I don't want to sync all 500 collections on there.
I had to put in https://cloud.redhat.com/api/automation-hub/v3/collections
as the base URL for hub because just pointing to the api root didn't seem to work, so I assume appending v2/collections...
is not the correct behaviour.
Here is my config:
galaxy
{
"name": "galaxy",
"url": "https://galaxy.ansible.com/api/v2/collections",
"requirements_file": "---\ncollections:\n - newswangerd.collection_demo"
}
hub
{
"name": "test remote",
"url": "https://cloud.redhat.com/api/automation-hub/v3/collections",
"requirements_file": "---\ncollections:\n - frr.frr",
"auth_url": "https://sso.redhat.com/auth/realms/redhat-external/protocol/openid-connect/token",
"token": "REDACTED"
}
Related issues
Actions
Build collections URL according to requirements.yml
https://pulp.plan.io/issues/7412 closes #7412