RemoveAllResilienceHandlers is marked as experimental.
However it is documented to be used in case of scenario's where you can want to diverge from the defaults: https://learn.microsoft.com/en-us/dotnet/core/resilience/http-resilience?tabs=dotnet-cli#remove-standard-resilience-handlers
This is especially notable when using Aspire which defines it as default in its ServiceDefaults, and for cases where for some you need to override, and thus remove existing, you have to suppress the warning/error.
If possible it would be great to have the experimental removed, as this also means for some applications it cannot be used due internal policies, while it is referred to as the way to go.
Without it either some weird patterns came into play when using the Aspire, or even some attempting to do what the extension does (and never update it)
RemoveAllResilienceHandlersis marked as experimental.However it is documented to be used in case of scenario's where you can want to diverge from the defaults: https://learn.microsoft.com/en-us/dotnet/core/resilience/http-resilience?tabs=dotnet-cli#remove-standard-resilience-handlers
This is especially notable when using Aspire which defines it as default in its ServiceDefaults, and for cases where for some you need to override, and thus remove existing, you have to suppress the warning/error.
If possible it would be great to have the experimental removed, as this also means for some applications it cannot be used due internal policies, while it is referred to as the way to go.
Without it either some weird patterns came into play when using the Aspire, or even some attempting to do what the extension does (and never update it)