apparmor: Add base test coverage
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
The existing AppArmor functionality is not covered by automated tests. This PR introduces a base coverage for the essential use cases: load and unload profiles into the cluster nodes.
Which issue(s) this PR fixes:
Relates https://github.com/kubernetes-sigs/security-profiles-operator/issues/718
Does this PR have test?
Yes.
Special notes for your reviewer:
Does this PR introduce a user-facing change?
NONE
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: pjbgf
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [pjbgf]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Codecov Report
Merging #1074 (ec1415e) into main (fcb0acd) will not change coverage. The diff coverage is
n/a.
Additional details and impacted files
@@ Coverage Diff @@
## main #1074 +/- ##
=======================================
Coverage 43.92% 43.92%
=======================================
Files 49 49
Lines 5514 5514
=======================================
Hits 2422 2422
Misses 2972 2972
Partials 120 120
@pjbgf: PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Closing in favour of https://github.com/kubernetes-sigs/security-profiles-operator/pull/1684.