Handle VirtualNetworkRuleBadRequest error for VNetRule
#1010
Conversation
This file contains 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
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Closes #1006
What this PR does / why we need it:
If a user creates a VNetRule on MySqlServer or PostgreSqlServer with a server on EastUS instead of WestUS, the reconciler continues to error "VirtualNetworkRuleBadRequest".'
This PR catches that error, and throws a failed provision state because it will never be provision correctly.
Special notes for your reviewer:
(same with MySql)
How does this PR make you feel:
If applicable: