With docker and even with rpms, we could not always guarantee correct operation of setup-ds.pl -u. Instead, we should be running "upgrade" tasks at the server start up instead.
As a server core, we should have upgrade tasks in libslapd. This likely means we need some way to track what version of libslapd we are and our config to perform the upgrade.
Similar, plugins may need to upgrade their details. We should do this in a constructive manner, and I think offering a plugin hook for "upgrade" if the plugin is enabled is a good way to achieve this before server start up.
NOTE: This is partially related to plugin v4.
Metadata Update from @mreynolds: - Custom field type adjusted to defect - Issue set to the milestone: 1.3.7.0
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @firstyear: - Issue status updated to: Open (was: Closed)
@firstyear is this needed?
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.3 (was: 1.3.7.0)
I think it's needed, but only for me to document how to achieve this properly since we've added some code and helpers to achieve this.
https://github.com/marcus2376/389wiki/pull/26
Metadata Update from @firstyear: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/2270
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 (was: fixed)
Login to comment on this ticket.