Repository navigation
Conversation
Keep older and custom endpoints and link credits connectivity to canonical network requirements for upcoming 8.1. Amp-Thread-ID: https://ampcode.com/threads/T-26fae6b7-6e69-4053-9d3d-7b5c04f2cebc Co-authored-by: Amp <amp@ampcode.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Direct preview links to pages changed in this PR: |
This comment has been minimized.
This comment has been minimized.
Amp-Thread-ID: https://ampcode.com/threads/T-26fae6b7-6e69-4053-9d3d-7b5c04f2cebc Co-authored-by: Amp <amp@ampcode.com>
Keep publication gated on 8.1, describe current behavior concisely, and record documentation conventions. Amp-Thread-ID: https://ampcode.com/threads/T-26fae6b7-6e69-4053-9d3d-7b5c04f2cebc Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-26fae6b7-6e69-4053-9d3d-7b5c04f2cebc Co-authored-by: Amp <amp@ampcode.com>
| - `sourcegraph.com`: the full [Cloudflare IP ranges](https://www.cloudflare.com/ips/), when required by your configured services. | ||
|
|
||
| Keep access to your configured Enterprise Portal endpoint and any other custom endpoints. Do not remove those rules merely because the services gateway is available. | ||
| The gateway is not Cloudflare-proxied and does **not** require Cloudflare's shared IP ranges. This IP covers only these service interactions. Keep separate access rules for code hosts, LLM providers, update/download artifacts, browser access to Enterprise Portal, custom endpoints, and other enabled integrations. |
There was a problem hiding this comment.
@bobheadxi the absence of Cloudflare is not required to mention here, this could be said in fewer words.
I'm curious about a better way to frame this. Telemetry / pings / events / license validity checks / upgrade checks, all sound like "telemetry" to me, wearing my customer hat. services.sourcegraph.com is generic / vague, which creates the need for clarity around this endpoint vs our LLM gateway endpoint. I'm not sure if the LLM gateway should also be served on the same URL / IP / port for easier egress allowlisting, or what level of clarity we need in the docs.
There was a problem hiding this comment.
hmm yeah this is a bit slop. FWIW, a lot of stuff covered now is not telemetry (credit consumption and credit quota checks, site admin notifications broadcast by us)
There was a problem hiding this comment.
WDYT about:
Sourcegraph makes requests to
https://services.sourcegraph.comfor key product capabilities.To ensure a smooth experience, instances must allow [...]
There was a problem hiding this comment.
👍
credit consumption and credit quota checks, site admin notifications
I’m fairly liberal with my definition of telemetry, and these bits fit into the same conversation with the customer admin and their NetSec team.
key product capabilities
I’ll put some thought into this. We can ship your proposed fix and iterate to clarify if needed.
Keep the previous Pings section anchor with a link to the new location. Amp-Thread-ID: https://ampcode.com/threads/T-26fae6b7-6e69-4053-9d3d-7b5c04f2cebc Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-26fae6b7-6e69-4053-9d3d-7b5c04f2cebc Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-26fae6b7-6e69-4053-9d3d-7b5c04f2cebc Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-26fae6b7-6e69-4053-9d3d-7b5c04f2cebc Co-authored-by: Amp <amp@ampcode.com>
This branch was successfully deployed
3 participants
Document
services.sourcegraph.comoutbound access on34.36.231.254:443(HTTPS and HTTP/2 gRPC), linked from telemetry, Pings, and Credits. Add timeless documentation guidance toAGENTS.md.Merge after 8.1 releases. Related: client, upgrade notes, legacy RPC removal, and infrastructure gateway, retained IP, DNS.
Checks: build, links/anchors, filenames, images, spelling, hostnames, and rendered-page inspection.