-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix s3csi path & readme #486
Conversation
Thanks for the PR. We are investigating as the |
Hi ksuderman This error occurs if there are subpath, and I use no subpath only see the byhand managed two folder I found older versions don't have subpath. If the path of s3 has not changed from the old version to the current version, there should be no need to add a new subpath. |
@bravo325806 Can you clarify what you meant by "I found older versions don't have subpath"? Are you trying to upgrade or is this a fresh install? The subPath is not cvmfs specific and is needed for the bucket too: http://biorefdata.s3-website-ap-southeast-2.amazonaws.com/#galaxy/v1/ |
@nuwang Sorry I didn't make this part clear. I used v5.1.0 Because values.yaml Maybe we can only change values.yaml? |
@bravo325806 I made a PR to your PR as jobs that are run also mount the refdata PV and should not include the Also, that table of values in the README.md is generated by a script from comments in the As soon as you merge those changes we can go ahead and merge your PR. |
Fix s3csi path
@ksuderman I have merged your PR, Thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks both for persevering with these fixes + testing. The changes lgtm!
I found no subpath when using s3csi. The readme refdata.type is for using s3csi not s3fs