dagsterApiGrpcArgs

in Kubernetes configuration is unable to load multiple repositories or from

workspace.yaml

. How do I solve this? I tried doing this:

dagsterApiGrpcArgs:
        - "-p"
        - "3030"

but no repository is loaded. If I do this:

dagsterApiGrpcArgs: []

throws error due to extra args (). If I do this:

- "-m"
        - "team_checkpoint.repo"
        - "-m"
        - "leanpd_notion.repo"

only the last repo is loaded. Additionally:

Try 'dagster api grpc -h' for help.

But if I run that, I get:

Error: Option '-h' requires an argument.

Dagster version: 0.14.19

Hi Hendy - each server takes in a single entry point that can either be a file or a module. That entry point can absolutely import repositories from other modules though. So you could have a single module that imports from both team_checkpoint.repo and leanpd_notion.repo and use that module as the one that you pass in

Thank you @daniel, so that means

workspace.yaml

is not used at all by

grpc api

?

that's right - workspace.yaml can point at a gRPC server if it has a

grpc_server

key in it: https://docs.dagster.io/concepts/repositories-workspaces/workspaces#running-your-own-grpc-server

Thank you @daniel . I have to say that Dagster itself as software is awesome . However, navigating the docs is still challenging, and there are patterns that are still unclear. I hope this benefits other people: my current pattern that works and structured well, is having a `workspace.py`:

from team_checkpoint.repo import *
from leanpd_notion.repo import *

Then putting this in the Helm config:

dagsterApiGrpcArgs:
        - "-m"
        - "workspace"
      port: 3030

totally hear you on the docs front! Adding more examples and clarifying things is a big focus for us right now. The main reason you would want to have more than one entry in your workspace.yaml is if there are two different images or Python environments, or you want to update and deploy things separately