From 0ce8bc74c345292deea5cb651620fd5d4245b2d1 Mon Sep 17 00:00:00 2001 From: rootkiller6788 Date: Fri, 21 Aug 2026 23:23:06 +0800 Subject: [PATCH] fix(agent-platform-migrate-from-ai-studio): use numeric-project-id metadata key for in-VM project number The in-VM branch of step 3 curls the metadata server's project-id endpoint but uses the result as the project number, interpolating it into the Compute Engine default service account address (${PROJECT_NUMBER}-compute@developer.gserviceaccount.com). The project-id endpoint returns the project ID, so the generated service account address is invalid and the gcloud key creation step fails. Switch to the numeric-project-id metadata key, matching the projectNumber value returned by the out-of-VM gcloud projects describe branch just above. --- skills/cloud/agent-platform-migrate-from-ai-studio/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/cloud/agent-platform-migrate-from-ai-studio/SKILL.md b/skills/cloud/agent-platform-migrate-from-ai-studio/SKILL.md index fec6836823..c757ea8901 100644 --- a/skills/cloud/agent-platform-migrate-from-ai-studio/SKILL.md +++ b/skills/cloud/agent-platform-migrate-from-ai-studio/SKILL.md @@ -264,7 +264,7 @@ echo "Project number: $PROJECT_NUMBER" Within a Compute Engine VM, run: ```bash -export PROJECT_NUMBER=$(curl "http://metadata.google.internal/computeMetadata/v1/project/project-id" -H "Metadata-Flavor: Google") +export PROJECT_NUMBER=$(curl "http://metadata.google.internal/computeMetadata/v1/project/numeric-project-id" -H "Metadata-Flavor: Google") echo "Project number: $PROJECT_NUMBER" ```