gsadmin/spinifex
1
0
Fork 0
mirror of https://github.com/mulgadc/spinifex.git synced 2026-10-20 03:11:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: update compatibility pages

Browse Source
This commit is contained in:
Julian Sommer
2026-09-14 11:49:46 +10:00
parent fb6494da01
commit 29faaa78fd
17 changed files with 121 additions and 201 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/compatibility/aws-api-coverage/README.md
-13
View File
@@ -29,17 +29,4 @@ Spinifex serves the AWS APIs below. Every page counts the operations in the pinn
| [ELBv2](/docs/elbv2-api-coverage) | 2015-12-01 | 33 | 46 | 71.7% |
| [IAM](/docs/iam-api-coverage) | 2010-05-08 | 75 | 159 | 47.2% |
| [RDS](/docs/rds-api-coverage) | 2014-10-31 | 26 | 162 | 16.0% |
| [S3](/docs/s3-api-coverage) | 2006-03-01 | — | 99 | — |
| [STS](/docs/sts-api-coverage) | 2011-06-15 | 4 | 8 | 50.0% |
| Status | Meaning |
|---|---|
| ✅ Implemented | A modelled operation bound to a real handler. |
| 🟡 Stub | A registered handler that answers with a fixed or empty result. |
| 🚫 Not supported | A registered handler that deliberately refuses, so a client sees "not offered" rather than an unknown action. |
| ❌ Not implemented | Modelled by AWS, not registered by Spinifex. |
| 🔒 Outside the pinned model | Registered by Spinifex but absent from the pinned model — an internal route, not a tenant-callable AWS action. |
### What "implemented" means here
An operation is implemented when the gateway binds it to a real handler. These pages are generated from those dispatch tables on every build, so they cannot go stale against the code. That is a mechanical fact, and it is the only claim they make. It does not say the handler honours every parameter AWS models, and no page reports parameter or field-level detail: a handler receives a fully-populated typed SDK struct, so nothing distinguishes a field it honours from one it ignores. Behavioural conformance is measured separately by the integration conformance suite.
docs/compatibility/aws-api-coverage/intro.md
-3
View File
@@ -1,3 +0,0 @@
### What "implemented" means here
An operation is implemented when the gateway binds it to a real handler. These pages are generated from those dispatch tables on every build, so they cannot go stale against the code. That is a mechanical fact, and it is the only claim they make. It does not say the handler honours every parameter AWS models, and no page reports parameter or field-level detail: a handler receives a fully-populated typed SDK struct, so nothing distinguishes a field it honours from one it ignores. Behavioural conformance is measured separately by the integration conformance suite.