Skip to content

Reorganize Temporal Proxy documentation - #5298

Open
lukeknep wants to merge 1 commit into
docs/clarify-proxy-fail-closedfrom
docs/restructure-temporal-proxy
Open

Reorganize Temporal Proxy documentation#5298
lukeknep wants to merge 1 commit into
docs/clarify-proxy-fail-closedfrom
docs/restructure-temporal-proxy

Conversation

@lukeknep

Copy link
Copy Markdown
Contributor

Summary

  • Reorganize the Temporal Proxy section around operator jobs: evaluate, plan, configure, deploy, operate, and reference.
  • Add a Temporal Cloud quickstart, deployment-planning guide, key-lifecycle guide, centralized operations and troubleshooting guide, and source-verified reference.
  • Split routing and Namespace translation from transport security and authorization while keeping existing public page URLs stable.
  • Preserve and surface the fail-closed clarification from Clarify Temporal Proxy fail-closed encryption #5293 throughout the new information architecture.

Why

The existing section mixes evaluation guidance, configuration, encryption-key operations, troubleshooting, and reference material on a few long pages. This structure makes critical deployment decisions—especially proxy bypass, security boundaries, availability, and key retirement—harder to find and evaluate.

Validation

  • vale --config .vale-ci.ini docs/production-deployment/temporal-proxy
  • yarn lint:mermaid
  • yarn check:orphans
  • yarn build
  • Parsed every YAML example with the repository's YAML dependency.
  • git diff --cached --check

PR stack

This PR is stacked on #5293, which adds the fail-closed clarification incorporated into the reorganized encryption page. Existing Proxy document IDs and slugs are preserved, so this change does not require redirects.

@lukeknep
lukeknep requested a review from a team as a code owner September 10, 2026 15:56
@vercel

vercel Bot commented Sep 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
temporal-documentation Ready Ready Preview Sep 10, 2026 3:56pm UTC

Request Review

@github-actions

Copy link
Copy Markdown
Contributor

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5ebcbcbdda

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread sidebars.js
},
'production-deployment/temporal-proxy/deploy-kubernetes',
'production-deployment/temporal-proxy/operate-troubleshoot',
'production-deployment/temporal-proxy/reference',

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Move the lookup page into References

This entry places a pure lookup page under Deploy to production: reference.mdx consists of release artifacts, command flags, configuration keys, compatibility, and metrics. readme/INFORMATION-ARCHITECTURE.md defines this section as how-tos and explanations while assigning command, configuration, and metrics reference material to References, so move this page—or split its reference material—under /references and link to it from the Proxy section.

AGENTS.md reference: AGENTS.md:L246-L250

Useful? React with 👍 / 👎.

Comment on lines +115 to +118
## Resolve startup failures

The proxy validates its configuration before accepting gateway traffic. Configuration errors include the YAML path of
the invalid field when possible. Check these causes first:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Split troubleshooting by concrete symptom

This catch-all troubleshooting section combines invalid configuration, certificate errors, unavailable upstreams, port conflicts, and KMS failures, followed by another table covering unrelated request failures. readme/INFORMATION-ARCHITECTURE.md requires troubleshooting pages to target one specific error or operational problem, so keep monitoring and routine operations here and move the concrete failure cases into focused pages under docs/troubleshooting/.

AGENTS.md reference: AGENTS.md:L248-L252

Useful? React with 👍 / 👎.

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