I m trying to figure out how to pass a parameter to an `op`

Question

I m trying to figure out how to pass a parameter to an `op` within a `job` I m trying to follow this one <https docs dagster io concepts io management unconnected inputs loading a built in dagster type from config> But when I run dagit it still require me to add configs Actually what I m looking for is a way to have an `op` that takes a parameter a string and then pass that parameter to the `op` from a `job`

Martin Carlsson · Answer

Technically I want to do something like this

Martin Carlsson · Answer

Of cause I can do this but it seems a bit ugly

Jordan W · Answer

you need a run config <https docs dagster io concepts configuration config schema>

Martin Carlsson · Answer

< Jordan W> how do I add that to the code

Jordan W · Answer

This is the<https docs dagster io concepts configuration config schema config schema| relevant spot in the docs>

Jordan W · Answer

what you would need is ``` op config schema= input string str def my op context in string = context op config input string ```

Martin Carlsson · Answer

< Jordan W> ok but how to I supply the parameter to the `op` within the `job`

Martin Carlsson · Answer

How should I write my `job`

Jordan W · Answer

that depends where you are executing the job

Jordan W · Answer

in code dagit or on the cli

Martin Carlsson · Answer

All of them I want to define the input im my code so it can run from the cli dagit and later maybe via the python api

Martin Carlsson · Answer

From the link what I want is to add a parameter here

Martin Carlsson · Answer

I am able to do this

Martin Carlsson · Answer

But not this

Jordan W · Answer

a job doesnt allow for any hard coded values in an `op` s parameters Everything parameter within a job needs to be a result from a previous solid in your case with your first solid requiring a parameter that would be done through the run config

daniel · Answer

Martin you might find this example useful you can specify default config on the job which could help here <https docs dagster io concepts ops jobs graphs jobs graphs hardcoded configuration>

Martin Carlsson · Answer

< Jordan W> < daniel> thanks a lot for the help I m now 99 sure that the way I m building my program is subpar and there is a good reason for ops in jobs don t take string parameters Does anyone know why this is I mean why Dagster doesn t allow this

Alex Saltzman · Answer

I m new here but my guess is Dagster is designed the way it is to remain modular and flexible with minimal no changes necessary to the actual op job code logic when you simply are changing inputs