Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Send Homing_solution=none during macro instantiation
Add flag 'FLAG_DISABLE_HOMING' (by default set to true) which defines
whether homing_solution should be in request to so or not
Issue-ID: VID-576
Signed-off-by: wsliwka <wojciech.sliwka@nokia.com>
Change-Id: I6151151a0256a5bb4e637acf08ae511f4b265dc2
Signed-off-by: wsliwka <wojciech.sliwka@nokia.com>
|
|
|
|
Issue-ID: VID-646
Signed-off-by: Einat Vinouze <einat.vinouze@intl.att.com>
Change-Id: Ifc6a43f9b34c5c792a05cc3502c1e8fcf5023210
|
|
Issue-ID: VID-646
Signed-off-by: Eylon Malin <eylon.malin@intl.att.com>
Change-Id: I533221a6115c4a2d00ce3ed02eef4d1ad882df3a
|
|
Issue-ID: VID-596
Signed-off-by: Alexey Sandler <alexey.sandler@intl.att.com>
Change-Id: I72d9c2c9dc3f39fcc3c87e083ac230d20135e979
|
|
As we are now using AaiController2, the AaiController endpoint of change-management is redundant
Issue-ID: VID-596
Signed-off-by: Amichai Hemli <amichai.hemli@intl.att.com>
Change-Id: I68289eb5acb02af75c052e891dc6f77a48dc62c7
|
|
Issue-ID: VID-637
Signed-off-by: Eylon Malin <eylon.malin@intl.att.com>
Change-Id: Ia9340269dd6a4a6616a6fdbfe166eea0731490de
|
|
|
|
|
|
|
|
print raw body for cases like errors
make sure the response can be read logging it
Issue-ID: VID-611
Signed-off-by: Eylon Malin <eylon.malin@intl.att.com>
Change-Id: If138531f515fb2927a13417040b68e81babebc4e
|
|
Issue-ID: VID-611
Signed-off-by: Einat Vinouze <einat.vinouze@intl.att.com>
Change-Id: I0e64e9520e566f9317f3fcbf0495b67349993ce4
|
|
optional"
|
|
Issue-ID: VID-596
Signed-off-by: Amir Skalka <as221v@intl.att.com>
Change-Id: I4462ef0c2dbc9880d1a0d204f6552e3842aad821
Signed-off-by: Alexey Sandler <alexey.sandler@intl.att.com>
|
|
Issue-ID: VID-378
Signed-off-by: Sara Weiss <sara.weiss@intl.att.com>
Change-Id: I21a4b541f32626823d84f9d0d6fb0392275b7428
Signed-off-by: Sara Weiss <sara.weiss@intl.att.com>
|
|
Create class that implement joshworks object mapper that used jackson
object mapper that support kotlin.
Use it instead local anonymous classes where needed
Issue-ID: VID-611
Signed-off-by: Eylon Malin <eylon.malin@intl.att.com>
Change-Id: Ie00dce0ec9b366515c5e40d9f37b9e64a2ceb357
|
|
|
|
Issue-ID: VID-611
Change-Id: I120782884351c55b2e0d1b4ca8bae1e2479d1d0a
Signed-off-by: Eylon Malin <eylon.malin@intl.att.com>
|
|
Issue-ID: VID-596
Signed-off-by: Alexey Sandler <alexey.sandler@intl.att.com>
Change-Id: I36e5ea4842816dfa8a6734299bf667150600a375
|
|
Issue-ID: VID-603
Signed-off-by: Einat Vinouze <einat.vinouze@intl.att.com>
Change-Id: If50a1f810a7851e4eaa88ac07fe3a09f381c0e4a
|
|
at the end of this line"
|
|
at the end of this line"
|
|
at the end of this line"
|
|
* changes:
Add Semicolon at the end
Add Semicolon at the end
Add Semicolon ath the end
|
|
end of this line
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can
be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end
of each line.
Issue-ID: VID-606
Change-Id: Ic6daf9162504a2296a7e2cf48f08e60cabe14b21
Signed-off-by: anushadasari <danush10@in.ibm.com>
|
|
end of this line
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can
be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end
of each line.
Issue-ID: VID-606
Change-Id: Ib1484f91b4b47457c4150b536d420ffc1e6902b4
Signed-off-by: anushadasari <danush10@in.ibm.com>
|
|
end of this line
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can
be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end
of each line.
Issue-ID: VID-604
Change-Id: I850ee4d00e2f263105a15a5778c11cfb2e526986
Signed-off-by: anushadasari <danush10@in.ibm.com>
|
|
* changes:
Add Semicolon at the end
Add Semicolon at the end
Add Semicolon at the end
|
|
at the end of this line"
|
|
Renamed from FLAG_FLASH_VIEW_IN_NEW_VIEWEDIT_SCREEN.
Added features.properties.md to document the different flags.
Change-Id: I819a31851eab8bed54f807f0ffb5082496677d3f
Issue-ID: VID-603
Signed-off-by: Ittay Stern <ittay.stern@att.com>
|
|
align MSO create service instance URL to
/serviceInstantiation/v7/serviceInstances
also unify some system properties variables
Issue-ID: VID-622
Signed-off-by: Eylon Malin <eylon.malin@intl.att.com>
Change-Id: I7a0744f5d6cfe776ce2f17b11aa5ebba4c8e65fb
Signed-off-by: Eylon Malin <eylon.malin@intl.att.com>
|
|
Issue-ID: VID-603
Change-Id: I59068a0979d6fb733e4243c8f78921f396dc9d17
Signed-off-by: Einat Vinouze <einat.vinouze@intl.att.com>
Signed-off-by: Amichai Hemli <amichai.hemli@intl.att.com>
Signed-off-by: Ittay Stern <ittay.stern@att.com>
|
|
Don't use static headers for ECOMP_REQUEST_ID and ONAP_REQUEST_ID but
getting them from request / generate them each time
Issue-ID: VID-378
Signed-off-by: Eylon Malin <eylon.malin@intl.att.com>
Change-Id: I1be4e8e86195901975d613694acf0082cd555886
Signed-off-by: Eylon Malin <eylon.malin@intl.att.com>
|
|
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: Ic75affcf10f990fa507eaf738a360df603a700dc
Signed-off-by: anushadasari <danush10@in.ibm.com>
|
|
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: I40df40c69bf7de18eeafbf640b4ebe1d0efe6def
Signed-off-by: anushadasari <danush10@in.ibm.com>
|
|
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: I9ca9d0f3c935efe83859b4d623939adce0a38465
Signed-off-by: anushadasari <danush10@in.ibm.com>
|
|
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: I53b2e7a540b88b3e04d9169670d1fc6b4a32c6e8
Signed-off-by: anushadasari <danush10@in.ibm.com>
|
|
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: Icdfa98d7f67fbf3b21cba97b0013f0181ed34675
Signed-off-by: anushadasari <danush10@in.ibm.com>
|
|
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each lin
Issue-ID: VID-607
Change-Id: Ibde377c9a1f4fe473d8f2c0542657888cfbd44c5
Signed-off-by: anushadasari <danush10@in.ibm.com>
|
|
Issue-ID: VID-378
Signed-off-by: Eylon Malin <eylon.malin@intl.att.com>
Change-Id: Icf215cf8b9711a63561740b22c035595f5281f58
Signed-off-by: Eylon Malin <eylon.malin@intl.att.com>
|
|
end of this line
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can
be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end
of each line.
Issue-ID: VID-606
Change-Id: If88beef4fa028d01eda5119dfa5bc005d8225e17
Signed-off-by: anushadasari <danush10@in.ibm.com>
|
|
Add the "@Override" annotation
Issue-ID: VID-561
Change-Id: I86d14dbd8357e92baef111f1ac6db2fdfd963ba1
Signed-off-by: Thugutla sailakshmi <tsaila10@in.ibm.com>
|
|
* changes:
Add semicolon at the end
Add a semicolon at the end of this statement
|
|
* changes:
Semicolon at the end of the Statement
Add a semicolon at the end of this statement
|
|
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: Ief3162f9990689251c7268c515107a34b1a03a52
Signed-off-by: anushadasari <danush10@in.ibm.com>
|
|
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: I92d5834ace5659334bdede1dfc2af23cc697f78a
Signed-off-by: anushadasari <danush10@in.ibm.com>
|
|
Issue-ID: VID-561
Change-Id: Ie27eea2f8219575bcdcaba6f7796acdd1dd07aa9
Signed-off-by: Thugutla sailakshmi <tsaila10@in.ibm.com>
|
|
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: I45f7576fe1410b4ab46949547584a597ed98c0b3
Signed-off-by: anushadasari <danush10@in.ibm.com>
|
|
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: Iaf0757c6a0c4a2ebe6cba74ced60f1e978160bd6
Signed-off-by: anushadasari <danush10@in.ibm.com>
|