[BRE-1907] Add artifact manifest to build.yml#7920
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7920 +/- ##
==========================================
- Coverage 61.36% 61.36% -0.01%
==========================================
Files 2244 2244
Lines 98776 98776
Branches 8928 8928
==========================================
- Hits 60617 60616 -1
- Misses 36014 36015 +1
Partials 2145 2145 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
🤖 Bitwarden Claude Code ReviewOverall Assessment: APPROVE This PR adds an image manifest to Code Review DetailsNo blocking findings. The fragment filenames are keyed on unique project names (safe under |
56a0603 to
af5442a
Compare
…for the image built in that step. added a final job to aggregate the fragments into a final manifest
af5442a to
eb02883
Compare
🎟️ Tracking
BRE-1907
📔 Objective
This PR is one of 3 across the server, deploy, and devops repos. The overall goal of these is to provide the final deployment workflow in
devopswith the SHAs of the images that need to be deployed. The current logic uses image tags in the deploy workflow, which are mutable. Deploying using the immutable SHAs from the build step ensures the intended images are deployed.This PR adds steps to
.github/workflows/build.ymlthat builds and uploads a manifest as an artifact to the run. The manifest contains digests of all the container images built in the run so that downstream workflows can use a givenbuild.ymlrun's ID as a key to retrieve and deploy the exact images built in that run. The manifest follows the standard outlined in this action.