-
Notifications
You must be signed in to change notification settings - Fork 1k
Extending support for rds_topology metadata handling #4992
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
Open
nielsvogell
wants to merge
5
commits into
sysown:v3.0
Choose a base branch
from
nielsvogell:v3.0_aws
base: v3.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
0c5eabf
Refactoring rds_topology discovery to support Multi-AZ and Blue/Green…
a31838d
Removing unsafe assert and moving error logging to correct if-else block
80e100a
Aligning datatypes for server creation and adding SSL flag for server…
cee3185
Modified process_discovered_topology to use an in-memory list of disc…
8a94185
Merge branch 'sysown:v3.0' into v3.0_aws
nielsvogell File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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.
The logic for
added_new_serverhas changed. Previously, it would reflect the status of the last server addition attempt. Now, it reflects the status of the first attempt if it was successful (0), or the error code of the first failure if all prior attempts also failed.For example:
create_new_server_in_hgreturns 0 for success, -1 for failure:S, S, F->added_new_server = -1S, S, F->added_new_server = 0(from the first S)F, S, S->added_new_server = 0F, S, S->added_new_server = -1(from the first F)Confirm if this change in how
added_new_serveris determined aligns with the intended behavior. If the goal is to know if any server was successfully added, a boolean flag might be clearer.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.
I might be missing something, but wouldn't
F, S, Sresult inadded_new_server = 0?First server:
res = -1,added_new_server = -1->added_new_server = -1Second server:
res = 0,added_new_server = -1->added_new_server = 0Third server:
res = 0,added_new_server = 0-> no change becauseadded_new_server >= 0The desired behavior is to update the internal structures if at least one new server was added. The previous implementation didn't do that.
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.
You reasoning is correct, and I agree the new behavior is better than the one on the previous impl.