Repository navigation
Open
Description
Summary
Building the ovh provider (stackql-registry/stackql-provider-ovh: 88 pinned OpenAPI documents, 7,313 operations, 98 services) against stackql v1.0.888 turned up four gaps in omnisdk. Each is filed there with its evidence and a proposed contract. This issue tracks the host side: taking the omnisdk release that carries them and wiring, documenting and regression-testing each through SQL.
| omnisdk issue | Gap | What it blocks in the provider |
|---|---|---|
| stackql-labs/omnisdk#56 | OVHcloud application key request signing (ovh_signing_v1) |
AK/AS/CK credentials (OVH_APPLICATION_KEY, OVH_APPLICATION_SECRET, OVH_CONSUMER_KEY); the provider ships with the OAuth2 client credentials grant only |
| stackql-labs/omnisdk#57 | Pagination tokens carried in a response header | 277 API v2 and 5 API v1 list reads return their first page only (X-Pagination-Cursor-Next -> X-Pagination-Cursor) |
| stackql-labs/omnisdk#58 | No snake_case alias for a parameter name containing a dot | WHERE date_from = ... fails; "date.from" must be quoted (25 names, 30 operations) |
| stackql-labs/omnisdk#59 | Ordered auth alternatives in a provider document | one document cannot offer the OAuth2 grant, a pre-issued token and (once #56 lands) application keys without --auth |
Host work per item
Request signing (omnisdk#56)
- Accept
ovh_signing_v1and its keys in the--authJSON (internal/stackql/runtimeconfig/auth_ctx.goand theomnisdk.AuthConfigit feeds), inline values and environment variable names. - Credential handling: the three values and the
X-Ovh-Signatureheader are secrets in logs, in the MCP credential report (reload_credentialsreports names and status only) and in session storage. docs/auth.mdand the README auth section: the new type and its variables.- Robot: a mock that recomputes the signature from the method, URL, body and timestamp it receives and rejects a mismatch, exercised by SELECT (query string signed), INSERT and UPDATE (body signed) and DELETE; a mocked
/auth/timewith a non-zero delta.stackql_oci_auth.robotis the nearest existing shape.
Header-carried pagination tokens (omnisdk#57)
- No host code expected beyond the omnisdk bump.
- Robot: add to
stackql_rest_pagination.robota two-page fixture where page 1 answers with a cursor response header and page 2 is requested with it as a request header; assert both pages' rows and exactly two requests; assert--http.response.pageLimitstill bounds it. A Link-header case must be unchanged.
Dotted parameter aliases (omnisdk#58)
- Robot: add to
stackql_casing.robota query parameter nameddate.fromon anativeCasing: camelmethod;WHERE date_from = ...reaches the wire as?date.from=..., andSHOW METHODS/DESCRIBEreport the snake name.
Auth alternatives (omnisdk#59)
- Precedence:
--authand a session alias credential replace the whole declaration (as they replaceconfig.authtoday); document it next to the existing note that a runtime credential bypassesconfig.auth.variables. - Surface which method a session selected, by kind only:
SHOW PROVIDERSor the MCPserver_info/reload_credentialsreport. - The credential resolution error names every alternative and the variables it looked for, so the "ask the operator, then reload" loop the MCP instructions describe has something precise to ask for.
- Robot: the selection, partial and none-complete cases through
stackql exec.
After the release
The provider picks these up with rule changes only (provider-dev/config/provider_config.json for auth, a document-level pagination block for the v2 services), then make build && make test.
Metadata
Metadata
Assignees
Labels
No labels
Activity