-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 FYI, I've put in a proposal to redo the upload API in a way that would allow an upload once, associate many use case.
The main design story: https://pulp.plan.io/issues/892 Two related stories: https://pulp.plan.io/issues/894 https://pulp.plan.io/issues/923 Consider adding comments or +1's to those. Improvements are welcome! - -Brian On 11/12/2015 09:09 AM, Randy Barlow wrote: > 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! > > > > _______________________________________________ Pulp-list mailing > list [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWRMQiAAoJEK48cdELyEfyoi8IAI5cQrGvM71KfgN52rrDhcKm ktIn0vt7kPJ6kpi5P6zVnMUvlKTqs0tG+zrKwl17AB7iioamjog7JDMT2afpMbSo AGhHzGYAx/jz/bzOpFg0d1li0iXpUlwXIXde8QzICE2XhEEa73M6m4Bv4665wsZm RTqz9ecbbtq0WHxz7fkzDpYoUVBHa4620aTuIMJ028p1Bp8DtcvgjXVO02Wu/tYq wurpRi//vh45LHKXGI03vNykH5xXMkc1dwnEIhVkBAGm4VVn1i9cJX0uR9uZw6Cd hJyRQ7cQAuD1oWofbuEiZRWYluE22gT1zPu9op5UFi4d4wK9XnJN4DMjdp5JS3I= =I0qY -----END PGP SIGNATURE----- _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
