Details
-
Task
-
Resolution: Done
-
Major
-
master
-
None
Description
What is the problem?
At the moment tools-common is a single module with multiple packages providing a wide range of functionality - from an abstraction over different cloud provider's blob storage (objstore) to various datastructures (LRU, freelist etc).
This can cause problems for downstream because if they only want the functionality of a specific package they still have to pull in all of tools-common's dependencies (like the cloud SDKs which are not exactly lightweight)
What is the solution?
We should consider whether we can/should split tools-common into separate modules. This could be a 1:1 conversion off packages to modules or it could be more grouped (e.g. datastructures, objstore, couchbase cluster tools).
Attachments
| For Gerrit Dashboard: MB-55390 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 193588,7 | MB-55390 Reorganize 'tools-common' package structures | master | tools-common | Status: MERGED | +2 | +1 |
| 193723,6 | MB-55390 Create initial sub-modules | master | tools-common | Status: MERGED | +2 | +1 |
| 193798,5 | MB-55390 Update README for sub-modules | master | tools-common | Status: MERGED | +2 | +1 |
| 193804,2 | MB-55390 Pass the correct path to the 'reports' directory | master | tools-common | Status: MERGED | +2 | +1 |
| 193816,3 | MB-55390 Switch from using 'jq' to using 'gojq' in CV | master | tools-common | Status: MERGED | +2 | +1 |