Azure Web App should not include Custom Installation Directory feature

[MarkSiedle]

Our Azure Web App step includes the option for a custom installation directory, which doesn't actually get used. This is confusing customers, as they are (rightfully) thinking this is where we install relative to their web root.

Azure Web Apps have a "Physical Path" variable for this, so we need to remove the Custom Install Directory feature to avoid confusion. We checked and this feature does not appear to be used, and is not mentioned in the docs as something that should be available: https://octopus.com/docs/deployment-examples/azure-deployments/deploying-a-package-to-an-azure-web-app#DeployingapackagetoanAzureWebApp-DeploymentfeaturesavailabletoAzureWebAppsteps

While we're here, we should double check other cloud-related steps to make sure only valid features are available.

Source: https://help.octopus.com/t/custom-install-directory-not-used-with-new-azure-target/20674

[MarkSiedle]

Azure Web App should not include Custom Installation Directory feature

[benPearce1]

Fixed in 2018.7

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.