Release 4.1.0

• Adds support for homePageUrl #88

Release 4.0.0

This release offers many new features that will improve the resiliency and overall performance of the Eureka client.

New features:

• Improved strategies around cluster resolution (#68). Eureka cluster hosts can be statically configured per availability-zone using a map, or a list of hosts for simpler or non-zoned deployments.
• Zone affinity for DNS-based and static-based cluster configurations. By default, when the Node application is deployed in a zone-based datacenter (AWS, etc), the client will first try to connect to the Eureka server located in the same availability-zone as it's currently in. This behavior can be disabled through configuration.
• New middleware option for Eureka requests (#84). The client now exposes the ability to modify the outgoing request options object prior to a Eureka call. This is useful for setting authentication or other headers before the request is executed.

Breaking change:

• getInstancesByAppId and getInstancesByVipAddress now always return an array. If there are no instances in the registry you will get an empty array back instead of undefined. This change allows developers to chain .filter or .map onto the method call without having to check for undefined.

Other Notes:

• Even with all the new code, coverage is still up 2% to +96%. Thanks to everyone who helped build/test these features!

Release 3.1.2

• Adds exception handling around malformed or missing JSON content while fetching the full registry. The module already checked for a 200 status, but this will just protect against other server-related or network issues.

Release 3.1.1

• Updating the module to use lodash/merge due to this issue: TehShrike/deepmerge#28

Release 3.1.0

• #65 DNS lookups can now be used for locating a Eureka server in non-AWS datacenters.

Release 3.0.0

• Added better exception handling around malformed YAML configuration files.
• Added support for the following events: started, registered, deregistered, heartbeat, and registryUpdated.
• Improved the stability of the client when it encounters downstream DNS errors, as a side-effect the callback for fetchRegistries() now returns errors when they are encountered.
• Populate registry cache with instances that have a status of UP, filterUpInstances can be set to false to disable.