Repository navigation
UID2-8248: scan the Azure CC image with the shared vulnerability scan action - #2819
Merged
Merged
Conversation
cYKatherine
previously approved these changes
Nov 3, 2026
… action Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mcollins-ttd
force-pushed
the
mkc-UID2-8248-azure-cc-shared-scan
branch
from
November 3, 2026 23:08
bf53318 to
8c1307f
Compare
cYKatherine
approved these changes
Nov 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces the Azure CC workflow's own Trivy steps with the shared
vulnerability_scanaction, the same as the GCP OIDC workflow (#1395). The Azure CC image now gets the same scan as the other images: CVEs without a fix are reported, the JSON report artifacts are uploaded, and.trivyignore.regois applied.The scan still runs before "Push to Docker by digest", so a failed scan stops the publish.
A local build of the Azure CC image has no HIGH/CRITICAL findings with either the old or the new scan settings, so this change does not add new failures today.
🤖 Generated with Claude Code