Project

Profile

Help

Issue #9030

closed

As a user I want consistent naming between the remote options retained_versions and retain_package_versions

Added by quba42 over 2 years ago. Updated over 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
1. Low
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 101
Quarter:

Description

See this community discussion: https://github.com/pulp/community/discussions/36

Note that while retain_package_versions currently comes from RPM only, retained_versions comes from pulpcore.

The state of the discussion is that renaming retained_versions to retain_repo_versions would be the most meaningful and consistent. Of course this does mean renaming a API option which can break existing scripts? I don't know to what extent it is possible/desirable to retain aliases for backwards compatibility in such cases.


Related issues

Related to RPM Support - Story #9031: As a user, retain_package_versions remote option uses 0 vs. Null in an intuitive way, consistent with other Pulp configuration optionsCLOSED - DUPLICATE

Actions

Also available in: Atom PDF