Hello Yufei, I think that is fair as we don't currently support spec versioning and there can be breaking changes across version which declarative spec can be challenging. I will get some prototype up and share for the minimal scope then expand it as needed. Thanks for the great feedback.
Side note, as API versioning is kind important for this type functionality (as well as for MCP etc.), do we have a plan to add those support? Even for general CLI, this is needed as if we are running latest CLI on older polaris server, not all features will work. Thanks, Yong Zheng On 2026/02/24 01:59:39 Yufei Gu wrote: > Hi Yong, > > I think it is useful. However, maintaining a declarative spec could be > challenging over time, especially as entities and defaults evolve. If we go > this direction, I would strongly prefer keeping the scope minimal and > versioned, and treating it as a bootstrap focused schema rather than a > general reconciler. A general reconciler would need to encode ongoing > desired state, drift handling, and potentially destructive updates as > Polaris evolves, which is a much larger long term maintenance and > compatibility commitment than a one time, mostly additive bootstrap. > > Yufei > > > On Mon, Feb 23, 2026 at 3:02 PM Dmitri Bourlatchkov <[email protected]> > wrote: > > > Hi Yong, > > > > Indeed, the synchronizer tool does not appear to have much traction in the > > community (unfortunately). > > > > I'd support enhancing the CLI with handy tools for better UX. > > > > TBH, I did not review PR 1474, but the idea sounds reasonable to me. > > > > Cheers, > > Dmitri. > > > > On Sat, Feb 21, 2026 at 1:38 AM Yong Zheng <[email protected]> wrote: > > > > > Hello, > > > > > > I created https://github.com/apache/polaris/pull/1474 a while back as a > > > POV to show whether we should add functionality in the CLI to allow > > > bootstrapping base Polaris entities for a given setup. This is very handy > > > IMO when people need to bootstrap multiple catalogs while avoiding some > > > local scripts or creating another internal tool for orchestration work to > > > get Polaris to a working state when deploying to a new environment. > > > > > > From the POV, the discussion around that time was that polaris > > > synchronizer ( > > > > > https://github.com/apache/polaris-tools/tree/46fe5e057e617eecee4da41bc36791736e3c55de/polaris-synchronizer > > ) > > > would take up these functionalities. However, that doesn't appear to be > > in > > > place as of today. Thus, I would like to get some feedback from the > > > community on whether we should proceed with adding this functionality > > into > > > the CLI. > > > > > > I really like the philosophy of declarative automation. Perhaps we can > > > implement it with a lightweight declarative reconciler for bootstrap. > > > > > > Thanks, > > > Yong Zheng > > > > > >
