question: child process-composes

[dzmitry-lahoda]

Currently all processes are merged and run by single process compose. There is no "direct" way to unmerge.

I have deps set of processes. And want to launch a lot more, as part of tests. This will make process compose list huge. Will it make PC slow? For example I have 100 tests, each configured and merged to start, each test may be 1 or 2 processes, so can up 150 names in PC.

Update allows to "unmrege", but not clear if it is scalable(hundreds of tests), nor it forces parts to be properly independence/isolated.

Alternative for "update", could be that there is main process compose. And child process compose depend on it and can reference it. Child can be shutdown after test finished. Child can depend on main process compose, but no other way around.

Allowing namespacing to be first class could help either #378

[dzmitry-lahoda]

@F1bonacc1 what do you think?

[dzmitry-lahoda]

I think that making:

add namespace - adds all process configs in namespace - fails if at least one same name process exists
remove namespace - removes all processes in namespace. fails as unit if there is at least on process is dependent by somebody else.

Why cannot use just update config?

Because it is not always the case I know whole config. I have 100 tests. And they run independently. The only thing they know is shared config for their deps. While config of each test is dyanamic and prefixes by namespace.

[F1bonacc1]

Have you considered the extends functionality?
https://f1bonacc1.github.io/process-compose/merge/?h=extends#configuration-inheritance-with-extends

[dzmitry-lahoda]

Not sure.

1. how i can remove part of config? my tests did run, no need config part for them.
2. i do not see extend in API, i see UpdateProcess. So I can use namespace with process update as child PC.
3. no guarantees loops/cycles will be created or that only processes will be updated (not whole PC config)
4. is it resonable to make extend to be API?

[dzmitry-lahoda]

I fill like namespaces operations are much cleaner to what I want: add/remove/stop/start/enabled/disable namespace operation.

Most are just updating(including deletion) process state/config, with some checks (like that all processes from single namespace).

Is deletion of process config possible? When I update whole project state, some processes can be missing, so they to be deleted, so possible.

I think using extend emulating first class namespaces(and namespace as child PC) is not what is good, but first class namespaces are?

[dzmitry-lahoda]

Here is whole agenda which will be ok for me #385