Yu Xia
Yu Xia
The add cluster from config is deprecated and a warning log will show if you figure it via config. `{"level":"warn","ts":"2022-07-15T14:38:43.425-0700","msg":"ClusterInformation in ClusterMetadata config is deprecated. Please use TCTL admin tool...
We cannot deprecate the clusterMetadata because we need to know the current cluster and load it from DB. I agree we can do better to refine this cluster metadata. But...
Directly change this could be a non-backward compatible change. One thing we can think of is to add a side effect for this generated child workflow id
It doesn't support if there is pending child workflows. With finished child workflows, I think it should support
TCTL task is tracking in https://github.com/temporalio/tctl/issues/270
With the new proposal, the checkRunID invokes a remote call so it will be a (system) activity? If we introduce a version in the start workflow, will it be easier...
The cluster id is added into the membership app name. https://github.com/temporalio/temporal/pull/3415.
This is merged. https://github.com/temporalio/temporal/pull/6430. The newClient should use dns by default.