Hi Yufei, My plan is to make specific changes available in the form of a PR... I'm still working on them :)
Cheers, Dmitri. On Thu, Aug 21, 2025 at 8:54 PM Yufei Gu <flyrain...@gmail.com> wrote: > Hi Dimitri, > > > add another integration point that would handle the construction of > PolarisStorageConfigurationInfo and work in conjunction with > PolarisStorageIntegrationProvider > > Could you share more details about it? Or we can just review the PR. > > Yufei > > > On Wed, Aug 20, 2025 at 10:59 PM Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > > > Hi Dmitri > > > > It looks good to me. I'm looking forward the PR to have a better > > understanding of the proposal. > > > > Thanks ! > > Regards > > JB > > > > On Mon, Aug 18, 2025 at 6:08 PM Dmitri Bourlatchkov <di...@apache.org> > > wrote: > > > > > > 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. > > >
