[MGNLCACHE-190] Backport: Flush cache when new light-module resources are pushed to the server Created: 11/Dec/17 Updated: 16/Jan/18 Resolved: 16/Jan/18 |
|
| Status: | Closed |
| Project: | Cache Modules |
| Component/s: | cache core |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Ervin Vystup | Assignee: | Roman Kovařík |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| 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)
|
||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Story Points: | 5 | ||||||||||||||||
| Description |
|
During pushing resources to an app server would be good to flush a cache memory to reflect made changes after updating in Magnolia. |
| Comments |
| Comment by Antti Hietala [ 16/Jan/18 ] |
|
This feature won't be backported to Magnolia 5.5 or earlier branches. The feature is available in Magnolia 5.6 as If you are unable to upgrade to 5.6 you can accomplish the same functionality by executing the flushAll caches command via the commands REST endpoint. You can incorporate an automatic cache flush into your deployment process, for example by triggering a flush on pulling changed content from Git. |