•  
     
    story #12870 delete empty releases and packages
Summary
Empty
delete empty releases and packages

I can move away from SOAP

In SOAP api there was a possibility to delete empty packages and releases. We cannot replicate the exact same API with REST as the approach is not RESTful but we can provide the following en points

GET /projects/:id/frs_packages?query={"is_empty": true}

The result is paginated

GET /frs_packages/:id/frs_releases?query={"is_empty": true}

The result is paginated

DELETE /frs_releases/:id

It can only delete releases that doesn't have any files in it.

DELETE /frs_packages/:id

It can only delete packages that doesn't have any releases in it

Empty
Nouha Terzi (terzino), Denis PILAT (denis_pilat)
Status
Empty
Ready (stalled)
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#12870
Manuel Vacelet (vaceletm)
2021-01-20 11:35
2019-01-29 10:01
4060

References
Referencing story #12870

Follow-ups

User avatar

Yeah, somehow those two methods were forgotten, I agree it's a missing point that we should schedule in a not too far future.


  • Category set to
User avatar
Yes I knew that. So I guess there is no plan yet to have this REST method available on Tuleap, but it will probably come as soon as you have decided the date when SOAP is not supported anymore.

P.S. we have some people who starts to migrate to REST following some deprecation announce, that why I'm asking for this.
User avatar

My bad, I thought that the base DELETE method where implemented for both routes but it was not.

So this not possible to delete a package or a release right now.

User avatar
Hi Manuel

You mean it's possible to delete empty releases and packages with REST ? How ?
User avatar

No plan for theses extensions.

To be honest it doesn't really make any sense for an API to provide this and was a mistake in SOAP in first place.

This can already be done in 2 APIs call without having to maintain a dedicated end point for that.


  • So that
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes