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.
title, seoTitle, description, category, sections, tags
| title | seoTitle | description | category | sections | tags | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ACM API Coverage | AWS Certificate Manager API Coverage — Spinifex Docs | The AWS Certificate Manager API operations Spinifex implements, generated from the gateway dispatch tables on each build, with those it does not offer and why. | Coverage |
|
|
ACM API Coverage
Overview
Spinifex implements 9 operations in the ACM 2015-12-08 API model.
Import and issuance
Spinifex both stores externally-issued certificates and issues its own for load balancer listener references. Certificates are account-scoped, and a delete is refused while any listener still references the ARN — there is no force flag, matching AWS.
RequestCertificate mints an ARN immediately and returns PENDING_VALIDATION; it never issues inline except against a tenant private CA, which has no domain to validate. The validation mode is derived from deployment state rather than configured: the DNS provider API where a credential exists, a manual TXT record where the platform hosts the zone, and a private CA otherwise — the only option for a deployment with no publicly delegated domain.
Terraform's canonical certificate, DNS record and validation flow works unmodified in every mode. Where Spinifex owns the record write it emits no ResourceRecord, so iterating the validation options yields zero records and the validation resource still blocks correctly by polling until the certificate is issued.
Operations
| Operation |
|---|
AddTagsToCertificate |
DeleteCertificate |
DescribeCertificate |
GetCertificate |
ImportCertificate |
ListCertificates |
ListTagsForCertificate |
RemoveTagsFromCertificate |
RequestCertificate |