fix: change clusterId in Cmek test #716
Merged
Conversation
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
google-cla bot added the cla: yes 
product-auto-label bot added the api: bigtable 
Change-Id: Idc8ad885205190374b089349ee94cc627bafd782
Change-Id: I8d0ce18de5fa8e914344340850786930fbd670f1
ad548 changed the title 
Codecov Report
@@ Coverage Diff @@ ## master #716 +/- ## ========================================= Coverage 83.64% 83.64% Complexity 1220 1220 ========================================= Files 112 112 Lines 7417 7417 Branches 394 394 ========================================= Hits 6204 6204 Misses 1010 1010 Partials 203 203 Continue to review full report at Codecov.
|
kolea2 approved these changes Apr 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 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.
Change-Id: Idc8ad885205190374b089349ee94cc627bafd782
Getting an error internally about cluster with clusterId2 already existing. So changing to use new clusterId for the other zone scenario.