diff options
| author |   Bogumil Zebek <bogumil.zebek@nokia.com> | 2021-01-20 14:53:39 +0100 |
|---|---|---|
| committer | Zebek Bogumil <bogumil.zebek@nokia.com> | 2021-01-20 14:53:39 +0100 |
| commit | 398dcd3e75651e047e307a3207fb2b8dc1207ab0 (patch) | |
| tree | 14b0e7fbf8445b2a207d094fc3525efe2b0e82db /csarvalidation/src/main/resources/open-cli-schema/sol004/vtp-validate-csar-r130206.yaml | |
| parent | 59010375b15438297c5e25e6864fd88b76c80760 (diff) | |
Add release parameter to rules
- All vnf/pnf rules where updated. Release parameter was added into the info->metadata section.
- VNFSDK validation logic supports optional release parameter. Parameter defines which rules should be used during validation process.
By default: all rules are used during validation process.
--release parameter defines which rules (parent with ancestors) should be used.
For example: if user run validation with --release=dublin, then amsterdam, casablanca and dublin rules will be used during validation.
Rules order is defined in the vnfreqs.properties file.
Change-Id: I3e9dc1e7a899fa51c266808cbcb73e04a2e252cc
Issue-ID: VNFSDK-731
Signed-off-by: Zebek Bogumil <bogumil.zebek@nokia.com>
Diffstat (limited to 'csarvalidation/src/main/resources/open-cli-schema/sol004/vtp-validate-csar-r130206.yaml')
| -rw-r--r-- | csarvalidation/src/main/resources/open-cli-schema/sol004/vtp-validate-csar-r130206.yaml | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/csarvalidation/src/main/resources/open-cli-schema/sol004/vtp-validate-csar-r130206.yaml b/csarvalidation/src/main/resources/open-cli-schema/sol004/vtp-validate-csar-r130206.yaml index ff349bc..5f02207 100644 --- a/csarvalidation/src/main/resources/open-cli-schema/sol004/vtp-validate-csar-r130206.yaml +++ b/csarvalidation/src/main/resources/open-cli-schema/sol004/vtp-validate-csar-r130206.yaml @@ -20,10 +20,12 @@ description: | The VNF/PNF package shall contain a Digest (a.k.a. hash) for each of the components of the VNF package. The table of hashes is included in the manifest file, which is signed with the VNF provider private key. In addition, the VNF provider shall include a signing certificate that includes the VNF provider public key, following a pre-defined naming convention and located either at the root of the archive or in a predefined location (e.g. directory). info: - product: onap-dublin + product: onap-vtp version: 1.0 service: validation author: ONAP VTP Team onap-discuss@lists.onap.org + metadata: + release: guilin parameters: - name: csar |