Actions
Issue #9030
closedAs a user I want consistent naming between the remote options retained_versions and retain_package_versions
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
Updated by quba42 over 3 years ago
- Related to Story #9031: As a user, retain_package_versions remote option uses 0 vs. Null in an intuitive way, consistent with other Pulp configuration options added
Updated by pulpbot over 3 years ago
- Status changed from NEW to POST
Updated by dkliban@redhat.com over 3 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 100
Added by daviddavis over 3 years ago
Updated by daviddavis over 3 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulpcore|77efe581eb1032c0aad175f90c8bc66be60738ce.
Updated by pulpbot about 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Rename retained_versions field for consistency
fixes #9030