[tests-only] [full-ci] getPersonalSpaceIdForUser from webdav propfind #39751
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.
Description
See the comments and code for details. When on oCIS,
/graph/v1.0/me/drives
endpoint exists and returns a list of spaces, and the code parses that list like it previously did and finds the personal space id for the user.If that nice endpoint does not exist, then the code does a PROPFIND on the webdav root of the user. On reva (at least) the response contains
oc:id
which id a base64-encoded value that happens to include the personal space id. See the code for how the personal space id is reconstructed.This allows us to test using the personal space id to access the files of a user. That allows us to verify what webdav space scenarios pass, or fail, in reva. That will be helpful when fixing stuff - a developer can try to make the tests pass.
Fixed issue #39617
How Has This Been Tested?
CI passes here in core
oCIS CI passes in owncloud/ocis#3077 - there is no change there because the test code running there will not use the new webdav propfind way to find the personal space id.
cs3org/rev
CI passes in cs3org/reva#2505 - that starts runningpersonalSpace
API tests in reva. It makes use of the new test code in this PR, and it adds the failingpersonalSpaces
tests to expected-failures.After merge this PR, I will switch those oCIS and reva PRs to use the new master commit id, and then we can also merge them.
Types of changes
Checklist: