Skip to content
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

Improvement: Package dependencies for lambda #46

Closed
strcrzy opened this issue Mar 1, 2017 · 1 comment
Closed

Improvement: Package dependencies for lambda #46

strcrzy opened this issue Mar 1, 2017 · 1 comment

Comments

@strcrzy
Copy link
Collaborator

strcrzy commented Mar 1, 2017

We already have code to package and deploy third party libraries, but it might be cool to have SA package its own dependencies (from requirements.txt) into the deployment archive as well. #40 introduced a new lambda dependency, and other revisions likely will too.

We could track these in third_party_libs in variables.json but IMO those should just be the dependencies of the rules themselves rather than their underlying infrastructure.

@jacknagz jacknagz modified the milestone: 1.3.0 Mar 9, 2017
@ghost ghost added the improvement label Apr 3, 2017
@jacknagz jacknagz removed this from the 1.3.0 milestone Jun 6, 2017
@ryandeivert
Copy link
Contributor

this is actually complete and we have these in the packaging logic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants