BED-7784: disable provenance in publish image step#183
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Ticket: https://specterops.atlassian.net/browse/BED-7784
Adds provenance: false to the Push Image step in the
publishworkflow.Recent GitHub Actions runner updates changed Docker Buildx's default behavior to include "provenance attestations" (metadata) when pushing images. AWS ECR doesn't support the manifest format used by these attestations, causing the push to fail with a 403 Forbidden. This disables the attestation metadata on push. The image itself not affected.
Already made this change to the
buildstep in this pr, but forgot to make the same change for thepublishstep which is what I am doing here.Ref: docker/build-push-action#826
Summary by CodeRabbit