Only essential differences between azure-py-vdc and azureng-py-vdc #810
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
mikhailshilkov
approved these changes
Nov 5, 2020
dixler
pushed a commit
that referenced
this pull request
Jan 21, 2022
) * Backport location, separator and suffix * Add suffix to logical names * Update README * Update README * Reconcile READMEs * Only append suffix where needed * Update READMEs * Typed apply works for both * Update comment for apply * Improve configuration and error handling * Restore previous peering
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Make comparison between current and azure-nextgen provider clearer by eliminating extraneous differences.
Backport improvements and fix whitespace and comment issues.