From e542e89ce260863335fc6080c88459f379bb2adf Mon Sep 17 00:00:00 2001 From: Andy Stark Date: Tue, 11 Aug 2026 15:23:34 +0100 Subject: [PATCH] DOC-6955 Repoint the Google ADK links at Agent Memory's new home Ten relref calls across three Google ADK pages still named Agent Memory paths that moved to operate/iris. Repointed to the new locations, confirmed with Andy as the right targets rather than assumed, since both pages moved across product areas and a link's intended destination is not always the file's new home. /develop/ai/context-engine/agent-memory/self-managed -> /operate/iris/agent-memory/self-managed (7) /operate/rc/context-engine/agent-memory/create-service -> /operate/iris/agent-memory/create-service (3) The reader-facing damage was worse than the ticket recorded, and only visible on the rendered page. Both old URLs return 200, because the moved pages carry aliases for them, so it looked as though readers were being redirected and only the build was complaining. They were not: relref resolves pages, not aliases, so a relref naming an alias path fails even while that URL works. With refLinksErrorLevel set to WARNING the failure is not fatal, and Hugo emits an empty string -- so the live pages render three `` anchors that go nowhere. Typing the old URL worked; clicking the link did not. Verified against a build rather than by reading the diff. Before: three empty hrefs on the live ADK index. After: zero empty hrefs across all three pages, ten resolved links to the new targets, and no REF_NOT_FOUND anywhere in the build. The six sibling refs to `/develop/ai/context-engine/agent-memory`, its `api-reference` and `/operate/rc/context-engine/agent-memory` are deliberately untouched -- those paths still have real pages, restored as bridges during the restructure, which is why only two of the five targets broke. Worth noting for the next time this happens: DOC-6951's scanner could not have caught this. It reads git rename records and reasons about URLs, and relref targets are resolved at build time from content paths, so broken inbound references are invisible to it. The signal that exists today is a build warning nobody reads. Learned: both dead URLs returned 200 because aliases covered them, which made this look like a build-only complaint -- the rendered page was the only place the empty hrefs showed, so severity had to be read off the HTML rather than the status codes Constraint: relref resolves pages and not aliases, so a relref naming an alias path fails at build time even though that URL serves a redirect Ticket: DOC-6955 Co-Authored-By: Claude Opus 5 (1M context) --- content/integrate/google-adk/_index.md | 6 +++--- content/integrate/google-adk/agent-memory-server.md | 8 ++++---- content/integrate/google-adk/redis-agent-memory.md | 6 +++--- 3 files changed, 10 insertions(+), 10 deletions(-) diff --git a/content/integrate/google-adk/_index.md b/content/integrate/google-adk/_index.md index 7a9917f8c9..8f62525dcb 100644 --- a/content/integrate/google-adk/_index.md +++ b/content/integrate/google-adk/_index.md @@ -25,7 +25,7 @@ weight: 30 adk-redis connects several backend systems to the ADK framework: -- **[Redis Agent Memory]({{< relref "/develop/ai/context-engine/agent-memory" >}})** handles working memory (sessions), long-term memory (extracted facts), auto-summarization, and memory search. Use the default `redis-agent-memory` for new work. It runs either on [Redis Cloud]({{< relref "/operate/rc/context-engine/agent-memory" >}}) or [self-managed]({{< relref "/develop/ai/context-engine/agent-memory/self-managed" >}}) on your own Kubernetes cluster; both share one Data Plane API, so you pick a deployment by pointing `api_base_url` at the right endpoint. +- **[Redis Agent Memory]({{< relref "/develop/ai/context-engine/agent-memory" >}})** handles working memory (sessions), long-term memory (extracted facts), auto-summarization, and memory search. Use the default `redis-agent-memory` for new work. It runs either on [Redis Cloud]({{< relref "/operate/rc/context-engine/agent-memory" >}}) or [self-managed]({{< relref "/operate/iris/agent-memory/self-managed" >}}) on your own Kubernetes cluster; both share one Data Plane API, so you pick a deployment by pointing `api_base_url` at the right endpoint. - **[RedisVL]({{< relref "/develop/ai/redisvl" >}})** (Redis Vector Library) powers the search tools and local semantic cache provider. - **[LangCache](https://redis.io/langcache/)** provides managed semantic caching with server-side embeddings. @@ -44,8 +44,8 @@ which also covers migrating to Redis Agent Memory. Provision a store, then pass its Data Plane endpoint, API key, and store ID to the services. -- On **Redis Cloud**, there is nothing to run. See [Create an Agent Memory service]({{< relref "/operate/rc/context-engine/agent-memory/create-service" >}}). -- To run it **yourself**, see [Self-managed Agent Memory]({{< relref "/develop/ai/context-engine/agent-memory/self-managed" >}}) for deployment, configuration, and operations on your own Kubernetes cluster. +- On **Redis Cloud**, there is nothing to run. See [Create an Agent Memory service]({{< relref "/operate/iris/agent-memory/create-service" >}}). +- To run it **yourself**, see [Self-managed Agent Memory]({{< relref "/operate/iris/agent-memory/self-managed" >}}) for deployment, configuration, and operations on your own Kubernetes cluster. Both use `backend="redis-agent-memory"`. Only `api_base_url` differs. diff --git a/content/integrate/google-adk/agent-memory-server.md b/content/integrate/google-adk/agent-memory-server.md index cd6b88d7c9..014af63144 100644 --- a/content/integrate/google-adk/agent-memory-server.md +++ b/content/integrate/google-adk/agent-memory-server.md @@ -30,7 +30,7 @@ New agents should use [Redis Agent Memory]({{< relref "/integrate/google-adk/redis-agent-memory" >}}) with `backend="redis-agent-memory"`, on [Redis Cloud]({{< relref "/operate/rc/context-engine/agent-memory" >}}) or -[self-managed]({{< relref "/develop/ai/context-engine/agent-memory/self-managed" >}}) +[self-managed]({{< relref "/operate/iris/agent-memory/self-managed" >}}) on your own Kubernetes cluster. This page exists only to help existing deployments migrate. @@ -64,8 +64,8 @@ like Redis Cloud. You choose a deployment with `api_base_url`, not with ## Migrate to Redis Agent Memory 1. Provision a Redis Agent Memory store, on - [Redis Cloud]({{< relref "/operate/rc/context-engine/agent-memory/create-service" >}}) - or [self-managed]({{< relref "/develop/ai/context-engine/agent-memory/self-managed" >}}). + [Redis Cloud]({{< relref "/operate/iris/agent-memory/create-service" >}}) + or [self-managed]({{< relref "/operate/iris/agent-memory/self-managed" >}}). Either gives you a Data Plane endpoint, an API key, and a store ID. 2. Change `backend` from `opensource-agent-memory` to `redis-agent-memory` on every service and tool config, or drop the field, since it is the default. @@ -120,5 +120,5 @@ switches backends with `REDIS_MEMORY_BACKEND`, so it already runs on ## More info - [Redis Agent Memory]({{< relref "/integrate/google-adk/redis-agent-memory" >}}): the supported backend -- [Self-managed Agent Memory]({{< relref "/develop/ai/context-engine/agent-memory/self-managed" >}}): run Agent Memory on your own Kubernetes cluster +- [Self-managed Agent Memory]({{< relref "/operate/iris/agent-memory/self-managed" >}}): run Agent Memory on your own Kubernetes cluster - [Agent Memory Server on GitHub](https://github.com/redis/agent-memory-server): the deprecated server's own documentation diff --git a/content/integrate/google-adk/redis-agent-memory.md b/content/integrate/google-adk/redis-agent-memory.md index fc1dbe806b..3274e1c26e 100644 --- a/content/integrate/google-adk/redis-agent-memory.md +++ b/content/integrate/google-adk/redis-agent-memory.md @@ -31,8 +31,8 @@ not by changing `backend`: | Deployment | `api_base_url` | Setup | |------------|----------------|-------| -| Redis Cloud | Your Redis Cloud Agent Memory endpoint | [Create an Agent Memory service]({{< relref "/operate/rc/context-engine/agent-memory/create-service" >}}) | -| Self-managed | Your own Data Plane URL | [Self-managed Agent Memory]({{< relref "/develop/ai/context-engine/agent-memory/self-managed" >}}) | +| Redis Cloud | Your Redis Cloud Agent Memory endpoint | [Create an Agent Memory service]({{< relref "/operate/iris/agent-memory/create-service" >}}) | +| Self-managed | Your own Data Plane URL | [Self-managed Agent Memory]({{< relref "/operate/iris/agent-memory/self-managed" >}}) | {{< note >}} Running Agent Memory yourself does not mean using the deprecated @@ -250,6 +250,6 @@ Redis Cloud or self-managed; use the REST tools above. - [Integration patterns]({{< relref "/integrate/google-adk/integration-patterns" >}}): Detailed tradeoff comparison of the approaches - [managed_memory_quickstart](https://github.com/redis-developer/adk-redis/tree/main/examples/managed_memory_quickstart): Framework services, no Docker - [travel_agent_memory_tools](https://github.com/redis-developer/adk-redis/tree/main/examples/travel_agent_memory_tools): REST tools only -- [Self-managed Agent Memory]({{< relref "/develop/ai/context-engine/agent-memory/self-managed" >}}): run Agent Memory on your own Kubernetes cluster +- [Self-managed Agent Memory]({{< relref "/operate/iris/agent-memory/self-managed" >}}): run Agent Memory on your own Kubernetes cluster - [Agent Memory Server (deprecated)]({{< relref "/integrate/google-adk/agent-memory-server" >}}): existing deployments and migration