Parity grade: A · SDK aws-sdk-go-v2/service/codedeploy@v1.37.0 · last audited 2026-07-23 (59ab8f6a)
| Metric | Value |
|---|---|
| Operations audited | 47 (46 ok, 1 partial) |
| Feature families | 8 (8 ok) |
| Known gaps | 2 |
| Deferred items | 2 |
| Resource leaks | clean |
- ContinueDeployment does not model blue/green wait-state (DeploymentWaitType READY_WAIT/TERMINATION_WAIT); it only validates the deployment exists and no-ops. STILL OPEN after this pass -- see items_still_open in the audit receipt for the exact reason. Low-value to fix without the CreateDeployment lifecycle itself modeling a genuine in-progress/waiting state, since deployments complete synchronously today. (bd: unfiled)
- DeploymentTarget/DeploymentInstance family's Server-platform resolution only covers on-premises instances (this service's own registry); Ec2TagFilters/Ec2TagSet on a deployment group match zero targets because this backend has no live EC2 instance registry to resolve them against. This is a real, documented boundary (not a fabricated/stubbed op) -- a full fix needs a dedicated instance-participation model coordinated with how services/ec2 exposes instances, which is cross-service scope this pass deliberately did not take on. (bd: unfiled)
- ContinueDeployment blue/green wait-state modeling (see gaps) — deferred pending a genuine async deployment lifecycle, which is a larger rearchitecture than this pass's scope
- Ec2TagFilters/Ec2TagSet resolution against real EC2 instances (see gaps) — deferred pending cross-service coordination with services/ec2