Hey y'all, I recently switched from using a repository to definitions for setting up all my dagster assets, sensors, and jobs. So far so good running locally. However I deploy to kubernetes in our staging environment (this project isn't in production quite yet). There used to be a workspace.yml file that specified the port that was used for communication between dagit and dagster and this is removed when using defintions. Is there anything I need to change to make sure those two can communicate in k8? Or is that already handled since I'm using the helm chart? In the values.yaml for helm there's a section that looks like this I've been using during deployment to get the usercode stuff to talk to dagster/dagit:

dagsterApiGrpcArgs:

- "--python-file" - "hq_dagster/repository.py" - "--working-directory" - "/opt/dagster/app" - "-h" - "0.0.0.0"

Hi Jayme - no changes should be required here. (There's actually still a workspace.yaml under the hood here, but it's entirely managed by the Helm chart)

Thanks @daniel in my config code above there's a reference to the repository.py which no longer exists. What would you recommend I change with that? Appreciate your help as always.

Is there a new file or module that you can reference instead?

I followed some examples in the issues for when the repository to definitions change was made. This recommended putting the definitions file in a module initialization file containing the usercode assets of the source. In my case

hq_dagster/__init__.py

When you run this code locally, what command do you run?

dagster dev -p 9000

What's in your pyproject.toml?

[build-system] requires = ["setuptools"] build-backend = "setuptools.build_meta" [tool.dagster] module_name = "hq_dagster"

This should work then:

dagsterApiGrpcArgs:
          - "--module-name"
          - "hq_dagster"
          - "--working-directory"
          - "/opt/dagster/app"
          - "-h"
          - "0.0.0.0"

Sweet. Thanks man! I'm sure y'all are planning it, but maybe a doc topic on how to convert from repositories to definitions in the helm/deployment area would help here. Not sure how many people are doing k8 though. Python is one of the languages I have less experience with so some of this stuff may be elementary to more people though.

absolutely, i can pass that along to our docs hit list

I am also using Helm, but I have multi module repo, is it possible to pass in multiple

--module-name

arguments to the

dagsterApiGrpcArgs

?

It's not currently possible to specify multiple modules to a gRPC server - that's a limitation of the underlying command, not the Helm chart

right that’s what I am doing but that would mean I have to keep using repositories and not use the new

Definitions

Oh i see - right now you can only have one Definitions object per code location. If you want multiple repositories, our recommend is to keep using repository, there are no plans to remove it

oh.. interesting.. yes that might be worthwhile switching to it

I don't think currently - I expect that to work for quite some time