-
Notifications
You must be signed in to change notification settings - Fork 43
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
[BUG] [RULES] Some rules are being triggered in comments #685
Comments
This issue is currently awaiting triage. |
I don't know if I agree that this is a bug, the rule in question is asking for all the file contents to be searched and is finding the correct values. In some cases, we would still very much want this to find things in comments. I can think of something that we are already considering for these cases, where you can explictly ignore certain incidents, and they will not show up again. The other option, is that we would need to have a new provider capabability, that would tell us what the comments look like, and then add an option to the builtin to ask all the providers what the comments look like and an optional field that would ignore incidents in comments. The third option, is to fix the rules, by taking the line found and chaining it to another conditon that would look for the specific comment lines, like I think the provider capability is probably not worth doing, I would rather focus on rule fixes here IMO. But I did want to make sure that we added the context of what is happening. |
Is there an existing issue for this?
Konveyor version
0.5 beta 1
Priority
Undefined (Default)
Current Behavior
Some rules are triggering false positives when detecting incidents in code comments
Anything else?
Examples:
azure-file-system-02000
azure-file-system-03000
hardcoded-ip-address
The text was updated successfully, but these errors were encountered: