Kinesis keeps running...

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript

Research direction

Start by locating the Kinesis process and the CloudWatch deletion handling in this repository, then reproduce the case where CloudWatch is deleted. Trace why the process remains running and verify that it stops after the deletion event; add or update a regression test if the repository provides one.

Written by the indexing model from the issue text.

Description

Kinesis process will not stop after CloudWatch was deleted

Dominant language
JavaScript
Stars
344
Forks
127
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws-samples/lambda-refarch-streamprocessing

All issues in aws-samples/lambda-refarch-streamprocessing

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.