chore(spec): refresh bundled cloud_openapi.json from upstream#101
Merged
Conversation
Re-fetched `tests/fixtures/cloud_openapi.json` from `https://api.redislabs.com/v1/cloud-api-docs` (the URL #40 cites as the authoritative source). The bundled copy was last refreshed when upstream had 75 paths / 119 schemas / 130 operations; upstream now has 93 paths / 138 schemas / 155 operations — pure additions, no removals. 18 new paths land in the fixture: - cost-report endpoints (already implemented in CostReportHandler): /cost-report, /cost-report/{costReportId} - pro databases: /traffic, /traffic/resume, /upgrade, /available-target-versions - fixed databases: same set - private-link: 8 new endpoints under /subscriptions/{id}/private-link and /subscriptions/{id}/regions/{regionId}/private-link - /subscriptions/{id}/resource-tags 19 new schemas. None of the existing operations or schemas were removed or renamed, so this is a non-breaking refresh. Also nudged `tests/openapi_validation.rs::test_all_endpoints_documented` threshold from 130 to 150, and rewrote the stale comment that referenced "the spec we analyzed from redis.io had 140" (it now has 155). The assertion stays as a floor so future refreshes that strictly add endpoints don't break it. This unblocks #67 (route coverage check needs an authoritative spec) and #72 (reconciling typed handlers with the spec — drift will be larger now that the spec has caught up). Closes #69 Test plan - cargo fmt --all -- --check - cargo clippy --workspace --all-targets -- -D warnings - cargo test --workspace (all existing tests pass; the new fixture is purely additive)
This was referenced May 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Re-fetched
tests/fixtures/cloud_openapi.jsonfromhttps://api.redislabs.com/v1/cloud-api-docs(the URL #40 cites as the authoritative source).Zero removals or renames — the refresh is purely additive.
What's new in the fixture
cost-report(already implemented)/cost-report,/cost-report/{costReportId}/traffic,/traffic/resume,/upgrade,/available-target-versions/fixed/.../subscriptions/{id}/private-link/subscriptions/{id}/regions/{regionId}/private-link/subscriptions/{id}/resource-tagsDrive-by
Nudged
tests/openapi_validation.rs::test_all_endpoints_documentedfloor from 130 → 150 and rewrote the comment that referenced "the spec we analyzed from redis.io had 140" (the live spec now has 155). The assertion remains a floor so additive refreshes don't break it.Why now
Two open issues depend on a fresh fixture:
Closes #69.
Test plan
cargo fmt --all -- --checkcargo clippy --workspace --all-targets -- -D warningscargo test --workspace— all 72 doctests + every integration suite green; the new fixture is purely additive