Where a VSP is onboarded and imported than contains a custom data type, a model specific to the package will be created during import. The model shall extend from the model selected during import (e.g. ETSI SOL001 2.5.1) and the custom datatype(s) will be associated to the package specific model.

These data type definitions need to be included in an import files for the model when the model is created (org.openecomp.sdc.be.components.impl.ModelBusinessLogic#createModel(org.openecomp.sdc.be.model.Model, java.lang.String))

Also the logic for adding the import files during csar generation also needs to be updated to include the import files for the model and also any models the given model derivesFrom.

For example a csar for a VF from a VSP including custom data types should include

• Import file associated with the package model: i.e. an import file created when the package specific model is created containing the custom data types 
• Import files associated with the ETSI model the package model is derived from: etsi_nfv_sol001_vnfd_types.yaml, etsi_nfv_sol001_nsd_types.yaml