This repository was archived by the owner on Oct 2, 2025. It is now read-only.
Automatically create a project when a workflow is run #912
Description
There are a couple issues with the GenSX local dev loop:
- All traces from when you run locally go to default/default, even if you have a project deployed making local traces hard to find and separated from the rest of the project
- If you are using an app with storage (particularly vector search) you have to create a project/env before you can use vector search which makes the dev loop less seamless
To solve these problems, I propose the following:
- When you run a workflow, we look for the project name from the GenSX yaml file and if the project doesn't exist we create it with the "default" environment. We won't deploy to the project, just create it to hold the traces and storage.
- If there is no gensx.yaml, we will just send the trace to default/default still
- Traces from local runs always go to the "default" env of the project. We could read what the selected environment is from the CLI but that approach would be problematic because it will be easy for users to get confused about where traces are going. For example, if they deploy to prod and then run the workflow locally, the trace would go to prod because that env would be auto-selected after deployment
Alternatives:
- We could always have traces from local runs go to a "local" environment so it's fully separate from any deployed project.
- We could come up with some method to give users control over which env local traces go to while having a reasonable default. not quite sure what this would be (workflow opts or dev server param?)