When a service is imported and the usage of a node type in the service template is not consistent with the already deployed definition of that type, then the definition of that type in the service csar should be checked for compatibility and deployed if appropriate in order to allow the service import to continue.

The following changes to be supported:

• Addition of a new attribute with type already known
• Addition of a new requirement with type already known
• Addition of a new capability with type already known
• Addition of a new interface with type already known

If the node type definition in the csar changes the type of a property then an error should be thrown indicating the import is failing due to a non compatible model