Skip to content

Add changelog, and bump version#53

Merged
motdotla merged 4 commits intomasterfrom
sm-adjustments
Apr 18, 2016
Merged

Add changelog, and bump version#53
motdotla merged 4 commits intomasterfrom
sm-adjustments

Conversation

@motdotla
Copy link
Owner

@motdotla motdotla commented Jan 20, 2016

No description provided.

@DeviaVir
Copy link
Collaborator

DeviaVir commented Apr 8, 2016 •
edited
Loading

Let's get this bumped up and deployed when the below list of PR's is merged?

I think that would make a great 0.8.0 release.

This was referenced Apr 13, 2016
Closed
Closed
@DeviaVir
Copy link
Collaborator

DeviaVir commented Apr 18, 2016

@motdotla I'm running a few tests on current master and will then contact you to get 0.8.0 pushed out. We may also want to discuss the mentioned solution to semantic releases in brought up in #39 (comment)

@DeviaVir
Copy link
Collaborator

DeviaVir commented Apr 18, 2016

✅ Tests:

~ node-lambda/bin/node-lambda deploy -e staging -r us-west-2 -n test --handler index.handler -o arn:aws:iam::xxxxxxxxxxxx:role/lambda_basic_vpc_execution -d RemoveMe -u nodejs4.3 -p -b subnet-xxxxxxxx,subnet-xxxxxxxx -g sg-xxxxxxxx
Warning!!! You are building on a platform that is not 64-bit Linux (darwin.x64). If any of your Node dependencies include C-extensions, they may not work as expected in the Lambda environment.


=> Moving files to temporary directory
=> Running npm install --production
=> Zipping deployment package
=> Reading zip file to memory
=> Uploading zip file to AWS Lambda us-west-2 with parameters:
{ FunctionName: 'test-staging',
  Code: { ZipFile: <Buffer 50 4b 03 04 14 00 00 00 08 00 b6 65 92 48 6a 00 88 6d b2 00 00 00 04 18 00 00 09 00 1c 00 2e 44 53 5f 53 74 6f 72 65 55 54 09 00 03 d7 ba 14 57 d7 ba ... > },
  Handler: 'index.handler',
  Role: 'arn:aws:iam::xxxxxxxxxxxx:role/lambda_basic_vpc_execution',
  Runtime: 'nodejs4.3',
  Description: 'RemoveMe',
  MemorySize: '128',
  Timeout: '3',
  Publish: true,
  VpcConfig:
   { SubnetIds: [ 'subnet-xxxxxxxx', 'subnet-xxxxxxxx' ],
     SecurityGroupIds: [ 'sg-xxxxxxxx' ] } }
=> Zip file(s) done uploading. Results follow:
[ { FunctionName: 'test-staging',
    FunctionArn: 'arn:aws:lambda:us-west-2:xxxxxxxxxxxx:function:test-staging',
    Runtime: 'nodejs4.3',
    Role: 'arn:aws:iam::xxxxxxxxxxx:role/lambda_basic_vpc_execution',
    Handler: 'index.handler',
    CodeSize: 45021,
    Description: 'RemoveMe',
    Timeout: 3,
    MemorySize: 128,
    LastModified: '2016-04-18T10:45:45.422+0000',
    CodeSha256: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
    Version: '1',
    VpcConfig:
     { SubnetIds: [Object],
       SecurityGroupIds: [Object],
       VpcId: 'vpc-xxxxxxxx' } } ]

DeviaVir and others added 2 commits April 18, 2016 13:02
@DeviaVir
Updated changelog (#83)
c49e0a3 
* Added package command to create a local zip.

Exclude *.env files from being uploaded to amazon.
Exclude .git* to exclude .gitignore.
Exclude test from zip.
Exclude packageDirectory from zip if specified.

* added test for refactored _archive method.

* Add -e to not escape \n when echo'ing

* VpcConfig support:
- http://docs.aws.amazon.com/lambda/latest/dg/API_VpcConfig.html
- http://docs.aws.amazon.com/lambda/latest/dg/vpc.html
This allows users to place their Lambda functions in specific subnets with specific security groups.

* Use AWS API 2015-03-31:
- Check if the function exists, if it does update else create new
- This API provides compatibility with VpcConfig

* Only ignore deploy.env by default

* Updated readme: MODE is no longer a thing

* Throw on failures

* - Fix rsync namespaced error
- Add editorconfig
- Ignore editorconfig

* Update to pass callback for nodejs4.3 runtime (#74)

* Update to pass callback for nodejs4.3 runtime
* Default to recommended runtime
* Add note about runtimes
* Added note on how to target v0.10.36

* Runhandler: Hotfixes

* Runhandler: Hotfixes (#75)

* Post install script second atttempt

* Post install script

* Add '-x' / '--excludeGlobs' args for general file exclusion on deploy. (2) (#80)

This lets me e.g. exclude not only `.env` but by `.env.prod` / `.env.dev`
and any other junky / sample files that happen to live in the method's
directory.  Or for that matter to move all those files into a sub-
directory and exclude that.  Less policy, more flexibility.

* Excludes: Ignore *.swp (#81)

* Ignore .swp files by default. Remove redundant deploy.env ignore from the examples.

* Add option to create a sample file with a custom filename and fix the run command when running with a custom event file (#51)

* Feature/context file (#82)

* Add context.json example
* Add contextFile -x --contextFile parameter
* fix contextFile example filename
* update setup log message
* Runhandler: Hotfixes
* Reformat to match existing whitespace
*  more reformating to match existing whitespace
* revert version back to 0.7.1
* Fix indenting

* Update changelog
Merge master
d250a05
@motdotla
Copy link
Owner Author

motdotla commented Apr 18, 2016

Huge thanks to @DeviaVir for tackling all these issues and putting things together! And thanks to all who submitted PR requests.

@motdotla
Copy link
Owner Author

motdotla commented Apr 18, 2016

semantic-release looks cool but I think overkill right now. We'll tag and release like normal.

@motdotla motdotla merged commit 2286328 into master Apr 18, 2016
@motdotla motdotla deleted the sm-adjustments branch April 18, 2016 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@motdotla @DeviaVir