search

Azure / logicapps

Azure Logic Apps labs, samples, and tools
MIT License
367 stars 302 forks source link

VSCode custom location Logic App deployment #743

Closed gijsebaert closed 1 year ago

gijsebaert commented 1 year ago

VSCode Dump

The request content was invalid and could not be deserialized: 'Required property 'type' not found in JSON. Path 'extendedLocation', line 1, position 327.'.

Source: Azure Logic Apps (Standard) (Extension)

Steps to Reproduce the Bug or Issue

When creating a Logic app via the AZ Logic App extension GUI interface I face the following error. Since I run ARC enabled Kubernetes I want this resource to run on a custom location (my kubernetes cluster). The custom location is visible in the options when choosing my resource location. As seen below. However on creation it fails with the following error. What could be the cause of this error?

image image

When creating the Logic app via the CLI interface it appears in VSCode, however I cannot manage it and find the authentication token anywhere. Not on the Azure site, nor the VSCode overview pane. As you can see when I expand my workflows I don't see any after I did my VSCode deployment to the LA with custom location. Is there another source where I can find the URL for my workflow?

image

I already checked configurations but they are identical. I don't see why the workflows don't appear when the LA isn't created in VSCode and why the deployment of a LA fails with a custom location specified. Many thanks for checking in on this!

AB#17470694

ccastrotrejo commented 1 year ago

Hi @gijsebaert sorry for the late response. Does this keep happening? I am looking for why the first issues happens, however for the second issue. Does your Logic app project in the Azure portal doesn't show any workflows?

gijsebaert commented 1 year ago

Thanks for getting back @ccastrotrejo, we found our solution following the Azure Jumpstart procedure for deploying logicApps. It can be found over here. https://github.com/microsoft/azure_arc/tree/main/azure_arc_app_services_jumpstart/aks/ARM/artifacts. Both the AppServicesLogonScript.ps1 and the deployLogicApp.ps1 where used to get to our sulotion.

ccastrotrejo commented 1 year ago

@gijsebaert Thanks for letting me know! Glad you found the solution.