From 65138d597f0ab5e440026869d002eb6646da2370 Mon Sep 17 00:00:00 2001 From: Blai Peidro Date: Thu, 17 Sep 2026 01:03:52 +0200 Subject: [PATCH] ci: stop the docs build failing on a fetch nothing needs 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. --- docs/upgrade/upgrading.md | 2 +- .../deploying-a-specific-version-of-awx.md | 2 +- mkdocs.yml | 14 +++++++++++--- 3 files changed, 13 insertions(+), 5 deletions(-) diff --git a/docs/upgrade/upgrading.md b/docs/upgrade/upgrading.md index cd84fbe..259d7a9 100644 --- a/docs/upgrade/upgrading.md +++ b/docs/upgrade/upgrading.md @@ -71,6 +71,6 @@ $ kubectl -n default delete clusterrolebinding awx-operator $ kubectl -n default delete clusterrole awx-operator ``` -Then install the new Ascender Operator by following the instructions in [Basic Install](#basic-install-on-existing-cluster). The `NAMESPACE` environment variable have to be the name of the namespace in which your old Ascender instance resides. +Then install the new Ascender Operator by following the instructions in [Basic Install](../installation/basic-install.md). The `NAMESPACE` environment variable have to be the name of the namespace in which your old Ascender instance resides. Once the new Ascender Operator is up and running, your Ascender deployment will also be upgraded. diff --git a/docs/user-guide/advanced-configuration/deploying-a-specific-version-of-awx.md b/docs/user-guide/advanced-configuration/deploying-a-specific-version-of-awx.md index 30bf32c..635f70a 100644 --- a/docs/user-guide/advanced-configuration/deploying-a-specific-version-of-awx.md +++ b/docs/user-guide/advanced-configuration/deploying-a-specific-version-of-awx.md @@ -36,4 +36,4 @@ spec: init_projects_container_image: myorg/my-mirrored-centos:stream9 ``` -**Note**: The `image` and `image_version` are intended for local mirroring scenarios. `DEFAULT_AWX_VERSION` controls the main Ascender image tag and we are now changing the execution environment default to the same pinned release for `ghcr.io/ctrliq/ascender-ee` unless you override them explicitly. For the current defaults, check [roles/installer/defaults/main.yml](/home/weyerkaa/ascender-operator/roles/installer/defaults/main.yml). +**Note**: The `image` and `image_version` are intended for local mirroring scenarios. `DEFAULT_AWX_VERSION` controls the main Ascender image tag and we are now changing the execution environment default to the same pinned release for `ghcr.io/ctrliq/ascender-ee` unless you override them explicitly. For the current defaults, check [roles/installer/defaults/main.yml](https://github.com/ctrliq/ascender-operator/blob/devel/roles/installer/defaults/main.yml). diff --git a/mkdocs.yml b/mkdocs.yml index 1b26f14..902ca0c 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -48,6 +48,7 @@ nav: - Installation: - Installation: installation/index.md - installation/basic-install.md + - installation/kind-install.md - installation/creating-a-minikube-cluster-for-testing.md - installation/helm-install-on-existing-cluster.md - Migrate: @@ -64,6 +65,9 @@ nav: - Advanced Configuration: - user-guide/advanced-configuration/deploying-a-specific-version-of-awx.md - user-guide/advanced-configuration/redis-container-capabilities.md + - user-guide/advanced-configuration/container-probes.md + - user-guide/advanced-configuration/horizontal-pod-autoscaler.md + - user-guide/advanced-configuration/resource-cleanup.md - user-guide/advanced-configuration/privileged-tasks.md - user-guide/advanced-configuration/security-context.md - user-guide/advanced-configuration/containers-resource-requirements.md @@ -110,9 +114,13 @@ plugins: docstring_style: sphinx merge_init_into_class: yes show_submodules: yes - inventories: - - url: https://docs.ansible.com/ansible/latest/objects.inv - domains: [py, std] + # No page carries a ::: directive, so this handler renders nothing + # today. It used to pull https://docs.ansible.com/ansible/latest/ + # objects.inv to cross reference Python symbols, and that fetch is + # what has been failing the build: the site answers 429 and strict + # mode turns it into an error, so the docs stopped publishing for an + # inventory no page consumes. Put it back beside the first page that + # needs it. markdown_extensions: - admonition