Team, In order for the self serve initiative to provide the vf-module-parameters along with the capability-name, the service-data needs to be filled through some mechanism ( restconf/config/GENERIC-RESOURCE-API:services/service/$serviceInstanceId/service-data) Reason this needs to be done is so the sub-dg that will be created for assign/unassign will be able to, based on the capability name, select the proper plugin and trigger the right action.
I envisioned this being done at design time or an SO flow to take care of that; and looking at current SO flows, it currently seems to be done in groovy through SDNCAdapterWorkflowRequest. Is that the route we want to pursue for our current initiative? If yes, does it means I create a new BPMN subprocess specifically for this, e.g. DoCreateVfModuleSelfServe, where the param and capability are passed through SO request? Or should I be using the new freshly added building block, such as SDNCAssignTasks? but I’m very un-clear how to use it. Could please shed some light on how should I proceed? Thanks, Alexi -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12024): https://lists.onap.org/g/onap-discuss/message/12024 Mute This Topic: https://lists.onap.org/mt/24923559/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
