Extract storage integration code from polaris-core into seprate modules per technology
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 522
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 137
Description
### Is your feature request related to a problem? Please describe.
Currently `polaris-core` forces all dependencies to receive all storage integration implementations (AWS, GCS, Azure) with their transitive dependencies.
This can be inconvenient in downstream builds.
### Describe the solution you'd like
It would be nice to have separate storage integration modules per technology
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Start by mapping the storage integration implementations currently bundled in polaris-core for AWS, GCS, and Azure, including their transitive dependencies. Separate the integrations into technology-specific modules and verify that downstream builds no longer receive unrelated storage implementations or dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, java
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100