#50746 Add option to healthcheck to list all the lint reports
Closed: wontfix by mhonek. Opened by mreynolds.

Issue Description

It would be nice if the healthcheck tool could list all the possible errors it reports on.

It would also be nice to have an option to pick which component to health check (instead of checking all areas). Like, just check replication, or config, or backends, or plugins, etc.


PoC patch that adds listing of checks. Uses lazy object proxy to cease from unnecessary allocation of the instance in case someone wants to just check the listing regardless the instance being real or not.
886a8d75fe1bb8519a5f72925c0b3c3d8e0d1f16.patch

Metadata Update from @mhonek:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

Metadata Update from @mreynolds:
- Issue priority set to: major
- Issue set to the milestone: 1.4.1 (was: 1.4.0)

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

https://pagure.io/389-ds-base/pull-request/50987

Commit 4a55322c fixes this issue

Commit 4a55322 fixes this issue

b3315a55f..66cd2a906 389-ds-base-1.4.3 -> 389-ds-base-1.4.3
db11e8ecc..08eed33d6 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

Metadata Update from @mhonek:
- Issue close_status updated to: None (was: Fixed)

Commit 4610b5f6 relates to this ticket

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

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

Metadata
Related Pull Requests