Hey everyone, I’m trying to create a source asset which represents a table in my db that is managed completely outside of Dagster (it’s essentially a manually curated set of ids that we want to rely on in the pipelines with sensors). I’d like to create an

observable_source_asset

for this, but I need to have access to a resource (db connection) within the

observe_fn

to calculate a

LogicalVersion

value. For a normal asset I have

required_resource_keys

and the

context

object, but how do I do this in an observable source asset? Does this even make sense?

Hi Andras, this certainly makes sense and we’re adding this functionality in our next dagster release-- it was an oversight that resources aren’t currently accessible.

Great, thanks for the confirmation! At least I wasn't looking at it totally backwards 😄