{"push_id":889344918,"size":1,"distinct_size":1,"ref":"refs/heads/develop","head":"536819ffce0122c69ec4ac3e762a9ddab55054a4","before":"bd3c3b9f38c898bd52f5b32b8fdf25c4523083e9","commits":[{"sha":"536819ffce0122c69ec4ac3e762a9ddab55054a4","author":{"email":"61779cc052260166caf5044b633d3ad23459a853@vmware.com","name":"Mikhail Vyshegorodtsev"},"message":"Uses explicit template for setup-aws-infrastructure task\n\nWe needed to variablize the stack name used for the various aws\ninfrastructures, so we can no longer us the stack name variable to pick\nthe correct cloudformation template to use.  In this case it is fine to\nhardcode to a specific template which fixes the problem.\n\n[#108585160](https://www.pivotaltracker.com/story/show/108585160)\n\nSigned-off-by: Jonathan Barnes <jbarnes@pivotal.io>","distinct":true,"url":"https://api.github.com/repos/pivotal-golang/s3cli/commits/536819ffce0122c69ec4ac3e762a9ddab55054a4"}]}