Reputation: 1506
I have a logic app that calls azure app using a logic app azure api action. It passes some parameters to the api. When i last looked at this some months ago, i could see the parameters, and even edit the action if required.
Now if i look at the action, either in run history or when editing the action in the browser i get the error: Swagger definition is currently unavailable for this operation.
It is affecting POST and PUT operations. GET seems unaffected.
Is anyone aware of anything that has changed with Azure API Management or Logic APP's Azure API Management Action?
Upvotes: 1
Views: 1133
Reputation: 3533
Adding to @wilson_smyth inputs
Swagger definition is currently unavailable for this operation. This could result into errors when saving.
The above error occurs when the Api is not fully connected.
I followed the below steps which gave me the expected results to avoid the given error.
For demonstration purposes, I have created an Azure Function with Http Trigger.
Then I have created Api in Azure Api Management as mentioned in the above Azure Function. Tested it which gave me the output "Hello, Azure. This HTTP triggered function executed successfully. "
I have created a Azure Logic Apps (Consumption) and selected the Azure Api management which was created earlier.
Select the post method with parameters like authentication type, value and subscription key. Save the application and run it.
Upvotes: 0
Reputation: 1506
We found a resolution to this. Something has changed within the Logic Apps API management Action, and it now requires that POST & PUT operations within Azure API require a sample of the message body that will be sent.
Once we added in a sample, we could again expand the Azure API actions in the logic app and see all the various params.
Upvotes: 1