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

Add Properties for Azure.Containers.ContainerRegistry.ArtifactManifestProperties #40465

Open
Nickcandy opened this issue Dec 1, 2023 · 2 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Container Registry customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved.
Milestone

Comments

@Nickcandy
Copy link

Library name

Azure.Containers.ContainerRegistry

Please describe the feature.

In the previous iteration of our cmdlets, particularly Get-AzContainerRegistryManifest, the output included two properties: MediaType and ConfigMediaType. However, following the update to Track 2 SDK, as per the changes documented in the pull request 24341 , we noticed that these properties have been removed in here. The justification mentioned was a lack of usage by customers.
Given this situation, we find ourselves in a challenging position. As per our internal policy regarding breaking changes, and considering the potential impact on basic user scenarios, it is critical for us to find an appropriate solution. The absence of these properties in the Track 2 client could potentially hinder some fundamental functionalities for our users.
Hence, we request the reintroduction of the MediaType and ConfigMediaType properties in future releases.

@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. Container Registry customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-triage Workflow: This issue needs the team to triage. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Dec 1, 2023
@jsquire jsquire added needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team and removed needs-team-triage Workflow: This issue needs the team to triage. labels Dec 1, 2023
@jsquire
Copy link
Member

jsquire commented Dec 1, 2023

Thank you for your feedback. Tagging and routing to the team member best able to assist.

@annelo-msft
Copy link
Member

Hi @Nickcandy -

Thank you for sharing your requirement!

In the meantime, I have provided a sample showing how you can obtain these values using lower-level APIs available in the Azure.Core library here: Accessing Manifest properties using lower-level Azure.Core APIs. We had previously discussed making a single call at a time - I have updated the gist to include a description of how to access a collection of manifest property values.

We hope this unblocks your scenario while we investigate the feasibility and timeline of adding the convenience APIs you've requested.

@pallavit pallavit added this to the Backlog milestone Dec 4, 2023
@pallavit pallavit added feature-request This issue requires a new behavior in the product in order be resolved. and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team labels Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. Container Registry customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved.
Projects
Status: No status
Development

No branches or pull requests

4 participants