Skip to content

feat: API Server - User Pipelines - Support storing user pipelines on the backend server#181

Open
Ark-kun wants to merge 1 commit intomasterfrom
ark/feat--API-Server---User-Pipelines---Support-storing-user-pipelines-on-the-backend-server
Open

feat: API Server - User Pipelines - Support storing user pipelines on the backend server#181
Ark-kun wants to merge 1 commit intomasterfrom
ark/feat--API-Server---User-Pipelines---Support-storing-user-pipelines-on-the-backend-server

Conversation

@Ark-kun
Copy link
Contributor

@Ark-kun Ark-kun commented Mar 19, 2026

We store not just the pipeline itself (ComponentSpec), but also the pipeline arguments (TaskSpec) and even pipeline run annotations.

Routes:

  • GET /api/users/me/pipelines/all
  • GET /api/users/me/pipelines/?file_path=...
  • PUT /api/users/me/pipelines/?file_path=...
  • DELETE /api/users/me/pipelines/?file_path=...

Closes #168

… the backend server

We store not just the pipeline itself (`ComponentSpec`), but also the pipeline arguments (`TaskSpec`) and even pipeline run annotations.

Routes:
* GET `/api/users/me/pipelines/all`
* GET `/api/users/me/pipelines/?file_path=...`
* PUT `/api/users/me/pipelines/?file_path=...`
* DELETE `/api/users/me/pipelines/?file_path=...`

Closes #168
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: Support storing user pipelines on the backend server

2 participants