[WIP][?.?] support "remoteonly" value for the Access protocol parameter #8291
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.
Some sites have distinct local and remote storage infrastructure (e.g. use different endpoints for uploads from WNs and transfers from external sites). DIRAC already support local endpoint via "Access" parameter (can be set to local). However, currently in case of a failure SE operation will fall back to remote protocols, which can be undesirable (e.g. if it can create race conditions between uploads via local and remote endpoints). To address the problem, we introduce "remoteonly" value for the Access parameter, which acts similarly to "remote" but prevents fallbacks to the protocol in local context.
BEGINRELEASENOTES
NEW: support "remoteonly" value for the Access protocol parameter
ENDRELEASENOTES