Model dmi plugins might work based on cmhandle properties when it giving back the module sets.
To make cmHandle version upgrade work model dmi plugin behavior can be modified to work based on properties and moduleSetTag, to be able to give back correct module set during a cmhandle version upgrade.
Currently moduleSetTag is not added to the request which is sent to model dmi plugin (in CPS version 3.4.1). Without that cmhandle upgrade wont work in an environment where model dmi plugin is prepared to work based on moduleSetTag.
Please add moduleSetTag to the request towards dmi plugin if moduleSetTag is set for the cmHandle.

Affected Interface: DMI-I-01

Open API Method:  /v1/ch/{cmHandle}/modules

affected component
ModuleReferencesRequest:
type: object
properties:
cmHandleProperties:
$ref: '#/components/schemas/cmHandleProperties'
moduleSetTag:
.....
 

csaba.eder to check if other method (for resource) needs this too:  /v1/ch/{cmHandle}/moduleResources:

Decision: We don't need the module set tag to get the definition of a given module reference

Note the new field wil always be added but value could be 'blank' (depending on client use)

How?

1. update DMI interface to have the optional field (moduleSetTag)
2. release DMI
3. update NCMP to use the latest version
4. populate the new optional field in the relevant request
5. update DMI Stub to log the moduleSetTag

A/C:

1. deliver updated DMI plugin (incl. Swagger updates)
2. demo that the correct module set tag is logged