Project

Profile

Help

Issue #7739

closed

Requirement.yml code doesn't filter by version

Added by daviddavis 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

If you use this requirements.yml file[0], you will end up with 3 collection versions. However, you should only have 1 as the two releases for testing.ansible_testing_content are 4.0.4 and 4.0.6[1] which don't match ">=1.0.0,<=2.0.0", and there's only one release of testing.k8s_demo_collection[2].

To reproduce this in a test environment, change this line[3] to use assertEqual since ANSIBLE_COLLECTION_FIXTURE_COUNT is 1.

[0] https://github.com/pulp/pulp_ansible/blob/739a5551c87f4fffa9f46bee7fce9975e39020e8/pulp_ansible/tests/functional/constants.py#L83-L88

[1] https://galaxy-dev.ansible.com/api/v2/collections/testing/ansible_testing_content/versions/

[2] https://galaxy.ansible.com/api/v2/collections/testing/k8s_demo_collection/versions/

[3] https://github.com/pulp/pulp_ansible/blob/739a5551c87f4fffa9f46bee7fce9975e39020e8/pulp_ansible/tests/functional/api/collection/v2/test_sync.py#L204


Related issues

Related to Ansible Plugin - Refactor #7777: As a developer I want collections sync machinery easier to maintainCLOSED - CURRENTRELEASEbmbouter

Actions
Has duplicate Ansible Plugin - Issue #5309: Download only specified version on requirements.ymlCLOSED - DUPLICATEActions

Also available in: Atom PDF