-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[improve][doc] Add info for health check CMD and fix incorrect REST API links #16267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Hi @horizonzy, thanks for your support and effort in addressing the REST API issues. Can you pls review this PR? |
horizonzy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
|
Ping @Anonymitaet for review. |
| <TabItem value="REST API"> | ||
|
|
||
| {@inject: endpoint|GET|/admin/v2/brokers/leaderBroker?version=@pulsar:version_number@} | ||
| {@inject: endpoint|GET|/admin/v2/brokers/leaderBroker|operation/getLeaderBroker?version=@pulsar:version_number@} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Do these links go to the specific REST API doc rather than the home page?
- Will you fix all the occurrences in
master?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Yes. The logic has been verified. Theoretically, they can go to the correct place but this cannot be directly verified in the local build because what we use for version numbers is a variable.
- I've corrected all the occurrences that I've searched out in the master branch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I see your point. I didn't expect we have such cases. The search term I use is "@Pulsar:version_number@", to make sure it is injected in the correct place. So these cases are not included. I can resolve them in another PR after verifying the results of this PR on the Pulsar website.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After looking into the MD file, I found the link itself is correct, which contains "@Pulsar:version_number@" and the variable is replaced with the version number of docs as we can see on the website. The only issue is that it is written in a command style, rather than a link. I will commit the updates today.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Anonymitaet the updates for the cmd style have been committed.
| { | ||
| "type": "doc", | ||
| "id": "version-2.8.2/security-basic-auth" | ||
| "id": "version-2.8.3/security-basic-auth" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reminder: any other doc versions need this chapter?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a fix. Other doc versions require this chapter have been implemented in #15734.

Modifications
The preview looks good.

Documentation
doc