Zuul2: Routing without using Eureka service discovery

Hello,

We want to use Zuul without service discovery, for instance, defining properties such as zuul.routes.books.url = http://localhost:8090/books, and routing accordingly with a custom filter. But, I can’t figure out how to disable eureka and perform routing via custom filters. zuul-core has dependencies to ribbon-eureka and eureka-client, and disabling eureka seems impossible to me.

Is it possible? OR Are you considering to release a zuul-without-eureka?

[mmdemirbas]

Thank you, it works.

My configuration (application.properties) is below, in the case someone else needs it:

### Instance env settings

region=us-east-1
environment=test

## Eureka instance registration for this app

Name of the application to be identified by other services
eureka.name=zuul

The port where the service will be running and serving requests
eureka.port=7001

Virtual host name by which the clients identifies this service
eureka.vipAddress=${eureka.name}:${eureka.port}

For eureka clients running in eureka server, it needs to connect to servers in other zones
eureka.preferSameZone=false

 Don't register locally running instances.
eureka.registration.enabled=false

# Loading Filters
zuul.filters.root=zuul-sample/src/main/groovy/com/netflix/zuul/sample/filters
zuul.filters.locations=${zuul.filters.root}/inbound,${zuul.filters.root}/outbound,${zuul.filters.root}/endpoint
zuul.filters.packages=com.netflix.zuul.filters.common

##########################################
## Everything above included in the sample.
## Everything below added by me.
##########################################

api.ribbon.listOfServers=localhost:8090
api.ribbon.client.NIWSServerListClassName=com.netflix.loadbalancer.ConfigurationBasedServerList

eureka.validateInstanceId=false
eureka.shouldFetchRegistry=false

zuul.server.port.main=9090

And inside Routes.apply() method (Routes is an HttpInboundSyncFilter included in the sample):

SessionContext context = request.getContext()
context.setEndpoint(ZuulEndPointRunner.PROXY_ENDPOINT_FILTER_NAME);
context.setRouteVIP("api")

[SMakhrov]

@BigSully, @artgon hi! Could you help please - why is it doesn’t work if url with multiple subdomains? Like this: test.s3-us-west-2.amazonaws.com:80

I see 301 Permanent redirect.