Bug/WP-306: If input file target path is empty, do not send it to tapis #871
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
A recent change #857 introduced target path for input file. But, this was done only if the app definition requested for it.
When the app definition does not want this feature, the current implementation is overriding target path to "*" always. This is a regression. The production behavior is to not send targetPath back to tapis.
Related
Changes
The behavior in prod is to not send targetPath. This code change will match that to not send target path if it is empty (undefined, null or empty in UI). This will meet all conditions.
Testing
1.Tested OpenSees which was failing before to copy files to right location
Job parameters show no targetPath( this matches prod):
Tested extract which has target path exposed.
The job worked
Tested with namd
It matches the production behavior (compared with frontera). Output location: frontera/home1/09478/cyemparala/tapis-jobs-archive/2023-10-03Z/namd-2.14_2023-10-03T23:44:19-c9521e71-1cbc-420b-9dbb-a249d52a15c5-007
UI
No Change
Notes
Created bug WP-307 to support the default targetPath setup in app definition. We have never used it, and it needs to be tested and any changes should not break apps.