Unable to run "func durable..." commands when using hubName set in local.settings.json

[AHarman]

Description

When hubName in host.json is set to a string like %TaskHubName% commands run locally that start with "func durable" always return the following message:

Invalid container name. Check MSDN for more information about valid container naming.

Expected behavior

The command to run normally, having retrieved the hubName value from the app settings.

Actual behavior

The command does not run, and instead returns the error message Invalid container name. Check MSDN for more information about valid container naming.

Relevant source code snippets

host.json:

{
  "version": "2.0",
  "logging": {
    "fileLoggingMode": "always",
    "logLevel": {
      "default": "Information"
    }
  },
  "extensions": {
    "durableTask": {
      "hubName": "%TaskHubName%"
    }
  }
}

Known workarounds

Using a "normal" value for hubName

{
  "version": "2.0",
  "logging": {
    "fileLoggingMode": "always",
    "logLevel": {
      "default": "Information"
    }
  },
  "extensions": {
    "durableTask": {
      "hubName": "mylocalhubname"
    }
  }
}

App Details

• Durable Functions extension version (e.g. v1.8.3): v2.1.1
• Azure Functions runtime version (1.0 or 2.0): 2.0
• Programming language used: C#

[fabiocav]

Flagging this as a feature request.

[pratyushaadavalli]

@fabiocav do you have any ETA for this?

[jyeblog]

I had moved to Function App 2.0 to resolve the racing issue of TaskHub. And the recommendation is to change "hubName" to "%TaskHubName%".

However, this is breaking my local development experience, please address this issue, thanks!

[ctrl-brk]

Any ETA on this?

[mronnblom-ith]

This is still an issue with latest versions of Azure Functions Core Tools and an Azure Durable FunctionApp, .Net 8 isolated.