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

dagster

Hello Dagster - I'm having real trouble figuring out how to serve a single grpc server against two code locations - one a repository file - and a second a Definition type file... when serving Dagit locally I can see the two being served - but it doesn't look like the dagster api grpc command can serve two files.  Any help?  I can't seem to mix old style repo with def style code locations with grpc currently.

(Disclaimer: I’m still using repositories)
I did see this post earlier in the week and saved it for when I get around to transitioning to definitions - might be useful? <https://dagster.slack.com/archives/C01U954MEER/p1684878796973119|https://dagster.slack.com/archives/C01U954MEER/p1684878796973119>

Ahh - so you create repo from a Def - that does help - I'll give that a try.

LOL
```ExperimentalWarning: "create_repository_using_definitions_args" is an experimental function. It may break in future versions, even between dot releases. To mute warnings for experimental functionality, invoke warnings.filterwarnings("ignore", category=dagster.ExperimentalWarning) or use one of the other methods described at <https://docs.python.org/3/library/warnings.html#describing-warning-filters>.```

That’s not uncommon with new APIs in dagster. I’ve used many of those in my user code without issue. Just read release notes carefully when doing upgrades - anything labeled experimental can change at anytime. I think the most I had to do was change arguments for a function once.