Hi everyone, While reviewing PR 5664, (https://github.com/apache/polaris/pull/5664) I found storageName requires the admin creating a connection to know a name configured on the server. That is awkward when catalog admins and Polaris deployment admins are different people. It’s very likely in a multi-realm Polaris deployment.
Polaris already uses this pattern for storage credentials (#3409 ( https://github.com/apache/polaris/pull/3409)). I think we can keep it and improve discovery. One idea is to treat these names as credential profiles and later let users list the profiles they are allowed to use. They would select one and put its name into storageName. Credentials would stay on the server, and existing configurations would continue to work. This would let catalog admins choose credentials without inspecting server configuration or asking deployment admins for each name. Both listing and using a profile should respect permissions. WDYT? Thanks, Yufei
