Repository navigation
SNOW-3020359 expand tilde to key file path in connection - #2759
Merged
sfc-gh-turbaszek merged 11 commits intoFeb 11, 2026
Merged
Conversation
|
All contributors have signed the CLA ✍️ ✅ |
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA |
sfc-gh-turbaszek
approved these changes
Feb 11, 2026
sfc-gh-turbaszek
approved these changes
Feb 11, 2026
sfc-gh-turbaszek
deleted the
SNOW-3020359-expand-tilde-in-connection-too
branch
February 11, 2026 10:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please answer these questions before submitting your pull requests. Thanks!
What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
This fix aims to address issue SNOW-3020359: Automatically expand tilde (~) to $HOME in private_key_file path #2746, where we do not expand tilde (
~) in Connection forprivate_key_fileconfiguration, thus the driver cannot read the key file for keypair auth in such cases.Fill out the following pre-review checklist:
Please describe how your code solves the related issue.
Using
pathlib.Path(path_to_key).expanduser(), which should work on both Unix and Windows bases systems, and even work withoutHOMEenvvar set (and for Linux, read it from/etc/passwd)Besides adding an automated test, also manually tested on Linux and Windows (latter both with
\\and/style path separator)(Optional) PR for stored-proc connector: