Conan Remove API Endpoints
Implement the API endpoint (details below) needed in order to successfully run conan search
and view available packages from the GitLab Conan registry.
This is the 5th of 6 steps to implementing the Conan API https://gitlab.com/gitlab-org/gitlab-ee/issues/8248:
- #12567 (closed) - Skeleton API - Ping endpoint
- #12568 (closed) - Conan authentication endpoints
-
#13345 (closed) -
conan upload
endpoints -
#13350 (closed)
conan install
endpoints -
#13347 (closed)
conan search
endpoints -
conan info
endpoints (all endpoints forconan info
are implemented in previous steps) -
#31941 (closed)
conan remove
endpoints
Endpoints to implement in this issue:
-
DELETE /v1/conans/{recipe}
- Remove existing recipes or packages
Endpoints that may be related, but not necessary for MVC
-
POST /v1/conans/{recipe}/packages/delete
- Remove specified packages -
POST /v1/conans/{recipe}/remove_files
- Remove specified files There is a comment in the code here:The remove files is a part of the upload process, where the revision in v1 will always be 0
, possibly is necessary forconan upload
conan remove
makes a series of API calls to the registry (aka remote)
Related: #8248 (closed)
Edited by Steve Abrams