Repository navigation
ci: stop the docs build failing on a fetch nothing needs - #53
Merged
cigamit merged 1 commit intoSep 16, 2026
Merged
Conversation
The documentation has not published since 2026-09-13. Every run fails the
same way:
ERROR - mkdocstrings: Couldn't load inventory
https://docs.ansible.com/ansible/latest/objects.inv through
handler 'python': HTTP Error 429: Too Many Requests
Aborted with 1 errors in strict mode!
The inventory is fetched so that mkdocstrings can cross reference Python
symbols against the Ansible documentation. No page here carries a :::
directive, so the handler renders nothing and the inventory is consumed
by nobody. The build was failing on a network call for a feature the site
does not use. It goes, with a comment saying where to put it back.
Three other things the same build reported, now that it can be read:
Four pages exist but are in no nav entry, so nothing links to them:
kind-install, container-probes, horizontal-pod-autoscaler and
resource-cleanup. They are in the nav now.
upgrading.md linked to #basic-install-on-existing-cluster, an anchor that
is not on that page. It points at the Basic Install page instead.
deploying-a-specific-version-of-awx.md linked to
/home/weyerkaa/ascender-operator/roles/installer/defaults/main.yml, which
is somebody's home directory. It points at the file on the default branch.
Verified with the command CI runs, against docs/requirements.txt:
mkdocs build --strict finishes in two seconds with no warnings and exit
zero.
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
cigamit
approved these changes
Sep 16, 2026
Collaborator
|
Oops closed this one on accident, meant to close mine |
cigamit
approved these changes
Sep 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The documentation site has not published since 2026-09-13. Every run of
Publish the Ascender Operator documentationfails identically:Why that fetch exists, and why it can go
The inventory lets mkdocstrings cross reference Python symbols against the Ansible docs. No page in this repository carries a
:::directive, so the handler renders nothing and the inventory is consumed by nobody. The build has been failing on a network call for a feature the site does not use. Removed, with a comment saying where to put it back when a page needs it.Three more things the build was reporting, once it could be read
naventry, so nothing links to them:kind-install,container-probes,horizontal-pod-autoscaler,resource-cleanup. Added.upgrading.mdlinked to#basic-install-on-existing-cluster, an anchor that is not on that page. It now points at the Basic Install page.deploying-a-specific-version-of-awx.mdlinked to/home/weyerkaa/ascender-operator/roles/installer/defaults/main.yml, somebody's home directory. It now points at the file ondevel.Verification
Run locally with the command CI uses, against
docs/requirements.txt:No warnings, which is what
--strictneeds.