UseAzureAppConfiguration and AzureAppConfigurationRefreshMiddleware break context execution

Open

#915 opened on May 10, 2024 19 comments 8 reactions 1 assignee View on GitHub

@amerjusupovic is already working on this.

Since May 10, 2024.

Assessment

This issue has not been assessed yet.

Description

.NET Config Provider question

I have detected that if we make use of ‘UseAzureAppConfiguration’, which in turn internally injects the middleware ‘AzureAppConfigurationRefreshMiddleware’, it breaks the execution of the context of the Eternal Orchestration Functions.

I am using Azure Isolated Function in NET 8, using package ‘Microsoft.Azure.AppConfiguration.Functions.Worker’ in version 7.2.0.

The middleware internally performs an ‘ExecutionContext.SuppressFlow()’, which breaks the execution flow of the context: https://learn.microsoft.com/en-us/dotnet/api/system.threading.executioncontext.suppressflow?view=net-8.0

Right now the solution I am applying is to use ‘AddAzureAppConfiguration’ without ‘UseAzureAppConfiguration’. In my orchestrator constructor I inject ‘IConfigurationRefresherProvider’ to use the configuration refresher in the orchestrator activities.

The problem is not described anywhere and should be checked. Thanks in advance.

Dominant language: No language data
Stars: 263
Forks: 82
Avg merge: 3d 15h
Merged PRs (30d): 6

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

UseAzureAppConfiguration and AzureAppConfigurationRefreshMiddleware break context execution

Assessment

Description

Contributor guide

First steps

More from Azure/AppConfiguration

Get new issues in your inbox