feat(rds-data): conformance coverage + docs/metadata sync (batch 4)#2011
Merged
Conversation
…h 4) Wire RDS Data API into the Level-1 conformance harness and bring every evergreen surface in line with the new service. - aws-models/service-map.json: register rds-data so the probe loads its Smithy model. - conformance probe: map rds-data to the restJson1 (REST) protocol so the @http-trait-driven request builder routes ExecuteStatement -> POST /Execute etc. (previously fell through to the Query default -> 404). - conformance-baseline.json: add rds-data at 253/253 variants and bump the totals to 124,508. The 253 variants are environment-independent (they exercise the no-DB error path, which returns the modeled BadRequestException the probe counts as conformant), so they reproduce identically in CI without Docker. - parity.md: new RDS Data API row (6 ops) and header bump to 42 services / 3,723 operations / 124,508 variants. - Sync every doc-counts-tracked surface (README, AGENTS, llms.txt, vs/*, service indexes, etc.) to the new service/op/variant totals, and add an RDS Data API row to the README service + LocalStack-comparison tables and the supported-services / docs service-index lists. `check-doc-counts.sh`, `cargo run -p fakecloud-conformance -- check` and `-- audit`, the service_protocol coverage test, and `clippy --all-targets -D warnings` all pass.
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
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.
Final batch of the RDS Data API (
rds-data) service: bring it into the Level-1 conformance harness and sync every metadata surface.Conformance
aws-models/service-map.json: registerrds-dataso the probe loads its Smithy model.probe/service_detection.rs: maprds-datato the restJson1 REST protocol. The@http-trait request builder then routesExecuteStatement->POST /Execute, etc. (it previously fell through to the awsQuery default and every request 404'd).conformance-baseline.json: addrds-dataat 253/253 variants, totals bumped to 124,508.The 253 variants are environment-independent: they exercise the no-DB error path, which returns the modeled
BadRequestExceptionthat the probe counts as conformant (declared in the op's Smithyerror_shapes). So they reproduce identically in CI without Docker — no gaming, the real responses are shape-correct. Verified:cargo run -p fakecloud-conformance -- checkpasses (no regressions),-- auditpasses, and theservice_protocol_covers_every_shipped_servicetest passes.Docs / metadata
parity.md: new RDS Data API row (6 ops) + header bump to 42 services / 3,723 operations / 124,508 variants.check-doc-counts.sh-tracked surface (README, AGENTS,llms.txt/llms-full.txt,vs/*, service indexes, FAQ, glossary, ...) to the new totals.docs/services/_index.mdtable, andsupported-services.md.check-doc-counts.shpasses. No source-behavior change — this is harness registration + documentation.Summary by cubic
Adds RDS Data API (
rds-data) to the conformance harness and fixes protocol detection so its REST endpoints route correctly. Totals now: 42 services and 124,508 passing variants; no behavior changes.rds-datainaws-models/service-map.jsonand map it to restJson1 in the probe (e.g.,ExecuteStatement-> POST/Execute).rds-datatoconformance-baseline.jsonat 253/253 variants.Written for commit 9a7372a. Summary will update on new commits.