Hi, Just curious, is there any way using which once can easily create repository dynamically in Dagster?

could you elaborate a little here about the feature and use case

I already have a workspace.yaml, running in a docker image with me, which contains the repositories' python file location in it. There are 4 repositories as of now DS_1, DS_2, DS_3, DS_4 (DS:- Data Source). Now, imagine there is a new DS to be added say DS_5. I don't want to make changes in the project structure then commit those changes and redeploy, what I want is, if I upload the DS_5's python file at some some location and refresh the Dagster's workload space, then repository of DS_5 should be visible on the UI.

This isn’t directly supported by Dagster currently. There are possibilities of using some CD pipeline that would run a redeploy to get a similar result. But I’m curious- if you don’t want to make a commit, where is the new python code coming from for the repository?

We can use the package approach, in that scenario.