Support for Lambda built-in versions and aliases

[haack]

Hello,

I was wondering if there we're plans to support or migrate to Lambda's official versioning (documented here: http://docs.aws.amazon.com/lambda/latest/dg/versioning-aliases.html).

I'd be happy to implement this and pull-request if it would be useful.

[haack]

Because node-lambda uses the previous version of the AWS API (2014-11-11), which doesn't have support for built-in versions and aliases, I have written a separate package to handle versioning. Will publish once I have permission.

[motdotla]

Yes, plans would be to migrate to it.

I haven't given this repo any ❤️ for a long time.

I'm taking a look at things this weekend, but yes, @haack go ahead.

[jkervine]

Hi, I would really need this feature and would like to contribute. Is there a branch / fork where someone is already working on this or should I start from current master?

[DeviaVir]

Migrated to AWS API 2015-03-31 in this PR: #64
Which clears the way for actual versioning (not implemented in the scope of that PR).

[DeviaVir]

@jkervine (and others) now the AWS API is updated, feel free to pick up versioning for this project.

[teebu]

any news on this? i'd like to see some sort of version/aliasing

[ajagnanan]

Hey guys, do you have an update on when this will be implemented?

[DeviaVir]

@ajagnanan this is an open ticket with (far as I know) nobody working on it at the moment.

[duhseekoh]

I'm curious how others are getting around this? Do you essentially just always have a $LATEST version and no aliases?

How do you know what version is actually out there?

[DeviaVir]

You can use AWS_FUNCTION_VERSION environment variable which appends the version to the function name but does not actually use the versions functionality yet.