Support keyless s3 integration for iceberg destination #47417
+0
−4
Conversation
This file contains 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
|
@noamd-legit is attempting to deploy a commit to the Airbyte Growth Team on Vercel. A member of the Team first needs to authorize it. |
|
|
octavia-squidington-iii
added
area/connectors
noamd-legit
had a problem deploying
to
community-ci-auto
GitHub Actions
Error
noamd-legit
had a problem deploying
to
community-ci
GitHub Actions
Error
noamd-legit
had a problem deploying
to
community-ci-auto
GitHub Actions
Error
noamd-legit
had a problem deploying
to
community-ci
GitHub Actions
Error
noamd-legit
requested a deployment
to
community-ci
GitHub Actions
Waiting
noamd-legit
had a problem deploying
to
community-ci-auto
GitHub Actions
Failure
noamd-legit
requested a deployment
to
community-ci
GitHub Actions
Waiting
noamd-legit
had a problem deploying
to
community-ci-auto
GitHub Actions
Failure
noamd-legit
changed the title
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.
What
The destination Iceberg connector does not support IAM machine authentication for S3, and instead requires access key and secret ID credentials, even though the underlying code does support IAM authentication.
How
Removing the access access key and key id from the spec required fields
Review guide
User Impact
The user will be able to integration s3 based iceberg tables with out access key and key id
Can this PR be safely reverted and rolled back?