@omkar20xx1 wrote:
Though this talks about invalidating single URL as such.
That is correct, the outlined solution is only taking care of a single path. You could build up on it and iterate through multiple paths, though. (That's what I was referring to as "batch processing" in my initial answer.) Be aware of the load this might cause on both ends, AEM and the CDN, though.
@omkar20xx1 wrote:
Any header or pattern that gives a complete flush or soft purge for CDN.
I'm not aware of an option for a complete cache purge on CDN level. While the Fastly API does provide different purge options, all of them are targeted at specific parts of the cached content. I'm not an in-depth Fastly expert but would assume that there simply might be no option for a complete purge - which makes perfect sense as the approach to caching and cache invalidation usually works differently (with TTLs being the recommended way to handle cache invalidation on that level).
@omkar20xx1 wrote:
Any method or class which invalidates entire dispatcher cache like giving a root path or something within the SCD API
Invalidating the Dispatcher cache is certainly possible. For AEM 6.5 (on-premise or AMS), this can easily be achieved by deleting files from the caching folder on the files system or sending a request to the dispatchers invalidation endpoint.
For AEM CS, things get a bit more tricky but you should still be able to leverage some of the techniques from this page. Especially the Flush Servlet might come in handy, although it would need some modifications to achieve this - and potentially also some batch processing.
The other important question is if this is a one-off thing you need or if your aim is to clear the cache on a regular basis. For the latter, you might want to re-evaluate the statsfile level option. Also, I'd highly recommend to re-evaluate the underlying requirement for a repeated complete cache deletion as this is an anti-pattern. For regular setups of AEM, this should not be needed and is not recommended.
Hope this helps!
