"Purge sudoers.d directory, but leave sudoers file as it is" about puppet-sudo

Yeah I spotted that too the other day and thought it's probably a typo in documentation and should actually be false. Would be nice if someone could also confirm this.

[tosmi]

Yeah, that's a mistake in the docs. the default is true, so the sudo module works on all platforms. this was set to false in version <3 but changed to true afterwards.
this was actually changed before my merge of the augeas redhat 5 fix, so maybe steffen could change it back to false. i would feel more comfortable if this is per default false, but it's up to steffen to decide.
nevertheless i'm going to send a pull request to fix the documentation.

[saz]

This was indeed a mistake in the docs.

@tosmi I've set this to true, as many (including me) are expecting full management of sudo. If the sudoers file isn't replaced by default, this might lead to an unexpected result, which impact might be bigger than locking yourself out.

Locking yourself out might easily be fixed with puppet (maybe it requires some research in a backup, but hey...). For me, the bigger impact might be, if a user can get more rights than expected. The sudoers files in this module should grant almost no special rights.
If you really need the current sudoers file, this should be a decision made by you and you should be fully aware of this.

Anything else isn't something I'd expect from a puppet module.

[tosmi]

i'm ok with that. your module your rules :) we just have some old legacy system with quite a lot of sudo entries were overwritting the sudoers file would really hurt. we just had to be sure we explictly set config_file_replace to false after upgradeing to 3.0.