Azure.Functions.Cli.Workloads.ExtensionBundles

Azure Functions CLI – Extension Bundles workload

This package ships the Azure Functions extension bundle payload for the func CLI. It is a content workload (Workload Spec §3, §5.3): the package carries files only, with no entry-point assembly and no runtime services. func start resolves the install directory by package id and reads the bundle layout directly.

The bundle payload version is encoded directly in the workload pkg version (1:1 mapping; this is a content-only workload, so there is no separate workload code to version).

The prerelease label, when present, names the channel. func always reports the 3-part bundle version (4.35.0) in user-facing logs.

Install

func workload install [email protected]
# or by alias
func workload install [email protected]

Multiple bundle versions coexist via --force (Workload Spec §4.6).

Build-time channel selection

The CDN bundle id used at pack time is driven by $(BundleChannel) in Directory.Version.props:

dotnet pack ... /p:BundleChannel=preview
dotnet pack ... /p:BundleChannel=experimental

Layout

The package places the bundle payload under tools/any/<BundleVersion>/ so the on-disk layout matches what the host's ExtensionBundleManager expects to probe (<downloadPath>/<version>/...). After install:

<workload-home>/workloads/azure.functions.cli.workloads.extensionbundles/<version>/
  tools/any/
    <BundleVersion>/         ← extension bundle root (bin/, extensions.json, ...)
  workload.json

The CLI bundle resolver sets downloadPath to <install>/tools/any/ and the host walks the <BundleVersion>/ child for the requested version. tools/any/ is the canonical content-workload payload path.

Links

• Azure Functions CLI
• Workload spec
• Bundles workload spec