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>
|
|
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-2789
Change-Id: I3f2c877874e5fbcd0520b811c984fa8d14b05435
Signed-off-by: Jim Hahn <jrh3@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>
|