Azure.Functions.Cli.Workloads.Host.win-arm64 4.1048.200-preview.1

Azure Functions CLI - Host workload

Content workload that ships a small Azure Functions host shell and the host payload consumed by the Azure Functions CLI when running function apps locally.

Install

func workload install Azure.Functions.Cli.Workloads.Host.<rid>
# or by alias
func workload install host

Note: released packages are RID-specific, for example Azure.Functions.Cli.Workloads.Host.win-x64. The CLI resolves the current RID package internally; end users should normally install/manage the workload by the shorter alias host.

Status

Preview. The shell expects the Azure Functions CLI to prepare the process environment and command-line arguments before launch. It does not translate private CLI configuration into host settings. Local builds are framework-dependent by default.

Release packaging should be performed with a RID-specific self-contained payload under tools/any/ by passing -p:PackRidSpecificHostWorkload=true -r <rid> -p:SelfContained=true, which also suffixes the package id with the RID. The self-contained executable must be placed at tools/any/Azure.Functions.Cli.Workloads.Host on Unix-like platforms and tools/any/Azure.Functions.Cli.Workloads.Host.exe on Windows.

Launch contract

The workload executable is a thin bootstrapper around the packaged Azure Functions Host. It supports one shell-specific command-line option; every other argument passed to the workload executable is forwarded unchanged to the host.

The Azure Functions CLI is responsible for resolving the RID-specific workload package, setting the process working directory, overlaying prepared environment variables, and building host arguments before launching the workload process. The working directory and AzureWebJobsScriptRoot environment variable both point to the prepared function app startup directory.

For local CLI/host iteration, set FUNC_HOST_CONTENT_ROOT to a built host content root that contains Azure.Functions.Cli.Workloads.Host(.exe) and workers/workers.txt. The CLI then skips workload resolution/installation and launches that local content root through the normal start pipeline.

The shell does not support private CLI options such as --script-root, --port, --cors, --cors-credentials, or --functions. The CLI should resolve those concepts before process launch and express them using the host's expected environment/configuration surface.

Diagnostics

The workload writes the normal stdout/stderr host event stream as newline-delimited JSON records with source: "azure-functions-cli-host" and schema_version: 1. The CLI parses those records before falling back to plain line output. Records may include dashboard attributes such as cli.event_kind, host.state, function.name, function.invocation_id, HTTP request details, and function metadata snapshots emitted after host startup.

Set FUNC_HOST_RAW_LOG_CAPTURE_PATH to an absolute file path to capture raw host ILogger records as newline-delimited JSON. This is a diagnostic-only capture file used to inspect category, level, event id, structured state, scopes, and exception data without changing the stdout/stderr stream consumed by the CLI.