### Summary I keep triggering redsky's rate limit. it'd be nice to avoid that w/o any intervention on my part ### Proposed Solution add a wait timer between requests. configure the rate limit to be in reference to an environment variable. ### Alternative change the user agent for each request, but that seems shady ### Requirements - [ ] can call an excess of 600 requests w/o triggering a 'not authenticated' error - [ ] test validates the time between calls can be manipulated by defined env. var. ### Additional Context - https://search.gov/indexing/robotstxt.html - https://redsky.target.com/robots.txt - ~~I assume many failed gh-actions runs on main fail because the PR just prior to it ran too many calls in a short time.~~ ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](../blob/main/CODE_OF_CONDUCT.md)
Summary
I keep triggering redsky's rate limit. it'd be nice to avoid that w/o any intervention on my part
Proposed Solution
add a wait timer between requests. configure the rate limit to be in reference to an environment variable.
Alternative
change the user agent for each request, but that seems shady
Requirements
Additional Context
I assume many failed gh-actions runs on main fail because the PR just prior to it ran too many calls in a short time.Code of Conduct