Using the old process model for Azure Web Apps we were able to bind the web app name to a variable, so that we could deploy to different deployment slots for different environments.
It looks like the documentation hasn’t been updated to reflect the new Octopus Azure App Service deployment model where web apps are treated as separate deployment targets. I’m on
v2018.5.7, and I don’t see where we can bind the web app name to a variable. We also can’t bind the Azure account to a variable.
Does this mean we would have to create a deployment target for each deployment slot for each web app? For us, we use deployment slots for dev, test, smoke testing, staging, and production. It seems like this will gobble up quite a few of our deployment target licenses.
Am I missing something, or are there plans to allow variable binding for Azure Web App names and Azure Subscriptions?