The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Did the graphql interface change between v0.15.9 and v1.1.21?

Upgrading dagster seems fine but some of our services can’t upgrade `dagster-graphql` yet due to conflicting graphql deps. I wonder if its okay to keep the version mismatch for a lil while.

We don’t recommend that you keep a version mismatch between dagster, dagit, and dagster-graphql. These should all be in lockstep.

`dagster-graphql` should only be required in `dagit`, which should be a standalone service, assuming that you’ve deployed your code servers separate from the Dagster UI server

we’re using the interfaces to call dagster’s graphql from another service :sweat:

we might move towards a graphql call without using the graphql lib tho

Even then, your external service shouldn’t need `dagster-graphql` to make a GraphQL request to the Dagster UI server?

We do use it tho. Example:

```from dagster_graphql import DagsterGraphQLClient

client = DagsterGraphQLClient(config.DAGIT_HOSTNAME, port_number=config.DAGIT_PORT)
job = "job_name"
client.submit_job_execution(
    job,
    repository_location_name="main",
    run_config={
        "inputs": {
            &lt;redacted&gt;
        },
        "execution": {
            "config": {
                "max_concurrent": 1,
            }
        },
    },
)```

ahh you’re using the python client, i see

yeah, if you want to excise this dependency, you would need to switch to raw graphql queries

we might do that instead of upgrading flask graphql for now :sweat:

Hey <@U03B5BSSGJU> , can I ask you if you have deployed dagster on k8s? I have written graphql code within the dagster code and am trying to connect to dagit but it's not connecting. I am using the IP of the pod where dagster-dagit is being served.. do you have any pointers?

<@U01AV4K3W14> could you weigh in if you have any pointers..?

We had no issue connecting to dagit on ECS using the service discovery feature :disappointed:

I got it working. Was using the wrong port. Should have removed my comment.

Thanks so much though!