Project

Profile

Help

Story #2757

As an API user, a call to delete a Repository generates a Task

Added by amacdona@redhat.com over 2 years ago. Updated 6 months ago.

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

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

After a discussion on the pulp-dev list [0], we decided that all updates and deletes for Publishers, Importers, and Repositories should be done asynchronously.

[0]: https://www.redhat.com/archives/pulp-dev/2017-May/msg00014.html


Checklist


Related issues

Copied from Pulp - Story #2756: As an API user, a call to update a Repository generates a Task MODIFIED Actions

History

#1 Updated by amacdona@redhat.com over 2 years ago

  • Copied from Story #2756: As an API user, a call to update a Repository generates a Task added

#2 Updated by bmbouter over 2 years ago

  • Sprint Candidate changed from No to Yes

We already have the Celery task pulp.app.tasks.repository.delete so all we need is for the Viewset to call apply_async_with_reservation for that task and return the 202 to the user.

#3 Updated by bmbouter over 2 years ago

  • Groomed changed from No to Yes

grooming per IRC convo w/ @asmacdo.

#5 Updated by bmbouter over 2 years ago

  • Status changed from NEW to CLOSED - WORKSFORME

This is already done so I'm marking as WORKSFORME.

#6 Updated by daviddavis 6 months ago

  • Sprint/Milestone set to 3.0

#7 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF