Fix: Synchronize MKPs to slave sites in distributed WATO setup #789
+8
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
General information
All local uploaded packages are stored in this directory. This directory is not synchronized to slave sites.
Bug reports
All versions are affected by this issue, because synchronization is same on all editions.
Create a distributed setup with master and slave. Do a login on slave site. MKPs are not
shown on Extention packages sites or with mkp list in terminal.
Proposed changes
If those MKPs are uploaded on master site, they should also be available on slave site the same way. If slave is reconfigured to be standalone, all is correct and MKPs can also be used. Otherwise they must all be uploaded again.