riposte-marketplace

Files

T

f3nris ed56523b07 fix(ovhcloud): treat the billing-account list as advice, never as a verdict (1.2.6)

The listing now answers 200 with an empty array rather than erroring, and the
probe failed on "not one of the accounts these credentials can see" — the same
mistake as 1.2.4, in its other shape: a diagnostic step deciding the outcome of
the test it exists to explain.

OVH's IAM filters what you may SEE rather than refusing you, so an empty list is
how it says no — and a policy can grant a resource without granting the route that
enumerates it, which makes "not in the list" weak evidence either way. Only the
account-scoped routes decide now.

When nothing is reachable anywhere, the message names the IAM policy as the cause
and says what to grant, because an empty array is the least self-explanatory
refusal this API produces.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TN1R4EnNFUV2Xwtd9q98tj

2026-09-19 19:29:09 +00:00

get_account.py

fix(ovhcloud): use the API endpoint as configured, for both schemes (1.2.5)

2026-09-19 19:26:02 +00:00

get_dedicated_server.py

fix(ovhcloud): use the API endpoint as configured, for both schemes (1.2.5)

2026-09-19 19:26:02 +00:00

get_oncall_ladder.py

fix(ovhcloud): use the API endpoint as configured, for both schemes (1.2.5)

2026-09-19 19:26:02 +00:00

list_calls.py

fix(ovhcloud): use the API endpoint as configured, for both schemes (1.2.5)