Project

Profile

Help

Story #3035

As a REST API user, I can determine which publication is associated with a publish task

Added by dkliban@redhat.com about 2 years ago. Updated 6 months ago.

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

0%

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

History

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

  • Tracker changed from Issue to Story
  • % Done set to 0
  • Tags Pulp 3 added

#2 Updated by jortel@redhat.com about 2 years ago

Let's consider adding a natural key to the publication. A name for example that the user can optionally specify. I imagine the user would name the publication based on version of build#. This gives the user something meaningful to use when selecting a publication to be associated to a distribution or to be deleted.

We could default the Publication._name_ to the task ID when not specified by the user.

Should be unique by (publisher_id, name)

We'd need to update the /Publisher/publish endpoint and add an optional "publication_name" parameter which would need to be passed to Publisher.publish().

#3 Updated by dkliban@redhat.com almost 2 years ago

This problem could be avoided if we treated publications the same way we treat other resources in Pulp's REST API.

The user currently performs a

POST to http://localhost:8000/api/v3/repositories/foo/publishers/example/bar/publish/
to create a publication. The user receives a 202 response with a reference to a task.

If instead the user performed a

POST to http://localhost:8000/api/v3/repositories/foo/publishers/example/bar/publications/
to create a publication and received a 201 with the created publication that references a task, the user would know which publication to associate with a distribution. The user would also know which task to monitor.

#4 Updated by amacdona@redhat.com 11 months ago

  • Status changed from NEW to CLOSED - CURRENTRELEASE

The task returns created_resources, which includes any created publication.

#5 Updated by daviddavis 6 months ago

  • Sprint/Milestone set to 3.0

#6 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF