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
Copy file name to clipboardExpand all lines: docs/integrations/engines/duckdb.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@
17
17
|`catalogs`| Mapping to define multiple catalogs. Can [attach DuckDB catalogs](#duckdb-catalogs-example) or [catalogs for other connections](#other-connection-catalogs-example). First entry is the default catalog. Cannot be defined if using `database`. | dict | N |
18
18
|`extensions`| Extension to load into duckdb. Only autoloadable extensions are supported. | list | N |
19
19
|`connector_config`| Configuration to pass into the duckdb connector. | dict | N |
20
-
|`secrets_config`| Configuration for authenticating external sources (e.g., S3) using DuckDB secrets. | dict | N |
20
+
|`secrets`| Configuration for authenticating external sources (e.g., S3) using DuckDB secrets. | dict | N |
21
21
22
22
#### DuckDB Catalogs Example
23
23
@@ -142,11 +142,11 @@ If a connector, like Postgres, requires sensitive information in the path, it mi
142
142
143
143
DuckDB can read data directly from cloud services via extensions (e.g., [httpfs](https://duckdb.org/docs/extensions/httpfs/s3api), [azure](https://duckdb.org/docs/extensions/azure)).
144
144
145
-
The `secrets_config` option allows you to configure DuckDB's [Secrets Manager](https://duckdb.org/docs/configuration/secrets_manager.html) to authenticate with external services like S3. This is the recommended approach for cloud storage authentication in DuckDB v0.10.0 and newer, replacing the [legacy authentication method](https://duckdb.org/docs/stable/extensions/httpfs/s3api_legacy_authentication.html) via variables.
145
+
The `secrets` option allows you to configure DuckDB's [Secrets Manager](https://duckdb.org/docs/configuration/secrets_manager.html) to authenticate with external services like S3. This is the recommended approach for cloud storage authentication in DuckDB v0.10.0 and newer, replacing the [legacy authentication method](https://duckdb.org/docs/stable/extensions/httpfs/s3api_legacy_authentication.html) via variables.
146
146
147
147
##### Secrets Configuration Example for S3
148
148
149
-
The `secrets_config` accepts a list of secret configurations, each defining the necessary authentication parameters for the specific service:
149
+
The `secrets` accepts a list of secret configurations, each defining the necessary authentication parameters for the specific service:
150
150
151
151
=== "YAML"
152
152
@@ -160,7 +160,7 @@ The `secrets_config` accepts a list of secret configurations, each defining the
160
160
remote: "s3://bucket/data/remote.duckdb"
161
161
extensions:
162
162
- name: httpfs
163
-
secrets_config:
163
+
secrets:
164
164
- type: s3
165
165
region: "YOUR_AWS_REGION"
166
166
key_id: "YOUR_AWS_ACCESS_KEY"
@@ -189,7 +189,7 @@ The `secrets_config` accepts a list of secret configurations, each defining the
0 commit comments