fix: Remove redirect_facility to fix broken redirects #678
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes stackabletech/crddocs#44
This came up in stackabletech/crddocs#44. Initial investigation revealed that the
roles-and-role-groups.html
file was not present in the stable (24.7) and nightly (soon 24.11) version of generated files when using the production antor playbook.This playbook is used when Netlify deploys the docs using
make netlify-build
. Local builds usingmake
on the other hand included the file in both versions and as such, the redirect works.Finally, the
redirect_facility: netlify
option was identified as the cause. The generated_redirects
file only contained a redirect fromconcepts/roles-and-role-groups.html
toconcepts/stacklet.html
. This matched with the behaviour we experiences when surfing the live site.Removing this option (and thus using the default facility) potentially fixes the issue. Netlify already provides redirect using the "Pretty URLs" post-processing feature.
References: