Open killnine opened 7 months ago
I did see this in the past when I inadvertently included azurecr.io
to my registry name. The script gives a log message saying it scrubs it from the input, but I don't think that's accurate and only once I set the registry to the name without the suffix did it finally work. It was tricky to find this issue because it was running on a build pipeline with injected envrionment vars for the registry and repo names. But running locally I was able to troubleshoot.
Now it just stopped working entirely.
@wtomw is this kinda a "YMMV" sorta script or something Microsoft officially supports? Or is there some other tooling that would make it easier to tap into Defender results for new images?
@killnine I don't think it's supported anymore, but check this: https://learn.microsoft.com/en-us/azure/defender-for-cloud/transition-to-defender-vulnerability-management the assessment keys are different with Defender now
Describe the bug The container image scan vulnerability assessment script no longer seems to be working. I don't know if there was a schema change or API change on the Graph but it never finds results, even if they do actually appear in Defender for Cloud UI dashboard.
To Reproduce Steps to reproduce the behavior:
No results for image:932 yet ...
No results for image :932 yet ...
Write-Error: No results were found for digest: sha256:4a3e5843...snip...2063 after 3 retries!