Hi All, Currently Polaris core code has a very specific mechanism for extracting PolarisStorageConfigurationInfo from entities. The config value is then passed to a PolarisStorageIntegrationProvider.
Now, PolarisStorageIntegrationProvider is pluggable and works with the config extracted from entities by Polaris core. I am proposing to add another integration point that would handle the construction of PolarisStorageConfigurationInfo and work in conjunction with PolarisStorageIntegrationProvider. Having both of these actions customizable is intended to allow more flexibility (and better code alignment) in handling storage integrations in downstream projects. I'm working on a PR to provide a concrete suggestion. Sending this email to proactively ask if there are any concerns with this approach. WDYT? Thanks, Dmitri.
