Use service account to download file #72
Merged
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
This is a workaround for bug documented in * https://jira.tacc.utexas.edu/browse/CS-169 * https://jira.tacc.utexas.edu/browse/DES-2084 Sometimes a 403 is returned by tapis sometimes using the prod tenant instead of the designsafe tenant. The workaround is to use the service account on the designsafe tenant (which "fixes" the problem for future downloads).
nathanfranklin
deleted the
task/DES-2084-provide-workaround-for-failing-file-gets
branch
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.
Overview:
This is a workaround for bug documented in
Sometimes a 403 is returned by tapis sometimes using the prod tenant
instead of the designsafe tenant. The workaround is to use the service
account on the designsafe tenant (which somehow "fixes" the problem in case someone tries to access the file again later)
PR Status:
Related Jira tickets:
Testing Steps:
Notes:
I was thinking originally as doing a file listing by the user to check if they have access. I didn't do that. Instead, I just check if the system was
public. So far, we've only seen this on published projects so hopefully it just occurs there. If occurs in private systems, we'll see that in the logs now and improve our work-around.