As a Beta Cluster maintainer
I want to allow networks used by trusted contributors to pass through large range blocks established to reduce damage from aggressive crawlers
So that the folks who depend on Beta to validate correct technical implementations can perform their work.
<dancy> This stuff would be a lot easier if there were an allowlist of IPs that was processed before abuse_networks.As discussed in tasks like T392003: High load on deployment-mediawiki14 and slow responses and on the wikitech-l mailing list, the edge CDN for the Beta Cluster wikis has been making use of abuse_networks:blocked_nets:networks to block larger and larger IPv4 address blocks while fighting aggressive crawlers. This works in that it can turn back unwanted traffic without too much work. It is a failure, or at least an unwanted obstacle, when these wide blocks catch traffic from community members who are trying to use Beta to get various forms of work done. We currently have folks doing CIDR math to split larger blocks to leave open holes for smaller networks that known trusted contributors are using. @dancy wisely noted that it would be a bit simpler if we could add the blocks we want to trust to an explicit allow list that would exempt them from the larger blocks.