Well, this is a breaking change as you are modifying the API endpoint. There needs to be a related web PR.

Web: pi-hole/web#3553

Core: pi-hole/pi-hole#6319

I'm still unsure how we should handle this. It does remove an API endpoint which is unlikely to be used by external scripts but it is also not impossible. We could maybe have both, /api/action/flush/arp and /api/action/flush/network doing the same thing and say the former is deprecated and will be removed in a future release? This mostly shifts the "breaking" issue into the future, however, it does at least give maintainers of such scripts some time for mitigation/migration of their scripts.

We could maybe have both, /api/action/flush/arp and /api/action/flush/network doing the same thing and say the former is deprecated and will be removed in a future release?

Yep - agree this is the correct way to do it

Added /action/flush/arp back and set it to deprecated. I would have expected, the documentation still shows the endpoint but marks it as deprecated. However, it's not shown at all on

https://ftl.pi-hole.net/arp/network/docs/

. However, it's not shown at all on

???

Nice. Must have been a timing issue or browser cache issue.

I think this is good to go but I made a few comments on the related core PR. I plan to test this myself over the next days.

I think this triad of PRs is ready. However, I see @dschaper labeled the core repo one as waiting for next point release so I am not starting merging here as I'm unsure where we are in the release cycle. I plan to work on the static DHCP thing but I cannot promise when (if) I can finish this soon

Core PR pi-hole/pi-hole#6319 has been merged.