and also allow explicitly configured services to be unignored. I.e.
zuul:
ignoredServices: *
routes:
foo: /foo/**
Will expose only the foo service.
Fixes gh-198
@ -708,7 +708,22 @@ failures will show up in Hystrix metrics, and once the circuit is open
@@ -708,7 +708,22 @@ failures will show up in Hystrix metrics, and once the circuit is open
the proxy will not try to contact the service.
To skip having a service automatically added, set
`zuul.ignored-services` to a list of service ids. To augment or change
`zuul.ignored-services` to a list of service id patterns. If a service
matches a pattern that is ignored, but also included in the explicitly
configured routes map, then it will be unignored. Example:
.application.yml
[source,yaml]
----
zuul:
ignoredServices: *
routes:
users: /myusers/**
----
In this example, all services are ignored *except* "users".
To augment or change
the proxy routes, you can add external configuration like the
@ -107,7 +108,7 @@ public class ProxyRouteLocator implements RouteLocator {
@@ -107,7 +108,7 @@ public class ProxyRouteLocator implements RouteLocator {
prefix=prefix+routePrefix;
}
}
if(route.getRetryable()!=null){
if(route.getRetryable()!=null){
retryable=route.getRetryable();
}
break;
@ -122,19 +123,38 @@ public class ProxyRouteLocator implements RouteLocator {
@@ -122,19 +123,38 @@ public class ProxyRouteLocator implements RouteLocator {
@ -167,8 +187,8 @@ public class ProxyRouteLocator implements RouteLocator {
@@ -167,8 +187,8 @@ public class ProxyRouteLocator implements RouteLocator {
for(ZuulRouteentry:routeEntries.values()){
Stringroute=entry.getPath();
if(routes.containsKey(route)){
log.warn("Overwriting route "+route+": already defined by "+
routes.get(route));
log.warn("Overwriting route "+route+": already defined by "