16 Dec 2013
Highlights of this release:
Updates for this release:
Highlights
New tasks for AWS Elastic Beanstalk
You can now facilitate Amazon Web Service's Platform as a Service (PaaS) offering AWS Elastic Beanstalk to quickly deploy and manage applications in the AWS cloud - this is enabled by three new tasks:
- Create/Update/Delete AWS Elastic Beanstalk applications
- Create/Update/Delete AWS Elastic Beanstalk application versions
- Create/Update/Rebuild/Restart/Swap/Terminate AWS Elastic Beanstalk environments
'Make it so' option for the create/update CloudFormation actions
To simplify common AWS CloudFormation usage scenarios, the Create stack action now allows to Update [the] stack, if it already exists.; similarly, the Update stack action allows to Create [the] stack, if it does not already exist.
Only shared options are supported
Please note that in both cases only the shared subset of options available for both actions is passed though to the 'Make it so' action - the more advanced options remain available via the dedicated tasks.
Updates
Release 2.2.3
This release addresses the following issues:
- Improvements
- TAWS-198 - The Elastic Beanstalk Environment task can create worker tier environments
- TAWS-101 - All tasks feature a 'How to use this task' help link to the online documentation
Release 2.2.2
This release addresses the following issues:
- Bugs
- TAWS-190 - The EBS Snapshot, EC2 Image and EC2 Instance tasks could yield an exception due to improperly accounting for the Eventually consistency of the AWS API
- TAWS-189 - The CloudFormation Delete action required the template field to be populated via the Create or Update action first
Release 2.2.1
This release addresses the following issues:
- Improvements
- TAWS-183 - The CloudFormation task now offers several samples via an inline dialog
- Bugs
- TAWS-182 - Elastic Beanstalk task names referred to Amazon rather than AWS
- TAWS-181 The Application and Application Version tasks lacked output variables
- TAWS-179 - CloudFormation resource output variable values used the stack id (ARN) rather than its name