As a user, I can publish a Python repository in a way that can be consumed by Pulp
This story is to implement PyPI's json API. This story is successful when a second Pulp can sync from a repository published by this Pulp.
Since we want to use the resulting api for both upload from twine, and syncing from Pulp we should provide a 'live' endpoint for the packages without using Pulp's publication/distribution mechanism, since those objects are only used for a 'flat' publish.
We would need a new view that would dynamically generate the json and the url for each PythonPackageContent, the 'url' in the json would link to the location of the package in the Content View.
This new view would provide an endpoint like
for each package in a repository. This new view would not have to support upload requests from twine, as that will be done in #2887
#3 Updated by email@example.com over 2 years ago
This is only necessary for Pulp syncing from Pulp, so if only considering this plugin, this could be a pretty low priority. It is in the MVP, but could be done near the release.
This story could go into some exciting new territory, to create a custom API endpoint that implements PyPI's json API. Since the json API is simpler than puppet or crane, this story might be worth doing soon as a prototype for other plugins.
Please register to edit this issue