are resources cached in any way in dagit (or dagster in general)? e.g. if we're using a resource with no config schema, will it spin up a new instance of that resource for each pipeline run, or use the same instance for each run?
(we're seeing a problem with a gcloud-authenticated resource where its access token is reporting as invalid sporadically, and i'm trying to see if it might be because it's using an old instance of the resource whose token has expired)
04/28/2021, 2:52 PM
Hi Steve - each pipeline run typically happens in its own process separate from dagit, so there shouldn't be any resource caching happening here due to dagster
04/28/2021, 2:53 PM
well, that's good, but disappointing that i'm back to square one. thank you!