Skip to content

fix!: do not create provisioner job for orphan delete #18460

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

johnstcn
Copy link
Member

@johnstcn johnstcn commented Jun 19, 2025

Fixes #18080

NOTE: calling this out as a breaking change so that it is highly visible in the changelog.

This modifies wsbuilder to no longer create a workspace build when orphan is set.
As a consequence of this, POST /api/v2/workspaces/{id}/builds will return a 204 No Content when a workspace is successfully deleted with the --orphan option.

@johnstcn johnstcn self-assigned this Jun 19, 2025
@johnstcn johnstcn changed the title fix(coderd): do not create provisioner job for orphan delete fix!(coderd): do not create provisioner job for orphan delete Jun 19, 2025
@johnstcn johnstcn added the release/breaking This label is applied to PRs to detect breaking changes as part of the release process label Jun 19, 2025
@johnstcn johnstcn changed the title fix!(coderd): do not create provisioner job for orphan delete fix!: do not create provisioner job for orphan delete Jun 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release/breaking This label is applied to PRs to detect breaking changes as part of the release process
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Deleting workspaces with no matching provisioner is convoluted
1 participant