Recursively copies artifact dir when it's in source dir until it errors out:
JSON-RPC input:
{
...
"source_dir": "path/to/source",
"artifacts_dir": "path/to/source/.build/artifact",
...
}
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 the source_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)
- OS: Mac
- If using SAM CLI,
sam --version:
- AWS region: us-east-1 (shouldn't matter)
Add --debug flag to any SAM CLI commands you are running
Recursively copies artifact dir when it's in source dir until it errors out:
JSON-RPC input:
{ ... "source_dir": "path/to/source", "artifacts_dir": "path/to/source/.build/artifact", ... }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_diroutside thesource_dirsolves 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