Update Pulp's apply_async function signature to conform with Celery's
Currently pulp's apply_async function signature does not explicitly match Celery's 
This has caused some confusion over what to pass to Pulp's apply_async 
Refactoring our apply_async signature to take in the keyword arguments 'args' and 'kwargs' may be ugly, but it does explicitly state that these are the arguments that Celery passes to a task. It also allows us to distinguish between the arguments for celery, and the arguments for our task.
We should also document how to kick off Pulp3 apply_async and apply_async_with_reservations tasks in a blog post
#3 Updated by bizhang almost 4 years ago
Documentation for running apply_async and apply_async_with_reservation is now in the pulp wiki https://pulp.plan.io/projects/pulp/wiki/Pulp_3_Developer_Notes
Please register to edit this issue