Thanks for the added explanation.
CAmkES probably has a missing concept for defining “monitor” or “supervisor” relationships between component instances to deal with concerns such as fault handling or scheduling. These relationships are a different class to existing connection relationships because they imply access to an entity’s objects that are also part of it’s standard connections, whereas standard connections are somewhat isolated from each other. Without this concept, you are left with having to implement something internally like what’s proposed here which I think is the best way you could achieve the functionality under the present constraints.
We called the python function “alloc_ent.” We are not stuck on the name, feel free to rename.
What do you think about alloc_unsafe for the name? This does open the door to hidden connections between components that would otherwise appear isolated from looking at the composition part of the CAmkES ADL spec.
Feel free to make a PR on the camkes-tool repo also.