Cloudinary Storage: Old image returned after replacing/editing about directus

[sethkaufee]

First off, thank you all for getting #22551 out so quickly!

Our team is experiencing caching issues after editing a photo with Cloudinary as a backend. It is my understanding a temporary file is created and then "moved" (renamed) to the original asset. If the Cloudinary docs are accurate, we can use an invalidate parameter to ensure the asset fetched is up to date. Without contacting Cloudinary support, the editing feature will likely seem broken when Cloudinary is used as a backend.

The Cloundary upload API Documentation states the invalidate param is supported in most API calls, but, as @rijkvanzanten may know, the Cloudinary docs leave a lot to be desired.

My initial thoughts on solutions if the invalidate param solves the issue would be:

1. Add invalidate=true on move.
2. Add a storage configuration option for the Cloudinary driver to always (or on certain methods) pass this param.
3. Some combination of 1 + 2.

Let me know what y'all think!

[cesar-augusto-ramirez]

If the issue is caused by caching, and the caching issue is caused by Directus' use of signed URLs, I believe it would make sense to toogle using/not using signed URLs based on the public status of the Cloudinary setup (i.e. STORAGE_<LOCATION>_ACCESS_MODE)

Just my 2 cents, thanks for the amazing support!