You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the problem you're trying to solve
In Log editor, SHA value of image is displayed in both Tag and Digest column. i.e. when a Managed Identity pulls the image from the registry using the tag name (not the SHA name), such as when attempting to build a custom image in Azure DevOps (ADO) by pulling the ACR image with the tag mentioned in the Docker file, the report still shows the SHA value. It's important to note that there are no Kubernetes, cluster, or other services involved in this scenario. It solely revolves around the ADO pipeline using a Docker file, where the image is pulled from ACR with a specified tag.
However, when a user retrieves the ACR registry image with a specified tag from a laptop, the report displays the tag name.
Describe the solution you'd like
Just like user pull, even for managed identity pull should show tag vaule in the Tag column
Additional context
for more details refere :TrackingID#2401230040009938
Also attaching screenshot.
The text was updated successfully, but these errors were encountered:
What is the problem you're trying to solve
In Log editor, SHA value of image is displayed in both Tag and Digest column. i.e. when a Managed Identity pulls the image from the registry using the tag name (not the SHA name), such as when attempting to build a custom image in Azure DevOps (ADO) by pulling the ACR image with the tag mentioned in the Docker file, the report still shows the SHA value. It's important to note that there are no Kubernetes, cluster, or other services involved in this scenario. It solely revolves around the ADO pipeline using a Docker file, where the image is pulled from ACR with a specified tag.
However, when a user retrieves the ACR registry image with a specified tag from a laptop, the report displays the tag name.
Describe the solution you'd like
Just like user pull, even for managed identity pull should show tag vaule in the Tag column
Additional context

for more details refere :TrackingID#2401230040009938
Also attaching screenshot.
The text was updated successfully, but these errors were encountered: