As a user, I can create a publication by specifying a repository
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.
#3 Updated by email@example.com about 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.
#5 Updated by daviddavis about 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.
Please register to edit this issue