Merge pull request #267266 from ggailey777/cleanup

[Functions] Python quickstart updates and other clean-up fixes

Author: v-dirichards

articles/azure-functions/TOC.yml

@@ -1015,6 +1015,8 @@
             href: errors-diagnostics/diagnostic-events/azfd0010.md
           - name: AZFD0011
             href: errors-diagnostics/diagnostic-events/azfd0011.md
+          - name: AZFD0012
+            href: errors-diagnostics/diagnostic-events/azfd0012.md
     - name: host.json 2.x reference
       href: functions-host-json.md
     - name: host.json 1.x reference

articles/azure-functions/create-first-function-cli-node.md

@@ -159,6 +159,12 @@ Each binding requires a direction, a type, and a unique name. The HTTP trigger h
 [!INCLUDE [functions-cleanup-resources-cli](../../includes/functions-cleanup-resources-cli.md)]
 
 ## Next steps
-
+<!--- Revert this after we get Node.js v4 support added to the follow-on quickstarts -->
+::: zone pivot="nodejs-model-v3"  
 > [!div class="nextstepaction"]
 > [Connect to an Azure Storage queue](functions-add-output-binding-storage-queue-cli.md?pivots=programming-language-javascript)
+::: zone-end  
+::: zone pivot="nodejs-model-v4"   
+> [!div class="nextstepaction"]
+> [Learn more about JavaScript functions](./functions-reference-node.md)
+::: zone-end  

articles/azure-functions/create-first-function-cli-python.md

@@ -1,22 +1,17 @@
 ---
 title: Create a Python function from the command line - Azure Functions
 description: Learn how to create a Python function from the command line, then publish the local project to serverless hosting in Azure Functions.
-ms.date: 02/16/2024
+ms.date: 02/29/2024
 ms.topic: quickstart
 ms.devlang: python
 ms.custom: devx-track-python, devx-track-azurecli, devx-track-azurepowershell, mode-api, devdivchpfy22
-zone_pivot_groups: python-mode-functions
-
 ---
 
 # Quickstart: Create a Python function in Azure from the command line
 
 In this article, you use command-line tools to create a Python function that responds to HTTP requests. After testing the code locally, you deploy it to the serverless environment of Azure Functions. 
 
-This article covers both Python programming models supported by Azure Functions. Use the selector at the top to choose your programming model.  
-
->[!NOTE]
->The Python v2 programming model for Azure Functions provides a decorator-based approach for creating functions. To learn more about the Python v2 programming model, see the [Developer Reference Guide](functions-reference-python.md?pivots=python-mode-decorators).
+This article uses the Python v2 programming model for Azure Functions, which provides a decorator-based approach for creating functions. To learn more about the Python v2 programming model, see the [Developer Reference Guide](functions-reference-python.md?pivots=python-mode-decorators)
 
 Completing this quickstart incurs a small cost of a few USD cents or less in your Azure account.
 
@@ -35,12 +30,13 @@ Before you begin, you must have the following requirements in place:
   + The Azure [Az PowerShell module](/powershell/azure/install-azure-powershell) version 5.9.0 or later.
 
 + [A Python version supported by Azure Functions](supported-languages.md#languages-by-runtime-version).
-::: zone pivot="python-mode-decorators"  
+
 + The [Azurite storage emulator](../storage/common/storage-use-azurite.md?tabs=npm#install-azurite). While you can also use an actual Azure Storage account, the article assumes you're using this emulator.
-::: zone-end  
 
 [!INCLUDE [functions-install-core-tools](../../includes/functions-install-core-tools.md)]
 
+Use the `func --version` command to make sure your version of Core Tools is at least `4.0.5530`.
+
 ## <a name="create-venv"></a>Create and activate a virtual environment
 
 In a suitable folder, run the following commands to create and activate a virtual environment named `.venv`. Make sure that you're using a [version of Python supported by Azure Functions](supported-languages.md?pivots=programming-language-python#languages-by-runtime-version).
@@ -88,49 +84,7 @@ You run all subsequent commands in this activated virtual environment.
 ## Create a local function
 
 In Azure Functions, a function project is a container for one or more individual functions that each responds to a specific trigger. All functions in a project share the same local and hosting configurations. 
-::: zone pivot="python-mode-configuration"  
-In this section, you create a function project that contains a single function.
-
-1. Run the [`func init`](functions-core-tools-reference.md#func-init) command as follows to create a Python functions project in the virtual environment.
-
-    ```console
-    func init --python --model V1
-    ```
-
-    The environment now contains various files for the project, including configuration files named [*local.settings.json*](functions-develop-local.md#local-settings-file) and [*host.json*](functions-host-json.md). Because *local.settings.json* can contain secrets downloaded from Azure, the file is excluded from source control by default in the *.gitignore* file.
-
-1. Add a function to your project by using the following command, where the `--name` argument is the unique name of your function (HttpExample) and the `--template` argument specifies the function's trigger (HTTP).
-
-    ```console
-    func new --name HttpExample --template "HTTP trigger" --authlevel "anonymous"
-    ```
-
-   [`func new`](functions-core-tools-reference.md#func-new) creates a subfolder matching the function name that contains a code file appropriate to the project's chosen language and a configuration file named *function.json*.    
-
-1. Run this command to make sure that the Azure Functions library is installed in the environment.
-
-    ### [bash](#tab/bash)
-
-    ```bash
-    .venv/bin/python -m pip install -r requirements.txt
-    ```
-    
-    ### [PowerShell](#tab/powershell)
-    
-    ```powershell
-    .venv\Scripts\python -m pip install -r requirements.txt
-    ```
-    
-    ### [Cmd](#tab/cmd)
-    
-    ```cmd
-    .venv\Scripts\python -m pip install -r requirements.txt
-    ```
-    
-    ---
 
-::: zone-end  
-::: zone pivot="python-mode-decorators"  
 In this section, you create a function project and add an HTTP triggered function.
 
 1. Run the [`func init`](functions-core-tools-reference.md#func-init) command as follows to create a Python v2 functions project in the virtual environment.
@@ -148,53 +102,6 @@ In this section, you create a function project and add an HTTP triggered functio
     ```
 
     If prompted, choose the **ANONYMOUS** option. [`func new`](functions-core-tools-reference.md#func-new) adds an HTTP trigger endpoint named `HttpExample` to the `function_app.py` file, which is accessible without authentication.    
-<!--- Remove these last steps after the next Core Tools version is released (4.28.0)--->    
-1. Open the local.settings.json project file and verify that the `AzureWebJobsFeatureFlags` setting has a value of `EnableWorkerIndexing`. This setting is required for Functions to interpret your project correctly as the Python v2 model when running locally. 
-
-1. In the local.settings.json file, update the `AzureWebJobsStorage` setting as in the following example:
-
-    ```json
-    "AzureWebJobsStorage": "UseDevelopmentStorage=true",
-    ```
-
-    This setting tells the local Functions host to use the storage emulator for the storage connection currently required by the Python v2 model. When you publish your project to Azure, you need to instead use the default storage account. If you're instead using an Azure Storage account, set your storage account connection string here.   
-
-1. Run this command to make sure that the Azure Functions library is installed in the environment.
-
-    ### [bash](#tab/bash)
-
-    ```bash
-    .venv/bin/python -m pip install -r requirements.txt
-    ```
-    
-    ### [PowerShell](#tab/powershell)
-    
-    ```powershell
-    .venv\Scripts\python -m pip install -r requirements.txt
-    ```
-    
-    ### [Cmd](#tab/cmd)
-    
-    ```cmd
-    .venv\Scripts\python -m pip install -r requirements.txt
-    ```
-    
-    ---
-
-## Start the storage emulator
-
-By default, local development uses the Azurite storage emulator. This emulator is used when the `AzureWebJobsStorage` setting in the *local.settings.json* project file is set to `UseDevelopmentStorage=true`. When using the emulator, you must start the local Azurite storage emulator before running the function. 
-
-You can skip this step if the `AzureWebJobsStorage` setting in *local.settings.json* is set to the connection string for an Azure Storage account instead of `UseDevelopmentStorage=true`. 
-
-Use the following command to start the Azurite storage emulator in a separate process:
-
-```cmd
-start azurite
-```
-
-For more information, see [Run Azurite](../storage/common/storage-use-azurite.md?tabs=npm#run-azurite)
-::: zone-end
 
 [!INCLUDE [functions-run-function-test-local-cli](../../includes/functions-run-function-test-local-cli.md)]
 
@@ -210,14 +117,14 @@ Use the following commands to create these items. Both Azure CLI and PowerShell
 
 1. If needed, sign in to Azure.
 
-    # [Azure CLI](#tab/azure-cli)
+    ### [Azure CLI](#tab/azure-cli)
     ```azurecli
     az login
     ```
 
     The [`az login`](/cli/azure/reference-index#az-login) command signs you into your Azure account.
 
-    # [Azure PowerShell](#tab/azure-powershell)
+    ### [Azure PowerShell](#tab/azure-powershell)
     ```azurepowershell
     Connect-AzAccount
     ```
@@ -226,18 +133,17 @@ Use the following commands to create these items. Both Azure CLI and PowerShell
 
     ---
 
-
 1. Create a resource group named `AzureFunctionsQuickstart-rg` in your chosen region.
 
-    # [Azure CLI](#tab/azure-cli)
+    ### [Azure CLI](#tab/azure-cli)
 
     ```azurecli
     az group create --name AzureFunctionsQuickstart-rg --location <REGION>
     ```
 
     The [az group create](/cli/azure/group#az-group-create) command creates a resource group. In the above command, replace `<REGION>` with a region near you, using an available region code returned from the [az account list-locations](/cli/azure/account#az-account-list-locations) command.
 
-    # [Azure PowerShell](#tab/azure-powershell)
+    ### [Azure PowerShell](#tab/azure-powershell)
 
     ```azurepowershell
     New-AzResourceGroup -Name AzureFunctionsQuickstart-rg -Location '<REGION>'
@@ -247,23 +153,20 @@ Use the following commands to create these items. Both Azure CLI and PowerShell
 
     ---
 
-    ::: zone pivot="python-mode-decorators" 
-    ::: zone-end
-
     > [!NOTE]
     > You can't host Linux and Windows apps in the same resource group. If you have an existing resource group named `AzureFunctionsQuickstart-rg` with a Windows function app or web app, you must use a different resource group.
 
 1. Create a general-purpose storage account in your resource group and region.
 
-    # [Azure CLI](#tab/azure-cli)
+    ### [Azure CLI](#tab/azure-cli)
 
     ```azurecli
     az storage account create --name <STORAGE_NAME> --location <REGION> --resource-group AzureFunctionsQuickstart-rg --sku Standard_LRS
     ```
 
     The [az storage account create](/cli/azure/storage/account#az-storage-account-create) command creates the storage account.
 
-    # [Azure PowerShell](#tab/azure-powershell)
+    ### [Azure PowerShell](#tab/azure-powershell)
 
     ```azurepowershell
     New-AzStorageAccount -ResourceGroupName AzureFunctionsQuickstart-rg -Name <STORAGE_NAME> -SkuName Standard_LRS -Location <REGION>
@@ -279,15 +182,15 @@ Use the following commands to create these items. Both Azure CLI and PowerShell
 
 1. Create the function app in Azure.
 
-    # [Azure CLI](#tab/azure-cli)
+    ### [Azure CLI](#tab/azure-cli)
 
     ```azurecli
     az functionapp create --resource-group AzureFunctionsQuickstart-rg --consumption-plan-location westeurope --runtime python --runtime-version <PYTHON_VERSION> --functions-version 4 --name <APP_NAME> --os-type linux --storage-account <STORAGE_NAME>
     ```
 
     The [az functionapp create](/cli/azure/functionapp#az-functionapp-create) command creates the function app in Azure. You must supply `--os-type linux` because Python functions only run on Linux.
 
-    # [Azure PowerShell](#tab/azure-powershell)
+    ### [Azure PowerShell](#tab/azure-powershell)
 
     ```azurepowershell
     New-AzFunctionApp -Name <APP_NAME> -ResourceGroupName AzureFunctionsQuickstart-rg -StorageAccountName <STORAGE_NAME> -FunctionsVersion 4 -RuntimeVersion <PYTHON_VERSION> -Runtime python -Location '<REGION>'
@@ -303,15 +206,29 @@ Use the following commands to create these items. Both Azure CLI and PowerShell
 
 [!INCLUDE [functions-publish-project-cli](../../includes/functions-publish-project-cli.md)]
 
-## Verify in Azure
+## Invoke the function on Azure
+
+Because your function uses an HTTP trigger, you invoke it by making an HTTP request to its URL in the browser or with a tool like curl. 
+
+### [Browser](#tab/browser)
+
+Copy the complete **Invoke URL** shown in the output of the `publish` command into a browser address bar, appending the query parameter `?name=Functions`. The browser should display similar output as when you ran the function locally.
+
+### [curl](#tab/curl)
+
+Run [`curl`](https://curl.haxx.se/) with the **Invoke URL** shown in the output of the `publish` command, appending the parameter `?name=Functions`. The output of the command should be the text, "Hello Functions."
+
+---
 
+<!--- // Re-enable this after this bug gets fixed: https://github.com/Azure/azure-functions-core-tools/issues/3609
 Run the following command to view near real-time streaming logs in Application Insights in the Azure portal.
 
 ```console
 func azure functionapp logstream <APP_NAME> --browser
 ```
 
 In a separate terminal window or in the browser, call the remote function again. A verbose log of the function execution in Azure is shown in the terminal.
+--->
 
 [!INCLUDE [functions-cleanup-resources-cli](../../includes/functions-cleanup-resources-cli.md)]
 

articles/azure-functions/create-first-function-vs-code-node.md

@@ -170,13 +170,20 @@ Use the following table to resolve the most common issues encountered when using
 [!INCLUDE [functions-cleanup-resources-vs-code.md](../../includes/functions-cleanup-resources-vs-code-extension.md)]
 
 ## Next steps
-
+<!--- Revert this after we get Node.js v4 support added to the follow-on quickstarts -->
+::: zone pivot="nodejs-model-v3"  
 You have used [Visual Studio Code](functions-develop-vs-code.md?tabs=javascript) to create a function app with a simple HTTP-triggered function. In the next article, you expand that function by connecting to either Azure Cosmos DB or Azure Storage. To learn more about connecting to other Azure services, see [Add bindings to an existing function in Azure Functions](add-bindings-existing-function.md?tabs=javascript). If you want to learn more about security, see [Securing Azure Functions](security-concepts.md).
 
 > [!div class="nextstepaction"]
 > [Connect to Azure Cosmos DB](functions-add-output-binding-cosmos-db-vs-code.md?pivots=programming-language-javascript)
 > [!div class="nextstepaction"]
 > [Connect to Azure Queue Storage](functions-add-output-binding-storage-queue-vs-code.md?pivots=programming-language-javascript)
+::: zone-end  
+::: zone pivot="nodejs-model-v4"  
+You have used [Visual Studio Code](functions-develop-vs-code.md?tabs=javascript) to create a function app with a simple HTTP-triggered function. 
 
+> [!div class="nextstepaction"]
+> [Learn more about JavaScript functions](./functions-reference-node.md)
+::: zone-end  
 [Azure Functions Core Tools]: functions-run-local.md
 [Azure Functions extension for Visual Studio Code]: https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurefunctions