Barry Sun06/03/2022, 5:47 AM
jamie06/03/2022, 2:40 PM
your run config would look like this
or the equivalent in python dictionary form if that's how you're specifying config
resources: io_manager: config: base_dir: "new/path"
Barry Sun06/06/2022, 6:11 AM
jamie06/06/2022, 4:01 PM
call is throwing the error, which would make me believe that
isn't being properly set in your
It might be useful to throw a couple print statements in your init to make sure the value from config is getting passed through and set as an instance variable as expected
Barry Sun06/07/2022, 12:22 AM
like so. I'll give the print statements a go too!
? I've also seen config being supplied to resources via i)
and ii) supplying the config as you did. I wonder when is the right time to use each one?
jamie06/07/2022, 2:12 AM
in all cases and be fine (i haven't confirmed this everywhere but i'm pretty sure it's true). it's likely a naming discrepancy in our documentation, or a naming choice to indicate that it's the context passed when the resource is initialized (feature or bug ¯\_(ツ)_/¯ ) as for the
API, it provides another way to provide config to a resource in code. so it may be that for a certain job you always want
API allows you to specify it in code once and never have to deal with it again. providing run config via the dagit UI allows you to modify config more "on the fly" and update values for every run of a job. you may have already found this documentation, but the opening sections do a pretty good job going over cases when you might want to use
Barry Sun06/07/2022, 3:46 AM