Hi folks, I created the PR for the Polaris Console (UI): https://github.com/apache/polaris-tools/pull/85
I also recorded a quick video with the current console in action: https://drive.google.com/file/d/1crPlUyQQPtEAZPO37for7SQvp4NwR_Pj/view?usp=sharing I would like to thank the two contributors with me on this effort: Sohan and Artur. I'm still working on the Console, but if it's OK for you all, I would like to land the console in polaris-tools to encourage contributions on this. Please, feel free to take a look at the PR, and let me know if you have any questions. Thanks ! Regards JB JB On Wed, Nov 26, 2025 at 7:45 PM Yufei Gu <[email protected]> wrote: > > Hi JB, > > Thanks again for pushing the UI effort forward! It’s exciting to see the > progress. > > Given that this introduces a fairly big change in how users interact with > Polaris, would you mind sharing a design document (or even a draft) that > outlines the overall architecture, scope, and key workflows you have in mind? > This will help the community review the approach consistently and ensure the > design aligns well with our long-term direction. > > Appreciate your work on this and looking forward to the details. > > Best, > > Yufei > > > On Tue, Oct 14, 2025 at 11:47 PM Jean-Baptiste Onofré <[email protected]> > wrote: >> >> About 2, I can share the screenshots that I did. Basically, you can >> configure multiple Polaris server instances in the UI. >> Then you can have several catalogs on each server. >> >> The UI has to manage several server instances, and multiple catalogs. >> That's what the UI should not be in one server, but a standalone UI >> being to manage several servers. >> >> Also, in my PoC (as you can see in the screenshots), I manage the >> entities but also Polaris feature (Policies, TMS, ...). >> >> Regards >> JB >> >> On Tue, Oct 14, 2025 at 10:29 PM artur rakhmatulin >> <[email protected]> wrote: >> > >> > Hello. Thank you very much for the detailed information provided. >> > >> > Regarding point 1, I don't have a strong opinion about whether this should >> > be a separate UI application or part of Polaris Deployment together with >> > "polaris-server". >> > Regarding point 2, could you please clarify? >> > As I understand it, Polaris already supports working with multiple >> > catalogs, since there is the ability to create them through the API. Do >> > you mean the ability to connect to different Backend Hosts? >> > >> > I would also like to add that if there is already a repository or branch >> > with developments, I would be happy to dedicate some of my time to >> > refining the existing solution in accordance with Apache standards and >> > technologies. >> > >> > вт, 14 окт. 2025 г. в 14:50, Jean-Baptiste Onofré <[email protected]>: >> >> >> >> Hi >> >> >> >> It’s also what I did. I think we agreed on: >> >> 1. Have a “standalone” UI (not shipped in the Polaris server). >> >> 2. Have a multi catalog/instance UI, so basically with a configuration to >> >> define several instance endpoints. >> >> >> >> I started 2 with a minimal backend (with file store). >> >> >> >> Regards >> >> JB >> >> >> >> Le lun. 13 oct. 2025 à 19:42, artur rakhmatulin >> >> <[email protected]> a écrit : >> >>> >> >>> Hello. I would like to propose my help in this initiative if needed. >> >>> >> >>> I also lately build a personal Polaris UI with the minimal functionality >> >>> for managing roles and principals. >> >>> Initially my motivation was to have a minimal interface which could help >> >>> to better understand all relations between entities. >> >>> >> >>> The repo is public, so everyone can clone it and try [1] >> >>> Demo video [2] >> >>> >> >>> [1]: https://github.com/binarycat0/polaris-admin-panel >> >>> [2]: >> >>> https://github.com/binarycat0/polaris-admin-panel/releases/download/0.0.1-dev/Screen.Recording.2025-10-13.at.17.38.41.mov >> >>> >> >>> >> >>> чт, 4 сент. 2025 г. в 18:03, Yufei Gu <[email protected]>: >> >>>> >> >>>> Awesome, thanks for the update! >> >>>> >> >>>> >> >>>> On Thu, Sep 4, 2025 at 01:27 Jean-Baptiste Onofré <[email protected]> >> >>>> wrote: >> >>>> >> >>>> > Hi folks, >> >>>> > >> >>>> > FYI, I'm resuming the work on the UI, I have the first components >> >>>> > working with the backend. >> >>>> > I will probably submit a draft PR on polaris-tools as a discussion >> >>>> > base. >> >>>> > >> >>>> > Stay tuned ;) >> >>>> > >> >>>> > Regards >> >>>> > JB >> >>>> > >> >>>> > On Thu, Apr 17, 2025 at 1:06 AM Jean-Baptiste Onofré >> >>>> > <[email protected]> >> >>>> > wrote: >> >>>> > > >> >>>> > > Hi folks, >> >>>> > > >> >>>> > > In order to grow our community, I think there's a space where we >> >>>> > > could >> >>>> > > do better work: onboarding of new users. >> >>>> > > New users are looking for Polaris to be easy to start with and easy >> >>>> > > to >> >>>> > use. >> >>>> > > >> >>>> > > We already do great improvements here, especially, I strongly >> >>>> > > believe >> >>>> > > that starting from the 0.10.0-beta-incubating release (and the next >> >>>> > > releases), we will have new users thanks to the binary >> >>>> > > distributions. >> >>>> > > >> >>>> > > And so, the onboarding and ease of use becomes even more important >> >>>> > > for >> >>>> > > these new users. >> >>>> > > For onboarding, documentation is crucial. I know we already have >> >>>> > > effort on the documentation, a focus on onboarding is welcome >> >>>> > > (started >> >>>> > > guide, curl example, engines examples, ...). >> >>>> > > >> >>>> > > Also, the CLI is helping for the onboard/bootstrap. >> >>>> > > >> >>>> > > For both onboard and ease of use, I would like to propose Polaris >> >>>> > > UI. >> >>>> > > I started to work on a Polaris UI. You can see the first screenshots >> >>>> > here: >> >>>> > > >> >>>> > > >> >>>> > https://drive.google.com/file/d/14q47kfdpWNvxYcv723xUqnBdwBFJ9qCx/view?usp=sharing >> >>>> > > >> >>>> > > >> >>>> > https://drive.google.com/file/d/1-TckYYif4Jz0dnHc7oRikgXx6i3awKKL/view?usp=sharing >> >>>> > > >> >>>> > > It uses RestJS (https://react.dev/) and Ant Design >> >>>> > > (https://ant.design/) frameworks, using MIT license (which is >> >>>> > > Category >> >>>> > > A from The ASF standpoint). >> >>>> > > I'm currently build static web app (using yarn or npm). It means >> >>>> > > that: >> >>>> > > - the UI can be "embedded" in the Polaris server (just pure >> >>>> > > HTML/JavaScript resources basically) >> >>>> > > - the UI can run "standalone" and connect to Polaris server >> >>>> > > instances. >> >>>> > > About that, I plan to add an item in the settings menu to be able to >> >>>> > > configure multiplace Polaris server instances. >> >>>> > > >> >>>> > > To be clear, it's certainly a "non production" audience that is >> >>>> > > gonna >> >>>> > > use this UI (new users, experiment, ...) but valuable overall. >> >>>> > > >> >>>> > > Thoughts ? >> >>>> > > >> >>>> > > Regards >> >>>> > > JB >> >>>> > >> >>> >> >>> >> >>> >> >>> -- >> >>> Best regards, Artur Rakhmatulin >> >>> e-mail: [email protected], >> >>> telegram: https://t.me/binarycat0 >> >>> >> > >> > >> > -- >> > Best regards, Artur Rakhmatulin >> > e-mail: [email protected], >> > telegram: https://t.me/binarycat0 >> >
