anchor.diff:  spring.cloud.gateway.discovery.locator.predicates[0].args[pattern]: "'/'+serviceId+'/**'"
   spring.cloud.gateway.discovery.locator.predicates[1].name: Host
   spring.cloud.gateway.discovery.locator.predicates[1].args[pattern]: "'**.foo.com'"
  -spring.cloud.gateway.discovery.locator.filters[0].name: Hystrix
  +spring.cloud.gateway.discovery.locator.filters[0].name: CircuitBreaker
   spring.cloud.gateway.discovery.locator.filters[0].args[name]: serviceId
   spring.cloud.gateway.discovery.locator.filters[1].name: RewritePath
   spring.cloud.gateway.discovery.locator.filters[1].args[regexp]: "'/' + serviceId + '/(?<remaining>.*)'"
  
positive.code: To configure the circuit breaker, see the configuration for the underlying circuit breaker implementation you are using.
  
  * https://cloud.spring.io/spring-cloud-circuitbreaker/reference/html/spring-cloud-circuitbreaker.html[Resilience4J Documentation]
  * https://cloud.spring.io/spring-cloud-netflix/reference/html/[Hystrix Documentation]
  
  The Spring Cloud CircuitBreaker filter can also accept an optional `fallbackUri` parameter.
  Currently, only `forward:` schemed URIs are supported.
  
negative.code: === Spring Cloud CircuitBreaker GatewayFilter Factory
  
  The Spring Cloud CircuitBreaker GatewayFilter factory uses the Spring Cloud CircuitBreaker APIs to wrap Gateway routes in
  a circuit breaker. Spring Cloud CircuitBreaker supports multiple libraries that can be used with Spring Cloud Gateway. Spring Cloud supports Resilience4J out of the box.
  
  To enable the Spring Cloud CircuitBreaker filter, you need to place `spring-cloud-starter-circuitbreaker-reactor-resilience4j` on the classpath.
  The following example configures a Spring Cloud CircuitBreaker `GatewayFilter`:
  
  .application.yml
  