Files
gcp_solution_architecture_a…/.agents/plans/iter-04-learning-and-skills/steps/step-18.md
Jonathan Boniface f1f6f1b83a feat: load the env file at start-up, trim schema lookups, remove legacy samples
Start-up
- Export the env file's variables for other libraries (the Cloud provider's
  client) into the process environment; the app's own settings and secrets
  are never exported, and a value already in the environment wins.
- Use GOOGLE_GENAI_USE_ENTERPRISE in place of the deprecated
  GOOGLE_GENAI_USE_VERTEXAI.

Target architect
- Look each distinct resource type up once instead of once per setting: in
  the run of 2026-10-07 it made 39 lookups for 8 types and exhausted its
  budget. terraform_schema's find takes several names; budget 30 to 45.
- A cut-off schema outline says so.

Removed, as leftovers of the original pipeline that nothing read
- terraform/ (no longer passed terraform validate), scripts/validate.sh,
  tests/test_package.py and the CI steps that ran on them.
- The sample outputs under docs/ and requirements.yaml.
- CI now pins Terraform 1.14.3, as the container image does.

Plans record the case 01 run: completed at 100% in 18 minutes with no
Revision, against 60 minutes and warnings before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-07 20:06:58 +01:00

2.1 KiB

Step 18 — Implementation Detail

Built on 2026-10-07.

  1. providers/gcp.yaml pins terraform.required_providers.google to hashicorp/google 8.6.0. load_provider requires a source and an exact version.
  2. TerraformRunner.schema(resource_type, block, find) writes a versions file for the pinned providers in a scratch directory, runs terraform init -backend=false and terraform providers schema -json once per process, and keeps the resource schemas in memory. Measured here: 0.6 seconds and a 9.7 MB reply for the Google provider, from the plugin cache.
  3. With resource_type alone it lists the arguments code may set (read-only ones are left out) and outlines every block. With block it gives one block's arguments with descriptions. With find it says where a setting sits, or that the resource type has none. An unknown resource type gets close matches.
  4. The tool is terraform_schema, tier general, given to the target architect, the IaC author and the validator.

Checked against the real provider on 2026-10-07:

  • find="startup_cpu_boost" on google_cloud_run_v2_job: "has no argument or block named like 'startup_cpu_boost'. It cannot be set on this resource type."
  • the same on google_cloud_run_v2_service: template.containers.resources.startup_cpu_boost (bool, optional).

Not done: generated code is not forced onto the pinned version. An agent that writes its own required_providers with another version is validated against that version. The patterns Skill gives it the pinned versions.tf to use.

Tests: tests/tools/test_local.py, "schema lookup", on a stand-in schema; tests/test_providers.py for the pin.

After the run of 2026-10-07 16:59 UTC: the target architect made 39 lookups for 8 distinct resource types and exhausted its budget. find now takes several names separated by commas, the tool's description says the plain lookup lists every argument and block, and agents/target-architect.md asks for one lookup per distinct resource type (budget 45). An outline longer than 8,000 characters is cut with a note to use block or find; 7 of the provider's 1,370 resource types are that long, google_container_cluster the longest.