Deploy and observability guidance give contradictory infrastructure ordering
@asrujana-44 is already working on this.
Since Sep 2, 2026.
Assessment
This issue has not been assessed yet.
Description
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.
- Dominant language
- Python
- Stars
- 6k
- Forks
- 670
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from google/agents-cli
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
google/agents-cli#86 ·
-
google/agents-cli#89 · 1 assignee ·
-
google/agents-cli#87 · 1 comment · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
google/agents-cli#85 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
google/agents-cli#84 · 1 comment ·
All issues in google/agents-cli
Similar issues
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DiamondLightSource/dodal#2211 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openml/openml-python#1749 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sipyourdrink-ltd/bernstein#6191 ·