-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Fix New-AzSqlDatabaseSecondary existing database name check #10908
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
Conversation
| try | ||
| { | ||
| ModelAdapter.GetDatabase(this.PartnerResourceGroupName, this.PartnerServerName, this.DatabaseName); | ||
| ModelAdapter.GetDatabase(this.PartnerResourceGroupName, this.PartnerServerName, string.IsNullOrEmpty(this.PartnerDatabaseName) ? this.DatabaseName : this.PartnerDatabaseName); |
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.
Consider extracting method to get effective partner database name.
isra-fel
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.
Hi @bradrich-msft the change looks good to me. Please add an entry to ChangeLog.md (as the PR template said) then I can get it merged. Thanks
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
closing in favor of #10983 |
Description
Bug fix. New-AzSqlDatabaseSecondary was checking existence of source database instead of target database.
Checklist
CONTRIBUTING.mdChangeLog.mdfile(s) has been updated:ChangeLog.mdfile can be found atsrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md## Upcoming Releaseheader -- no new version header should be added