Project

Profile

Help

Story #2475

As a user, I can use REST API to remove a repository.

Added by ipanova@redhat.com over 3 years ago. Updated 7 months ago.

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

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Sprint 12

Description

As a result of this story the user will be able to make a DELETE request to /api/v3/repositories/<pk> and receive back a 202 response that looks like this:


[
    {
        "_href": "/api/v3/tasks/adlfk-bala-23k5l7-lslser",
        "task_id": "adlfk-bala-23k5l7-lslser" 
    }
]

The repository viewset should be extended to handle a DELETE. As a result of the request a pulp.app.tasks.repository.delete.apply_async_with_reservation() should be called and the AsyncResult should be used to instantiate an OperationPostponedResponse0 object. The object should then be returned.

Just to clarify, our ViewSets already support the DELETE verb, so this would specifically entail implementing the existing ViewSet "destroy" method, having it return the response as explained in the description.

http://www.django-rest-framework.org/api-guide/viewsets/#marking-extra-actions-for-routing
[0] http://docs.pulpproject.org/en/3.0/nightly/contributing/platform_api/app/response.html#pulp.app.response.OperationPostponedResponse

Associated revisions

Revision 63b6686b View on GitHub
Added by ipanova@redhat.com over 3 years ago

As a user, I can use REST API to remove a repository.

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

Revision 63b6686b View on GitHub
Added by ipanova@redhat.com over 3 years ago

As a user, I can use REST API to remove a repository.

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

History

#1 Updated by ipanova@redhat.com over 3 years ago

  • Tags Pulp 3 added

#2 Updated by ipanova@redhat.com over 3 years ago

  • Sprint Candidate changed from No to Yes

#3 Updated by dkliban@redhat.com over 3 years ago

  • Groomed changed from No to Yes

#4 Updated by dkliban@redhat.com over 3 years ago

  • Sprint/Milestone set to 30

#5 Updated by ipanova@redhat.com over 3 years ago

  • Status changed from NEW to POST
  • Assignee set to ipanova@redhat.com

#6 Updated by ipanova@redhat.com over 3 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#7 Updated by bmbouter over 2 years ago

  • Sprint set to Sprint 12

#8 Updated by bmbouter over 2 years ago

  • Sprint/Milestone deleted (30)

#9 Updated by daviddavis about 1 year ago

  • Sprint/Milestone set to 3.0.0

#10 Updated by bmbouter about 1 year ago

  • Tags deleted (Pulp 3)

#11 Updated by bmbouter 7 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF