This repository has been archived by the owner on Sep 4, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 655
Deployment from External Git with Bicep Template fails #3312
Comments
It could be the limitation in App Settings api where it is async in nature (meaning may take time upto 10s to propagate to the VM even after the api returns successfully). Try to put a delay (say 10s) (not sure if possible - not familiar with this bicep template) between the app settings and source control step and see it that helps or confirms it was an issue. |
Hi Suwat,
Adding a delay in Bicep template is not possible.
However, I've found another workaround.
And you're indeed correct, with the delay between the app settings and the source control, the deployment works.
Thanks for the feedback!
Pieter
From: Suwat Ch ***@***.***>
Sent: Tuesday, June 29, 2021 6:25 PM
To: projectkudu/kudu ***@***.***>
Cc: Pieter Vanhove ***@***.***>; Author ***@***.***>
Subject: Re: [projectkudu/kudu] Deployment from External Git with Bicep Template fails (#3312)
It could be the limitation in App Settings api where it is async in nature (meaning may take time upto 10s to propagate to the VM even after the api returns successfully). Try to put a delay (say 10s) (not sure if possible - not familiar with this bicep template) between the app settings and source control step and see it that helps or confirms it was an issue.
-
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fprojectkudu%2Fkudu%2Fissues%2F3312%23issuecomment-870741730&data=04%7C01%7Cpieter.vanhove%40microsoft.com%7Cc33004be415147ff56aa08d93b1a668d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605806859940158%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=8SGMbjp1Xtd8YwrcuL2DdSWYEbcySiC8mj6198IrMMw%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGCY5GVA6GW46Q6TKVDHV6TTVHXUVANCNFSM47PTKTIQ&data=04%7C01%7Cpieter.vanhove%40microsoft.com%7Cc33004be415147ff56aa08d93b1a668d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605806859950114%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1BxLn7lHoeHXz1OQ%2BsWABMMKBvwEfn8q2IwSlgW9Tiw%3D&reserved=0>.
|
Hi If the problem persists and is related to running it on Azure App Service, please open a support incident in Azure: This way we can better track and assist you on this case Thanks, Joaquin Vano |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
Since last week, we noticed that our deployment of our Web App service is failing, which was working before.
I have created a Bicep Template file to deploy the App Service plan and the App Service. (see attachment)
The web site that I want to deploy is stored on my GitHub Repository, as you can see in the sourcecontrols section.
In the config section, I have configured an application setting "PROJECT", which points to the project file that is stored on my GitHub repository.
When I try to deploy my Bicep Template, the Deployment Center gets configured with my external Git Repository. However, I noticed that the PROJECT property is not created anymore. This causes a failure of the deployment with reason "Unable to determine which solution file to build." This is normal, because the PROJECT property is missing.
When I remove the App Service again, but I don't disconnect my External GitHub, and redeploy, it succeeds because the PROJECT property is configured.
So it seems when my GitHub repository is not connected yet to the deployment center, it is failing...
The Web App name is called eaeaedemoapp.
WebApp.txt
The text was updated successfully, but these errors were encountered: