Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Review outstanding feedback from #5500 (move a Namespace between Projects)

Aperta
  • Qualcosa non va?
#5,506 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
22/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
cloud, documentation

Direzione di ricerca

Start with the four open review threads on PR #5500, then the pages they name: docs/cloud/connectivity/index.mdx, docs/cloud/connectivity/ip-addresses.mdx, docs/cloud/projects.mdx and limits.mdx. Several checklist items need answers from the Cloud team (feature flag, CLI reference, Nexus Endpoints, limit enforcement), so confirm those before editing. Done means each checkbox is resolved or explicitly deferred, and the tabs in projects.mdx use groupId with the sync behavior checked.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Follow-up to #5500 ("Document how to move a Namespace between Projects"), which is merging as is. Go back through the feedback that was still open at merge time and decide what to change.

Open review threads on #5500

  • docs/cloud/connectivity/index.mdx: two comments from @hsadoyan say the "1 public Connectivity Rule per Project" wording can be confusing. Check whether the final text resolves them.
  • docs/cloud/connectivity/ip-addresses.mdx: "Do we need the same information multiple times?" The per-Project limit sentence repeats in several places on this page. Keep one mention and link to /evaluate/cloud/limits#connectivity-rules.
  • docs/cloud/projects.mdx (CLI tab): the CLI command needs Temporal Cloud CLI 0.1.1 or later. Add the minimum version in place of "a release that supports namespace move-to-project".
  • Copilot's thread on public Connectivity Rule scope (projects.mdx:223): the PR's later commits (e95b9590c through 9ef698f9d) changed the connectivity pages and limits.mdx. Confirm that resolves it, then close the thread.

Items to verify with the Cloud team

  • Release stage. The control plane gates the move behind a per-account feature flag (EnableMoveNamespaceToProject, default off). The page only says to contact Support if Move to Project is missing. Decide whether the section needs a release-stage note.
  • CLI reference. docs/cli/command-reference/cloud/namespace.mdx has no move-to-project entry. Confirm the command has shipped, and check whether the generated reference needs to catch up.
  • Nexus Endpoints. projects.mdx says "Other resources cannot yet be moved from one Project to another." MoveNexusEndpointToProject exists behind the same flag. Confirm whether Nexus Endpoints can move and reword or document accordingly.
  • Destination Project limit. The page says the destination Project must be under its Namespace limit. Confirm where this is enforced.
  • Destination access. The control plane backfills the destination Project's Member role for principals who would otherwise lose visibility of the moved Namespace. Decide whether the access section should say so.

Smaller edits

  • Link to the move section from the Connectivity Rules page, since the move has a rule-specific prerequisite.
  • Rephrase "Access that comes only from the source Project does not carry over" and "Detach rules only when that is the intended result" as reader actions.
  • Tabs in projects.mdx and docs/cloud/manage-access/custom-roles.mdx use groupID. The Docusaurus prop is groupId, so these tabs don't sync. Changing it turns syncing on across repeated groups, so check the behavior before changing it.
Lingua principale
JavaScript
Stelle
175
Fork
333
Merge medio
1g 7h
PR unite (30g)
140

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di temporalio/documentation

Tutte le issue di temporalio/documentation

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.