Medium The API call
POST http://so.onap:8080/onap/so/infra/serviceInstantiation/v7/serviceInstances/
fails due to the pending slash ("/") with the workflow error:
2020-04-15T06:06:14.768Z|2196fdff-826c-4096-abaf-3a7b7d134970|o.o.s.b.i.workflow.tasks.WorkflowAction - found match on v7/serviceInstances/ : java.util.regex.Matcher[pattern=[vV]\d+.*?(?:(?:/(?<type>vnfs|vfModules|networks|networkCollections|volumeGroups|serviceInstances|instanceGroups)(?:/(?<id>[^/]+))?)(?:/(?<action>[^/]+))?(?:/resume)?)?$ region=0,20 lastmatch=v7/serviceInstances/]
2020-04-15T06:06:14.773Z|2196fdff-826c-4096-abaf-3a7b7d134970|o.o.s.b.i.workflow.tasks.WorkflowAction - Exception while setting execution list.
java.lang.IllegalArgumentException: Uri could not be parsed. No type found. v7/serviceInstances/
at org.onap.so.bpmn.infrastructure.workflow.tasks.WorkflowAction.extractResourceIdAndTypeFromUri(WorkflowAction.java:1209)
at org.onap.so.bpmn.infrastructure.workflow.tasks.WorkflowAction.selectExecutionList(WorkflowAction.java:204)
From API perspective there should be no difference if the call ends with or without slash.
This behaviour has changed since ElAlto, as the ExtAPI used the pending slash until that release.