test(clients): registry live reads use the global location; record live registry findings

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-25 08:48:29 +01:00
co-authored by Claude Sonnet 5.5
parent 438e737ffb
commit 89f556e187
2 changed files with 14 additions and 3 deletions
+2
View File
@@ -218,6 +218,8 @@ Neither discovery nor the docs state these; each is a choice made here:
- `iam.v2.policies.update` (PUT) needs the policy `etag`: `update_deny_policy` reads it first. Whether IAM accepts an empty etag is unread.
- `searchPolicyBindings` (iam v3) is listed under key `policyBindings` from the response schema; no live reply was seen (organization scope, no org access).
Agent Registry location (2026-10-25, project `lisa-448004`, service-account token, after the API was enabled): the registry is global. `v1/agents`, `v1/mcpServers` and `v1alpha/skills`, `v1alpha/publishers` answer 200 on `locations/global` (mcpServers about 200 KB, skills 130 KB per page of 100, skills paginates). On `locations/us-central1`, `v1/agents` and `v1/mcpServers` answer 200 but empty, while `v1alpha/skills` and `v1alpha/publishers` answer 503 UNAVAILABLE after about a minute. The live tests therefore use `global`; a caller with `GOOGLE_CLOUD_LOCATION=us-central1` must build the registry with `location = "global"`.
## Gaps
- The three APIs above are not enabled on the test project, so no response