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

Question: Rolling this into a Lambda #20

Open
armenr opened this issue Sep 13, 2019 · 7 comments
Open

Question: Rolling this into a Lambda #20

armenr opened this issue Sep 13, 2019 · 7 comments

Comments

@armenr
Copy link

armenr commented Sep 13, 2019

Thank you for all of your fantastic work! This is one of my absolute favorite things about ASGs in AWS. I didn't want to opt out of Terraform/Pulumi and into CloudFormation or Ruby Sparkleformation just for the sake of benefitting from the autorolling feature.

The other alternative was to create a cloudformation template just for the ASG, rendered through Pulumi, then go down that terrible rabbithole.

You've made something that others - like me - needed. Thank you! :)

If I fork this away and work on turning into a Lambda a-la Lambda Layers, would you want me to open a PR back to you, or you'd prefer not to consider an implementation like that?

@deitch
Copy link
Owner

deitch commented Sep 13, 2019

I’d love it, thank you. Multiple methods of deployment. The particular seed use case was a client on kubernetes. More than happy to have it as a lambda option.

@armenr
Copy link
Author

armenr commented Sep 13, 2019

I understand that in its current form, it's sitting as a running service, steadily listening. I was thinking of the convenience factor and the value case for having it run ad-hoc, on some ASG notification via SNS.

With what you've got in the repo already, it appears mostly trivial to extend it as such (possibly a famous last words statement), but I figured I'd check with you - the author, to make sure my estimation is accurate.

Thanks again! :)

@deitch
Copy link
Owner

deitch commented Sep 13, 2019

Five most dangerous words and engineer can say, “how hard could it be?” :-)

@armenr
Copy link
Author

armenr commented Sep 13, 2019

Roger that. If I've learned anything in my 11 years, it's to always do the hardest stuff first, and never commit work or time on estimations of "ease" :)

Any way to communicate short-cycle, in case of questions?

@deitch
Copy link
Owner

deitch commented Sep 13, 2019

LOL!

Any way to communicate short-cycle, in case of questions?

My travel schedule doesn't always allow short-cycle; being on a plane often precludes it. You can try on Slack, though. I am on the Kubernetes slack, Docker slack, Gophers slack, LFEdge slack, and even the databacker slack.

@legal90
Copy link

legal90 commented May 6, 2020

Hi @armenr,
Your idea of having having it run ad-hoc on Lambda sounds good 👍
Did you manage to get it working so far? Do you have anything what you can share? Thank you!

@deitch
Copy link
Owner

deitch commented May 10, 2020

Did you get anywhere?

One of the nice things about the growth of go over the last few years was the ease with which this was made into a single binary, easily built for multiple platforms. So running this on Lambda should be straightforward.

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

3 participants