Skip to content
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

Secret support #887

Open
Mause opened this issue Feb 4, 2024 · 1 comment
Open

Secret support #887

Mause opened this issue Feb 4, 2024 · 1 comment

Comments

@Mause
Copy link
Owner

Mause commented Feb 4, 2024

DuckDB has added support for secrets in the latest dev version: duckdb/duckdb#10042

Can we support this as a first class feature?

CREATE [OR REPLACE] [PERSISTENT | TEMPORARY] SECRET [IF NOT EXISTS] [secret_name] [IN storage_specifier] (
 	TYPE secret_type,
   	[PROVIDER provider,]
	[SCOPE path_or_list_of_paths,]
	[KEY1 value1],
	[KEY2 value2],
	...
)
@Joel-PeakMetrics
Copy link

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.

Thank you for your contributions on this project!

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

No branches or pull requests

2 participants