TASK: IGDB ETL – Batch Fetch Full Records (Rate Limit Aware)

[AndersonGACFilho]

Summary

Take the list of updated game IDs and fetch the full records from IGDB in batches, while respecting the API's rate limits.

Details

• The IGDB API allows fetching multiple records at once by providing a list of IDs.
• The fetching logic must include a mechanism (e.g., a small delay between requests) to avoid hitting the rate limit.

Acceptance Criteria

• The ETL can fetch full game records for a given list of IDs.
• The ETL includes a simple delay or token bucket implementation to manage the request rate.
• Tests updated/added (unit/integration)
• No linter / build errors

Dependencies

• IGDB ETL – Fetch Updated IDs > watermark

Out of Scope

• Processing or storing the fetched data.

Test Plan

• Write a test that provides a list of IDs and mocks the IGDB API to verify that the ETL makes batched requests and includes a delay.

Checklist

• Labels added (task, component/igdb-etl)
• CHANGELOG updated if user-visible
• No secrets committed