Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
Change-Id: I44a3596c05b02faa171f90b9207f774ce34976a6
Issue-ID: CCSDK-1577
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
|
|
Change-Id: I66d340727918842a26f07e8609a043c37e5089f4
Issue-ID: CCSDK-1577
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
|
|
Change-Id: If68ce2e944700cb19380d34ff3b466a9c8633472
Issue-ID: CCSDK-1577
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
|
|
Change-Id: I83a3d1391c60cd426236b55d0d399e273e7c15dc
Issue-ID: CCSDK-1577
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
|
|
Change-Id: If21c4964bda08e5d50e6fd11fb1d657e5bf8785c
Issue-ID: CCSDK-1577
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
|
|
When doing resource resolution, if the same resolution-key,
or the same resource-id/resource-type combo, is used, then the
process will only try to resolve the resources set with a "failure"
status from the RESOURCE_RESOLUTION db table.
In the case the resource has previsously successfully been resolved,
then we need to set its value in the resource assignemnt resolution
store so it can be used later in the processing, for instance if another
resource depends on it.
Change-Id: Ifa3957fe3d2365e1f4347aa61ed963124f8a69f7
Issue-ID: CCSDK-1606
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
It can happen the resolve fails, and the status end up not
being set, hence to avoid any exception, we default to failure.
Change-Id: Ia5fb9ad954c109f394425f33c506e66d7e1969e4
Issue-ID: CCSDK-1606
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Change-Id: I18c4d0803e20ed18e4dde553288d37143dff936a
Issue-ID: CCSDK-1572
Signed-off-by: Eliezio Oliveira <eliezio.oliveira@est.tech>
|
|
Added service for search result CBA
Change-Id: Iba00f048abc59878e6dcda9d1de9f0fc823d9130
Issue-ID: CCSDK-1275
Signed-off-by: Ezhilarasi <ezhrajam@in.ibm.com>
|
|
Roll versions to 0.5.1 - need to re-release El Alto early release
Change-Id: Ifc0d4af8920065ca4ae8f509c63f98dc6e112322
Issue-ID: CCSDK-1563
Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.com>
|
|
Change-Id: I7888ac302da2a51ca34c531b7553d04af13786ac
Issue-ID: CCSDK-1380
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
|
|
|
|
|
|
|
|
Change-Id: Iec330d87f9609d42c05f8d4c7c8515fa37310a6e
Issue-ID: CCSDK-1046
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
|
|
Change-Id: Icd12c87e017d4b8586bb60f63abce6cda3c7751c
Issue-ID: CCSDK-1380
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
|
|
Change-Id: I739ad054fafc0c302fb6ad03999561f2b3cf9652
Issue-ID: CCSDK-1380
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
|
|
|
|
JPA repository functions .findBy......... needs occurence value
the API in the TemplateResolutionService was defaulting it to 1.
Issue-Id: CCSDK-1526
Signed-off-by: Oleg Mitsura <oleg.mitsura@amdocs.com>
Change-Id: Iea1e7c50d57c60323eb5c71c0caf61d1ad573bfb
|
|
Change-Id: I0f323bd13c433d9ef0e207f51234d10cd8c22858
Issue-ID: CCSDK-1352
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
|
|
Change-Id: I193e2a092ff8cefe48419031096e1336e5c84fc1
Issue-ID: CCSDK-1046
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
|
|
Change-Id: Id439ac5ded631aac0ee7fc69846ebe9bca650bb2
Issue-ID: CCSDK-1499
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
|
|
Change-Id: Ibbec8cd5785372a89e14a86d4e6ff7f9fed4aad2
Issue-ID: CCSDK-1499
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
Signed-off-by: Steve Siani <alphonse.steve.siani.djissitchi@ibm.com>
|
|
Issue-ID: CCSDK-1489
Signed-off-by: Steve Siani <alphonse.steve.siani.djissitchi@ibm.com>
Change-Id: If27c0dd301f2c0e63cecc662cd89b1a72d1b21f1
|
|
Change-Id: I77a60de87acec862ce47256557a1223fefe82a12
Issue-ID: CCSDK-1497
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Exception is always thrown due to the contract, enforcing
the get attribute to throw an exception if not found.
For the resource resolution result, we can simply initialize
the property to an empty json, so system won't throw an exception
if user request the output, but process failed.
Change-Id: I39e288590502c75495e2938a44b874dfd0671155
Issue-ID: CCSDK-1495
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
|
|
|
|
possibility of cyclic dependencies between blueprint-script module and code module. To avoid cyclic dependency blueprint-script implementation should be moved to Core module. This implementation has zero impact on code functionality and code testing."
|
|
Issue-ID: CCSDK-1479
Signed-off-by: Prathamesh Morde <prathamesh.morde@bell.ca>
Change-Id: I37fbce8d4621d85d3a47d38464eeeee267d46741
Signed-off-by: Prathamesh Morde <prathamesh_morde@yahoo.ca>
|
|
|
|
|
|
|
|
Change-Id: I16afd71c2c35b7f270577ea784a9173ea3e0d604
Issue-ID: CCSDK-1357
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
|
|
There is a possibility of cyclic dependencies between blueprint-script module and code module. To avoid cyclic dependency blueprint-script implementation should be moved to Core module.
This implementation has zero impact on code functionality and code testing.
Change-Id: Ic18ea848cb2e1e2e7a5f1c144714de26d1495cee
Issue-ID: CCSDK-1469
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
|
|
Issue-Id: CCSDK-1467
Signed-off-by: Abdelmuhaimen Seaudi <abdelmuhaimen.seaudi@orange.com>
Change-Id: Ibc50be0bf9986c49d2c7546f895c85c6851447bb
|
|
Issue-ID: CCSDK-1468
Signed-off-by: Oleg Mitsura <oleg.mitsura@amdocs.com>
Change-Id: If8eb50fc2e8dfa084e486b02ace163eee1bfac77
|
|
Change-Id: Ida75e839668eeeabd4577629f2bc6ec3240d7734
Issue-ID: CCSDK-1428
Signed-off-by: Brinda Santh <brindasanth@in.ibm.com>
|
|
ISSUE-ID: CCSDK-1463
Signed-off-by: prathameshmo <prathamesh.morde@bell.ca>
Change-Id: Id4e9827d94999a585b79460f147562bdd655ccfb
|
|
Issue-ID: CCSDK-1461
Signed-off-by: Steve Siani <alphonse.steve.siani.djissitchi@ibm.com>
Change-Id: I25521090a2ab8e5b9d7a9edef3178ba83b463657
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|