-
Notifications
You must be signed in to change notification settings - Fork 91
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
Fix cpinstall tag for kong-mesh #1532
Conversation
✅ Deploy Preview for kuma ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
5ac5975
to
a4c52b5
Compare
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 just asked a question for my education
@lahabana can we merge this? |
@fabianrbz you need to sign your commit: https://github.com/kumahq/.github/blob/main/CONTRIBUTING.md#sign-your-commits |
a4c52b5
to
16a04bc
Compare
@lahabana done |
There's a slight difference between Kuma and Kong Mesh in terms of the base segment of the docs' url. For Kuma, all the docs live under `/docs/`. Unfortunately, that's not the case for Kong Mesh. Kong docs renders multiple products, so we namespace the docs with the corresponding product name, i.e. they live under `/mesh/`. This commit updates the tag's code so that it uses the base path in which the page is generated as the first url segment. That way we can re-use the code in both platforms. It also modifies the link that is rendered, so that it uses `page.release` instead of `page.version` so that it also works for both docs sites. Signed-off-by: Fabian Rodriguez <[email protected]>
16a04bc
to
9d09be2
Compare
There's a slight difference between Kuma and Kong Mesh regarding the base segment of the docs' URL.
For Kuma, all the docs live under
/docs/
. Unfortunately, that's not the case for Kong Mesh. Kong docs renders multiple products, so we namespace the docs with the corresponding product name, i.e. they live under/mesh/
.This commit updates the tag's code so that it uses the base path in which the page is generated as the first URL segment. That way we can re-use the code on both platforms.
It also modifies the rendered link, so that it uses
page.release
instead ofpage.version
to work for both docs sites.Steps to Reproduce
Visit multi-zone deployments and choose
helm
. Thefollow these steps
link is broken.Did you sign your commit? Instructions
Have you read Contributing guidelines?