[CLOUDINARY-50] Uploading asset in Cloudinary doesn't refresh the cache Created: 07/Dec/23  Updated: 12/Jan/24  Resolved: 02/Jan/24

Status: Closed
Project: Cloudinary DAM Connector
Component/s: None
Affects Version/s: 1.1.15
Fix Version/s: 1.1.17

Type: Bug Priority: Neutral
Reporter: Raphael Falvo Assignee: Raphael Falvo
Resolution: Fixed Votes: 0
Labels: Integration-Testing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Work Started:
Approved:
Yes

 Description   

When uploading an asset from cloudinary dam browser, the asset is not visible right after the upload in the browser view. It becomes visible only after a while, most likely after the period of caching defined.

Uploading an asset shall evict the cache to make sure asset is immediately visible.

 

Proposed resolution :

uploadMedia method in CloudinaryServiceImpl shall have the same evict mechanism as deleteMediaById method

https://git.magnolia-cms.com/projects/INCUBATOR/repos/cloudinary-parent/browse/cloudinary-dam-connector/src/main/java/info/magnolia/external/dam/cloudinary/service/CloudinaryServiceImpl.java#17,111,156-159



 Comments   
Comment by Raphael Falvo [ 11/Dec/23 ]

The problem persists with the cloud instance (integration-tests demo), while it works properly on the local setup.
Kindly reopen the matter for a deeper investigation into the underlying cause of this difference in behavior.

Comment by Teresa Miyar [ 02/Jan/24 ]

followed up on cloudinary-56

Generated at Mon Feb 12 00:00:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.