-
Notifications
You must be signed in to change notification settings - Fork 131
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
dcache-frontend: support VO- or user-root relative paths in requests
Motivation: See #7072 dcache-frontend: add extraction of effective root for user to include in REST API for bulk/stage. Modification: The frontend resources had to be modified to use the user root derived from the login attributes in order to determine the `target-prefix` which would allow for resolution of the relative paths. In the case of a user-provided prefix (`/api/v1/bulk-requests`) this is done by trying to union the root and prefix paths; for the `TAPE` resources, we simply set the prefix to the root under the covers. On the bulk end, a little be of re-engineering was necessary to make sure the users can retrieve paths according to their root expectations. Thus, if the submitted paths are originally relative, they will get back all relative paths, including those discovered through recursion. If they submitted absolute paths, they should see those instead. The consistency is arrived at by allowing the initial paths to go into the database as given, but derived/discovered paths are stored as absolute and then given back through the REST API according to the prefix that has been set. Result: The RESTful interface supports paths relative to the user root as well as absolute paths for requests to the bulk service. Note: a separate solution will be necessary for the one-off `namespace` resource operations. Target: master Request: 9.0 Request: 8.2 Patch: https://rb.dcache.org/r/13937 Requires-notes: yes Closes: #7072 Acked-by: Tigran
- Loading branch information
Showing
9 changed files
with
286 additions
and
16 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.