Reputation: 8203
I have created a Azure Durable function with targetframework:.NET Core 3.1, which gets triggered whenever an entry is added to the Azure Queue which in turn invokes the Orchestrator function. This Orchestrator function triggers other activity functions which are part of a workflow process. While running this application in my local development environment with all the settings managed in local.settings.json, I noticed some additional Queues and Blob containers are getting created in the Azure portal.
Azure Queue:
Azure Blob Containers:
Can anyone help me to resolve this issue?
Upvotes: 1
Views: 652
Reputation: 29780
Can anyone help me to resolve this issue?
There is no issues, this is by design:
Azure Storage is the default storage provider for Durable Functions. It uses queues, tables, and blobs to persist orchestration and entity state. It also uses blobs and blob leases to manage partitions. In many cases, the storage account used to store Durable Functions runtime state is the same as the default storage account used by Azure Functions (AzureWebJobsStorage).
You can however specify a seperate storage account to be used by the framework if you want:
However, it's also possible to configure Durable Functions with a separate storage account. The Azure Storage provider is built-into the Durable Functions extension and doesn't have any other dependencies.
(source)
There is also the option to use a different storage provider.
Upvotes: 2