-
Notifications
You must be signed in to change notification settings - Fork 21
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
Do not validate Azure or GCP storage paths #29
Conversation
Similar to AWS, Azure and GCP do not handle empty files and directories very well (because they aren't real!). This PR ignores them in the same manner as AWS S3 blob storage.
ec7dd94
to
e43d01f
Compare
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.
Thank you! seems like a good temporary solution
Can you update the changelog in the meantime? |
Done now, want me to merge? |
Yeah you can go ahead! I'll release the fix tomorrow :) |
Anywhere good to write tests before I merge? |
You can add tests here: https://github.com/nextflow-io/nf-schema/blob/master/plugins/nf-schema/src/test/nextflow/validation/ValidateParametersTest.groovy (just some simple test with those paths suffices for now, I will expand this later when implementing the full support) |
See 4262965 for tests. Good to go now once tests have passed. |
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.
Thank you!
Similar to AWS, Azure and GCP do not handle empty files and directories very well (because they aren't real!). This PR ignores them in the same manner as AWS S3 blob storage.
Should fix #16