Simplify the plugin api for writing stages
With the invent of content with futures, that are able to feed back in earlier stages of the pipeline, the need came up for some sort of flow control in the batching of content process to prevent deadlocks .
To keep full authority over any future implementation of this flow control, i suggest to refactor the stages api with a simple but strict definition, what the implementation of a stage must do / can rely on.
- A stage must override
async def run(self):.
run, items can be retrieved through either
- ..., items must be forwarded by
Further discussion can be found here .
#2 Updated by bmbouter about 2 years ago
+1 also to the run approach.
It looks like that is the current code pushed to this PR https://github.com/pulp/pulpcore-plugin/pull/35/files is that right? Does that mean https://github.com/pulp/pulpcore-plugin/pull/35/files is ready for review?
Please register to edit this issue