Repository navigation
feat: an organization input for organization-level GCP resources (ENG-1196) - #6
Conversation
…-1196) Wires the CLI's --organization fallback as a first-class input and documents it, replacing the extra-args workaround. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Claude: codex sweep (gpt-6.1-sol), pass 1, on head 2a3e88c. The CLI review found no issues. The operator persona said MERGE AFTER FIXES, with one major finding: the README's GCP example pins CLI v0.6.19 while saying organization-level resources need v0.6.27, which is still provisional. Agreed. It is fixed once the simulator release carrying linro-simulator#77 and the plugin-gcp pin exists: the example and the minimum-version line will name that release. This PR stays draft until then. |
…example pins it (ENG-1196) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Claude: resolves the codex sweep's one finding. linro-simulator v0.6.27 is released (tag == merge 74f064a of linro-simulator#77), so the README's minimum-version line (already v0.6.27) is now confirmed, and the GCP example's |
ENG-1196: adds an
organizationinput that passes--organizationto the CLI, for an organization-level GCP resource whose parent is a folder, a project, or unknown until apply. The README's GCP section documents it and drops theextra-argsworkaround.Organization-level resources (folders, tags, access policies and perimeters, Assured Workloads, SCC configs) are simulated from CLI v0.6.27: linro-simulator#77, tag == merge 74f064a, which pins plugin-gcp v0.1.62 from plugin-gcp#83. The README's GCP example now pins that version.
CI's self-test runs the default CLI (v0.2.1), which has no
--organization, so no CI step uses the input. The wiring mirrorsproject.Codex (gpt-6.1-sol): the CLI review found no issues. The persona's one finding, that the example pinned a CLI below the documented requirement, is fixed in fe239b2.
🤖 Generated with Claude Code