fix(cloud): repoint 8 dead cloud.google.com doc links - #209
Open
pucedoteth wants to merge 1 commit into
Open
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Nine link occurrences across six skills 404 on Google's current docs host. They sit in the "External Resources" / "Resources" sections that these skills point an agent at, so the agent follows them to a 404. Verified each replacement resolves 200 and covers the same topic as the link text: how-to/rollout-sequencing -> concepts/about-rollout-sequencing load-balancing/docs/overview -> docs/load-balancing-overview gke docs/how-to/secret-manager -> secret-manager/docs/secret-manager-managed-csi-component binauthz getting-started-gke -> binary-authorization/docs/setting-up gke concepts/sandbox -> concepts/sandbox-pods how-to/pod-security-standards -> how-to/podsecurityadmission bigtable docs/reference/sql -> bigtable/docs/googlesql-overview alloydb docs/reference/ -> alloydb/docs/reference/rest After the change all 89 cloud.google.com links under skills/ resolve.
pucedoteth
force-pushed
the
fix-dead-cloud-docs-links
branch
from
August 16, 2026 23:55
6e68625 to
252d71c
Compare
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.
Nine link occurrences across six skills return 404 on Google's current docs host. They sit in the "External Resources" / "Resources" sections these skills point an agent at, so an agent following them lands on a 404.
kubernetes-engine/docs/how-to/rollout-sequencingkubernetes-engine/docs/concepts/about-rollout-sequencingload-balancing/docs/overviewload-balancing/docs/load-balancing-overviewkubernetes-engine/docs/how-to/secret-manager×2secret-manager/docs/secret-manager-managed-csi-componentbinary-authorization/docs/getting-started-gkebinary-authorization/docs/setting-upkubernetes-engine/docs/concepts/sandboxkubernetes-engine/docs/concepts/sandbox-podskubernetes-engine/docs/how-to/pod-security-standardskubernetes-engine/docs/how-to/podsecurityadmissionbigtable/docs/reference/sqlbigtable/docs/googlesql-overviewalloydb/docs/reference/alloydb/docs/reference/restEach replacement was checked for a 200 and for a page title matching the existing link text — e.g.
secret-manager-managed-csi-componentrenders as "Use Secret Manager add-on with Google Kubernetes Engine", which covers both the "Secret Manager Add-on for GKE" and "Google Secret Manager CSI Driver" link texts, andbinary-authorization/docs/setting-uprenders as "Set up for GKE". After the change all 89cloud.google.comlinks underskills/resolve.Only link targets changed; no link text, prose, or code was touched.
Two notes:
skills/andplugins/. The only other failures were ~15registry.terraform.ioURLs, which are not broken — that host returns "Content not available in your region" for every path from my location, including its own root. I left those alone.Unrelated finding
skills/cloud/agent-platform-alert-configuration/scripts/analyze_traffic_test.pyfails for anyone outside Google: it reads mock data fromagent-platform-alert-configuration/_internal, which is not in the repo, not gitignored, and not a submodule, so all 12 of its cases error withFileNotFoundError. The other 13 Python test files pass. I did not touch it because the fix could be either publishing the fixtures or dropping the test, which is your call — happy to file it separately.