Simple question but how do we include op inputs in...
# ask-community
t
Simple question but how do we include op inputs in RunConfig. e.g.
Copy code
from dagster import Config, RunConfig, config_mapping, job, op


class DoSomethingConfig(Config):
    config_param: str


@op
def do_something(context, config: DoSomethingConfig, test: str) -> None:
    <http://context.log.info|context.log.info>("config_param: " + config.config_param + test)


class SimplifiedConfig(Config):
    simplified_param: str
    test: str


@config_mapping
def simplified_config(val: SimplifiedConfig) -> RunConfig:
    return RunConfig(
        ops={"do_something": DoSomethingConfig(config_param=val.simplified_param)}
    )


@job(config=simplified_config)
def do_it_all_with_simplified_config():
    do_something()
how can we get the value of test to do_something. I thought i could just do this and it would work but it doesn't seem like it.
Copy code
class SimplifiedConfig(Config):
    simplified_param: str

@job(config=simplified_config)
def do_it_all_with_simplified_config(test):
    do_something(test)
🤖 1
y
here’s how you can provide the config value to a job in an ad-hoc run: https://docs.dagster.io/concepts/configuration/config-schema#python
in your case, you’d define something like:
Copy code
class SimplifiedConfig(Config):
    simplified_param: str

@op
def do_something(config: DoSomethingConfig) -> None:
    print(config) # config value

@job
def do_it_all_with_simplified_config(): # note that job doesn't take inputs
    do_something()
t
It turns out the answer for me was that simplified_config mapping can return a dict with a key called 'inputs'. rather than a RunConfig object
👍 1