@marowi I have the exact same position as you on this -- many clients always making changes, resulting in broken caches. And to be unable to clear FastCGI within WordPress is a a big headache for us, because we have to train them to how to do it via Enhance.
I've started on a work-around for this, which i'll admit, is a bit of a hack:
- Create a new server-side API endpoint specifically listening for FastCGI clearing requests
- The API endpoint then send a message to Enhance (via Enhance API) to clear the FastCGI cache for that website
- Write a lightweight MU plugin for WordPress that speaks directly to your custom API from step 1 to send that request.
The reason for the middleman? So you do not expose your Enhance API (and credentials!) to the WordPress website.
That's all I've got so far. I wish there was an easier way, and Enhance mentioned that it was something they could fix in another thread here, but have not implemented it yet.