Only include users.sudo when a user with sudouser is declared.

[TimJones]

Using users-formula with another formula that manages sudo can cause clashes.
This patch stops users-formula from including the users.sudo state unless a user is specifically defined as a sudouser in the pillar data.

[gravyboat]

@TimJones I feel like the edge case of having a formula that manages sudo, as well as some users that are sudo users might be problematic. Were you able to test that by chance?

[TimJones]

When used along side the sudoers-formula, the result is users being managed in the /etc/sudoers file as well as /etc/suders.d/<user>.
In addition, if the sudoers.included state is invoked, it can result in both sudoers.included and users.sudo trying to manage /etc/sudoers.d/<user>.
As a third, minor, point is that if sudo is not wanted at all, users cannot be used to manage accounts.

[gravyboat]

Cool, I'm going to merge this for the time being. I feel like the include is out of place, but there isn't much that can be done about that due to the way this formula is structure. Thanks for the addition!

[TimJones]

Agreed. Another option would be to move the entire {% if 'sudouser' in user and user['sudouser'] %} block to the top of the state file for better visibility, but I felt that it would be a disproportionally large diff for such a functionally small change.