Currently synchronization assumes that all public instances are out of sync and tries to synchronize all existing ones. This, together with time necessary to run synchronization prevents possibility of synchronizing publics one-by-one as they come up.

Scenario:
The scenario is that you want to trigger sync over rest from headless env. it’s not human doing the invocation but a bot.

Proposed solution:

• separate synchronization configuration from publishing configuration
• allow each job to have configuration provided either by parameters or be able to use unique per-job configuration by other means (e.g. having multiple configurations for subscribers under module configuration and referencing them by configuration name from the job)
• prevent execution of multiple synchronizations against same public instance, while allowing multiple synchronization jobs to run at the same time.