Age | Commit message (Collapse) | Author | Files | Lines |
|
Use an account other than healthcheck in PAP for provisioning of policies.
Issue-ID: POLICY-2744
Change-Id: I897f7a4fffbac2d4bbd9cceb059bae1794753aa7
Signed-off-by: adheli.tavares <adheli.tavares@est.tech>
|
|
Update postman collection in pap to sync with recent changes made in audit & statistics api's.
Issue-ID: POLICY-3528
Change-Id: I38fe28cb6f7303ecb78f74c3546dee1962af9531
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Adding policy audit api's to the postman collection in pap.
Issue-ID: POLICY-3340
Change-Id: Ic549ad2e242dd611cac5434b5fc7b0ec052db3ac
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
The Pdp Policy Status is not updated during the pdp heartbeat
handling/registration flow, or during State change.
When a PDP goes down the pdppolicystatus gets cleared. But when the PDP
comes back online, PAP deploys the right policies into it, but the
deployment status was not getting updated.
Similarly, when the State is changed to PASSIVE, the status should be
undeployed, and when the state is changed back to ACTIVE, then the
status should be deployed for any active policies in any PDP.
These issues are fixed here.
Updating postman collection.
Also updating the csit test to check for 202 instead of 200 for the
deployment api response.
Change-Id: I1e05f22df23daaa8da8be1376413e995be2376f3
Issue-ID: POLICY-2526
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
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>
|