aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2021-03-24Bump apex-pdp to 2.5.3-SNAPSHOTRam Krishna Verma81-81/+81
Issue-ID: POLICY-3150 Change-Id: I563f3f4f2d0d3355b6f683db5904bd2d339f6623 Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
2021-03-24Release apex-pdp 2.5.2 docker8.0.0-ONAPRam Krishna Verma1-0/+8
Issue-ID: POLICY-3150 Change-Id: Ic146feb53bfe042f2ba213a01279b8878f4f37c2 Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
2021-03-24Release apex-pdp 2.5.2 maven artifactsRam Krishna Verma1-0/+5
Issue-ID: POLICY-3150 Change-Id: I27c09b2cc644937fc7812ee0bbbb6cf9b9784a78 Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
2021-03-24Point to 2.4.2 modelsRam Krishna Verma1-1/+1
Issue-ID: POLICY-3150 Change-Id: I92dd8dd234820daa78de25c85276bb079282811c Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
2021-03-23Fixing issues around deploying APEX policies with duplicate conceptsa.sreekumar1-25/+35
Deploying invalid APEX policies with duplicate concepts resulting in corrupting all the policies in memory. This is fixed here. This entire functionality handling multiple policies will be revisited as part of https://jira.onap.org/browse/POLICY-3018 Change-Id: I751102d5dddcb92cdcede8222855e2f467bb724d Issue-ID: POLICY-3141 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca> (cherry picked from commit e3f1349915f425c2f0c09688a2cc6d8d246f4110)
2021-03-23Fixing parallel event execution problem in APEX-PDP REST layera.sreekumar6-135/+29
Parallel event execution in APEX was resulting in incorrect dynamic REST url. This issue is fixed in this review. Change-Id: Id8a28c001a7fd7915df1f5909109bb369667ab40 Issue-ID: POLICY-3019 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca> (cherry picked from commit 369a94a9fd626b35d52c2e7ee5f19e6ff6e1b9d8)
2021-03-16Update policy-keystore with newer certificatesjhh2-0/+0
Issue-ID: POLICY-3139 Signed-off-by: jhh <jorge.hernandez-herrero@att.com> Change-Id: Ia67cb1486a5625385a710c5f6c2b4325ca108820
2021-03-10Default to honolulu branchJim Hahn1-1/+1
Issue-ID: POLICY-3105 Change-Id: I49d5c47b029d95664409f785dc3ed2e1229e9ed9 Signed-off-by: Jim Hahn <jrh3@att.com>
2021-03-10Bump apex-pdp to 2.5.2-SNAPSHOTa.sreekumar81-81/+81
Change-Id: I291f968367b1f864bb417a72fd0bdb22a07ba0f7 Issue-ID: POLICY-3127 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
2021-03-10Release apex-pdp 2.5.1 dockera.sreekumar1-0/+8
Change-Id: I9b5ee20c4760d4f9adcc28c708af62922d6952fa Issue-ID: POLICY-3127 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
2021-03-10Release apex-pdp 2.5.1 maven artifactsa.sreekumar1-0/+5
Change-Id: Ib32e0a9dc3d3b9a27f712a02c0317bf7640bc12d Issue-ID: POLICY-3127 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
2021-03-09Point to policy-models 2.4.1a.sreekumar1-1/+1
Change-Id: I142f196ddcd71048b6812af2d6af014ca42aa5a9 Issue-ID: POLICY-3127 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
2021-02-24Update info.yaml in apex-pdpRam Krishna Verma1-2/+2
Issue-ID: POLICY-3028 Change-Id: Icf1319122ed19a0ba36b148bab7d77be626ba20e Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
2021-02-24Bump apex-pdp to 2.5.1-SNAPSHOTa.sreekumar81-81/+81
Change-Id: I761ded255a97128f858d3a7ce95f2479b6208a4e Issue-ID: POLICY-3088 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
2021-02-23Release apex-pdp 2.5.0 docker imageRam Krishna Verma1-0/+8
Issue-ID: POLICY-3088 Change-Id: Id5754dac1e8bab68cdb280800750ad98f14c76b1 Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
2021-02-23Merge "Fixing intermittent test failures in APEX"Ram Krishna Verma1-75/+58
2021-02-23Release apex-pdp 2.5.0 maven artifactsRam Krishna Verma1-0/+5
Issue-ID: POLICY-3088 Change-Id: Ifa746c534623e43f883f9101c4beb0f34dffbaac Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
2021-02-23Fixing intermittent test failures in APEXa.sreekumar1-75/+58
This review should fix the intermittent test failures in TestExecutionPropertyRest class in APEX. Change-Id: I1871a3ac1a40985ad44bbd1433c54930793c7b3c Issue-ID: POLICY-3096 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
2021-02-23Point to released version of docker, parent, common and modelsa.sreekumar2-5/+6
Change-Id: I17e2e093421733fc94a3de8f5946b867b3b73ba9 Issue-ID: POLICY-3088 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
2021-02-19Convert Date to Instant in statsliamfallon1-2/+2
Issue-ID: POLICY-3069 Change-Id: Ib30782485652ec693d2dbea79514183c7cfbb0c4 Signed-off-by: liamfallon <liam.fallon@est.tech>
2021-02-19Merge "Fix sonars in apex-pdp"Ram Krishna Verma58-720/+509
2021-02-18Update CSIT to check for 202 response during PAP Deploymenta.sreekumar1-1/+1
Change-Id: I947207f10cfd3bc54193ee7c8d356ad40587f072 Issue-ID: POLICY-2526 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
2021-02-18Fix sonars in apex-pdpJim Hahn58-720/+509
Addressed the following issues: - initialize mocks before use - use parameterized queries - Random() is not secure - provide parameterized type for generics - unused imports - constructor visibility - use compute() instead of containsKey()/put() - make final fields static - rename constants to all upper case - no assert() in Thread.run() methods - nested try - nested if/else - too many break/continue - use try-with-resources - repeatable annotations - overlapping characters in reg ex - hashcode is not sufficient in compareTo() - need equals() with compareTo() - make class an interface - use parameterized test - multiple calls in assert() - log or re-throw - use different type of lambda - use parameterized logging - use StringBuilder instead of concatenation - use StandardCharsets.UTF_8 Issue-ID: POLICY-2906 Change-Id: I2cf8c885e3e22c2c6cbe6403a34906928afad022 Signed-off-by: Jim Hahn <jrh3@att.com>
2021-02-18Replace GsonXxxAdaptersJim Hahn14-29/+93
The GsonXxxAdapters were removed from the models Serialization classes and replaced with type adapters from common. Modified the code to refer to the new adapters. Without this fix, examples-onap-vcpe will not compile. Could that be the cause of the apex-pdp standalone issue, POLICY-3066? Allow TypeAdapter in lieu of JsonSerializer/Deserializer adapters in config files. Note: examples-ona-bbs refers to the following, which were removed several releases ago (during the actor re-write?): - appclcm.util.Serialization$RequestAdapter & Serialization$ResponseAdapter Issue-ID: POLICY-2905 Change-Id: Ia57e0346343614cbd4a1cffd9c8393f207284244 Signed-off-by: Jim Hahn <jrh3@att.com>
2021-02-11Fix jackson version in apex-pdpJim Hahn1-1/+12
The kafka_2.12 jar depends on jackson-module-scala, but the default version does not work with the version of jackson used by policy. Modified the dependency tree to include a version that does work. Issue-ID: POLICY-3005 Change-Id: I06fd5b99d6e5c1053e17a754f22f815062f907b2 Signed-off-by: Jim Hahn <jrh3@att.com>
2021-02-11move csit to policy/apex-pdp repoTaka Cho7-0/+7603
move csit to policy/apex-pdp repo Issue-ID: POLICY-2895 Change-Id: I73bd2f59c09f4ae213cab9b1dd2a83e909b218c6 Signed-off-by: Taka Cho <takamune.cho@att.com>
2021-02-11Changes related to multi policy handling improvement in APEXa.sreekumar8-323/+343
This review fixes an issue identified during testing the changes done for improving multiple policy handling in APEX. Changes done to a few test files in the previous review are reverted as well. Change-Id: I98324da708239d314aadd4c45dc377137fd552ba Issue-ID: POLICY-2883 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
2021-02-10Remove URL and useerid from JMS pluginliamfallon5-44/+55
This review makes the default URL and userid for JMS null, the actual values must be specified as parameters. Issue-ID: POLICY-3035 Change-Id: I9c06d94d8816092425e2df58b849d837ad953fb2 Signed-off-by: liamfallon <liam.fallon@est.tech>
2021-02-08Remove security credentials from JMS pluginliamfallon4-26/+40
The default security credential of "password" was encoded in a constant in the JMS plugin parameters file. This commit removes these credentials and defaults the credentials to null. Issue-ID: POLICY-3035 Change-Id: I6313340e64c893c4f99de78d9dd448ac53d81246 Signed-off-by: liamfallon <liam.fallon@est.tech>
2021-01-28Improve handling of multiple policy in APEX PDPa.sreekumar14-506/+958
Change-Id: Ic4adf5bd8876dc31fc93993298e90389baaa2c39 Issue-ID: POLICY-2883 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
2021-01-20Merge "Add logs for REST request/response in APEX"Ram Krishna Verma5-16/+29
2021-01-20Update Hazelcast version, remove security vulnerabilityliamfallon2-9/+11
Security vulnerabillitles were flagged in CLM in Hazelcast version 3.11-BETA-1. Hazelcast version 4.1.1 removes that vulnerability. The lock handling is slightly different in version 4.1.1 and the old ILock class is removed. The code is updated to use the new FencedLock locks. Issue-ID: POLICY-2943 Change-Id: I0cb7d3cb279fed17b3f8758e55902703491f4b5c Signed-off-by: liamfallon <liam.fallon@est.tech>
2021-01-20Add logs for REST request/response in APEXa.sreekumar5-16/+29
Change-Id: Ibf2cf19a1ec91473d8c655b87a712aa8738848c8 Issue-ID: POLICY-3003 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
2021-01-15Add exception to logsRam Krishna Verma2-8/+8
Fixing the comments from previous review - https://gerrit.onap.org/r/c/policy/apex-pdp/+/116833 Issue-ID: POLICY-2885 Change-Id: I85474b365d92771e6e1b56bba95bde6e319d4ec2 Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
2021-01-13Avoiding unwanted logging in APEX during event processinga.sreekumar12-127/+52
Change-Id: If0c93bfea08025c6c10e3f4572a14088990f415f Issue-ID: POLICY-2885 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
2021-01-06Merge "Changed identifiers to concept identifiers"Liam Fallon8-56/+55
2021-01-06Removing duplicate logging of single response eventa.sreekumar1-4/+2
Change-Id: I88c8f2eea9cb295e422d20222df21a46ef84cd4e Issue-ID: POLICY-2885 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
2021-01-05use jre base 2.2.0 - apexTaka Cho1-1/+1
use jre base 2.2.0 Issue-ID: POLICY-2917 Change-Id: I75ae9f401c3665cfad6bc9657511e8c59fe09d02 Signed-off-by: Taka Cho <takamune.cho@att.com>
2021-01-04Changed identifiers to concept identifiersliamfallon8-56/+55
The policy models tosca classes ToscaPolicyIdentifier and ToscaPolicyIdentifierOptVersion can be used to identify any TOSCA concept, not just TOSCA policies so they are renamed to ToscaConceptIdentifier and ToscaCinceptIdentifierOptVersion respectively. The class ToscaPolicyTypeIdentifier is redundant and is replaced by ToscaConceptIdentifier. Issue-ID: POLICY-2900 Change-Id: I5df89d023949cdf0f649951dbbd81a0b30f44ef6 Signed-off-by: liamfallon <liam.fallon@est.tech>
2020-12-21Merge "Prune superfluous log and exception messages"Liam Fallon10-50/+58
2020-12-17Prune superfluous log and exception messagesgregory.hayes10-50/+58
Large volume exception messages should not be repeated in log messages or in rethrown exceptions. Jira-Link: https://jira.onap.org/browse/POLICY-2885 Issue-ID: POLICY-2885 Signed-off-by: gregory.hayes <gregory.hayes@est.tech> Change-Id: I345531d3a7640cc5ad9dbfc367052b9c8cc19387
2020-12-07move all bash to ash shell scripts - apexTaka Cho8-129/+200
bash scripts convert to ash Issue-ID: POLICY-2847 Change-Id: I4617223d4914820797f5ea121f75ee5f69a6ba40 Signed-off-by: Taka Cho <takamune.cho@att.com>
2020-11-16Merge "Update vCPE example for JSON Stringify"Jim Hahn6-9/+30
2020-11-16Merge "Update gRPC example for JSON Stringify"Jim Hahn2-5/+48
2020-11-16Apex CLI editor closes standard input/output/errorliamfallon1-2/+9
The Apex CLI editor closes its input and output when it completes. This is correct behaviour when the input and output are files. However, if the input and output are tied to standard input, output, and error then if there are subsequent actions in the JVM (Such as continuing to run Apex as we do in tests), then any output such as logging is lost. This fix checks for standard input/output/error before closing the input and output. Issue-ID: POLICY-2897 Change-Id: Ifa20b62511f770197f30c4a817212a92876dd6a6 Signed-off-by: liamfallon <liam.fallon@est.tech>
2020-11-16Update vCPE example for JSON Stringifyliamfallon6-9/+30
The JSON.stringify() call in the Rhino Javascript interpreter is not working correctly. A previous patch introduced a method into the Apex execution context to provide an alternative method for stringifying JSON. This patch updates the vCPE example in apex to use that new method. Issue-ID: POLICY-2463 Change-Id: I85cc33dc4633b1b6f4c4db3d5ad8579c66d7c18c Signed-off-by: liamfallon <liam.fallon@est.tech>
2020-11-16Update gRPC example for JSON Stringifyliamfallon2-5/+48
The JSON.stringify() call in the Rhino Javascript interpreter is not working correctly. A previous patch introduced a method into the Apex execution context to provide an alternative method for stringifying JSON. This patch updates the gRPC example in apex to use that new method. Issue-ID: POLICY-2463 Change-Id: I7f789c000d53dec60020fda2a6fccd71ef18edc3 Signed-off-by: liamfallon <liam.fallon@est.tech>
2020-11-11Add method to allow JSON conversion to execution context for logicliamfallon5-63/+147
The Rhino JSON.Stringify() method does not work well. This patch allows the user to call schema specific or generic JSON conversion using the schema handling in Apex or not as the developer chooses. Added a single argument stringify2Json() method. Issue-ID: POLICY-2463 Change-Id: I9ec1e0dea2f6cd153b73b2eace63d8806674884d Signed-off-by: liamfallon <liam.fallon@est.tech>
2020-10-28Stability test planwaynedunican1-11/+10
Update to apexPdpStabilityTestPlan.jmx file Issue-ID: POLICY-2831 Change-Id: I76764e0614a523f2e58df04eed01111c59623e09 Signed-off-by: waynedunican <wayne.dunican@est.tech>
2020-10-27Point to snapshot versionsRam Krishna Verma1-3/+3
Issue-ID: POLICY-2875 Change-Id: I8a7dbd9a1f8fbd88a94a85491304e0f75a05969c Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>