a2e5b2d67d
Prevent deployment status from regressing to FAILED after it's marked as FINISHED by: 1. Calling completeDeployment() first in post_deployment() before any operations that could fail 2. Wrapping all post-deployment side effects in try-catch blocks 3. Adding FINISHED to terminal states that cannot be changed 4. Protecting ExecuteRemoteCommand from overwriting FINISHED status This fixes the issue where a deployment with a healthy container and successful rolling update was still marked as Failed in the UI. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| AuthorizesResourceCreation.php | ||
| CalculatesExcludedStatus.php | ||
| ClearsGlobalSearchCache.php | ||
| DeletesUserSessions.php | ||
| EnvironmentVariableAnalyzer.php | ||
| EnvironmentVariableProtection.php | ||
| ExecuteRemoteCommand.php | ||
| HasConfiguration.php | ||
| HasNotificationSettings.php | ||
| HasSafeStringAttribute.php | ||
| SaveFromRedirect.php | ||
| SshRetryable.php | ||