Feature Request: beanstalk supplement
Closed this issue · 5 comments
We've been using beanstalker for awhile now, and it's helped us integrate with our maven build environment pretty well. I had some problems with RC6, but it looks like you're taking care of that which I appreciate.
One feature I've been thinking about which would be a substantial improvement would be actually adding using the AWS autoscaling API to supplement things which are missing or slow to be added to the official beanstalk API. For instance the feature in this forum post for HealthCheck termination
https://forums.aws.amazon.com/thread.jspa?messageID=298037񈰵
http://docs.amazonwebservices.com/AutoScaling/latest/APIReference/API_UpdateAutoScalingGroup.html
Another key thing missing from beanstalk is Autoscaling Policies instead of triggers
http://docs.amazonwebservices.com/AutoScaling/latest/APIReference/API_PutScalingPolicy.html
The advantage of doing these inside beanstalker is that it would be able to know the name of the scaling group at deployment time in order to make the API calls, and it would be fully automated into the scripted build process,.
Have you put any thought into this? Any feedback on approaches to incorporating into beanstalker if we do a branch/pull request to support this type of functionality?
It certainly looks interesting.
I'm almost giving up in configuration (too many small details), but let me ask: Do the Configuration Files Feature support it?
The Configuration Files, while looking very cool, don't support it. Those are more for customizing an individual instance upon initialization.
yeah, it looked like sorting out the environmentId, environmentName was a pain. Do know however that there are people out there using it heavily who are thankful for your contributions to the community. :)
The original goal for Beanstalker is to add value in Maven Projects.
While I admit this is a bit offside, I'd like to ask you if you see any source code which could work as a starting point, or a high-level desc (in terms of goals and config options)?
I think carrot-garden once wrote an EC2 Plugin. Isn't it more appropriate?
Aldrin:
thanks for brining this up:
https://github.com/carrot-garden/carrot-maven/tree/master/carrot-maven-aws-plugin
I got tired of beanstalk, and I use carrot-maven-aws-plugin
to bring up / manage my own replacement for beanstalk
cheers,
Andrei.
I think it's best to close this feature request as wontfix
In the time since I posted, Amazon have added features to beanstalk that allow you to customize software on an instance and resources associated with an application. This option is a nice standard way to do it, no need to build a custom maven impelementation. See http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environment-resources.html
They have also released an alternative to beanstalk called AWS OpsWorks: http://aws.typepad.com/aws/2013/02/aws-opsworks-flexible-application-management-in-the-cloud.html