fix: expose updated_replicas for deployment progress and add save feedback #48

Merged
adam merged 1 commit from fix/deployment-progress-indicator into main 2026-02-12 22:26:46 -05:00
Owner

The progress indicator was never visible because the backend sets status
back to RUNNING immediately after the K8s API call. Now we expose
updated_replicas from K8s deployment status so the frontend can detect
in-progress rollouts (updated_replicas < replicas). Also adds
saving/saved state feedback to the edit slideout Save button.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

The progress indicator was never visible because the backend sets status back to RUNNING immediately after the K8s API call. Now we expose updated_replicas from K8s deployment status so the frontend can detect in-progress rollouts (updated_replicas < replicas). Also adds saving/saved state feedback to the edit slideout Save button. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
fix: expose updated_replicas for deployment progress and add save feedback
All checks were successful
CI / test-backend (pull_request) Successful in 27s
CI / test-frontend (pull_request) Successful in 20s
231ae649bc
The progress indicator was never visible because the backend sets status
back to RUNNING immediately after the K8s API call. Now we expose
updated_replicas from K8s deployment status so the frontend can detect
in-progress rollouts (updated_replicas < replicas). Also adds
saving/saved state feedback to the edit slideout Save button.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
adam merged commit 534d24d66c into main 2026-02-12 22:26:46 -05:00
adam deleted branch fix/deployment-progress-indicator 2026-02-12 22:26:46 -05:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Canpute/canpute-ecs!48
No description provided.