Perl scripts will be removed. And we should have the replacement for syntax-validate.pl. We should add the CLI option to dsconf schema.
dsconf schema
https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide/syntax-validation#syntax-validation-script
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.4.1
Metadata Update from @spichugi: - Assignee reset
Metadata Update from @spichugi: - Issue assigned to spichugi
As per IRC discussion, let's think about adding it as a part of the healthcheck tool.
I think we should still have a standalone action to run the task in the CLI, but it should also be an option in the healthcheck tool.
Shouldn't it be in one place or the other, not both? Both seems confusing ....
@firstyear IMHO healthcheck tool will be a high level wrapper of several low level checking tools. It makes sens to trigger the checking through both a CLI (and it offers a 1-1 compatibility tool to validate-syntax) and healthcheck tool.
@tbordaz That's correct, what I'm saying is that we should not have 2 places in the cli to trigger the same task.
https://pagure.io/389-ds-base/pull-request/50583
Metadata Update from @spichugi: - 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/3232
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)