https://dagster.io/ logo
Join Slack
Powered by
Hey guys! I've switched to the new `Definitions` ...
# ask-community
d
Hey guys! I've switched to the new 
Definitions
API (the code is much cleaner now!), but my Dagster deployment is not loading them for some reason. I have 2 code locations which I'm accessing via the gRPC API. The containers don't have any suspicious logs. Everything works fine when starting 
dagit
locally in the code locations repos. I'm using the 
pyproject.toml
config. What can cause this problem?
s
Can you provide more information about how your deployment is configured?
d
Everything is running in docker containers on a single host. I have 3 deployments: 1. code location 1 2. code location 2 3. Main Dagster deployment I'm using the gRPC API to connect them. It was working fine until the transition from 
repository
to 
Definition
.
Here is the 
workspace.yaml
:
Copy code
load_from:
  - grpc_server:
      host: dagster-code-fetcher
      port: 4000
      location_name: Fetcher
  - grpc_server:
      host: dagster-code-afi
      port: 4001
      location_name: AFI
and here is the command that launches the API:
Copy code
command: ["dagster", "api", "grpc", "-h", "0.0.0.0", "-p", "4000"]
thinking about it again... maybe it ignores the code location in 
pyproject.toml
? at least it doesn't crash but maybe there is a bug that just ignores it...
Yep! That's the case! Seems like the 
dagsterapi grpc
doesn't read the 
[tool.dagster]
config from 
pyproject.toml
by default, unlike 
dagit
.
s
Ah just getting back to this. @Daniel Gafni thanks for the looking into this. I’ll look into supporting this. In the mean time can you use the 
-m
or 
-f
flags to workaround
d
thanks! that's what I did
6 Views
Open in Slack
PreviousNext
Powered by