-
Notifications
You must be signed in to change notification settings - Fork 67
Wire enableReplication into cli #881
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: next-server
Are you sure you want to change the base?
Conversation
|
|
go.mod
Outdated
| go.temporal.io/sdk v1.37.0 | ||
| go.temporal.io/sdk/contrib/envconfig v0.1.0 | ||
| go.temporal.io/server v1.29.1 | ||
| go.temporal.io/server v1.30.0-147.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR needs to target next-server branch IMO (unsure if has had main merged into it recently or if it needs to)
<!-- Describe what has changed in this PR --> **What changed?** Enable reading of new field added in AddOrUpdateRemoteClusterResponse as these apparently aren't sharing/reusing a common proto for reading/writing <!-- Tell your future self why have you made these changes --> **Why?** Enabling reads from cli <!-- Are there any breaking changes on binary or code level? --> **Breaking changes** na <!-- If this breaks the Server, please provide the Server PR to merge right after this PR was merged. --> **Server PR** temporalio/temporal#8744 cli PR - temporalio/cli#881
<!-- Describe what has changed in this PR --> **What changed?** Enable reading of new field added in AddOrUpdateRemoteClusterResponse as these apparently aren't sharing/reusing a common proto for reading/writing <!-- Tell your future self why have you made these changes --> **Why?** Enabling reads from cli <!-- Are there any breaking changes on binary or code level? --> **Breaking changes** na <!-- If this breaks the Server, please provide the Server PR to merge right after this PR was merged. --> **Server PR** temporalio/temporal#8744 cli PR - temporalio/cli#881
5dc43f4 to
dbd24ee
Compare
|
Semgrep found 3
No explicit |
cretz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM since it targets next-server, but will let someone on the CLI team provide approval
## What changed? Wiring in #8658 but for operator api ## Why? Compatibility with CLI ## How did you test it? - [x] built - [x] run locally and tested manually - [ ] covered by existing tests - [ ] added new unit test(s) - [ ] added new functional test(s) in our functional test I commented out ``` // Enable replication active -> standby _, err = activeCluster.AdminClient().AddOrUpdateRemoteCluster( ctx, &adminservice.AddOrUpdateRemoteClusterRequest{ FrontendAddress: standbyCluster.Host().RemoteFrontendGRPCAddress(), FrontendHttpAddress: standbyCluster.Host().FrontendHTTPAddress(), EnableRemoteClusterConnection: true, EnableReplication: true, // NOW enable replication }) s.Require().NoError(err) // Enable replication standby -> active _, err = standbyCluster.AdminClient().AddOrUpdateRemoteCluster( ctx, &adminservice.AddOrUpdateRemoteClusterRequest{ FrontendAddress: activeCluster.Host().RemoteFrontendGRPCAddress(), FrontendHttpAddress: activeCluster.Host().FrontendHTTPAddress(), EnableRemoteClusterConnection: true, EnableReplication: true, // NOW enable replication }) s.Require().NoError(err) ``` and used a locally built cli temporalio/cli#881 to enable, test passed
## What changed? Wiring in temporalio#8658 but for operator api ## Why? Compatibility with CLI ## How did you test it? - [x] built - [x] run locally and tested manually - [ ] covered by existing tests - [ ] added new unit test(s) - [ ] added new functional test(s) in our functional test I commented out ``` // Enable replication active -> standby _, err = activeCluster.AdminClient().AddOrUpdateRemoteCluster( ctx, &adminservice.AddOrUpdateRemoteClusterRequest{ FrontendAddress: standbyCluster.Host().RemoteFrontendGRPCAddress(), FrontendHttpAddress: standbyCluster.Host().FrontendHTTPAddress(), EnableRemoteClusterConnection: true, EnableReplication: true, // NOW enable replication }) s.Require().NoError(err) // Enable replication standby -> active _, err = standbyCluster.AdminClient().AddOrUpdateRemoteCluster( ctx, &adminservice.AddOrUpdateRemoteClusterRequest{ FrontendAddress: activeCluster.Host().RemoteFrontendGRPCAddress(), FrontendHttpAddress: activeCluster.Host().FrontendHTTPAddress(), EnableRemoteClusterConnection: true, EnableReplication: true, // NOW enable replication }) s.Require().NoError(err) ``` and used a locally built cli temporalio/cli#881 to enable, test passed
What was changed
Wiring in new enableReplication flag into cluster upsert cli.
Deleting sql pinning test as we no longer need this, see historical context:
#784
temporalio/temporal#7333
then unpinning in OSS temporalio/temporal#8489
Why?
Allows for users to leverage the new field
Checklist
Closes
How was this tested:
built locally and tested in conjunction with temporalio/temporal#8744, used the cli manually to make a replication based test pass