[I] CLI: Add support for custom IRC base URIs [polaris]

["dimas-b (via GitHub)" <gi...@apache.org>]

dimas-b opened a new issue, #4927:
URL: https://github.com/apache/polaris/issues/4927

   Suppose a deployment maps `http://localhost:8181/server1` to a particular IRC base URI.
   
   Trying to list namespaces via CLI yields a 404:
   
   ```
   $ .venv/bin/polaris --base-url http://localhost:8181/server1 --access-token $POLARIS_TOKEN namespaces list --catalog polaris --debug
   Request: GET http://localhost:8181/server1/api/catalog/v1/polaris/namespaces
   Headers: {'Accept': 'application/json', 'User-Agent': 'OpenAPI-Generator/1.0.0/python', 'Authorization': 'Bearer ***'}
   ```
   
   Notice that the CLI appended the `/api/catalog` path segment. However, in my env. `http://localhost:8181/server1` is already mapped to the root of the IRC catalog in the appropriate server. 
   
   The CLI is not usable in this env. because it assumes the `/api/catalog` base URI suffix.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@polaris.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] CLI: Add support for custom IRC base URIs [polaris]

["MonkeyCanCode (via GitHub)" <gi...@apache.org>]

MonkeyCanCode closed issue #4927: CLI: Add support for custom IRC base URIs
URL: https://github.com/apache/polaris/issues/4927


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@polaris.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] CLI: Add support for custom IRC base URIs [polaris]

["vigneshio (via GitHub)" <gi...@apache.org>]

vigneshio commented on issue #4927:
URL: https://github.com/apache/polaris/issues/4927#issuecomment-4836688676

   I'd like to work on this, @dimas-b.
   
   My initial thought is to keep this backward compatible by introducing a new `--catalog-url` option that is used verbatim as the Iceberg REST Catalog base URI (i.e., exactly what you'd provide as the Iceberg `uri`), while leaving `--base-url` unchanged for the management API.
   
   This would allow `--access-token` + `--catalog-url` to work for catalog-only commands without requiring any server-side changes.
   
   Sound reasonable ?? WDYT ?? ..  Or do you hve a diff direction in mind before I open a PR? 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@polaris.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org