URL:
https://github.com/SSSD/sssd/pull/583
Author: fidencio
Title: #583: sudo/sysdb regressions
Action: opened
PR body:
"""
This patch set consists in 3 patches:
- sudo_ldap: fix sudoHost=defaults -> cn=defaults: this is a typo that caused
https://pagure.io/SSSD/sssd/issue/3742
- Revert "sysdb custom: completely replace old object instead of merging it":
this one caused
https://pagure.io/SSSD/sssd/issue/3733
- sysdb_sudo: completely replace old object instead of merging it: As far as I understand,
the idea behind cd4590de was to never merged sudo rules. Instead, delete the old one and
add the new one. However, doing this all over place caused the regression mentioned above.
I've checked the other patches that leaded to this one and seems that keeping the
"delete the old one and add the new one" approach may be the cleaner possible
way.
@pbrezina, may I ask you to (re)test
https://pagure.io/SSSD/sssd/issue/3558 in order to be
sure that I won't be adding regressions while trying to fix regressions? Also, I do
believe this approach is cleaner than adding a new boolean flag in sysdb_store_custom(),
do you agree?
"""
To pull the PR as Git branch:
git remote add ghsssd
https://github.com/SSSD/sssd
git fetch ghsssd pull/583/head:pr583
git checkout pr583