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
refactor: Require ActiveClusterName for active-active domains (#7304)
<!-- Describe what has changed in this PR -->
**What changed?**
Requires ActiveClusterName to be set for active-active domains
<!-- Tell your future self why have you made these changes -->
**Why?**
Active-Active domains will use the ActiveClusterName as the "default"
ActiveCluster for any workflows that do not specify a valid `scope:name`
ClusterAttribute. This makes migration simple (existing domains can just
start adding ClusterAttributes to divide work).
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
**How did you test it?**
Unit tests + simulations.
Canary to come.
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
**Potential risks**
The existing Canary or Simulation tests may start to fail. I plan on
validating that they do not prior to merging.
<!-- Is it notable for release? e.g. schema updates, configuration or
data migration required? If so, please mention it, and also update
CHANGELOG.md -->
**Release notes**
Active-Active domains now require an ActiveClusterName.
<!-- Is there any documentation updates should be made for config,
https://cadenceworkflow.io/docs/operation-guide/setup/ ? If so, please
open an PR in https://github.com/cadence-workflow/cadence-docs -->
**Documentation Changes**
N/A
0 commit comments