Story #3219: As an authenticated user, I can delete any repository version. - Pulp

Send by e-mail

Story #3219

Story #3209: As a user, I have Repository Versions

As an authenticated user, I can delete any repository version.

Added by dkliban@redhat.com about 2 years ago. Updated about 2 months ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

daviddavis

Category:

Sprint/Milestone:

3.0.0

Start date:

Due date:

% Done:

100%

Platform Release:

Blocks Release:

Backwards Incompatible:

Groomed:

Yes

Sprint Candidate:

Yes

Tags:

QA Contact:

Complexity:

Smash Test:

871

Verified:

Verification Required:

Sprint:

Sprint 31

Description

The task for deleting repository versions needs to handle delete operations for the first version, last version, and any in between. This task should lock on the repository version and the associated repository..

Associated revisions

Revision 18acddab View on GitHub
Added by daviddavis about 2 years ago

Update repo last_version after a new version is created during sync

ref #3219
https://pulp.plan.io/issues/3219

Revision 0b5e7477 View on GitHub
Added by daviddavis about 2 years ago

Allow users to delete the latest repo version

fixes #3219
https://pulp.plan.io/issues/3219

Revision 0b5e7477 View on GitHub
Added by daviddavis about 2 years ago

Allow users to delete the latest repo version

fixes #3219
https://pulp.plan.io/issues/3219

History

#1 Updated by dkliban@redhat.com about 2 years ago

Parent task set to #3209

#2 Updated by daviddavis about 2 years ago

Tracker changed from Task to Story
Subject changed from Add support for deleting RepositoryVersions to As an authenticated user, I can delete any repository version.

#3 Updated by daviddavis about 2 years ago

I think this task may need to lock on the next repo version too. The squash code moves the content associations from the deleted repo version to the next repo version so it should be locked so that a user can't delete it, etc.