Replies: 2 comments
-
There was work started some time ago to add a query mode with state:query. But this was not completed yet. |
Beta Was this translation helpful? Give feedback.
0 replies
-
The issue is that the returned information could be huge as it is possible to have mass multi user tasks. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The thing is that if you want to modify information about a user, with the ansible module, only in the case that this user is enabled, I think is not possible to let the user in the same state that it was before.
I mean, if I want to change any user parameter only if the user is in state "enabled", the ipauser module will affect the current state. If an admin have changed it before to "disabled" (for instance), but I ignore that, the module will change the state to "present" (user enabled) unless you know previously that the state was "disabled", and you put that explicitly in the playbook.
I think it could be helpful to have an option in the module to retrieve all information for a user, without changing the current state, even if you don't know the state before using it.
Or if there where an state for "preserve state" (don't do anything with the current state).
It's maybe a dumb question... or does it was a developement decision for any security reason?
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions