Open BhargaviAnnadevara opened 3 years ago
Hi @BhargaviAnnadevara-MSFT , thanks for the information. Could you please split this issue per service or module. The issue is due to the behavior of service We need to route the issue to each service.
Although client can add additional logic to support it but service behavior change will make released client may not work. We are sensitive to add those features.
Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!
@dingmeng-xue Sure thanks, I will split this into two separate issues for tracking.
@dingmeng-xue I've updated this issue to report behavior about Get-AzContainerGroup
cmdlet.
The other issue for Get-AzPrivateDnsZone
cmdlet is here: https://github.com/Azure/azure-powershell/issues/16334
Please let me know if you need any other details.
@dingmeng-xue Can this please be routed to the appropriate Team?
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @macolso.
Author: | BhargaviAnnadevara-MSFT |
---|---|
Assignees: | - |
Labels: | `Container Instances`, `Service Attention`, `Service`, `needs-team-attention` |
Milestone: | - |
It should be issue on service implementation. According to Swagger https://github.com/Azure/azure-rest-api-specs/blob/main/specification/containerinstance/resource-manager/Microsoft.ContainerInstance/stable/2021-03-01/containerInstance.json, the schema of ContainerGroup
is used by listing container group in one resource group or across groups. I will notify service team.
This is still persistent
Description
We've had reports from a customer of late about the
InstanceViewState
property not being populated when executed without-Name
and-ResourceGroupName
parameters.Steps to reproduce
Get-AzContainerGroup
with and without-ResourceGroup
and-Name
parameters and note the difference in output.InstanceViewState
property is not populated inGet-AzContainerGroup | fl *
but present inGet-AzContainerGroup -ResourceGroupName <Resource-Group-Name> -Name <ContainerGroup-Name> | fl *
.Findings: It appears that this is because the
Get-AzContainerGroup
cmdlet invokes the Container Groups - List REST API under the hood, that does not have theinstanceView
property in the response. Whereas,Get-AzContainerGroup -ResourceGroupName <Resource-Group-Name> -Name <ContainerGroup-Name>
calls the Container Groups - Get REST API that returns all the extended properties as well.Post: How can I get Azure container state from command line?
Workaround: To work around this behavior, one has to run the
Get-AzContainerGroup
cmdlets twice to obtain the extended properties, as follows:Ask: IMHO, this experience can confuse customers especially when they're new to using Azure PowerShell modules/cmdlets to manage their resources and mislead them when such data discrepancies are observed. Would love to know your thoughts on the expected behavior and how this experience can be improved.
Environment data
Module versions