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

True AWS Lambda Aliases #148

Open
Smotrov opened this issue Dec 7, 2018 · 4 comments
Open

True AWS Lambda Aliases #148

Smotrov opened this issue Dec 7, 2018 · 4 comments

Comments

@Smotrov
Copy link

Smotrov commented Dec 7, 2018

Dear team,
We've been digging your readme for a day but with no luck :-(
The questions are still open for us:
Is this plugin can preserve previous versions of Lambda function when deploying new version?
To have something like this
2018-12-07 18 05 49

Is this plugin can preserve existing Aliases of Lambda function during deployment? Is it possible to set Alias for deployment (I mean exactly the kind of Alias which shown bellow)
Should be something like here
2018-12-07 18 05 42

Thank you in advance for your support!

@npomoAtWork
Copy link

I am also interested in this

@johnwongapi
Copy link

Agree.
And we also need command to manage versions since there is a limit of 200 resources in cloud formattion template.

@filipeoliveira
Copy link

This would be really nice.

@ilirosmanaj
Copy link

ilirosmanaj commented Jan 17, 2020

I had the same issue and was thinking that for some reason this plugin is not working correctly.

The fix to my problem was that I had the versionFunctions property set to false in my serverless yml configuration. As soon as you set it to true, deploying with an alias will work as expected and you will get what you attached in the screenshots

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

No branches or pull requests

5 participants