Page Comparison

1/ Is there an API URL Pattern for Backends ? Something like

/{apiName}/{version}

/resource1

/resource2

2/ To avoid client impact on path modification, backends might register one or several 'APIs' on MSB. For instance SO:

serviceInstance
/onap/so/infra/serviceInstantiation/v7/serviceInstances/

orchestration
/onap/so/infra/orchestrationRequests/v7

e2e
/onap/so/infra/e2eServiceInstances/v3

instead of unique /

For NBI we use this kind of registration

{
    "serviceName": "nbi",
    "version": "v3",
    "url": "/nbi/api/v3",
    "protocol": "REST",
    "visualRange": "1",
    "lb_policy": "round_robin",
    "enable_ssl": false,
    "nodes": [
        {
            "ip": "172.20.0.7",
            "port": "8080",
            "checkType": "HTTP",
            "checkUrl": "/nbi/api/v3/status",
            "checkInterval": "10s",
            "checkTimeOut": "10s"
        }
    ]
}

Convert to new Style for AAF authentification.

Item summarized in https://lists.onap.org/g/onap-discuss/message/12466

Gildas to check with Integration for Robot