Mark Atkins06/20/2022, 10:42 PM
package, I'm not currently using the dagster-snowflake implementation because I'd like to be able to use the web based browser authentication for this resource on a local machine.
Setting up the resource is no trouble, but something I'm noticing is that If I have multiple ops that consume this resource, the browser auth is triggered for every distinct op that utilizes the resource. Reading through the documentation it conceptually makes sense that this would happen, basically executing the code within a resource definition at every op. But is there any way to instantiate a connection object/cursor once at the beginning of a job within a resource, so that each time the resource is utilized in an op it doesn't attempt to recreate the object?
sandy06/21/2022, 12:19 AM
Stephen Bailey06/21/2022, 12:56 AM
Will also note I never got this working satisfactorily (hazy on the details of why) and went with a keypair route, so i'm just pointing you here, cant endorse it. 😬
Note: By default, every connection that dbt opens will require you to re-authenticate in a browser. The Snowflake connector package supports caching your session token, but it currently only supports Windows and Mac OS. See the Snowflake docs for how to enable this feature in your account.
Mark Atkins06/27/2022, 10:02 PM