Bump keystone deprecation to sodium #55612
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
ghost
requested a review
from 
dwoz
approved these changes
Dec 16, 2019
xeacott
approved these changes
Dec 16, 2019
Akm0d
approved these changes
Dec 16, 2019
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.
What does this PR do?
bumps the deprecation warning for the keystone module to sodium. The reasoning for this is explained in this issue: #55611 essentially it was not entirely deprecated properly and a lot more work will need to be put in to properly deprecate this module.
What issues does this PR fix or reference?
#49419
Previous Behavior
keystone module was set to deprecate in neon
New Behavior
keystone module set to depreacte in sodium once #55611 is taken care of.
Tests written?
No - just changing version of release to deprecate keystone module in
Commits signed with GPG?
Yes