#awswishlist Lambda supporting independent, versioned artifacts that could be included by a Lambda
-
Show this thread
-
Lambda doing automatic pip/npm install would be great, but can't hit my internal PyPI, and would require any common artifacts to get pushed to some repo even for quick dev pushes. I'd rather have the ability common code that belongs with Lambdas to live in the svc
3 replies 0 retweets 1 likeShow this thread -
Probably need something better than sequential version (+aliases). Semantic version probably too much? Monotonic version good imo http://blog.appliedcompscilab.com/monotonic_versioning_manifesto/ … release updates would re-deploy Lambdas that include the artifact
1 reply 0 retweets 1 likeShow this thread -
I *guess* aliases could accomplish this and keep Lambda's versioning style. But there'd be impedance mismatch, I think
1 reply 0 retweets 0 likesShow this thread -
These artifacts would get CloudFormation resources, supporting a CodeUri path that `aws cloudformation package` would handle for you. Then you could !Ref them in the Lambda or SAM function resource
1 reply 0 retweets 2 likesShow this thread -
Three primary use cases for this: * Common code/artifacts within a service shared by its Lambdas * A service could publish an SDK for use by external Lambdas * Common code/artifacts within an organization
3 replies 0 retweets 1 likeShow this thread
I like this solution! Right now I've been using webpack to achieve similar things and redeploying functions every time.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.