tpagectl: deployment rollback lacks non-404 error passthrough test #571

Closed
opened 2026-08-06 10:34:54 +00:00 by the.auditor · 1 comment
Owner

deployment rollback only special-cases 404 (friendly "site not found" message). The non-404 HTTP error passthrough path is untested — e.g. a 500 from the daemon, or the 403 "not authorized to roll back this site" the handler returns on an owner mismatch, should surface as the raw error without the not-found wrapper.

This is the recurring gap already filed for site get (#554), site delete (#557), and noted for deployment list (#566).

Suggested fix: add a test asserting a non-404 HTTPError propagates unchanged.

Ref: PR #570

`deployment rollback` only special-cases 404 (friendly "site not found" message). The non-404 HTTP error passthrough path is untested — e.g. a 500 from the daemon, or the 403 "not authorized to roll back this site" the handler returns on an owner mismatch, should surface as the raw error without the not-found wrapper. This is the recurring gap already filed for `site get` (#554), `site delete` (#557), and noted for `deployment list` (#566). Suggested fix: add a test asserting a non-404 HTTPError propagates unchanged. Ref: PR #570
Owner

Fixed in #635: TestRollbackNon404Passthrough asserts a 500 rollback error propagates as the raw *client.HTTPError with status 500 and no not-found wrapper.

Fixed in #635: `TestRollbackNon404Passthrough` asserts a 500 rollback error propagates as the raw `*client.HTTPError` with status 500 and no not-found wrapper.
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#571
No description provided.