At present, when updating the configuration on a deployed template, the default is to start all of the processors, or none of the processors (when the -noStartProcessors command-line argument is passed). However, it would be useful if the configuration JSON allowed the processors to land in a state of one's choosing (started, stopped, or disabled).
At present, when updating the configuration on a deployed template, the default is to start all of the processors, or none of the processors (when the
-noStartProcessorscommand-line argument is passed). However, it would be useful if the configuration JSON allowed the processors to land in a state of one's choosing (started, stopped, or disabled).