[Pulp-list] repo sync and the pulp-admin client
Jason L Connor
jconnor at redhat.com
Fri Sep 17 15:19:54 UTC 2010
On Fri, 2010-09-17 at 11:11 -0400, Todd B. Sanders wrote:
> Assume we will only allow one sync per repo at a time; so what
> happens
> if I initiate a POST on /pulp/api/repositories/<id>/sync/ for the
> same
> repo before the ongoing sync has finished?
The web services will return a 409 conflict message. I believe the
client already handles this (though I will double check).
>
> I do like the idea of an immediate return (default behavior) and a
> syncstatus for progress info. Assume you can also cancel ongoing
> sync?
Yep, cancel is already implemented (Thank you Sayli). The for waiting
for the sync, perhaps the flag should be: --foreground
--
Jason L Connor
Software Engineer
Systems Management and Cloud Enablement
Red Hat, Inc.
+1.919.890.8331
RHCT #605010081634021
Freenode: linear
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20100917/29c696d5/attachment.sig>
More information about the Pulp-list
mailing list