Open nathan815 opened 3 months ago
I think the bug is the call to ApplyUpdatesClient.GetParent
here: ApplyUpdateGetMethod.cs:45
2nd and 4th arguments swapped:
ApplyUpdatesClient.GetParent(resourceGroupName, resourceParentType, resourceParentName, providerName, resourceType, resourceName, applyUpdateName) :
should instead be
ApplyUpdatesClient.GetParent(resourceGroupName, providerName, resourceParentType, resourceParentName, resourceType, resourceName, applyUpdateName) :
public static ApplyUpdate GetParent(this IApplyUpdatesOperations operations, string resourceGroupName, string providerName, string resourceParentType, string resourceParentName, string resourceType, string resourceName, string applyUpdateName)
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @adana-popescu, @KalpeshChavan12, @ralucaminea.
Description
Az.Maintenance version 1.4.1 -
Get-AzApplyUpdate
The request this cmdlet sends is malformed in 1.4.1. It looks like it is swapping ProviderName and ResourceParentType when forming the ARM URI. It works fine after downgrading back to 1.1.0.
Command:
Get-AzApplyUpdate -ResourceGroupName rg_name -ResourceParentType hostGroups -ResourceParentName Cluster-2 -ResourceType hosts -ResourceName esx01-r50 -ProviderName Microsoft.Compute -ApplyUpdateName 8001a62a-9385-4fd7-ab25-577f59b85296 -Debug
Excerpt of the output (full output in Debug output field) showing the ARM URI:
Issue script & Debug output
Environment data
Module versions
Error output
No response