Cap-EC2 is pretty stable, and the rate of PRs has decreased, so I've decided to bump the version to 1.0.0.
- Remove the require of
capistrano/setup, so that people can make use ofcapistrano-multiconfig. @ashleybrown
- Stop using the
coloredgem, switch tocolorizeinstead. [@freakphp][https://github.com/freakphp]
- Update gemspec to explicitly use the AWS v1 SDK. @Tomtomgo
- Fix available roles for newer Capistrano versions. @AmirKremer
- Provide access to EC2 server tags within Capistrano recipes @eightbitraptor
- Fix sorting of servers when there is no Name tag @johnf
- Don't colorize status table output if STDOUT is not a TTY. @jcoglan
- Add
ec2_filter_by_status_ok?to filter out instances that aren't returningOKfor their EC2 status checks. @tomconroy
- Fix issue when tag was present in EC2 but had no value. @tomconroy
- Use AWS.memoize to speed up communication with AWS @cheald
- Use the instance's named state for searching for instances, rather than the code @ronny
- Allow instances to have multiple projects deployed to them. @rsslldnphy
- Fix the way instance tag matching works; the previous regex was not sufficient to ensure absolute matching of a given tag. @rsslldnphy
- Allow configurable setting of the EC2 contact point @christianblunden
- Handle no configured regions, (or specifically nil).
- Made
config/ec2.ymloptional, set all options by Capistrano variable. @rjocoleman - Remove requirement for default region to be set. @rjocoleman
- Removed monkey patching of
Capistrano::TaskEnhancements@rjocoleman - Instances don't always have a name tag, would cause
ec2:statusto blow up @rjocoleman
- Unbreak listing instances
- Don't return terminated instances when looking up instances from EC2
- Fix documentation to refer to correct tag for Stages @shaneog
- If you modified any of the tag names, the
ec2:statustable would blow up - Fixed a bug with stages
- Rename the default tag name used for determining to 'Stages' from 'Stage'
- Allow servers to be in multiple stages
- Initial release