When importing a versioned process group from the registry, all the components will be stopped (in case of update, only the newly added components will be stopped). We already have a command pg-start to start a process group, but it will fail if the process group relies on controller services that should be enabled first.
A new command like pg-enable-cs could be added, or just add a parameter/flag to the pg-start command.
Things to consider:
- there can be a dependency chain between the controller services requiring to start the controller services in the right order. Example: the avro schema registry CS and a reader/writer CS depending on the schema registry CS.
- there can be a CS defined at pg level that is not referenced by any component inside the pg but that would need to be started nevertheless. Example: the distributed map cache server CS.