Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Close the lambda's after limit is reached using DynamoDB event #112

Open
6 of 10 tasks
MehulKChaudhari opened this issue Jul 11, 2024 · 0 comments
Open
6 of 10 tasks

Close the lambda's after limit is reached using DynamoDB event #112

MehulKChaudhari opened this issue Jul 11, 2024 · 0 comments
Assignees
@MehulKChaudhari

Comments

@MehulKChaudhari
Copy link
Member

MehulKChaudhari commented Jul 11, 2024 •
edited
Loading

Issue Description

Now we set the reserved concurrency of Lambda's using code. But what we want is the reserved concurrency should be set zero if the pendingLimit is set zero as a side effect of it.

Current Behavior

Now we set the reserved concurrency of Lambda's using code.

Reproducibility

  • This issue is reproducible
  • This issue is not reproducible

Steps to Reproduce

  1. Open the repository
  2. check the file rateLimiterLambda/main.go

Severity/Priority

  • Critical
  • High
  • Medium
  • Low

Checklist

  • I have read and followed the project's code of conduct.
  • I have searched for similar issues before creating this one.
  • I have provided all the necessary information to understand and reproduce the issue.
  • I am willing to contribute to the resolution of this issue.
@MehulKChaudhari MehulKChaudhari self-assigned this Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MehulKChaudhari MehulKChaudhari

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MehulKChaudhari