configuration-anomaly-detection
configuration-anomaly-detection copied to clipboard
SREP-222 Adding local testing environment
Adds a way to test cadctl remediations without pushing the metadata.yaml file to the main branch of the configuration-anomaly-detection repository.
Tested on Fedora.
Testing steps: Create a staging cluster. Follow Readme.md instructions for local testing for one of the remediations. Additional actions will be shown as script error messages. After all env vars are set, tools installed , credentials provided the outcome should be the same as normal testing against the upstream OCM Backplane.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 31.86%. Comparing base (
b1691b0) to head (02f4186). Report is 19 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@
## main #458 +/- ##
==========================================
- Coverage 32.08% 31.86% -0.23%
==========================================
Files 35 36 +1
Lines 2425 2492 +67
==========================================
+ Hits 778 794 +16
- Misses 1587 1637 +50
- Partials 60 61 +1
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
Nice work, especially the proxy split @Makdaam :D :heart: I did not manage to finish testing yet, but it does look good
/lgtm /approve
Good stuff!!
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Makdaam, RaphaelBut
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [Makdaam,RaphaelBut]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@Makdaam: all tests passed!
Full PR test history. Your PR dashboard.
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-sigs/prow repository. I understand the commands that are listed here.