Scenario (VSP import procedure):

A VNF onboarding package is prepared, and it contains the following file, type: "CONTROLLER_BLUEPRINT_ARCHIVE", filename: "vFW_CNF_CDS.zip".

{
    "name": "virtualFirewall",
    "description": "",
    "data": [
        {
            "file": "vFW_CNF_CDS.zip",
            "type": "CONTROLLER_BLUEPRINT_ARCHIVE"
        }
     }
}

After such a file is loaded to SDC as part of VSP onboarding activity, and the VF Resource is created out of that VSP, this artifact is classified as "OTHER", instead of being classified as "CONTROLLER_BLUEPRINT_ARCHIVE".

After looking at the code, each artifact, which contains "CBA" string in the file name is classified as a "CONTROLLER_BLUEPRINT_ARCHIVE", which is wrong.
The classification shall be done based on the file type given in the manifest, and not based on the file name (or a substring in the filename).

See attachements (onboarding package, as well as SDC screen)