When generating a CSAR for a resource that is associated with a derived model, the default imports for the derived and parent model can conflict in path, therefore causing an issue during the CSAR zip generation which can't stand two entries with the same path.

For example:

Parent Model Imports:

• import1.yaml
• import2.yaml

Derived from Parent Model Imports:

• import2.yaml
• import3.yaml

When the CSAR is generated, the files from both Derived and Parent model will be included in the Definitions folder, therefore breaking the CSAR generation with the conflicting file path Definitions/import2.yaml.