Repository navigation
Task 4401- Report OSM cleanup failure on workspace delete - #151
Conversation
Make workspace deletion resilient to OSM cleanup failures: introduce DeleteWorkspaceResult and change WorkspacesClient.deleteWorkspace to use Promise.allSettled so the API record deletion and the OSM cleanup are attempted in parallel. The method now throws if the primary workspace delete fails and returns { osmRequestSucceeded: boolean } to indicate whether the OSM request succeeded. Update the Delete settings panel to show an informational toast when the workspace is deleted but OSM cleanup failed. Add unit tests for the new delete behavior and an e2e test that asserts the info toast is shown when OSM cleanup returns an error.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
…nction-ci Resolves a conflict in services/workspaces.ts deleteWorkspace: develop's PR #151 (report OSM cleanup failure) and this branch both reworked it. Took develop's version (parallel delete via Promise.allSettled returning DeleteWorkspaceResult), dropped the now-unused OsmApiClientError import, and removed this branch's obsolete OSM-first deleteWorkspace tests from test/unit/services/workspaces-lifecycle.test.ts (develop's workspaces.test.ts already covers the new behavior). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
DevBoard Task
https://dev.azure.com/TDEI-UW/TDEI/_workitems/edit/4401/
Changes implemented
Testing impact
Screenshot

Summary
WorkspacesClient.deleteWorkspacenow deletes the workspace and requests OSM cleanup in parallel. It throws if workspace deletion fails and reports whether OSM cleanup succeeded./dashboard.