You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
3. If your application does not already have its own dependency on the `@aws-sdk/client-dynamodb` package, and if it will _not_ be running in AWS Lambda, add `@aws-sdk/client-dynamodb` as well:
33
33
@@ -38,28 +38,28 @@ The `launchdarkly-node-server-sdk-dynamodb` package does not provide `@aws-sdk/c
By default, the DynamoDB client will try to get your AWS credentials and region name from environment variables and/or local configuration files, as described in the AWS SDK documentation. You can also specify any valid [DynamoDB client options](https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/DynamoDB.html#constructor-property) like this:
7. If the same DynamoDB table is being shared by SDK clients for different LaunchDarkly environments, set the `prefix` option to a different short string for each one to keep the keys from colliding:
75
75
76
76
```typescript
77
-
const store =DynamoDBFeatureStoreFactory('YOUR TABLE NAME', { prefix: 'env1' });
77
+
const store =DynamoDBFeatureStore('YOUR TABLE NAME', { prefix: 'env1' });
78
78
```
79
79
80
80
## Caching behavior
81
81
82
82
To reduce traffic to DynamoDB, there is an optional in-memory cache that retains the last known data for a configurable amount of time. This is on by default; to turn it off (and guarantee that the latest feature flag data will always be retrieved from DynamoDB for every flag evaluation), configure the store as follows:
0 commit comments