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
The DuckDB secrets manager provides a unified user interface for secrets across all backends that use them. Secrets can be scoped, so different storage prefixes can have different secrets, allowing for example to join data across organizations in a single query. Secrets can also be persisted, so that they do not need to be specified every time DuckDB is launched.
We want to use the secrets manager available since v0.9.2 to resplace the SET commands. Meaning instead of
# Setup connection parameters
SET sap_ashost = '[HOST IP ADRESS]';
SET sap_sysnr = '00';
SET sap_user = '[USERNAME]';
SET sap_password = '[PASSWORD]';
SET sap_client = '001';
SET sap_lang = 'EN';
One can do then
CREATE SECRET (
TYPE SAP_RFC,
ASHOST '${HOST_IP_ADDRESS}',
SYSNR '00',
CLIENT '001',
USER '${USERNAME}',
PASSWORD '${PASSWORD}',
LANG 'EN'
)
The text was updated successfully, but these errors were encountered:
No, unfortunately we were not aware of that issue. And we have to really
look into if if is a problem on our side.
Maybe you can open a separate issue? Does `select * from
duckdb_settings();` output the correct password?
Cheers, Joachim
Am Mi., 19. Juni 2024 um 16:26 Uhr schrieb Gregor Wolf <
***@***.***>:
The DuckDB secrets manager provides a unified user interface for secrets across all backends that use them. Secrets can be scoped, so different storage prefixes can have different secrets, allowing for example to join data across organizations in a single query. Secrets can also be persisted, so that they do not need to be specified every time DuckDB is launched.
We want to use the secrets manager available since v0.9.2 to resplace the
SET
commands. Meaning instead ofOne can do then
The text was updated successfully, but these errors were encountered: