Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: POLICY-2789
Change-Id: Ib3d48a3cbfe83a33ea9483447dc26e051a44ab2e
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
In G-rel, using 2.1.0 base.
Issue-ID: POLICY-2789
Change-Id: Ib5d85477a0ffe844bf22a3d61d162c71a4319f5a
Signed-off-by: Taka Cho <takamune.cho@att.com>
|
|
Default group will now have match Policy Type.
Issue-ID: POLICY-2596
Change-Id: I53c07b417097dc8250191e6ee8d043488b02562d
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
New guard filter should be advertised by pap.
Issue-ID: POLICY-2590
Change-Id: I7652057d4d759e60c358ee9fad84a8c6a9af6898
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Change-Id: If4613c0fc6f940bc82cf616aba2ba9cc03e1b599
Issue-ID: POLICY-2754
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
|
|
Make the application to return exitCode as 1 when the main process
terminates due to issues such as:
1) Any basic issue in the startup config file causing error and
terminates the main process, for e.g. a wrong name in parameterGroup.
2) Wrong info specified for database connectivity, say wrong username.
This doesn't impact a case where database isn't ready yet and PAP
container comes up first, such waiting is already handled by
initContainer in the oom chart. PAP pod waits for policy-mariadb pod to
be ready first, then only the main process is started and comes to this
point.
3) An invalid port number is specified and the rest server is not able
to start.
These are the some of the scenarios which already makes the main process
of PAP to terminate, and in these cases, an exception is thrown now which
returns the exitCode as 1.
Change-Id: Ie48726bcb36d7304eb60807fbaabbee8245e9c70
Issue-ID: POLICY-2754
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
|
|
Changing the policy component health check to fail if the required
PDP instances are down or not registered with PAP.
The check is performed by comparing the "currentInstanceCount"
& "desiredInstanceCount" fields of PdpSubGroup.
Issue-ID: POLICY-2718
Change-Id: Iad1075d0812f4ef166dfed4f110eff4d9e5f995e
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-2763
Change-Id: I9701a80cca10b9fd49d8060ecb6601097ca5824d
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-2615
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: I077bd1b8ff30b0d0ac620dab37a24cbe7776ca15
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
|
|
Issue-ID: POLICY-2738
Change-Id: Id0b6854fa4849f1a3e019fd76f875b29b8b5cf01
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-2738
Change-Id: Id71e48fd505ef529f3e710166f961f71d73665af
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Issue-ID: POLICY-2695
Change-Id: If21e048fda0375ac03309f520a675a4fd505187d
Signed-off-by: Taka Cho <takamune.cho@att.com>
|
|
Issue-ID: POLICY-2695
Change-Id: I7f30fa9c89d7ad9ddc00644c170d8659f7ee3230
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-2695
Change-Id: I1109acd92121dfeb35e1da94da43f3eac43fcf75
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-2695
Change-Id: I80d696fac311018b23d24d4a82e4423544a4aafc
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-2695
Change-Id: I300a2aa7eede8dbeedf3ebafc9914a62cc47b34e
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
When an error occurs fetching from DMaaP, PAP 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: Ifeb9ca9dc51a5d2080c84ae877781b02c3041001
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Replaced try/catch blocks in policy/pap test cases with assertj
assertions
Issue-ID: POLICY-2451
Change-Id: Ic963558e812b59d321e12fa87e7285732d6761e5
Signed-off-by: waynedunican <wayne.dunican@est.tech>
|
|
Issue-ID: POLICY-2391
Change-Id: I4b4239de3c840f0ecae82d1400a393bfdbbfa5ee
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Somehow missed this sonar on one line of code:
- remove useless assignments
Apparently, sonar only complains about some useless assignments (perhaps
those that do more than copy a constant). Fixed one about which it did
not complain, which appeared immediately before the one about which it
DID complain.
At one point, sonar complained about creating ArrayLists without
specifying the initial size (when it was known). It didn't complain
about this one, but went ahead and fixed it anyway.
Issue-ID: POLICY-2679
Change-Id: I270341195634416db1f8152a95a5822c8d505803
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
Issue-ID: POLICY-2679
Change-Id: I422856527b191a45b30a78bb8520f679ca2e7896
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
|
|
Issue-ID: POLICY-2390
Signed-off-by: puthuparambil.aditya <aditya.puthuparambil@bell.ca>
Change-Id: I42f443c64bcf6652adb9795ee8e71e37d8fa8c71
|
|
Issue-ID: POLICY-2188
Change-Id: I4bfb1019782d6e72feda18ae1414c07e8ed460a2
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Change-Id: I995515659a4b7837bb15120f9c50fa0fd1f5434c
Issue-ID: POLICY-2188
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
replace by assertNotSame
Issue-ID: POLICY-2616
Change-Id: I927dbd8c57654cd2d2ef6262d13d63c79ba9035f
Signed-off-by: Taka Cho <takamune.cho@att.com>
|
|
Modified PAP to discard any messages old than 10 minutes so that
if PAP is unable to communicate with DMaaP and then suddently gets
flooded, it will discard old messages.
Updates per review comments
- made the "max message age" configurable, with a default of 10 minutes
Issue-ID: POLICY-2170
Change-Id: I541c03aabf29482af12a07f51eeb5888bbafbf31
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Issue-ID: POLICY-2575
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: If1bc0bb344e0e07bba0988c9a6caa143eb54b9d1
|
|
Issue-ID: POLICY-2078
Change-Id: I035eceb45e76ef11df0e903b584fcf7f8eb63208
Signed-off-by: RossC <ross.carter@est.tech>
|
|
Creating postman collection for all api's exposed by policy-pap component.
Tested the collection in PFPP lab.
Going forward any change in api's must be updated in the postman collection as well.
So that we maintain a working collection for our users always.
Issue-ID: POLICY-2563
Change-Id: I057c365eaead63019a8327fc6bb393425e692950
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
|
|
Issue-ID: POLICY-2391
Change-Id: I0779d16f69d8d828601f7c39b26f2852b39317d2
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Issue-ID: POLICY-2544
Signed-off-by: aditya.puthuparambil <aditya.puthuparambil@est.tech>
Change-Id: Ia9d33b721dab87b91896612e6efcf65378a5c0ff
|
|
Issue-ID: POLICY-2514
Change-Id: Id780f9bc672cde633cf3d7d42b7c9f98fad0396f
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-2514
Change-Id: Iea5b6375975b0225d5b803cc2500adc46fc83804
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-2514
Change-Id: If25dfb5b31f379a0f41b6a464bab7d926755e49d
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-2514
Change-Id: I8577a3dd2b5fca7d3bc646cb448f866d99d17983
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
|
|
Issue-ID: POLICY-2514
Change-Id: I1d16241856c58f0bd778806e17c718991cf04226
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Issue-ID: POLICY-2454
Signed-off-by: aditya.puthuparambil <aditya.puthuparambil@est.tech>
Change-Id: Ifb7a89d4098e62f9ea3e0689e154f9bdd0e990e3
|
|
Issue-ID: POLICY-2454
Signed-off-by: aditya.puthuparambil <aditya.puthuparambil@est.tech>
Change-Id: I400dc0cf4df57714aac657e735fecc7fd29e6f87
|
|
Tracked it down to the following sequence:
- policies were deployed to the pdp
- received a request to undeploy a policy
- generated a notification for the formerly deployed policy
- this should not have been generated
- undeployed the policy
- received a response from the pdp indicating the policy had
been undeployed
- generated a notification indicating the policy was undeployed
Removed the code that generated a notification when a policy is
initially moved from deployed to undeployed (or vice versa).
Issue-ID: POLICY-2539
Signed-off-by: Jim Hahn <jrh3@att.com>
Change-Id: If175974b5fa5ccda6a1e1ab8fa1326b263bb8005
|
|
This is a more robust solution to the race condition previously
identified with back-to-back deployment requests. The old fix has
been rolled back and replaced with this fix.
Issue-ID: POLICY-2527
Signed-off-by: Jim Hahn <jrh3@att.com>
Change-Id: I2ea93f3a5eaac822abecf5d0745429b95712c861
|
|
|
|
The problem appears to be a multi-threading type of issue:
- PAP sends request to XACML
- JMeter pushes the next deployment request into PAP
- PAP receives response from XACML
- based on request ID, the response is routed to the handler,
but blocks while PAP processes the deployment request
- PAP replaces old list of policies with new, and changes the
request ID
- PAP responds to JMeter
- PAP handles XACML response, even though it's request ID no
longer matches
Modified PAP to no longer replace any messages that are at the
head of the queue.
Fixed the license.
Issue-ID: POLICY-2527
Change-Id: I43218a7d0591649d761e17282189e51d5dbd26ed
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
|
|
Issue-ID: POLICY-2525
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: Iea676911eaa7222949959ed0a7074b1260d8ce87
|