Compute generation is blocked. Maybe a conflicting model mapping for discovery. #6960

Activity

1. dbolduc

   added

   priority: p3Desirable enhancement or fix. May not be included in next release.Desirable enhancement or fix. May not be included in next release.

   on Sep 23, 2026
2. colinmoy

   added

   api: computeIssues related to the Compute Engine API.Issues related to the Compute Engine API.

   type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

   on Sep 23, 2026
3. coryan commented on Sep 24, 2026

   

   coryan

   on Sep 24, 2026

   Contributor

   More actions

   This is probably disallowed in proto but allowed by discovery + our mapping of resources to services.

   I think discovery service names are cameCase and we convert them to PascalCase.... in any case, the idea of using a module (in snake_case) for both is ours.

   We should look into which one of the two is new, and try to preserve the old name.

   👍React with 👍1Reacted by Darren Bolduc