Project

Profile

Help

Story #3223

As a user, I can create a publication by specifying a repository

Added by dkliban@redhat.com almost 2 years ago. Updated 29 days ago.

Status:
CLOSED - WONTFIX
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:

Description

The publications REST API needs to be updated to accept an optional 'repository' parameter. When specified, the latest repository version for that repository is used to create the publication.

History

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

  • Parent task set to #3209

#2 Updated by daviddavis almost 2 years ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes

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

The publisher href included in the body of the post specifies the repository. Passing a repository parameter seems redundant and an odd way to specify the repository version. What is the expected behavior when the parameter is not passed? Can someone add some clarity.

#4 Updated by jortel@redhat.com almost 2 years ago

  • Groomed changed from Yes to No
  • Sprint Candidate changed from Yes to No

#5 Updated by daviddavis almost 2 years ago

@jortel, good question. I can see two possible reasons to implement this user story:

1. I just want to sync a repo and publish without having to look up the latest repo version. Without this story, I have to sync, look up the latest repo version, then publish. That requires an extra step.
2. Users might be concerned that by the time a publish happens, the version they are asking to be published is no longer the latest version. Depending on how we implement this user story, it could guarantee that it always publishes the latest repo version for a repo.

I don't find either case compelling though. I'm leaning toward removing this from the MVP and maybe only implementing this if users ask for it.

#6 Updated by amacdona@redhat.com almost 2 years ago

  • Status changed from NEW to CLOSED - WONTFIX

This issue will become part of each plugin story to implement this endpoint.

#7 Updated by amacdona@redhat.com over 1 year ago

  • Parent task deleted (#3209)

#8 Updated by dkliban@redhat.com over 1 year ago

  • Sprint/Milestone set to 3.0

#9 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3, Pulp 3 MVP)

#10 Updated by nobita66 29 days ago

Your article content is being very much interested, I am very impressed with your post. I hope to receive more great posts.
https://shell-shockers.online

Please register to edit this issue

Also available in: Atom PDF