[DOP-29475] Implement Iceberg connection type #144
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dolfinus
force-pushed
the
feature/DOP-29475
branch
from
0fa93c1 to
caa1d95
Compare
dolfinus
force-pushed
the
feature/DOP-29475
branch
from
caa1d95 to
490b816
Compare
srj-mx-a11y
approved these changes
Dec 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Iceberg connection has selectable REST Catalog Auth options (either Bearer token or OAuth2ClientCredentials), and S3 access (direct vs. delegate to REST Catalog). This makes component a bit complicated, as auth fields depend on S3 access style.
Form with BearerToken and delegated S3 access
Form with OAuth2ClientCredentials and direct S3 access:
Transfer creation page:
