Closed viananth closed 1 month ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @TravisCragg-MSFT, @nikhilpatel909, @sandeepraichura, @hilaryw29, @GabstaMSFT, @ramankumarlive, @ushnaarshadkhan.
@viananth Thank you for the feedback. I agree that this parameter is not succinct, and it is not possible to filter by a specific edge zone at this time.
We are in the process of revamping the SKU API, and it will give better options to query specific edge zones, search for specific VM Series, and filter results better. Using the -EdgeZone paramter will no longer be a best practice. We expect a preview of this new service to be out later this year.
Description
According to the documentation, Get-AzComputeResourceSku cmdlet supports "-EdgeZone" parameter. But when used it throws error.
PS C:\Users\viananth> Get-AzComputeResourceSku -location westus -edgezone losangeles Get-AzComputeResourceSku: The value 'losangeles' was provided for includeExtendedLocations; the value must be boolean. ErrorCode: InvalidParameters ErrorMessage: The value 'losangeles' was provided for includeExtendedLocations; the value must be boolean. ErrorTarget: StatusCode: 400 ReasonPhrase: Bad Request OperationID : a89762d0-9b75-49be-889e-80c504a85247
This behavior is not correct. If "edgezone" parameter is expecting a boolean input, the parameter should be a switch parameter (eg. "-inclueExtendedLocations". If "-edgezone" parameter is present, it should take an edgezone name and filter based on that name.
Issue script & Debug output
Environment data
Module versions
Error output