1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2025-03-10 01:46:55 +00:00
kyverno/test/conformance/chainsaw/reports/admission/update-deployment
Mariam Fahmy 8eb081475e
fix: skip processing the oldObject for audit policies (#10233)
* fix: skip processing the oldObject for audit policies

Signed-off-by: Mariam Fahmy <mariam.fahmy@nirmata.com>

* fix: modify error and skip messages

Signed-off-by: Mariam Fahmy <mariam.fahmy@nirmata.com>

* fix: modify the log level

Signed-off-by: Mariam Fahmy <mariam.fahmy@nirmata.com>

---------

Signed-off-by: Mariam Fahmy <mariam.fahmy@nirmata.com>
2024-09-20 12:28:18 +00:00
..
chainsaw-test.yaml fix: skip processing the oldObject for audit policies (#10233) 2024-09-20 12:28:18 +00:00
deployment.yaml fix: skip processing the oldObject for audit policies (#10233) 2024-09-20 12:28:18 +00:00
policy-assert.yaml fix: skip processing the oldObject for audit policies (#10233) 2024-09-20 12:28:18 +00:00
policy.yaml fix: skip processing the oldObject for audit policies (#10233) 2024-09-20 12:28:18 +00:00
README.md fix: skip processing the oldObject for audit policies (#10233) 2024-09-20 12:28:18 +00:00
report-assert.yaml fix: skip processing the oldObject for audit policies (#10233) 2024-09-20 12:28:18 +00:00
update-deployment.yaml fix: skip processing the oldObject for audit policies (#10233) 2024-09-20 12:28:18 +00:00

Description

This test verifies that policy report doesn't change when a resource is updated and the engine response is the same as before.

A policy in Audit mode is created. A deployment is created, the deployment violates the policy and we assert the policy report contains a warn result. The deployment is then updated but it still violates the policy.

Expected result

When the resource is updated and it still violates the policy, the policy report should not change.