feat: Improve Performance of delete Command with Concurrency #322
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #79
Also trying to fix #316
Inspired from #80
Handles concurrent deletion of projects, registries and repositories
Description
This PR enhances the performance of the harbor project delete command by introducing concurrency to handle multiple project deletions in parallel. The changes ensure that the command is more efficient, especially when dealing with multiple projects.
Changes
Changes made in
RepoDeleteCmd()
,DeleteRegistryCommand()
andDeleteProjectCommand()
to handle batch operation by using go routines.Benefits
Performance: Can concurently handle delete operations, thus improving execution time when dealing with multiple projects.
Readibility: Logging of any errors and overall status delivers a clear insight into errors and issues.
Usage
Looking forward for integration into the main branch. Waiting for your comments maintainers and contributors.