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
Fix httpasswd result false positive in test mode #26026
Conversation
@anlutro, is it possible to fix this in another way since the state system relies on the result being |
There might be an underlying issue I'm missing, but my impression is that "no change" should be represented as |
The current behaviour of returning |
|
If that's correct then the other pull request I made with a similar change On Wed, 5 Aug 2015 17:37 Justin Findlay notifications@github.com wrote:
|
I'll take a closer look later tonight, hard to do on the phone! On Wed, 5 Aug 2015 19:36 Justin Findlay notifications@github.com wrote:
|
Sure, thank you for your work on these issues. |
@jfindlay thanks for the clarification in the docs. I think my change is still correct. If at any point in the function there are any changes, there will have been an early return. The changes I made are at a place in the code where no changes have been made, so It looks to me like the author of b23c0fa thought you were supposed to return |
Fix httpasswd result false positive in test mode
Speaking as someone who wasn't clear on what it meant before, it definitely does. Cheers! |
httpasswd.user_exists
currently always shows up as having changed something if ran withtest=True
.