mirror of
https://github.com/mulgadc/spinifex.git
synced 2026-10-15 17:11:30 +00:00
Julian Sommer
e2fb37c0ac
The coverage pages led with a percentage and an "x of y" count, and every table listed the modelled operations Spinifex does not implement, which reads as a scorecard against AWS rather than a statement of what the platform serves. A published page now opens with the operation count alone, tables the operations the gateway serves, and carries a separate not-applicable table with each reason inline instead of footnotes. The unimplemented operations and the counts move to docs/coverage/internal-report.md, which no docs-site slug points at. A service with no implemented operations has no publishable page.
950 B
950 B
title, seoTitle, description, category, sections, tags
| title | seoTitle | description | category | sections | tags | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| AWS API Coverage | Which AWS API Operations Spinifex Implements — Spinifex Docs | The AWS API operations Spinifex serves, generated from its gateway dispatch tables and the pinned AWS SDK service models on each build, service by service. | Coverage |
|
|
AWS API Coverage
Overview
Spinifex serves the AWS APIs below. Every page names the operations Spinifex implements from the pinned aws-sdk-go v1.55.8 api-2.json model for its service, alongside those the platform does not offer and why.
| Service | Operations |
|---|---|
| ACM | 9 |
| EC2 | 125 |
| ECR | 19 |
| ECS | 31 |
| EKS | 34 |
| ELBv2 | 34 |
| IAM | 75 |
| RDS | 26 |
| STS | 5 |