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
docs: Fix gRPC API generation for online docs #27014
Conversation
bfd7c61
to
5d4a581
Compare
Netlify preview still works 🎉 |
Edit: No it doesn't, because we pick the Makefile from the repo, not from the image. The CI error was because I missed that we explicitly run |
To generate the gRPC API reference, we copy the "api" repository at the root of the repository to "Documentation/_api". This step is required everywhere we need to build the docs: - Locally, we run it through the "copy-api" target in Documentation/Makefile, before generating the HTML. - Same thing for the Netlify preview, where "copy-api" is a dependency for the "html-netlify" target. - However, on ReadTheDocs, where we generate and host the online documentation, we do not perform this step; nor do we use the Makefile at all. As a workaround, let's simplify the way we access the API reference. Instead of copying the docs, just symlink them from the Documentation directory. Signed-off-by: Quentin Monnet <quentin@isovalent.com>
248ff65
to
9070f8e
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.
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 looks like a reasonable approach to me.
I confirm the issue is fixed on the online doc 🎉 Let's mark this for backports. |
This is an attempt to fix the gRPC API, which is missing from the hosted version of the documentation. Let's try to symlink the
api
directory instead of having an additional step to copy it.I'll mark this PR for backports if it gets merged and if it indeed fixes the API reference on the hosted documentation.