Reputation: 1
When trying to get started with Cloudify, importing the "Cloudify Hello World Example", I get an error:
TypeError: Object.getOwnPropertyNames called on non-object
I get the same error for any blueprint I try to import. I've searched, but found no help on this error.
The example is being imported from a local clone of cloudify-hello-world-example.git on GitHub. I'm using the Composer UI "Blueprint Settings" tool "Import" option, and selecting the local file "blueprint.yaml" from the cloned repo.
I'm running this on CentOS 7, and installed the Composer as described at thank_you_composer.htm on getcloudify.org. Logging into the Composer at localhost port 3000, using Chrome or Firefox, same result.
What is the reason for this TypeError
when importing Cloudify blueprints, and how do I correct/avoid it?
Upvotes: 0
Views: 232
Reputation: 429
The composer philosophy is to model and design applications.
You can use it to create new blueprints and add new stencils.
For the moment (version 3.3.1) there is a problem importing blueprints that are using external imports (https://cloudifysource.atlassian.net/browse/CFY-4325), you can bypass it by importing the blueprint without those plugins and then add lifecycle operations that will add the functions of those plugins.
Upvotes: 2