Project

Profile

Help

Issue #7551

closed

Standalone galaxy_ng syncing from cloud.ci doesn't get docs for collections (https://github.com/ansible/galaxy_ng/issues/441)

Added by alikins over 3 years ago. Updated over 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

https://github.com/ansible/galaxy_ng/issues/441 is the origin of this.

It seems like if a standalone galaxy_ng syncs from cloud.ci.redhat.com, the doc blobs for the collections isn't synced.

https://ci.cloud.redhat.com/api/automation-hub/content/synctest/v3/collections is an example repo set up with some collections with docs blobs.

At the moment, it's unclear if this is an issue with standalone galaxy_ng, or with the ci.cloud galaxy_ng / pulp_ansible / pulp_core issue. But this is a heads up.

For an example of a collection in that repo:

https://ci.cloud.redhat.com/api/automation-hub/content/synctest/v3/collections/ibm/spectrum_virtualize/

And the docs-blob for a particular version: https://ci.cloud.redhat.com/api/automation-hub/content/synctest/v3/collections/ibm/spectrum_virtualize/versions/1.0.12-awc16/docs-blob/

The latter shows info available in the docs-blob, but it apperently doesn't sync synced to the standalone galaxy_ng

Versions:

On the standalone side:

galaxy-ng (4.2.0b2) pulp-ansible (0.3.0) pulpcore (3.6.0

Also available in: Atom PDF