Changes includes:
1. Correcting connection-attachment topology container name.
2. Make the vnf-topology-operation implementation flexible to allow
SDNC generate vnf-id for assign/create operation rather then mandating
SO to provide it.
Change-Id: I8958a72a4ca2064b781d246e9329436848f578ad
Issue-ID: SDNC-384
Signed-off-by: Gaurav Agrawal <gaurav.agrawal@huawei.com>
}\r
\r
grouping connection-attachment-topology {\r
- container brg-topology {\r
+ container connection-attachment-topology {\r
uses allotted-resource-identifiers;\r
uses onap-model-information;\r
uses connection-attachment-assignments;\r
trySetSvcRequestId(input, responseBuilder);
+ /* Comment out mandatory check for vnf id for scenario wherein for assign/create request vnf-id is generated by
+ SDNC itself.
if (hasInvalidVnfId(input)) {
log.debug("exiting {} because of null or empty vnf-id", svcOperation);
responseBuilder.setResponseCode("404");
return Futures.immediateFuture(rpcResult);
}
+ */
String vnfId = input.getVnfInformation().getVnfId();
ServiceDataBuilder serviceDataBuilder = new ServiceDataBuilder();
}
+ /*
@Test
public void should_fail_when_invalid_vnf_id() throws Exception {
assertEquals("404", output.getResponseCode());
assertEquals("invalid input, null or empty vnf-id", output.getResponseMessage());
assertEquals("Y", output.getAckFinalIndicator());
- }
+ }*/
@Test