All notable changes to the LaunchDarkly Go SDK Redis integration will be documented in this file. This project adheres to Semantic Versioning.
- Added support for SDK v7 to support technology migrations.
- When using Big Segments, do not log a database error if the Big Segments status data has not yet been populated.
- When using Big Segments, do not log a database error if the Big Segments status data has not yet been populated.
This release corresponds to the 6.0.0 release of the LaunchDarkly Go SDK. Any application code that is being updated to use the 6.0.0 SDK, and was using a 1.x version of go-server-sdk-redis-redigo
, should now use a 2.x version instead.
There are no functional differences in the behavior of the Redis integration; the differences are only related to changes in the usage of interface types for configuration in the SDK.
BigSegmentStore()
, which creates a configuration builder for use with Big Segments. Previously, theDataStore()
builder was used for both regular data stores and Big Segment stores.
- The type
RedisDataStoreBuilder
has been removed, replaced by a generic typeRedisStoreBuilder
. Application code would not normally need to reference these types by name, but if necessary, use eitherRedisStoreBuilder[PersistentDataStore]
orRedisStoreBuilder[BigSegmentStore]
depending on whether you are configuring a regular data store or a Big Segment store.
- When logging the Redis URL at startup, if the URL contains a password it is replaced by
xxxxx
(the same behavior as Go'sURL.Redacted()
).
- Added support for Big Segments. An Early Access Program for creating and syncing Big Segments from customer data platforms is available to enterprise customers.
DataStoreBuilder.PoolInterface()
is equivalent to.Pool()
, but allows specifying the connection pool as an interface type rather than the concrete*Pool
type from Redigo. (Thanks, rafaeljusto!)
Initial release of the stand-alone version of this package to be used with versions 5.0.0 and above of the LaunchDarkly Server-Side SDK for Go.