WHY?
Short answer: because
“...okay, what version of the app do we need to deploy? Great, yeah, let me spin up a machine really quick. Running puppet… hold on,
I’m getting a puppet exec timeout, let me get into the code really quickly and fix something. Okay, things are looking good. Wait, what
version of $library do you need? Okay, one sec, let me append $package to the list of packages. Uh, hold on, the other machines have
a dependency resolution error. Give me some time, there’s a duplicate resource declaration. No, I have to do that one, the IAM setup
doesn’t permit access to route 53, which subdomain do you need? That’s on the old AWS account, give me one sec to add it to the
wiki, we still need some automation around provisioning route 53 entries. It looks like there are some errors getting at it from in front of
the ELB, are you sure the app is running? Yeah, let me double check to see whether there are any errors in the logs. Okay, it looks like
there are some permissions problems, we’ll need to change ownership of $dir for the app, let me take a look at puppet. Okay, the
daemon starts up, I get a 200 OK, does the app look good from your side? Which part? Let me check the environment variables. Okay,
yeah, it looks like puppet interpolated an empty string, the app is missing the token, let me add some validation and re-run puppet.
Does that look okay now? Okay, great.”
Can only take you so far before you reach Peak Sysadmin™