[Deployment] Modify echo-bot to work out of the box w/ new ARM template

[stevengum]

Specific Changes

• Rename flask APP to app to utilize Azure's automated flask app:app detection
• Add ARM template with Linux App Service and Linux App Service Plan provisioning
  • Note: The ARM template automatically configures kudu to build on deployment, which differs from the Node.js model where the developer is expected to include their local node_modules/

The commands used to deploy with this ARM template mirror the steps found in the docs page: "Deploy your bot"

Commands:

az ad app create --display-name "MSAAppName" --password "AppPassword" --available-to-other-tenants

# When using from the root of the 02.echo-bot sample
az group deployment create --name "deployment-name" --resource-group "resource-group" --template-file "deploymentTemplates/template-with-preexisting-rg.json" --parameters appId="AppIdOutputFromPreviousCommand" appSecret="AppPassword" botId="UniqueIdOrNameForBot" newWebAppName="NameOfLinuxAppService" newAppServicePlanName="NameOfLinuxAppServicePlan" appServicePlanLocation="LocationToBeUsedForCreatingResources"

az webapp deployment source config-zip --resource-group "resource-group" --name "NameOfLinuxAppService" --src "02.echo-bot.zip"

Follow-up

• Flask samples need to be updated so that the flask APP is app
  • Django samples should use wsgi.py as per the documentation
  • We can also provide custom start-up commands, but should then close on a pattern if this is the route we wish to pursue
• Investigate performing a zip-deploy with a virtual environment already configured.
  • Oryx's venv name looks to be antenv

[tracyboehrer]

Tested with echo-bot. Works perfect.

Add future tasks: template for new RG.

Add to steps: Manually zip before final 'az' command.