Expose proxy_user and proxy_password from SnowflakeConnection to SnowflakeCredentials class #1303
+8
−0
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.
resolves #
docs dbt-labs/docs.getdbt.com/#
Problem
Unable to connect to Snowflake in a corporate environment as
proxy_user
andproxy password
are not attributes ofSnowflakeCredentials
. These attributes are attributes of the underlyingSnowflakeConnection
, just likeproxy_host
andproxy_port
, however theSnowflakeCredentials
class does not currently expose them.Solution
Successfully connected to Snowflake after hard-coding the
proxy_user
andproxy password
in thesnowflake.connector.connect(...)
in theSnowflakeConnectionManager
class.This PR exposes the
proxy_user
andproxy password
attributes of the underlyingSnowflakeConnection
class to theSnowflakeCredentials
class so that the above workaround is not needed.Checklist