subclasses to define a common set of parameters for our ETL jobs including nice descriptions. However, not all flows use all parameters. Is there any way to exclude some parameters from being considered on the fly? Something like defining an
exclude
list??
Jacob Blanco
03/10/2025, 9:13 AM
Just for anyone stumbling into this we ended up making a function that builds a BaseModel on the fly using the pydantic functional API.
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.
