Repository navigation
Add reserved IP ranges to Vertex AI pipeline jobs - #72560
Merged
Merged
Conversation
SameerMesiah97
left a comment
Contributor
There was a problem hiding this comment.
The test could benefit from a slight adjustment. Looks good otherwise.
LE0-Lin
force-pushed
the
add-vertex-ai-reserved-ip-ranges
branch
from
September 5, 2026 16:49
7e4124e to
2898959
Compare
|
Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions. |
imrichardwu
pushed a commit
to imrichardwu/airflow
that referenced
this pull request
Sep 11, 2026
* Add reserved IP ranges to Vertex AI pipeline jobs * Split Vertex AI pipeline job hook tests
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
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.
Adds
reserved_ip_rangessupport toRunPipelineJobOperatorso Vertex AI pipeline jobs can be restricted to configured VPC IP ranges. The value is propagated through both hook submission paths without collapsingNoneor an empty list, with unit coverage at the operator and SDK boundaries.Tests:
pytest providers/google/tests/unit/google/cloud/hooks/vertex_ai/test_pipeline_job.py(25 passed)pytest providers/google/tests/unit/google/cloud/operators/test_vertex_ai.py -k RunPipelineJobOperator(6 passed)git diff --checkcloses: #62733
Was generative AI tooling used to co-author this PR?
Generated-by: OpenAI Codex following the guidelines
OpenAI Codex was used for limited implementation and testing assistance. All changes were reviewed and validated by me.
Drafted-by: OpenAI Codex (reviewed by @LE0-Lin)