Project

Profile

Help

Story #3324

Pulp - Story #3209: As a user, I have Repository Versions

As a user, I can publish any repository version

Added by dkliban@redhat.com over 2 years ago. Updated 11 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Sprint 33
Quarter:

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 ed8f77a8 View on GitHub
Added by dkliban@redhat.com over 2 years ago

Problem: only the latest repository version can be published

Solution: add ability to publish any repository version

This patch adds an optional repository_version parameter for the 'publish' endpoint of the 'file' publisher. The REST API accepts either 'repository' or 'repository_version', but not both at the same time.

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

History

#1 Updated by dkliban@redhat.com over 2 years ago

  • Tracker changed from Issue to Story
  • % Done set to 0

#2 Updated by bmbouter over 2 years ago

  • Description updated (diff)

#3 Updated by bmbouter over 2 years ago

  • Description updated (diff)

Adding info about raising an exception when both arguments are submitted together.

#4 Updated by bmbouter over 2 years ago

  • Sprint Candidate changed from No to Yes

added some checklist items.

#5 Updated by milan over 2 years ago

Sample JSON Blobs

Repository specified defaulting to latest version POST pulp.example.com/pulp/api/v3/pubisher/<publisher_uuid>/publish/:

{
    "repository": "https://pulp.example.com/pulp/api/v3/repository/<repository_uuid>/",
    "repository_version": null
}

Repository version specified implying the snapshot of a repository of the given version is published POST pulp.example.com/pulp/api/v3/publisher/<publisher_uuid>/publish/:

{
    "repository": null,
    "repository_version": "https://pulp.example.com/pulp/api/v3/repository/<repository_uuid>/version/<version_id>/"
}

#6 Updated by milan over 2 years ago

  • Groomed changed from No to Yes

#7 Updated by bmbouter over 2 years ago

  • Sprint/Milestone set to 54

milan, those look good.

I'm adding to the sprint because it's part of the versioned repos work and groomed.

#8 Updated by bmbouter over 2 years ago

  • Sprint/Milestone changed from 54 to 53

Added to the wrong sprint.

#9 Updated by dkliban@redhat.com over 2 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to dkliban@redhat.com

#10 Updated by jortel@redhat.com over 2 years ago

  • Sprint/Milestone changed from 53 to 54

#11 Updated by rchan over 2 years ago

  • Sprint/Milestone changed from 54 to 56

#12 Updated by daviddavis over 2 years ago

Added checklist item to open a pulp-smash Github issue.

#13 Updated by dkliban@redhat.com over 2 years ago

  • Status changed from ASSIGNED to POST

#15 Updated by dkliban@redhat.com over 2 years ago

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

#16 Updated by bmbouter over 2 years ago

  • Sprint set to Sprint 33

#17 Updated by bmbouter over 2 years ago

  • Sprint/Milestone deleted (56)

#18 Updated by bmbouter over 1 year ago

  • Tags deleted (Pulp 3, Pulp 3 MVP)

#19 Updated by bmbouter 11 months ago

  • Sprint/Milestone set to 0.1.0

#20 Updated by bmbouter 11 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF