For the next major release it would be nice to restructure the cn=config layout. Here are a few ideas:
Metadata Update from @mreynolds: - Custom field type adjusted to defect - Issue set to the milestone: 1.4 backlog
Issue Description For the next major release it would be nice to restructure the cn=config layout. Here are a few ideas: Move logging configuration to separate entry: cn=logging,cn=config
Issue Description For the next major release it would be nice to restructure the cn=config layout. Here are a few ideas:
Move logging configuration to separate entry: cn=logging,cn=config
Yes, but we can do this as part of the logging rewrite perhaps?
Move password policy to separate entry (or new plugin)
New plugin,
Move performance settings to new entry. sizelimts, time limits, ioblocktimeout, fd limits,etc: cn=tuning,cn=config
Yes.
Move ldapi settings
Yes
Move anything that takes up more than 1 config attribute
Lets focus on the bottom three in this change, the top two can happen as part of some other tickets that are inflight for 1.4 :)
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field version adjusted to None - Issue tagged with: RFE
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2322
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.