-
Notifications
You must be signed in to change notification settings - Fork 660
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
Add rule for checking no_log is set when passwords are used #1558
Conversation
71cbb5b
to
110aa83
Compare
It's pretty important to ensure, that password won't be logged and thus exposed in the output. So we add linter rule that will check that all tasks, that have "password" in argument are not logged. Signed-Off-By: Dmitriy Rabotyagov <[email protected]>
110aa83
to
c94486d
Compare
You still need to: increase number of rules from 39 to 40 (specific test that fails). For lint I am sure you know how to test locally (tox -e lint). |
cdbee00
to
84e6fe9
Compare
Not sure how to satisfy |
You can fully ignore Codacy is there only as an experiment, but the others must pass, especially the unittesting. Run locally with |
Yep, also saw things failing, but barely understand why tbh. As how |
I fixed them. |
Since we already have old-style unittest, leaving it as is till mass migration to pytest. And ingoring raised by this choice warnings.
0ea7f03
to
9c4f9fe
Compare
It's pretty important to ensure, that password won't be logged
and thus exposed in the output. So we add linter rule that will
check that all tasks, that have "password" in argument are not logged.
Signed-Off-By: Dmitriy Rabotyagov [email protected]