Hi! First, thanks for this great extension!
One thing I have been thinking of for a while is, how might we securely set headers when talking to APIs that require authentication?
The most common use case I run into is setting Bearer tokens.
For now the best ways I found was to put the token in a file or in a database and read it from there to not hard-code it into the SQL.
Reading from environment variables doesn't work for my use case since I don't want to allow reading env vars.
What I was thinking: It would be cool if the extension would work with DuckDB secrets for Bearer tokens and potentially other headers. That way the user would not have any access to the secret but could still securely call APIs.
What do you think? Is this in the scope of this extension? Or am I missing some better ideas how to do this?
Thanks!
Hi! First, thanks for this great extension!
One thing I have been thinking of for a while is, how might we securely set headers when talking to APIs that require authentication?
The most common use case I run into is setting Bearer tokens.
For now the best ways I found was to put the token in a file or in a database and read it from there to not hard-code it into the SQL.
Reading from environment variables doesn't work for my use case since I don't want to allow reading env vars.
What I was thinking: It would be cool if the extension would work with DuckDB secrets for Bearer tokens and potentially other headers. That way the user would not have any access to the secret but could still securely call APIs.
What do you think? Is this in the scope of this extension? Or am I missing some better ideas how to do this?
Thanks!