Previously if a CNI set a flow's onTrigger to a component reference and also defined onInstanceDelete or onInstanceDeploy behavior, the flow's onInstance methods would be ignored.
This PR makes it such that if a flow defines both a component reference onTrigger (either explicitly or via default fallback) along with onInstance behavior, all defined onInstance behavior will execute.
In the case of both the component & the flow having defined onInstance behavior (e.g. they each have their own onInstanceDeploy definitions), the returned responses will be deep-merged with preference given to the flow's response if there's a conflict.
Previously if a CNI set a flow's
onTriggerto a component reference and also definedonInstanceDeleteoronInstanceDeploybehavior, the flow'sonInstancemethods would be ignored.This PR makes it such that if a flow defines both a component reference
onTrigger(either explicitly or via default fallback) along withonInstancebehavior, all definedonInstancebehavior will execute.In the case of both the component & the flow having defined
onInstancebehavior (e.g. they each have their ownonInstanceDeploydefinitions), the returned responses will be deep-merged with preference given to the flow's response if there's a conflict.