[Bug] dbt-snowflake opens a new connection per each model

[TiansuYu]

Is this a new bug in dbt-snowflake?

• I believe this is a new bug in dbt-snowflake
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

The way I am currently using dbt-snowflake locally is that, I have a dbt profile as follows:

my-snowflake:
  target: dev
  outputs:
    dev:
        type: snowflake
        account: some-account
        authenticator: externalbrowser
        
        database: xyz
        user: xyz
        role: xyz
        warehouse: xyz
        schema: ""

        threads: 4

However, running dbt test creates a snowflake connection per each model. This fires a huge amount of connection request on my browser, and I barely have time to click on Duo for 2FA requests. After a few try, because I wasn't responding enough on Duo, the 2FA would lock me out.

I am wondering what is the connection management practices in this repo looks like? Has the connection pool been properly managed? https://docs.snowflake.com/en/developer-guide/node-js/nodejs-driver-connect#creating-a-connection-pool

Expected Behavior

Each dbt run should create a proper connection, ideally one per each thread, and whatever dbt jobs running should pick up connections from the pool, instead of firing auth request like it is free candy.

Steps To Reproduce

1. Create a dbt profile in ~/.dbt/profile.yml
2. set authenticator: externalbrowser
3. Use an example dbt project with a lot of models and run dbt deps && dbt test.

Relevant log output

No response

Environment

- OS: MacOs
- Python: 3.12
- dbt-core: 1.8.8
- dbt-snowflake: 1.8.4

Additional Context

No response

[amychen1776]

@TiansuYu Have you enabled token caching? We have some links in our docs here https://docs.getdbt.com/docs/cloud/connect-data-platform/connect-snowflake#snowflake-mfa