Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions changes/unreleased/Fixed-20260906-140000.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
kind: Fixed
body: 'Eight query-protocol providers no longer fabricate a success. `rds`, `neptune`, `docdb`, `redshift`, `elasticache`, `autoscaling`, `cloudformation` and `elasticloadbalancingv2` answered any operation they do not implement with HTTP 200 and an empty `<ActionResponse/>`, so a caller was told an operation succeeded when nothing ran. The body also had no `<ActionResult>` wrapper, so botocore raised `KeyError` rather than returning a value — `neptune.describe_db_cluster_endpoints()` crashed the SDK. They now hand the operation to the generic CRUD engine, which serves the 223 CRUD-shaped ones from the real store and refuses the rest with a clean `InvalidAction`'
time: 2026-09-06T14:00:00.000000+09:00
custom:
Issue: "145"
4 changes: 2 additions & 2 deletions docs/coverage.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,8 +23,8 @@ Per operation, from the [fidelity manifest](fidelity-manifest.md):
| Tier | Operations |
|---|---|
| `hand-verified` | 4,496 |
| `auto-crud` | 4,970 |
| `unimplemented` | 2,941 |
| `auto-crud` | 5,193 |
| `unimplemented` | 2,718 |
| **total known** | **12,407** |

## Why a registered service can serve nothing
Expand Down
Loading