diff options
Diffstat (limited to 'csarvalidation/src/main/resources/open-cli-schema/sol004/vtp-validate-csar-r787965.yaml')
| -rw-r--r-- | csarvalidation/src/main/resources/open-cli-schema/sol004/vtp-validate-csar-r787965.yaml | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/csarvalidation/src/main/resources/open-cli-schema/sol004/vtp-validate-csar-r787965.yaml b/csarvalidation/src/main/resources/open-cli-schema/sol004/vtp-validate-csar-r787965.yaml index db5a1a1..e07434f 100644 --- a/csarvalidation/src/main/resources/open-cli-schema/sol004/vtp-validate-csar-r787965.yaml +++ b/csarvalidation/src/main/resources/open-cli-schema/sol004/vtp-validate-csar-r787965.yaml @@ -20,10 +20,12 @@ description: | If the VNF or PNF CSAR Package utilizes Option 2 for package security, then the complete CSAR file MUST be digitally signed with the VNF or PNF provider private key. The VNF or PNF provider delivers one zip file consisting of the CSAR file, a signature file and a certificate file that includes the VNF or PNF provider public key. The certificate may also be included in the signature container, if the signature format allows that. The VNF or PNF provider creates a zip file consisting of the CSAR file with .csar extension, signature and certificate files. The signature and certificate files must be siblings of the CSAR file with extensions .cms and .cert respectively. info: - product: onap-dublin + product: onap-vtp version: 1.0 service: vnf-compliance author: ONAP VTP Team onap-discuss@lists.onap.org + metadata: + release: dublin parameters: - name: csar |