Azure-functions

Added
- Java and C support for the local project tree item
- Copy local http trigger urls
- Execute local timer triggers
- Allow Python 3.8 when creating local project or deploying to Azure (only supported in v3 of the Azure Functions runtime)
- Allow deploying Java projects to Linux Function Apps in Azure (only supported in v3 of the Azure Functions runtime)
- Added setting "azureFunctions.showDeployConfirmation" to turn off "Are you sure you want to deploy..." dialog
- Logging is enabled by default when creating a Function App in Azure

Changed
- Bindings are no longer displayed in the tree. View properties on the function instead
- "Add Binding..." was moved from the local "Bindings" tree item to the function tree item
- Prompt for runtime before OS when creating a Function App in Azure. OS will not be prompted if the runtime doesn't support it
- Inline button to view deployment logs was removed. Left or right click the tree item instead

[Fixed](https://github.com/Microsoft/vscode-azurefunctions/issues?q=is%3Aissue+milestone%3A%220.21.0%22+is%3Aclosed)
- Reduced time to create the first Function App in Azure on some new subscriptions
- Prompt to select existing resource group instead of "403" error when subscription doesn't have permissions to create
- "Init project for VS Code" will detect projects using "extensions.csproj" and configure to use "func extensions install" instead of bundle

Added
- Browse to website
- Added option to create a Node 12.x Function App, only supported in v3 of the Azure Functions runtime

Changed
- If the Azure Functions runtime version cannot be automatically detected, default to v3 instead of v2
- Removed ability to update app settings in Azure if language or runtime version don't match when deploying. Instead, create a new Function App in Azure

Fixed

- [Bugs fixed](https://github.com/Microsoft/vscode-azurefunctions/issues?q=is%3Aissue+milestone%3A%220.20.2%22+is%3Aclosed)

Added
- Select Python version (3.6.x or 3.7.x) when creating a project

[Fixed](https://github.com/Microsoft/vscode-azurefunctions/issues?q=is%3Aissue+milestone%3A%220.20.1%22+is%3Aclosed)
- Linux Premium Function App fails to run because it's missing CONTENT* app settings

Added
- Select Node.js or Python runtime version when creating a Function App in Azure
- Added support for [Azure Functions v3 Preview](https://aka.ms/AA6i3ev) in the following existing features:
- Install func cli from the command palette (brew and npm only)
- Create new project/function from a version-specific template
- Validate local version matches remote version when deploying
- View Files and Logs for your Function App in Azure

Fixed

- [Bugs fixed](https://github.com/Microsoft/vscode-azurefunctions/issues?q=is%3Aissue+milestone%3A%220.20.0%22+is%3Aclosed)

Changed

- Removed support for "azureFunctions.projectRuntime" value of "beta". Use "~1", "~2", or "~3" instead

[Fixed](https://github.com/Microsoft/vscode-azurefunctions/issues?q=is%3Aissue+milestone%3A%220.19.1%22+is%3Aclosed)

- Fix error "Expected value to be neither null nor undefined" when adding a binding

Added
- Added support for deployment slots (feature flag no longer required)
- Deploy
- Stream logs
- Start/stop/restart
- Create/delete/swap
- Default new Python projects to remote build. See here for more info: https://aka.ms/AA5vsfd
- Function templates respect extension bundle specified in host.json
- Add option to use a Premium (preview) hosting plan when creating a Function App in Azure

[Fixed](https://github.com/Microsoft/vscode-azurefunctions/issues?q=is%3Aissue+milestone%3A%220.19.0%22+is%3Aclosed)
- Fixed subfolders of a symbolically linked folder not included during deploy
- Fixed bundle dependency not added during "Add Binding"
- Reduced false positive deploy failures when listing triggers or logs