check_http: Adding deprecation text #2118
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
Beside the wording, I think it's also a question if the help output is the right place or if we should also show it in the usage output in any way. |
RincewindsHat
requested changes
Apr 21, 2025
waja
force-pushed
the
check_http_deprecation
branch
from
65fa7c6 to
14169fe
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As I think that #1806 will not happen soon, I think we should start informing users about deprecation of
check_http.I'm right now in the process of getting the Debian monitoring-plugins package bringing into shape for the upcoming Trixi release. This would be a great opportunity to patch
check_httpto bring our plans to the attention of the (Debian) users. Do you think this is the right way? Is there some better way or something to improve? I'd like to have a patch ready by the end of week 17 this year.Thanks a lot, Jan.