Include custom data types from VSP in csar imports 62/123662/3
authorandre.schmid <andre.schmid@est.tech>
Fri, 27 Aug 2021 14:07:43 +0000 (15:07 +0100)
committerMichael Morris <michael.morris@est.tech>
Mon, 30 Aug 2021 14:17:08 +0000 (14:17 +0000)
commita1cdcda28701f603cf95f591ba447bd723273622
tree3d9d36dbbfa5aca12bdeb3cfcddae04ee2cd34a3
parent37d9a984c45a2a3389b70fca38513fd4bd821e28
Include custom data types from VSP in csar imports

When a model with custom data types is created, the data types
are now being added as part of the default model imports files.
When a CSAR is generated from a Service Template that is
associated to a derived model, the default imports from the
parent model are also included in the package.

Change-Id: I027d25d7237989a40085edec7fdd399ac09c4db1
Issue-ID: SDC-3692
Signed-off-by: andre.schmid <andre.schmid@est.tech>
catalog-be/src/main/java/org/openecomp/sdc/be/components/impl/ModelBusinessLogic.java
catalog-be/src/main/java/org/openecomp/sdc/be/tosca/CsarUtils.java
catalog-be/src/main/java/org/openecomp/sdc/be/tosca/ToscaExportHandler.java
catalog-be/src/test/java/org/openecomp/sdc/be/components/impl/ModelBusinessLogicTest.java
catalog-be/src/test/java/org/openecomp/sdc/be/tosca/InterfacesOperationsConverterTest.java
catalog-model/src/main/java/org/openecomp/sdc/be/model/operations/impl/ModelOperation.java
catalog-model/src/test/java/org/openecomp/sdc/be/model/operations/impl/ModelOperationTest.java