Deploy and observability guidance give contradictory infrastructure ordering
@asrujana-44 ci sta già lavorando.
Dal 2/9/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Baseline
5a306f8956cb1eeae69f9709de0e4d61b44e11e7 (v1.3.1)
Reproduction
- Check out the baseline commit.
- Compare the deployment workflow in
skills/google-agents-cli-deploy/SKILL.mdwith the Agent Runtime order inskills/google-agents-cli-observability/SKILL.md. - Also inspect the README and Starter Pack migration entry points for an authoritative ordering rule.
Actual behavior
The deploy skill says not to run infra single-project before deployment and describes it as optional. The observability skill says Agent Runtime users must run it before the first deploy. README and the migration guide do not resolve the target/ownership distinction. A user following different entry points can therefore receive opposite instructions.
Issue #2 reports a related downstream symptom: applying Terraform after an imperative Agent Runtime deployment can create or target a second Runtime. This issue tracks the separate documentation root cause across the four user entry points.
Expected behavior
All four entry points should use one decision table:
- Basic Agent Runtime / Cloud Run: deploy directly.
- GKE: deploy performs the required targeted Terraform.
- Terraform-managed observability, any target: run
agents-cli infra single-project --applybefore deploy. - Existing imperative deployment: do not apply Terraform afterward without importing or deleting before switching; otherwise keep imperative ownership and configure observability manually.
Minimal fix
Add the same compact decision table to README, the migration guide, deploy skill, and observability skill; remove the conflicting statements; add a text contract test that requires the table and rejects the old contradictory wording.
Tested fix:
- Fork branch: https://github.com/benagentai93-dot/agents-cli/tree/codex/batch-5-doc-skill-consistency
- Root-cause commit: https://github.com/benagentai93-dot/agents-cli/commit/d68dcdf
Verification
- Documentation contract tests: 7 passed
- Full test suite: 99 passed
ruff check src tests: passedty check src: passeduv build: passed- Built wheel installed normally;
agents-cli --versionreturned1.3.1on Python 3.11 and 3.13
I am not opening a PR because the upstream repository currently does not accept PRs.
- Lingua principale
- Python
- Stelle
- 6k
- Fork
- 670
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di google/agents-cli
-
documentation needs review
Difficoltà 2/5 1-3 ore Idoneità per principianti 92/100
google/agents-cli#86 ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 42/100
google/agents-cli#92 ·
-
When an extension is applied, there is a warning emitted for EVERY commandForse già presa @asrujana-44 l’ha presa 4 giorni fa. Aperta
google/agents-cli#91 · 1 commento · 1 assegnatario ·
-
needs review
Difficoltà 3/5 1-2 giorni Idoneità per principianti 68/100
google/agents-cli#85 · 1 commento ·
-
[Bug] Scaffolded agent card grows a duplicate JSONRPC 0.3 interface on every GET (card_modifier mutates the shared AgentCard)Forse già presa @asrujana-44 l’ha presa 3 giorni fa. Aperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 68/100
google/agents-cli#84 · 1 commento · 1 assegnatario ·
Tutte le issue di google/agents-cli
Issue simili
-
bug status/needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
prowler-cloud/prowler#12887 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
area: desktop platform: macos priority: p3 status: ready type: enhancement
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 92/100
use-agent-os/agent-os#3484 ·
I maintainer di solito rispondono entro 2 giorni
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
open-telemetry/opentelemetry-python-contrib#5113 · 2 commenti · 2 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
external
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
langchain-ai/docs#6255 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno