Skip to content

Speed up requirements installation by skipping noDeploy #146

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

Merged
merged 1 commit into from
Mar 5, 2018

Conversation

kichik
Copy link
Contributor

@kichik kichik commented Feb 28, 2018

Instead of filtering later, just don't install them

Instead of filtering later, just don't install them
kichik added a commit to kichik/serverless-python-requirements that referenced this pull request Feb 28, 2018
serverless#146 already takes care of this, but we need proper noDeploy here again in case a white-listed package is dependent on a black-listed package
@dschep
Copy link
Contributor

dschep commented Feb 28, 2018

Hah. That's how this was initially implemented. Not sure why it was changed. I'll have to go back and review that to see if I had a good reason and if that's still applicable.

@kichik
Copy link
Contributor Author

kichik commented Feb 28, 2018

I haven't seen the change, but I would assume it happened because requirements.txt might contain a package that depends on boto3 which will then be installed and deployed regardless of noDeploy. I haven't removed the code that handles that issue. I think it's best to exclude it on both sides.

@dschep
Copy link
Contributor

dschep commented Feb 28, 2018

Yeah, that makes sense.

@dschep dschep merged commit 75b4d70 into serverless:master Mar 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants