Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

'infra single-project' fails when run after `deploy` for agent_runtime

Open
#2 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python, terraform
Domain
cli, cloud, infrastructure

Research direction

Start with the agents-cli deploy and agents-cli infra single-project flows, then read the order-of-operations guidance in skills/google-agents-cli-observability/SKILL.md. Reproduce the commands in that order and verify that single-project updates the existing Reasoning Engine rather than creating a second instance, with observability variables attached to the serving instance.

Written by the indexing model from the issue text.

Description

known issue
Problem

When using Agent Runtime (Reasoning Engine), running agents-cli infra single-project after an initial agents-cli deploy does not work as intended.

infra single-project uses terraform, but deploy does not and uses an API instead. This means that when single-project tries to use terraform to update, it doesn't have visibility into the existing reasoning engine resource already created. So, the terraform apply invoked by single-project silently provisions a second Reasoning Engine instance with the same name.

This leads to:

  • Observability environment variables being wired to the new (empty) instance.
  • The original (serving) instance remaining without observability configuration.
Workarounds

See https://github.com/google/agents-cli/blob/main/skills/google-agents-cli-observability/SKILL.md#order-of-operations-for-agent_runtime-deployments

The short version though: either run single-project before deploy so tracking is properly established, or fix it manually using the above instructions.

Ref: b/504375097

Dominant language
Python
Stars
6k
Forks
670
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from google/agents-cli

All issues in google/agents-cli

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.