You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9c0f306
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: nexus_standalone_operations/README.md
+73-26Lines changed: 73 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,12 +2,17 @@ This sample demonstrates how to execute Nexus operations directly from client co
2
2
without wrapping them in a workflow. It shows both synchronous and asynchronous
3
3
(workflow-backed) operations, plus listing and counting operations.
4
4
5
+
The starter and worker connect to two different namespaces (a "caller" namespace and a "handler"
6
+
namespace) — this mirrors how Nexus is typically used to cross namespace boundaries. The client is
7
+
configured via the SDK's [environment configuration](https://docs.temporal.io/develop/environment-configuration)
8
+
support (`ClientConfig.load_client_connect_config()`), which reads `TEMPORAL_NAMESPACE`,
9
+
`TEMPORAL_ADDRESS`, etc. from the environment (and optionally profiles from `temporal.toml`).
5
10
6
11
### Temporal Python SDK support for Standalone Nexus Operations is at [Pre-release](https://docs.temporal.io/evaluate/development-production-features/release-stages#pre-release).
7
12
8
13
All APIs are experimental and may be subject to backwards-incompatible changes.
9
14
10
-
Standalone Nexus operations require a server version that supports this feature. Use the dev server build at https://github.com/temporalio/cli/releases/tag/v1.7.3-standalone-nexus-operations.
15
+
Standalone Nexus operations require a server version that supports this feature. Use the dev server build at https://github.com/temporalio/cli/releases/tag/v1.7.4-standalone-nexus-operations.
11
16
12
17
### Sample directory structure
13
18
@@ -16,38 +21,36 @@ Standalone Nexus operations require a server version that supports this feature.
16
21
-[worker.py](./worker.py) - Temporal worker that hosts the Nexus service
17
22
-[starter.py](./starter.py) - Client that executes standalone Nexus operations
18
23
24
+
## Run locally against a dev server
19
25
20
-
### Instructions
26
+
1. Start the [Temporal dev server build that supports standalone Nexus operations](https://docs.temporal.io/standalone-nexus-operation#temporal-cli-support) with the required namespaces pre-created:
21
27
22
-
Run the [Temporal dev server build that supports standalone Nexus operations](https://github.com/temporalio/cli/releases/tag/v1.7.3-standalone-nexus-operations).
23
-
(If you are going to run locally, you will want to start it in another terminal; this command is blocking and runs until it receives a SIGINT (Ctrl + C) command.)
28
+
```bash
29
+
./temporal server start-dev \
30
+
--namespace my-caller-namespace \
31
+
--namespace my-handler-namespace
32
+
```
24
33
25
-
Start a Temporal dev server with the dynamic config flags required for standalone Nexus operations:
34
+
2. Create a Nexus endpoint that routes to the handler namespace and the worker's task queue:
0 commit comments