Replies: 1 comment
-
I could get things working by adding the following host configuration:
And in the local.settings.json the AzureWebJobsStorage and DurableConnection are exactly the same: But I just cannot get my head around this. It seems that when running locally the storage always defaults to development storage unless the storageProvider settings is actively set in host.json to something else than AzureWebJobsStorage. However when deployed it is enough to set the "AzureWebJobsStorage" app setting and no need to specify the connectionStringName, the app setting is honoured. Is this a bug? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to enable Azurite via HTTPS and keep getting this error. The function did work while using HTTP protocol for Azurite.
Since then the following has been made:
The error I get:
For me it looks like the Task Hub cannot be created and I pretty much suspect that the HttpClient in the DurableTask is not accepting the SSL certificate. How could I get over this problem?
The main idea with using Azurite via HTTPS is to be able to run a function locally that programmatically creates a BlobContainerClient with DefaultAzureCredentials, and not need to do tricks for dev / prod runs
Beta Was this translation helpful? Give feedback.
All reactions