`artifact-manager` needs to be better structured
Description
The structure of artifact-manager needs to be refactored to be better structured. Currently there is almost no structure and classes are added to random places.
Examples
store folder has filters, I'd assume that different stores should be put here
Store classes not under store folder
Special structure for vRLI under rest/client, but no other clients present
Misplaced models
Proposal
- Ignore the fact that it says
artifact-newthis is just a placeholder, the sameartifactfolder should be used. - Each different archetype is put in a separate folder
commonfolder contains any common components that can be used by the other archetypes- Inside the archetype folders, if the API is versioned, then we need to have a clear distinction for that too... this is only valid for major API changes, example would be vRLI v1 and v2 apis.
- Example:
-
@akantchev this will not be a breaking change, correct? If so do we need to have the 3.0.0 milestone?
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Partially implemented in milestone 3.x.x, will be finished in 4.x.x
Related PRs:
- https://github.com/vmware/build-tools-for-vmware-aria/pull/581
- https://github.com/vmware/build-tools-for-vmware-aria/pull/593
- https://github.com/vmware/build-tools-for-vmware-aria/pull/710
- https://github.com/vmware/build-tools-for-vmware-aria/pull/829
https://github.com/vmware/build-tools-for-vmware-aria/blob/main/common/artifact-manager/src/main/java/com/vmware/pscoe/iac/artifact/IMPORTANT.md
Good job @VenelinBakalov 😁 this has been a hell of a task, finally done
@Michaelpalacce it was fun, especially the linter fixes :D as usual, thanks for suggesting this restructuring and proposing the current state - the new organization is way better and much easier to work with