Skip to content
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

[Website]Update route jump for restapi endpoint #8898

Conversation

tuteng
Copy link
Member

@tuteng tuteng commented Dec 10, 2020

Motivation

This is an update after #8888, functions should jump to /functions-rest-api, source should jump to /source-rest-api, sink should jump to /sink-rest-api

Modifications

  • Update route jump
  • Update markdown content render

Verifying this change

  • Make sure that the change passes the CI checks.

image
image

When release website, pulsar:version_number will be automatically replaced with the current pulsar version number

Documentation

  • Does this pull request introduce a new feature? (yes / no)
  • If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
  • If a feature is not applicable for documentation, explain why?
  • If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

@tuteng tuteng self-assigned this Dec 10, 2020
@tuteng tuteng added area/build component/website type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages labels Dec 10, 2020
@tuteng tuteng changed the title Fix/add version number for doc endpoint update [Website]Update route jump for restapi endpoint Dec 10, 2020
@tuteng tuteng added this to the 2.8.0 milestone Dec 10, 2020
@sijie sijie merged commit 9547dc0 into apache:master Dec 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants