Skip to content

feat(rds-data): conformance coverage + docs/metadata sync (batch 4)#2011

Merged
vieiralucas merged 1 commit into
mainfrom
wt-rdsdata-4
Jun 27, 2026
Merged

feat(rds-data): conformance coverage + docs/metadata sync (batch 4)#2011
vieiralucas merged 1 commit into
mainfrom
wt-rdsdata-4

Conversation

@vieiralucas

@vieiralucas vieiralucas commented Jun 27, 2026

Copy link
Copy Markdown
Member

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: register rds-data so the probe loads its Smithy model.
  • probe/service_detection.rs: map rds-data to the restJson1 REST protocol. The @http-trait request builder then routes ExecuteStatement -> POST /Execute, etc. (it previously fell through to the awsQuery default and every request 404'd).
  • conformance-baseline.json: add rds-data at 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 BadRequestException that the probe counts as conformant (declared in the op's Smithy error_shapes). So they reproduce identically in CI without Docker — no gaming, the real responses are shape-correct. Verified: cargo run -p fakecloud-conformance -- check passes (no regressions), -- audit passes, and the service_protocol_covers_every_shipped_service test passes.

Docs / metadata

  • parity.md: new RDS Data API row (6 ops) + header bump to 42 services / 3,723 operations / 124,508 variants.
  • Swept every check-doc-counts.sh-tracked surface (README, AGENTS, llms.txt/llms-full.txt, vs/*, service indexes, FAQ, glossary, ...) to the new totals.
  • Added an RDS Data API row to the README service table + LocalStack-comparison table, the docs/services/_index.md table, and supported-services.md.

check-doc-counts.sh passes. 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.

  • New Features
    • Register rds-data in aws-models/service-map.json and map it to restJson1 in the probe (e.g., ExecuteStatement -> POST /Execute).
    • Add rds-data to conformance-baseline.json at 253/253 variants.
    • Update docs and service tables (README, parity, supported-services, vs/*) with RDS Data API (6 ops) and refreshed totals.

Written for commit 9a7372a. Summary will update on new commits.

Review in cubic

…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.
@vieiralucas vieiralucas merged commit 1babd11 into main Jun 27, 2026
104 checks passed
@vieiralucas vieiralucas deleted the wt-rdsdata-4 branch June 27, 2026 22:25
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