Repository navigation
Add guidance on when to deploy the Registry Server - #1355
Merged
Merged
Conversation
New concept page with a decision matrix for the optional Registry Server versus the Connector Gateway's connector catalog, how registry imports reach the catalog, and keeping connectors in sync with approved records. Link it from the platform setup, Registry Server, and connectors pages. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The documentation implies every published version is retained, but catalog synchronization removes versions absent upstream, potentially misleading readers about preserved approval history.
1 open issue
What changed in this PR
This PR helps platform administrators decide when the optional Registry Server adds value alongside the Connector Gateway's connector catalog.
Changes:
- Adds a catalog comparison, decision matrix, and operating models.
- Explains one-time registry imports and how to keep connectors aligned with approved records.
- Links the guidance from platform setup, registry configuration, connector management, and sidebar navigation.
| File | Description |
|---|---|
sidebars.ts |
Adds the concept page to platform navigation. |
docs/platform/enterprise-platform/index.mdx |
Links deployment decisions to the new guidance. |
docs/platform/enterprise-platform/configure-registry-server.mdx |
Clarifies optional deployment and links the comparison. |
docs/platform/concepts/registry-server-and-connector-catalog.mdx |
Adds deployment criteria, import behavior, and ownership guidance. |
docs/connector-gateway/connectors.mdx |
Explains that registry imports do not follow later entry changes. |
Review effort: Balanced
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
danbarr
marked this pull request as ready for review
November 17, 2026 22:21
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
rdimitrov
approved these changes
Nov 17, 2026
Derek2Tu
reviewed
Nov 18, 2026
This branch was successfully deployed
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
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.

Description
The Registry Server is an optional platform component, but the docs don't say when a deployment needs it alongside the Connector Gateway's connector catalog. Now that the console has no direct registry management, the two catalogs are easy to confuse.
This adds a concept page, "When to deploy the Registry Server," with:
latestentry, with no ongoing link between the connector and the entryIt also links the page from the platform setup overview, Configure the Registry Server, and the import section of Manage connectors.
Type of change
Related issues/PRs
Screenshots
Submitter checklist
Content and formatting
Navigation
sidebars.ts) updated for added, deleted, reordered, or renamed filesReviewer checklist
Content