Ah great, thanks for that Jeff. Jon
On 5 December 2014 at 22:36, Jeff Ortel <[email protected]> wrote: > Hey Jon, > > The REST API [1] for binding a consumer to a repository returns a task > that can be used to track the implementation of the bind request by the > agent on the consumer. When that task has completed, the bind work on the > consumer has been completed. The state of that task is a direct reflection > of the state of that bind request to the agent. > > Hope this helps. > > -jeff > > [1] http://pulp-dev-guide.readthedocs.org/en/latest/ > integration/rest-api/consumer/bind.html > > > On 12/05/2014 08:16 AM, Jon Shanks wrote: > >> Hi, >> >> I was wondering if there is some way to determine whether or not the >> task is completed from a consumer end when it binds to a repo. In terms >> of automation, when i bind a consumer, in this case via puppet, i have >> had to put a sleep in as there is no real way for me to determine when >> the task is completed from the server side, to then know to proceed with >> other elements of the configuration. >> >> Without any real feature in there for awareness of task completion or >> with it still running asynchronously it's hard to coordinate tasks >> around the succession of repository creation on a node. >> >> If possible, i'd like to raise a feature if this doesn't exist, but not >> sure where bugs / features get raised? >> >> Thanks >> >> Jon >> >> >> _______________________________________________ >> Pulp-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/pulp-list >> >> > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list >
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
