Docs update for EU instance - #513
Open
mindymo wants to merge 11 commits into
Open
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Bucket-2 pages (API/CLI/service-principal reference material with conductor.one baked into many examples) get a callout noting EU tenants substitute c1eu.ai, placed at each section that actually has domain examples rather than once at the top. Also fixes a leftover stale callout color in qs-set-up-c1.mdx. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ist entries Bucket-1 pages (single fixed values a user pastes into a third-party OAuth app or firewall config) now print both the default and EU data residency values side by side, instead of relying on a substitute-this-for-that callout. Also fills a gap in requirements.mdx's firewall allowlist table (tenant and MCP domains were missing their EU counterparts). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Connector and function egress IP allowlists now list both the default and EU instance source IPs, labeled by region, so EU tenants don't accidentally allowlist only the default-instance addresses. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Captures the two treatments used for default-instance vs. EU data residency references: dual-value display for single pasted values, and the pink Callout component for example-heavy reference pages, plus placement rules and when to use each. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Self-hosted connector egress was pointing at the wrong default domain (conductorone.com instead of conductor.one) and didn't have an EU counterpart; also clarifies that hosting region is a one-time choice made at signup.
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.
What this does
Documents the new EU data residency instance option alongside the existing default instance, everywhere the docs reference a
conductor.oneURL, hostname, or IP address that differs by region.How we decided what to change
We audited every
conductor.oneoccurrence in the docs (~200 across ~65 files) and split them into two treatments based on how the value is actually used, not just where it appears:conductor.oneappears repeatedly inside code samples — these get a single callout near the relevant section noting that EU tenants substitutec1eu.ai, rather than rewriting every code block. On pages where the examples are spread across several unrelated sections, the callout is repeated at each one so it stays adjacent to what it's describing.The "Hosting regions" table in Create a C1 tenant is the canonical explainer both treatments assume the reader has seen.
Open questions — resolved
product/admin/requirements.mdx,baton/deploy.mdx) — turned out the existing default value itself was wrong (*.conductorone.cominstead of*.conductor.one), independent of the EU question. Both files now list*.conductor.onefor the default instance and*.c1eu.aifor EU.product/admin/email-provider.mdxand its 4 platform-specific pages) — confirmedno-reply@conductorone.comis the sender for both regions. No doc changes needed.product/how-to/qs-set-up-c1.mdx) — confirmed it's a one-time choice made at signup; added a one-line clarification to the "Hosting regions" section.Open questions — still open
product/admin/requirements.mdx,product/intro.mdx,product/release-notes.mdx) — whether EU gets a separate status page or sharesstatus.conductorone.comis still being decided internally. Leaving these references as-is until that's settled.