This repository was archived by the owner on Dec 9, 2024. It is now read-only.
remove shell-escaping url in S3ZipContent #200
Merged
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.
Hello,
when I deploy a Kubeless function with strategy: S3ZipContent, the deploy fails.
The pod goes in Init:CrashLoopBackOff status because the Kubeless prepare initContainer cannot retrieve the artifact from the bucket using the S3 presigned url.
Logs of the prepare initContainer:
The issue seems related to the CURL command in the preapre container that has the url argument with two quotes before and after the url.
Example:
Seems that shellescape in lib/strategy/s3_zip_content.js is the cause of this issue and I think it should be no more necessary because of this commit to the kubeless project.
I hope this PR could be merged to fix issues with S3ZipContent deploys.
Let me know if you have any questions, comments or suggestions.
Thank you very much for your work,
Lorenzo Angelini