Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #7512

closed

Seeing some collections skipped with CollectionRemote with requirements.yml (related to https://github.com/ansible/galaxy_ng/issues/437)

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

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

Description

This is kind of asking for a consult on https://github.com/ansible/galaxy_ng/issues/437

When testing standalone automation-hub that is setup for a remote that points to "community" (https://galaxy.ansible.com) when trying to sync with a remote that has a "requirements_file" specified, sometimes some collections are synced but others are ignored, seemingly with no errors.

The comments at https://github.com/ansible/galaxy_ng/issues/437 have more examples.

The current hypothesis is that it may just be malformed requirements.yml causing parts to be ignored.

But I'm looking for any other ideas that may need to be investigated.

Actions
Send by e-mail Copy link

Also available in: Atom PDF