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

chore: adapt apidocs-gen script to use kconf definitions #689

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

czeslavo
Copy link
Contributor

@czeslavo czeslavo commented Oct 3, 2024

What this PR does / why we need it:

It makes the scripts/apidocs-gen script include kubernetes-configuration types that KGO support in the generated markdown reference.

From now on, all new types that shall be included in the documentation need to be annotated with the new +apireference:kgo:include.

It depends on Kong/kubernetes-configuration#110.

Which issue this PR fixes

Part of Kong/kubernetes-configuration#105.

@czeslavo czeslavo added documentation Improvements or additions to documentation area/crds labels Oct 3, 2024
@czeslavo czeslavo added this to the KGO v1.4.x milestone Oct 3, 2024
@czeslavo czeslavo self-assigned this Oct 3, 2024
@czeslavo czeslavo force-pushed the chore/generate-docs-markdown-from-kconf branch 4 times, most recently from e2d2f75 to 03410f4 Compare October 3, 2024 12:26
@czeslavo czeslavo marked this pull request as ready for review October 3, 2024 12:27
@czeslavo czeslavo requested a review from a team as a code owner October 3, 2024 12:27
@czeslavo czeslavo force-pushed the chore/generate-docs-markdown-from-kconf branch 4 times, most recently from 798ea04 to 37edec5 Compare October 3, 2024 12:50
@czeslavo czeslavo force-pushed the chore/generate-docs-markdown-from-kconf branch from 37edec5 to 6ee6a7c Compare October 3, 2024 13:32
Comment on lines +91 to +92
- Annotate the CRD and any new type it depends on with the right markers to make sure it will be included
in the generated documentation. See [available markers][available-markers].
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there an option crd-ref-docs that would allow us to just add this annotation on a package instead of adding it to every type (which can be error prone)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/crds documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants