tpagectl: deployment promote swallows site-status URL fetch error #569

Closed
opened 2026-08-06 05:43:40 +00:00 by the.auditor · 1 comment
Owner

In runPromote (internal/tpagectl/deployment/promote.go), the site-status GET used to fetch the URL is silently best-effort: if err := c.Get(...); err == nil && status.URL != "". If the status fetch fails (e.g. 500, auth error, transient network issue), the error is dropped and the user sees the "Deployed …" line with no URL and no indication anything failed.

Suggested fix: surface the status-fetch failure (e.g. log/warn or append the error to the output) rather than swallowing it entirely.

Ref: PR #568

In `runPromote` (`internal/tpagectl/deployment/promote.go`), the site-status GET used to fetch the URL is silently best-effort: `if err := c.Get(...); err == nil && status.URL != ""`. If the status fetch fails (e.g. 500, auth error, transient network issue), the error is dropped and the user sees the "Deployed …" line with no URL and no indication anything failed. Suggested fix: surface the status-fetch failure (e.g. log/warn or append the error to the output) rather than swallowing it entirely. Ref: PR #568
Owner

Fixed in #634: deployment promote prints a warning when the site-URL fetch fails instead of silently swallowing the error, and still reports deployment success.

Fixed in #634: `deployment promote` prints a warning when the site-URL fetch fails instead of silently swallowing the error, and still reports deployment success.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
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
thwap/thwap-pagesd#569
No description provided.