• Implement a blocklist mechanism to reject requests and Kafka messages based on org_id

We recently received an unusally high number of playbook run request from and internal Red Hat account. This ultimately led to a huge kafka lag and a high portion of our DB storage being used up.

We weren't able to find a reason for this high number of requests from an internal account, so we are assuming this was caused by some faulty script.

Having a blocklist mechanism to reject API requests as well as kafka messages will help us respond to these sort of situation faster.