Skip to content

Fix ECR artifact verification when retries add immutable tags - #48

Merged
jmgasper merged 1 commit into
masterfrom
fix/verify-immutable-release-tag
Nov 4, 2026
Merged

jmgasper merged 1 commit into
masterfrom
fix/verify-immutable-release-tag

Conversation

@jmgasper

@jmgasper jmgasper commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

Retrying AV Scanner and Opportunities publishes a new immutable release tag for an image digest already in ECR. In the observed AWS responses, BatchGetImage by digest returned one image record per tag. The deployer required exactly one record and stopped with Cannot verify pushed image before deployment.

Resolve the exact immutable release tag, then require the returned tag and digest to match the release identity before verifying the image configuration digest and scan. This preserves artifact identity and the single-image response check while allowing multiple tags to refer to the same immutable image.

Validation: all 100 tests pass offline in the pinned CircleCI AWS executor. The regression reproduces ECR's multiple-record digest lookup and verifies the exact-tag path, plus rejection of missing/mismatched tag/digest identities. Read-only checks against the affected dev images returned two records by digest and exactly one matching record by release tag.

Release as v2.0.8 after merge; affected application PRs will pin the tag and exact merged commit. IAM fixes for the original AV Scanner and Opportunities failures are already applied in dev through private IaC. The Payload-dev-only scan policy from v2.0.7 remains unchanged.

@jmgasper
jmgasper merged commit 75bf839 into master Nov 4, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant