Just to provide an added data point, I'll be merging the one-shot PR for pulp_python soon and it currently uses /api/v3/python/upload/
I wanted to keep it simple as well, and so would be happy to change it for consistency based on whatever we decide. --Dana Dana Walker She / Her / Hers Software Engineer, Pulp Project Red Hat <https://www.redhat.com> dawal...@redhat.com <https://www.redhat.com> On Mon, Jul 29, 2019 at 10:42 AM Ina Panova <ipan...@redhat.com> wrote: > Hi all, > As of today, plugins have the freedom to define whichever endpoints they > want ( to some extent). > This leads to the question - shall we namespace one-shot upload and copy > endpoints for some consistency? > > POST /api/v3/content/rpm/packages/upload/ > POST /api/v3/content/rpm/packages/copy/ > > or > > POST /api/v3/content/rpm/upload/ type =package > POST /api/v3/content/rpm/copy/ type = [package, modulemd] > > I wanted to bring this up, before it diverges a lot. For the record, I > have checked only RPM plugin, I am not aware of the state of the other > plugins. > Right now we have an active endpoint for one-shot upload of rpm package: > POST /api/v3/content/rpm/upload/ > > And there is PR for one-shot upload of modulemd-defaults: > POST /api/v3/content/rpm/modulemd-defaults/ > > For rpm copy we have POST /api/v3/content/rpm/copy/ types=[] > > We are starting some work on docker recursive copy, so it would be helpful > to reach some agreement before going further that path. > > Thank you! > -------- > Regards, > > Ina Panova > Senior Software Engineer| Pulp| Red Hat Inc. > > "Do not go where the path may lead, > go instead where there is no path and leave a trail." > _______________________________________________ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
