When triggering a deployment using a deployment proxy node that has been defined as a new type then the outputs of the triggered deployment are not retrieved by the deployment_proxy node.
To reproduce try the attached blueprint. Two nodes are defined, one cloudify.nodes.DeploymentProxy and another deployment_proxy_type. The second is a custom type that derives from a cloudify.nodes.DeploymentProxy.
When deploying the blueprint the first node retrieved the dummy output of the deployment_proxy triggered deployment, while the second does not.
New_Blueprint_1.zip
When triggering a deployment using a deployment proxy node that has been defined as a new type then the outputs of the triggered deployment are not retrieved by the deployment_proxy node.
To reproduce try the attached blueprint. Two nodes are defined, one cloudify.nodes.DeploymentProxy and another deployment_proxy_type. The second is a custom type that derives from a cloudify.nodes.DeploymentProxy.
When deploying the blueprint the first node retrieved the dummy output of the deployment_proxy triggered deployment, while the second does not. New_Blueprint_1.zip