[CLOUDGA-28234] Add backup replication target support in edit cluster#312
Merged
pranbansal02 merged 2 commits intomainfrom Aug 29, 2025
Merged
[CLOUDGA-28234] Add backup replication target support in edit cluster#312pranbansal02 merged 2 commits intomainfrom
pranbansal02 merged 2 commits intomainfrom
Conversation
Siddarth-Baldwa
approved these changes
Aug 25, 2025
Contributor
Siddarth-Baldwa
left a comment
Siddarth-Baldwa
left a comment
There was a problem hiding this comment.
Minor nit. Rest Lgtm
pranbansal02
force-pushed
the
CLOUDGA-28234
branch
from
9a37f44 to
515f1a0
Compare
arishta-yb
approved these changes
Aug 25, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
[CLOUDGA-28234] Add backup replication target support in edit cluster
Testing
Help (Without feature flag enabled):
$ ./ybm cluster update --help Update a cluster Usage: ybm cluster update [flags] Flags: --cloud-provider string [OPTIONAL] The cloud provider where database needs to be deployed. AWS, AZURE or GCP. --cluster-name string [REQUIRED] Name of the cluster. --cluster-tier string [OPTIONAL] The tier of the cluster. Sandbox or Dedicated. --cluster-type string [OPTIONAL] Cluster replication type. SYNCHRONOUS or GEO_PARTITIONED. --database-version string [OPTIONAL] The database version of the cluster. Production, Innovation, Preview, or 'Early Access'. --fault-tolerance string [OPTIONAL] Fault tolerance of the cluster. The possible values are NONE, NODE, ZONE, or REGION. Default NONE. -h, --help help for update --new-name string [OPTIONAL] The new name to be given to the cluster. --region-info stringArray Region information for the cluster, provided as key-value pairs. Arguments are region=<region-name>,num-nodes=<number-of-nodes>,vpc=<vpc-name>,num-cores=<num-cores>,disk-size-gb=<disk-size-gb>,disk-iops=<disk-iops> (AWS only)Help (With feature flag enabled):
$ ./ybm cluster update --help Update a cluster Usage: ybm cluster update [flags] Flags: --cloud-provider string [OPTIONAL] The cloud provider where database needs to be deployed. AWS, AZURE or GCP. --cluster-name string [REQUIRED] Name of the cluster. --cluster-tier string [OPTIONAL] The tier of the cluster. Sandbox or Dedicated. --cluster-type string [OPTIONAL] Cluster replication type. SYNCHRONOUS or GEO_PARTITIONED. --database-version string [OPTIONAL] The database version of the cluster. Production, Innovation, Preview, or 'Early Access'. --fault-tolerance string [OPTIONAL] Fault tolerance of the cluster. The possible values are NONE, NODE, ZONE, or REGION. Default NONE. -h, --help help for update --new-name string [OPTIONAL] The new name to be given to the cluster. --region-info stringArray Region information for the cluster, provided as key-value pairs. Arguments are region=<region-name>,num-nodes=<number-of-nodes>,vpc=<vpc-name>,num-cores=<num-cores>,disk-size-gb=<disk-size-gb>,disk-iops=<disk-iops> (AWS only),backup-replication-gcp-target=<gcp-target>. region, num-nodes, num-cores, disk-size-gb are required. Specify one --region-info flag for each region in the cluster.Documentation