-
Notifications
You must be signed in to change notification settings - Fork 186
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
Deprecate SkipException to help avoid confusion #3662
Deprecate SkipException to help avoid confusion #3662
Conversation
BTW, this PR breaks the tests of gss and prodsec rules, I raised a MR to resolve the test of gss rules and asked ProdSec team to resolve the prodsec rules as well. |
* Mark SkipException deprecated to help avoid confusion as the dirty parser difference isn't really needed. * Replaced all internal references with SkipComponent. Signed-off-by: Ryan Blakley <[email protected]>
@xiangce Another good catch I tested the other projects but forgot about gss-rules. In addition to your PR, I corrected the issue by adding a back import in insights/core/init.py for SkipException. All tests pass for me now on all projects that I know about. |
@ryan-blakley Thank you. The PR looks good. Our rule repository won't be affected. We haven't been using |
* Mark SkipException deprecated to help avoid confusion as the dirty parser difference isn't really needed. * Replaced all internal references with SkipComponent. Signed-off-by: Ryan Blakley <[email protected]> (cherry picked from commit d46b4eb)
* Mark SkipException deprecated to help avoid confusion as the dirty parser difference isn't really needed. * Replaced all internal references with SkipComponent. Signed-off-by: Ryan Blakley <[email protected]>
Check all that apply:
Complete Description of Additions/Changes:
Mark SkipException deprecated to help avoid confusion as the dirty parser difference isn't really needed. Replaced all internal references with SkipComponent.