Skip to content

Allow redeployment of failed and stuck-upgrading stacks via deploy hook#349

Merged
Wiesenwischer merged 1 commit intomainfrom
bugfix/allow-redeploy-failed-upgrading-stacks
Mar 26, 2026
Merged

Allow redeployment of failed and stuck-upgrading stacks via deploy hook#349
Wiesenwischer merged 1 commit intomainfrom
bugfix/allow-redeploy-failed-upgrading-stacks

Conversation

@Wiesenwischer
Copy link
Copy Markdown
Owner

Summary

  • The deploy hook (POST /api/hooks/deploy) rejected all non-Running deployments, blocking CI pipelines from retrying after a failed deploy (e.g. NuGet error in Dockerfile)
  • Now Failed and stuck Upgrading deployments can be redeployed via the hook
  • Installing and Removed remain non-redeployable
  • The DeploymentService recovers stuck Upgrading status via MarkAsFailedStartRollbackProcess before proceeding with the new deployment

Changed Files

  • DeployViaHookCommand.cs — accept Failed/Upgrading statuses, use "retried" action label
  • DeploymentService.cs — add Upgrading to upgrade detection, recover stuck state
  • DeployViaHookHandlerTests.cs — tests for new redeployable statuses, updated rejection tests

Test plan

  • Unit tests pass (44/44)
  • Build succeeds with 0 errors

The deploy hook endpoint rejected all non-Running deployments, blocking
CI pipelines from retrying after a failed deploy. Now Failed and stuck
Upgrading deployments can be redeployed. Installing and Removed remain
rejected. The DeploymentService recovers stuck Upgrading status via
MarkAsFailed + StartRollbackProcess before proceeding.
@github-actions github-actions bot added the bug Something isn't working label Mar 26, 2026
@Wiesenwischer Wiesenwischer merged commit f2b4846 into main Mar 26, 2026
2 checks passed
@Wiesenwischer Wiesenwischer deleted the bugfix/allow-redeploy-failed-upgrading-stacks branch March 26, 2026 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant