You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This debug output happens when trying to deploy to the logic app
Successfully parsed SCM credential from publish-profile format.
Using SCM credential for authentication, GitHub Action will not perform resource validation.
Error: Execution Exception (state: ValidateAzureResource) (step: Invocation)
Error: When request Azure resource at ValidateAzureResource, Get Function App Settings : Failed to acquire app settings from https://<scmsite>/api/settings with publish-profile
Error: Failed to fetch Kudu App Settings.
Service Unavailable (CODE: 503)
Error: Error: Failed to fetch Kudu App Settings.
Service Unavailable (CODE: 503)
at Kudu.<anonymous> (/home/actions/actions-runner/_work/_actions/Azure/functions-action/v1.4.6/node_modules/azure-actions-appservice-rest/Kudu/azure-app-kudu-service.js:62:23)
at Generator.next (<anonymous>)
at fulfilled (/home/actions/actions-runner/_work/_actions/Azure/functions-action/v1.4.6/node_modules/azure-actions-appservice-rest/Kudu/azure-app-kudu-service.js:5:58)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
Error: Deployment Failed!
Expected Behaviour
When you create the resource you can use the publish profile to deploy to it.
Actual Behaviour
What happens here is that the Logic App that gets deployed doesn't create the required fileshare in the storage account and you have to manually (or via azurerm_storage_share) create a fileshare that stores the content of the App.
Steps to Reproduce
Create the Logic App Standard Resource pointing to certain storage account.
Try to deploy using the Publish Profile.
Important Factoids
Using GitHub actions Azure/functions-action@v1.4.6 to deploy the content of the Logic App
References
No response
The text was updated successfully, but these errors were encountered:
We found the same behaviour with the azurerm_linux_function_app resource.
Basically, what’s happening is that when we use the azurerm_linux_function_app resource it fails to create the File Share needed in the linked Storage Account, so what we had to do is create the File Share using the azurerm_storage_share resource and then add the WEBSITE_CONTENTSHARE app setting in the Function App with the name of the File Share created.
In this case we are using the version 3.18.0 of the hashicorp/azurerm Terraform provider.
Is there an existing issue for this?
Community Note
Terraform Version
1.3.4
AzureRM Provider Version
3.20.0
Affected Resource(s)/Data Source(s)
azurerm_logic_app_standard
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
When you create the resource you can use the publish profile to deploy to it.
Actual Behaviour
What happens here is that the Logic App that gets deployed doesn't create the required fileshare in the storage account and you have to manually (or via azurerm_storage_share) create a fileshare that stores the content of the App.
Steps to Reproduce
Create the Logic App Standard Resource pointing to certain storage account.
Try to deploy using the Publish Profile.
Important Factoids
Using GitHub actions Azure/functions-action@v1.4.6 to deploy the content of the Logic App
References
No response
The text was updated successfully, but these errors were encountered: