Open danielniccoli opened 1 year ago
Hey @danielniccoli - thank you for this report. Could you do me a favor and ping me offline on my twitter @paulyuki99? I have a follow up question. Paul - from Azure team
Hi @paulyuk, I don't have a Twitter account. I could contact you through the email address on your profile, if you like.
When working with Azure Durable Functions, Azurite is usually involved. If for some reason you have to change the ports that Azurite is listening on in
settings.json
as shown here ...... one also must modify
local.settings.json
to inform the locally running azure functions host to connect to the new Azurite ports. This includes having to know the exact connection string details, including a public predefined password.So the simple JSON key-value pair
must be replaced by this very verbose line
My suggestion is that the azurite listening configuration (e.g.,
azurite.blobPort
) is passed to the functions host when set.Implementation approach
The setting
UseDevelopmentStorage=True
is the short-hand forDefaultEndpointsProtocol=http;AccountName=devstoreaccount1;AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;BlobEndpoint=http://127.0.0.1:10000/devstoreaccount1;QueueEndpoint=http://127.0.0.1:10001/devstoreaccount1;TableEndpoint=http://127.0.0.1:10002/devstoreaccount1;
. (The AccountKey is pre-defined as well and taken from the Microsoft docs!)local.settings.json
containsUseDevelopmentStorage=True
settings.json
contains azurite listenening settings.local.settings.json
valueI don't know the function host enough to know if that would work, so I'll just leave it here.