PR to address incorrect package versions in DataProtection Configuration document (Issue #19770) #19771
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
|
@Rick-Anderson ... This isn't the only spot for the updates. I don't see any sample apps that need work, but there are perhaps four more topics that need updates. |
|
@pakrym please review or recommend a reviewer |
pakrym
reviewed
Sep 3, 2020
|
I've updated the PR at @pakrym 's request to have the original setup arguments, I changed mine when migrating to the new libraries, but apparently the original ones in the documentation still work. |
pakrym
approved these changes
Sep 4, 2020
guardrex
approved these changes
Sep 4, 2020
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.
Fixes #19770
Update to fix package references and minor configuration changes when moving to the new libraries.
Left the workaround in place for the issue with the old library incase people are googling the error and come across the document (included a comment suggesting them to upgrade)