Skip to main content
← Back to list
01Issue
FeatureShippedExtensions
Assigneesstack72

Relationships

#561 Codegen: auto-merge resources across GCP API versions instead of manual ADDITIONAL_VERSION_RESOURCE_FILTER

Opened by stack72 · 6/5/2026· Shipped 6/5/2026

Problem

The GCP codegen pipeline uses ADDITIONAL_VERSIONS + ADDITIONAL_VERSION_RESOURCE_FILTER in codegen/gcp/pipeline.ts to manually control which resources from non-preferred API versions get generated. This is a whack-a-mole pattern — each missing resource requires a manual filter addition (e.g. issue #550 for IAM serviceAccounts).

~30 GCP APIs are on v2+ preferred versions with few resources, potentially missing significant surface area from older versions (cloudbuild, cloudfunctions, cloudtasks, etc.).

Proposed Solution

Change the pipeline to automatically discover and merge resources across all available versions of an API. The scope deduplication logic already handles the projects/organizations merge — the resource filter is redundant with it. This would remove the need for ADDITIONAL_VERSIONS and ADDITIONAL_VERSION_RESOURCE_FILTER entirely.

Investigation needed

  • Survey which v2+ APIs have significant v1 resource surface area
  • Determine whether any older-version resources conflict with preferred-version resources (beyond scope deduplication)
  • Assess blast radius of generating all merged resources
02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 3 MOREPR_MERGEDCOMPLETE

Shipped

6/5/2026, 10:52:48 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack726/5/2026, 9:43:28 PM

Sign in to post a ripple.