#49829 no plugin start for export of replication data required
Closed: wontfix by spichugi. Opened by lkrispen.

Issue Description

currently for d2ldif -r we already start the backend in main, together with the replication plugin, persistent search and the eventqueue.

All this is not needed to export replication metadata, it is sufficient to start the backend in the ldbm layer


Metadata Update from @lkrispen:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.0

Metadata Update from @vashirov:
- Issue priority set to: normal
- Issue set to the milestone: FUTURE (was: 1.4.0)

Metadata Update from @mreynolds:
- Issue priority set to: major (was: normal)
- Issue set to the milestone: 1.4.4 (was: FUTURE)

Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1859300

Issue linked to Bugzilla: Bug 1859300

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/2888

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

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)

Metadata