Hey there,
I'm working on implementing Cloudflare purging for a high-traffic site that's hosted on Acquia cloud. We've had Acquia purge working for a long time, and it's working well, but when I try to stack the Cloudflare purger on top of it, it creates a situation... Cloudflare implements a diagnostic check that returns an error when the Cloudflare API rate limit is exceeded. Because diagnostics are checked once, globally, this means that all purging stops the moment we hit the rate limit (including Acquia purging). For our use case, we need the system to continue purging Acquia (which has a very long cache lifetime), even if Cloudflare can't be purged. I don't think this needs to be UI configurable, but I do think it should be possible.

Issue fork purge-3062616

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

rbayliss created an issue. See original summary.

japerry made their first commit to this issue’s fork.

japerry opened merge request !84

  • japerry committed 9f26c686 on 8.x-3.x 
    fix: #3062616 Only block the purgers a failing diagnostic check is bound...
japerry’s picture

japerry
Location KOMK
commented
Status: Active » Fixed

Confirmed the bug on 8.x-3.x. PurgersService throws for any diagnostic check that reports an error, without looking at the check's dependent_purger_plugins, so one rate-limited purger stops every other purger too.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.