FeatureManager in ASP.NET Core Web API about featuremanagement-dotnet HOT 8 CLOSED

Hello @wen-git-acc,

This is expected behavior from the Azure App Configuration configuration provider. This is because the provider is designed to perform a refresh when a request is made, but it is done in parallel to the request to avoid slowing the request down. There are a few downsides that arise from deviating from this model. Can you explain a bit the problem that this is causing so I may offer a suggestion?

from featuremanagement-dotnet.

Hi @jimmyca15

Based on our design, the desktop application will be querying the API to retrieve set of feature status during the start up. It means that the user have to boot up the application twice in order to retrieve latest feature state (if any feature is toggled on azure portal), which is not ideal in our use case. Hence, I am looking if there is any work around to request the latest change update instead of sending request twice to retrieve the latest state.

from featuremanagement-dotnet.

While looking through previous few issues post, understand that we could not disable caching. Is there any way for me to refresh configuration in every request on purpose so that my IsEnabledAsync could have query the latest change from azure config service?

Besides, I have found this url, curious to know that does it works on feature flag items and will it increase cost of using azure config service since we are making more request.

from featuremanagement-dotnet.

Hi, is there any update on this?

from featuremanagement-dotnet.

Is there any way for me to refresh configuration in every request on purpose so that my IsEnabledAsync could have query the latest change from azure config service?

Yes. You can call IConfigurationProvider.RefreshAsync during the request pipeline and await it. This will ensure that the refresh completes before your code evaluates the flag. The refresh will still be subject to the configured cache interval.

This has the downsides that I mentioned that now the requests success and response time is now dependent upon the success of the refresh operation.

from featuremanagement-dotnet.

Hello @wen-git-acc, does this solve the issue?

from featuremanagement-dotnet.

@wen-git-acc The suggested approach should be able to solve the issue. Please feel free to re-open if anything is missed.

from featuremanagement-dotnet.

Hi @jimmyca15 , sorry missed out to reply. For your information, the above method only work without use azure configuration middleware :) Definitely solved my issue, thanks for your help

from featuremanagement-dotnet.