Replace /pcs with /xpan API endpoints URL. #2
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
moorchegue
force-pushed
the
hotfix/pcs_to_xpan
branch
from
a36e4cc to
5ea3c29
Compare
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.
It seems that at least some of the
/rest/2.0/pcs/started returning 403 errors, which breakslsanddownloadcommands. Interestingly enoughinfostill works.There're
/rest/2.0/xpanendpoints described here: https://pan.baidu.com/union/doc/Zksg0sb73 which seems to be very similar. So this PR is about partially switching to using it.I'm unclear as to what exactly is the history here and what's the best way forward, but at least this seems to fix most important commands. Do let me know if there's a better way to deal with it.