Skip to content

feat(duckdb-driver): Add support for using default credential provider chain for duckdb s3 access #9679

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

KSDaemon
Copy link
Member

@KSDaemon KSDaemon commented Jun 13, 2025

This PR supersedes the original one #8935 by @GabeInDevOps. Just some code polishment.

Fixes #8920.
Closes #8935.

Check List

  • Tests have been run in packages where changes made if available
  • Linter has been run for changed code
  • Tests for the changes have been added if not covered yet
  • Docs have been added / updated if required

GabeInDevOps and others added 4 commits November 6, 2024 21:31
…beInDevOps/cube into GabeInDevOps-feat/duckdb-credential-provider-chain

# Conflicts:
#	packages/cubejs-backend-shared/src/env.ts
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.

Duckdb driver should look for credentials in the default provider chain for AWS S3
2 participants