Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
When placing a template onto the graph, all included / required controller services are also created... even if an exact duplicate already exists (possibly even from a previous instance of the same template). It is definitely possible you might not want to reuse an existing controller service, so that shouldn't be the default behavior. However, it is also very likely that you do want to reuse a controller service.
Could we add a check on template instantiation that checks for controller service matches (name & configuration), and prompt with the option to either create new or use existing?
