Skip to content

Latest commit

 

History

History
76 lines (47 loc) · 3.48 KB

CHANGELOG.md

File metadata and controls

76 lines (47 loc) · 3.48 KB
Raw

Change log

All notable changes to the LaunchDarkly Relay will be documented in this file. This project adheres to Semantic Versioning.

[5.5.0] - 2018-11-27

Added

  • The relay now supports additional database integrations: Consul and DynamoDB. As with the existing Redis integration, these can be used to store feature flags that will be read from the same database by a LaunchDarkly SDK client (as described here), or simply as a persistence mechanism for the relay itself. See README.MD for configuration details.
  • It is now possible to specify a Redis URL in $REDIS_URL, rather than just $REDIS_HOST and $REDIS_PORT, when running the Relay in Docker. (Thanks, lukasmrtvy!)

Fixed

  • When deployed in a Docker container, the relay no longer runs as the root user; instead, it creates a user called ldr-user. Also, the configuration file is now in /ldr instead of in /etc. (Thanks, sdif!)

[5.4.4] - 2018-11-19

Fixed

  • Fixed a bug that would cause the relay to hang after the LaunchDarkly client finished initializing, if you had previously queried any relay endpoint before the client finished initializing (e.g. if there was a delay due to network problems and you checked the status resource during that delay).

[5.4.3] - 2018-09-97

Added

  • Return flag evaluation reasons for mobile and client-side endpoints when withReasons=true query param is set.
  • Added support for metric collection configuration in docker entrypoint script. Thanks @matthalbersma for the suggestion.

Fixes

  • Fix internal relay metrics event field.

[5.4.2] - 2018-08-29

Changed

  • Use latest go client (4.3.0).
  • Preserves the "client-side-enabled" property of feature flags so that the new SDK method AllFlagsState() - which has an option for selecting only client-side flags - will work correctly when using the relay.

Fixes

  • Ensure that server-side eval endpoints don't panic (work around gorilla mux bug)

[5.4.1] - 2018-08-24

Fixed

  • Strip trailing slash that was breaking default urls for polling and streaming.
  • If set X-LaunchDarkly-User-Agent will be used instead of the User-Agent header for metrics.
  • Documentation improvements.

[5.4.0] - 2018-08-09

Added

  • The Relay now supports the streaming endpoint used by current mobile SDKs. It does not fully proxy the stream, but will send an event causing mobile SDKs to re-request their flags when flags have changed.

[5.3.1] - 2018-02-03

Fixed

  • Route metrics are now tagged correctly with the route name.
  • Datadog exporter now works with 32-bit builds.

[5.3.0] - 2018-07-30

Added

  • The Relay now supports exporting metrics and traces to Datadog, Prometheus, and Stackdriver. See the README for configuration instructions.

Changed

  • Packages intended for internal relay use are now marked as internal and no longer accessible exsternally.
  • The package is now released using goreleaser.

[5.2.0] - 2018-07-13

Added

  • The Redis server location-- and logical database-- can now optionally be specified as a URL (url property in [redis] section) rather than a hostname and port.
  • The relay now sends usage metrics back to LaunchDarkly at 1-minute intervals.

Fixed

  • The /sdk/goals/ endpoint now supports caching and repeats any headers it received to the client.