As a plugin writer, I can inject stages into DeclarativeVersion
If a plugin needs to inject a custom stage, e.g. RPMs RelatedErrataModelSaver, it must carry lots of code that is already contained in DeclarativeVersion. This is doubly unfortunate because as DeclarativeVersion gets more feature over time, these other forked pipelines have to continue to duplicate those changes also.
Create a method in DeclarativeVersion call pipeline_stages that provides the artifact and content portions of the pipeline (leaving out the associate/unassociate stages).
Quoting from @gmbnomis' comment plugin writers have lots of options then:
- Scrap the whole thing if it does not fit
- Overwrite pipeline_stages() to instantiate stock or customized stages in any order
- Do "surgery" on the stages list by calling super().pipeline_stages() and modifying the result (the idea of this PR).
- Use it as is
#8 Updated by bmbouter about 1 year ago
- Sprint deleted (
Taking off the sprint since it's waiting on work that was discussed in this PR: https://github.com/pulp/pulp/pull/3605#issuecomment-421358274
Please register to edit this issue