azure-functions-core-tools
azure-functions-core-tools copied to clipboard
wrong task hub name is used for durable functions 2.x with durable commands
Version
4.0.5907
Description
using any durable function command defaults the task-hub-name parameter of those commands to DurableFunctionsHub.
DurableFunctionsHub is the default task hub name in Durable Functions 1.x only.
https://github.com/MicrosoftDocs/azure-docs/blob/561b5b43606212719112cf3d6125af91241a6828/includes/functions-host-json-durabletask.md?plain=1#L104
if ran against a Durable Functions 2.x project, the default TestHubName, is not picked up and resources are created in the storage account named according to DurableFunctionsHub and the requests aren't processed by the function app.
Steps to reproduce
create a .net8 isolated function app from the visual studio template with a durable function selected as the function for the template
broken
run func durable start-new --function-name Function1
observe Function1 never starts and it created the resources in your storage account
workaround 1
run func durable start-new --function-name Function1 --task-hub-name TestHubName
observe Function1 running to completion
workaround 2
set extensions:durableTask:hubName to "TestHubName" (which is the default)
run func durable start-new --function-name Function1
observe Function1 running to completion