Remove Azure <1.0 Old Dependency Change Note #48159
Merged
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
I understand there was a period where pyazure 1.0 was not working with salt per saltstack#27980 and seeing as this was resolved with newer versions, the note is no longer relevant.
|
Welcome @emattiza! And thank you for submitting this doc fix. :) |
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.
I understand there was a period where pyazure 1.0 was not working with salt per #27980 and seeing as this was resolved with newer versions, the note is no longer relevant.
What does this PR do?
Amends doc to remove old warning note given new azure dependency fix
What issues does this PR fix or reference?
Conflicting documentation information
Previous Behavior
Talk about a dependency problem that used to exist
New Behavior
Issue 27980 closed and azure dependency updated
Tests written?
Not required?
Commits signed with GPG?
No