Repository navigation
Feature Request: Add delete command to CLI to remove APIs from Microcks #294
Description
Description :
Currently, the Microcks CLI allows users to import and test APIs, but there is no native way to delete an API directly from the command line. This makes it difficult to maintain clean environments, especially in CI/CD pipelines where we often want to clean up older, unused iterations of an API or tear down temporary mock services.
Describe the solution you'd like
I would like to see a new microcks delete command added to the CLI.
The command should:
- Take the API name and version as a single argument (e.g.,
<serviceName:version>). - Look up the internal service ID using the Microcks REST API.
- Safely delete the target service.
- Return a clear success or failure message.
Proposed Usage:
microcks delete "MyService:1.0"
Describe alternatives you've considered
The only current alternative is to manually write curl scripts to first query the /api/services/search endpoint to find the system id and then issue a DELETE request, or to manage deletions manually through the Web UI. Having this integrated into the CLI is much cleaner.
Activity
yada commentedon Oct 28, 2026
Status check: PR #295 (
microcks delete) is still open and was last updated on May 16. It is awaiting review and has not been rebased recently, so I cannot tell yet if it is mergeable. @DivyanshuVortex, are you still on it? Please rebase on master and confirm thatgo vetandgo test ./...pass. Maintainers: it needs a review decision, notably on the safety of deleting byname:version(confirmation prompt or--forcefor CI use).Disclosure: this comment was drafted with AI assistance, and I checked the claims against current master.
aniket866 commentedon Oct 28, 2026
I would like to work, upon that PR
DivyanshuVortex commentedon Oct 29, 2026
Hello @yada , i like to work on it but im quite busy currently due to college stuff.... and @aniket866 want to works on it....therefore please assign this task to him.... thnx
yada commentedon Oct 29, 2026
Thanks for the info, @DivyanshuVortex: @aniket866 : looking forward to your PR; we do not need to assign for this purpose.