#50937 Update CLI/UI for new backend split configuration
Closed: wontfix 2 years ago by mreynolds. Opened 2 years ago by mreynolds.

Issue Description

With the work for allowing the db backend to be pluggable the database configuration is now split between multiple entries:

cn=config,cn=ldbm database,cn=plugins,cn=config
cn=bdb,cn=config,cn=ldbm database,cn=plugins,cn=config
cn=lmdb,cn=config,cn=ldbm database,cn=plugins,cn=config <--- yet to be implemented, but eventually it will be

The UI/CLI needs to handle this change


Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.4.2 (was: 0.0 NEEDS_TRIAGE)

2 years ago

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

2 years ago

Metadata Update from @mreynolds:
- Assignee reset

2 years ago

Commit a5e0fef relates to this ticket

Commit a5e0fef relates to this ticket

88b5cd3..005fbc7 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

2 years ago

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

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 (was: fixed)

a year ago

Login to comment on this ticket.

Metadata
Related Pull Requests