the SDC CSAR structure is seperated into 4 phases:
CSAR provided by the vendor to the SDC for onboarding:
this is the currently expected structure supported by SDC
ROOT/
MainServiceTemplate.mf [a map representing the different parts of the CSAR structure.]
MainServiceTemplate.yaml [copy of the main service template located under Defanitions]
/TOSCA-Metadate/
TOSCA.meta [ metadata regarding the CSAR structure]
/Artifacts/ [includes all artifacts.]
Images are not supported.
Artifact type will be identified by an additional folder under “Informational”/“Deployment” that will define the artifact type.
\Informational\ [will hold all informative artifacts in the direct asset level]
\Deployment\ [Sub-folder directly under “Artifacts”– Deployment artifacts in the direct asset level]
\<VFC TOSCA name>\
\Informational\ [will hold all informative artifacts on VFC level ]
\Deployment\ [will hold all deployment artifacts on VFC level ]
Do we map a folder name to an artifact type?
Artifacts at the root directory or unrecognized folder(s) will be classified as “Other” type
/Definitions – includes all TOSCA yaml files
Need to include SDC global definition file(s).
CSAR created by SDC for VF:
CSAR created by SDC for SERVICE: