1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2025-03-06 16:06:56 +00:00
kyverno/test/conformance/kuttl/reports/background/exception
Charles-Edouard Brétéché 6934c66a71
refactor: add more functionnalities to engine interface (#6212)
* refactor: add more functionnalities to engine interface

Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>

* exclude mechanism

Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>

* fix

Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>

* polex

Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>

* fix kuttl tests

Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>

---------

Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>
2023-02-06 13:49:47 +08:00
..
01-policy.yaml fix: policy exceptions not working in background mode (#5980) 2023-01-13 10:58:02 +00:00
02-exception.yaml fix: policy exceptions not working in background mode (#5980) 2023-01-13 10:58:02 +00:00
03-configmap.yaml fix: policy exceptions not working in background mode (#5980) 2023-01-13 10:58:02 +00:00
04-report.yaml fix: policy exceptions not working in background mode (#5980) 2023-01-13 10:58:02 +00:00
configmap.yaml fix: policy exceptions not working in background mode (#5980) 2023-01-13 10:58:02 +00:00
exception.yaml refactor: add more functionnalities to engine interface (#6212) 2023-02-06 13:49:47 +08:00
policy-assert.yaml fix: policy exceptions not working in background mode (#5980) 2023-01-13 10:58:02 +00:00
policy.yaml fix: policy exceptions not working in background mode (#5980) 2023-01-13 10:58:02 +00:00
README.md fix: policy exceptions not working in background mode (#5980) 2023-01-13 10:58:02 +00:00
report-assert.yaml fix: policy exceptions not working in background mode (#5980) 2023-01-13 10:58:02 +00:00

Description

This test creates a policy, a policy exception and a configmap. It makes sure the generated background scan report contains a skipped result instead of a failed one.

Steps

    • Create a cluster policy
    • Assert the policy becomes ready
    • Create a policy exception for the cluster policy created above, configured to apply to configmap named emergency
    • Try to create a confimap named emergency
    • Assert that an background scan report exists with a skipped result