Gathering detailed insights and metrics for serverless-offline-dynamodb-streams-handler
Gathering detailed insights and metrics for serverless-offline-dynamodb-streams-handler
Installations
npm install serverless-offline-dynamodb-streams-handlerDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Min. Node Version
>=10.0
Releases
Unable to fetch releases
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
Maintainers
1
Package Meta Information
Latest Version
1.0.1
Package Id
serverless-offline-dynamodb-streams-handler@1.0.1
Unpacked Size
54.86 kB
Size
12.27 kB
File Count
23
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
serverless-offline-dynamodb-streams-handler
This plugin acts as a bridge between the Serverless Offline and DynamoDB Local plugins to provide DynamoDB streams functionality for to your Serverless Offline stacks.
It is inspired by an earlier plugin: serverless-offline-dynamodb-streams
Supported Features
- DynamoDB Streams events
- Typescript
- Event Filtering
Installation
1npm install serverless-offline-dynamodb-streams-handler
In your serverless.yml:
1plugins: 2 - serverless-offline-dynamodb-streams-handler
Configuration
1plugins: 2 - serverless-offline-dynamodb-streams-handler 3custom: 4 serverless-offline-dynamodb-streams-handler: 5 endpoint: http://localhost:8000 # Required - dynamodb local endpoint 6 tableNames: # Optional. See below for explanation of table names mapping 7 tableKey1: tableName1 8 tableKey2: tableName2
Table Names
- If you are using only string ARNS, the plugin will be able to extract the table names from the ARN.
- If you are using a Ref function, the plugin will scan your resources to locate the table
- However, if you are using a cross stack reference, you must provide a mapping in the
tableNamesconfiguration block
The entry value should be the dynamo table name and the key should be the name of the cross stack reference after interpolation. For example, given the following event mapping and having stage set to 'dev':
1handler: src/handler.handler 2events: 3- stream: 4 arn: !ImportValue ${self:provider.stage}StreamArn 5 type: dynamodb 6 batchSize: 10 7 startingPosition: TRIM_HORIZON
The import value key would resolve to "devStreamArn" so the tableNames block would be as follows:
1custom: 2 serverless-offline-dynamodb-streams-handler: 3 tableNames: 4 devStreamArn: my-dynamo-table
Usage with Typescript
In order for the plugin to correctly locate your transpiled handlers, set the 'location' property of serverless-offline This should be compatible with a number of transpilers that put transpiled code in a separate build directory (tested with the serverless-esbuild plugin)
1custom: 2 serverless-offline: 3 location: .esbuild/.build
Filter Patterns
See the Filter Patterns Guide
No vulnerabilities found.
No security vulnerabilities found.