Project

Profile

Help

Refactor #8827

closed

Remove ContentUnassociation stage

Added by dalley over 1 year ago. Updated over 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

ContentUnassociation doesn't really need to be a separate stage, and making it one breaks the expectations of the "pipeline" by changing the semantics of what goes into and out of the queues.

The ContentAssociation stage puts querysets into the queue (instead of declarative content) for the sake of the ContentUnassociation stage, and also these querysets represent content to remove rather than content to add.

Furthermore this isn't necessary. Rather than toggling whether the ContentUnassociation stage is run as a whole, we can just pass a boolean parameter into the ContentAssociation stage to toggle the behavior.


Related issues

Copied from Pulp - Refactor #8635: Deprecate ContentUnassociation stageCLOSED - CURRENTRELEASEdalley

Actions
Actions #1

Updated by dalley over 1 year ago

  • Copied from Refactor #8635: Deprecate ContentUnassociation stage added
Actions #2

Updated by pulpbot over 1 year ago

  • Status changed from NEW to POST

Added by dalley over 1 year ago

Revision 663d238c

Merge ContentUnassociation stage into the ContentAssociation stage

ContentUnassociation doesn't really need to be a separate stage, and making it one breaks the expectations of the "pipeline" by changing the semantics of what goes into and out of the queues.

closes: #8827 https://pulp.plan.io/issues/8827

Actions #3

Updated by dalley over 1 year ago

  • Status changed from POST to MODIFIED
Actions #4

Updated by pulpbot over 1 year ago

  • Sprint/Milestone set to 3.14.0
Actions #5

Updated by pulpbot over 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF