We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I zip my project up to deploy as a lambda function via the serverless framework.
After bumping the version of this orb the deploy would fail with AWS saying the payload was too large.
I ran the build with SSH enabled and noticed an 'aws' directory would appear in my project folder after running aws-cli/setup.
If I exclude this directory from the serverless packaging, the build succeeds again.
Is this an install artefact left behind? Should the install not clean up after itself without leaving artefacts in my project directory?
The text was updated successfully, but these errors were encountered:
Same problem, in our case it breaks ESLint checks.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
I zip my project up to deploy as a lambda function via the serverless framework.
After bumping the version of this orb the deploy would fail with AWS saying the payload was too large.
I ran the build with SSH enabled and noticed an 'aws' directory would appear in my project folder after running aws-cli/setup.
If I exclude this directory from the serverless packaging, the build succeeds again.
Is this an install artefact left behind? Should the install not clean up after itself without leaving artefacts in my project directory?
The text was updated successfully, but these errors were encountered: