-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SNOW-1855886 gracefully ignore when default region us-west-2 is used in DSN or NewConnector #1278
base: master
Are you sure you want to change the base?
Conversation
…in DSN or NewConnector
dsn_test.go
Outdated
User: "u", | ||
Password: "p", | ||
Account: "account", | ||
Host: "account.us-west-2.snowflakecomputing.com", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we support also account.us-west-2.aws
- there also dsn should be shortened?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
then the next question is that we should correct every notation in every driver, which i agree is the ideal final goal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added SNOW-1858448
to track the more comprehensive effort
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1278 +/- ##
==========================================
- Coverage 82.21% 82.20% -0.02%
==========================================
Files 55 55
Lines 13537 13547 +10
==========================================
+ Hits 11130 11136 +6
- Misses 2407 2411 +4 ☔ View full report in Codecov by Sentry. |
Description
us-west-2
region is the default region in Snowflake, and a special one. We already had checks for the case where someone accidentally configures it inRegion
, but forAccount
we did not have any, which led to anAccount
(mis)configured asmyaccount.us-west-2
instead of omitting the region (as is the default) and usingmyaccount
, not being able to connect to Snowflake and instead failing with HTTP404.This change attempts to step over such simple misconfiguration gracefully and
.us-west-2
from Account instead of allowing the connection to proceed, which then surely will fail on the Snowflake backendChecklist