I was trying to take a stab at the migration to pythonic resources (see here), but I'm getting a little confused about the best way to deal with the following case: We have quite a lot of existing configuration that is based on pydantic

BaseModel

and/or

BaseSettings

(the structures here are quite nested and complex). As far as I can tell, dagster

ConfigurableResource

should be very similar to this, and likely based on the same pydantic base classes. Now, I would like to turn few of these top-level configs into dagster resources, but I'm not quite sure how to go about that.

So for anything inheriting from basemodel, reasonably sure that you can just inherit instead from

ConfigurableResource

and it will just work. All of the extra resource wrapping / converting to dagster’s config system can just go away. I’m not honestly sure how

BaseSettings

works in comparison to

BaseModel

, but I think it’s worth a more generic treatment / discussion so going to open one

Question in the thread has been surfaced to GitHub Discussions for future discoverability: https://github.com/dagster-io/dagster/discussions/15210