-
Notifications
You must be signed in to change notification settings - Fork 1k
feat: Removing old schema #12840
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
feat: Removing old schema #12840
Conversation
Signed-off-by: kushal9897 <kushalag2580@gmail.com>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #12840 +/- ##
==========================================
- Coverage 15.33% 15.32% -0.01%
==========================================
Files 923 923
Lines 100275 100282 +7
==========================================
- Hits 15374 15369 -5
- Misses 83189 83199 +10
- Partials 1712 1714 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Release
Release
Release
Release
|
Hello @MariamFahmy98 , we also want to correct the warning message for the release |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have to remove the old approach for userInfo
and value
as well. You can find here all the functions that check deprecations for the test
command.
IMO we should check the returned value from these functions and if they detect a deprecation being used in the test, the command should fail with an error, preventing the test from running with outdated syntax.
For example, the following code is used to check if there are any deprecations used for the values file:
deprecations.CheckValues(out, path, v) |
I would check the returned value, and if it is
true
, I will return an error and this should prevent the test from running.
cc @eddycharly
Signed-off-by: kushal9897 <kushalag2580@gmail.com>
Explanation
This PR removes support for the deprecated Kyverno CLI test schema, which did not include
apiVersion
andkind
. From now on, test cases must follow the new schema format (apiVersion: cli.kyverno.io/v1alpha1
,kind: Test
).This change improves schema validation consistency and ensures a single test format moving forward.
Related issue
#8928
Milestone of this PR
/milestone 1.15.0
Documentation (required for features)
My PR contains new or altered behavior to Kyverno.
What type of PR is this
/kind cleanup
/kind feature
Proposed Changes
Proof Manifests
Checklist
Further Comments