IMHO we have two separate issues here, both of which need to be addressed:
First, and most important, installing an update for the sssd package MUST NOT revert an intentional local configuration change. If you insist in adding `sss` to the `sudoers` line in nsswitch.conf on initial installation, you'll need to do it in such a way that it *only* happens on initial installation, and not on every update.
Second, sssd should handle that configuration more gracefully, as proposed by 4tro in comment #24.
But the first issue is the much more urgent one. In a company environment you must be able to rely on updates not to destroy your local configuration.
IMHO we have two separate issues here, both of which need to be addressed:
First, and most important, installing an update for the sssd package MUST NOT revert an intentional local configuration change. If you insist in adding `sss` to the `sudoers` line in nsswitch.conf on initial installation, you'll need to do it in such a way that it *only* happens on initial installation, and not on every update.
Second, sssd should handle that configuration more gracefully, as proposed by 4tro in comment #24.
But the first issue is the much more urgent one. In a company environment you must be able to rely on updates not to destroy your local configuration.