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

Remove dots from operator reference filenames #50734

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

Conversation

ptgott
Copy link
Contributor

@ptgott ptgott commented Jan 3, 2025

The dots cause issues with our hosting infrastructure, which returns 404s when users make requests for Kubernetes operator reference pages with no trailing slash.

This change returns a filename from the format function in the CRD/CRD docs generator so we can return different file names for CRDs and their docs. It also renames CRD docs pages to include hyphens instead of dots and underscores, and adds redirects.

@ptgott
Copy link
Contributor Author

ptgott commented Jan 3, 2025

Reviewer note: this PR adds redirects to master for a cleaner/easier backport. Since the Docusaurus site doesn't have redirect limits like the Vercel one did, we don't need to worry about only maintaining redirects on the default docs version.

Copy link

github-actions bot commented Jan 3, 2025

Amplify deployment status

Branch Commit Job ID Status Preview Updated (UTC)
paul.gottschling/2025-01-03-dot-404s f781ca9 2 ✅SUCCEED paul-gottschling-2025-01-03-dot-404s 2025-01-03 20:59:28

The dots cause issues with our hosting infrastructure, which returns
404s when users make requests for Kubernetes operator reference pages
with no trailing slash.

This change returns a filename from the format function in the CRD/CRD
docs generator so we can return different file names for CRDs and their
docs. It also renames CRD docs pages to include hyphens instead of dots
and underscores, and adds redirects.
@ptgott ptgott force-pushed the paul.gottschling/2025-01-03-dot-404s branch from 8e68065 to f781ca9 Compare January 3, 2025 20:54
@ptgott
Copy link
Contributor Author

ptgott commented Jan 3, 2025

The prose linter failure is due to a bug in which the GHA workflow passes the name of a deleted file to the linter, which exits with an error. The linter isn't required yet, and I'll plan to fix the error next week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants