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.

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

Update Rate Limit for getLivdData Azure Function #16657

Open
3 of 9 tasks
arnejduranovic opened this issue Nov 24, 2024 · 0 comments
Open
3 of 9 tasks

Update Rate Limit for getLivdData Azure Function #16657

arnejduranovic opened this issue Nov 24, 2024 · 0 comments
Labels
DevSecOps Team Aq DevSecOps work label reportstream

Comments

@arnejduranovic
Copy link
Collaborator

arnejduranovic commented Nov 24, 2024

DevSecOps Issue

Summary

getLivdData is an Azure Function with HTTPTrigger that provides the client a dump of our LIVD table. To enforce that this endpoint should not get called often because the data rarely changes, we should update the rate limit to 2 call per 5 minutes.

Environment

  • Local
  • Dev
  • Stage
  • Prod

Priority

  • Critical - affecting prod systems
  • Major - blocking major functionality, deployment, etc
  • Minor - improvements, bug fixes
  • Nice-to-have - feature request

Blocks the following

  • NA

Blocked by the following

  • NA

Contact

Team: Platform

Slack Contact (Full Name): @arnejduranovic

Technical Team Lead: @arnejduranovic

How to Reproduce

Screenshots, links, etc. for context

How to Test

Definition of Done

  • Rate limit for getLivdData Azure Function updated for Prod and Staging envs

Context Links

Git Repo:

Relevant Code Links:

Azure: Prod: https://prime.cdc.gov/api/metadata/livd

Site URL:

Other:

Notes

  • Presently, we are getting this endpoint called hundreds of times an hour by seemingly only a few callers.
@arnejduranovic arnejduranovic added reportstream DevSecOps Team Aq DevSecOps work label labels Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DevSecOps Team Aq DevSecOps work label reportstream
Projects
None yet
Development

No branches or pull requests

1 participant