All paths under "OAM Layer - Basic Part" have the operation-server uuid as path parameter.
For the link and link-port service the uuids are a special case and don't follow the normal pattern, but contain "get/put/del" substrings:
I only tried to call the service to change the life-cycle-state and Postman returned an error, but I assume the same problem will occur for all those services, when using any of the above uuids:
"code": 400,
"message": "request.params.uuid should match pattern \"^([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-op-s-([bi][ms])-([0-9]{3})$\"",
"errors": [
{
"path": ".params.uuid",
"message": "should match pattern \"^([a-z]{2,6})-([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})-op-s-([bi][ms])-([0-9]{3})$\"",
"errorCode": "pattern.openapi.validation"
}
]
}
Also see #958.
All paths under "OAM Layer - Basic Part" have the operation-server uuid as path parameter. For the link and link-port service the uuids are a special case and don't follow the normal pattern, but contain "get/put/del" substrings:
I only tried to call the service to change the life-cycle-state and Postman returned an error, but I assume the same problem will occur for all those services, when using any of the above uuids: