Skip to content
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

Only fail user lookup is the user parameter is required #35054

Merged
merged 1 commit into from
Jul 29, 2016

Conversation

lubyou
Copy link
Contributor

@lubyou lubyou commented Jul 29, 2016

What does this PR do?

This PR fixes two functions that broke win_dacl.disableinheritance and win_dacl.enableinheritance.

Previous Behavior

win_dacl.disableinheritance and win_dacl.enableinheritance always failed, because check_inheritance() always returned false when called without the user parameter.

New Behavior

win_dacl.disableinheritance and win_dacl.enableinheritance succeed.

Tests written?

No

Summary

get() and check_inheritance() have an optional user parameter.
While said parameter is optional, the functions in questions
do not treat it as such, which at the very least breaks
disable_inheritance() (used by win_dacl.disableinheritance) and
enable_inheritance (used by win_dacl.enableinheritance), as those
functions call check_inheritance() without the user parameter.

get() and check_inheritance() have an optional user parameter.
While said parameter is optional, the functions in questions
do not treat it as such, which at the very least breaks
disable_inheritance() (used by win_dacl.disableinheritance) and
enable_inheritance (used by win_dacl.enableinheritance), as those
functions call check_inheritance() without the user parameter.
@cachedout cachedout merged commit f34bb7a into saltstack:2016.3 Jul 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants