Implement Configure Max Requests

Problem/Motivation

In our environment, content edit tickets often lead to hundreds of node paths in the Purge queue. Processing only 100 queued paths at a time is less efficient given that CloudFront has a limit of 3,000 active invalidations at a time.

Proposed resolution

The Varnish purger → module already implements a user configurable value for max requests that allows users to configure a value other than 100 without impacting the dynamically calculated capacity.

Remaining tasks

Test patch

User interface changes

Adds a "Max Requests" field to the Purger configuration screen, with a limit of 3,000.

API changes

None.

Data model changes

Addition of a max_requests key in the existing cloudfront_purger.settings data.