dsconf support to control referential integrity plugin.
Metadata Update from @ilias95: - Issue assigned to ilias95
While working on this, I discovered an issue related with the plugin and then a bug. So I decided to work on those first and continue with the dsconf support for the plugin afterwards.
https://pagure.io/389-ds-base/issue/49202 https://pagure.io/389-ds-base/issue/49309
However, I have another question. What does the referint-logchanges attribute configure? I can't find anywhere on the docs what's the meaning of this attribute. And should the user/admin be able to configure its value through dsconf?
Sure, it would be great to have those two issues resolved.
The logchanges is related to the issue 49202, where refint writes what it's doing to it's own log file. We'd rather have this going to the slapi_log_err interface, and we can put this at an appropriate level (likely SLAPI_LOG_PLUGIN). This attribute would then become a "dead attribute".
<img alt="0001-Issue-43-Add-support-for-Referential-Integrity-plugi.patch" src="/lib389/issue/raw/files/ae71d5937a1e1a81f334b3fd5325e2781c383e95886b0a00c3d34295b339fc44-0001-Issue-43-Add-support-for-Referential-Integrity-plugi.patch" />
Depends on #92.
Metadata Update from @ilias95: - Custom field Origin adjusted to None - Custom field Review Status adjusted to None
Metadata Update from @ilias95: - Custom field Review Status adjusted to review (was: None)
Hey mate, I've applied all your other patches, but this one doesn't want to apply along with the other changes. Perhaps it needs a rebase to master?
Yeap, there were some conflicts that I resolved:
<img alt="0001-Issue-43-Add-support-for-Referential-Integrity-plugi.patch" src="/lib389/issue/raw/files/ac788e2b935857e0b89423c9ec7681fdd161dd0e32f066dfb04317ac651aee06-0001-Issue-43-Add-support-for-Referential-Integrity-plugi.patch" />
commit 33534a0 To ssh://git@pagure.io/lib389.git 709d572..33534a0 master -> master
Metadata Update from @ilias95: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.