Hi, I am having trouble trying to supply config to a graph-backed asset. Here's my contrived example again, but with config on the 2nd op ("op2"):

@op
def op1():
    return "Some string"


@op(
    config_schema={
        "name": str
    }
)
def op2(context, dummy_str: str):
    print(dummy_str)
    return f"Hello {context.op_config['name']}"


@graph(
    out={
        "asset_from_op2": GraphOut()
    }
)
def test_graph():
    asset_from_op2 = op2(op1())

    return {"asset_from_op2": asset_from_op2}

test_asset = AssetsDefinition.from_graph(test_graph, group_name="test_asset")


@repository
def test_repo():
    return [
        [
            test_asset,
            define_asset_job(
                name="test_asset_job",
                config={
                    "ops": {
                        "test_graph": {
                            "ops": {
                                "op2": {
                                    "config": {
                                        "name": "Daniel"
                                    }
                                }
                            }
                        }
                    }
                }
            ),
        ],
    ]

I run dagit and dagit launches fine. But when I try to materialize this, I get this error:

test_asset_job cannot be executed with the provided config. Please fix the following errors:

Missing required config entry "ops" at the root. Sample config for missing entry: {'ops': {'test_graph': {'ops': {'op2': {'config': {'name': '...'}}}}}}

Been struggling trying to nail down what I'm doing wrong with the config entry. Any help appreciated!

you don't need to nest into the graph to enter config, you should be good using this:

{
  "ops": {
    "op2": {
      "config": {
        "name": "Daniel"
      }
    }
  }
}

@jamie That's what I actually had originally and back then it gave me this error message:

test_asset_job cannot be executed with the provided config. Please fix the following errors:

Missing required config entry "ops" at the root. Sample config for missing entry: {'ops': {'test_graph': {'ops': {'op2': {'config': {'name': '...'}}}}}}

That's a good tip about removing the config entry! But I'll have to unmaterialize or delete the pickle object to force the scaffolding. It isn't scaffolding anymore I'm guessing because it was materialized earlier.

that's odd that it isn't scaffolding. not the behavior i would expect. I'll see if i can replicate. I'll also try replicating the config error. i would expect the config i gave to work for a normal job, but maybe there's something going on when it turns into an asset. I'll get back to you

Hmm, strange, so the scaffolding is showing me that I had to double nest:

does that config work when you materialize?

Yup! So not sure why my code example above is throwing that error.

yeah i'm pretty confused now too. working on a replication now

@jamie Yup, that worked.

ok, pretty sure it's a UI bug. I'll raise an issue

Sorry, one more quick question. So is the double nested ops entries the "right" or expected config?

i agree that double nested "ops" is a bit strange. It is correct though. I'm asking some folks more familiar with graph backed assets if this is intentional or a possible bug

@jamie Well thank you so much for helping me and for being patient with my wacky contrived examples! I currently don't have access to heavy-weight infra so I am basically learning SDA features via these simple contrived examples that I can come up with.

no worries! happy to help out!