You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would be useful for enabling the AWS extension default credentials provider chain:
CREATE SECRET secret1 (
TYPE S3,
PROVIDER CREDENTIAL_CHAIN
);
There doesn't seem to be any other way to use the default credential provider chain with the duckdb_engine create_engine call. Using duckdb_engine with Superset, all of the setup for secrets needs to be accomplished in the create_engine call. Passing the s3_* configuration works if using a specific access/secret key credentials, but there are no configuration options for AWS extension settings.
DuckDB has added support for secrets in the latest dev version: duckdb/duckdb#10042
Can we support this as a first class feature?
The text was updated successfully, but these errors were encountered: