Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prepare 6.1.6 release #136

Merged
merged 665 commits into from
Apr 23, 2021
Merged

prepare 6.1.6 release #136

merged 665 commits into from
Apr 23, 2021

Conversation

LaunchDarklyCI
Copy link
Contributor

[6.1.6] - 2021-04-23

Fixed:

  • In automatic configuration mode, if a new credential was created for an already-configured environment (for instance, by using "reset SDK key" on the LaunchDarkly dashboard), the Relay Proxy did not accept subsequent SDK requests using the new credential until the next time the Relay Proxy was started. The symptom was that the SDK endpoints would return a 404 status instead of 200 (even though unknown credentials normally receive a 401). Also, if an SDK key or mobile key had already been changed prior to starting the Relay Proxy, but the older key had not yet expired, the Relay Proxy was not recognizing the old key in requests. Both of these problems have been fixed.
  • Fixed a broken link in the Metrics documentation page. (Thanks, natashanwright!)

eli-darkly and others added 30 commits July 29, 2020 12:42
support new filtering properties for client-side/mobile flags
This reverts commit 885691b.
(v6 - #7) reorganization and expansion of readme content
(v6 - #8) use configtypes library for config validation
(v6 - #9) create RelayCore and move most of the core logic into it
(v6 - #10) logic for adding/removing environments dynamically
(v6 - #11) factor out application startup code
(v6 - #12) cleaner encapsulation of stream logic
LaunchDarklyCI and others added 25 commits December 4, 2020 18:43
There is some additional information provided in the response body for certain 504 error codes and this should allow us to see it.
* improve metrics documentation and fix route strings in docs

* clarify mobile + browser terminology
environment should still be usable even if the client timed out
recognize alias events from non-v3-schema payloads and forward them unchanged
update go-server-sdk-dynamodb to get newer AWS SDK
LaunchDarklyCI pushed a commit that referenced this pull request Apr 23, 2021
@eli-darkly eli-darkly requested a review from bwoskow-ld April 23, 2021 21:57
@LaunchDarklyCI LaunchDarklyCI merged commit bdf0a4b into v6 Apr 23, 2021
@LaunchDarklyCI LaunchDarklyCI deleted the release-6.1.6 branch April 23, 2021 22:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants