Skip to content

fix(api): align v2 contracts and pagination - #3168

Merged
wklken merged 3 commits into
TencentBlueKing:masterfrom
wklken:fix_v2_apis_0813
Aug 13, 2026
Merged

fix(api): align v2 contracts and pagination#3168
wklken merged 3 commits into
TencentBlueKing:masterfrom
wklken:fix_v2_apis_0813

Conversation

@wklken

@wklken wklken commented Aug 13, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • align V2 Swagger metadata, gateway resource definitions, and API docs with runtime contracts
  • standardize V2 list responses on count and results
  • apply real limit/offset pagination to resource versions, MCP permission records, and released resources
  • keep externally paginated request logs on the same response envelope
  • add contract and regression coverage for the affected endpoints

Verification

  • uv run make lint-check
  • uv run make test (3856 passed)
  • focused V2 pagination and contract tests (10 passed)

wklken added 3 commits August 13, 2026 16:21
Correct response status codes, request serializers, and collection shapes in
Swagger metadata, registered gateway resources, and API documentation.

Add contract tests covering the affected sync and MCP permission endpoints so
future schema drift is detected without changing runtime behavior.
Why this change was needed:
Several V2 list endpoints exposed inconsistent response envelopes or advertised pagination parameters without applying them.

What changed:
- Standardize V2 list responses on count/results
- Apply limit/offset pagination after MCP record deduplication and to released resources
- Synchronize runtime schemas, gateway definitions, documentation, and regression tests

Problem solved:
V2 list clients now receive a consistent pagination contract and pagination parameters affect the returned page.
@wklken
wklken merged commit 12fd402 into TencentBlueKing:master Aug 13, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant