Replies: 2 comments 2 replies
-
|
More info on #1589. |
Beta Was this translation helpful? Give feedback.
-
|
@decentral1se @geerlingguy @greg-hellings @dmsimard @sshnaidm I hope you will vote for one of the options. I want to see at least 10 votes on that. |
Beta Was this translation helpful? Give feedback.
-
|
I think I've only seen the warning pop up once, so it's not a big deal to me either way. |
Beta Was this translation helpful? Give feedback.
-
|
The rule is now opt-in (#1620). I hope someone will rewrite it so it comes a bit closer to what it should actually do... |
Beta Was this translation helpful? Give feedback.
-
As @felixfontein suggested several times the removal of the no-log-password rule due to its high level of false-positive and false-negative matches, I would like to make a survey among ansible-lint users regarding which direction we should take.
Please note that we already made a change on master that should make it only report when looping is used as for the other cases ansible build-in protection should be enough to avoid leaking secrets. Still, looping is known to easily cause undesired exposures.
Beta Was this translation helpful? Give feedback.
All reactions