-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Get-AzAks is missing (many) details provided by az aks list
#11885
Comments
Thanks for the feedback. Azure PowerShell needs to deserialize output. It is different from Azure CLI. We will evaluate the feature. |
@jsco2t , could you please try latest stable version Az.Aks 1.1.1? The return value is object and you could use . to access return object's properties. |
@jsco2t , have you had chance to try Az.Aks 1.1.1? Does it work for you? We'll assume the issue has been solved and will close the issue if we don't hear from you within 5 days, thanks. |
Close this issue and required attributes are added. |
Sorry for the slow follow-up. The updated version looks great. Thanks so much for getting a bug fix in for it. |
Description
When I issue a call to
az aks list
I get a large JSON document back with what appears to be a complete dump of the details related to the AKS cluster matching the input parameters.When I make the same call to
Get-AzAks
I get a significantly abbreviated version of the details for the same cluster.In particular data fields like the following appear to be missing from the output:
managed identity clusters
this is needed to find theUser Managed Id
that AKS/Azure creates for us.....etc....etc
My expectation is that I should be able to get the exact same level of detail from
Get-AzAks
as I do fromaz aks list
. For reasons beyond the scope of this bug report - I need to use the PowerShell CLI to interact with Azure instead of the Console CLI and these limitations are a significant impediment to working with AKS via PowerShell.Steps to reproduce
Environment data
Module versions
Debug output
Error output
The text was updated successfully, but these errors were encountered: