Repository navigation
Name the fixed Cloud outbound IP in IP-allowlist adapter texts - #1493
Merged
Merged
Conversation
Atlassian, Mercury, Revolut Business, Snowflake and Splunk told Cloud users to ask support for the egress IP, which is now fixed and shown on the setup page. Name 104.248.242.235 instead, as eMAG and Korea Law already do. Mark Snowflake requiresIpAllowlist (a PAT needs a network policy by default), add a network note to Bitrix24 (portals behind an IP restriction or firewall), and update the Google Maps and T-Bank address hints.
helpcodeai
enabled auto-merge (squash)
November 3, 2026 16:15
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Follow-up to #1487. Cloud now calls every API from the fixed address 104.248.242.235 and shows it on the setup page, but several adapter texts still told Cloud users to "ask support for the current egress IP". A Bitrix24 support ticket today was about exactly this: a portal behind an IP restriction. This PR names the address in the adapters whose provider can refuse unknown IPs.
Changes
104.248.242.235" (same wording style as eMAG and Korea Law).requiresIpAllowlist: true. A PAT only works for a user under a network policy by default, so the allowlist is a setup step, not a side note.Splunk is not flagged
requiresIpAllowlist: only Splunk Cloud needs the allow list; Splunk Enterprise does not.Cloud / self-hosted: texts only. On self-hosted the instructions point to the setup page (which shows
EGRESS_IPSwhen set) and "the address of your server"; the Cloud address is named only as the Cloud case.Type
Testing
Run in the repository root and
packages/backend:node scripts/validate-adapters.mjs --warn: exit 0, 1443 warnings before and after (no new warnings).node scripts/regenerate-catalog.mjs: no diff incatalog.ts.node scripts/adapter-count.mjs --check: OK (695 adapters).node scripts/generate-llms-txt.mjs: no diff.npx jest --maxWorkers=4on the static specs of atlassian, bitrix24, google-maps, mercury, revolut-business, snowflake, tbank pluscatalog.spec.tsandinstruction-facts.spec.ts: 9 suites passed (14836 tests).adapters.service.spec.tsandcatalog-summary.spec.tscould not run locally (shared node_modules without@types/picomatch, unrelated to this change); left to CI.Related Issues
Relates to #1487