[Pulp-list] Uploading the same RPM to multiple pulp repos via the REST API

[Randy Barlow]

Mihai Ibanescu wrote:
> * if I find an orphan (a unit for which repository_memberships is
> empty), I can't figure out how I can copy that into a repo. The
> association code seems to expect a source repo. I suspect I need to
> re-upload in that case.

Would you be willing to file an RFE about this? That seems like a pretty
glaring shortcoming in the API to me. The more I think about it, the
less sense it makes to require a source repository when performing an
association. It makes far more sense for Pulp to offer an API where
units are associated with repositories by filters on the units themselves.

> * if I attempt to push a new unit into two repos, I can push it to the
> first one, but I could not figure out a way to retrieve the underlying
> unit from the original upload's task. There are some IDs that do not
> correlate to anything I can use. So I need to do an unnecessary lookup
> to find out what I've just pushed, which is a real shame. I guess I
> could do the copying by checksum again, to avoid an extra lookup.

Would you be willing to file another RFE about this use case as well?

I wonder if a better set of APIs would be:

0) upload lets you upload units, and it returns their unit ids in Pulp.
It does not associate with repositories.

1) associate allows you to associate units by ids with repositories.

The combination of the two I think would work well for your use case, as
well as all other use cases that I am familiar with.

Thanks for the e-mail!

-- 
Randy Barlow
irc:   bowlofeggs
phone: +1-919-890-8150

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20151112/e9ba0664/attachment.sig>