Skip to content
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

Snowflake alternative hostname implementation #22133

Closed
BenSatori opened this issue Apr 27, 2022 · 1 comment · Fixed by #39471
Closed

Snowflake alternative hostname implementation #22133

BenSatori opened this issue Apr 27, 2022 · 1 comment · Fixed by #39471

Comments

@BenSatori
Copy link

BenSatori commented Apr 27, 2022

Is your feature request related to a problem? Please describe.
Snowflake supports using an alternative hostname (e.g. not .snowflakecomputing.com). Without setting it, in environments such as with privatelink or custom hostnames (such as proxied), it's not possible to configure Snowflake.

Describe the solution you'd like
Adding an advanced settings field of "alternative hostname", which if present will override the existing hostname (.snowflakecomputing.com). Note that the account itself needs to be sent with the "account" JDBC parameter.

How important is this feature to you?
For us this is specifically important, as we proxy traffic to Snowflake accounts.

⬇️ Please click the 👍 reaction instead of leaving a +1 or update? comment

@likeshumidity
Copy link
Contributor

Metabase users are unable to connect to Snowflake via PrivateLink until this is resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants