What is a Temporal namespace?

A namespace is a logical isolation unit within a Temporal cluster that provides independent task queues, workflow IDs, and configuration settings like data retention.

What are Nexus endpoints used for?

Nexus endpoints facilitate cross-namespace communication, allowing workflows in one namespace to start or interact with workflows in a different namespace securely.

How do I update a namespace retention period?

You can use the 'temporal operator namespace update' command with the --retention flag, or use the timelord-cli extensions provided in this skill.

Which multi-tenancy pattern should I use?

The skill outlines three main patterns: Namespace Per Team (clear ownership), Namespace Per Environment (isolation), and Namespace Per Service (independent scaling).

Does this skill support custom search attributes?

Yes, it provides guidance on creating and managing searchable fields like Keywords, Integers, and Datetimes to help you filter and monitor workflows.

Temporal Namespace Management

Name: Temporal Namespace Management
Author: therealbill

bytherealbill

0•

Infraestructura en la Nube

Manages and configures Temporal namespaces for workflow isolation, multi-tenancy, and resource organization.

The Namespace Management skill provides a comprehensive toolkit for organizing and scaling Temporal workflow environments. It guides users through creating and updating namespaces using the Temporal CLI, Go SDK, and specialized timelord-cli tools. With detailed patterns for multi-tenancy, retention policy configuration, search attribute management, and Nexus endpoint routing, this skill ensures that developers and SREs can maintain secure, scalable, and well-isolated workflow ecosystems across development and production environments.

Características Principales

01Configuration of data retention periods and archival settings

02Nexus endpoint setup for secure cross-namespace workflow routing

03Custom search attribute definition for business-specific workflow filtering

040 GitHub stars

05Automated namespace creation and lifecycle management via CLI and SDK

06Multi-tenancy pattern implementation (Team, Environment, or Service-based)

Casos de Uso

01Implementing complex multi-tenant architectures using Nexus for cross-service calls

02Migrating production workflow data between namespaces with zero downtime

03Setting up isolated workflow environments for different engineering teams

Características Principales

01Configuration of data retention periods and archival settings

02Nexus endpoint setup for secure cross-namespace workflow routing

03Custom search attribute definition for business-specific workflow filtering

040 GitHub stars

05Automated namespace creation and lifecycle management via CLI and SDK

06Multi-tenancy pattern implementation (Team, Environment, or Service-based)

Casos de Uso

01Implementing complex multi-tenant architectures using Nexus for cross-service calls

02Migrating production workflow data between namespaces with zero downtime

03Setting up isolated workflow environments for different engineering teams