You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run the command:
snow connection set-default connection2.
Instead of switching connection2 to be the default, it tries to connect first to connection1 (through browser authentication) before it switches to connection2.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
changing default CLI connection requires using older connection.
SNOW-1617095: changing default CLI connection requires using older connection.
Aug 7, 2024
I think this applies to other commands like 'snow --version'. We shouldn't be using the existing connection for these. If we do it for telemetry, then we should set some kind of strict/short timeout.
SnowCLI version
3.0.0.dev0
Python version
3.10.0
Platform
macOS-10.16-x86_64-i386-64bit
What happened
snow CLI uses the old connection when setting the default connection to something new.
Console output
No response
How to reproduce
Assume 2 connections in your config list:
connection1: {'account': 'x', 'user': 'x', 'host': 'x', 'port': x, 'role': 'x', 'authenticator': 'externalbrowser'}
connection2: {'account': 'x', 'user': 'x', 'password': 'x', 'host': 'x', 'warehouse': 'x', 'role': 'x', 'authenticator': 'SNOWFLAKE_JWT', 'private_key_path': 'x'}
Default connection is connection1.
I run the command:
snow connection set-default connection2.
Instead of switching connection2 to be the default, it tries to connect first to connection1 (through browser authentication) before it switches to connection2.
The text was updated successfully, but these errors were encountered: