Deprecated legacy key migration#87
Open
svanegasm wants to merge 3 commits into
Open
Conversation
|
Can confirm that this PR solves my issue! Forked this gem and applied these changes and all is golden. |
Owner
|
Hey guys.. I know this is late, but I think you can do the same thing with XML-RPC by doing the following: The key change is adding |
Owner
|
Updated Readme |
This file contains hidden or 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
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.
These changes seek to maintain the usability of the gem according to the Legacy Api Key deprecation plan.
Ref:
Legacy Key Deprecation
Schedule for Legacy Key Deprecation
Legacy Key Migration
Personal Access Tokens & Service Account Keys