aws-amplify
[Feature request] Ability to manually purge cached pages/urls
Is your feature request related to a problem? Please describe. According to this comment from AWS it's a feature that deleted files don't get purged from the cache until after several more builds. This can present problems for some (possibly even legal ones). I'm opening this up as a feature request, since it seems all the other issues relating to this are getting closed because it's a feature, not a bug.
Describe the solution you'd like Either via UI or through a configuration file/setting/api (preferably all of the aforementioned ways) a way to purge specific urls, or even the entire cache. It could even be a build-time setting. Cloudfront has UI and APIs for this, though not instant, it'd probably be acceptable.
Additional context Related issues: #74, #178, #294
I have a copyright lawyer after me to delete a file and I can't. This is a big problem.
I am also in hot water because I can't purge files that users have explicitly requested be removed from our platform, we have deleted them in the build but the cache still exists. Is there any short term workaround for this while we find a better solution?
@simpson @dhait @stefangomez we have picked this up on our priority list and will work on a fix. Will update when we have something ready.
Is this still being worked on? I just had to delete and re-create my app for updates in my React routing to work...
@swaminator Is there an update since you picked up this issue on the priority list? Needing to manually run 6 consecutive builds is not a feasible solution to remove a page from cache when, as others mentioned, there may be legal concerns. An update would be much appreciated.
