zyratlo opened a new issue, #7131: URL: https://github.com/apache/texera/issues/7131
### Task Summary There is no way to delete a workflow's stored notebook and its workflow-to-notebook mapping from the backend. The notebook-migration service can store and fetch a notebook for a workflow (`store-notebook-and-mapping`, `fetch-notebook-and-mapping`), but once stored, a notebook and its mapping stay in the database with no endpoint to remove them. When a user closes or discards a migrated notebook, the persisted rows are left behind. There is no server-side operation for the frontend to call to clear them. This blocks the end-to-end notebook deletion flow: the close-panel path needs a backend endpoint it can call to remove a workflow's notebook before it can reset the UI state that reflects whether a notebook exists. We need a single backend endpoint that, given a workflow, removes its stored notebook and the associated mapping, enforces write access to the workflow, and is safe to call when nothing is stored. ### Task Type - [x] Refactor / Cleanup - [ ] DevOps / Deployment / CI - [ ] Testing / QA - [ ] Documentation - [ ] Performance - [ ] Other -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
