From d46468aecde19dfd998ed175910bfb3ee9d2f034 Mon Sep 17 00:00:00 2001 From: Samuel K Date: Sat, 24 Oct 2026 00:14:45 -0600 Subject: [PATCH 1/5] docs(workspaces): correct delete --force provider teardown claim The stop/delete page said --force only removes the workspace on the Devsy side. In pkg/client/clientimplementation/workspace_client.go, force still runs the provider delete command when the workspace is running; it only ignores its errors and skips teardown when the running check fails. --- .../developing-in-workspaces/stop-and-delete-a-workspace.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx index 79487aba22..895c2ca849 100644 --- a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx +++ b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx @@ -43,4 +43,4 @@ If the provider is unreachable, you can force the delete: devsy workspace delete my-workspace --force ``` -This only removes the workspace on the Devsy side and ignores provider errors, so it can leave cloud resources behind. +`--force` skips the status check and ignores errors from provider teardown. If the provider cannot be checked, Devsy skips provider teardown, so provider resources can be left behind. From 590fd01000371753e450784e60a4d36b11083c19 Mon Sep 17 00:00:00 2001 From: Samuel K Date: Sat, 24 Oct 2026 00:34:11 -0600 Subject: [PATCH 2/5] docs(workspaces): scope delete --force teardown wording Name the container and auto-delete machine paths separately. deleteContainer skips teardown when the machine status check fails under force; deleteInstance sends AutoDelete machines to deleteMachine, which logs a failed delete command and continues. --- .../developing-in-workspaces/stop-and-delete-a-workspace.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx index 895c2ca849..652e3fb1c1 100644 --- a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx +++ b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx @@ -43,4 +43,4 @@ If the provider is unreachable, you can force the delete: devsy workspace delete my-workspace --force ``` -`--force` skips the status check and ignores errors from provider teardown. If the provider cannot be checked, Devsy skips provider teardown, so provider resources can be left behind. +`--force` makes provider teardown errors non-fatal in the container and auto-delete machine paths. For container deletion (including machine providers without `autoDelete`), a failed container teardown is logged and ignored, and if Devsy cannot check the machine status it skips the container teardown. For auto-delete machines, a failed machine delete command is logged and the delete continues. Provider resources may remain in these cases. From 86506a917083bb0c82d689288ad6dcaba8aacfa9 Mon Sep 17 00:00:00 2001 From: Samuel K Date: Sat, 24 Oct 2026 00:48:48 -0600 Subject: [PATCH 3/5] docs(workspaces): cover daemon-backed delete under force daemonclient/delete.go deleteInstance logs a failed instance delete and returns nil under force, but waitForWorkspaceDeleted can still return an error. Document that narrowly. --- .../developing-in-workspaces/stop-and-delete-a-workspace.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx index 652e3fb1c1..1131688d5f 100644 --- a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx +++ b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx @@ -43,4 +43,4 @@ If the provider is unreachable, you can force the delete: devsy workspace delete my-workspace --force ``` -`--force` makes provider teardown errors non-fatal in the container and auto-delete machine paths. For container deletion (including machine providers without `autoDelete`), a failed container teardown is logged and ignored, and if Devsy cannot check the machine status it skips the container teardown. For auto-delete machines, a failed machine delete command is logged and the delete continues. Provider resources may remain in these cases. +`--force` makes several provider teardown errors non-fatal. For container deletion (including machine providers without `autoDelete`), a failed container teardown is logged and ignored, and if Devsy cannot check the machine status it skips the container teardown. For auto-delete machines, a failed machine delete command is logged and the delete continues. Daemon-backed workspaces still attempt their instance delete under `--force`; a failed delete request is logged rather than returned, but waiting for deletion can still return an error. Provider resources may remain in these cases. From cd30ac14b92430138b52ef333b05e80b4a46f187 Mon Sep 17 00:00:00 2001 From: Samuel K Date: Sat, 24 Oct 2026 00:50:06 -0600 Subject: [PATCH 4/5] docs(workspaces): clarify container force teardown logging handleForceError ignores non-nil errors under force and logs only errors other than context.DeadlineExceeded. Reword the container clause to match. --- .../developing-in-workspaces/stop-and-delete-a-workspace.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx index 1131688d5f..155cca1c42 100644 --- a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx +++ b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx @@ -43,4 +43,4 @@ If the provider is unreachable, you can force the delete: devsy workspace delete my-workspace --force ``` -`--force` makes several provider teardown errors non-fatal. For container deletion (including machine providers without `autoDelete`), a failed container teardown is logged and ignored, and if Devsy cannot check the machine status it skips the container teardown. For auto-delete machines, a failed machine delete command is logged and the delete continues. Daemon-backed workspaces still attempt their instance delete under `--force`; a failed delete request is logged rather than returned, but waiting for deletion can still return an error. Provider resources may remain in these cases. +`--force` makes several provider teardown errors non-fatal. For container deletion (including machine providers without `autoDelete`), a failed container teardown is ignored, with errors other than a deadline timeout logged, and if Devsy cannot check the machine status it skips the container teardown. For auto-delete machines, a failed machine delete command is logged and the delete continues. Daemon-backed workspaces still attempt their instance delete under `--force`; a failed delete request is logged rather than returned, but waiting for deletion can still return an error. Provider resources may remain in these cases. From 225bdebbb1fb8d1614e0d505bf34215214a2dadd Mon Sep 17 00:00:00 2001 From: Samuel K Date: Sat, 24 Oct 2026 01:10:02 -0600 Subject: [PATCH 5/5] docs(workspaces): scope daemon delete logging to non-NotFound errors daemonclient deleteInstance logs delete request errors under force only when they are not NotFound, then returns nil. Reword the daemon clause to match. --- .../developing-in-workspaces/stop-and-delete-a-workspace.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx index 155cca1c42..1939d34c41 100644 --- a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx +++ b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/stop-and-delete-a-workspace.mdx @@ -43,4 +43,4 @@ If the provider is unreachable, you can force the delete: devsy workspace delete my-workspace --force ``` -`--force` makes several provider teardown errors non-fatal. For container deletion (including machine providers without `autoDelete`), a failed container teardown is ignored, with errors other than a deadline timeout logged, and if Devsy cannot check the machine status it skips the container teardown. For auto-delete machines, a failed machine delete command is logged and the delete continues. Daemon-backed workspaces still attempt their instance delete under `--force`; a failed delete request is logged rather than returned, but waiting for deletion can still return an error. Provider resources may remain in these cases. +`--force` makes several provider teardown errors non-fatal. For container deletion (including machine providers without `autoDelete`), a failed container teardown is ignored, with errors other than a deadline timeout logged, and if Devsy cannot check the machine status it skips the container teardown. For auto-delete machines, a failed machine delete command is logged and the delete continues. Daemon-backed workspaces still attempt their instance delete under `--force`; delete request errors other than NotFound are logged and do not stop deletion, but waiting for deletion can still return an error. Provider resources may remain in these cases.