Implement API Key Failover for Rate Limiting#4
Conversation
- Update `manifest.json` to use forked `idfm-api` with `RequestError` support. - Implement `MultiKeyIDFMApi` wrapper to handle key rotation on 429 errors. - Update `config_flow.py` and `__init__.py` to support comma-separated keys and use the wrapper. - Ensure `get_traffic`, `get_destinations`, `get_directions`, `get_line_reports` support failover. - Keep `get_lines` and `get_stops` as pass-through (Open Data, no key needed).
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Review changes with Changed Files
|
1 participant
This change implements a failover strategy for API keys to handle rate limiting (HTTP 429).
It introduces a
MultiKeyIDFMApiwrapper that accepts a list of API keys (comma-separated in config).When a 429 error is encountered during authenticated API calls (
get_traffic, etc.), the wrapper automatically rotates to the next available key and retries.The project dependency is updated to a specific git branch of
idfm-apithat exposes theRequestErrorexception with status codes.Unauthenticated calls (
get_lines,get_stops) remain unchanged as they do not use the API key.PR created automatically by Jules for task 11574969537721125545 started by @azman0101