dagster
dagster copied to clipboard
dagster-io
RFC (more like dump prototype) Typed resource ctor:
This is more of a pattern rather than real technology. I banged this out very quickly so it is not fleshed out. The idea here is to make it norm to provide typed constructors for resources as opposed to configured. The configurable resource is still available for advanced cases.
The big drawback here is that this breaks direct resource invocation. However I think for the spin-up/simple use case this is far more self-explantory.
Additionally a natural extension would be to generate config schema from the python types on the typed signature if that is desirable.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Ignored Deployments
| Name | Status | Preview | Updated |
|---|---|---|---|
| dagit-storybook | ⬜️ Ignored (Inspect) | Sep 21, 2022 at 4:49PM (UTC) | |
| dagster | ⬜️ Ignored (Inspect) | Sep 21, 2022 at 4:49PM (UTC) | |
| dagster-oss-cloud-consolidated | ⬜️ Ignored (Inspect) | Sep 21, 2022 at 4:49PM (UTC) |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
To point it out explictly, the level of indirection is so that existing callsites that call configured still work
The big drawback here is that this breaks direct resource invocation. However I think for the spin-up/simple use case this is far more self-explantory.
Is there a fundamental reason it needs to break direct resource invocation?
