Call for Action - Bring git back!

[Aldrin Leal]

Fellas,

Over the next few years, beanstalker has got huge traction and support. Yet it started from a day, back years ago, when I've got pissed with a Java PaaS and decided to take it with my own hands.

So basically, right now, I believe we've got the most comprehensive solution for AWS Deployment, and most of you will likely agree. Be it the number of downloads, or the number of projects based on the archetype found on github, or the amount of questions on Stackoverflow, I believe they're subtle metrics of its success.

However, it isn't easy dealing with Amazon. For instance, I've got a support case (# 78136031) open for two years, emails sent to Product Managers (ok, they got into other positions shortly - twice), discussions on Twitter, but I've never got as far as getting a solution.

Now with eu-central-1, things got worse. git endpoints are disabled, and I took the opportunity to get into Vegas to look for things directly. I've mentioned the case open for two years, and the lack of a line of communications means I can't really help support my users, and you're left on your own with the AWS stuff, which is okay for most persons, but not for me. I don't want to force my choice of tools, but of course, I'm biased.

(Consider I've made all the hassle to get a visa, get to re:Invent, and look for the people. Out of my own pocket. Ok, it is a passion, but its a hobby which you guys get the result for)

So think about it for a while: beanstalker allows users which doesn't run Linux (like me actually), or rely on git, and allow you to automate deployments with nothing but Java installed. This means portability. 

The official AWS tools were originally written in Ruby (slow and unreliable when it comes to managing dependencies on Windows), then had a powershell-based hack, and they're now converging on Python. 

At the very same time, things changed almost nothing on our side. And I'm still happy to see new users with questions, and special workloads, and archetypes. As far as I know, I've heard customers talking a lot when they discuss with AWS architects, and show its power. I'm not on competition, I just want the best of my tools.

However, I must remind you guys two things: Most of its development is done on my spare time. Sponsorship is limited, and sometimes my patience is, like what I've did with the Jenkins AWSEB Plugin, which I intend to overhaul. This didn't stop having a fork, and a little fight on the Jenkins mailing lists, which hurt my motivation to keep doing these things.

But lets focus on git. I actually met two PMs from Amazon in Vegas and explained my problem. We found out that:

• It is a shame to have a ticket open for two years without reaching someone with autonomy
• They deprecated git, as their opinion is that by averaging their slug size, it is not needed (REALLY?)
• In fact, the newer tools, git aws.push is simply a wrapper around git export and uploading to S3)

I didn't like the deprecation of the git endpoints for two reasons, which are:

• Not all projects actually use git. I use mercurial on Windows. It is not that I despise git. It is that makes a badass to just type a single command - or perhaps two -, and create, deploy and instantiate an environment on AWS.
• Java workloads are quite different from all the others, so a SCM to wrap our deployments are a bad thing. We only use fast-deploy to wrap the binary slug, to allow incremental
• Incremental is simply badass. For instance, an average slug size for Java starts at 25MiB. Losing incremental means a lot to me, as I happen to live in the other amazon and I can't affort the loss of productivity

The fact is that I don't like the idea of deprecating git, and yet AWS communication is horrible to say the least. I sent a couple of emails a month ago to no avail.

Which hurts my ability to bring you the best. I've hold it for years literally, but now I'm considering dropping maintenance, since there are several other platforms out there to help your deployment, and the amount of stress with Amazon is becoming overkill, specially since eu-central-1 disabling git

So lets get guerilla. I need you guys to help support me this time. I need a favor: Can you create a ticket on AWS Support mentioning you need the git endpoint activated, mentioning this email, and also mentioning case #78136031. you can also copy jeffbarr and randhunt at AWS. If possible, send me it its number so I can track it from here. If you don't have AWS support, open on the forum and explain - It really matters to me

(I'm also open for other ideas. We really need to get this message delivered.)

Thank you

--
-- Aldrin Leal, <ald...@leal.eng.br>

Master your EC2-fu! Get the latest ekaterminal public beta http://www.ingenieux.com.br/products/ekaterminal/