Skip to content

docs: clarify Shared deployment isolation on dedicated infrastructure#10787

Merged
keydunov merged 1 commit intomasterfrom
docs/shared-deployments-dedicated-infra-isolation
Apr 30, 2026
Merged

docs: clarify Shared deployment isolation on dedicated infrastructure#10787
keydunov merged 1 commit intomasterfrom
docs/shared-deployments-dedicated-infra-isolation

Conversation

@keydunov
Copy link
Copy Markdown
Member

Adds a note explaining that, for accounts on dedicated infrastructure, Shared deployments are only shared across that customer's own deployments and remain fully isolated from other customers.

Made-with: Cursor

Check List

  • Tests have been run in packages where changes have been made if available
  • Linter has been run for changed code
  • Tests for the changes have been added if not covered yet
  • Docs have been added / updated if required

Adds a note explaining that, for accounts on dedicated infrastructure,
Shared deployments are only shared across that customer's own
deployments and remain fully isolated from other customers.

Made-with: Cursor
@keydunov keydunov merged commit 3ac618e into master Apr 30, 2026
9 of 10 checks passed
@keydunov keydunov deleted the docs/shared-deployments-dedicated-infra-isolation branch April 30, 2026 17:28
@claude
Copy link
Copy Markdown
Contributor

claude Bot commented Apr 30, 2026

Claude finished @keydunov's task in 54s —— View job


Review: docs: clarify Shared deployment isolation on dedicated infrastructure

  • Gather context and review PR diff
  • Review documentation changes
  • Post review feedback

LGTM — this is a clean, well-placed documentation addition.

The PR adds a <Note> callout (10 lines) to the Shared deployment section in docs-mintlify/admin/deployment/deployment-types.mdx, clarifying that on dedicated infrastructure, "Shared" only means shared across the customer's own deployments, not with other customers.

What looks good:

  • Placement: The note is positioned right after the paragraph that describes what "shared" means (line 27–28), which is exactly where a reader might worry about isolation. Good information architecture.
  • Tone: Clear, concise, and reassuring — "never with other customers" and "fully isolated at the infrastructure level" directly address the concern.
  • Cross-reference: The [ref-dedicated-infra] link points to /admin/deployment/infrastructure#dedicated-infrastructure, which I verified exists and has a matching anchor.
  • Component choice: Using <Note> (vs <Warning> or <Info>) is the right fit — it's supplementary context, not a caution or promotional callout.

No issues found. No code changes, no security concerns, no broken links. The commit message and PR description are well-written and follow conventional commit format.

@mintlify
Copy link
Copy Markdown
Contributor

mintlify Bot commented Apr 30, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
cubed3 🔴 Failed Apr 30, 2026, 5:35 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@keydunov keydunov restored the docs/shared-deployments-dedicated-infra-isolation branch April 30, 2026 19:53
@keydunov keydunov deleted the docs/shared-deployments-dedicated-infra-isolation branch April 30, 2026 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant