Parity grade: A · SDK aws-sdk-go-v2/service/resourcegroupstaggingapi@v1.41.3 · last audited 2026-10-10 (6d3b2159e)
| Metric | Value |
|---|---|
| PARITY entries audited | 9 (8 ok, 1 partial) |
| Feature families | 2 (2 ok) |
| Known gaps | none |
| Structural gaps (can't be emulated) | 2 |
| Deferred items | 1 |
| Resource leaks | clean |
These do not block an A grade — no implementation could produce real data here because the underlying data source cannot exist in an emulator.
- s3control tagging is not wired: its taggable ARNs use the s3/s3-object-lambda namespaces, which the s3 tagger already owns.
- GetComplianceSummary always reports zero noncompliant resources: it is callable only from an organization management account and aggregates noncompliant counts across every member account, and there is no multi-account resource store to aggregate across (bd: gopherstack-i710).
- "Full TagsPerPage/ResourcesPerPage interaction edge cases beyond the cumulative-tag-count cap (e.g. exact AWS behavior when a single oversized resource's tag count alone exceeds TagsPerPage across multiple such resources in a row) -- current fix always keeps at least one resource per page, matching the 'never split a resource across pages' rule, but has not been stress-tested against arbitrarily adversarial tag-count distributions."