Closed joshuap-cfy closed 7 years ago
We are currently testing this in v1.2.3 to see if error is resolved.
After upgrading to version 1.2.3, the following error when trying to deploy a blueprint with a DeploymentProxy node. 1.2.3 does fix the issue of cloudify.nodes.DeploymentProxy (1.2.2) deleted the existing deployment.
Log:
2017-06-22T00:06:55 CFY
Should be fixed in 149aca363d1e101caaf44edb2b28274b0295d85b
fixed in 1.2.5
What’s the right way to use DeploymentProxy in this new version of 1.2.2? I have used deployment proxy to implement the following use case: · Given an existing deployment (deployment_id: network), which exposes several resources through outputs. · Deploy and install another blueprint, which needs access to the resources created in the deployment above.
I tried to upgrade my proxy node to use the new version of the proxy plugin (1.2.2) following the example in this link: https://github.com/cloudify-incubator/cloudify-utilities-plugin/blob/1.2.2/cloudify_deployment_proxy/examples/test/deployment-proxy.yaml. My question is: since I’m just importing outputs exposed by an existing deployment, why is it required to provide the “blueprint” input to the proxy node? If I set the blueprint input to empty values, I’m getting an error. The error appears to be resulted from the plugin trying to upload a blueprint. What’s the right way to use DeploymentProxy in this new version of 1.2.2?