Merge pull request #285458 from ggailey777/patch-4

[Functions] Reformat H2 refs in Core Tools ref

Author: prmerger-automator[bot]

articles/azure-functions/functions-core-tools-reference.md

@@ -4,7 +4,7 @@ description: Reference documentation that supports the Azure Functions Core Tool
 ms.topic: reference
 ms.custom:
   - ignite-2023
-ms.date: 08/22/2024
+ms.date: 08/20/2023
 ---
 
 # Azure Functions Core Tools reference
@@ -26,7 +26,7 @@ Core Tools commands are organized into the following contexts, each providing a
 
 Before using the commands in this article, you must [install the Core Tools](functions-run-local.md#install-the-azure-functions-core-tools). 
 
-## func init 
+## `func init`
 
 Creates a new Functions project in a specific language.
 
@@ -55,7 +55,7 @@ When you supply `<PROJECT_FOLDER>`, the project is created in a new folder with
 > [!NOTE]
 > When you use either `--docker` or `--docker-only` options, Core Tools automatically create the Dockerfile for C#, JavaScript, Python, and PowerShell functions. For Java functions, you must manually create the Dockerfile. For more information, see [Creating containerized function apps](functions-how-to-custom-container.md#creating-containerized-function-apps).
 
-## func logs
+## `func logs`
 
 Gets logs for functions running in a Kubernetes cluster.
 
@@ -72,7 +72,7 @@ The `func logs` action supports the following options:
 
 To learn more, see [Azure Functions on Kubernetes with KEDA](functions-kubernetes-keda.md).
 
-## func new
+## `func new`
 
 Creates a new function in the current project based on a template.
 
@@ -94,7 +94,7 @@ The `func new` action supports the following options:
 
 To learn more, see [Create a function](functions-run-local.md#create-func).
 
-## func run
+## `func run`
 
 *Version 1.x only.*
 
@@ -120,13 +120,13 @@ For example, to call an HTTP-triggered function and pass content body, run the f
 func run MyHttpTrigger --content '{\"name\": \"Azure\"}'
 ```
 
-## func start
+## `func start`
 
 Starts the local runtime host and loads the function project in the current folder. 
 
 The specific command depends on the [runtime version](functions-versions.md).   
 
-# [v2.x+](#tab/v2)
+### [v2.x+](#tab/v2)
 
 ```command
 func start
@@ -152,7 +152,7 @@ func start
 
 With the project running, you can [verify individual function endpoints](functions-run-local.md#run-a-local-function).
 
-# [v1.x](#tab/v1)
+### [v1.x](#tab/v1)
 
 ```command
 func host start
@@ -173,48 +173,26 @@ In version 1.x, you can also use the [`func run`](#func-run) command to run a sp
 
 ---
 
-## func azure functionapp fetch-app-settings
+## `func azure functionapp fetch-app-settings`
 
 Gets settings from a specific function app.
 
 ```command
 func azure functionapp fetch-app-settings <APP_NAME> 
 ```
 
-`func azure functionapp fetch-app-settings` supports these optional arguments:
-
-| Option     | Description                            |
-| ------------ | -------------------------------------- |
-| **`--access-token`** | Lets you use a specific access token when performing authenticated `azure` actions. |
-| **`--access-token-stdin `** | Reads a specific access token from a standard input. Use this when reading the token directly from a previous command such as [`az account get-access-token`](/cli/azure/account#az-account-get-access-token). |
-| **`--management-url`** | Sets the management URL for your cloud. Use this when running in a sovereign cloud. |
-| **`--slot`** | Optional name of a specific slot to which to publish. |
-| **`--subscription`** | Sets the default subscription to use. |
-
 For more information, see [Download application settings](functions-run-local.md#download-application-settings).
 
 Settings are downloaded into the local.settings.json file for the project. On-screen values are masked for security. You can protect settings in the local.settings.json file by [enabling local encryption](functions-run-local.md#encrypt-the-local-settings-file). 
 
-## func azure functionapp list-functions
+## `func azure functionapp list-functions`
 
 Returns a list of the functions in the specified function app.
 
 ```command
 func azure functionapp list-functions <APP_NAME>
 ```
-
-`func azure functionapp list-functions` supports these optional arguments:
-
-| Option     | Description                            |
-| ------------ | -------------------------------------- |
-| **`--access-token`** | Lets you use a specific access token when performing authenticated `azure` actions. |
-| **`--access-token-stdin `** | Reads a specific access token from a standard input. Use this when reading the token directly from a previous command such as [`az account get-access-token`](/cli/azure/account#az-account-get-access-token). |
-| **`--management-url`** | Sets the management URL for your cloud. Use this when running in a sovereign cloud. |
-| **`--show-keys`** | Shows HTTP function endpoint URLs that include their default access keys. These URLs can be used to access function endpoints with `function` level [HTTP authentication](functions-bindings-http-webhook-trigger.md#http-auth). | 
-| **`--slot`** | Optional name of a specific slot to which to publish. |
-| **`--subscription`** | Sets the default subscription to use. |
-
-## func azure functionapp logstream
+## `func azure functionapp logstream`
 
 Connects the local command prompt to streaming logs for the function app in Azure.
 
@@ -224,20 +202,15 @@ func azure functionapp logstream <APP_NAME>
 
 The default timeout for the connection is 2 hours. You can change the timeout by adding an app setting named [SCM_LOGSTREAM_TIMEOUT](functions-app-settings.md#scm_logstream_timeout), with a timeout value in seconds. Not yet supported for Linux apps in the Consumption plan. For these apps, use the `--browser` option to view logs in the portal.
 
-The `func azure functionapp logstream` command supports these optional arguments:
+The `deploy` action supports the following options:
 
 | Option     | Description                            |
 | ------------ | -------------------------------------- |
-| **`--access-token`** | Lets you use a specific access token when performing authenticated `azure` actions. |
-| **`--access-token-stdin `** | Reads a specific access token from a standard input. Use this when reading the token directly from a previous command such as [`az account get-access-token`](/cli/azure/account#az-account-get-access-token). |
 | **`--browser`** | Open Azure Application Insights Live Stream for the function app in the default browser. |
-| **`--management-url`** | Sets the management URL for your cloud. Use this when running in a sovereign cloud. |
-| **`--slot`** | Optional name of a specific slot to which to publish. |
-| **`--subscription`** | Sets the default subscription to use. |
 
 For more information, see [Enable streaming execution logs in Azure Functions](streaming-logs.md).
 
-## func azure functionapp publish 
+## `func azure functionapp publish`
 
 Deploys a Functions project to an existing function app resource in Azure. 
 
@@ -269,7 +242,6 @@ The following publish options apply, based on version:
 | **`--overwrite-settings -y`** | Suppress the prompt to overwrite app settings when `--publish-local-settings -i` is used.|
 | **`--publish-local-settings -i`** |  Publish settings in local.settings.json to Azure, prompting to overwrite if the setting already exists. If you're using a [local storage emulator](functions-develop-local.md#local-storage-emulator), first change the app setting to an [actual storage connection](#func-azure-storage-fetch-connection-string). |
 | **`--publish-settings-only`**, **`-o`** |  Only publish settings and skip the content. Default is prompt. |
-| **`--show-keys`** | Shows HTTP function endpoint URLs that include their default access keys. These URLs can be used to access function endpoints with `function` level [HTTP authentication](functions-bindings-http-webhook-trigger.md#http-auth). | 
 | **`--slot`** | Optional name of a specific slot to which to publish. |
 | **`--subscription`** | Sets the default subscription to use. |
 
@@ -283,7 +255,7 @@ The following publish options apply, based on version:
 
 ---
 
-## func azure storage fetch-connection-string    
+## `func azure storage fetch-connection-string`
 
 Gets the connection string for the specified Azure Storage account.
 
@@ -293,7 +265,7 @@ func azure storage fetch-connection-string <STORAGE_ACCOUNT_NAME>
 
 For more information, see [Download a storage connection string](functions-run-local.md#download-a-storage-connection-string).
 
-## func azurecontainerapps deploy    
+## `func azurecontainerapps deploy`
 
 Deploys a containerized function app to an Azure Container Apps environment. Both the storage account used by the function app and the environment must already exist. For more information, see [Azure Container Apps hosting of Azure Functions](functions-container-apps-hosting.md). 
 
@@ -326,11 +298,11 @@ The following deployment options apply:
 > [!IMPORTANT]
 > Storage connection strings and other service credentials are important secrets. Make sure to securely store any script files using `func azurecontainerapps deploy` and don't store them in any publicly accessible source control. 
 
-## func deploy
+## `func deploy`
 
 The `func deploy` command is deprecated. Instead use [`func kubernetes deploy`](#func-kubernetes-deploy).
 
-## func durable delete-task-hub
+## `func durable delete-task-hub`
 
 Deletes all storage artifacts in the Durable Functions task hub.
 
@@ -347,7 +319,7 @@ The `delete-task-hub` action supports the following options:
 
 To learn more, see the [Durable Functions documentation](./durable/durable-functions-instance-management.md#delete-a-task-hub).
 
-## func durable get-history
+## `func durable get-history`
 
 Returns the history of the specified orchestration instance.
 
@@ -365,7 +337,7 @@ The `get-history` action supports the following options:
 
 To learn more, see the [Durable Functions documentation](./durable/durable-functions-instance-management.md#azure-functions-core-tools-1).
 
-## func durable get-instances
+## `func durable get-instances`
 
 Returns the status of all orchestration instances. Supports paging using the `top` parameter.
 
@@ -387,7 +359,7 @@ The `get-instances` action supports the following options:
 
 To learn more, see the [Durable Functions documentation](./durable/durable-functions-instance-management.md#azure-functions-core-tools-2).
 
-## func durable get-runtime-status  
+## `func durable get-runtime-status`
 
 Returns the status of the specified orchestration instance.
 
@@ -407,7 +379,7 @@ The `get-runtime-status` action supports the following options:
 
 To learn more, see the [Durable Functions documentation](./durable/durable-functions-instance-management.md#azure-functions-core-tools-1).
 
-## func durable purge-history
+## `func durable purge-history`
 
 Purge orchestration instance state, history, and blob storage for orchestrations older than the specified threshold.
 
@@ -427,7 +399,7 @@ The `purge-history` action supports the following options:
 
 To learn more, see the [Durable Functions documentation](./durable/durable-functions-instance-management.md#azure-functions-core-tools-7).
 
-## func durable raise-event         
+## `func durable raise-event`
 
 Raises an event to the specified orchestration instance.
 
@@ -447,7 +419,7 @@ The `raise-event` action supports the following options:
 
 To learn more, see the [Durable Functions documentation](./durable/durable-functions-instance-management.md#azure-functions-core-tools-5).
 
-## func durable rewind              
+## `func durable rewind`
 
 Rewinds the specified orchestration instance.
 
@@ -466,7 +438,7 @@ The `rewind` action supports the following options:
 
 To learn more, see the [Durable Functions documentation](./durable/durable-functions-instance-management.md#azure-functions-core-tools-6).
 
-## func durable start-new
+## `func durable start-new`
 
 Starts a new instance of the specified orchestrator function.
 
@@ -486,7 +458,7 @@ The `start-new` action supports the following options:
 
 To learn more, see the [Durable Functions documentation](./durable/durable-functions-instance-management.md#azure-functions-core-tools).
 
-## func durable terminate
+## `func durable terminate`
 
 Stops the specified orchestration instance.
 
@@ -505,7 +477,7 @@ The `terminate` action supports the following options:
 
 To learn more, see the [Durable Functions documentation](./durable/durable-functions-instance-management.md#azure-functions-core-tools-4).
 
-## func extensions install
+## `func extensions install`
 
 Manually installs Functions extensions in a non-.NET project or in a C# script project. 
 
@@ -547,7 +519,7 @@ The following considerations apply when using `func extensions install`:
 
 + The first time you explicitly install an extension, a .NET project file named extensions.csproj is added to the root of your app project. This file defines the set of NuGet packages required by your functions. While you can work with the [NuGet package references](/nuget/consume-packages/package-references-in-project-files) in this file, Core Tools lets you install extensions without having to manually edit this C# project file.
 
-## func extensions sync
+## `func extensions sync`
 
 Installs all extensions added to the function app.
 
@@ -561,7 +533,7 @@ The `sync` action supports the following options:
 
 Regenerates a missing extensions.csproj file. No action is taken when an extension bundle is defined in your host.json file.
 
-## func kubernetes deploy
+## `func kubernetes deploy`
 
 Deploys a Functions project as a custom docker container to a Kubernetes cluster.
 
@@ -600,7 +572,7 @@ Core Tools uses the local Docker CLI to build and publish the image. Make sure y
 
 To learn more, see [Deploying a function app to Kubernetes](functions-kubernetes-keda.md#deploying-a-function-app-to-kubernetes).
 
-## func kubernetes install
+## `func kubernetes install`
 
 Installs KEDA in a Kubernetes cluster.
 
@@ -620,7 +592,7 @@ The `install` action supports the following options:
 
 To learn more, see [Managing KEDA and functions in Kubernetes](functions-kubernetes-keda.md#managing-keda-and-functions-in-kubernetes).
 
-## func kubernetes remove
+## `func kubernetes remove`
 
 Removes KEDA from the Kubernetes cluster defined in the kubectl config file.
 
@@ -638,7 +610,7 @@ The `remove` action supports the following options:
 
 To learn more, see [Uninstalling KEDA from Kubernetes](functions-kubernetes-keda.md#uninstalling-keda-from-kubernetes).
 
-## func settings add
+## `func settings add`
 
 Adds a new setting to the `Values` collection in the [local.settings.json file].
 
@@ -654,7 +626,7 @@ The `add` action supports the following option:
 | ------------ | -------------------------------------- |
 | **`--connectionString`** | Adds the name-value pair to the `ConnectionStrings` collection instead of the `Values` collection. Only use the `ConnectionStrings` collection when required by certain frameworks. To learn more, see [local.settings.json file]. |
 
-## func settings decrypt
+## `func settings decrypt`
 
 Decrypts previously encrypted values in the `Values` collection in the [local.settings.json file].
 
@@ -664,7 +636,7 @@ func settings decrypt
 
 Connection string values in the `ConnectionStrings` collection are also decrypted. In local.settings.json, `IsEncrypted` is also set to `false`. Encrypt local settings to reduce the risk of leaking valuable information from local.settings.json. In Azure, application settings are always stored encrypted. 
 
-## func settings delete
+## `func settings delete`
 
 Removes an existing setting from the `Values` collection in the [local.settings.json file].
 
@@ -680,7 +652,7 @@ The `delete` action supports the following option:
 | ------------ | -------------------------------------- |
 | **`--connectionString`** | Removes the name-value pair from the `ConnectionStrings` collection instead of from the `Values` collection. |
 
-## func settings encrypt
+## `func settings encrypt`
 
 Encrypts the values of individual items in the `Values` collection in the [local.settings.json file].
 
@@ -690,7 +662,7 @@ func settings encrypt
 
 Connection string values in the `ConnectionStrings` collection are also encrypted. In local.settings.json, `IsEncrypted` is also set to `true`, which specifies that the local runtime decrypts settings before using them. Encrypt local settings to reduce the risk of leaking valuable information from local.settings.json. In Azure, application settings are always stored encrypted. 
 
-## func settings list
+## `func settings list`
 
 Outputs a list of settings in the `Values` collection in the [local.settings.json file]. 
 
@@ -706,7 +678,7 @@ The `list` action supports the following option:
 | ------------ | -------------------------------------- |
 | **`--showValue`** | Shows the actual unmasked values in the output. |
 
-## func templates list
+## `func templates list`
 
 Lists the available function (trigger) templates.