[HASSETS-8] Hybrid assets / S3: browser should auto-refresh content Created: 03/Sep/20 Updated: 12/Jan/21 |
|
| Status: | Open |
| Project: | Hybrid Assets |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Critical |
| Reporter: | Thomas Comiotto | Assignee: | Andrew Warinner |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
The hybrid asset file picker and the S3 app should auto-refresh remote content when you browse files - at least when you open the app / dialog. In a scenario where users upload and manage files with a dedicated client (cyberduck, transfer, s3cmd), you are forced to go to the S3 app and do a manual refresh every time work with hybrid assets because the local S3 tree might be out of sync with the server. |
| Comments |
| Comment by Andrew Warinner [ 17/Sep/20 ] |
|
Will implement a "targeted" flush of the S3 cache associated with the S3 credentials (not all S3 caches) before opening the link asset dialog and the edit asset dialog. Once implemented, I will put a snapshot release into the AWS test environment so we can assess its performance impact.
|
| Comment by Thomas Comiotto [ 12/Jan/21 ] |
|
Hi Andrew, Best wishes,
|