Skip to content

feat(offline-dynamodb-streams): add retries option#100

Closed
dolsem wants to merge 1 commit into
CoorpAcademy:masterfrom
dolsem:offline-dynamodb-streams-retries-option
Closed

feat(offline-dynamodb-streams): add retries option#100
dolsem wants to merge 1 commit into
CoorpAcademy:masterfrom
dolsem:offline-dynamodb-streams-retries-option

Conversation

@dolsem

@dolsem dolsem commented Oct 23, 2019

Copy link
Copy Markdown

This PR adds a config option to specify number of retries for the lambda function in case of failure.

@sang2087

Copy link
Copy Markdown

I want this feature, too. I hope to merge this PR.

@sang2087

sang2087 commented Nov 5, 2019

Copy link
Copy Markdown

why this PR was not merged? do you have any plan to merge this issue? @CoorpAcademyAdmin

silouone added a commit that referenced this pull request Jun 19, 2026
…nt-def fixes

- Serverless v4 logger migration (src/log.js shim threaded in; handler errors are now logged instead of silently swallowed).
- Fix undefined this.region -> this.options.region so emitted events carry awsRegion. Re-implements #166 (thanks @zlalvani).
- Replace the infinite silent handler retry with a bounded, logged retry (default maximumRetryAttempts=10, mirrors dynamodb-streams). Re-implements #100 (thanks @dolsem).
- Await this.lambda.create(...). Re-implements #249 (thanks @gabsong).
- Fix kinesis-event-definition omit list (tableName -> streamName copy-paste bug).
- Backward compatible with serverless v3. Adds docker-free unit tests. v7.1.0.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@silouone

Copy link
Copy Markdown
Member

Thanks again @dolsem — your retries option was a great idea, and #265 implements bounded, logged retry handling across serverless-offline-kinesis and serverless-offline-dynamodb-streams. It's on master now and ships in the next release of those packages, alongside Serverless Framework v4 support; note our test/CI harness now runs on osls (the community license-free fork of Serverless v3) so the dev/CI loop stays free and open while the plugins still support v4. Closing in favor of #265 with thanks 🙏

@silouone silouone closed this Jun 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants