Seems improvements done in the order of v2.6.1, v3.3.1, v2.8.1
It looks some improvements on api-tests have been done in the order of v2.6.1, v3.3.1, v2.8.1. For example, the following steps look improved in the order mentioned above. In such a case, are you planning to forward/backport the latest improvement to older/newer version? I would like you to clarify the rule about it to prevent users from making miss-design in future.
<api-tests/SOL003/VNFLifecycleManagement-API/VnfLcmMntOperationKeywords.robot> "POST Create a new vnfInstance"
<v2.6.1-fix-plu>
${body}= Get File jsons/createVnfRequest.json
Post ${apiRoot}/${apiName}/${apiVersion}/vnf_instances ${body}
==> Whole content of Json is used as the body of Post request
<v3.3.1-fix-plu>
${template}= Get File jsons/createVnfRequest.json
${body}= Format String ${template} vnfdId=${vnfdId}
Post ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_instances ${body}
==> Json is used as the template of the body, and then only "vnfdId" is updated
<v2.8.1-fix-plu>
${template}= Get File jsons/createVnfRequest.json
${body}= Format String ${template} vnfdId=${Descriptor_ID} vnfProvider=${Provider} vnfProductName=${Product_Name} vnfSoftwareVersion=${Software_Version} vnfdVersion= ${Descriptor_Version}
Post ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_instances ${body}
==> In addition to the update in v3.3.1, other multiple variables in the body are also updated