feat: Expose ActiveClusterSelectionPolicy type (#1469)

* feat: Expose ActiveClusterSelectionPolicy type

* add comment

Author: Shaddoll

client/client.go

@@ -92,6 +92,18 @@ type (
 	// Valid values are QueryConsistencyLevelEventual (served by the receiving cluster), and QueryConsistencyLevelStrong (redirects to the active cluster).
 	QueryConsistencyLevel = internal.QueryConsistencyLevel
 
+	// ActiveClusterSelectionPolicy - Policy for selecting the active cluster to start the workflow execution on for active-active domains.
+	// An example policy is:
+	//   {
+	//     ClusterAttribute: {
+	//       Scope: "region",
+	//       Name: "us-west",
+	//     }
+	//   }
+	// The workflow will be active in the corresponding active cluster of that cluster attribute specified in the policy
+	// If the policy is empty or nil, the workflow will be active in the domain's active cluster.
+	ActiveClusterSelectionPolicy = internal.ActiveClusterSelectionPolicy
+
 	// CancelOption values are functional options for the CancelWorkflow method.
 	// Supported values can be created with:
 	//  - WithCancelReason(...)

internal/client.go

@@ -509,8 +509,7 @@ type (
 		CronOverlapPolicy s.CronOverlapPolicy
 
 		// ActiveClusterSelectionPolicy - Policy for selecting the active cluster to start the workflow execution on for active-active domains.
-		// Note: This doesn't apply to local or active-passive domains.
-		// Optional: defaulted to region sticky strategy with receiver cluster as the active cluster.
+		// Optional: defaulted to nil, if it's nil, the active cluster of the workflow is the domain's active cluster.
 		ActiveClusterSelectionPolicy *ActiveClusterSelectionPolicy
 	}