-
Notifications
You must be signed in to change notification settings - Fork 338
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
vmware_local_user_manager - shell access #1790
base: main
Are you sure you want to change the base?
Conversation
Build failed.
|
recheck |
Build failed. ❌ ansible-tox-linters FAILURE in 8m 40s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 44s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 32s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 33s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 9m 44s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 8m 32s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I understand the documentation correctly, I don't see how this can be implemented in a way that won't possibly break existing playbooks- at least not as long as there's a default for this parameter. I think it would be better to remove the defaul and ignore the parameter if it isn't set.
We could add a default in the next major release (4.0.0), but would prefer it to be false
because it would be more secure by design. Giving accounts shell access (or any other privileges) should always be done explicitly imho ;-)
Additionally, please add a changelog fragment similar to this one.
SUMMARY
vmware_local_user_manager
Add the possibility to grants or not the "shell access" for user creation or update
ISSUE TYPE
COMPONENT NAME
vmware_local_user_manager
ADDITIONAL INFORMATION