Issue #3445
closed
Remove the ability for users to delete a single content unit.
Status:
CLOSED - CURRENTRELEASE
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
- 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
- Related to Story #3442: As a user, I can clean up both orphaned content units and orphaned artifacts added
- Severity changed from 2. Medium to 3. High
- Triaged changed from No to Yes
- 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.
- 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)
- Description updated (diff)
- Sprint set to Sprint 35
- Status changed from ASSIGNED to POST
- Status changed from POST to MODIFIED
- Sprint/Milestone set to 3.0.0
- Related to Test #4216: test_crud_content_unit should test that content units cannot be deleted manually added
- Tags deleted (
Pulp 3, Pulp 3 MVP)
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
.
Remove ability to delete content units
closes #3445 https://pulp.plan.io/issues/3445