Skip to content

Commit 13d3198

Browse files
Update Changelog for release of version 6.7.0
1 parent cf490d3 commit 13d3198

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

CHANGELOG.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,14 @@
22

33
All notable changes to the LaunchDarkly Python SDK will be documented in this file. This project adheres to [Semantic Versioning](http://semver.org).
44

5+
## [6.7.0] - 2019-01-15
6+
### Added:
7+
- It is now possible to use DynamoDB as a persistent feature store, similar to the existing Redis integration. See `DynamoDB` in `ldclient.integrations`, and the reference guide to ["Using a persistent feature store"](https://docs.launchdarkly.com/v2.0/docs/using-a-persistent-feature-store).
8+
- The new class `CacheConfig` (in `ldclient.feature_store`) encapsulates all the parameters that control local caching in database feature stores. This takes the place of the `expiration` and `capacity` parameters that are in the deprecated `RedisFeatureStore` constructor; it can be used with DynamoDB and any other database integrations in the future, and if more caching options are added to `CacheConfig` they will be automatically supported in all of the feature stores.
9+
10+
### Deprecated:
11+
- The `RedisFeatureStore` constructor in `ldclient.redis_feature_store`. The recommended way to create a Redis feature store now is to use `Redis.new_feature_store` in `ldclient.integrations`.
12+
513
## [6.6.0] - 2018-11-14
614
### Added:
715
- It is now possible to inject feature flags into the client from local JSON or YAML files, replacing the normal LaunchDarkly connection. This would typically be for testing purposes. See `file_data_source.py`.

0 commit comments

Comments
 (0)