Skip to content

Auto-infer rest.auth.type explicitly in catalog_create_rest - #115

Open
gbrgr wants to merge 1 commit into
mainfrom
gb/rest-auth-type-inference
Open

gbrgr wants to merge 1 commit into
mainfrom
gb/rest-auth-type-inference

Conversation

@gbrgr

@gbrgr gbrgr commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Summary

iceberg-rust's REST catalog client infers rest.auth.type=oauth2 from token/credential/oauth2-server-uri properties and logs a WARN every time it does, specifically to push callers toward setting the property explicitly instead of relying on inference. We can be that explicit caller ourselves in catalog_create_rest, so every caller (raicode included) stops getting spammed by this warning, rather than pushing the fix onto each of them individually.

This was originally part of #114 but got dropped in that PR's squash-merge (committed locally, never pushed to that branch before it merged) — re-submitting standalone since it's unrelated to that PR's actual content.

Test plan

  • Full make test-dev suite: 27,950 passed, 0 failed
  • Confirmed 0 occurrences of the "Inferring rest.auth.type=oauth2" warning across the whole suite (previously present on every REST-catalog test)

🤖 Generated with Claude Code

iceberg-rust's REST catalog client infers rest.auth.type=oauth2 from
token/credential/oauth2-server-uri properties and logs a WARN every
time it does, specifically to push callers toward setting the
property explicitly instead of relying on inference. We can be that
explicit caller ourselves in catalog_create_rest, so every caller
(raicode included) stops getting spammed by this warning, rather than
pushing the fix onto each of them individually.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant