-
Notifications
You must be signed in to change notification settings - Fork 140
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
Bug: recursively copies artifact dir when it's in source dir #382
Comments
@israelg99 On the In the mean time, my suggestion is to use separate directories for each as this was how Lambda Builders (and SAM CLI) was designed. |
Err... how exactly it should be done?
What's the proposed solution for building this one?
will fail miserably because of that strange behavior. The solution that I would do will have something like:
Where:
|
Ah, this one is so cute!
So, aws-sam does suffer from the same bug, but you've just hardcoded the escape hatch...Nice! |
@pkit Agreed. I think exposing this escape hatch with some |
We have a few issues asking for a similar thing in |
Recursively copies artifact dir when it's in source dir until it errors out:
JSON-RPC input:
Then running
lambda-builders <JSON INPUT>
Results in
PythonPipBuilder:CopySource - [Errno 63] File name too long: '/path/to/source/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/.build/artifact/python_dateutil-2.8.2.dist-info/top_level.txt'
Setting
artifact_dir
outside thesource_dir
solves this issue.Is this a bug, or is this expected? Perhaps we should add
ignore: {}
interface? I can contribute a PR for this if you guys can point me in the right direction.Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
:Add --debug flag to any SAM CLI commands you are running
The text was updated successfully, but these errors were encountered: