Issue #3445: Remove the ability for users to delete a single content unit. - Pulp

Send by e-mail

Issue #3445

Remove the ability for users to delete a single content unit.

Added by daviddavis almost 3 years ago. Updated about 1 year ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

dalley

Category:

Sprint/Milestone:

3.0.0

Start date:

Due date:

Estimated time:

Severity:

3. High

Version:

Platform Release:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Sprint:

Sprint 35

Quarter:

Description

When we sync for example we have the following workflow:

1. Download artifact(s) and save them
2. Create content unit
3. Add artifact(s) to my content unit
4. Add the content unit to my base_version

While each step is atomic, the entire workflow is not. Therefore, a user could delete a content unit anytime after step 2. This creates a problem for syncing and other tasks that use content units.

For the MVP, we should instead just remove this functionality and require users to use orphan cleanup instead:

https://pulp.plan.io/issues/3442

Related issues

Associated revisions

Revision 2e9f917f View on GitHub
Added by dalley almost 3 years ago

Remove ability to delete content units

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

Revision 2e9f917f View on GitHub
Added by dalley almost 3 years ago

Remove ability to delete content units

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

History

#1 Updated by daviddavis almost 3 years ago

Subject changed from I can delete content units that are being actively used by other things to I can delete content units that are being actively used by tasks
Tags Pulp 3, Pulp 3 MVP added

#2 Updated by daviddavis almost 3 years ago

Related to Story #3442: As a user, I can clean up both orphaned content units and orphaned artifacts added

#3 Updated by dalley almost 3 years ago

Severity changed from 2. Medium to 3. High
Triaged changed from No to Yes

#4 Updated by dalley almost 3 years ago

This essentially duplicates https://pulp.plan.io/issues/3380

Which should we leave open?

#5 Updated by amacdona@redhat.com almost 3 years ago

Status changed from NEW to ASSIGNED
Assignee set to dalley

dalley, since you are assigned to the other one, I assigned you this one as well so we don't forget about it. I don't think it really matters which stays open, but if there is useful information on one, please copy it to the other.

#7 Updated by daviddavis almost 3 years ago

Subject changed from I can delete content units that are being actively used by tasks to Remove the ability for users to delete a single content unit.
Description updated (diff)