Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If image with tag name is pulled by managed identity, log editor should show tag value under Tag cloumn insted of SHA value #735

Closed
docgurureddy opened this issue Feb 9, 2024 · 2 comments
Labels
feature-request Issues that request new features triaged Use after the issue is triaged

Comments

@docgurureddy
Copy link

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.
LogEditor_ACR_Pull_records

@docgurureddy docgurureddy added the feature-request Issues that request new features label Feb 9, 2024
@cegraybl
Copy link

cegraybl commented Feb 9, 2024

this looks like a duplicate of #734, is there anything additional from this issue that would make it different?

@toddysm
Copy link
Contributor

toddysm commented Jan 15, 2025

Closing as duplicate

@toddysm toddysm closed this as completed Jan 15, 2025
@toddysm toddysm added the triaged Use after the issue is triaged label Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Issues that request new features triaged Use after the issue is triaged
Projects
None yet
Development

No branches or pull requests

3 participants