Project

Profile

Help

Issue #7392

closed

Create from Bandersnatch Remotes are filling in fields incorrectly

Added by gerrod over 3 years ago. Updated about 3 years ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Python:
Platform Release:
3.0.0
Target Release - Python:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

The prereleases field for a Python remote is the opposite of the prereleases field specified in the Bandersnatch config file. Setting prereleases True for Python remotes includes prereleases while setting the field in the Bandersnatch config filters out prereleases. This logic should be switch to better match Bandersnatch's behaviour.

Also, Bandersnatch has now changed the names of their includes/excludes filters from 'whitelist/blacklist' to 'allowlist/blocklist'. This should be updated in the create_frombandersnatch viewset.

Added by gerrod over 3 years ago

Revision fe7e7802 | View on GitHub

Fields in remote from Bandersnatch config are correctly set

fixes: #7392 https://pulp.plan.io/issues/7392

Actions #1

Updated by gerrod over 3 years ago

  • Status changed from NEW to MODIFIED
Actions #2

Updated by dalley about 3 years ago

  • Platform Release set to 3.0.0

Also available in: Atom PDF