Proper parsing to be applied in steps "Parse public IPs" and "Parse private IPs", due to the changed response JSON structure introduced in PRB1701963 - Known Error

Proper parsing to be applied in steps "Parse public IPs" and "Parse private IPs", due to the changed response JSON structure introduced in PRB1701963 Description Issue is related to PRB1701963 , where once response structure from step " Get Azure query results " part of identification section " Application Gateway service identification " associated to discovery pattern " Azure Application Gateway TD (LBS) " is changed, then in shared library " Azure - Application Gateway creation " the new JSON structure is not adopted to the parsing. During steps " Parse public IPs " and " Parse private IPs " the public and the private IP addresses cannot be parsed as the JSON response already have structure " root.value ", but not only " value ". This is due to change of the response in step " Get Azure query results ", where the response is assigned to " rest_resp " variable. Steps to Reproduce

Create service map (Application service) with entry point Load Balancer Service (Application Gateway). Observe on the map that no CI is created due to the reason Public and Private IPs are not retrieved in discovery pattern "Azure Application Gateway TD (LBS)" during top down discovery. Workaround Issue is fixed as part of PRB1743729 already available out of the box, as part of plugin " Discovery and Service Mapping Patterns " version 1.18.0 and after.