Support numeric project number in GCP Batch service configuration#5275
Merged
Conversation
decoNR
approved these changes
May 13, 2026
PauloVLB
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For context: b/512799286
Description
The GCP Batch API parent field does not support domain-scoped project IDs containing colons (e.g.,
google.com:clusterfuzz), leading to400 parent field is invalidparser errors. Using the numeric project ID (project number) instead bypasses this routing issue.This PR introduces support for configuring a numeric project ID via a new
project-numberattribute in the batch configuration.Changes
project_numberfield toBatchWorkloadSpec(defaulting toNone)._get_specs_from_configto readproject-numberfrom configuration.projectstring ifproject-numberis not provided.project_numberwhen present.