Description:

Application: spring-cloud-gateway:Hoxton.SR3
Circuit-Breaker version: 1.0.2.RELEASE

As far as I can tell, yaml configurations are ignored. The provided ReactiveResilience4JCircuitBreakerFactory bean uses the default CircuitBreakerRegistry which only uses the hard-coded defaults. I tried creating my own ReactiveResilience4JCircuitBreakerFactory bean which uses the CircuitBreakerRegistry from here. However, spring-cloud-circuit-breaker seems to ignore resiliency4j configurations defined for the registry. I think that is because of this logic which pulls configurations from here; but it seems like configure is never called, so that configurations map is always empty. Therefore, it always falls back to the defaults.
As a result, every CircuitBreaker is created with those defaults. Does anyone know why the circuitBreaker(id, configs) method is being used instead of one of the other methods like circuitBreaker(id) which uses the configurations set for the CircuitBreakerRegistry?

Is there some existing logic I'm missing? If not would it be possible to change the implementation to support providing resilience4J configurations from application.yml?