5.4.3

[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.

Docker images

• docker pull launchdarkly/ld-relay:5.4.3
• docker pull launchdarkly/ld-relay:v5
• docker pull launchdarkly/ld-relay:latest

5.4.2

[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)

Docker images

• docker pull launchdarkly/ld-relay:5.4.2
• docker pull launchdarkly/ld-relay:v5
• docker pull launchdarkly/ld-relay:latest

5.4.1

[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.

Docker images

• docker pull launchdarkly/ld-relay:5.4.1
• docker pull launchdarkly/ld-relay:v5
• docker pull launchdarkly/ld-relay:latest

5.4.0

[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.

Docker images

• docker pull launchdarkly/ld-relay:5.4.0
• docker pull launchdarkly/ld-relay:v5
• docker pull launchdarkly/ld-relay:latest

5.3.1

[5.3.1] - 2018-08-03

Fixed

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

Docker images

• docker pull launchdarkly/ld-relay:5.3.1
• docker pull launchdarkly/ld-relay:v5
• docker pull launchdarkly/ld-relay:latest

5.3.0

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

[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.

5.1.0

[5.1.0] - 2018-06-25

Added

• /status endpoint includes version and clientVersion fields for the relay and go client versions respectively.

Changed

• Official package has moved to gopkg.in/launchdarkly/ld-relay.v5
• Binary target is gopkg.in/launchdarkly/ld-relay.v5/cmd/ld-relay
• gopkg.in/launchdarkly/ld-relay.v5 is now a package that can be used as library code and includes the Relay object with implements http.Handler so you can roll your own relay.

5.0.0

[5.0.0] - 2018-05-29

Changed:

• Instead of the configuration option apiKey, please use sdkKey. It has the same function, but is less misleading (since it is really an SDK key, not an API token).
• The /status endpoint now returns environments as a map of configuration name to details/status. It also no longer exposes full SDK keys so this endpoint should be safe to expose publicly.

Fixed:

• Support for the OPTIONS method for /sdk/goals/{envId} was restored after being accidentally dropped in 4.1.0.

Deprecated:

• The configuration option apiKey is now deprecated, but will still work if there is no sdkKey.

4.1.1

Fixed: Fix JS streaming by sending an empty data field in ping events