everything I’ve found on deployment so far has a (hardcoded) coupling from the dagit/dagster deployment back to the repositories that are supposed to be running - which means that a central “infra team” would have to redeploy each time another team would like to add a project. Is that the case?

Yes your understanding is correct. currently we don’t have support to auto-discover new grpc user code deployments from dagit. https://github.com/dagster-io/dagster/issues/4411 is one idea to solve for this

Got it, thanks! The operator route would be nice, but for corporates it’s also tricky to get past platform teams ;) alternatively, you could allow for the config to be stored in the database, and allow creation of new repos through an api :) ah well, for now PRs should work just fine :) thanks for the quick reply, much appreciated!