Changing where staging action gets user id from for cloud data #845
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.
Changing where cloudstaging action gets user id from. Instead of using mod_shredder which does not exist in the xsede version use modw.systemaccount instead and add resource_id to join clause.
This also fixes this error.
Motivation and Context
Prevents errors with being used with XSEDE and make sure user is retrieved from the correct resource
Tests performed
Manually verified in docker and all test pass
Types of changes
Checklist: