ARM Template apiVersion for Microsoft.web/sites/sourcecontrol

[richross]

Source code for this repo was cloned into our GitHub Enterprise (GHE) environment. Deploying the ARM template repeatedly failed on the step where it deployed the source code to the Azure Functions and WebSites and mentioned the Microsoft.Web/Sites/SourceControl resource provider. Looking at this RP there is a newer version of this api. I updated the apiVersion property for this part of the ARM template to use apiVersion 2018-11-01. I was able to successfully deploy code to all of the functions and the web site following this change.

[richross]

Just wanted to see if there are any comments to the issue posted here. We have a customer attempting to deploy this into their test environment and they have not had a successful deployment with the deploy failing on the Microsoft.Web/Sites/SourceControl step. They have tried to redeploy this application multiple times with no success.

[abbodh]

Hi @richross , can you try to troubleshoot the issue by checking steps here - https://github.com/OfficeDev/microsoft-teams-apps-diversityandinclusion-preview-/wiki/Troubleshooting#delete-node-modules

Recently few deployments are reported failed due to npm errors, and we got 100% success when node_modules are cleared from app service.

[adamgernon]

Hi
I keep getting a conflict error on the /web deployment

. Tried to fix it using the steps here but to no avail. Logs are attached.

Please advise.
Thanks for your guidance.

error_logs.txt

[Mikhail2k15]

@adamgernon try to use my way #17

[adamgernon]

@Mikhail2k15 - will do once merged. Thanks

[cristianoag]

Use those steps to fix the issue with the sync process.

• Open portal.azure.com and use an admin credential to authenticate.
• Navigate to the resource group where all GC resources are installed.
• Click the App Service resource.
• On the left rail, scroll down to Development Tools and click Advanced Tools.
• Click Go
• Now on the menu located on the top of the page, select Debug console, and then click CMD
• Navigate to site\repository\Source\DiConnect\ClientApp. You can do that clicking on the folders on the box located on the top of the page or using the CD command on the MS-DOS command console
• Delete the node_modules folder by running the commands below on the command console

DEL /S /Q node_modules
RD /S /Q node_modules

• Delete the package-lock.json file
• Now clear the cache, you need to run the npm cache clean --force command in terminal.
• Run the npm install command in the terminal. (This will take some time).
• When finished, retry the sync process, and let me know the results.