[MGNLSYNC-55] Config references nonexisting publishing config on public instance Created: 15/Jan/21 Updated: 06/Oct/22 |
|
| Status: | Open |
| Project: | Magnolia Synchronization Module |
| Component/s: | None |
| Affects Version/s: | 1.9.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Viet Nguyen | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| 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)
|
||||
| Testcase included: |
Yes
|
||||
| Documentation update required: |
Yes
|
||||
| Epic Link: | Maintenance of Synchronization module | ||||
| Team: | |||||
| Description |
|
For customers who don't use Synchronization module, an error log printed out when public instance startup "Can't find referenced node for value: node /modules/synchronization-core/commands/synchronization/synchronize/receivers" because they don't have any receivers in public instance. Also it is hard for customer to remove the module because it affect the build process and consistency of code base between author and public instance. So would be better if we have a mechanism to disable synchronization module on startup. |