Skip to content

Ingest API: Implement rate limiting#18

Draft
abdullah-kasim wants to merge 51 commits intotrunkfrom
vip-2487-ingest-api-implement-ratelimiting
Draft

Ingest API: Implement rate limiting#18
abdullah-kasim wants to merge 51 commits intotrunkfrom
vip-2487-ingest-api-implement-ratelimiting

Conversation

@abdullah-kasim
Copy link
Contributor

Description

This PR adds rate limiting. On-hold as we prioritize bulk-syncing to work first.

Pre-review checklist

Please make sure the items below have been covered before requesting a review:

  • This change works and has been tested locally or in Codespaces (or has an appropriate fallback).
  • This change has relevant unit tests (if applicable).
  • This change has relevant documentation additions / updates (if applicable).
  • I've created a changelog description that aligns with the provided examples.

Pre-deploy checklist

  • VIP staff: Ensure any alerts added/updated conform to internal standards (see internal documentation).

Steps to Test

abdullah-kasim and others added 30 commits December 3, 2025 16:54
…rce_post_ingestion_complete-action

feat: `vip_agentforce_post_ingestion_failed` hook to catch failed ingestions.
…r' into vip-2470-ingest-api-handle-deletions-through-wp-cli-commands
Resolved conflicts:
- Kept upstream fire_ingestion_failure() signature (post_id, failure_code, details)
- Removed Logger calls from ingestion methods (as per original task)
- Preserved API implementation changes
…clean-up-logs-and-implement-pr-recommendations-in
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Base automatically changed from vip-2488-part-2-ingest-api-actual-deletion-calls to trunk January 11, 2026 00:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant