Skip to content

Commit 5aa9e52

Browse files
authored
Updated cluster argument syntax (#215)
Updating the cluster configu documentation to match the new syntax, see PR: cadence-workflow/cadence#6658 for context
1 parent 46086f9 commit 5aa9e52

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

docs/03-concepts/08-cross-dc-replication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -173,7 +173,7 @@ clusterMetadata:
173173
After the configuration is deployed:
174174
175175
1. Register a global domain
176-
`cadence --do <domain_name> domain register --global_domain true --clusters clusterDCA clusterDCB --active_cluster clusterDCA`
176+
`cadence --do <domain_name> domain register --global_domain true --clusters clusterDCA,clusterDCB --active_cluster clusterDCA`
177177

178178

179179
2. Run some workflow and failover domain from one to another

docs/06-cli/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -190,7 +190,7 @@ cadence --do samples-domain d re
190190
```
191191
If your Cadence cluster has enable [global domain(XDC replication)](https://cadenceworkflow.io/docs/concepts/cross-dc-replication/), then you have to specify the replicaiton settings when registering a domain:
192192
```bash
193-
cadence --domains amples-domain domain register --active_cluster clusterNameA --clusters clusterNameA clusterNameB
193+
cadence --domains amples-domain domain register --active_cluster clusterNameA --clusters clusterNameA,clusterNameB
194194
```
195195

196196
- View "samples-domain" details:

docs/07-operation-guide/05-migration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ First of all, try replicating a single domain to make sure everything work. Here
124124

125125
* 2.1 Assuming the domain only contain `currentCluster` in the cluster list, let's add the new cluster to the domain.
126126
```bash
127-
cadence --address <currentClusterAddress> --do <domain_name> domain update --clusters <currentClusterName> <newClusterName>
127+
cadence --address <currentClusterAddress> --do <domain_name> domain update --clusters <currentClusterName>,<newClusterName>
128128
```
129129

130130
Run the command below to refresh the domain after adding a new cluster to the cluster list; we need to update the active_cluster to the same value that it appears to be.

0 commit comments

Comments
 (0)