[BUG] Extracted WSDL Fails Validation

[bcvantage]

Release version

APIOps Toolkit for Azure APIM v4.6.0

Describe the bug

APIOps successfully extracts WSDL but then run-publisher.yaml is unable to validate the extracted WSDL. Affected SOAP APIs are working in development and production environment and were able to be extracted and deployed successfully using the previous extractor of https://github.com/Azure/azure-api-management-devops-resource-kit.

Pipeline log is attached and WSDL.

dev.azure.com_vbtx_f1ea0352-831b-49ac-bd4a-c268ba747183__apis_build_builds_24538_logs_11.txt
specification-wsdl.txt

Expected behavior

• APIOps extracts WSDL
• APIOps validates WSDL
• APIOps publishes WSDL

Actual behavior

• APIOps extracts WSDL
• APIOps fails validation of WSDL

Reproduction Steps

• run-extractor.yaml pointing against APIM instance with SOAP api.
• run-publisher.yaml pointing against test APIM instance using artifacts extracted by run-extractor.yaml

[github-actions]

🎉 Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the closed issues in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes. 🎉

[waelkdouh]

Are you able to successfully upload the files to apim using the portal?

[bcvantage]

Trying to upload using the portal also gives validation error. Informational: ParsingXMLStarted : Started parsing XML Informational: ParsingXMLComplete : Completed parsing XML Error: WsdlImportRuleVerifyWadl11Schema : The element 'operation' in namespace 'http://schemas.xmlsoap.org/wsdl/' has incomplete content. List of possible elements expected: 'documentation, input, output' in namespace 'http://schemas.xmlsoap.org/wsdl/' as well as any element in namespace '##other'. Error: WsdlImportRuleVerifyWadl11Schema : The element 'operation' in namespace 'http://schemas.xmlsoap.org/wsdl/' has incomplete content. List of possible elements expected: 'documentation, input, output' in namespace 'http://schemas.xmlsoap.org/wsdl/' as well as any element in namespace '##other'. Error: WsdlImportRuleVerifyWadl11Schema : The element 'operation' in namespace 'http://schemas.xmlsoap.org/wsdl/' has incomplete content. List of possible elements expected: 'documentation, input, output' in namespace 'http://schemas.xmlsoap.org/wsdl/' as well as any element in namespace '##other'. Error: WsdlImportRuleVerifyWadl11Schema : The element 'operation' in namespace 'http://schemas.xmlsoap.org/wsdl/' has incomplete content. List of possible elements expected: 'documentation, input, output' in namespace 'http://schemas.xmlsoap.org/wsdl/' as well as any element in namespace '##other'. Error: WsdlImportRuleVerifyWadl11Schema : The element 'operation' in namespace 'http://schemas.xmlsoap.org/wsdl/' has incomplete content. List of possible elements expected: 'documentation, input, output' in namespace 'http://schemas.xmlsoap.org/wsdl/' as well as any element in namespace '##other'. Error: WsdlImportRuleVerifyWadl11Schema : The element 'operation' in namespace 'http://schemas.xmlsoap.org/wsdl/' has incomplete content. List of possible elements expected: 'documentation, input, output' in namespace 'http://schemas.xmlsoap.org/wsdl/' as well as any element in namespace '##other'. Error: Parsing error : Unable to parse WSDL Billy Chen Software Developer 1801 S. 2nd St.| McAllen, TX 78503 P: (956) 664-8442 ***@***.***| www.vantage.bank The information contained in this message may be privileged and confidential. Please notify the sender if this message is received in error. Any views or opinions expressed in this message are those of the individual sender and not necessarily those of Vantage Bank Texas, its directors or its shareholders. From: Wael Kdouh ***@***.***> Sent: Wednesday, September 20, 2023 12:29 PM To: Azure/apiops ***@***.***> Cc: Billy Chen ***@***.***>; Author ***@***.***> Subject: Re: [Azure/apiops] [BUG] Extracted WSDL Fails Validation (Issue #387) Are you able to successfully upload the files to apim using the portal? - Reply to this email directly, view it on GitHub<#387 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BBRVIQAWI37CR3AYOU2DVZDX3MRWZANCNFSM6AAAAAA463WBD4>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[waelkdouh]

So this means that the issue is not in the publisher as it's failing when you are using the portal.

Can you try to extract using extractor and compare it to an export from the portal and share with us your findings?

[bcvantage]

That last import was the extracted wsdl artifact. WSDL was extracted originally using extractor from an API that is working in production. Billy Chen Software Developer 1801 S. 2nd St.| McAllen, TX 78503 P: (956) 664-8442 ***@***.***| www.vantage.bank The information contained in this message may be privileged and confidential. Please notify the sender if this message is received in error. Any views or opinions expressed in this message are those of the individual sender and not necessarily those of Vantage Bank Texas, its directors or its shareholders. From: Wael Kdouh ***@***.***> Sent: Wednesday, September 20, 2023 5:11 PM To: Azure/apiops ***@***.***> Cc: Billy Chen ***@***.***>; Author ***@***.***> Subject: Re: [Azure/apiops] [BUG] Extracted WSDL Fails Validation (Issue #387) So this means that the issue is not in the publisher as it's failing when you are using the portal. Can you try to extract using extractor and compare it to an export from the portal and share with us your findings? - Reply to this email directly, view it on GitHub<#387 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BBRVIQCEC7EOS75WI4IXPHTX3NSYHANCNFSM6AAAAAA463WBD4>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[bcvantage]

[Merged] XferSvc_v9_0.txt

This is the original WSDL that was imported into APIM. I reconfirmed that this can be imported successfully just now. The extractor created the artifact that is having validation issues from that imported WSDL which is an API that is currently used in Production. This API was deployed successfully using the previous Azure API Management Devops Resource Kit found here https://github.com/Azure/azure-api-management-devops-resource-kit albeit with many bugs we had to work around to get deployments working.

[guythetechie]

@bcvantage - I was able to replicate your issue, but unfortunately it's an APIM issue, not an ApiOps one. Here's what I did:

1. Took your .txt file above and imported it into my APIM instance through the Azure portal. No issues.
2. From the portal, selected the API and clicked on Export. Selected WSDL as my desired format. Again, no issues.
   
3. Repeated step 1 using the exported file. I received a validation error message.

ApiOps can't help you here, as all we do is make REST API calls to Azure API Management. I would suggest raising a support ticket to see why APIM cannot reimport the file it just exported from the portal.

[waelkdouh]

closing due to inactivity.