fix(clickpipes): update region docs to reflect current clickpipe regions#6397
Open
tpanetti wants to merge 1 commit into
Open
fix(clickpipes): update region docs to reflect current clickpipe regions#6397tpanetti wants to merge 1 commit into
tpanetti wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
4 Skipped Deployments
|
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
1 participant
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.
Summary
GCP services now point correctly at their respective regions for all services that did not launch clickpipes prior to June 15th, 2026. This updates the docs to reflect that.
Checklist
Note
Low Risk
Documentation-only wording change in ClickPipes IP allow-list guidance; no application or infrastructure code is modified.
Overview
Updates the List of Static IPs guidance in the ClickPipes intro doc so Google Cloud routing matches current behavior.
The cutoff for using Google Cloud–specific NAT IPs is no longer tied to service creation on or after 27 May 2026. It now depends on whether the service had pre-existing ClickPipes before June 15th, 2026—services without prior ClickPipes use the regional GCP IPs; those with prior ClickPipes keep the default region IPs.
The same June 15th, 2026 / pre-existing ClickPipes wording replaces the old 27 May 2026 / created before phrasing in the eu-central-1 and us-east-2 default-region bullets for Azure and Google Cloud EU/other cases.
Reviewed by Cursor Bugbot for commit 4343174. Bugbot is set up for automated code reviews on this repo. Configure here.