Follow-up to #280.
PR #280 explains when a running sync is waiting for a resource carrying Prune=confirm, but Argonaut still cannot approve that deletion. Users must leave the TUI and run argocd app confirm-deletion or use the Argo CD Web UI.
Add an action to the sync-status pane that confirms the pending prune deletion through the Argo CD API.
Acceptance criteria:
- Show a confirmation action only when the operation is genuinely waiting on prune confirmation.
- Require an explicit destructive-action confirmation before approving deletion.
- Confirm the pending deletion for the correct application and namespace.
- Surface success and API errors in the TUI.
- Refresh or watch the operation so the pane reflects the resumed sync.
- Cover visibility, cancellation, request construction, success, and failure with tests.
The detection and explanatory status added by #280 should be reused rather than independently inferred.
Follow-up to #280.
PR #280 explains when a running sync is waiting for a resource carrying
Prune=confirm, but Argonaut still cannot approve that deletion. Users must leave the TUI and runargocd app confirm-deletionor use the Argo CD Web UI.Add an action to the sync-status pane that confirms the pending prune deletion through the Argo CD API.
Acceptance criteria:
The detection and explanatory status added by #280 should be reused rather than independently inferred.