Actions
Refactor #4346
closedSimplify the plugin api for writing stages
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Problem¶
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 [0].
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.
Solution¶
- A stage must override
async def run(self):
. - In
run
, items can be retrieved through eitherself.items
orself.batches
iterator. - ..., items must be forwarded by
self.put
.
Further discussion can be found here [1].
[0] https://pulp.plan.io/issues/4296
[1] https://github.com/pulp/pulpcore-plugin/pull/35
Actions
Adapt to Plugin API changes
re #4346 https://pulp.plan.io/issues/4346