Age | Commit message (Collapse) | Author | Files | Lines |
|
Initially, just moving the applicationName and actions as protected
fields got rid of the sonar issue. I included also the supportedPolicyTypes
also. But that triggered another sonar duplicate code, so I had to rename
a few private fields to rid that. Seems like a very sensitive sonar detection
that results in kludgy code.
Issue-ID: POLICY-2681
Change-Id: Ie79a95786cdb80381cbce4b182e9e66a2776e0dd
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Addressed the following sonar issues:
- extract common test method
- too many assertions in a test method
Issue-ID: POLICY-2681
Change-Id: I7438be8286d52cd8479c66542fc785b27448972b
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Changed the artifact IDs of the xacml-pdp applications so they won't
clash with other jar file names.
Issue-ID: POLICY-2848
Change-Id: I844aaf6b2c4d81e52716d840b3a784873c6ce121
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Issue-ID: POLICY-2827
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: Icbe559ceb51f34ec7596516ba0ebe735e086b312
|
|
Issue-ID: POLICY-2550
Change-Id: I05d9af99401991ea867e7ab8d697692c9020b3b7
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-2819
Change-Id: I680120b164881f69f094dd3c979f58eb0e158db8
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Issue-ID: POLICY-2789
Change-Id: I3f2c877874e5fbcd0520b811c984fa8d14b05435
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Issue-ID: POLICY-2789
Change-Id: If4559cbab91f26733590ffb4fdfe702f8fc9168f
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Issue-ID: POLICY-2789
Change-Id: I4acbc0d3c66fe1870bd7f781afeeaccbd2a67846
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Issue-ID: POLICY-2789
Change-Id: Ib708114ead0001e3c7be2d77f830d98f7bcba18c
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
In G-rel, using 2.1.0 base.
Issue-ID: POLICY-2789
Change-Id: I8d1e4387a210326ef356aa452e8f34ac89c143c4
Signed-off-by: Taka Cho <takamune.cho@att.com>
|
|
|
|
Add new generic match application to XACML PDP. This app
will allow ONAP users to design their own matchable policy
types and use StdMatchableTranslator out-of-the box without
any modification. Fills the gap left behind since "configure"
via the Monitoring can support StdCombinedResultsTranslator,
but the Optimization policy types have a specific "closest
match" algorithm tied to them. Gives flexibility.
removed unused import
Issue-ID: POLICY-2596
Change-Id: I0aebae706fb9634e7bb13d78eff0ccc1ae4d752f
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Change-Id: Id8c18b6888128a3efaa96f05d911fde5e6a92694
Issue-ID: POLICY-2757
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
Actually, this does not need to have any specific monitoring
policy type designated because since Frankfurt we added the
feature to support onap.monitoring.*
Issue-ID: POLICY-2772
Change-Id: Ief24550c3e90b7a54ad3c1c381330580ca738798
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Fixing too much complexity for GuardPolicyRequest by breaking
it up into methods.
Added more code coverage to guard translator.
Added missing code coverage for coordination guard, it was below
66% and there were some trivial fixes that were needed. Seems that
a test resource was never really used, or perhaps got omitted in a
previous review.
Issue-ID: POLICY-2590
Change-Id: I1be4ff166e6c43c1c4ea54fdf7e761e22adcaa2d
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
* Added new Policy Guard filter Policy type.
* Enhanced translator tests to ensure bad filter policies
are detected.
* Added new filter application test to ensure new guard
propertly creates xacml policies.
Issue-ID: POLICY-2590
Change-Id: Ifc047a33084ce45b67be98a61f660d7a8c9d8615
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Eclipse reports 2 unused imports and deprecated methods.
Does not show up in sonar, but these are simple fixes.
Issue-ID: POLICY-2590
Change-Id: I41b4b43e8d1d5e88c66a368b47482ef20297a4c1
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Issue-ID: POLICY-2615
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: I8360ee5f3bf30c0ea00b58a1f891ef46e9ea9f00
|
|
Change-Id: I43ed3a85e462327ad45370efcdde3d27f4a79e0f
Issue-ID: POLICY-2738
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
Issue-ID: POLICY-2738
Change-Id: I70febaab7c132b6860a4038c4f89dc19c6826a94
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Adding postman collection for decision api's supported by xacml-pdp.
Currently it is updated as per Guilin first release.
Idea is to update this along with any change in api's.
Once this is merged, will create review to point policy documents to this collection.
Issue-ID: POLICY-2727
Change-Id: Iff516528e4b858f559da2324b4fa53e7426d201d
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-2695
Change-Id: Ie6d4d900610b818b81d8ce92f4bbbefb8d199da5
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-2695
Change-Id: I7be4fdd72aad0ab794a0d5a6919afec5998dad09
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Issue-ID: POLICY-2695
Change-Id: I9e7ba1ec8744b9631a7f0bdb07f72efa1e777755
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Issue-ID: POLICY-2695
Change-Id: I4e392e7a5a014d544293c1c822dfbf077ea46a8c
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Issue-ID: POLICY-2695
Change-Id: I0baedd8711c0886107c48dd99a1b4419949ad791
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
When an error occurs fetching from DMaaP, xacml-pdp should not try again
immediately, but should wait a little bit before retrying. Added the
the fetch timeout property to prevent it from defaulting to -1 when
retrying.
Issue-ID: POLICY-2702
Change-Id: I1b3432854d1e3c68836cf81779e22105a6236fca
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
|
|
Replaced try/catch blocks in policy/xacml-pdp with assertj assertions
Issue-ID: POLICY-2451
Change-Id: I3e6947a61e0000561c7053a1cdede9ae5825e5ca
Signed-off-by: waynedunican <wayne.dunican@est.tech>
|
|
Issue-ID: POLICY-2387
Change-Id: Ia8b5774b6b43e175c86f35ee1468b18d2a151f92
Signed-off-by: RossC <ross.carter@est.tech>
|
|
Somehow missed this sonar issue in one line of code:
- invoke only one method in a junit lambda
Issue-ID: POLICY-2681
Change-Id: I03a6708e0d3ed2a43577a63d0f3cdfc9bd76c8d8
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Addressed issues reported due to updates to the sonar rules:
- invoke only one method in a junit lambda
- complete the assertion
- use assertThat().exists(), canRead(), etc.
Issue-ID: POLICY-2681
Change-Id: I2935f4d0295244ab3b11a57a3bc401c64b695fd1
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Changes for Checkstyle 8.32
Issue-ID: POLICY-2188
Change-Id: Ib7605206d43291f582c035fb84f9c1c55d66d8b3
Signed-off-by: Taka Cho <takamune.cho@att.com>
|
|
Issue-ID: POLICY-2188
Change-Id: I64a115240a71e5014db9cfb66747887e156afb50
Signed-off-by: Taka Cho <takamune.cho@att.com>
|
|
replace with '<>' and
assert statements
Issue-ID: POLICY-2616
Change-Id: Id999d3299918491c06918caaa28c44e2148574bc
Signed-off-by: Taka Cho <takamune.cho@att.com>
|
|
Issue-ID: POLICY-2575
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: Icd6395fe4403b1fc2dd838a5ecdd3295f42639d2
|
|
|
|
Deleted Dbao and replaced it with the shared class in policy-models.
Also had to update the queries and the persistence.xml accordingly.
Issue-ID: POLICY-2581
Change-Id: I59dfa2f37c272796ccebc0f578c9f4e8e1b9c8ab
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
The default provider has been changed to gson, so the provider property
no longer has to be set.
Issue-ID: POLICY-1527
Change-Id: I21f5a3af2bc1d7fc10dc41f58e6e62a04f4bda77
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Issue-ID: POLICY-2581
Change-Id: Ia88f76ff65efe806d3f51f9259471d8e88b65b20
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
|
|
Issue-ID: POLICY-2319
Change-Id: I2f2fe8f565bde0f5986e987e8541fb644241b2d3
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
|
|
Modified the sql script to create the secondary indices.
Issue-ID: POLICY-2581
Change-Id: If0bdaa9d8769e99bd47b8780251d96dba172b3e2
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Change the CLC policy logic to match the udpate Operations History DB
rules. Now if a record has outcome = Started, it is considered
to be in progress. Else it is considered to be complete.
Issue-ID: POLICY-2583
Change-Id: If3f626bfec2d0656e43a26929107f68ff27af020
Signed-off-by: pramod.jamkhedkar <pramod@research.att.com>
|
|
Queries to the operationshistory table will degrade substantially
as more records are added to the DB.
The Dbao class should be moved to policy-models, but for now
we'll just update it in both places (i.e., drools-apps and xacml-pdp).
Issue-ID: POLICY-2581
Signed-off-by: Jim Hahn <jrh3@att.com>
Change-Id: Icc4529e56968ceda4d9b63a8ccea6ba219250506
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Change-Id: I4e2a3a7a89eb3e59111c0a2bff70624d9f987abb
Issue-ID: POLICY-2514
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
Change-Id: I753851b22200de1f69489d13a283832c469fab22
Issue-ID: POLICY-2514
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
Change-Id: I8d3ba3c01708ed0876bfc1c135be7e9106803ce8
Issue-ID: POLICY-2514
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|