CP-12230 DVP Record size validation changes for setting ZFS record size

[rakshandabhat]

Problem

DVP Record size schema validation changes for setting ZFS record size
CP-12230

Solution

Added schema validation in plugin_schema.json to check if the field "recordSizeInKB" is of type "integer".

Explanation of the change:

Here in this case the normal validation like below won't work :
"recordSizeInKB": { "type" : "integer" }

In this case, we need to retrieve the properties of recordSizeInKB to get the type and then validate it.

• In order to validate if the field "recordSizeInKB" is of type "integer", we have to first retrieve the "properties" field of "linkedSourceDefinition" and "virtualSourceDefinition". This is because the "recordSizeInKB" field needs to be listed within the "properties" field of "linkedSourceDefinition" and "virtualSourceDefinition".
• Once the "properties" field is retrieved, then we need to get the properties of the "recordSizeInKB" to get the "type".
• We have checked the string value of "type" field has to be "integer".

Testing Done

Manual:
Executed dvp --verbose build --dev for correct schema for both linkedSourceDefinition and virtualSourceDefinition.

Executed dvp --verbose build --dev for inavlid schema for both linkedSourceDefinition and virtualSourceDefinition.

Executed dvp --verbose build --dev for schema without "recordSizeInKB" field in schema.

Unit test:

Unit test execution after adding new test cases :

Blackbox tests:
virtualization_sdk APPDATA_SDK_UBUNTU20_DIRECT_RHEL79
virtualization_sdk APPDATA_SDK_WIN10_STAGED_WIN2019

[SumoSourabh]

Changes looks good to me. I would suggest adding unit test cases for the validations.

[SumoSourabh]

LGTM

[vimleshmishra]

LGTM.