Skip to content
Open
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/source/format/connection_profiles.rst
Original file line number Diff line number Diff line change
Expand Up @@ -193,8 +193,11 @@ When using a profile name (not an absolute path), the driver manager searches fo
1. **Additional Search Paths** (if configured via ``AdbcDriverManagerDatabaseSetAdditionalSearchPathList()``)
2. **ADBC_PROFILE_PATH** environment variable (colon-separated on Unix, semicolon-separated on Windows)
3. **Conda Environment** (if built with Conda support and ``CONDA_PREFIX`` is set):

- ``$CONDA_PREFIX/etc/adbc/profiles/``

4. **User Configuration Directory**:

- Linux: ``~/.config/adbc/profiles/``
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zeroshade I notice that in the driver manifests docs, we mention XDG_CONFIG_HOME, but here in the connection profiles docs we don't.

Does the driver manager search behavior not work consistently w.r.t. XDG_CONFIG_HOME in both cases?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at the code, it should be consistent and I just forgot to mention the XDG_CONFIG_HOME here. So you can just update this appropriately to match

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added in fd2d228

- macOS: ``~/Library/Application Support/ADBC/Profiles/``
- Windows: ``%LOCALAPPDATA%\ADBC\Profiles\``
Expand Down Expand Up @@ -433,7 +436,7 @@ Store credentials separately from code:

[options]
adbc.snowflake.sql.account = "mycompany"
adbc.snowflake.sql.auth_token = "env_var(SNOWFLAKE_TOKEN)"
adbc.snowflake.sql.auth_token = "{{ env_var(SNOWFLAKE_TOKEN) }}"

Then set ``SNOWFLAKE_TOKEN`` via environment variable, secrets manager, or configuration service.

Expand Down
2 changes: 1 addition & 1 deletion docs/source/format/driver_manifests.rst
Original file line number Diff line number Diff line change
Expand Up @@ -499,7 +499,7 @@ would happen for ODBC drivers. The search for a manifest on Windows would be the
* ``entrypoint`` - the entrypoint to use for the driver if a non-default entrypoint is needed
* ``driver`` - the path to the driver shared library

* If no registry key is found, then the directory ``%LOCAL_APPDATA%\ADBC\Drivers`` is searched
* If no registry key is found, then the directory ``%LOCALAPPDATA%\ADBC\Drivers`` is searched

#. If the ``LOAD_FLAG_SEARCH_SYSTEM`` load option is set, the driver manager will search for a system-level configuration

Expand Down
Loading