Describe the bug
Under certain conditions (typically new users deploying their first application), tapis apps deploy fails with a 404 unless --no-upload is specified.
To Reproduce
Steps to reproduce the behavior:
Create a new DesignSafe Account (or temporarily rename the apps directory)
Run tapis auth init --interactive and choose designsafe
Expected behavior
A message similar to the one below
[Errno 404] Not Found for https://agave.designsafe-ci.org/files/v2/media/system/designsafe.storage.default//bpachev/apps/assets-2021-06-07: 'No such file or directory'
After some time digging around the source code, I discovered the issue was because I didn't have an apps directory on my DesignSafe account - and the code did not handle the case when multiple directories on deployPath don't exist. I created a simple, minimal PR that resolved the issue I ran into - https://github.com/TACC-Cloud/tapis-cli/pull/359.
Describe the bug Under certain conditions (typically new users deploying their first application),
tapis apps deploy
fails with a 404 unless --no-upload is specified.To Reproduce Steps to reproduce the behavior:
tapis auth init --interactive
and choose designsafecd tapisv2_apps/test_app
tapis apps deploy
Expected behavior A message similar to the one below
[Errno 404] Not Found for https://agave.designsafe-ci.org/files/v2/media/system/designsafe.storage.default//bpachev/apps/assets-2021-06-07: 'No such file or directory'
After some time digging around the source code, I discovered the issue was because I didn't have an
apps
directory on my DesignSafe account - and the code did not handle the case when multiple directories ondeployPath
don't exist. I created a simple, minimal PR that resolved the issue I ran into - https://github.com/TACC-Cloud/tapis-cli/pull/359.