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

Fix cpinstall tag for kong-mesh #1532

Merged
merged 1 commit into from
Nov 23, 2023

Conversation

fabianrbz
Copy link
Contributor

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 of page.version to work for both docs sites.

Steps to Reproduce

Visit multi-zone deployments and choose helm. The follow these steps link is broken.

Screenshot 2023-11-16 at 11 29 09

Did you sign your commit? Instructions

Have you read Contributing guidelines?

@fabianrbz fabianrbz requested a review from a team as a code owner November 16, 2023 10:30
@fabianrbz fabianrbz requested review from michaelbeaumont and lobkovilya and removed request for a team November 16, 2023 10:30
Copy link

netlify bot commented Nov 16, 2023

Deploy Preview for kuma ready!

Name Link
🔨 Latest commit 9d09be2
🔍 Latest deploy log https://app.netlify.com/sites/kuma/deploys/655db93dd0717500081351bf
😎 Deploy Preview https://deploy-preview-1532--kuma.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@fabianrbz fabianrbz force-pushed the fix-cpinstall-for-mesh branch from 5ac5975 to a4c52b5 Compare November 16, 2023 10:40
Copy link
Contributor

@lahabana lahabana left a 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

@fabianrbz
Copy link
Contributor Author

@lahabana can we merge this?

@lahabana
Copy link
Contributor

@fabianrbz you need to sign your commit: https://github.com/kumahq/.github/blob/main/CONTRIBUTING.md#sign-your-commits

@fabianrbz fabianrbz force-pushed the fix-cpinstall-for-mesh branch from a4c52b5 to 16a04bc Compare November 20, 2023 09:47
@fabianrbz
Copy link
Contributor Author

@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]>
@fabianrbz fabianrbz force-pushed the fix-cpinstall-for-mesh branch from 16a04bc to 9d09be2 Compare November 22, 2023 08:18
@Automaat Automaat merged commit 31bc302 into kumahq:master Nov 23, 2023
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants