Project

Profile

Help

Story #3504

As a user, I can publish any repository version

Added by dalley over 1 year ago. Updated 6 months ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Platform Release:
Blocks Release:
Target Release - Python:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

The publish REST API needs to accept a repository or a repository_version parameter. When the repository_version is specified, the publisher should publish that repository version. When only the repository is specified, the latest repository version for that repository should be published.

The repository and repository_version cannot be used together. When submitted together, an exception should be raised. I think the most appropriate HTTP error response for this is a 400 Bad Request.


Checklist

Associated revisions

Revision e4ef2d97 View on GitHub
Added by dalley over 1 year ago

Support publishing any repository version, not just the latest one

  • Able to publish any version of the repo, not just the latest one
  • Refactoring and cleanup

closes #3504
https://pulp.plan.io/issues/3504

History

#1 Updated by dalley over 1 year ago

This basically clones https://pulp.plan.io/issues/3324 from pulp_file

PR here: https://github.com/pulp/pulp_file/pull/53

Most can be copied.

#2 Updated by daviddavis over 1 year ago

Adding checklist item to do a bit of refactoring to create a shared method which can get the repo version from the options.

#4 Updated by dalley over 1 year ago

  • Status changed from NEW to POST

#5 Updated by dalley over 1 year ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#6 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3, Pulp 3 MVP)

Please register to edit this issue

Also available in: Atom PDF