Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix template #1

Merged
merged 2 commits into from Aug 17, 2018
Merged

Fix template #1

merged 2 commits into from Aug 17, 2018

Conversation

peterbozso
Copy link
Contributor

Hi Tomas,

I found this code while reading your blog post. Excellent work, thank you! It certainly saved me a great deal of time.
But I found that the template itself is not working, hence I am providing the below fixes. I suggest you to update the blog post as well - in case you find my fixes worthy of a merge, of course. :)

Thanks,
Péter

Changes:

* Change default App Service Plan size to Basic. The Application Insights Profiler won't work with plan sizes below that.
* Make the Web App settings change dependent upon the presence of the extension. Otherwise the settings change would cause the Web App to restart which would fail the deployment at the extension installation step. More on this here: https://stackoverflow.com/questions/45106303/app-insights-status-monitor-extension-failing-to-deploy-with-arm-template
* Set the Application Insights' location to the location of the resource group.
WebSite.json Outdated
@@ -92,7 +92,8 @@
"name": "appsettings",
"type": "config",
"dependsOn": [
"[resourceId('Microsoft.Web/Sites', parameters('webSiteName'))]"
"[resourceId('Microsoft.Web/Sites', parameters('webSiteName'))]",
"Microsoft.ApplicationInsights.AzureWebSites"
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you sure this dependency is specified correctly? I'm somewhat surprised it works.....

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be honest with you I was quite surprised myself as well, but I tried it multiple times and the deployment always succeeded this way.

@tomasr tomasr merged commit f7dc4f9 into tomasr:master Aug 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants