-
Notifications
You must be signed in to change notification settings - Fork 41
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
Separate build step for version + alias #31
Comments
Hi, We are in need of a similar feature, having a separate publish version step in our pipeline. Something like "AWS Lambda Publish Version" with version and alias as input enabling the publishing of a new version and updating an alias to point to it. |
I have now started to look at the possibility to add this to the code. A totalt workflow will be like: build jar -> upload to lambda as $LATEST version -> test with payload -> publish $LATEST as new version -> point the alias currently used in production (for example ACTIVE) to the new version. |
Hi, I have now completed the code extension and are putting the finishing touches on it. |
Thanks msulland, I reviewed the pull request and merged it to this fork. |
Included in release 0.5.4, arriving during the course of tomorrow in update panel. |
Great work guys! Thanks for doing this! |
I was thinking that it would be nice to have a separate step for creating a version and alias. I think it offers more flexibility.
It would make conditionally applying versions and aliases a lot more easier.
How could this be integraded UI-wise? Leave it open to you but this is my suggestion.
Publish version
and on forAssign Alias
. Both can be checked or unchecked independently. IfAssign Alias
is checked, an input box popups up for creating the alias(es).If
Publish version
andAssign Alias
are both checked, a new version is created which will be aliased by all the aliases provided in the input box (comma separated).If only
Assign Alias
is checked, the aliases will be applied to the $LATEST version.Feedback is more then welcome :).
The text was updated successfully, but these errors were encountered: