[BUG] Azure Resource Mover APIs do not work for Network interface resources #47729
Labels
ARM
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
Mgmt
This issue is related to a management-plane library.
needs-team-attention
Workflow: This issue needs attention from Azure service team or SDK team
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Service Attention
Workflow: This issue is responsible by Azure service team.
Library name and version
Azure.ResourceManager.ResourceMover 1.1.1
Describe the bug
The
MoverResourceSetResource.GetMoverResource
andMoverResourceCollection.CreateOrUpdateAsync
API does not seem to handle the JSON response/request if a NIC resource is passed correctly. The first one fails on deserializing the "IsOptional" field as it interprets "True" and "False" as strings. The second one fails if a private address field is an empty string as it attempts to parse it as System.Net.IpAddress, even though this is a valid value and would be the default if using the Azure Resource Mover from the Azure Portal.Note that the exact same set of commands and configuration works with the Az PowerShell library,
Expected behavior
GetMoverResource
should return the data model for an existing valid resource in a move collection, andCreateOrUpdateAsync
should be able to successfully add a NIC to a move collection.Actual behavior
GetMoverResource
fails with the following exception:CreateOrUpdateAsync
fails with the following exception:Reproduction Steps
For the issue with the GetMoverResource API:
For the issue with the CreateOrUpdateAsync API:
Environment
The text was updated successfully, but these errors were encountered: