You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Include reserved_ip_ranges to airflow.providers.google.cloud.operators.vertex_ai.pipeline_job.RunPipelineJobTrigger #62733
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
Hi, I'd like to pick this up now that the two previous PRs (#62739 and #66625) have been closed without an active replacement.
I'll keep the change focused on propagating reserved_ip_ranges through RunPipelineJobOperator and both PipelineJobHook submission paths. I will also cover the compatibility behavior when it is unset, preserve an explicitly empty list, and add focused operator and hook regression tests.
Drafted-by: OpenAI Codex (no human review before posting)
Activity
boring-cyborg commentedon Mar 2, 2026
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
LE0-Lin commentedon Sep 5, 2026
Hi, I'd like to pick this up now that the two previous PRs (#62739 and #66625) have been closed without an active replacement.
I'll keep the change focused on propagating
reserved_ip_rangesthroughRunPipelineJobOperatorand bothPipelineJobHooksubmission paths. I will also cover the compatibility behavior when it is unset, preserve an explicitly empty list, and add focused operator and hook regression tests.Drafted-by: OpenAI Codex (no human review before posting)