[MGNLSYNC-36] Add support for configuration of synchronization source (version vs current content) Created: 05/Jan/18 Updated: 11/Jan/23 |
|
| Status: | Open |
| Project: | Magnolia Synchronization Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jan Haderka | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | to-estimate | ||
| 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)
|
||||
| Epic Link: | Maintenance of Synchronization module | ||||
| Team: | |||||
| Description |
|
There are cases like when version store is corrupted or when versioning scheme is different than the default one which might make sync module take wrong content and activate it. E.g. in DAM versioning strategy is on modification, not on activation hence latest version of the content, might not be the one we want to activate, but current one might be better match when activated. Thus it would be beneficial to optionally configure whether to activate latest activated version, current content or use custom to-be-synchroned-content-selection-strategy. |