Helps with less verbose testing story; people don't have to call .hardcoded_resource or .hardcoded_io_manager. Probably going to consolidate this implementation with that from build_resources.
I'm not sure I have a strong stance on this one
- the deferred construction pattern of resource_defs is good in a lot of situations, not a bad "pit of success"
- taking instances directly is good for ramp up, simple cases, and pretty user friendly
I could go either way
I had originally been a strong proponent of this, but, having reviewed the resources in our dogfood pipelines, I'm less sure. It's only really the IOManagers that would benefit from this. I wonder if it would make more sense to just make it a little less verbose to make a hardcoded resource. Right now it requires ResourceDefinition.hardcoded_resource. We could make hardcoded_resource a top-level API?