Cost of Azure App Service targets should be per-server, not per-service
Octopus Deploy penalises you for using PaaS resources over IaaS.
We currently use VMs which are capable of hosting many web services and only consume 1 deployment target on our licence. If you were to convert that same VM to an Azure App Service, you would consume far more licences for the same server power, which sucks.
e.g.
A single Virtual Machine hosting 15 web apps in IIS costs only 1 deployment target
A single App Service Plan hosting 15 web services costs 15 deployment targets
TL;DR; Azure App Service Plan should consume 1 deployment target regardless of how many app services are contained within it.
Rhys Koedijk
shared this idea
-
Mark Raming
commented
We solve this using "Dynamic Infrastructure" - as part of the deployment process we create the Azure WebApp target in Octopus and then remove it again at the end of the process
-
Ian Straton
commented
Its a bizarre choice from octopus. Really puts an unnecessary constraint on adoption of Cloud Services.