docs: Update README and CONFIG docs (#464)

Author: tbarlow12

README.md

@@ -2,20 +2,21 @@
 
 This plugin enables Azure Functions support within the Serverless Framework.
 
-[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions) [![Node Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/Node%20Integration%20Tests/badge.svg)](https://github.com/serverless/serverless-azure-functions/actions?query=workflow%3A%22Node+Integration+Tests%22) [![Python Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/Python%20Integration%20Tests/badge.svg)](https://github.com/serverless/serverless-azure-functions/actions?query=workflow%3A%22Python+Integration+Tests%22) [![.NET Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/.NET%20Integration%20Tests/badge.svg)](https://github.com/serverless/serverless-azure-functions/actions?query=workflow%3A%22.NET+Integration+Tests%22)
+[![Build Status](https://dev.azure.com/serverless-inc/serverless-azure-functions/_apis/build/status/Publish%20Release?branchName=master)](https://dev.azure.com/serverless-inc/serverless-azure-functions/_build/latest?definitionId=13&branchName=master) [![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions) [![npm version](https://badge.fury.io/js/serverless-azure-functions.svg)](https://www.npmjs.com/package/serverless-azure-functions) [![Node Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/Node%20Integration%20Tests/badge.svg)](https://github.com/serverless/serverless-azure-functions/actions?query=workflow%3A%22Node+Integration+Tests%22) [![Python Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/Python%20Integration%20Tests/badge.svg)](https://github.com/serverless/serverless-azure-functions/actions?query=workflow%3A%22Python+Integration+Tests%22) [![.NET Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/.NET%20Integration%20Tests/badge.svg)](https://github.com/serverless/serverless-azure-functions/actions?query=workflow%3A%22.NET+Integration+Tests%22)
 
 ## Quickstart
 
 ### Pre-requisites
 
-1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*
+1. Node.js 8.x or above
 2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.
 3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.
 
 ### Create a new Azure Function App
 
 ```bash
 # Create Azure Function App from template
+# Templates include: azure-nodejs, azure-python, azure-dotnet
 $ sls create -t azure-nodejs -p <appName>
 # Move into project directory
 $ cd <appName>
@@ -27,13 +28,7 @@ The `serverless.yml` file contains the configuration for your service. For more
 
 ### Running Function App Locally (`offline` plugin)
 
-In order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:
-
-```bash
-$ npm i azure-functions-core-tools -g
-```
-
-Then, at the root of your project directory, run:
+At the root of your project directory, run:
 
 ```bash
 # Builds necessary function bindings files and starts the function app
@@ -44,16 +39,16 @@ The `offline` process will generate a directory for each of your functions, whic
 
 After the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.
 
-To simply start the function app *without* building the files, run:
+To build the files *without* spawning the process to start the function app, run:
 
 ```bash
-$ sls offline start
+$ sls offline build
 ```
 
-To build the files *without* spawning the process to start the function app, run:
+To simply start the function app *without* building the files, run:
 
 ```bash
-$ sls offline build
+$ sls offline start
 ```
 
 To clean up files generated from the build, run:
@@ -325,10 +320,14 @@ We run our integration tests twice per day from our GitHub workflow. These tests
 - Python 3.6 (Linux only) using premium functions
 - Python 3.7 (Linux only)
 - Python 3.8 (Linux only)
+- .NET Core 2.2 on Linux
+- .NET Core 2.2 on Windows
+- .NET Core 3.1 on Linux
+- .NET Core 3.1 on Windows
 
 We made these configurations as minimal as possible. If you are having problems with your project, feel free to check to see if our integration tests are passing (see badge at top of readme) and then double check our configuration inside the `integrationTests` directory. 
 
-We use [Clover](https://www.npmjs.com/package/clvr) to run the integration tests, and they run 2x per day in our GitHub Action.
+We use [Clover](https://www.npmjs.com/package/clvr) to run the integration tests, and they run 2x per day in our GitHub Action, split out by runtime language.
 
 #### Signing commits
 

docs/CONFIG.md

@@ -16,13 +16,52 @@ This document serves as a basic outline for configuring your Azure Function App
     - `python3.6` (forced to use `linux`)
     - `python3.7` (forced to use `linux`)
     - `python3.8` (forced to use `linux`)
+    - `dotnet2.2`
+    - `dotnet3.1`
 - `provider.region` - [Azure region](https://azure.microsoft.com/en-us/global-infrastructure/regions/) for resources
 - `provider.prefix` - Prefix used in naming convention for resources. Default `sls`
 - `provider.subscriptionId` - Subscription ID to be used in deployment. Can also be set via:
    - Command-line argument (`--subscriptionId {SUB_ID}`)
    - Environment variable (`AZURE_SUBSCRIPTION_ID`)
 - `provider.stage` - Stage for resources. Default `dev`
- <!-- TODO - provider.type -->
+- `provider.type` - Type of Azure Function app
+  - `consumption` (default)
+  - `premium`
+  - `ase`
+- `provider.subscriptionId` - Azure subscription ID. Can also be specified by environment variable (`AZURE_SUBSCRIPTION_ID`) or command-line args (`--subscriptionId`)
+- `provider.tenantId` - Azure subscription ID. Can also be specified by environment variable (`AZURE_TENANT_ID`) or command-line args (`--tenantId`)
+- `provider.appId` - Azure subscription ID. Can also be specified by environment variable (`AZURE_CLIENT_ID`) or command-line args (`--appId`)
+- `provider.tags` - Tags to apply to resource group
+  ```yaml
+  provider:
+    tags:
+      tagName: tagValue
+  ```
+- `provider.deployment` - Deployment configuration
+  - `provider.deployment.external` - Publishes function app by uploading to blob storage and executes a sync triggers command
+  - `provider.deployment.rollback` - Enables the rollback scenario by timestamping deployments and artifacts. (Default true)
+  - `provider.deployment.container` - Optional specification of container name for zipped code artifacts
+- `provider.{resource}.name` - Specify name of resource for the Azure resource types
+- `provider.{resource}.sku.name` - Specify name of the sku for the Azure resource types
+- `provider.{resource}.sku.tier` - Specify tier of the sku for the Azure resource types
+- Azure resource types 👆
+  - `functionApp`
+  - `appInsights`
+  - `appServicePlan`
+  - `storageAccount`
+  - `hostingEnvironment`
+  - `virtualNetwork`
+  - `keyVaultConfig` (can only specify `name` or `resourceGroup`)
+- `provider.deploymentName` - Specification of deployment name
+- `provider.armTemplate` - Specification of ARM template to use
+    ```yaml
+    provider:
+      armTemplate:
+        file: "pathToArmTemplate.json"
+        parameters:
+          param1: value1
+          param2: value2
+    ```
 - `provider.environment` - Key value pairs to set as app settings (environment variables) within function app. Example:
     ```yaml
     provider: