-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
List Registries API Returns Duplicated Resources #31173
Comments
will check |
@jojoochen ,could you share more screenshots or details? |
now in my resource group, I have one registry with a primary region and two additional regions. Then the result after calling the list api are 2. Does the regions in
mean the additional regions? |
Hi @jojoochen. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue. |
Thank you for your response and for looking into this issue! What I meant by Here are the steps to reproduce the issue:
Therefore, the total count was 5 registries * 4 identical entries = 20 resources. I appreciate your help in resolving this and look forward to your insights. Thanks again! |
I can repro this issue with using Rest Api, so I think this should be a service backend issue, |
Hi @kazrael2119, thanks for your previous response regarding the issue. Since it's been a week, I wanted to kindly follow up and check on the current status. |
offline ping the api owner , and they logged this issue in their board https://dev.azure.com/msdata/Vienna/_workitems/edit/3544286 |
close it as we will use the above ado link to track this. |
Describe the bug
When retrieving a list of resources using the Azure API(https://learn.microsoft.com/en-us/rest/api/azureml/registries/list-by-subscription?view=rest-azureml-2024-04-01&tabs=HTTP#code-try-0), the number of returned resources is multiplied by
the number of regions
in which they are deployed. This results in duplicate entries for each unique resource across all regions.To Reproduce
Steps to reproduce the behavior:
region count
.Expected behavior
The API should return a single entry per unique resource, regardless of how many regions it is deployed in.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
This is what we've discovered so far, though we are unsure if there may be some underlying mechanism that we're unaware of. We would appreciate your assistance in clarifying this issue.
The text was updated successfully, but these errors were encountered: